OpenInsight Crashing and Not Responding Issues.


We have recently received a number of support requests from clients reporting that OpenInsight has stopped responding or OpenInsight has stopped working and crashed.  This is sometimes the message that OpenInsight has stopped working because it is addressing illegal memory, or that OpenInsight has stopped responding and you can opt to close it, ask Windows to correct it or carry on waiting for a close.  On further questioning, we sometimes find that there is an associated FS1030 or and FS231 error message.

In 99% of cases, the issue is the result of something environmental or that the UD has been incorrectly installed or some has changed something on the network, such as replacing the server and not reinstalling the UD correctly.

If you should be faced with an issue such as those above, we recommend that you thoroughly check the Universal Driver installation and even uninstall and reinstall the Universal Driver, whilst ‘closely’ following the installation manual.  We also suggest that you check for DEP running on the system because this also causes issues on older OpenInsight based systems.

However, below are a few specific things to consider:

  • FS1030 – This is usually a result of the SYSTEM USER either not being configured correctly with full permissions during the installation, or someone has decided to delete the user.  The latter is common where a server administrator (or outside IT contractor) is running a user audit and removing old users.  They don’t recognise the SYSTEM user or don’t understand the significance and simply delete it as no longer needed, or reset the SYSTEM user with restricted permissions.

 

  • FS231 – This error message is often attributable to an issue within the REVPARAM file, or where the REVPARAM file has been deleted or created with an extension, such as .txt.  One of the most common configuration issues is the SERVERNAME= parameter in the REVPARAM file not matching the name in the registry that was input during the installation wizard.  Sometimes, if you try to run the UD Manager that will fail with an FS231 error message, this is often a result of the servername being incorrect in the UD Manager’s REVPARAM file.

 

  • FS1019 – New server and workstation deployments often contain default firewall rules that block OpenInsight from communicating with the Linear Hash service on the server.  When this occurs a FS1019 or similar message will appear during OpenInsight start-up.  Revelation have published a white paper (knowledgebase article) on this issue and an accompanying Port Checker.  Both are available on request or from http://www.revelation.com/o4wtrs/KB_Articles/KB0269.htm.

 

  • OpenInsight Is Not Responding – This message often shows in the top of the OpenInsight window or in a message.  Three options are offered and one is to allow the program to run until completed. OpenInsight is actually working but the Operating System, often Windows 7 or later, thinks that it has stopped responding because OpenInsight is busy and not ‘currently’ communicating with the Operating System for a time.  Often waiting for the OpenInsight process to complete will result in the message closing itself (or going away) and everything returns to normal.  Some likely causes could be a resize or creation of a large file or a large indexing run. If this becomes an issue for users, it is often necessary to identify which process is taking the time and then to add some code to let the Operating System know that OpenInsight is working.

 

  • OpenInsight has stopped working and Will Close – This is a more serious issue because the operating system will forcibly close down OpenInsight.  We have recently experienced that running OpenInsight with a profile log eradicates this issue and that OpenInsight again crashes when the log is removed.  This has been an issue invoked by the driver in NETDRV being incorrect.  One recent installation of the Universal Driver 4.7.2 was being run with the UD 4.6 driver set in OpenInsight.  This was because the 4.7.2 driver was not amongst the options in NETDRV.  We completed the Universal Driver installation correctly by running the UD Client Install and the system immediately began to run correctly.  If you experience ‘any’ OpenInsight crashing or not responding messages, we would advise that the client driver is checked and make sure that the UD and the client are running as a pair – i.e. 4.7.2 server and 4.7.2 client.

Sprezzatura have a useful blog article which discusses the OpenInsight Not Responding issue in much more detail.  Click Here for the SENL article.

Of course, if none of the above help to eradicate your networking or OpenInsight crashing issue, please contact your local Revelation support person and they will be happy to investigate the issue further.

Finally, if you are running an older version of the Universal Driver, please consider an upgrade to version 4.7.2 which has some important enhancements, including a memory leak fix.  The upgrade from 4.0 is free and your local Revelation representative will be happy to process the supply of the upgrade for you.

Advertisements

Things just got a little quicker.


