VMware Horizon Community
malabelle
Enthusiast
Enthusiast
Jump to solution

Upgrade View 5.1 to 5.1.3 or 5.3 failed

Hi,

I have a functional View 5.1.0 with about 1500 desktops.

I tried to upgrade to 5.3 and it failed. I reversed (snapshot) to 5.1.0 and tried to 5.1.3 and failed...

The /admin page is not working, 443 ports not opened.

The services are started...

I have vCops for view installed 5.7

any ideas?

Here are some logs.

5.1.3

014-03-25T19:51:10.968-04:00 INFO  (0670-069C) <logloaded> [MessageFrameWork] Program 'ws_ConnectionServer - VMware View Java Component Service' started, version=5.1.3 build-1007228, pid=0x670, buildtype=release, usethread=1, closeafterwrite=0

2014-03-25T19:51:10.968-04:00 INFO  (0670-069C) <logloaded> [MessageFrameWork] Plugin 'ws_java_bridgeDLL - VMware View Framework Java Bridge' loaded, version=5.1.3 build-1007228, buildtype=release

2014-03-25T19:51:10.984-04:00 INFO  (0670-0698) <logloaded> [MessageFrameWork] Plugin 'ws_java_native - VMware View Framework Java Native Support' loaded, version=5.1.3 build-1007228, buildtype=release

2014-03-25T19:51:13.640-04:00 INFO  (069C-02CC) <Service Main Thread> [MessageFrameWork] Program 'wsnm - VMware View Framework Node Manager' started, version=5.1.3 build-1007228, pid=0x69C, buildtype=release, usethread=1, closeafterwrite=0

2014-03-25T19:51:13.734-04:00 INFO  (069C-0870) <logloaded> [MessageFrameWork] Plugin 'ws_ldap - VMware View Framework LDAP Support Handler' loaded, version=5.1.3 build-1007228, buildtype=release

2014-03-25T19:38:23.681-04:00 INFO  (069C-02CC) <Service Main Thread> [ws_ldap] LDAP synchronization command on Brokerserver01.domain.local completed successfully

2014-03-25T19:38:23.759-04:00 WARN  (069C-02CC) <Service Main Thread> [ws_ldap] LDAP synchronization command on Brokerserver02.domain.local failed - exit status 1398 (There is a time and/or date difference between the client and server.)

2014-03-25T19:38:23.759-04:00 INFO  (069C-02CC) <Service Main Thread> [ws_ldap] If Connection Server Brokerserver02.domain.local is no longer in use, you can remove references to it by running the command "vdmadmin -S -s desktopSVR55 -r"

2014-03-25T19:38:24.087-04:00 INFO  (069C-02CC) <Service Main Thread> [ws_ldap] LDAP synchronization command on Brokerserver01.domain.local completed successfully

2014-03-25T19:38:24.197-04:00 WARN  (069C-02CC) <Service Main Thread> [ws_ldap] LDAP synchronization command on Brokerserver02.domain.local failed - exit status 1398 (There is a time and/or date difference between the client and server.)

2014-03-25T19:38:24.197-04:00 INFO  (069C-02CC) <Service Main Thread> [ws_ldap] If Connection Server Brokerserver02.domain.local is no longer in use, you can remove references to it by running the command "vdmadmin -S -s desktopSVR55 -r"

2014-03-25T19:38:26.931-04:00 INFO  (069C-02CC) <Service Main Thread> [ws_ldap] LDAP Notify Service - created all notification threads

2014-03-25T19:38:27.041-04:00 INFO  (069C-0D4C) <logloaded> [MessageFrameWork] Plugin 'ws_admin - VMware View LDAP Admin Utility' loaded, version=5.1.3 build-1007228, buildtype=release

2014-03-25T19:38:27.072-04:00 INFO  (069C-0D68) <logloaded> [MessageFrameWork] Plugin 'ws_filesystem - VMware View filesystem plugin component' loaded, version=5.1.3 build-1007228, buildtype=release

