When I attempt to execute the Network Monitor, I get an error and it fails to open. I have attached a screenshot of the error message. Hopefully someone can help me out. Everything was working until I applied the hotfix.
We've been trying to reproduce the error here in house, but are unable to. Could you provide more details? Is there something special with your Network Monitor configuration? Can you go to the Add\Remove Programs window in the Control Panel and click our Support Information link for the Toolset product and provide us with the 4 digit Version number?
We are really suprised that you are receiving this error after the hotfix. The hotfix did not touch the Network Monitor tool and it did not install any versions of MDAC. Do you know if any other software has been installed on the box lately?
Thanks,
There doesn't appear to be anything special about our installation. It's the only application running on a machine inside a firewall on our corporate network. The machine is running Windows XP SP2 with a P4 1.8 GHz with 256 MB of RAM. The version number for the toolset is 9.1.0.1. I hope this helps.
The "unrecognized database format" error I was receiving was not fixed by the compact and repair database feature in Network-Monitor-Maint.exe. Do we need to start over with a new database? The file is nearly 3 GB, I believe. We'd want to keep it of course, because it has months upon months worth of network data.
The Network-Monitor.cfg file is actually an Access database file. Microsoft Access has a 2GB limit. This may be what you are running into. Can you rename the file to Network-Monitor.cfg.mdb (adding the mdb extension) and open it in Microsoft Access? If it is running into the 2GB limit, you'll need to adjust your nightly maintence settings or start with a new database. I don't know the best practices for your situation, but a call to our Tech Support should get you some recommended values.
It may be that the database just got corrupted. Microsoft Access has the ability to try and fix it. If that is all, then after fixing it, remove the .mdb extention on the file and try to open Network Monitor again.
