Hi Roberto,
We are simply unable to reproduce the timestamp issue here. I also checked with another customer who has been running Unbrowse (the GUI) on a quiet network for weeks. No timestamp issues. If you still receive these errors, can you do the following ?
- Go to the Program Files\Unleash Networks\Unbrowse\BIN directory
- Rt click on the ATSNW3.EXE file. This is the trap receiver server.
- Go to Details , Product Version
It should read something like 1_6_0_1297
Did you get a chance to test the timestamp issue with the GUI Trap Console ?
--
When these fail, it usually makes the whole application fail and no more traps are received until I run t2sql again. Are you aware of any problems that might occur with these?
This is typical VBScript behavior. You can add the following statement to the top of the script to prevent it from bailing out on errors.
Alternately, you can use Ruby instead of VBScript. Sadly, there is no sample yet.
Let me know how it goes,
Best,
Vivek