WinGate Engine service terminated unexpectedly

[llupin]

I was just commenting to myself this morning how well Wingate has been behaving lately. When I got to the office howqever I found that the enhgine had stopped. I restarted it and looked in the event viewer to find the following error. I updated Wingate to 6.0.3 and less than a hour later it shutdown again. Any ideas?


Event Type: Error
Event Source: Service Control Manager
Event Category: None
Event ID: 7031
Date: 9/23/2004
Time: 9:13:51 AM
User: N/A
Computer: PROXY
Description:
The Qbik WinGate Engine service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 0 milliseconds: No action.

[adrien]

Hi

Can you please check through your log files to see what are the last things to be logged before it died?

We haven't had any reported issues like this, so I wonder whether something external took WinGate out.

Adrien

[llupin]

I maybe having some hardware problems. I am building a new machine and will move everything over to it early next week. If it continues to happen I will let you know.

[adrien]

OK, thanks

Adrien

[jacky]

Hi,

Well I got a problem with the Wingate server too, but doesn't seem to be the exact same thing. It's already happend a few times, and it's really annoying!

What's happenning is that the wingate server seems to "freeze", it doesn't work/answer anymore. This means on the client computers that we just don't have a connection, but no error messages either
About that: why WGIC doesn't show the messages as it used to (in v5) ?? Like the dialing/checking username/error ones for example?? Cause now when we try to get to the Internet, and nothing happens, we have no idea if it's working, it's just dialing and connecting to the Internet and we should wait a little, or if there's an error, or if the server has frozen again... :(

And back to the main problem: the server freeze, on the client nothing, so I have to go to the "server" computer to kill wingate.exe using the task manager, and then start the engine again. If I don't kill wingate.exe, and try to start GateKeeper, I have a message saying that he got no answer from the server...

Any idea how to fix this please?
Thanks

PS: running wingate 6.0.2 b1001

[labull]

Jacky,

Try the instructions below.

Larry

[adrien]

Hi Jacky

Do you know what WinGate is doing at the time that it freezes (this should be in the log files).

Also.

1. Are you running any WinGate plugins?
2. Do you have any other AV product running on the WinGate machine.

If you have another AV running on the WinGate machine, that can seriously disrupt WinGate, as WinGate touches a lot of files many times a second - so if an AV is scanning these changes, the performance of the system can be drastically affected.

We normally recommend turning off AV scanning on the WinGate directories.

Adrien