Provisioning Error (missing)

[mwynne]

Hi,

I have seen this issue for some time now, but it just got to a point where I need a solution. I have 30 machines in my view environment that have gone missing. I get the error that is the title of the thread (Provisioniong Error (missing)) in View Admin, but the machines do not exist in vcenter. I have looked into the one KB article on this (1010841) and it suggests that there may be a vmware-ufab process ruinning that needs to be stopped. That process is not running, it also refers to an Composer log that I was not able to find.

Can anyone tell me: 1) How to get the machines deleted so that they can be reprovisioned and/or where the Composer log is located.

Thank You

Mark

[mittim12]

Sounds like View Composer still thinks that those desktops are there.  Did you see this KB article  http://kb.vmware.com/kb/1008658?

[mwynne]

Ya, you know I looked at that one a while back when I just had a couple of machines with this issue. The instructions don't make sense at a couple points there....particularly when creating a connection and creating a query.....there's not really even an option to create a query in the mmc window that the ADAM ADSI Edit uses.

....I did just try the last piece of the article and as I suspected would be the case, it doesn't find the "missing" machines....see this is where my issue is. The machines still exist in view admin, but they dion't exist in the composer database, that's why they show up as missing. What I need is a way to remove them from view admin....

Thanks for trying though....any other thoughts/suggestions?

Mark

[mittim12]

The ADAM database is where VIew Admin is pulling that data from.  You will need to get that cleaned up too.  

[mwynne]

Ya, that's what I thought too, but these machines are NOT FOUND in the database.....unless you can point me to a table that this knowledge base article doesn't mention.

Mark

[mittim12 · Accepted solution]

I thought you said in your previous post you couldn't figure out how to connect using ADAM and just went to the last step which is the Composer database.   Sorry if I misread that but if not I have included a print screen of what the ADAM connection settings should look like to connect.

Open up MMC, choose adsi edit, right click and choose connect  to.  This will allow you to setup your connection to connect to the View ADAM database.

[mwynne]

You are right, it was the composer database I was talking about, and your connection info SS was the key...thanks for sticking with me on this.....now if I can figure out why it is happening in the first place......

Thank You,

Mark

[mittim12]

Sometimes it just happens.  Whether its a timing issue or someone just deletes it from vCenter and not the View Admin.   Don't hesitate to ask if you run into any problems or just have general questions.   

[mwynne]

Ok, so one more. This solution worked for all of my missing machines, but 2 came back. These are the same 2 that originally were showing the missing error. So when I delete them from the ADAM database they are removed from view admin, but then they just show up again with the same error and are still "missing". Any iideas on that? Where else could it be finding references to those machines?

Mark

[mittim12]

Do you have auto provisioning enabled?   perhaps it's trying to recreate them as soon as you clean up everything and it's failing again for whatever reason.   

[mwynne]

Yes, the pools are set to auto provision.....and most of them reprovisioned correctly after deleting them from the db....just 2 that continually come back with this same error. Not sure why.

[mittim12]

You might need to gather log information from the connection server and composer to figure this out.  You can find information on log locations here, http://kb.vmware.com/kb/1027744.  It could also be something as simple as those particular VMs already existing in the domain and it's not finishing properly.