Build Number (Full Version)

All Forums >> [Web & Mail Security] >> GFI WebMonitor



Message

Charlie IT -> Build Number (12.Jun.2009 8:32:48 AM)

I just downloaded and install the new webmon. Problem is when I check the version informaiton it displays build Number 20090403. Is this correct?
I thought it should be 20090515
file size 40.4 MB (42,435,415 bytes)



DrewE -> RE: Build Number (12.Jun.2009 8:40:49 AM)

Yes, the latest build should be 20090515.
  1. Where did you download the build from?
  2. Where are you looking at the build information?
Can you clear out Internet Explorer's cache and cookies and check the build information again?  Also, the build information should be in the registry under HKEY_Local_Machine\Software\GFI\WebMonitor\build. Does this registry key also show you the older build number?



Charlie IT -> RE: Build Number (12.Jun.2009 8:48:09 AM)

The reg shows the correct build 20090515 and does not show the old build number.
I cleared out the IE cache and cookies.
When I open webmon go to the version Information it shows Build Number 20090403



DrewE -> RE: Build Number (12.Jun.2009 8:48:57 AM)

Sounds like something else may be caching this page. Have you tried a restart of the MS Firewall service and the GFI WebMonitor server? Do you have any other caching proxy on your network?



Charlie IT -> RE: Build Number (12.Jun.2009 8:50:46 AM)

yes, I did a hard restart after the install. no other proxy servers.

I did restore the webmoncfg.txt and avapicfg.mdb so not to lose my settings.
could that be causing the error.

yes I just found it in the avapicfg.mdb changed the versioninfo to the correct build
restarted webmon now it shows the correct build.

Is there any other way to export/backup the setting in webmon so I can do a restore ?
In addition does restoring the old avapicfg.mbd have any effect on the corrections in SR1?



DrewE -> RE: Build Number (12.Jun.2009 11:27:04 AM)

I'm not aware of the specific changes in avapicfg.mdb between these two builds, however it certainly has the potential to cause some trouble. Depending on the changes made by our developers between these two editions it may not be anything to worry about. Typically, any issue with this would show up as you not being able to save a setting. That is you make changes to the configuration, click save, and when you look at the page again the settings are gone.



Page: [1]