Highlighted
Contributor
Contributor

App Volumes 4 - issues with any installer that needs to register an ocx/dll

Hi,

We currently have a live environment using app volumes 2.16, however we are now looking to upgrade to app volumes 4.

We have created a new app volumes 4 manager, and are in the process of packaging up all of our applications. Any installer that registers an ocx/dll either fails with error 'couldn't register ocx/dll' or successfully installs and allows me to finish the packaging process and once attached to a desktop i get an error while trying to launch the application 'ocx/dll is not registered'. This has only happened on App Volumes 4 as the applications in question are currently in use in our live environment on App Volumes 2.16. I've also noticed if the packaging machine isn't in record/packaging mode the applications install and launch without any errors.

Has anyone else come across this issue in App Volumes 4? 

Thanks

Tags (1)
7 Replies
Highlighted
Enthusiast
Enthusiast

I am now experiencing the same behaviour when trying to package SAS Professional. No OCX files are registered successfully and thus the application does not install successfully.

Have you had any luck in getting it to work for you? Have you talked to VMware about it yet?

Thanks

0 Kudos
Highlighted
VMware Employee
VMware Employee

Moderator: Thread moved to the App Volumes area.

0 Kudos
Highlighted
Contributor
Contributor

We are experiencing the same Problem. Has anybody opened a SR?

0 Kudos
Highlighted
Enthusiast
Enthusiast

I have now opened an SR (number 20136981607) and will post here with any findings.

0 Kudos
Highlighted
Enthusiast
Enthusiast

Response from Support:

This is a known issue in App Volumes 4.0.1, that will be resolved in the next release of App volumes 4.1.

There is a workaround for the issue. Can you log into your provisioning machine, and run the following command through cmd:

reg add HKLM\SYSTEM\CurrentControlSet\Services\svdriver\Parameters /v OptimizationLevel /t REG_DWORD /d 0 /f

After adding this, reboot the provisioning vm after this command, and only after that start the provisioning process.

Then try recapture the application and see if you see the same issue.

If this resolves the issue, then this confirms you are experiencing a known issue, and it will be resolved in the next release of App Volumes.

Have not tried it yet. Will report back after.

Highlighted
Enthusiast
Enthusiast

After applying the registry fix I seem to have been able to capture my application (SAS Professional). At least I could start it without errors after deploying it to a test user.

Highlighted
Contributor
Contributor

The Registry Key did solve the Problem in our case too. Thanks for sharing!

0 Kudos