Silverfoxs
Contributor
Contributor

Can't start VDM Connection server after installation

Event Type: Error

Event Source: VMware VDM

Event Category: VMware VDM

Event ID: 105

Date: 4/9/2009

Time: 1:35:23 PM

User: NT AUTHORITY\SYSTEM

Computer: PVVIEW

Description:

VMware VDM Connection Server can not start. The ADAM configuration entry for this computer (cn=PVVIEW,ou=server,ou=properties,dc=vdi,dc=vmware,dc=int) can not be read (No Such Object). It is possible that this server computer name has changed since the "VMware VDM Connection Server" software was installed or the entry has been removed from ADAM. From Control Panel "Add or Remove Programs" please remove "VMware VDM Connection Server" and "Adam Instance VMwareVDMDS" and then reinstall "VMware VDM Connection Server".

I never have this vdi.int domain in my system. Does it look normal?

After I finish installation, the service was one. When I start to browse Admin page, the page can't be displayed.

http://localhost/admin

The page cannot be displayed

Service went off. I tried to restart the service, nothing is working.

0 Kudos
11 Replies
Linjo
Leadership
Leadership

It feels like your ADAM Install is confused somehow.

Try to uninstall all ADAM related things, reboot and reinstall.

Best regards,

Linjo

If you find this information useful, please award points for "correct" or "helpful".

Best regards, Linjo Please follow me on twitter: @viewgeek If you find this information useful, please award points for "correct" or "helpful".
0 Kudos
Silverfoxs
Contributor
Contributor

Thanks, but I have reinstall everything multiple times and even rebuild a VM to test it.

No good luck so far.

0 Kudos
lbourque
VMware Employee
VMware Employee

A few questions to understand your environment:

1. What user did you use to install View with?

2. What version of Windows 2003 is it? (english, international, service packs?)

