.NET 247

Multimobile Development: Building Applications for any Smartphone

Logon or Create an Account

Problem: Viewing MSDN Help with User account

Messages

Related Types

This message was discovered on microsoft.public.vsnet.documentation.

Post a new message to this list...

Stefano

GOOD ANSWER

I'm not sure if this is a bug.
If i push the F1 key over the word "WriteLine" in a
Console.WriteLine() statement i get msi windows installer pop-up
dialogs viewing some content in the msdn July 2003 library.
This only happens when I'm running under a non-administrator account
as microsoft recommends for development work with .net.

If i deinstall the VS.NET 2003 and use the MSDN documentation directly
all works.

I'm using the july 2003 MSDN within VS.NET Professional. I've tried
full-install and custom install
with no difference -- only running as admin works.
The wwwroot$ is shared and explicit permissions for the
non-admin user has also been enabled.

Here's the messages that pop up.

Preparing to install ...
Gathering required information
Please wait while Windows configures Visual Studio.NET
Professional 2003 - Italian
Error 1606: Could not access network location wwwroot$:
Unable to get security info for this object.
Error 1606. Could not access network location VS
Developers (could not create group)

It's happened everytime.
If i use the Administrative account all work and it's works even if i
give to the user the PowerUser privilege, call the help, and than go
back to the "normal user" privilege again.
Someone can help me ??
Thanks a lot
Stefano

	Reply to this message...
	Vote that this is a GOOD answer... (19 votes from other users already)

Art Wallace

GOOD ANSWER

Stefano,
I was having the same problems on every computer that I installed VS.NET on. I think I found the solution.

Try importing one or both of these into the registry of your User account:

[HKEY_CURRENT_USER\Software\Microsoft\Office\10.0\Common]
"UserData"=dword:00000001

[HKEY_CURRENT_USER\Software\Microsoft\Office\10.0\Common\UserInfo]
"UserInitials"=hex:00,00
"UserName"=hex:00,00

	Reply to this message...
	Vote that this is a GOOD answer... (24 votes from other users already)

Stefano

GOOD ANSWER

Hi Art,
following your way i have finally found a solution for this problem.
The problem is related at 2 Office XP keys in the registry.
I have find that if in your machine you install OFFICE XP all works.
So i have investigating what changes do in the registry Office XP and
i have found these 2 crucial keyss

>>>>>>>>>>>>>>>>>>>>>>>>
First Key
>>>>>>>>>>>>>>>>>>>>>>>>
[HKEY_CURRENT_USER\Software\Microsoft\Office\10.0]

[HKEY_CURRENT_USER\Software\Microsoft\Office\10.0\Common]
"UserData"=dword:00000001
"OSAShortcut"=dword:00000001
"WebDriveUserData"=dword:00000001

[HKEY_CURRENT_USER\Software\Microsoft\Office\10.0\Common\Search]

[HKEY_CURRENT_USER\Software\Microsoft\Office\10.0\Common\Search\Scopes]

[HKEY_CURRENT_USER\Software\Microsoft\Office\10.0\Common\Search\Scopes\My
Computer]
@="{3933B2EA-3EF1-11D3-8D06-005004838597}"

[HKEY_CURRENT_USER\Software\Microsoft\Office\10.0\Common\Search\Scopes\My
Email]
@="{3933B2EC-3EF1-11D3-8D06-005004838597}"

[HKEY_CURRENT_USER\Software\Microsoft\Office\10.0\Common\Search\Scopes\My
Projects]
@="{3933B2EB-3EF1-11D3-8D06-005004838597}"

>>>>>>>>>>>>>>>>>>>>>>>>
Second Key
>>>>>>>>>>>>>>>>>>>>>>>>

[HKEY_CURRENT_USER\Software\Microsoft\Shared Tools]

[HKEY_CURRENT_USER\Software\Microsoft\Shared Tools\Proofing Tools]

[HKEY_CURRENT_USER\Software\Microsoft\Shared Tools\Proofing
Tools\Custom Dictionaries]
"1"="CUSTOM.DIC"

And all works !!!!!!!!!!!!

I think that someone in MS should check this "deadlock" between VS.NET
2003 and Office XP (or 2003, i presume).

If you don't install VS.NET then help System works in the SDK and in
the MSDN version , without installing Office XP
Probably, VS.NET set some component that when you invoke the help it
try to find something and the installer starts again.
I hope that this can help you !!!
By
Stefano

"Art Wallace" <Click here to reveal e-mail address> wrote:

[Original message clipped]

	Reply to this message...
	Vote that this is a GOOD answer... (17 votes from other users already)

Art Wallace

GOOD ANSWER

Hi Stefano,
Your solution worked for me. I was worried about importing any of those GUID reg keys but it doesn't seem to cause any problems. Thanks.

And yes, this is definitely something MS needs to fix.

	Reply to this message...
	Vote that this is a GOOD answer... (20 votes from other users already)

System.Console

BootFX
Reliable and powerful .NET application framework.

iOS, Android and Windows Phone Development Training and Consultancy

Hosted by RackSRV Communications