Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
HomeAnnouncementsFree MagazinesWhite PapersSubmit Content
Discussion GroupsASP.NETWindows FormsLanguages.NET FrameworkVisual Studio.NET
Articles.NET FrameworkASP.NETToolsWindows Forms
.NET DirectoryOpen Source ProjectsUser GroupsWeb Resources
Related Topics
Visual Basic 6SQL ServerMS AccessOther DB ProductsMS Server ProductsMore Topics ...

.NET Forum / Visual Studio.NET / Setup / February 2004

Tip: Looking for answers? Try searching our database.

Solution to "Error 1606" with MSDN Library and User accounts

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
Art Wallace - 28 Feb 2004 22:21 GMT
I have been plagued with problems when running VS.NET 2003 on clean installs of Win XP. I install under the Administrator account but have a normal user account for running VS.NET in (plus the VS Devs and Debuggers groups). VS will run fine but when accessing the MSDN Library, navigating to a document in the sidebar, then clicking that document, the Installer dialog will pop up and start going on about "Error 1606". I can't remember the exact error message now because it's working. If I clicked "Canel" the help page would successfully come up after some seconds. However that is very frustrating because it comes up for _every_ page I viewed and the whole process can take 30 seconds when hitting Cancel. Not clicking Cancel and letting it run can take minutes. If I run the same task from the Admin account there are no problems

I saw the messages from someone at MS about using RegMon to try to track the problems. That didn't help me but I did finally get around to looking in the OS Event - Application log. There are about 10 errrors but the most important looks like this
"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.

Using Regedit.exe I pulled up that area of the registry and verified that there was no UserData there. When I checked under the Admin account it was. So in "HKEY_CURRENT_USER\Software\Microsoft\Office\10.0\Common\" I created a new DWord entry with the title "UserData" and changed the value from 0 to 1. I also exported these values from the Admin account and imported them into my user account
[HKEY_CURRENT_USER\Software\Microsoft\Office\10.0\Common\UserInfo
"UserInitials"=hex:00,0
"UserName"=hex:00,0

Now it seems to work. Fingers crossed
Art Wallace - 28 Feb 2004 22:41 GMT
Ugh, after a reboot the error is back. Looking at the App log, it is now complaining about other registry keys

sorry to get your hopes up.
Phil Wilson - 29 Feb 2004 01:29 GMT
When you installed VS, make sure that you installed for everyone as a
per-machine install. That behavior has some echoes of installing a product
for the current user (Administrator account) and accessing it from another
user account (which doesn't have per-user entries and keeps getting
repaired). (I *think* there's a per-machine/per system choice when you
install VS 2003).

Signature

Phil Wilson
[MVP Windows Installer]

> I have been plagued with problems when running VS.NET 2003 on clean installs of Win XP. I install under the Administrator account but have a
normal user account for running VS.NET in (plus the VS Devs and Debuggers
groups). VS will run fine but when accessing the MSDN Library, navigating to
a document in the sidebar, then clicking that document, the Installer dialog
will pop up and start going on about "Error 1606". I can't remember the
exact error message now because it's working. If I clicked "Canel" the help
page would successfully come up after some seconds. However that is very
frustrating because it comes up for _every_ page I viewed and the whole
process can take 30 seconds when hitting Cancel. Not clicking Cancel and
letting it run can take minutes. If I run the same task from the Admin
account there are no problems.

> I saw the messages from someone at MS about using RegMon to try to track the problems. That didn't help me but I did finally get around to looking in
the OS Event - Application log. There are about 10 errrors but the most
important looks like this:
> "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."

> Using Regedit.exe I pulled up that area of the registry and verified that there was no UserData there. When I checked under the Admin account it was.
So in "HKEY_CURRENT_USER\Software\Microsoft\Office\10.0\Common\" I created a
new DWord entry with the title "UserData" and changed the value from 0 to 1.
I also exported these values from the Admin account and imported them into
my user account:
> [HKEY_CURRENT_USER\Software\Microsoft\Office\10.0\Common\UserInfo]
> "UserInitials"=hex:00,00
> "UserName"=hex:00,00
>
> Now it seems to work. Fingers crossed.
Art Wallace - 29 Feb 2004 03:56 GMT
Hi
I think VS.NET is always for "All Users"

I have been trying to figure out why I get this error every time I do a reformat and reinstall and so many others don't. Maybe it's because the user account doesn't exist before the install?
Art Wallace - 29 Feb 2004 03:56 GMT
PS- If anyone at MS is reading, here is another of the errors from the Event log
Detection of product '{E05F0409-0E9A-48A1-AC04-E35E3033604A}', feature 'dotNET_Framework_SDK' failed during request for component '{C763CD13-6E1E-4166-8C78-D274B266E9B6}'

Rate this thread:







Free Magazines

Get these publications absolutely FREE for up to 12 months. There are no hidden fees and no obligation. Simply choose a title, complete the application form and submit it. Read more ...

Oracle MagazineNetwork ComputingComputer WorldBio-IT WorldeWeekInformation WeekInfosecurity
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2008 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.