benchtestresultsThis will be my last posting of the day with regards to the new Universal Driver (UD) releases, I promise, no more interruptions to your day from me 😉

Everyone keeps talking to me about performance these days and I wanted to share with you that I have heard a whisper that a test using the UD 4.7.2 (and I believe the UD 5.0.0.4 because that has the same enhancements) is performing better than previous versions during a mammoth testing project.

Testing is on going and loads are increasing, but I’m hearing about 17,000 reads being completed in around 3 seconds.  Obviously different systems will perform differently, but if performance is important to you, then maybe now is the time to take a look at what OpenInsight 9.4 and the Universal Driver 4.7.2 or the 5.0.0.4 can do for you.

UD 5.0.0.4


benchtestresultsFor me, the release of the Universal Driver 5.0 for use with OpenInsight 9.4 was one of the best enhancements in recent times for people running OpenInsight.  It had new features that were sought after by many VARs and end users, and now it just got better with the release of 5.0.0.4.

Now available from www.revelation.com, this new version replaces all previous versions of the Universal Driver 5 and it is available at no cost to anyone who has purchased the Universal Driver 5.  Don’t feel left behind if you have an older version of the UD because we have an upgrade path for anyone running the UD and a new purchase option if this is your first time using the UD to enhance your deployed system.

So what’s all the excitement about?

The Universal Driver 5.0.0.4 resolves a potential memory leak /overrun issue when running in ‘debug output’ or logging mode.

It has also been enhanced to eliminate ‘hanging’ when shutting down the service.  This should allow sites to terminate and restart the Universal Driver without requiring a server reboot.

The new version addresses an issue that recently came to light where the record count and alpha values in the file header can get corrupted when several incomplete latent select / readnext are followed by a complete latent_Select/readnext.  This corruption has the side effect to cause the LK to expand rapidly.  A later complete select/readnext can repair the header and cause the UD to resize the table to normal size.  From the outside it looks like the service is bogging down for no reason.  In extreme cases the resize can crash the service and leave a huge file on the server.  It appears that this is a long-standing issue which may explain some of the issues witnessed by large sites.

The Volume Shadow Copy Service (VSS) feature now pauses the resizing thread and flushes all buffers.  Before 5.0.0.4 there was the possibility of a file being resized during the snapshot and of some new header record counts / alpha values not being written to disk.

Revelation have implemented the ability to pause the resizing thread.  The idea is to let the UD continue to queue files for resizing, pause the resize thread during the day so it does not slow the server, then release the thread in the evening to let the files catch up.

Revelation has also implemented a set-sizelock call inside the UD.  Prior to 5.0.0.4 the fix_lh program must OSBWrite the new sizelock into the header, which is not compatible with using a sharename to isolate the rev files.  The next UD Manager will support this feature.  The goal is to provide fine-grained control of resizing.  In theory you could pause the resizing thread, then view which files are going to resize, and control the order of the resizing by locking or releasing individual tables.

A “feature” where the UD will clear a sizelock of 1 has also been identified and removed in the new version.  Revelation has always stated that you presize a file, set sizelock to 1 and load it with data.  But, the UD clears the 1 on any select / readnext, making the feature less useful.  They have therefore removed this feature from the UD so that it is easier to pre-size tables and to leave them set to expand only.

The Universal Driver 5.0.0.4 software can be downloaded HERE.

UD 4.7.2


benchtestresultsFollowing several weeks of intensive research, working with one of our key users here in the UK and reviewing many thousands of lines of code, Revelation have now released the Universal Driver 4.7.2.

So why should a new point release be of such interest?

The UD 4.7.2 is a minor upgrade from UD 4.7 but it resolves a significant issue with corrupted table header counts and sizes, a potential memory leak/overrun issue when running in ‘debug output’ or logging mode, and eliminates “hanging” when shutting down the service.  This should allow sites to terminate and restart the UD without requiring a server reboot.

The UD 4.7.2 has been released for both the “NT” and “NU” versions.  This replaces all previous versions of the Universal Driver 4.7 and 4.7.1 and it is available at no cost to anyone who already has the Universal Driver 4.x.

