Sims.Net & Solus 2 - Phantom Users Issue

We've come to run a couple of patches in Solus 2 for Sims.Net and when we click the Sims Information button and look at the Information about your system we are told that there are a shed load of users still in Sims.Net under The following list of users are recorded as currently using your system....?!

This is at midnight and after a shutdown of all our workstation clients and a reboot of the Sims.Net server. How do we clear this list / make sure that there are no users logged in? A search of Capita Support Net has turned up nowt.

In the hazy distant past I seem to remember dealing with phantom users in Sims.Net when I still had hair. I thought this issue had disappeared?

Thank you.

Confused-in-Warwickshire.

*BUMPY*

Cant say I've seen this error but then again I check via SQL Server Management. Have you check to see what SQL Server Management says?

Try this bit of code:

Code:

---

use master;

select distinct sysprocesses.loginame,
/* sysprocesses.spid, */
sysprocesses.hostname,
sysdatabases.name,
/* sysprocesses.nt_username, */
/* sysprocesses.login_time, */
sysprocesses.status,
sysprocesses.memusage,
sysprocesses.dbid
from sysprocesses


join sysdatabases on sysprocesses.dbid = sysdatabases.dbid


where sysdatabases.name = 'sims' OR sysdatabases.name = 'fms'


order by sysdatabases.name, sysprocesses.loginame

---

Replace the sysdatabase.name line with the names of your actual dbs there are also a couple of extra lines that i've commented out that you could use to show more details but i think it's mostly redundant.

Mostly i would ignore that message about phantom users and use this bit of code.
It is possible that a machine that is logged in somewhere but is not in use shows up as a connection, because teh homepage widgets all poll, check, talk to teh server.

Some schools of thought advocate putting the db into single user mode, the problem with this is, it's not picky about who that user is, and once i found that everytime i remotely restarted offending PCs another would take it's place, and even i was blocked out.

I usually turn off the tcp/ip protocols from SQL config and also remove access to the sims share where the connect.ini is. Anyone with a local connect.ini that points straight to the server will get through still, unless the tcp/ip is off.

then i do all i need from a console session.