Ok..this install is driving me nuts. We started out building the .ini to install using the /unattendfile switch. Everytime we launch it with the switch, it gets part of the way through the install and then bombs out (watching the progress on the task manager) with an error 1603. Curious, we run the install manually on the same machine, no errors.

So, we try just using the /q /full switches inherent to the setup.exe.....fails on deployment again, same error (1603). Install manually again, no problems.

Figuring maybe it's just this machine that has issues, i've tried on 3 others - same result.

Basically, everything I try to do to make this run silently fails, whether it's with the /q, /q /full, /unattendfile - but running it manually installs just fine. I've even resorted to trying to hack my way around the MSI to force it to run without much luck. The setup.exe offers you the option to build a transform...but it doesnt seem to work with the msi either! Tried running this install as the system account, regular user account and domain user accounts...same result for all.

Tell me someone has seen this before and can point us in the right direction!!!


****
update:

in the dd_error_vs_vstdcore_90 log, was this line:

[06/13/08,13:42:33] setup.exe: [2] ISetupComponent::Pre/Post/Install() failed in ISetupManager::InternalInstallManager() with HRESULT -2147023293.

that -2147023293 is a very generic failure error...no idea what is causing it, so not sure if it's much of a help. i've even seen that display when things have been successful.
****


****
another update:

found the 1603 error in the install_vs_nstdcore_90 log - twice...strange.

[06/13/08,13:42:33] Setup.exe: GetGlobalCustomProperty - Property: {092114C2-997D-4D68-8F3A-8BC2584FD23B} - PropertyName: Quiet Mode Setup - Value:
[06/13/08,13:42:33] Setup.exe: ERROR (non critical): Suite Main Directory:C:\Program Files\Microsoft Visual Studio 9.0\Microsoft Visual Studio Team System 2008 Development Edition - ENU does not exists. Log files will not be copied in the suite directory!
[06/13/08,13:42:33] Setup.exe: GetGlobalCustomProperty - Property: {383F0141-C682-4665-A69B-756E719C968D} - PropertyName: Process Return Code - Value: 1603
[06/13/08,13:42:33] Setup.exe: GetGlobalCustomProperty - Property: {BBE1827C-F2FD-4FDA-A6D6-C83B62FFFDCA} - PropertyName: compfailed - Value: 1


and


[06/13/08,13:42:34] UTILS::RunNGENAction: Started
[06/13/08,13:42:34] UTILS::RunNGENAction: starting "C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\ngen.exe queue continue"
[06/13/08,13:42:34] UTILS::RunNGENAction: ngen.exe returned 0
[06/13/08,13:42:34] Setup.exe: GetGlobalCustomProperty - Property: {383F0141-C682-4665-A69B-756E719C968D} - PropertyName: Process Return Code - Value: 1603
[06/13/08,13:42:34] Setup.exe: SETUP EXIT CODE - 1603
[06/13/08,13:42:34] End_Session:


obviously it's saying it failed on the .NET2.0 setup....which makes no sense because .NET 2.0 is already installed on the machine. the bigger questions are:

-why is it trying to reinstall something thats already there?
-why does this not cause a failure when running manually???

****
0 Comments   [ + ] Show Comments

Comments

Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

Answers


Please log in to comment
0
Thanks for the reply...

The machines i've been testing on have 1GB of RAM, and i've checked the logs looking for similar errors with unpacking the files but have found nothing similar to whats posted in that thread unfortunately.

The main culprit looks to be the second piece of the log I posted regarding .NET 2.0, but I havent managed to sort that out yet.
Answered 06/13/2008 by: RichC
Senior Yellow Belt

Please log in to comment
0
Could it be that VS2008 requires .NET 3.5?

Maybe you can find something at http://forums.msdn.microsoft.com/ru-RU/vssetup/thread/1c2426b5-2faa-4d6e-885b-9a3251c14042/

Try to do a search on any of these blogs:
http://blogs.msdn.com/aaronru/default.aspx
http://blogs.msdn.com/heaths/default.aspx
Answered 06/13/2008 by: AngelD
Red Belt

Please log in to comment
0
It does require .NET 3.5.....and it installs it automatically itself when you do a manual install. However, if you try to run it silently in any way, shape or form it seems to bomb out on the .NET installs/prereqs. I just don't get it. I'm at a loss. I will check out that link though....
Answered 06/13/2008 by: RichC
Senior Yellow Belt

Please log in to comment
0
Still no luck. I can get the .NET framework 3.5 preinstalled now, but Visual Studio still fails with a 1603 error doing something with .NET. This makes zero sense to me, and i've been reading blogs and notes online for about 2 weeks and have made very little progress considering i'm still getting the same error I started with. I've even tried pulling off all the .NET versions and using the MS cleanup tool for .NET to clear out everything...install 3.5, and get the same error once I try to install VS.

In the 4 years or so i've been doing packaging, i've come across some odd installs and errors, but this really takes the cake. None of the 5 or 6 solutions i've consistently found online seem to have worked, nor does any combination of tactics i've tried.

Hopefully someone out there is having these issues as well.
Answered 06/17/2008 by: RichC
Senior Yellow Belt

Please log in to comment
0
How about asking at the provided blogs above, the Microsoft forum or directly contact Microsoft?
Answered 06/17/2008 by: AngelD
Red Belt

Please log in to comment
0
I've actually got open posts on 2 different VS2008 blogs on MSDN as well. Covering my bases as best I can [;)]
Answered 06/17/2008 by: RichC
Senior Yellow Belt

Please log in to comment
0
Great, please post back any feedback you get.
Answered 06/17/2008 by: AngelD
Red Belt

Please log in to comment
0
I am getting the same result here. Please post back your findings! I'll look into it aswell.
Answered 06/23/2008 by: jaybot
Senior Yellow Belt

Please log in to comment
0
I had similar issues, but different to yours. You could try the below from Aaron stebner's blog, editing the ini file helped my issue. and since you already have dotnet2 installed, it might help yours. (even though it says VS2005, this applies to VS2008 also)


http://blogs.msdn.com/astebner/archive/2006/03/17/554248.aspx

http://support.microsoft.com/?kbid=913445
Answered 07/15/2008 by: reds4eva
Second Degree Blue Belt

Please log in to comment
Answer this question or Comment on this question for clarity