Logs in Activity Window won't refresh...

[edmund.remo]

Hi Admins,

I have noticed that the logs in the activity window of our Wingate Version 5.0.1 [766] won't refreshed. The old logs are still displayed in the activity window even the users are no longer accessing the internet, though it still monitors the currently browsing users. However, this incident is not normal, as previously the activity window shows only the users who are presently accessing the internet.

Need you assistance please...

Thanks

Edmund

[Nev]

Try installing the latest version, Wingate 6.2.1

http://www.wingate.com/download.php

With these amazing improvements to the version you are using;

http://forums.qbik.com/viewtopic.php?t=4215

[edmund.remo]

Hi,

How about fixing this bug without upgrading the Wingate Version, please give me prcedures to make this issue resolved. Since, this error occurred just recently.

Upgrading the version, as I have tested, makes my puresight, visnetic firewall and antivirus won't work. I have to upgrade also these plugins for them to work.

Imagine just to fix that only glitch, I have lots of things to consider...

I hope you understand.

Thank you very much.

Edmund Remo

[Pascal]

By "Activity Log" are you indicating the history database or the actual activity window?

If it is the history database - the files sometimes get corrupted when there is an abnormal system restart (BSOD or other failure condition). In those cases, stop the WinGate engine and copy HISTORY.DBF and HISTORY.CDX to a separate folder as a backup. Then delete those two files. When the engine starts up it will automatically recreate the files and history logging should resume. Later version of WinGate will attempt fixes and recovery once this occurs and will automate as much of that process as possible.

If it is the activity window, have you tried closing GateKeeper and restarting the Engine? Just rebooting the server should resolve that.

[edmund.remo]

Hi,

The actual activity window is what I am referring at. I did try several times - restarting the gatekeeper and the engine, as well as rebooting the server, the issue wasn't resolved by the procedures.

Thanks again for your prompt response.

Edmund

[Pascal]

Hm. Activity is never stored on disk, so a restart of the machine should clear it up. After a fresh restart, does the system keep on running normally for a certain length of time?

Do you typically leave GateKeeper open and connected to the Engine?

[edmund.remo]

Hi Pascal,

Apparently, when you restart the machine, the logs will be refreshed… because the users will be cut on the connection and all the services and everything will also be cut/stop. However, when the users begin to access the internet, this issue will again subsequently occur. “The user logs will remain still in the activity windows even though they are no longer accessing the internet or outside”.

I normally run the gatekeeper open and connected to the engine at all times, obviously for the reason of real-time monitoring. I am doing this for three years now, so this should not be the issue.

And, as I’ve mentioned, this problem is just recently experienced…

Thank you.

Edmund

[adrien]

try shutting down the client machine that shows as still connected

I think you will find that the reason they still show in gateKeeper is because they are still connected to WinGate. Nothing as you say has changed in WinGate, so for behaviour to change, something else must have, e.g client service packs, client software etc.

Adrien

[edmund.remo]

Figuratively, as I’ve said, the activity window still displays the logs of their previous activities even though the users are no longer connected. Similarly and literally, after office hours --all workstation computers are off and obviously no other users are accessing the internet or the gatekeeper. And yes, nothing has changed in the configurations of the wingate and on the other components in the server… prior to the occurrence of the error.

Thanks, Edmund

[edmund.remo]

Hey Admins,

Any definite answer with my query... ?

[SkyMan]

Did you ever delete the history.cdx and history.dbf as suggested?

Are you monitoring GateKeeper on the WinGate server or on a remote system?

[edmund.remo]

Did you ever delete the history.cdx and history.dbf as suggested?

-- YES...Twice

Are you monitoring GateKeeper on the WinGate server or on a remote system?

-- On the WinGate server

[edmund.remo]

UPDATE please!

[Pascal]

I normally run the gatekeeper open and connected to the engine at all times, obviously for the reason of real-time monitoring. I am doing this for three years now, so this should not be the issue.

And, as I’ve mentioned, this problem is just recently experienced…

What has changed recently? From your descriptions, WinGate itself has not changed, so the problem is not there. This leads me to believe that:

(a) A setting / configuration was changed
(b) A service pack or software update was installed on either the clients or the server to affect this

You could try working out which machines are affected by this and which machines are not. Then work out what has changed on all of the affected machines.

That should give you a basic handle on the problem at least.

[edmund.remo]

Dude,

I did not change anything in the configurations! That is why I am asking you (the support and developer of this application) what causes the problem! Good that it has no effect to the users, though we couldn’t monitor who are connecting in real-time!

Don’t throw sarcastic answer on my query… as I will not ask you if I, myself changed something prior to the issue that caused the problem!

Evenmore, you should also supposedly know the ins and outs of your product – whether we’d changed or not the configurations. You should have answers to resolve every issue… I am very willing to coordinate, help and wait for your assistance to further resolve the issue, BUT again don’t answer me negative.

[SkyMan]

Dude,

Pascal is trying to be very thorough in getting the details of your problem and you accuse him of being "sarcastic"?

Listen, you're using a version of WinGate that first came out over 4 years ago. WinGate has undergone MAJOR revisions and the source code for 5.01 hasn't see the light of day for years. Most companies wouldn't even bother talking to you about supporting a product that old. Try getting Microsoft to fix a bug in Office 2002/XP.

Yet here are Pascal and Adrien trying to help and your response is to use words like "supposedly", "sarcastic" and "negative"?

You accusatory tone and unwillingness to upgrade will not get your problem resolved.

[Pascal]

Edmund, if you have been using the software for a number of years without any issues like this it is almost impossible for it to suddenly develop this flaw on it's own. Software is a fixed, immutable entity. The environment in which it operates however can influence how it operates.

It cannot just fail on it's own, it fails either because of a bug (which would be a consistent failure once the conditions are met) OR because of an environmental change which introduces unexpected behavior.

This change can be something as subtle as a hardware change, a driver change or even a Windows Update. This is why I am suggesting that you check back to when the problem started occurring and see what changed at that point in time. As you had a perfectly operational system up until then. This would at least give us a starting point to try and work out what is wrong.

So the alternatives before you are:

1. Work out what changed, post it here and we'll see if we can come up with a workaround.

2. Take advantage of the version upgrade option. You can re-use an existing license key with any newer version of the software. Qbik traditionally release bug fixes through new releases, your keys are forwards compatible but without access to the new features in the newer releases. This would mean you'd need to find an alternative to Visnetic Antivirus however, so if that is not possible you will not be able to take this option.

3. Upgrade to one of the releases that supported Visnetic Antivirus. 5.0.1 is now four and a half years old. I'd recommend trying 5.2.3, the last release of the 5.x branch. I don't have a download location at hand, but I'll ask the support team to update this post with one for you.

[logan]

Hi Edumund,

Here is the download location for WinGate 5.2.3

http://downloads.qbik.com/qbiknz2/archi ... 01-USE.EXE

[deftech]

deleting the history files out of the root of the wingate folder fixed this issue with me. :) Just had this problem recently, so I'm providing feedback a little late.