all groups > visual studio .net setup > january 2004 >
You're in the

visual studio .net setup

group:

vs.net 2003 installation nightmare continues..



vs.net 2003 installation nightmare continues.. varunmathur NO[at]SPAM hotmail.com
1/20/2004 3:00:04 PM
visual studio .net setup: VS.NET 2003 installation nightmare is now three days old..

whenever i run setup.exe (disc1), i get a dialog box which states
"checking product information for system requirements",as soon as the
progress bar reaches the end,the dialog box vanishes,nothing else
happens,just some files appear in *temp*

->vserror71.txt : 'search' couldn't find it on my computer
->vsmsilog**** : 'search' couldn't find any filename containing
vsmsilog
->vsinstall71.txt : this file exists,is in my temp folder and is given
below

->msinterr : given below


here are more details of all the things i've tried to get it
installed:
-> tried the command d:\setup\setup.exe NO_BSLN_CHECK
just copies some files to the temp dir,then nothing happens

-> copied all four disks onto my hard drive,tried running
setup,problem same as before

->tried running vssetup,it says must run setup.exe after a while and
generates some logs

->i have installed all the required prerequisites
separately/manually,and they include : frontpage ext,
setup runtime files,MSIE6sp1(told me i have a newer version of IE6
already),.NET 1.1,J#.NET.
also able to successfully install all 3 MSDN cds

-> about my system : win xp home, p4 1.8ghz,about 6gb of free
space,128mb ram,

-> posted my problem on microsoft.public.vsnet.setup,haven't received
any reply.

-> tried deleting registry entries for visual studio and continuosly
deleting *temp*

->before i bought vs.net,i had downloaded .net redistribitable 1.1
from msdn website

->add/remove programs option doesn't work on my computer(thanks to a
worm which struck windows last year).


thanks

varun

***************MSINTERR.TXT*****************
[Event]
Event1=Setup.exe:GetGlobalCustomProperty({1B3F6DC3-205F-11D3-A824-00C04FB1799F})
Event2=Setup.exe:GetGlobalCustomProperty({383F0141-C682-4665-A69B-756E719C968D})
*********************************************

