Join The Works program to have access to the most current content, and to be able to ask questions and get answers from Revelation staff and the Revelation community

At 30 APR 2002 03:33:43AM Paul Rowe wrote:

I posted a message a couple of weeks ago regarding a problem with the NT/2000 Service, 2.1, running TCP/IP on a Win 2000 server. All workstations are all NT 4.0. OpenInsight 3.7.0. I haven't got any closer to resolving the problem at this stage.

When a machine needs to be rebooted while in OpenInsight (e.g. the machine has locked up) the user remains listed in the SYSLOGINS table. If they try to log into the application again (after rebooted the machine) they get the error message:

Cannot select on SYSLOGINS, lock held by another user.

Logging in with a different station id allows the user to log in, but the entry remains in the SYSLOGINS table, reducing the number of user who are able to get into the system. The only way to get rid of the rogue entry has been to restart the NT/2000 Service. This is quite drastic, as all of the other users have to log out of the application.

Is this a possible bug in the NT/2000 2.1 service? Is there some setting I am missing? Is there any other way to clear out the rogue entries?

Paul Rowe

Vernon Systems Ltd

View this thread on the Works forum...

  • third_party_content/community/commentary/forums_works/5ffec3b00f68b45a88256bab00298a09.txt
  • Last modified: 2023/12/30 11:57
  • by 127.0.0.1