MarcBouchard
Enthusiast
Enthusiast

Microsoft Access 2010 woes...

Jump to solution

3 days... That I've been trying to get this going. I hope someone can help.

I have gone thru about 12 blogs, KBs, step-by-step recipes and I can't get this package to work...

Build VM: XP SP3, latest hotfixes installed, ThinApp 4.7.3-891762

Destination: Windows 7 SP1, latest hotfixes, 64 bits.

My issue is licensing related, which is adressed by about all the blogs I've found but I can't get it to work. I always receive this message: "Microsoft Office cannot verify the  license for this application. A repair attempt failed or was canceled by  the user. The Application will now shut down."

I have a thick install of Office 2010 on the target workstations. From what I read it's an issue that was resolved with the latest version of ThinApp, which I'm running.

Any help would be greatly appreciated. I have a case opened with VMware and so far, they pointed me to the KBs I already had read...

My installation recipe:

1. Copy the Access 2010 installation sources to the Build VM.

2. Disable network

3. Run pre-scan

4. Take snapshot Smiley Wink

5. Install Access to C:\Office (I created an MSP, but I also tried with a manual install with same result).

6. Open Access 2010, disable Update Checking, verify that it is NOT activated, press F1 to run the help menu, then close.

7. Usually I enable the network here, run a windows update to get the latest updates for Access, then disable the network. After verification it is still not activated. I also tried without doing this step, same result.

8. Run postscan

9. Delete the %History%, %Cookies%, %Internet Cache%, %Fonts% folders (tried without this step as well)

10. Copy the captured files to my network share then start editing the configs.

One step mentions to copy the folder OfficeSoftwareProtectionPlatform from
%Drive_C%\Documents and Settings\All Users\Microsoft
to
%Drive_C%\ProgramData

which I have tried (ProgramData doesn't exist, I have to create it).

PACKAGE.INI

1. Enable MSIstreaming (1)

2. Set VirtualComputerName=ACCESS2010 (to check in KMS logs, easier than admin-1435986)

3. Exclude filelist (also tried without this)

[FileList]
ExcludePattern=*.bak,*.msi,*.mst,*.cab,*.msp

HKEY_LOCAL_MACHINE.txt

1. Insert the following at the beginning of the file:

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}

2. Then this at the end of the file (might not be necessary as I read this is for MAK, not KMS - also tried without it)

isolation_full HKEY_LOCAL_MACHINE\Software\Microsoft\OfficeSoftwareProtectionPlatform
Value=UserOperations
REG_DWORD=#01#00#00#00

0 Kudos
1 Solution

Accepted Solutions
pbjork
VMware Employee
VMware Employee
0 Kudos
12 Replies
pbjork
VMware Employee
VMware Employee
0 Kudos
MarcBouchard
Enthusiast
Enthusiast

No, that's one I hadn't seen yet... Smiley Wink I'll go through this one right now and report back. Thanks!

Marc

0 Kudos
MarcBouchard
Enthusiast
Enthusiast

No luck, same error message. On the KMS server, I don't even see an event that the activation request was processed...

Smiley Sad

0 Kudos
MarcBouchard
Enthusiast
Enthusiast

Oops! I just deleted the sandbox folders and it seems to work. I overlooked that part (cleanup of the sandbox), maybe that's what's been giving me those false failures...

Thanks a lot for the pointers (and for the writeup, noticed you're the one who did it Smiley Happy ), I'll run some more tests before calling it a "WIN" !

Marc

0 Kudos
Lakshman
Champion
Champion

Can you try setting the below values in the config.xml?

<Setting Id="KMSSERVICENAME" Value="kmsserver.domain.com" />

<Setting Id="AUTO_ACTIVATE" Value="1" />
0 Kudos
pbjork
VMware Employee
VMware Employee

Great stuff.. Yes, not deleting the Sandbox can jump up and bite you sometimes..

0 Kudos
MarcBouchard
Enthusiast
Enthusiast

As per the above posts, I got it to work finally. That step was in the writeup, I had seen it before but it was listed as "optional"...

Thanks!

Marc

0 Kudos
MarcBouchard
Enthusiast
Enthusiast

Well, the licensing issue IS resolved. However...

Getting a bunch of error messages when opening up or creating an MDB... Time to troubleshoot...

"Workgroup Administrator couldn't create the workgroup information file. Make sure you have specified a valid path and file name, that you have adequate permissions to create the file, and that you have enough disk space on the destination drive (-3100)"

Then I get another popup with "Microsoft Access couldn't find file 'chinese string'. This file is required for startup.

EDIT: Ok, after following this troubleshooting tips (http://answers.microsoft.com/en-us/office/forum/office_2007-access/workgroup-administrator-couldnt-c...) I found that the package is unable to write to the C:\Users\username\AppData\Roaming\Microsoft\Access\ folder.

In my %APPDATA%\##Attributes.ini file, the DirectoryIsolationMode is set to Merged, so I don't understand why it can't write to it...

Marc

0 Kudos
MarcBouchard
Enthusiast
Enthusiast

Finally got it to work. Ran log monitor, which identified possible issues and once I changed the folder isolations to merged for the mentionned issues, it ran perfectly.

I now have a fully working recipe for Access 2010, that works with Office 2010 natively installed.

Thanks for the assistance... I'll be posting another question for my 2nd package which is quite different Smiley Wink

Marc

0 Kudos
JonoDSparks2
Contributor
Contributor

Marc,

Any chance you remember which folders needed to be changed to Merged or at least what to look for in the Log Monitor?  I am seeing the same errors regarding folder access as you were after my builds and I'm at a logs generated are huge.

Thanks for any help!

-Jonathan-

0 Kudos
MarcBouchard
Enthusiast
Enthusiast

I posted the whole process on my blog, you can find it here:

http://www.subnet192.com/?p=555

0 Kudos
JonoDSparks2
Contributor
Contributor

I found your blog about an hour after my post.  It took me a few more tries and tweaks, but I think I got it working!

Thanks for your help!

0 Kudos