Skip navigation
VMware
Up to Discussions in VMware View™ (with View Manager)

This Question is Not Answered

1 "correct" answer available (10 pts) 2 "helpful" answers available (6 pts)
277 Views 5 Replies Last post: Apr 22, 2009 6:24 PM by kimu2 RSS
kimu2 Lurker
kimu2
2 posts since
Apr 9, 2009
Currently Being Moderated

Apr 9, 2009 9:50 PM

Missing VM was not in the original query: vm-181

 

dear all,

 

 

my vCenter is a vm. ESX version is 3.5 up3 build-123630 and Virtual Center is 2.5.0 build-119801, VMware View Administrator  3.0.1 build-142034.

 

 

VMware View Administrator ⇒ Events ⇒ Message ↓

 

 

「Missing VM was not in the original query: vm-181 」

 

 

＜Event Detqils＞

 

 

Message:

Missing VM was not in the original query: vm-181

Type:

Warn

Time:

4/10/09 12:50:34 PM

Module:

VirtualCenterDriver

Thread:

VirtualCenterDriver-c443c02c-ee23-4243-a852-f326a5588734

Additional details:

 

 

 

 

 

anybody can help? thanks a lot!

 

 

 

 

 

 

 

 

lbourque Master VMware Employees
lbourque
879 posts since
Oct 26, 2005
Currently Being Moderated
1. Apr 10, 2009 4:15 AM in response to: kimu2
Re: Missing VM was not in the original query: vm-181

 

It sounds like you might have a corrupted ADAM database. Check out this thread: http://communities.vmware.com//thread/202435?tstart=15

 

 

Can you build a replica and see if it resolves the issue?

 

 

Want make a difference in the future of VMware Products? Feature request your ideas ( http://www.vmware.com/support/policies/feature.html )!
jkatz71 Enthusiast
jkatz71
48 posts since
Oct 21, 2008
Currently Being Moderated
2. Apr 19, 2009 8:48 PM in response to: kimu2
Re: Missing VM was not in the original query: vm-181

 

I had a similar problem and was unable to deploy new VMs while this error was being generated at the rate of 4-5 a second.  After about a week with VMware support, my engineer still had no clue and I eventually re-built the View server and re-created each VM manually.

 

 

Their suggestion was to export the ADAM database, re-build the server, and then import the DB.  Once I had done that, the symptoms returned.  It turns out the DB was corrupted and they didn't seem to know how to fix it.  Luckily, my installation only had about 150 individual desktops.

 

 

I now backup my DB nightly and archive it to tape.  I can't imagine what would happen now if this happened as we've gone the linked clone route.  (which is awesome!)

 

 

 

 

 

-jonathan

 

 

-jonathan
AnneJanElsinga Novice
AnneJanElsinga
10 posts since
Mar 9, 2006
Currently Being Moderated
3. Apr 22, 2009 12:49 AM in response to: kimu2
Re: Missing VM was not in the original query: vm-181

 

I had the same problem yesterday.  I solved it by removing ADAM en reinstalling View because I had little time to do troubleshooting (we're still building the environment and have a very short time to get it operating). Since I already reinstalled I unfortunately have nothing to send to VMware support.

 

 

 

 

 

But what I really want to know is: What is causing this? Is this

something I can prevent? You should always backup, but not knowing what's causing this gives me a a strange feeling.

 

 

 

 

 

-------------------- http://www.vmguru.nl
jkatz71 Enthusiast
jkatz71
48 posts since
Oct 21, 2008
Currently Being Moderated
4. Apr 22, 2009 11:07 AM in response to: AnneJanElsinga
Re: Missing VM was not in the original query: vm-181

My problems started when an automated pool tried to deploy a new VM to a disconnected host.  (regular VM, not a linked clone)

 

 

-jonathan

-jonathan
kimu2 Lurker
kimu2
2 posts since
Apr 9, 2009
Currently Being Moderated
5. Apr 22, 2009 6:24 PM in response to: lbourque
Re: Missing VM was not in the original query: vm-181

 

Thank you for the top it as for the answer.

 

 

The replica can be made.

 

 

However, I want to know what this errer　message is output.

 

 

Bookmarked By (0)

Share This Page

Communities