I was hoping to get some general help with a problem I am having with deploying Visual Studio 2008 Pro using SMS 2003. Going by the posts I found on this site and other places it was recommended to install .NET 3.5 SP1, Document Explorer 2007, and Web Designer Tools first and then VS 2008 Pro. So, the machines in question have Visual Studio 2005 Pro installed on them so I created scripts to pull this out through SMS and reboot the machines and this part works fine. The machines already have .NET 3.5 SP1 installed so I install Document Explorer and Web Designer Tools and these go in fine and then I get a failure through SMS when installing VS 2008, if I use 'setup.exe /q /norestart /full' (from the '\setup' folder and not the root) I get error 1603 and if I use a VB Script with the same command I get error 1. Here's the thing, VS 2008 installs, launches and works. I can remove it, install it again manually, and I had some users test a few of my test machines and everything seems to work fine.

I am new at this so how would you recommend I go about properly logging this so I know exactly what is failing so I can correct this. I don't know if this error is simply related to the machine needing a reboot or if there is a problem with the install itself. After VS 2008 is installed I would also like to install Service Pack 1 and MSDN but the failed install is making we wonder where the problem is.

I used the information from these threads basically to install this...


What would you suggest I do to find out where the problem is? Is there a way to log this to see what is failing on the install?

Thanks for any help or input.
0 Comments   [ + ] Show 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.


You'll find AppDeploy's 'Package KB' to be most useful. Always try to use it before posting. In this article, open the 'Notes' section. You'll find the first set most useful. It includes the logging switch syntax.
Answered 01/14/2010 by: VBScab
Red Belt

Please log in to comment
Thanks for the reply, the link you posted is pointing to Imaging so I don't think this is going to help. I did look at the Package KB which I linked to above and I did use the install strings posted there but the install is not completing properly. I found some log files and I can see that it is stopping while trying to install 'Windows Mobile 5.0 SDK R2 for Pocket PC'...

MSI (s) (88:88) [15:53:40:217]: Note: 1: 1708
MSI (s) (88:88) [15:53:40:217]: Product: Windows Mobile 5.0 SDK R2 for Pocket PC -- Installation operation failed.

MSI (s) (88:88) [15:53:40:232]: Cleaning up uninstalled install packages, if any exist
MSI (s) (88:88) [15:53:40:232]: MainEngineThread is returning 1603
MSI (s) (88:EC) [15:53:40:342]: Destroying RemoteAPI object.
MSI (s) (88:D8) [15:53:40:342]: Custom Action Manager thread ending.
=== Logging stopped: 1/13/2010 15:53:40 ===
MSI (c) (00:98) [15:53:40:357]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied. Counter after decrement: -1
MSI (c) (00:98) [15:53:40:357]: MainEngineThread is returning 1603
=== Verbose logging stopped: 1/13/2010 15:53:40 ===

I found this in the VSSWMSISummary.txt log file so it would be good to know what log files are created so I can look further into this issue. I checked the machine and comapred it to one that I did a manual upgrade on and it is missing a number of SDK's so it looks like the install stopped well before it was done even though it seems to work fine. I found this link that I will need to check on and see if this has any useful information... http://social.msdn.microsoft.com/Forums/en/windowssdk/thread/006edcd4-888d-4b95-8454-9651dc298390 When I install this manually everything seems to install so I don't think there is a oribkem with the files on my server, it looks like there is an issue with setup and the configuration of my machines.

Thanks again for the input.
Answered 01/14/2010 by: Deploy_Guy
Yellow Belt

Please log in to comment
Sorry about that gash link! Looks like I had something lurking in my clipboard. I've corrected it for posterity's sake.

Anyway, if you used the command lines shown in that KB article, there'll be a verbose log in C:\VS_SETUP.LOG.
Answered 01/15/2010 by: VBScab
Red Belt

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