Strange windows when I tried to launch OP log viewer

[A884126]

Sometimes when I launch OP Viewer I got the following pop up windows saying the database is read only and I have no permission to access to it. I have then to launch it again in oder to successfully open it.

[Manny Carvalho]

Possibly a corrupted database. In log viewer mark it corrupted and create a new one on the next boot. See if that helps.

[Rickster100]

Hello A884126,

Its not just happening with this version. Ive seen it happen with all the versions of Outpost I have used. It doesnt happen very often but ive found that just trying to open the database again corrects the issue as you have already found and without having to reboot and repair it. Another Outpost quirk.

[The_Mayor]

I agree -- happens every once in a while with OP - latest release as well as OSS RC2 -- just closing the message and trying again works (although sometimes I have to do that twice -- but "third time is a charm"). When it first happened, I checked the database off-line and it was fine. As Rickster said, just a "quirk".

[Manny Carvalho]

I've never experienced this particular error myself. It is a quirk then.

[Rah]

A little off topic, but very relevant.

Marking to repair and rebooting, to me, is the long way around a simple operation of repairing an ODBC database. Here's what I do when it gets corrupted (or I think it's corrupted).

1. Go to Outpost Tools menu and turn off Enable Logging.
2. Under Start/Administrative Tools, select Data Sources (ODBC)
3. In the menu that appears, select Outpost Database and click Configure...
4. Click Repair...
5. You should get a confirmation it is repaired.
6. Go turn back on Enable Logging in Outpost.
7. It's done and you didn't have to reboot.
   

Just my 2 cents worth.

[Rickster100]

Thanks Rah, for the information. I would just add to that to disable OP's self protection first before doing this.

[Manny Carvalho]

A little off topic, but very relevant.

Marking to repair and rebooting, to me, is the long way around a simple operation of repairing an ODBC database. Here's what I do when it gets corrupted (or I think it's corrupted).

You can certainly do a repair this way but I've always felt that, when problems arise in the log viewer database, the most expedient thing in the long run is to blow it away and start with a new one rather then repairing the old one. It's anecdotal on my part no doubt but I think you save more time this way.

[garry]

its just a bug with outpost, most likely your databse is fine, just press log viewer again and it opens.. behaviour will happen with or without antileak/self protection