simonwhitelock
MIS
I have been running SMS for about a month now and have a problem with Software Metering. I have a critical error appearing under my site status alerts against SMS_Licence_Servicer_Manager and SMS_Collection_Evaluator (I assume the two services need each other to operate effectively).
The error messages reported on SMS Licence Server Manager say: The software metering server service is not running on "SMSUK".
The error messages reported on SMS Collection Evaluator say: Microsoft SQL Server reported SQL message 3023, severity 16: Backup, CHECKALLOC, bulk copy, SELECT INTO, and file manipulation (such as CREATE FILE) operations on a database must be serialized. Reissue the statement after the current backup, CHECKALLOC, or file manipulation operation is completed.
I am running SMS 2.0 SP3 on a Win2K Server Box with SQL 7.0.
I am really hoping a rebuild isnt neccessary as the SMS Server has a full database now and running like a dream in all other aspects.
If I restart the services or reboot the machine all is fine for about 1 hour and the problem comes back.
Has anyone else come across this problem and know what could be the cause ?
Perhaps it could be the fact that I set the SMS database backup from within SQL Manager and not SMS itself... ??
The error messages reported on SMS Licence Server Manager say: The software metering server service is not running on "SMSUK".
The error messages reported on SMS Collection Evaluator say: Microsoft SQL Server reported SQL message 3023, severity 16: Backup, CHECKALLOC, bulk copy, SELECT INTO, and file manipulation (such as CREATE FILE) operations on a database must be serialized. Reissue the statement after the current backup, CHECKALLOC, or file manipulation operation is completed.
I am running SMS 2.0 SP3 on a Win2K Server Box with SQL 7.0.
I am really hoping a rebuild isnt neccessary as the SMS Server has a full database now and running like a dream in all other aspects.
If I restart the services or reboot the machine all is fine for about 1 hour and the problem comes back.
Has anyone else come across this problem and know what could be the cause ?
Perhaps it could be the fact that I set the SMS database backup from within SQL Manager and not SMS itself... ??