The Universal Driver 4.7.2 fixes an issue where the record count and alpha values in the file header can get corrupted when several incomplete latent select / readnext process are followed by a complete latent_Select/readnext process.  This corruption has the side effect to cause the LK to expand rapidly.  A later complete select/readnext can repair the header and cause the UD to resize the table to normal size.  From the outside it looks like the service is bogging down for no reason.  In extreme cases the resize can crash the service and leave a huge file on the server.  It appears that this is a long standing feature which may explain some of the issues witnessed by large sites.

The Universal Driver 4.7.2 also now enables system administrators to more gracefully close down the Universal Driver in the event of a system crash. In such a situation the UD appears to have simply hung and most people are finding it necessary to aggressively terminate the Universal Driver before restarting the system.  This new version addresses this issue.

Please contact your system author (VAR) or your usual Revelation Representative to obtain your UD 4.7.2 upgrade or to discuss upgrade options if you are running an older Universal Driver (1.5 2.x or 3.x).

 

Important News about the UD


benchtestresultsIf you are running, or have clients running, multi-user systems based on OpenInsight, there are a couple of postings in the WORKS discussion forum that you will have seen this morning relating to some big changes to the Universal Driver line up.

Because some of my readers are not on WORKS and because these new versions of the Universal Driver have some important fixes and new features that I know most end users will want to take advantage of I plan to write a few separate postings on each piece of news.

In the meantime, I would like to personally thank Bob Carten and Bryan Shumsky and one of my key UK clients who have worked extremely hard in identifying the cause of and correcting an issue in the Universal Driver.  Also, thank you to the team at Revelation who have added some much sought after new features in the UD5 and who have rolled those back for those of you running on OpenInsight version 9.4.

Watch for more coming from me over the next hour or so……

UD5 vs UD4.7


benchtestresultsI don’t look at the Knowledge Base on www.revelation.com enough and I’m often surprised at the information that resides there.  Today was no exception and just proves how long it was since I took a look and how important it is to check there fore time to time.

I have been talking to a few people about the UD5 and the upgrade process from earlier versions of the Universal Driver and the benefits of the upgrade and performance ‘always’ comes up.  I was therefore pleasantly surprised to see that Revelation have recently published some bench test results which compare the Universal Driver 4.7 to the Universal Driver 5.0, running both with and without encryption.

There are four tests which were completed using all three configurations (UD4.7 without encryption, UD 5.0 without encryption and UD 5.0 with encryption).  The results are nicely summarised in a graphic and there are also detailed screen shots of the results screens and the parameters used for each of the tests – totally transparent reporting.

I’ll leave you to review the knowledge base article, but it was good to see that the UD 5.0 is consistently faster than the UD4.7 when running without encryption. 

Running with encryption sees a decrease in performance of around 2 to 2.5 times the time taken in the UD 4.7 without encryption.Which is expected for obvious reasons.

Please see www.revsoft.co.uk for more details about the Universal Driver or contact your local Revelation representative or application author to discuss your upgrade to the UD5.

Universal Driver 5.0 Released


I am pleased to announce that the Universal Driver (UD) 5.0 is now available to anyone running OpenInsight version 9.4.

Originally planned to only be supported with the forthcoming OpenInsight 10 release, interest has been sufficiently high in the UD 5.0’s new features that Revelation has released the new version with support for the widely adopted OpenInsight version 9.4.

The Universal Driver that is bundled free of charge with all of the 9.x releases, remains Universal Driver NUL 4.7.  However, the Universal Driver NUL 5.0 is only compatible with OpenInsight 9.4.

If you are purchasing a new Universal Driver License for use with OpenInsight 9.4, you now have the choice of using the Universal Driver 4.7 or the newer Universal Driver NUL 5.0 – please specify your preference when ordering.

If you are an existing user and you are running OpenInsight 9.4 and the Universal Driver 4.7 or Universal Driver NUL 4.7, then we have an upgrade path for you to get to the version 5.0.  Again, drop us a line and we will be pleased to provide you with the appropriate costs.

If you are an existing user and you are running an older Universal Driver, then you’ll need to purchase the upgrade to the UD 4.7 and then the upgrade to the UD 5.0.  Again, we will be pleased to quote for your specific needs accordingly.