VMware Horizon Community
EricNichols
Hot Shot
Hot Shot
Jump to solution

On View 6.0.1 Linked Clone Pool, wssm.exe prevents some apps from running

As soon as we kill wssm.exe, our apps will start. We can then restart wssm.exe.

Below is the app info from tcpview. Output from procmon did not give any indication as to why the app failed to start. These apps worked fine with View 5.2's version of wssm.exe.

processPIDProtocolLocalAddressLocalPortRemoteAddressRemotePortState
grapple.exe4360TCPdev-001.a.local56453db.a.localinformixESTABLISHED
hook.exe4224TCPdev-001.a.local56458db.a.localinformixESTABLISHED
push.exe2036TCPdev-001.a.local56459db.a.localinformixESTABLISHED
wrong.exe5780TCPdev-001.a.local56460db.a.localinformixESTABLISHED
Reply
0 Kudos
1 Solution

Accepted Solutions
mpryor
Commander
Commander
Jump to solution

I've seen another report of this, can you try the following workaround?

* Set HKLM\Software\VMware, Inc.\VMware VDM\Plugins\wssm\applaunchmgr\enabled = dword:0 (you'll probably need to create the value, the key should exist)

* Try with a new login

The applaunchmgr component is responsible for the launching of seamless applications and window monitoring in RDSH but is a shared component that is put down on desktop OS versions too, and is meant to be inactive unless needed. Let me know if it fixes the issue, and if you could find an example of a freely distributable program that has the same problem please link to it.

Mike

View solution in original post

Reply
0 Kudos
5 Replies
EricNichols
Hot Shot
Hot Shot
Jump to solution

Setting the TCP dynamic port range to something higher did not get the programs to start.

netsh int ipv4 set dynamicport tcp start=64000 num=1000

We still needed to kill wssm.exe first. The programs then used ports starting with 64010. Is wssm.exe acting like a security proxy? We get the same behavior with or without the windows firewall or blast gateway on or off.

Copying wssm.exe and messageframework.dll from a 5.2 client to 6.0.1 client and things worked fine.

Reply
0 Kudos
mpryor
Commander
Commander
Jump to solution

I've seen another report of this, can you try the following workaround?

* Set HKLM\Software\VMware, Inc.\VMware VDM\Plugins\wssm\applaunchmgr\enabled = dword:0 (you'll probably need to create the value, the key should exist)

* Try with a new login

The applaunchmgr component is responsible for the launching of seamless applications and window monitoring in RDSH but is a shared component that is put down on desktop OS versions too, and is meant to be inactive unless needed. Let me know if it fixes the issue, and if you could find an example of a freely distributable program that has the same problem please link to it.

Mike

Reply
0 Kudos
EricNichols
Hot Shot
Hot Shot
Jump to solution

Will this affect the run command on connect and reconnect? Is it okay to use this in production?

Reply
0 Kudos
mpryor
Commander
Commander
Jump to solution

This won't affect CommandsToRunOnConnect, no. I have no reason to believe it would have a negative impact on desktop systems but it's not officially supported as a workaround right now - please raise a support request to get this solved for you. Did you have a sample app I can try out myself that shows this problem?

Reply
0 Kudos
EricNichols
Hot Shot
Hot Shot
Jump to solution

Unfortunately, this is a closed source proprietary app. I might be able to put you in touch with the developers.

Reply
0 Kudos