*************VSINSTALL71.TXT***********************
[01/20/04,11:42:12] Setup.exe:
[01/20/04,11:42:12] Setup.exe: ========== Logging started ==========
[01/20/04,11:42:12] Setup.exe: =====================================
[01/20/04,11:42:12] Setup.exe:
GetGlobalCustomProperty({481CEF9F-033A-11D3-ACE2-00C04F8EEBA1})
[01/20/04,11:42:12] Setup.exe:
GetGlobalCustomProperty(B51015E7-26A5-4c8f-B871-26ABA9BEFB65)
[01/20/04,11:42:12] Setup.exe: entering ISetupManager::RunIntro()
[01/20/04,11:42:12] Setup.exe: LoadSetupDatabase()
[01/20/04,11:42:12] Setup.exe: in InternalRegisterSetupService()
[01/20/04,11:42:12] Setup.exe: in InternalRegisterSetupService()
[01/20/04,11:42:12] Setup.exe: IsRunningUnattended
[01/20/04,11:42:12] Setup.exe: ISetupManager::RunIntro() :
LoadSuiteRequirements
[01/20/04,11:42:12] Setup.exe: ISetupManager::RunIntro() :
CheckSuiteBlocks
[01/20/04,11:42:12] Setup.exe: IsRunningUnattended
[01/20/04,11:42:12] Setup.exe: ISetupManager::RunIntro() :
LoadHelpManager
[01/20/04,11:42:12] Setup.exe: inside ISetupManager::LoadHelpManager()
[01/20/04,11:42:12] Setup.exe: in InternalRegisterSetupService()
[01/20/04,11:42:12] Setup.exe: ISetupManager::RunIntro() :
LoadCommandLineMgr
[01/20/04,11:42:12] Setup.exe: in InternalRegisterSetupService()
[01/20/04,11:42:12] Setup.exe: ISetupManager::LoadCommandLineMgr()
completed
[01/20/04,11:42:12] Setup.exe: ISetupManager::RunIntro() :
LoadSetupLog
[01/20/04,11:42:12] Setup.exe: in InternalRegisterSetupService()
[01/20/04,11:42:12] Setup.exe: ISetupManager::LoadSetupLog() completed
[01/20/04,11:42:12] Setup.exe: ISetupManager::RunIntro() :
LoadManagers
[01/20/04,11:42:12] Setup.exe: inside ISetupManager::LoadUIManager()
[01/20/04,11:42:13] vs70uimgr: Entering InitializeModule() method.
[01/20/04,11:42:13] Setup.exe: in InternalRegisterSetupService()
[01/20/04,11:42:13] Setup.exe: CSetupManager::InstallSetupFiles()
starting
[01/20/04,11:42:13] Setup.exe:
GetGlobalCustomProperty({39E467CB-8962-4AD8-99F9-864AFF183FD4})
[01/20/04,11:42:13] vs70uimgr: Entering ShowSmallProgress() method.
[01/20/04,11:42:13] Setup.exe: IsRunningUnattended
[01/20/04,11:42:13] Setup.exe: IsRunningUnattended
[01/20/04,11:42:13] Setup.exe: IsRunningUnattended
[01/20/04,11:42:13] Setup.exe: IsRunningUnattended
[01/20/04,11:42:13] Setup.exe: IsRunningUnattended
[01/20/04,11:42:14] Setup.exe: IsRunningUnattended
[01/20/04,11:42:14] Setup.exe: IsRunningUnattended
[01/20/04,11:42:14] Setup.exe: IsRunningUnattended
[01/20/04,11:42:14] Setup.exe: IsRunningUnattended
[01/20/04,11:42:14] Setup.exe: IsRunningUnattended
[01/20/04,11:42:14] Setup.exe: IsRunningUnattended
[01/20/04,11:42:14] Setup.exe: IsRunningUnattended
[01/20/04,11:42:14] Setup.exe: IsRunningUnattended
[01/20/04,11:42:14] Setup.exe: IsRunningUnattended
[01/20/04,11:42:14] Setup.exe: IsRunningUnattended
[01/20/04,11:42:15] Setup.exe: IsRunningUnattended
[01/20/04,11:42:15] Setup.exe: IsRunningUnattended
[01/20/04,11:42:15] Setup.exe: IsRunningUnattended
[01/20/04,11:42:15] Setup.exe: IsRunningUnattended
[01/20/04,11:42:15] Setup.exe: IsRunningUnattended
[01/20/04,11:42:15] Setup.exe: IsRunningUnattended
[01/20/04,11:42:15] Setup.exe: IsRunningUnattended
[01/20/04,11:42:15] Setup.exe: IsRunningUnattended
[01/20/04,11:42:16] Setup.exe: IsRunningUnattended
[01/20/04,11:42:16] Setup.exe: IsRunningUnattended
[01/20/04,11:42:16] Setup.exe: IsRunningUnattended
[01/20/04,11:42:16] Setup.exe: IsRunningUnattended
[01/20/04,11:42:16] Setup.exe: IsRunningUnattended
[01/20/04,11:42:16] Setup.exe: IsRunningUnattended
[01/20/04,11:42:16] Setup.exe: IsRunningUnattended
[01/20/04,11:42:16] Setup.exe: IsRunningUnattended
[01/20/04,11:42:16] Setup.exe: IsRunningUnattended
[01/20/04,11:42:16] Setup.exe: IsRunningUnattended
[01/20/04,11:42:17] Setup.exe: IsRunningUnattended
[01/20/04,11:42:17] Setup.exe: IsRunningUnattended
[01/20/04,11:42:17] Setup.exe: IsRunningUnattended
[01/20/04,11:42:17] Setup.exe: IsRunningUnattended
[01/20/04,11:42:17] Setup.exe: IsRunningUnattended
[01/20/04,11:42:17] Setup.exe: IsRunningUnattended
[01/20/04,11:42:17] Setup.exe: IsRunningUnattended
[01/20/04,11:42:17] Setup.exe: IsRunningUnattended
[01/20/04,11:42:17] Setup.exe: IsRunningUnattended
[01/20/04,11:42:17] Setup.exe: IsRunningUnattended
[01/20/04,11:42:17] Setup.exe: IsRunningUnattended
[01/20/04,11:42:17] Setup.exe: IsRunningUnattended
[01/20/04,11:42:17] Setup.exe: IsRunningUnattended
[01/20/04,11:42:17] Setup.exe: IsRunningUnattended
[01/20/04,11:42:18] Setup.exe: IsRunningUnattended
[01/20/04,11:42:18] Setup.exe: IsRunningUnattended
[01/20/04,11:42:18] Setup.exe: IsRunningUnattended
[01/20/04,11:42:18] Setup.exe: IsRunningUnattended
[01/20/04,11:42:18] Setup.exe: IsRunningUnattended
[01/20/04,11:42:18] Setup.exe: IsRunningUnattended
[01/20/04,11:42:18] Setup.exe: IsRunningUnattended
[01/20/04,11:42:18] Setup.exe: IsRunningUnattended
[01/20/04,11:42:18] Setup.exe: IsRunningUnattended
Re: vs.net 2003 installation nightmare continues.. Peter van der Goes
1/20/2004 5:25:26 PM

