Corrupt or disc error: 8000ffff

jimbo123

Young grasshopper
Joined
Mar 15, 2019
Messages
65
Reaction score
11
Location
Australia
This had shown up and after reading here,.. I had wiped the DB folder and all seemed good - although I didn't see anything logged when it was supposed to do any work at 2am.

Thought all was good, but a couple of nights later its now come back again overnight.

Had verified that the folder along with a few others were excluded from AV.

Disc is a new WD purple 4TB,.. all else seems fine.

Thoughts ?

EDIT: Reading this thread now. Forgot to mention its BI5,.. v5.0.2.2.
 
Last edited:

jimbo123

Young grasshopper
Joined
Mar 15, 2019
Messages
65
Reaction score
11
Location
Australia
Updated last night,.. no error logged at 2am this morning.

Is there a way to check that it actually did anything as part of the scheduled 2am job ?
 

cferd5

Getting the hang of it
Joined
Aug 6, 2017
Messages
66
Reaction score
35
Thank you Walrus, I had this same issue and wasn't aware of the fix. I had unchecked the option in settings. Just ran Compact/Repair manually and no error reported.
 

archedraft

Getting the hang of it
Joined
Sep 11, 2018
Messages
138
Reaction score
91
Location
USA
Updated last night,.. no error logged at 2am this morning.

Is there a way to check that it actually did anything as part of the scheduled 2am job ?
Not that I am aware of but if you reassures you, I reported this issue BI support last Wednesday and got the response from Ken? (They didn’t sign the email) that version 5.0.2.4 fixes this issue.
 

jimbo123

Young grasshopper
Joined
Mar 15, 2019
Messages
65
Reaction score
11
Location
Australia
Thanks,... What's the mechanism to trigger this compact/repair manually ? Just change the scheduled time ? Or is there a more scientific approach ?
 

gotitmadecij

Young grasshopper
Joined
Feb 25, 2016
Messages
35
Reaction score
11
I was getting the same error, I deleted the db file in the Blue Iris folder , nothing worked . I contacted Ken who stated he had found an issue and that the latest update would address this issue. I updated and it fixed it for me...
 
Top