Hello,
So latly I have run into some issues that I can't explain and I hope someone here can. So I have MS Project 2010 and Office 2010 thinapped in my orginzation. Latly I have been getting this error.
"Microsoft Office cannot verify the license for the application. A repair attempt failed or was canceled by the user. The application will not shut down."
I have no idea what causes this. I can go to a diferant machine and run my Office and Project thinapps and they run and activat fine and I never see this error. I als created two exact vm's with Windows 7. All the same software and patch level It works on one but not the other! I dont understand. I attached the screenshot to the post.
Anyone have any ideas?
Thanks.
Both Office 2010 and Project 2010 ThinApps cannot work together on a same machine. It is a known issue.
A workaround is to capture both together as a single ThinApp.
Lakshman wrote:
Both Office 2010 and Project 2010 ThinApps cannot work together on a same machine. It is a known issue.
A workaround is to capture both together as a single ThinApp.
I don't have them running together on the same machine. The error that I get is from Project and Office form differant machine. The Thinapps are not installed together at all.
Quick questions:
1. Have you deleted the sandbox first and tried?
2. Are there any other Office 2010 family products (Eg: Visio, Project) installed, either ThinApp or native?
3. Do you have office 2010 natively installed?
4. Have you had Office 2010 deployment kit or App-V installed before?
5. If you are using KMS license, are you able to access (ping) the KMS server?
6. How different is that machine from your VM's?
1. Have you deleted the sandbox first and tried?
Yes and there is no change.
2. . Are there any other Office 2010 family products (Eg: Visio, Project) installed, either ThinApp or native?
Office 2010 Native
3. Do you have office 2010 natively installed?
Yes
4. Have you had Office 2010 deployment kit or App-V installed before?
No
5. If you are using KMS license, are you able to access (ping) the KMS server?
Yes
6. How different is that machine from your VM's?
No differance. We are in a VDI enviorment.
There you go. Office 2010 or Project 2010 ThinApp fail to launch if Office 2010 is installed natively.
Lakshman wrote:
There you go. Office 2010 or Project 2010 ThinApp fail to launch if Office 2010 is installed natively.
Wow. Im sorry but that to me seem like a huge black eye for application virtulization. Is this going to be fixed at some point in time? It seems silly that I can't have a native install of Office and ren a THinapp of Project...
I never had these issues with Project 2007 or 2003.
We are working on it. Hopefully, it will be fixed in the upcoming release of 4.7
I've downloaded and installed ThinApp 4.7, but I suspect that 4.7 does not resolve the issue. Any word?
Here's another thought: use VBscript to check for osppsvc and start it if it's not already running. This syntax works on my Windows 7 Pro 64-bit machine (UAC turned off, logged in with admin rights) when run from command prompt using cscript: modified from original script by Guy Thomas from www.computerperformance.co.uk/
Option Explicit
Dim objWMIService, objItem, objService
Dim colListOfServices, strComputer, strService, intSleep
strComputer = "."
'On Error Resume Next
' NB strService is case sensitive.
strService = " 'osppsvc' "
Set objWMIService = GetObject("winmgmts:{impersonationLevel=impersonate}!\\" & strComputer & "\root\cimv2")
Set colListOfServices = objWMIService.ExecQuery("Select * from Win32_Service Where Name =" & strService & " ")
For Each objService in colListOfServices
If objService.State <> "Running" Then
objService.StartService()
End If
Next
WScript.Echo "Your "& strService & " service has Started"
WScript.Quit
'End of Example WMI script to Start / Stop services
Question: If the ThinApp application is packaged on a VM where the APP-V deployment kit has already been installed with the appropriate switches, and this scipt is dropped in to the project root, will the script be looking inside the bubble to start the service, or outside? Keep in mind that the APP-V Deployment Kit for Office 2010 would be pushed to the client machine ahead of the ThinApp'ed Office 2010 component (in my case, Visio and Project.)
Toby Fruth wrote:
I've downloaded and installed ThinApp 4.7, but I suspect that 4.7 does not resolve the issue. Any word?
So I have tried the new release as well and it seems that you are correct, this did not fix the issues. ![]()
As for whether or not this is a "black eye" issue for application virtualization, please consider the following:
The issue is not fixed as of ThinApp 4.7. This is an isolation problem with the Office Software Protection Platform Service (OSPPSvc) in Office 2010.
1) The virtual OSPPSvc service does not start when native OSPPSvc service is already running.
2) The virtual Office 2010, including virtual OSPPSvc service, can READ most of the native files and registries, so it can see certain registries installed by native Office 2010. However those registries are not expected by the virtual OSPPSvc service. So you can say this is a configuration issue under the setup of having native and virtual coexist.
With native Office 2010 properly isolated, the problem will be fixed, but interaction between native and virtual may also be restricted, e.g. OLE.
This issue has been code fixed, should be available in the next release of ThinApp.
Well this is some good news hopefully. When will this be released.
Having issues with multiple Office 2010 applications (Office Suite, Project, Visio) not running on the same client? Please have a look here: http://kb.vmware.com/kb/1022287.
I was recently tasked with providing thinapps of ms project & visio 2010, to work in supplementation of a natively installed Office 2010 suite, and ran into the issues described here.
I was able to get thinapp version to work against a vanilla OS (no native installation), but that isn't what I was hoping for - it was however reassuring to see that I wasn't making a mistake with my builds.
What ultimately resolved this issue for me was contacting VMWare support, as described in the KB article linked above:
A virtualized Office 2010 family product may fail to launch, or terminate with an error, if deployed to an operating system that already has an Office 2010 component natively installed. To address this, file a support request with VMware Support and quote this Knowledge Base article ID (1022287) in the problem description. For more information, see How to Submit a Support Request.
They provided me with 4.7.0 build 556613 and the following reg settings to add to the top of HKEY_LOCAL_MACHINE.txt:
deleted HKEY_LOCAL_MACHINE\Software\Classes\AppID\{32820823-eb9f-42bf-badb-4482911536bb}
deleted HKEY_LOCAL_MACHINE\Software\Classes\AppID\{32f506a9-36f4-45ca-a3b7-e220e2fadcfc}
deleted HKEY_LOCAL_MACHINE\Software\Classes\AppID\{0b6faa6c-afa9-4c9f-92a9-d1b9e13e49e7}
deleted HKEY_LOCAL_MACHINE\Software\Classes\AppID\{b3fd0790-e46d-44d8-a88c-fcd99771da5e}
deleted HKEY_LOCAL_MACHINE\Software\Classes\AppID\{4918cead-10bb-4345-b406-c0096b646c24}
deleted HKEY_LOCAL_MACHINE\Software\Classes\AppID\{80f8087e-f900-4c25-b7fb-66ddf3ad2685}
deleted HKEY_LOCAL_MACHINE\Software\Classes\AppID\{2fe7e56b-8195-4c8f-a199-fde2e4e09456}
deleted HKEY_LOCAL_MACHINE\Software\Classes\AppID\{f1f1e3ad-0dff-41f3-96d0-11b3aa4f0c96}
deleted HKEY_LOCAL_MACHINE\Software\Classes\AppID\{c722abe9-52ee-45de-b7aa-1cb7f27dac05}
deleted HKEY_LOCAL_MACHINE\Software\Classes\AppID\{458b6290-216a-410c-bdc8-24008876301b}
deleted HKEY_LOCAL_MACHINE\Software\Classes\AppID\{491ccf72-9e19-45bc-8a78-5e8c8be7f464}
deleted HKEY_LOCAL_MACHINE\Software\Classes\AppID\{529c81ad-3788-4f3d-8c1c-71ccf202de21}
deleted HKEY_LOCAL_MACHINE\Software\Classes\AppID\{2b402eec-0c7f-447c-8d44-e816888b1115}
deleted HKEY_LOCAL_MACHINE\Software\Classes\AppID\{ce175ea0-8692-4968-b769-1b0029498a41}
deleted HKEY_LOCAL_MACHINE\Software\Classes\AppID\{b69b7cc0-0e89-46d0-a99e-abddd4b61743}
deleted HKEY_LOCAL_MACHINE\Software\Classes\AppID\{de5206e8-c4ad-42cc-bd53-8cbb3558e80c}
deleted HKEY_LOCAL_MACHINE\Software\Classes\AppID\{f9285c37-8314-4516-89d5-e4932dc92de6}
deleted HKEY_LOCAL_MACHINE\Software\Classes\AppID\{dce06134-5696-4fa8-b13e-51aad6def5d9}
deleted HKEY_LOCAL_MACHINE\Software\Classes\AppID\{fc4fc45c-be7e-4704-99ac-951db77b91dc}
deleted HKEY_LOCAL_MACHINE\Software\Classes\AppID\{947a7174-52b0-44f2-bfb6-7f3e07843277}
deleted HKEY_LOCAL_MACHINE\Software\Classes\AppID\{69c6e0d2-c565-4d52-9930-d46c4116f708}
deleted HKEY_LOCAL_MACHINE\Software\Classes\AppID\{aedd0615-3da5-4d6a-abde-63cedf4e80a4}
deleted HKEY_LOCAL_MACHINE\Software\Classes\AppID\{23a22094-b01e-43cf-a372-6d4ee6d9eabf}
deleted HKEY_LOCAL_MACHINE\Software\Classes\AppID\{22c493c3-99e2-45e9-a739-ee497e141be3}
deleted HKEY_LOCAL_MACHINE\Software\Classes\AppID\{d049f335-4ac7-4400-b449-c532f4876693}
deleted HKEY_LOCAL_MACHINE\Software\Classes\AppID\{8d2d2f50-cdf0-45cb-8949-9a39ade5cb7a}
deleted HKEY_LOCAL_MACHINE\Software\Classes\AppID\{3ff290b5-342b-40dd-a66b-00e76c0e5b80}
deleted HKEY_LOCAL_MACHINE\Software\Classes\AppID\{3086391e-945a-44f8-880a-24d7eee14dae}
deleted HKEY_LOCAL_MACHINE\Software\Classes\AppID\{2f9a3248-de98-4b16-b56c-0cdc2d4d3d42}
deleted HKEY_LOCAL_MACHINE\Software\Classes\AppID\{23b98090-64e4-400f-9107-921a78bc2cdd}
deleted HKEY_LOCAL_MACHINE\Software\Classes\AppID\{8d95965c-956f-4eed-a18f-cf18e6d31e88}
deleted HKEY_LOCAL_MACHINE\Software\Classes\AppID\{4530f183-15be-4eba-8bef-e68b6686b921}
deleted HKEY_LOCAL_MACHINE\Software\Classes\AppID\{7f76b468-81a6-49ec-9c38-069143206618}
deleted HKEY_LOCAL_MACHINE\Software\Classes\AppID\{37d23cc0-470c-4312-a01c-77e1c6e0ad61}
deleted HKEY_LOCAL_MACHINE\Software\Classes\AppID\{b17b4b81-bb80-4c17-871c-57d5ab14991d}
deleted HKEY_LOCAL_MACHINE\Software\Classes\AppID\{b2e79a4f-f632-43af-86dc-191cd03082ae}
deleted HKEY_LOCAL_MACHINE\Software\Classes\AppID\{ea2c0345-2c36-45d4-9692-6972ce4e96c6}
deleted HKEY_LOCAL_MACHINE\Software\Classes\AppID\{35dee61f-342b-41a2-acdb-2e207760af1b}
deleted HKEY_LOCAL_MACHINE\Software\Classes\AppID\{8c74e7e1-d44a-4cce-9ec0-144a0e037d43}
deleted HKEY_LOCAL_MACHINE\Software\Classes\AppID\{816b6d90-87e6-430f-a5fd-734be662bb55}
deleted HKEY_LOCAL_MACHINE\Software\Classes\AppID\{a5fb8c3a-6da1-4438-a6cf-44c589aa2665}
deleted HKEY_LOCAL_MACHINE\Software\Classes\AppID\{6a4a43f1-4846-4c4b-9a70-c4eac0184d97}
deleted HKEY_LOCAL_MACHINE\Software\Classes\AppID\{c3fe9663-9bde-40dd-ae25-f2f8aa2d6b1a}
deleted HKEY_LOCAL_MACHINE\Software\Classes\AppID\{26cd69c4-d593-4936-a8bb-e592816a0fad}
deleted HKEY_LOCAL_MACHINE\Software\Classes\AppID\{ad89527a-aed4-4382-be23-19be89f9d01e}
deleted HKEY_LOCAL_MACHINE\Software\Classes\AppID\{c00469cb-209b-4823-94bb-4139e48f5923}
deleted HKEY_LOCAL_MACHINE\Software\Classes\AppID\{a5ce878d-59a9-48ae-8e0a-ed717267302d}
deleted HKEY_LOCAL_MACHINE\Software\Classes\AppID\{1a821936-fee1-43a8-8222-87f4e049afb9}
deleted HKEY_LOCAL_MACHINE\Software\Classes\AppID\{a5e4db17-4067-4d19-9812-2e3b879b8a35}
deleted HKEY_LOCAL_MACHINE\Software\Classes\AppID\{712cbb5d-58be-48dc-b930-c8362f63fdee}
deleted HKEY_LOCAL_MACHINE\Software\Classes\AppID\{f986cdbd-8807-418a-adbd-b8ddbf92c590}
deleted HKEY_LOCAL_MACHINE\Software\Classes\AppID\{8abec68c-a5d1-40f5-966c-501dddf5c3fe}
deleted HKEY_LOCAL_MACHINE\Software\Classes\AppID\{cc0569bb-bde5-4d6b-ac65-b1fa7a227258}
deleted HKEY_LOCAL_MACHINE\Software\Classes\AppID\{fbdc5f1a-0b96-4b9e-8f17-df17a3dc59ef}
deleted HKEY_LOCAL_MACHINE\Software\Classes\AppID\{17e35d4e-df3a-4a2b-83be-a1b17e710e8a}
deleted HKEY_LOCAL_MACHINE\Software\Classes\AppID\{a1971a89-4e84-41d9-b3e0-18a109146bff}
deleted HKEY_LOCAL_MACHINE\Software\Classes\AppID\{f4bc39d7-c2c0-40f1-8e59-fe9bd797d755}
deleted HKEY_LOCAL_MACHINE\Software\Classes\AppID\{0b753f3d-cf41-42b6-8289-b7a8d334e8f9}
deleted HKEY_LOCAL_MACHINE\Software\Classes\AppID\{9d9abca5-0a0b-485a-a962-d1b983ec8274}
deleted HKEY_LOCAL_MACHINE\Software\Classes\AppID\{d19d1258-ada6-40e1-b4d6-5d160e2ebfc9}
I am very excited to say that after testing my most recent builds of both project and visio, I am able to simultaneously run a native office 2010 installation and launch the thinapp project/visio without any licensing issues. All software is KMS licensing.
I am curious to know what enhancements were made under the new build, and if the above reg settings will work on the 4.7.0-519532 release as I was unable to test.
Hope this helps!
Hi nelshawn, build 4.7.0-519532 (4.7.0 GA) may not work even with the registry configuration change, because that build does not have a fix on virtual service.
Yang wrote:
Hi nelshawn, build 4.7.0-519532 (4.7.0 GA) may not work even with the registry configuration change, because that build does not have a fix on virtual service.
Does 4.7.0-556613 specifically address the virtual service issue?
I am asking because initially that is all I was provided, which I discovered my builds would function and license so long as the computer had a fresh reboot and the native office suite hadn't been launched yet. However, as soon as you launch excel or word the thinapps would immediately complain about licensing and terminate.
It wasn't until I added those reg settings that the thinapp & native would run simultaneously.
Yes, 4.7.0-556613 is a hotfix including a fix on virtual service, but it does not address another isolation problem. The registry configuration change helps the isolation problem. Both are required for this to work.
Good to know, thank you!
Should I be concerned with going to production under these current circumstances? My pilot users report no issues as of yet, but i'd hate to push it out only to see it break down the road.
