We have been having some lock ups at a client site. The system hangs on the splash screen. Generally, we can have everyone log out and then knock off the users that are still logged in and the system unfreezes. We thought the issue was multiple login sessions open on a single workstation but was able to rule out that as the problem thanks to Don's login utility.

They did have the NT 2.1 service set to Named pipes, so I changed the registry settings to mixed protocol (Named pipes -] TCP/IP) but the problem got much worse. One curious item I noticed, after shutting down the frozen splash screen, I was checking the revparam file in the main OpenInsight directory. As soon as I single clicked the Revparam file in Explorer, Explorer froze up on me. I closed the Explorer and reopened. I could click on any item in the OpenInsight directory except the Revparam file. We asked all the users to log out and one user was still remaining on the open files list. As soon as we knocked her off, the "lock" was gone. Any ideas why we are getting hanging OS exclusive locks on the Revparam file? I have switched the client back to Named Pipes because the Mixed Protocol was causing lock ups every hour. I did read a post that there was a corrupt DLL problem with 2.1 that caused hanging locks on OS files with the mixed protocol setting but we purchased the upgrade to 2.1 in early 2004 well after this post stated the error was corrected.

Locks using TCP/IP with 2.1 Service

Could this still be the problem? Would this corrupt DLL cause some issues with named pipes also? Thanks, Sandra

System:

OpenInsight 4.13a

Operating system Windows XP, Windows 98SE, and 1 Windows ME

(they are working on replacing the 98's but it will take a while)

NT Service 2.1

Server: Dell PowerEdge 2600 Pentium 2.0 Ghz. with 500 Megabytes of

Ram. Windows 2000 with Terminal Services activated. I do have the setstation feature enabled to provide a unique station id for the terminal service clients.

Sandra,

I did email you twice some additional questions (one before and one after your email suggesting that you aren't receiving mine). Since I still haven't heard back from you I'll post them here:

1. Was the service stopped and restarted after the registry changes were made?

2. Is the machine that locked the REVPARAM file (or any other machine) set to go into sleep or hibernation mode during inactivity? We've had similar issues with system locks hanging around due to this issue.

3. Can you tell us what is contained in this REVPARAM file?

dbakke@srpcs.com

SRP Computer Solutions, Inc.

Thanks for the response. For some reason I don't seem to get your emails. I will check our spam filter settings.

1. We rebooted the server just to make sure we had a clean start.

2. I am not aware of any of the machines set to hibernation mode, but I will check out this lead.

3. The REVPARAM file contains serveronly=1 and a carriage return. I found that the carriage return at the end was needed for the NT service to pick up the setting.

Thanks again for your help.

Thanks, Sandra

Sandra,

Re the 2.1 patch - I looked into my goodies folder and found a dll - Rclsrvr.dll with date 6 Nov 03. I had clean forgot the context of this patch and application. This may be of help. Suggest that you contact Kevin with site details if you need to obtain it.

Regards

Richard Bright

I think this is it. The date on the file we have is 10/3/2003. I will call Rev tomorrow for the patch DLL. I just thought we had the most recent version since the client bought the upgrade from the NLM service to NT service in 2004. Thanks! - Sandra

Sandra,

The patch that Richard is referring to was where I was going, especially if you were encountering anything similar to item #2 in my last list of questions. I didn't want to have you jump through a hoop until I was relatively confident this is probably what was happening in your situation. Here's a thread that provides some more detail on the nature of the problem.

dbakke@srpcs.com

SRP Computer Solutions, Inc.

Sandra,

Sounds like Richard and Don have given you some good advice so far. I have something of a shotgun approach:

Confirm That there is only one revparam in each data directory and that none of them have anything more than "ServerOnly=1"

Confirm that the Registry is cleanly set back to use Named Pipes:

AnonymousUserName=NONE

NamedPipeName=LHSRVC

TcpIpPort=NONE

Confirm that there is only one copy of the Service installed - do a search for "lhsrvc.exe"

Create both the lh2.log (in the OI directory) and the lhsrvc.log (in the 2.1 Service directory - don't forget to restart the Service). We can find out if it is falling down on the OI side, or the Service side.

Lets start with that.

Kevin

View this thread on the Works forum...