6.0.1 hard crash

[llupin]

While 6.0 has been a little shaky, occassionally locking up, it had run about as good as any version since 5.2.

I upgraded our server to run 6.0.1 last week so we could use our puresight license. This moring the server spontaneously rebooted. Afterwards I got a message that a service hadn't started. The event log showed that wingate failed to start. The reason for the reboot was simply listed as an unexpected restart.

Wingate was actually running but it was doing so using 99% of the cpu. This is running on W2K server SP4.

I tried unistalling the AV and puresight pluggins to no avail. I could run gatekeeper remotely but not locally as the CPU was being hogged by wingate. I tried stopping extraeous services such as ENS but nothing worked.

I uninstalled wingate and reinstalled it and loaded my users database from a registry backup. So far it is working again.

I didn't copy my upgrade key so I reinstalled by loading 5.2.3 first then I installed 6.0 and finally 6.0.1. If I tried to install 6.0.1 after 5.2.3 it said that it could not recognize the key but 6.0.0 would upgrade it to the new version.

I'd rather not have to do this again in a week. If anyone has any suggestions I would greatly appreciate it.

[Pascal]

Wingate was actually running but it was doing so using 99% of the cpu

That is normally caused by a corrupted history database (Usually corrupted by an unexpected stop of WinGate - through a system crash / power outtage / etc.

Normally, you can simply copy the history.* files from the WinGate folder to your backup folder (If you want a backup) and then remove them from the WinGate folder.

Our next planned release has a more robust startup of the history system, which will attempt further, deeper fixes on it if it fails to start the first time.