2014-03-25T19:38:27.103-04:00 INFO  (069C-0D6C) <logloaded> [MessageFrameWork] Plugin 'vmware_jpake_plugin - VMware View JPAKE Plugin' loaded, version=5.1.3 build-1007228, buildtype=release

2014-03-25T19:38:27.291-04:00 INFO  (069C-0BEC) <3052> [ws_ldap] 0 collision entry references resolved.

2014-03-25T19:38:27.291-04:00 INFO  (069C-0BEC) <3052> [ws_ldap] 0 deleted entry references removed.

2014-03-25T19:38:27.291-04:00 INFO  (069C-0BEC) <3052> [ws_ldap] 0 collision entries removed.

2014-03-25T19:38:28.009-04:00 INFO  (069C-0DF4) <logloaded> [MessageFrameWork] Plugin 'ws_mvdi - VMware View Framework Offline Desktop Handler' loaded, version=5.1.3 build-1007228, buildtype=release

2014-03-25T19:38:28.009-04:00 INFO  (069C-0DFC) <logloaded> [MessageFrameWork] Plugin 'ws_perfmon - VMware View Performance Monitor and Counter Store' loaded, version=5.1.3 build-1007228, buildtype=release

2014-03-25T19:38:28.166-04:00 INFO  (069C-0E2C) <logloaded> [MessageFrameWork] Plugin 'ws_thinappmgmt - VMware View Framework Application Management Support' loaded, version=5.1.3 build-1007228, buildtype=release

2014-03-25T19:38:28.244-04:00 INFO  (069C-02CC) <Service Main Thread> [wsnm] The VMware View System Service is starting

2014-03-25T19:38:28.275-04:00 INFO  (0E3C-0E48) <logloaded> [MessageFrameWork] Program 'ws_MessageBusService - VMware View Java Component Service' started, version=5.1.3 build-1007228, pid=0xE3C, buildtype=release, usethread=1, closeafterwrite=0

2014-03-25T19:38:28.275-04:00 INFO  (0E3C-0E48) <logloaded> [MessageFrameWork] Plugin 'ws_java_bridgeDLL - VMware View Framework Java Bridge' loaded, version=5.1.3 build-1007228, buildtype=release

2014-03-25T19:38:28.291-04:00 INFO  (069C-0E38) <logloaded> [MessageFrameWork] Plugin 'ws_winauth - VMware View Framework Windows Authentication Support' loaded, version=5.1.3 build-1007228, buildtype=release

2014-03-25T19:38:28.291-04:00 INFO  (0E3C-0E84) <Service Main Thread> [ws_MessageBusService] The service 'MessageBusService' is started

2014-03-25T19:38:28.306-04:00 INFO  (0E3C-0E44) <logloaded> [MessageFrameWork] Plugin 'ws_java_native - VMware View Framework Java Native Support' loaded, version=5.1.3 build-1007228, buildtype=release

2014-03-25T19:38:28.384-04:00 INFO  (0E3C-0E98) <logloaded> [MessageFrameWork] Plugin 'ws_javaview - VMware View Framework Java Diagnostics' loaded, version=5.1.3 build-1007228, buildtype=release

2014-03-25T19:38:28.822-04:00 ERROR (0E3C-0E88) <javabridge> [ws_java_bridgeDLL] Java Bridge Managed failed on serviceClass = jniEnv->FindClass(serviceClassName._mstr())

2014-03-25T19:38:28.837-04:00 ERROR (0E3C-0E88) <javabridge> [ws_java_bridgeDLL] Exception in JavaService::Init

2014-03-25T19:38:28.837-04:00 WARN  (0E3C-0E88) <javabridge> [ws_java_bridgeDLL] Exception

2014-03-25T19:38:28.837-04:00 WARN  (0E3C-0E88) <javabridge> [ws_java_bridgeDLL] in thread "Thread-0"

