VMware Cloud Community
m4biz
Hot Shot
Hot Shot

Side by side error 32 on Windows Server 2003 domain controller VM

Hi.

I need to virtualize a working Windows Server 2003 DC (32 bit) on a, new, vSphere Hypervisor machine (ESXi 5) based on a Proliant ML150 G6 server with Intel Xeon 5504 @ 2,0 GHz (64 bit)

To do this, I've choosed to install a fresh copy of Windows Server 2003 s.o and then perform a Primary Restore of the DC from the most recent full backup.

All seems works fine but after the last reboot I've seen in the event viewer many errors like this:

"Evet ID 32 - Side by side -  Impossible to find the dependent assembly Microsoft VC80.CRT. The last error was The assembly to wich ... is not installed in the computer (see attached screen shot)"

I think the issue is related to the virtualizzation process because, in the past, during Disaster Recovery simulation on physical (not virtual) hardware there was'nt any issue like this.

Any idea?

Thanks in advance

Ing. Cosimo Mercuro http://cosimomercuro.wordpress.com/
Tags (2)
Reply
0 Kudos
3 Replies
continuum
Immortal
Immortal

Microsoft VC80 * is part of the vcredist runtimes
make sure you have
Microsoft Visual C++ 2008 and 2010 installed.

If you already have them - install them again so that they fix errors


________________________________________________
Do you need support with a VMFS recovery problem ? - send a message via skype "sanbarrow"
I do not support Workstation 16 at this time ...

Reply
0 Kudos
golddiggie
Champion
Champion

Which B&R software are you using? Typically, you need to execute a different (even if only slightly) process when restoring a backup of a physical server as/to a virtual server.

Of course, it's best practice to NOT try to virtualize (P2V) a physical AD DC. Even the method you're trying isn't really recommended (AFAIK)... Best method has always been to create a new AD DC, put it into the forest, once it's fully integrated, make it the primary DC and demote/retire the physical AD DC.

Reply
0 Kudos