[Okta Webinar] Learn how to a build a cloud-first strategyRegister Now

x
?
Solved

VMWare converter SQL 2000 SP3 vssui.dll issues

Posted on 2009-04-08
4
Medium Priority
?
631 Views
Last Modified: 2012-05-06
I try to run the converter against a production sql box. get the following. Four VSS errors immediately. i tracked it down to vssui.dll. reregister that dll, converter starts working... Problem is it seems to screw up SQL access. Cant open event viewer, cant do a bunch of things... any ideas? Direction?

Volume Shadow Copy Service error: A critical component required by the Volume Shadow Copy service is not registered.  This might happened if an error occurred during Windows setup or during installation of a Shadow Copy provider.  The error returned from CoCreateInstance on class with CLSID {f5078f32-c551-11d3-89b9-0000f81fe221} and Name MSXML30 is [0x80040154].
0
Comment
Question by:jcorso1212
  • 2
4 Comments
 
LVL 42

Expert Comment

by:Paul Solovyovsky
ID: 24099246
try shutting down sql services and trying again, there may be contention on VSS which is used by vConverter.  If you're running windows 2000 make sure you're up to date on the service pack (rollup included)
0
 

Author Comment

by:jcorso1212
ID: 24099753
It is server 2003. Sql sp3 not 4....

when I reregister that dll, a service for an app fails requiring you to reregister msxml, msxml2, and msxml3 dlls
0
 
LVL 8

Expert Comment

by:markzz
ID: 24099818
I expect Paul has hit the nail on the head re: the SQL migration issue.
As far as the VSS issue goes, that's an entirely separate one to address. It may well be effecting your ability to perform a hot migration but VSS issues seem to be very common place post SP2. I'm chasing VSS issues myself currently.
Regarding your migration.
With most environments where you have active and persistemt disk access it's best practice to stop the applications which generate the disk activity or even better if you are licensed for it  perform a cold migration via the VMWare boot CD, of course you could use a Barts boot CD and ghost the server, this works fine but takes many hours.
Personally I always cold migrate servers like SQL, DB2, AD DC's basicly anything that runs a critical database. When cold migrating you can be assured of data integrity, when performing hot migrations many things can go wrong.
0
 
LVL 42

Accepted Solution

by:
Paul Solovyovsky earned 2000 total points
ID: 24101520
If it doesn't work download a trial copy of Acronis TrueImage or Symantec Backup Exec System Recovery.  Image the servers to a network location then use vConverter to convert the image to a virtual machine. the converter know both file types natively.
0

Featured Post

NEW Veeam Backup for Microsoft Office 365 1.5

With Office 365, it’s your data and your responsibility to protect it. NEW Veeam Backup for Microsoft Office 365 eliminates the risk of losing access to your Office 365 data.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

A Stored Procedure in Microsoft SQL Server is a powerful feature that it can be used to execute the Data Manipulation Language (DML) or Data Definition Language (DDL). Depending on business requirements, a single Stored Procedure can return differe…
Microsoft Access has a limit of 255 columns in a single table; SQL Server allows tables with over 255 columns, but reading that data is not necessarily simple.  The final solution for this task involved creating a custom text parser and then reading…
Viewers will learn how to use the SELECT statement in SQL and will be exposed to the many uses the SELECT statement has.
This video shows you how easy it is to boot from ISO images for virtual machines with the ISO images stored on a local datastore on the ESXi host.

872 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question