[quoted text, click to view]
<snip>

Your last statement speaks volumes to me.
Your system was infected and not fully restored. Under those circumstances,
I'd be strongly considering formatting my OS partition (perhaps the entire
drive) and reinstalling my OS from scratch. Bottom line: if Add/Remove
Programs doesn't work, who knows what else is wrong that you cannot see?
As installing Visual Studio .NET 2003 has been a remarkably trouble-free
exercise for us in several classrooms and labs, I can only think it's your
system.

--
Peter [MVP Academic]


Re: vs.net 2003 installation nightmare continues.. varunmathur NO[at]SPAM hotmail.com
1/20/2004 8:07:07 PM
thanks for your post.

as regards add/remove program not working,it's the link to it that
doesn't work,as does for most other programs on the system such as
IE..etc...etc. I've been working around the problem by right-clicking
and selecting *run-as*,and then the app launches perfectly....and i'm
not able to get add/remove to work in this way cause right-clicking on
it doesn't present the option of selecting *run-as*. Always get
missing rundll error.

Anyways,this has been going on since Feb 2002,and i've been able to
install/uninstall all sorts of applications and run every program on
the system except those in the control panel(with the exception of
admn tasks). Besides,I was also able to install the prerequisites.

Re-installing the OS would probably cause me to either lose some data
or require enormous shifting of data....which isn't an option at
all.So either i get this VS.NET installed w/out major changes to the
system or i return the almost dozen .net books i borrowed from the
library,get a refund and forget about .net altogether and go back to
java and the ilk (it still works on my system) and might as well pick
up a copy of lindows from the same university bookstore that sold me
VS.NET Academic.

varun


[quoted text, click to view]
Re: vs.net 2003 installation nightmare continues.. varunmathur NO[at]SPAM hotmail.com
1/21/2004 8:03:42 PM
problem resolved;setup of VS.NET 2003 Academic successful.

a worm (some 'yaha' variant) which infected my computer last year had
changed some registry setting because of which my vs.net setup was not
starting properly.i tracked activity through filemon and rectified the
problem by using a yaha-killer tool provided by f-secure (god bless
them). setup went smoothly and even the earlier problem which i
mentioned (of not being able to directly open files) is now resolved.
MS support was incredible.

thanks

Re: vs.net 2003 installation nightmare continues.. Peter van der Goes
1/22/2004 9:14:20 AM

[quoted text, click to view]

Glad to hear you finally got it installed, Varun!
Have fun with Visual Studio .NET.

--
Peter [MVP Academic]

Re: vs.net 2003 installation nightmare continues.. timmac NO[at]SPAM online.microsoft.com
1/23/2004 8:45:42 PM
Hello

First, I would agree with Peter. If your machine has not fully been
cleaned from the Worm that hit your machine from 2002, I would strongly
recommend to format and reinstall. The reason is, that there still could
be files that are infected and may be causing other issues.

Something to think about, is that right now you have the opportunity to
shift your data to backup and then format and reinstall, where, you may run
into an issue of the machine crashing and you not being able to shift your
data to backup.


1. What operating system are you installing VS.Net 2003?
2. What happens if you double click on the Setup.Exe file, do you receive
the same behavior or do you receive an error message?
3. If you are using Windows XP, what happens, if you clean boot the machine
and then execute the installation?

Here are some Microsoft Knowledge Base articles that may assist you.

319714 HOW TO: Troubleshoot Visual Studio .NET Installation
http://support.microsoft.com/?id=319714

180129 Cannot Disable Shortcuts in StartUp Folder Using Msconfig Tool
http://support.microsoft.com/?id=180129

281770 How to Perform Clean-Boot Troubleshooting for Windows 2000
http://support.microsoft.com/?id=281770

310353 How to Perform a Clean Boot in Windows XP
http://support.microsoft.com/?id=310353

Tim Macaulay, MCSD
Microsoft Visual Studio Setup & Deployment

This posting is "AS IS" with no warranties, and confers no rights.
AddThis Social Bookmark Button