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.
SO I guess im not following on this thread, what isolation isssue are you having?
As for all teh reg keys taht needed to be deleted I never did any of that. I just went back a rebuilt all my Office product (Project, Visio etc) and the KMS issue was gone.
I believe you may be experiencing the same issue that I ran across:
Office 2010 Suite (word, excel, access, outlook) installed natively.
MS Project 2010 KMS Thinapp works on the machine until you launch one of the natively installed products. Project 2010 will not work after this, unless you reboot or clear app data.
MS Visio 2010 yields same results.
Don't let it fool you, unless you've performed the same resolution steps that I have I am very doubtful that your rebuild solved the problem... unless you thinapped the entire office suite + project & visio?
nelshawn wrote:
I believe you may be experiencing the same issue that I ran across:
Office 2010 Suite (word, excel, access, outlook) installed natively.
MS Project 2010 KMS Thinapp works on the machine until you launch one of the natively installed products. Project 2010 will not work after this, unless you reboot or clear app data.
MS Visio 2010 yields same results.
Don't let it fool you, unless you've performed the same resolution steps that I have I am very doubtful that your rebuild solved the problem... unless you thinapped the entire office suite + project & visio?
No it works. Ive done every combonation of launching native and virtual and I have had no issues.
OUr enviroment hase office installed native and all the rest thinapped. No iisues so far.
>> No it works. Ive done every combonation of launching native and virtual and I have had no issues.
>> OUr enviroment hase office installed native and all the rest thinapped. No iisues so far.
Which ThinApp build did you use and did you do any additional customization other than the usual Office capture process?
I was running virtual Office 2010 and native Office together and I have to apply the registry change to make it work. Hope we can see feedback from more people.
Sometimes I get a little excited and post results before all the tests are complete. I'm doing it again!
I have the hotfix build of ThinApp, but I did not have the registry entries. KMS activations were failing about 50% of the time without the registry entries. I'm testing virtual Project 2010 and virtual Visio 2010 against native Office 2010.
I have many more tests to conduct this week, but so far it looks like the hotfix build of ThinApp 4.7, combined with the registry entries, resolves the KMS activation issues.
I will try various combinations of reboots and launch sequences and report the reults back to this thread.
Wish me luck!
nelshawn wrote:
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!
Can you explaine this post? About you said to add teh reg keys but what you have above has DELETED in front of it. Im not sure which is it
> Can you explaine this post? About you said to add teh reg keys but what you have above has DELETED in front of it. Im not sure which is it
By default a ThinApp application can see files and registries on the system unless isolation mode is "full". "DELETED" in front of a registry key means the application cannot see it even if it exists on the system.
It needs to be pasted exactly as you see it to the top of HKEY_LOCAL_MACHINE.txt located within the project build directory.
Essentially what is happening is these are the roughly 30 or so Class IDs associated to various different installs of MS 2010 products such as Office Standard, Office Pro Plus, Office Home and Student, Office Pro, Project Pro, Project Std, Visio Pro, and individual app installs such as Word, Excel, Outlook, PowerPoint, and Access.
Very basically, if what is installed natively doesn't match with what is packaged with ThinApp, then there are license activation issues.
Since ThinApp runtime loads the reg hives from top to bottom, deleting everything up front (at the top of the Local Machine registry hive) allows for the ThinApp package to only see just what it needs and none of the native settings which may interfere (as there are invariably going to be a couple of these further on down in the Local Machine hive for your ThinApp package of whatever MS 2010 product you are packaging - meaning ThinApp will load these as needed).
In short, by adding these values to the HKEY_LOCAL_MACHINE.TXT registry hive file, you are helping ThinApp properly isolate the MS 2010 app in question from whatever native settings in order for the ThinApp package to load and work correctly.
Hope this helps explain what is going on here. ![]()
Ok so, I have the new build of thinapp, the hot fix. Ive added the regkeys and I still have the problem.. Is there soemthing Im missing?
Make sure sandboxes are deleted and you are testing on a fresh system because a leftover sandbox will cause false results.
Dean Flaming wrote:
Make sure sandboxes are deleted and you are testing on a fresh system because a leftover sandbox will cause false results.
I have. I have a dev enviorment of 10 systems that are clean. No sandboxes. Still same issues. liceance error.
Did you stop the Office Software Protection Platform service before the postscan?
Does it work on a machine that does not have office products natively installed?
No I did not stop that service.
Yes it seems that it does work on a machine that DOES NTO have office products installed.
I would recommend stopping the service before you perform the post scan. I had mixed results when I left the service running.
What I dont get is that all I had to do is capture my package and deploy, that all I did and it worked. Today is when the KMS issues started happening.
> What I dont get is that all I had to do is capture my package and deploy, that all I did and it worked. Today is when the KMS issues started happening.
I'm guessing there has been some local file/registry changes lately, e.g. from usage of native Office, which become visible to virtual OSPPSvc and make it unhappy.
Yang wrote:
> What I dont get is that all I had to do is capture my package and deploy, that all I did and it worked. Today is when the KMS issues started happening.
I'm guessing there has been some local file/registry changes lately, e.g. from usage of native Office, which become visible to virtual OSPPSvc and make it unhappy.
I agree. I bet your right. I guess ill re package and stop that service and see what happends.
Well something new now.
When I lauch Project for example. It locks up and I have to open task manager to kill it...
we manage to thinapp Visio and Project 2010 without license issue for W7 x86 with Office 2010 x86 natively installed using ThinApp 4.7.0 build 588339 - Thanks to VMWare Technical Support. However, we are unable to get Visio/Project 2010 to do "Send as Attachment". Anyone else tried this?
