B2 Error Version Mismatch - Delete Version Fails

Support
1

After getting a file mismatch in a version (75), I decided to just delete that version and call it a day.

I executed a commandline delete with the only option being:
–version=75

This resulted in a timeout. I read somewhere that SSL/TLS could be responsible for communications issues, so I added a line to limit to Tls12, but that didn’t change anything.

The overall Message is:
“Operation List with file attempt 1 of 5 failed with message: Object reference not set to an instance of an object.”

All five attempts fail.

{"ClassName":"System.NullReferenceException","Message":"Object reference not set to an instance of an object.","Data":null,"InnerException":null,"HelpURL":null,"StackTraceString":"   at Duplicati.Library.Utility.FileBackedList`1.Add(T value)\r\n   at Duplicati.Server.WebServer.RESTMethods.CommandLine.LogWriter.WriteLine(String value)\r\n   at Duplicati.CommandLine.ConsoleOutput.BackendEvent(BackendActionType action, BackendEventType type, String path, Int64 size)\r\n   at Duplicati.Library.Main.MultiMessageSink.BackendEvent(BackendActionType action, BackendEventType type, String path, Int64 size)\r\n   at Duplicati.Library.Main.BasicResults.AddBackendEvent(BackendActionType action, BackendEventType type, String path, Int64 size)\r\n   at Duplicati.Library.Main.BasicResults.AddBackendEvent(BackendActionType action, BackendEventType type, String path, Int64 size)\r\n   at Duplicati.Library.Main.BackendManager.DoList(FileEntryItem item)\r\n   at Duplicati.Library.Main.BackendManager.ThreadRun()","RemoteStackTraceString":null,"RemoteStackIndex":0,"ExceptionMethod":"8\nAdd\nDuplicati.Library.Utility, Version=2.0.4.23, Culture=neutral, PublicKeyToken=null\nDuplicati.Library.Utility.FileBackedList`1\nVoid Add(T)","HResult":-2147467261,"Source":"Duplicati.Library.Utility","WatsonBuckets":null}

This is on a Windows server with B2 as the Backend Cloud Storage Service. I am not smart enough to figure out what this means, but it feels like the B2 is timing out.

Thanks,
|<

2

Does this refer to Using the Command line tools from within the Graphical User Interface? That’s prepopulated with some essential options plus others you manually added. Don’t delete them all.

Testing my B2 backup, though, deleting --passphrase got a complaint. Keeping that next run then complained about the database (because I deleted --dbpath). I’m not sure how yours timed out…
My test was on a current Duplicati, and that probably makes some difference in how things work.

There was a timeout change in January 2019 in web UI’s Commandline timeout, which increased allowable time without output from 5 minutes to 24 hours and fixed other things to avoid this error:

which looks similar to the error you had posted.

Does that refer to “Unexpected difference in fileset”, where the usual repair attempt is version delete?
The major cause of that was fixed in June 2019 in Canary, and was released in January 2.0.5.1 Beta.
You should definitely upgrade if you’re getting those, but it won’t fix an existing problem, if you’re in it.

Delete by Commandline is generally just adding the --version and clearing Commandline arguments. Anything you manually added that you suspect is irrelevant can also get deleted. Then run the delete.
Sometimes the “Unexpected difference in fileset” moves to a different version, but you’d have to try…

Backups fail with error: Object reference not set to an instance of an object was from too few options, however there are probably some other ways to get it. It’s sometimes a follow-up to some other error.

3

This is exactly what I had done.
After reading your reply, I instead removed what I thought to be irrelevant, leaving things that could possibly be relevant (like the encryption, etc.). This time it worked!!!

Thank you very much!!
|<

1 Like