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 / June 2004

Tip: Looking for answers? Try searching our database.

VS.NET 2003 Enterpise Architect and MSDN Library

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
Eric - 18 May 2004 14:34 GMT
Hi,

Strange behavior.
I have installed VS.NET and MSDN. I have for my VS.NET the MSDN as external
help configured.

All has worked fine until (I think) I changed my user profile on the
computer.
Now when I click a title in MSDN library, the Windows Installer for VS.NET
get started and I must insert the VS.NET DVD to complete the installation.
But this does not solve the problem. The installer starts the next time
again.

But also when I press cancel, the MSDN works fine. I have no idea, what he
tries to install or fix.

Do I need to make new complete installation?

Thanks
Eric
Felix Wang - 19 May 2004 10:54 GMT
Hello Eric,

Thanks for posting. To track this issue, you can open the application event
log and see what component and feature is triggering the reparation of
MSDN. You may post related application event log entries here.

Alternatively, you may also try removing the current installation of MSDN
and reinstall it with the current user account.

Regards,

Felix Wang
Microsoft Online Partner Support
Signature

Get Secure! - www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.

Eric - 19 May 2004 11:22 GMT
> Thanks for posting. To track this issue, you can open the application event
> log and see what component and feature is triggering the reparation of
> MSDN. You may post related application event log entries here.
Of course, forgot to look at it. Here's the message:

Event Type: Warning
Event Source: MsiInstaller
Event Category: None
Event ID: 1004
Date:  18.05.2004
Time:  15:26:05
User:  N/A
Computer: SARASOTA
Description:
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.

Event Type: Warning
Event Source: MsiInstaller
Event Category: None
Event ID: 1001
Date:  18.05.2004
Time:  15:26:05
User:  N/A
Computer: SARASOTA
Description:
Detection of product '{E05F0409-0E9A-48A1-AC04-E35E3033604A}', feature
'dotNET_Framework_SDK' failed during request for component
'{C763CD13-6E1E-4166-8C78-D274B266E9B6}'

But why he need this resource? And what is this exactly?
If have Office 2003 installed (Office11).

> Alternatively, you may also try removing the current installation of MSDN
> and reinstall it with the current user account.
This one doesn't work
Felix Wang - 20 May 2004 12:50 GMT
Hi Eric,

Thanks for your update. As far as the first entry is concerned, the
component "{C763CD13-6E1E-4166-8C78-D274B266E9B6}" has a keypath in
registry. Let's try creating the following key:

HKEY_CURRENT_USER\Software\Microsoft\Office\10.0\Common\UserData

The type of the key is REG_DWORD. The value is 1.

As far as the second entry is concerned, the component
"{C763CD13-6E1E-4166-8C78-D274B266E9B6}" has a keypath with file
"CookDoc.dll". Let's try the following to fix the second issue:

1. Search for the file "CookDoc.dll" on your system. By default, it should
be in the following folder:
C:\Program Files\Common Files\Microsoft Shared\MSDN
2. Open a command line interface (by running "cmd.exe") and issue the
following command:
RegSvr32 "C:\Program Files\Common Files\Microsoft Shared\MSDN\CookDoc.dll"
Here we need to use the quotation marks to quote the full path towards the
DLL.
3. Normally we should be able to see the prompt like the following. If not,
please let me know the error message.
DllRegisterServer in c:\program files\Common Files\Microsoft
Shared\MSDN\CookDoc.dll succeeded.

Please give it a try and see whether these help to resolve the issue. If
the problem still persists, you may open the application event log and see
whether we have eliminated one of the 2 causes.

Regards,

Felix Wang
Microsoft Online Partner Support
Signature

Get Secure! - www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.

Eric - 31 May 2004 12:29 GMT
Hi Felix,

Thank you very much.
It seems to work. Great support.

Eric
Felix Wang - 01 Jun 2004 02:13 GMT
Hello Eric,

Thanks for your feedback. I am glad to hear my suggestion helps. Please
feel free to post here if you have any further concerns.

Have a nice day.

Regards,

Felix Wang
Microsoft Online Partner Support
Signature

Get Secure! - www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.


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.