2014-03-25T19:38:28.837-04:00 INFO  (0E3C-0E88) <javabridge> [ws_java_bridgeDLL] JavaBridge cannot initiate the java service MessageBusService

2014-03-25T19:38:28.837-04:00 INFO  (0E3C-0E88) <javabridge> [ws_java_bridgeDLL] The View Message Bus subsystem has stopped

2014-03-25T19:38:29.603-04:00 INFO  (069C-0DF8) <InitHandler> [ws_mvdi] MVDI Service DLL loaded.

2014-03-25T19:41:24.884-04:00 INFO  (0648-0A88) <2696> [v4v_broker_agent_svc] Program 'v4v_broker_agent_svc - Broker Agent service' started, version=1.5.1.1526, pid=0x648, buildtype=release, usethread=0, closeafterwrite=0

2014-03-25T19:41:25.853-04:00 INFO  (0648-0A88) <2696> [v4v_broker_agent_svc] Program 'v4v_broker_agent_svc - Broker Agent service' started, version=1.5.1.1526, pid=0x648, buildtype=release, usethread=0, closeafterwrite=0

2014-03-25T19:41:28.275-04:00 INFO  (0648-094C) <Main CAPI Thread> [MessageFrameWork] Program 'v4v_broker_agent_svc - Broker Agent service' started, version=1.5.1.1526, pid=0x648, buildtype=release, usethread=0, closeafterwrite=0

5.3

2014-03-25T20:06:35.480-04:00 INFO  (0830-0E28) <logloaded> [MessageFrameWork] Plugin 'vmware_jpake_plugin - VMware View JPAKE Plugin' loaded, version=5.3.0 build-1427931, buildtype=release

2014-03-25T20:06:35.511-04:00 INFO  (0830-0E00) <logloaded> [MessageFrameWork] Plugin 'ws_perfmon - VMware View Performance Monitor and Counter Store' loaded, version=5.3.0 build-1427931, buildtype=release

2014-03-25T20:06:35.558-04:00 INFO  (0830-0E04) <logloaded> [MessageFrameWork] Plugin 'ws_mvdi - VMware View Framework Offline Desktop Handler' loaded, version=5.3.0 build-1427931, buildtype=release

2014-03-25T20:06:35.558-04:00 INFO  (0830-0E80) <logloaded> [MessageFrameWork] Plugin 'ws_thinappmgmt - VMware View Framework Application Management Support' loaded, version=5.3.0 build-1427931, buildtype=release

2014-03-25T20:06:35.558-04:00 INFO  (0830-0E84) <logloaded> [MessageFrameWork] Plugin 'ws_winauth - VMware View Framework Windows Authentication Support' loaded, version=5.3.0 build-1427931, buildtype=release

2014-03-25T20:06:35.558-04:00 INFO  (0830-0868) <Service Main Thread> [wsnm] The VMware View System Service is starting

2014-03-25T20:06:35.574-04:00 INFO  (0EDC-0E88) <logloaded> [MessageFrameWork] Program 'ws_MessageBusService - VMware View Java Component Service' started, version=5.3.0 build-1427931, pid=0xEDC, buildtype=release, usethread=1, closeafterwrite=0

2014-03-25T20:06:35.574-04:00 INFO  (0EDC-0E88) <logloaded> [MessageFrameWork] Plugin 'ws_java_bridgeDLL - VMware View Framework Java Bridge' loaded, version=5.3.0 build-1427931, buildtype=release

2014-03-25T20:06:35.589-04:00 INFO  (0EDC-0FE4) <Service Main Thread> [ws_MessageBusService] The service 'MessageBusService' is started

2014-03-25T20:06:35.605-04:00 INFO  (0EDC-0ECC) <logloaded> [MessageFrameWork] Plugin 'ws_java_native - VMware View Framework Java Native Support' loaded, version=5.3.0 build-1427931, buildtype=release

