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?
Moderator: Thread moved to the App Volumes area.
We are experiencing the same Problem. Has anybody opened a SR?
I have now opened an SR (number 20136981607) and will post here with any findings.
3 people found this helpful
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.
1 person found this helpful
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.
The Registry Key did solve the Problem in our case too. Thanks for sharing!