Recordings report as 'Failed'

[Talcum]

I've found a very big problem. I've got 22 recordings that are perfect and stored on my drive. GBPVR has played them back for me many times. Today, I went into my recordings and they are all reporting as 'FAILED'. These are recordings from days to weeks ago.
If I view them in the 'Video Library', they play back in their entirety without problem.
I've stopped the recording service and changed my GBPVR.MDB to GBPVR.MDB.BAD and renaming GBPVR.MDB.ORIGINAL to GBPVR.MDB. This hasn't helped. I'm also finding that every day, my GBPVR.MDB is growing to 60MB without ever making any schedule changes from my original 14MB GBPVR.MDB.

Is there any way to get those programs to show back up as 'READY'?
I've converted everything (GBPVR.MDB file) back to the way it was when I noticed this problem in case the MDB isn't it.
On another note, I DID have my GBPVR.MDB file go corrupt last week. I was able to perform a repair with MSACCESS and it appeared to work like a charm.
SUB, this is an odd one, I know. Any ideas at all?

Log files are attached

[sub]

7/25/2006 11:26:36 PM.430 ERROR [1] Error loading station list: System.Data.OleDb.OleDbException: Unrecognized database format 'C:\Program Files\devnz\gbpvr\gbpvr.mdb'.
at System.Data.OleDb.OleDbConnectionInternal..ctor(OleDbConnectionString constr, OleDbConnection connection)
at System.Data.OleDb.OleDbConnectionFactory.CreateConnection(DbConnectionOptions options, Object poolGroupProviderInfo, DbConnectionPool pool, DbConnection owningObject)
at System.Data.ProviderBase.DbConnectionFactory.CreateNonPooledConnection(DbConnection owningConnection, DbConnectionPoolGroup poolGroup)
at System.Data.ProviderBase.DbConnectionFactory.GetConnection(DbConnection owningConnection)
at System.Data.ProviderBase.DbConnectionClosed.OpenConnection(DbConnection outerConnection, DbConnectionFactory connectionFactory)
at System.Data.OleDb.OleDbConnection.Open()
at GBPVR.Backend.Common.xcbcfc48b9705b7a2.xa19cc1d2df8cbd74()
at GBPVR.xf4c930acf61d19ac.x60a8ea63f665aa5e()

Going by the most recent log you have provided, it sounds like a damaged MDB file to me.

I'm also finding that every day, my GBPVR.MDB is growing to 60MB without ever making any schedule changes from my original 14MB GBPVR.MDB.

This is precisely why the option to move to a SQLite database option was included. Very soon this database change will be mandatory.

[Talcum]

OK, I figured it was the MDB that was damaged. Next question though. Any way to repair it? Also I read in the 97.13 survival guide that NOD32 is known to be incompatible with .NET 2.0 Remoting, which is used by GB-PVR.
I just happen to use NOD32 and have been using it for years. Up until recently, I haven't had a problem with NOD32 and GBPVR. Could THIS be why the MDB is getting damaged and is there any fix for that?
I'd like to upgrade to 97.13 so I can move to the SQLite Database option.

Thanks Sub.
PEACE

[sub]

I just happen to use NOD32 and have been using it for years. Up until recently, I haven't had a problem with NOD32 and GBPVR.

NOD32 is incompatible with .NET 2.0's Remoting feature. When GB-PVR moved to .net 2.0 starting from v0.97, this became a problem. You wouldnt have had this problem with earlier releases because they were using .NET 1.1 Remoting.

Could THIS be why the MDB is getting damaged

Yes, possibly. It causes the recording service to terminate without giving it the chance to cleanly finish what it was working on. If it was in the middle of updating the database at the time this occured, then you could end up with a damaged database.

and is there any fix for that?

The options are either uninstall NOD32, or contact the manufacturer and ask them to stop their software from crashing applications that use .NET Remoting. Its a big pain in the arse, and not something I have any control over.

[Talcum]

Well, given the options provided, looks like NOD32 is out the door. My shop is a reseller of NOD32 and we have an inside with the tech support people at NOD32. I contacted them last week about it and they firmly denied any issues with .NET 2.0 Remoting.
That being said, I have to admit the problems didn't start until a recent program update of my NOD32. I'll let them know about it again, but I doubt there will be a quick resolution.
Thanks for the assistance. Looks like it's time to install E-Trust AV. Norton and McAfee are such severe resource hogs that using them is a performance killer for any system.

PEACE

[sub]

NOD32 very definitely does cause problems for applications using .NET remoting.

Some threads on the Microsoft developer forums for the NOD32 tech people to look at:

http://groups.google.com/group/microsoft...c58932230b
http://forums.microsoft.com/MSDN/ShowPos...0&SiteID=1
http://forums.microsoft.com/MSDN/ShowPos...0&SiteID=1
http://forums.microsoft.com/MSDN/ShowPos...0&SiteID=1
http://www.developersdex.com/vb/message....&r=4629297

Google turns up lots of bugs with NOD32's imon.dll.