2014-03-25T20:06:35.636-04:00 INFO  (0EDC-0FDC) <logloaded> [MessageFrameWork] Plugin 'ws_javaview - VMware View Framework Java Diagnostics' loaded, version=5.3.0 build-1427931, buildtype=release

2014-03-25T20:06:36.074-04:00 ERROR (0EDC-0C38) <javabridge> [ws_java_bridgeDLL] Java Bridge Managed failed on serviceClass = jniEnv->FindClass(serviceClassName._mstr())

2014-03-25T20:06:36.074-04:00 ERROR (0EDC-0C38) <javabridge> [ws_java_bridgeDLL] Exception in JavaService::Init

2014-03-25T20:06:36.074-04:00 WARN  (0EDC-0C38) <javabridge> [ws_java_bridgeDLL] Exception

2014-03-25T20:06:36.074-04:00 WARN  (0EDC-0C38) <javabridge> [ws_java_bridgeDLL] in thread "Thread-0"

2014-03-25T20:06:36.089-04:00 INFO  (0EDC-0C38) <javabridge> [ws_java_bridgeDLL] JavaBridge cannot initiate the java service MessageBusService

2014-03-25T20:06:36.089-04:00 INFO  (0EDC-0C38) <javabridge> [ws_java_bridgeDLL] The View Message Bus subsystem has stopped

vExpert '16, VCAP-DCA, VCAP-DCD
Reply
0 Kudos
1 Solution

Accepted Solutions
mpryor
Commander
Commander
Jump to solution

As mentioned, this is a known issue with the vcops for view component - while it's running, it's actively using files that are part of the connection server install. The 5.1 uninstall, unable to remove those files, schedules them for delete on reboot. It's a known issue that we created a KB article for, you need to stop the vcops service before upgrade as a workaround, and we plan to fix it by stopping the vcops service during the upgrade automatically in future releases.

http://kb.vmware.com/kb/2075114

[Edit: the KB article was not originally marked as public, link has been updated]

View solution in original post

Reply
0 Kudos
16 Replies
markbenson
VMware Employee
VMware Employee
Jump to solution

We've seen something similar before. It is interesting that you mentioned vcops as this is probably related.

This is not certain, but some of the files needed for upgrade are possibly being held open by vcops.

Can you:

1. Stop the vcops service.

2. Uninstall View Connection Server (leave the AD LDS instance in place)

3. Reinstall View Connection Server 5.3

Let us know if that resolves it.

Mark

Reply
0 Kudos
malabelle
Enthusiast
Enthusiast
Jump to solution

I tried uninstalling the vcops before upgrading.

How do you Uninstall the Connection Server and leave the AD LDS instance?

vExpert '16, VCAP-DCA, VCAP-DCD
Reply
0 Kudos
markbenson
VMware Employee
VMware Employee
Jump to solution

malabelle wrote:

How do you Uninstall the Connection Server and leave the AD LDS instance?

Just don't uninstall "AD LDS Instance VMwareVDMDS". Leave that in place.

Mark

Reply
0 Kudos
Linjo
Leadership
Leadership
Jump to solution

I don't think that the uninstall of the connection broker is needed, so maybe try to take one step at a time and see if it installs.

// Linjo

Best regards, Linjo Please follow me on twitter: @viewgeek If you find this information useful, please award points for "correct" or "helpful".
Reply
0 Kudos
malabelle
Enthusiast
Enthusiast
Jump to solution

Ok, so in my LAB, by stopping the service it works...

I'll try in production this weekend.

vExpert '16, VCAP-DCA, VCAP-DCD
Reply
0 Kudos
markbenson
VMware Employee
VMware Employee
Jump to solution

Yes, we think it is related to the vcops service. It's probably a bug but let us know if stopping the service during the upgrade is an effective workaround for you. We'll do some specific testing of this too.

Thanks again for raising this. Your reference to vcops was important so I'm glad you mentioned it.

Mark

