This Blog is a supplement to my website. Please also visit: www.DavidCocke.com

Sunday, December 25, 2011

VMware Converter - SQL_CANTOPEN Error

While working with the VMware vCenter Converter Standalone Client (in my case version 5.0) I kept getting the following error while trying to convert machines:

A general system error occurred: SQL_CANTOPEN: unable to open database file

After some research I find this error message has been around for awhile and also happens with previous versions of the Converter.  Some say network errors can cause it.

In my case it was the CrashPlan backup client that was causing it.  Forcing CrashPlan to sleep during my conversions corrected my issues.  I also read that for some disabling antivirus software corrected it for them.

So basically anything that could be locking files on the computer your running the VMware Converter software on is where you should look and not the machine being converted.  It was driving me crazy and I thought it was the target VSphere Server that was the issue.


Posted by at

10 comments:

  1. AnonymousSeptember 27, 2012 at 10:48 AM

    Thanks David! Looks like your recommendation to stop crashplan on my server during the conversion is working. REALLY APPRECIATE YOU RIGHT NOW!!

    -Scott Hardy
    www.hhtek.com

    ReplyDelete
  2. Chris StrasserDecember 9, 2013 at 6:49 AM

    I'm also very appreciative of your knowledge and that you took the time to post your results. I was sure that the error was going to come from the source system. Stupid McAfee doesn't even have a normal interface to disable its components.

    ReplyDelete
  3. mikeJanuary 16, 2014 at 9:33 PM

    Thanks for posting this. Over two years later it can still be a problem. Pausing Carbonite backup fixed it!

    ReplyDelete
  4. Bruce GarlockJanuary 19, 2014 at 11:05 AM

    I had the same error using Converter 5.1 on a CentOS 5.4 server, which also had CP running. Even after stopping the CP service, it still failed. Ended up using Converter 4.3, which seems to have solved this. I've had to use 4.3 for other jobs that fail on 5.1.

    ReplyDelete
  5. AnonymousNovember 27, 2014 at 3:04 AM

    This helped me too. In my case it was the McAfee Anti-virus. Turned it off and conversion worked foirst time. Many thanks for your help.

    ReplyDelete
  6. AnonymousMarch 17, 2015 at 11:57 AM

    Another thankful reader. Pausing CrashPlan worked for me.

    ReplyDelete
  7. Doug RossMay 10, 2015 at 8:15 PM

    In my case, pausing Carbonite resolved the problem.

    ReplyDelete
  8. El Cubano.November 8, 2015 at 4:51 PM

    Another thankful reader, David! Thank you, thank you, thank you for posting this. It hadn't occurred to me to disable CrashPlan and Symantic Antivirus. Once I did, everything started migrating correctly. :)

    ReplyDelete
  9. UnknownMarch 10, 2016 at 1:39 PM

    Crashplan did it. Thanks!

    ReplyDelete
  10. AnonymousDecember 7, 2016 at 5:30 AM

    Thanks David!
    Pausing Crashplan helped me as well!

    ReplyDelete

Subscribe to: Post Comments (Atom)