3. Did you enable DEP? (see this MS KB -- http://support.microsoft.com/kb/875352 -- for detailed instructions; this is REQUIRED to be enabled for ADAM to work)

4. Is the local firewall on or have you opened ports? (if you can disable it go to services.msc and stop and disable the service)

5. Is anything else installed on this system (IIS, vCenter, etc.)

0 Kudos
Silverfoxs
Contributor
Contributor

Sorry I didn't introduce the env before.

A few questions to understand your environment:

1. What user did you use to install View with?

I am using Domain admin account to install View.

2. What version of Windows 2003 is it? (english, international, service packs?)

It's a clean VM with W2K3R2SP2STD. Nothing else is installed.

3. Did you enable DEP? (see this MS KB -- -- for detailed instructions; this is REQUIRED to be enabled for ADAM to work)

Just setup as always, uninstall everything, reinstall, nothing work. Same error.

4. Is the local firewall on or have you opened ports? (if you can disable it go to services.msc and stop and disable the service)

No firewall.

5. Is anything else installed on this system (IIS, vCenter, etc.)

No, nothing. It only has SP2, ManageSoft, and Adam, ADAMSP1,VMTOOLS,VMCONNECTION.

Thanks

One more thing, VDAM service won't run with Network service account. I have to use my Domain admin account to run it.

0 Kudos
lbourque
VMware Employee
VMware Employee

Can you get the view logs and see if you can see additionally info around the time of the error? The logs should be in c:\docs and settings\all users\app data\Vmware\vmware view\logs

The logs are in XML and TXT format. The TXT logs should be fine (they are the same but the XML are more "colourful")

0 Kudos
Silverfoxs
Contributor
Contributor

Thanks, Guys. I don't have vmware view folder which hasn't created yet. I only got VDM and I past as following.

13:11:03,486 INFO <148> Program 'wsnm - VDM Framework Node Manager' started, version=3.0.1 build-142034, pid=1180, buildtype=release

13:11:03,502 INFO <148> [] WSNM: main

13:11:03,502 INFO <logloaded> Plugin 'MessageFrameWork - VDM Message FrameWork' loaded, version=3.0.1 build-142034, buildtype=release

13:11:03,502 INFO <Main Thread> WSNM: serviceRun

13:11:03,518 INFO <logloaded> Plugin 'ws_admin - VMware VDM LDAP Admin Utility' loaded, version=3.0.1 build-142034, buildtype=release

13:11:03,518 INFO <logloaded> Plugin 'ws_ldap - VDM Framework LDAP Support Handler' loaded, version=3.0.1 build-142034, buildtype=release

13:11:03,564 FATAL <Service Main Thread> VMware VDM Connection Server can not start. The ADAM configuration entry for this computer (cn=PAKENVVIEW,ou=server,ou=properties,dc=vdi,dc=vmware,dc=int) can not be read (No Such Object). It is possible that this server computer name has changed since the "VMware VDM Connection Server" software was installed or the entry has been removed from ADAM. From Control Panel "Add or Remove Programs" please remove "VMware VDM Connection Server" and "Adam Instance VMwareVDMDS" and then reinstall "VMware VDM Connection Server".

13:11:03,564 INFO <MessageFrameWorkDispatch> Node Manager received shutdown signal

13:11:03,564 INFO <logloaded> Plugin 'ws_java_starter - VDM Framework Java Bridge Controller' loaded, version=3.0.1 build-142034, buildtype=release

13:11:03,596 INFO <logloaded> Plugin 'ws_winauth - VDM Framework Windows Authentication Support' loaded, version=3.0.1 build-142034, buildtype=release

13:11:03,596 INFO <logloaded> Plugin 'ws_mvdi - VMware View Framework Offline Desktop Handler' loaded, version=3.0.1 build-142034, buildtype=release

13:11:03,611 INFO <logloaded> Plugin 'ws_perfmon - VMware VDM Performance Counter Store' loaded, version=3.0.1 build-142034, buildtype=release

13:11:03,627 INFO <Service Main Thread> The VMware VDM System Service is starting

13:11:03,627 INFO <Service Main Thread> The VMware VDM System Service is shutting down

13:11:03,643 WARN <3548> LDAP Notify Service Search failed on ou=authentication,ou=policies,dc=vdi,dc=vmware,dc=int (Authentication) error: No Such Object (0x20). 13:11:03,643 WARN <1544> LDAP Notify Service Search failed on ou=servers,dc=vdi,dc=vmware,dc=int (Servers) error: No Such Object (0x20). 13:11:03,643 WARN <3448> LDAP Notify Service Search failed on ou=server groups,dc=vdi,dc=vmware,dc=int (ServerGroups) error: No Such Object (0x20). 13:11:03,643 WARN <3624> LDAP Notify Service Search failed on ou=virtualcenter,ou=properties,dc=vdi,dc=vmware,dc=int (VirtualCenter) error: No Such Object (0x20). 13:11:03,643 WARN <3452> LDAP Notify Service Search failed on ou=properties,dc=vdi,dc=vmware,dc=int (Properties) error: No Such Object (0x20). 13:11:03,643 WARN <2320> LDAP Notify Service Search failed on ou=applications,dc=vdi,dc=vmware,dc=int (Portal) error: No Such Object (0x20).

13:11:03,955 INFO <InitHandler> MVDI Service DLL loaded.

13:11:04,049 INFO <logloaded> Program 'ws_MessageBusService - VDM Framework Java Bridge' started, version=3.0.1 build-142034, pid=3628, buildtype=release

13:11:04,049 INFO <logloaded> Plugin 'ws_java_native - VDM Framework Java Native Support' loaded, version=3.0.1 build-142034, buildtype=release

13:11:04,049 INFO <logloaded> Plugin 'ws_java_native - VDM Framework Java Native Support' loaded, version=3.0.1 build-142034, buildtype=release

13:11:04,065 INFO <logloaded> Program 'ws_TomcatService - VDM Framework Java Bridge' started, version=3.0.1 build-142034, pid=3492, buildtype=release

13:11:04,065 INFO <logloaded> Plugin 'MessageFrameWork - VDM Message FrameWork' loaded, version=3.0.1 build-142034, buildtype=release

13:11:04,049 INFO <logloaded> Plugin 'ws_java_native - VDM Framework Java Native Support' loaded, version=3.0.1 build-142034, buildtype=release

13:11:04,065 INFO <logloaded> Program 'ws_TunnelService - VDM Framework Java Bridge' started, version=3.0.1 build-142034, pid=2500, buildtype=release

13:11:04,065 INFO <logloaded> Plugin 'MessageFrameWork - VDM Message FrameWork' loaded, version=3.0.1 build-142034, buildtype=release

13:11:04,065 INFO <logloaded> Plugin 'MessageFrameWork - VDM Message FrameWork' loaded, version=3.0.1 build-142034, buildtype=release

13:11:04,065 INFO <Main Thread> JavaBridge could not connect to Node Manager

13:11:04,065 INFO <Main Thread> JavaBridge could not connect to Node Manager

13:11:04,080 INFO <Main Thread> JavaBridge could not connect to Node Manager

13:11:04,221 INFO <Service Main Thread> MVDI Exit Handler.

13:11:04,221 INFO <Service Main Thread> MVDI server un-installed.

13:11:04,236 INFO <Main Thread> The VMware VDM System Service has stopped

There are no such objects in my company AD, that's for sure. Not quite sure whether VDM supposes to create those OUs and whether I can view it just by ADSIEDIT.

Ta

0 Kudos
lbourque
VMware Employee
VMware Employee

Out of curiosity, the computer you're installing View on: when it was added to the domain was the domain signified as "domain" or "domain.com"?

0 Kudos
Silverfoxs
Contributor
Contributor

hi, Ibourque:

The vm was deployed by template. I renamed the machine and joined it into our production AD since ADAM not supposes to modify any schema.

The domain is more like subdomain.domain.com.au

It's member server of course.

0 Kudos
lbourque
VMware Employee
VMware Employee

Did the customization script attach the VM to the domain? And was the original template already attached to the domain?

0 Kudos
tchamberlain
Contributor
Contributor

If your getting:

ICE start com.vmware.vdi.ice.server.Ice.startServer(SourceFile:663)

java.net.BindException: Address already in use: bind

Caused by: java.lang.Exception: ICE Start: Address already in use: bind

Check to see if the IIS World Wide Web Publishing service is started, stop it, then restart the VMware View Connection Server service and see if that fixes it.

0 Kudos
rott
Enthusiast
Enthusiast

Thanks a lot! That helped for me.

Although a little strange - I allready tested port 443 on the server - it was not open! But the http/ssl service was indeed running...

Michael

0 Kudos