mpryor
Commander
Commander
Jump to solution

As mentioned, this is a known issue with the vcops for view component - while it's running, it's actively using files that are part of the connection server install. The 5.1 uninstall, unable to remove those files, schedules them for delete on reboot. It's a known issue that we created a KB article for, you need to stop the vcops service before upgrade as a workaround, and we plan to fix it by stopping the vcops service during the upgrade automatically in future releases.

http://kb.vmware.com/kb/2075114

[Edit: the KB article was not originally marked as public, link has been updated]

Reply
0 Kudos
malabelle
Enthusiast
Enthusiast
Jump to solution

Yes.

It worked. you should put this KB public... I lost a lot of time on this one...

Thanks.

vExpert '16, VCAP-DCA, VCAP-DCD
Reply
0 Kudos
vRickE
Enthusiast
Enthusiast
Jump to solution

I had this issue and had vcops too..

@rickespada
Reply
0 Kudos
mcosman
Contributor
Contributor
Jump to solution

This is still an issue when upgrading to Horizon 6!

Reply
0 Kudos
mpryor
Commander
Commander
Jump to solution

Are you sure you're seeing the exact same issue with the 6.0 install? There was an explicit action put into the 6.0 installer to stop the v4v_broker_agent service during the upgrade process.

Reply
0 Kudos
mcosman
Contributor
Contributor
Jump to solution

Yep.. vcops agent was running all the time.. and after i stopped it and reinstalled horizon, horizon works like a charm...

before I stopped it.. debug log file showed exactly the same error.. (that's how I came to this discussion..;-)   )

Reply
0 Kudos
mpryor
Commander
Commander
Jump to solution

Can you share the 6.0 installer upgrade log? If there's still an issue I want to make sure we fix it in the next release.

Should be either under c:\programdata\vmware\log or %TEMP%, vmmsi*.log and vminst*.log.

Thanks!

Reply
0 Kudos
mcosman
Contributor
Contributor
Jump to solution

I managed to find the files... files dated from the 14th are containing the failed installation... files from the 15th containing the upgrade I just did and wend well..

Hope this shed some light..

Cheers,

Michel.

Reply
0 Kudos
mpryor
Commander
Commander
Jump to solution

On first glance it looks like the installer should have worked by stopping the service, but the file replacements were definitely still blocked by something. I'll try and get a second opinion on what the issue is.

MSI (s) (4C:38) [13:13:19:237]: 10 application(s) had been reported to have files in use.

MSI (c) (A0:04) [13:13:19:238]: File In Use: -v4v_broker_agent_svc- Window could not be found. Process ID: 3488

MSI (c) (A0:04) [13:13:19:238]: File In Use: -v4v_broker_agent_cfg- Window could not be found. Process ID: 3104

...

MSI (s) (4C:38) [13:13:19:240]: PROPERTY CHANGE: Adding VMServiceControl property. Its value is 'v4v_broker_agent;0;1'.

MSI (s) (4C:38) [13:13:19:240]: Doing action: VM_StopV4VBrokerAgentService

Action 13:13:19: VM_StopV4VBrokerAgentService.

Action start 13:13:19: VM_StopV4VBrokerAgentService.

MSI (s) (4C:34) [13:13:19:244]: Invoking remote custom action. DLL: C:\Windows\Installer\MSIDEF3.tmp, Entrypoint: VMServiceControl

Action ended 13:13:20: VM_StopV4VBrokerAgentService. Return value 1.

...

Info 1603.The file C:\Program Files\VMware\VMware View\Server\jre\lib\rt.jar is being held in use. Close that application and retry.

Reply
0 Kudos
mpryor
Commander
Commander
Jump to solution

There should be some additional log lines that aren't appearing on the main file. Can you reproduce again and (before you reboot) double check for extra copies of vminst log files in the locations I mentioned (plus also %TEMP%\##; where ## is a low number that represents your windows session ID) ?

Reply
0 Kudos