VMNames limit reached. Cannot create

[I3vmware]

I'm creating a dedicated pool I'm getting this message.  I can go pick a new name and I think that will clear up the problem but I'm wondering why this is happening.  This is a small pool - 6 desktops and somehow it's run out of names.   The accounts are not still in active directory but View seems to think they are.  I've had to create and delete the inventory a few times to get the image right but I thought the behavior was to start with the lowest number available via AD?

Here's a screenie of the error/pool settings:

http://i.imgur.com/ET7wuZV.png

[mikko201110141]

Hi,

Main reason for this is that you have defined that pool will have only 2 digit numbering and next number 100 requires 3 digits. If I remember correctly view will use the next number of highest used currently, so it should start from the 01 if you empty the pool by deleting all desktops from the pool. If this is not the case I would check if there is some kind of inconsistency with view's connection server's ADAM database, view composers database and the linked clone VM's actually in the Vcenter's inventory.

http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=201237...

another kb gives instructions for manually deleting linked clone vm, but I would first check if there are extra vm's in the ADAM and if there is I would create a support ticket before starting to remove them to fix the original problem first which has caused this to happened.

http://kb.vmware.com/selfservice/search.do?cmd=displayKC&docType=kc&docTypeID=DT_KB_1_1&externalId=2...

[I3vmware]

Sorry for the delay in getting back, just now getting back into this after the holiday weekend.  I looked through the ADAM database but the 01-99 machines weren't in the list.  I suppose that means that it's something in the database itself.  Problem there is that I'm having a hard time figuring out which server is hosting the composer database.  I'm pretty sure it's not the VCenter.  There are two SQL instances on the vcenter and it does have the view event database but not a composer database (that I can figure).  Neither the composer server (runs on separate machine) nor the connection servers have SQL installed.  The only system ODBC connection listed on the composer points to vCenter.

Is there a way to find what the database server/database name composer is using?

[I3vmware]

As an update I ran the viewdbchk fling (we are using version 5.3) and it found 0 machines with 0 errors.  I'm opening a case at this point too.