MOSS Forum

Ask Question   UnAnswered
Home » Forum » MOSS       RSS Feeds

V2V conversion breaks MOSS 2007

  Asked By: Katharine    Date: Feb 11    Category: MOSS    Views: 854

I did a V2V conversion of a virtual machine running MOSS 2007, from MS
Virtual Server 2005 to VMware. This process changed NIC drivers in the
VM. The new VM's virtual NIC is configured with the same TCP/IP settings
as the original VM.

MOSS 2007 doesn't appear to work in the new VM. I get a "Server
Application Unavailable" error in the VM.

There are also numerous errors in the application log for the .NET 2.0
framework. I attempted to repair .NET 2.0, but this didn't appear to
make a difference.

Anyone know of special considerations to get MOSS working again after a
V2V conversion?



3 Answers Found

Answer #1    Answered By: Maggie Benson     Answered On: Feb 11

I've done V2V from Virtual Server 2005 R2 to Hyper-V and not had this
problem. V2V as a whole is possible. Not sure why you're having

Answer #2    Answered By: Lane Trujillo     Answered On: Feb 11

I've seen this on occasion - look up the steps for removing hidden
devices in Device Manager - you may have a hidden NIC conflicting with
the active one.

Answer #3    Answered By: Rafael Willis     Answered On: Feb 11

In VMWare you can have multiple networks trunked on the same physical
NIC. Is your NIC defined properly? Also is your VM set to the proper
network? (I know stating the obvious but that one has bitten me before).

Didn't find what you were looking for? Find more on V2V conversion breaks MOSS 2007 Or get search suggestion and latest updates.