>I have a VM that has been working. In fact, we successfully brought it into
>the domain today.
>
>I then proceeded to install some software, and had several occasions to shut
>it down, restart it, and turn it off.
>
>Eventually (and I don't know if this is related), I got event id 1130:
>
>The virtual machine "TFS" cannot connect virtual network adapter 1 because
>another virtual machine with the MAC address 00:03:FF:A9:80:46 is already
>running. This virtual network adapter will be left disconnected.
>------
>After turning it off again, Virtual Server will no longer start for long.
>Every time I start the service, I get event id 1066:
>
>Virtual Server encountered an unexpected error, 0x00000003.
>
>I've seen the other threads on this subject, but they don't seem to be
>relevant. There's nothing in the Application, Security or System logs that
>might explain this, and the problem has persisted across a reboot.
>
>Any suggestions would be appreciated, as my manager will almost certainly
>tell me to install "you know what" rather than play around with Virtual
>Server 2005 R2 SP1.

> On Fri, 25 Jan 2008 19:30:00 -0800, John Saunders [MVP] <john.saunders
> at trizetto.com> wrote:
>
>>I have a VM that has been working. In fact, we successfully brought it
>>into
>>the domain today.
>>
>>I then proceeded to install some software, and had several occasions to
>>shut
>>it down, restart it, and turn it off.
>>
>>Eventually (and I don't know if this is related), I got event id 1130:
>>
>>The virtual machine "TFS" cannot connect virtual network adapter 1 because
>>another virtual machine with the MAC address 00:03:FF:A9:80:46 is already
>>running. This virtual network adapter will be left disconnected.
>
>
> Try editing your .vmc and removing the above address and see if that
> makes a difference. I think it is the root cause of your problems. I
> had a similar problem with a VM I moved and it gave that message and
> VS began acting funky. After turning it off, VS and the other VMs
> went back to normal. I haven't done additional troubleshooting
> though.
>>------
>>After turning it off again, Virtual Server will no longer start for long.
>>Every time I start the service, I get event id 1066:
>>
>>Virtual Server encountered an unexpected error, 0x00000003.
>>
>>I've seen the other threads on this subject, but they don't seem to be
>>relevant. There's nothing in the Application, Security or System logs that
>>might explain this, and the problem has persisted across a reboot.
>>
>>Any suggestions would be appreciated, as my manager will almost certainly
>>tell me to install "you know what" rather than play around with Virtual
>>Server 2005 R2 SP1.
>
> I don't understand this logic. Other products have just as many
> issues, if not more in some cases, so what then? Keep switching
> products until the perfect "bug-free, issue-free" product is found?

> "Steve Jain" <(email address - cut out)> wrote in message
> news:(email address - cut out)...
>> On Fri, 25 Jan 2008 19:30:00 -0800, John Saunders [MVP] <john.saunders
>> at trizetto.com> wrote:
>>
>>>I have a VM that has been working. In fact, we successfully brought it
>>>into
>>>the domain today.
>>>
>>>I then proceeded to install some software, and had several occasions to
>>>shut
>>>it down, restart it, and turn it off.
>>>
>>>Eventually (and I don't know if this is related), I got event id 1130:
>>>
>>>The virtual machine "TFS" cannot connect virtual network adapter 1
>>>because
>>>another virtual machine with the MAC address 00:03:FF:A9:80:46 is already
>>>running. This virtual network adapter will be left disconnected.
>>
>>
>> Try editing your .vmc and removing the above address and see if that
>> makes a difference. I think it is the root cause of your problems. I
>> had a similar problem with a VM I moved and it gave that message and
>> VS began acting funky. After turning it off, VS and the other VMs
>> went back to normal. I haven't done additional troubleshooting
>> though.
>
> Thanks, Steve, I tried this but it didn't work. I went further and renamed
> all of the .vmc files. It still didn't work.
>
> I think I'll try a reinstall of Virtual Server.

> I have a VM that has been working. In fact, we successfully brought it into
> the domain today.
>
> I then proceeded to install some software, and had several occasions to shut
> it down, restart it, and turn it off.
>
> Eventually (and I don't know if this is related), I got event id 1130:
>
> The virtual machine "TFS" cannot connect virtual network adapter 1 because
> another virtual machine with the MAC address 00:03:FF:A9:80:46 is already
> running. This virtual network adapter will be left disconnected.
> ------
> After turning it off again, Virtual Server will no longer start for long.
> Every time I start the service, I get event id 1066:
>
> Virtual Server encountered an unexpected error, 0x00000003.
>
> I've seen the other threads on this subject, but they don't seem to be
> relevant. There's nothing in the Application, Security or System logs that
> might explain this, and the problem has persisted across a reboot.
>
> Any suggestions would be appreciated, as my manager will almost certainly
> tell me to install "you know what" rather than play around with Virtual
> Server 2005 R2 SP1.
> --
> John Saunders | MVP - Windows Server System - Connected System Developer
> https://mvp.support.microsoft.com/profile/John.Saunders
>