Sls Won't Start Folgen
SLS 9.30.2725
This is an installation that has worked fine for over a year. Yesterday I went to check license stats and the License Server splash screen appeared with "Loading ..." shown but disappeared after about 5 seconds. Checking Services shows the Seagull License Server service is not running. If I try to manually start the service it fails with the error "Could not start the Seagull License Server on Local Computer. Error 1067: The process terminated unexpectedly".
There is a log file created at C:\Documents and Settings\Administrator\My Documents\Seagull License Server\11082013.txt:
2013-11-08 11:59:20 1800 Information Network Trace OK <Client>: ---------- Client Connecting ------------
2013-11-08 11:59:20 1800 Information Network Trace OK -- Supported Protocols Enumerated on System --
2013-11-08 11:59:20 1800 Information Network Trace OK -- Supported Protocols Enumerated on System --
2013-11-08 11:59:20 1800 Information Network Trace OK -- Supported Protocols Enumerated on System --... masses of the same line repeated
2013-11-08 11:59:21 1800 Information Network Trace OK -- Supported Protocols Enumerated on System --
2013-11-08 11:59:21 1800 Information Network Trace OK -- Supported Protocols Enumerated on System --
2013-11-08 11:59:21 1800 Information Network Trace OK -- Supported Protocols Enumerated on System --
I went to Add/Remove Programs and did a Repair on the SLS installation - same problem. I've also re-booted the server (Windows 2003) and the problem persists.
I was considering completely uninstalling SLS and re-installing but wasn't sure if that would use up a 'life'?
3 Kommentare
Domingo Rodriguez
Moderator
Yes, you will be able to fully uninstall, then reinstall and reactivate License Server. This won't use a new activation attempt as the computer hardware is exactly the same. Please make sure to have your product key code at hand when doing the upgrade.
By 'fully uninstall' do you mean de-activate too?
The daylight savings issues does not apply here as according to the thread you linked to "Switching back to Standard Time in the fall does not cause a crash. To correct the problem, you simply need to restart the Seagull License Server service from the Windows Services panel."
The fix was to uninstall BarTender and SLS, then delete some registry entries and files (list provided by Seagull Support) before re-installing.
Bitte melden Sie sich an, um einen Kommentar zu hinterlassen.
