Problem:
When you start an AOS, you may notice it takes a very long time before the service gets the status “Started”. A possible cause is left-over data in SysClientSession table. When starting up, the AOS seems to check if the client is still around. The SysClientSessions contains the data for the client sessions that are currently active in the system.
Solution:
1. Shut down AOS for sing instance or all AOSes for multiple instances (not an ideal way in Production)
2. Use SQL Server Management Studio and run this sql
SELECT SESSIONID, SERVERID, VERSION, LOGINDATETIME, LOGINDATETIMETZID, STATUS, USERID, SID, USERLANGUAGE, HELPLANGUAGE, CLIENTTYPE,
SESSIONTYPE, CLIENTCOMPUTER, DATAPARTITION, RECVERSION, RECID
FROM SYSCLIENTSESSIONS
DELETE FROM SYSCLIENTSESSIONS;
3. Delete all client records
4. Restart AOS(es)
When you start an AOS, you may notice it takes a very long time before the service gets the status “Started”. A possible cause is left-over data in SysClientSession table. When starting up, the AOS seems to check if the client is still around. The SysClientSessions contains the data for the client sessions that are currently active in the system.
Solution:
1. Shut down AOS for sing instance or all AOSes for multiple instances (not an ideal way in Production)
2. Use SQL Server Management Studio and run this sql
SELECT SESSIONID, SERVERID, VERSION, LOGINDATETIME, LOGINDATETIMETZID, STATUS, USERID, SID, USERLANGUAGE, HELPLANGUAGE, CLIENTTYPE,
SESSIONTYPE, CLIENTCOMPUTER, DATAPARTITION, RECVERSION, RECID
FROM SYSCLIENTSESSIONS
DELETE FROM SYSCLIENTSESSIONS;
3. Delete all client records
4. Restart AOS(es)
No comments:
Post a Comment