VS.NET/MSDN Annoyance

[Jarred Ward]

I'm running/trying to run VS.NET 2003 as a limited user on an XPPRO fresh,
clean, and updated install. When I open the MSDN library and go to a topic,
via VS.NET help or the library viewer, the VS.NET installer opens, pokes
around, and eventually putters out with some errors. If I cancel the
installer, or let it error out a few more times, everything works fine, but
it happens AGAIN when I select a new topic. If I run it as an administrator,
which defeats my purpose, voila, it works great. Reinstall, repair, reboot
has yielded nothing. Judging by the events, it may be pertinent to say I
have Office 2003 installed. Here are the events/errors that the MsiInstaller
gives in order of occurence:

1) Event 1004. Detection of product
'{E05F0409-0E9A-48A1-AC04-E35E3033604A}', feature 'dotNET_Framework_SDK',
component '{C9AF9050-C8BE-11D1-9C67-0000F81F1B38}' failed. The resource
'HKEY_CURRENT_USER\Software\Microsoft\Office\10.0\Common\UserData' does not
exist.

2) Event 1001. Detection of product
'{E05F0409-0E9A-48A1-AC04-E35E3033604A}', feature 'dotNET_Framework_SDK'
failed during request for component '{C763CD13-6E1E-4166-8C78-D274B266E9B6}'

3) Event 11606. Product: Visual Studio .NET Enterprise Architect 2003 -
English -- Error 1606.Could not access network location wwwroot$: Unable to
get security info for this object.

4) Event 11606. Product: Visual Studio .NET Enterprise Architect 2003 -
English -- Error 1606.Could not access network location wwwroot$: Unable to
get security info for this object.

5) Event 11606. Product: Visual Studio .NET Enterprise Architect 2003 -
English -- Error 1606.Could not access network location VS Developers (could
not create group).

6) Event 11729. Product: Visual Studio .NET Enterprise Architect 2003 -
English -- Configuration failed.

I've seen a fewer other posts on this subject, but none of them with a
solution. What's the official word on this?

[Felix Wang]

Hi Jarred,

Thanks for posting. We have seen similar issues before. Let's try the
following:

1. Log on with the Admin user.

2. Rename the following file:

C:\Program Files\Common Files\Microsoft Shared\Office10\mso.dll

3. Launch VS.Net and let the reparation to finish.

4. Launch MSDN.

5. Close VS.Net and MSDN.

6. Search for the file named "CookDoc.dll". By default, it should be in
"C:\Program Files\Common Files\Microsoft Shared\MSDN".

7. Let's register the file by the following command:

RegSvr32 "C:\Program Files\Common Files\Microsoft Shared\MSDN\CookDoc.dll"

8. Logon with the original user.

I hope this can help to resolve the issue.

Regards,

Felix Wang
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.

[Jarred Ward]

Thanks Felix. It works perfect now.