| Groups | Blog | Home |
visual studio .net setup : Exit Code 1603 When Setting Up Visual Studio .NET 2003 Using SMS
1603 is a very generic error and it means 'Fatal error during installation.' To get exact message yu will have to look into VS setup log which is created in %TEMP% folder. Hope this helps. -- This posting is provided "AS IS" with no warranties, and confers no rights. [quoted text, click to view] "Paul Anderson" <paul.anderson@eaifhe.REMOVE_NOSPAM.ac.uk> wrote in message news:OxmgZCsCFHA.2156@TK2MSFTNGP10.phx.gbl... >I am setting up Visual Studio .NET 2003 using SMS by following this >Microsoft article: > > http://support.microsoft.com/default.aspx?scid=kb;en-us;327792 : "How to > deploy Visual Studio .NET 2003 by using Systems Management Server" > > I've created the collections, packages, programs and advertisements for > the prerequisites and the main application suite. However, although the > prerequisites deploy without a glitch, something strange is happening when > I deploy the main suite - Visual Studio .NET. > > As soon as the advertised program starts to run, the exit code 1603 is > returned to SMS and the following message appears in the advertisement > status. > > "The program for advertisement "NEW2008C" failed ("NEW0006C" - "Microsoft > Visual Studio .NET 2003"). A failure exit code of 1603 was returned. > User context: NT AUTHORITY\SYSTEM > > Possible cause: Systems Management Server (SMS) determines status for each > program it executes. If SMS cannot find or correlate any installation > status Management Information Format (MIF) files for the program, it uses > the program's exit code to determine status. An exit code of 1603 is > considered a failure. > Solution: For more information on the exit code, refer to the > documentation for the program you are distributing." > > However, the strange thing is the setup process on the client continues > and, after the msiexec.exe process closes, I can run VS.NET. It loads > without error. If I go into the Control Panel and open the Run Advertised > Programs applet, VS .NET shows as failed. > > I'm deploying VS.NET for a large number of users and want to be able to > verify that each deployment is completely successful. This exit code > indicates failure, but gives no more information. I'm not familiar with > using VS.NET, so can't thoroughly test it. Also, I'm new to SMS and am > still learning the ropes. I'd really appreciate some help on this one :) > > Here's the detail: > > Client O/S: Windows XP Pro SP2 > SMS server o/s: Windows Server 2003 > SMS version: 2.50.3174.1000 > Visual Studio .NET MSDE version 7.1.3088 > > I've double-checked the advertised program and tried specifying the vs.ini > file using the default folder (vs.ini), the setup folder (setup\vs.ini) > and the fully qualified UNC path (as given below) and all produce the same > result: > > smswrapper.exe setup\setup.exe /unattendfile > "\\campus\software$\microsoft\Visual Studio.net > 2003\VS72003\VS\Setup\vs.ini" /no_bsln_check > > I've searched the Net and found that exit code 1603 is an unspecified > failure. Has anyone else experienced this problem ? Can you help me out > as an SMS newbie ? > > Thanks. > > -- > Paul Anderson > IT Support > East Antrim Institute of Further & Higher Education > >
I am setting up Visual Studio .NET 2003 using SMS by following this
Microsoft article: http://support.microsoft.com/default.aspx?scid=kb;en-us;327792 : "How to deploy Visual Studio .NET 2003 by using Systems Management Server" I've created the collections, packages, programs and advertisements for the prerequisites and the main application suite. However, although the prerequisites deploy without a glitch, something strange is happening when I deploy the main suite - Visual Studio .NET. As soon as the advertised program starts to run, the exit code 1603 is returned to SMS and the following message appears in the advertisement status. "The program for advertisement "NEW2008C" failed ("NEW0006C" - "Microsoft Visual Studio .NET 2003"). A failure exit code of 1603 was returned. User context: NT AUTHORITY\SYSTEM Possible cause: Systems Management Server (SMS) determines status for each program it executes. If SMS cannot find or correlate any installation status Management Information Format (MIF) files for the program, it uses the program's exit code to determine status. An exit code of 1603 is considered a failure. Solution: For more information on the exit code, refer to the documentation for the program you are distributing." However, the strange thing is the setup process on the client continues and, after the msiexec.exe process closes, I can run VS.NET. It loads without error. If I go into the Control Panel and open the Run Advertised Programs applet, VS .NET shows as failed. I'm deploying VS.NET for a large number of users and want to be able to verify that each deployment is completely successful. This exit code indicates failure, but gives no more information. I'm not familiar with using VS.NET, so can't thoroughly test it. Also, I'm new to SMS and am still learning the ropes. I'd really appreciate some help on this one :) Here's the detail: Client O/S: Windows XP Pro SP2 SMS server o/s: Windows Server 2003 SMS version: 2.50.3174.1000 Visual Studio .NET MSDE version 7.1.3088 I've double-checked the advertised program and tried specifying the vs.ini file using the default folder (vs.ini), the setup folder (setup\vs.ini) and the fully qualified UNC path (as given below) and all produce the same result: smswrapper.exe setup\setup.exe /unattendfile "\\campus\software$\microsoft\Visual Studio.net 2003\VS72003\VS\Setup\vs.ini" /no_bsln_check I've searched the Net and found that exit code 1603 is an unspecified failure. Has anyone else experienced this problem ? Can you help me out as an SMS newbie ? Thanks. -- Paul Anderson IT Support East Antrim Institute of Further & Higher Education
Thanks for your prompt response, Shehzad.
This log shows that an error code of zero is being returned, which doesn't surprise me as the install process doesn't seem to be terminated prematurely. I think what is happening is smswrapper.exe is starting, kicking off setup.exe and immediately closing with exit code 1603, before setup.exe finishes. I suspect that the exit code 1603 is being returned by smswrapper.exe and not setup.exe. It's certainly being reported in SMS right at the beginning of the install process, long before the installation finishes on the client. I haven't been able to find any documentation or troubleshooting info on smswrapper.exe anywhere so far. Can you help ? Many thanks. [quoted text, click to view] "Shehzad Khoja [MSFT]" <srkhoja@online.microsoft.com> wrote in message news:OfA1kmtCFHA.2884@TK2MSFTNGP15.phx.gbl... > Hi Paul > > 1603 is a very generic error and it means 'Fatal error during > installation.' To get exact message yu will have to look into VS setup log > which is created in %TEMP% folder. > > Hope this helps. > > -- > This posting is provided "AS IS" with no warranties, and confers no > rights. > > > "Paul Anderson" <paul.anderson@eaifhe.REMOVE_NOSPAM.ac.uk> wrote in > message news:OxmgZCsCFHA.2156@TK2MSFTNGP10.phx.gbl... >>I am setting up Visual Studio .NET 2003 using SMS by following this >>Microsoft article: >> >> http://support.microsoft.com/default.aspx?scid=kb;en-us;327792 : "How to >> deploy Visual Studio .NET 2003 by using Systems Management Server" >> >> I've created the collections, packages, programs and advertisements for >> the prerequisites and the main application suite. However, although the >> prerequisites deploy without a glitch, something strange is happening >> when I deploy the main suite - Visual Studio .NET. >> >> As soon as the advertised program starts to run, the exit code 1603 is >> returned to SMS and the following message appears in the advertisement >> status. >> >> "The program for advertisement "NEW2008C" failed ("NEW0006C" - "Microsoft >> Visual Studio .NET 2003"). A failure exit code of 1603 was returned. >> User context: NT AUTHORITY\SYSTEM >> >> Possible cause: Systems Management Server (SMS) determines status for >> each program it executes. If SMS cannot find or correlate any >> installation status Management Information Format (MIF) files for the >> program, it uses the program's exit code to determine status. An exit >> code of 1603 is considered a failure. >> Solution: For more information on the exit code, refer to the >> documentation for the program you are distributing." >> >> However, the strange thing is the setup process on the client continues >> and, after the msiexec.exe process closes, I can run VS.NET. It loads >> without error. If I go into the Control Panel and open the Run >> Advertised Programs applet, VS .NET shows as failed. >> >> I'm deploying VS.NET for a large number of users and want to be able to >> verify that each deployment is completely successful. This exit code >> indicates failure, but gives no more information. I'm not familiar with >> using VS.NET, so can't thoroughly test it. Also, I'm new to SMS and am >> still learning the ropes. I'd really appreciate some help on this one :) >> >> Here's the detail: >> >> Client O/S: Windows XP Pro SP2 >> SMS server o/s: Windows Server 2003 >> SMS version: 2.50.3174.1000 >> Visual Studio .NET MSDE version 7.1.3088 >> >> I've double-checked the advertised program and tried specifying the >> vs.ini file using the default folder (vs.ini), the setup folder >> (setup\vs.ini) and the fully qualified UNC path (as given below) and all >> produce the same result: >> >> smswrapper.exe setup\setup.exe /unattendfile >> "\\campus\software$\microsoft\Visual Studio.net >> 2003\VS72003\VS\Setup\vs.ini" /no_bsln_check >> >> I've searched the Net and found that exit code 1603 is an unspecified >> failure. Has anyone else experienced this problem ? Can you help me out >> as an SMS newbie ? >> >> Thanks. >> >> -- >> Paul Anderson >> IT Support >> East Antrim Institute of Further & Higher Education >> >> > >
The exit code is being returned right at the start of the setup process.
Setup.exe continues to run and Visual Studio can be started once it finishes, however, as I'm not a programmer I can't verify that everything is installed properly. Does this indicate a failure or not ? VSInstall71.log contains the following line: [02/10/05,13:33:48] Visual Studio .NET Professional 2003 - English: MsiInstallProduct return code: 0. This, however, is by no means the last entry - there are dozens after it and the last entry occurs a minute and a half after this one. How do I get SMS to correctly report success or failure with reason ? [quoted text, click to view] "Paul Anderson" <paul.anderson@eaifhe.REMOVE_NOSPAM.ac.uk> wrote in message news:uzvF9yfDFHA.148@TK2MSFTNGP14.phx.gbl... > Thanks for your prompt response, Shehzad. > > This log shows that an error code of zero is being returned, which doesn't > surprise me as the install process doesn't seem to be terminated > prematurely. > > I think what is happening is smswrapper.exe is starting, kicking off > setup.exe and immediately closing with exit code 1603, before setup.exe > finishes. I suspect that the exit code 1603 is being returned by > smswrapper.exe and not setup.exe. It's certainly being reported in SMS > right at the beginning of the install process, long before the > installation finishes on the client. > > I haven't been able to find any documentation or troubleshooting info on > smswrapper.exe anywhere so far. Can you help ? > > Many thanks. > > > > "Shehzad Khoja [MSFT]" <srkhoja@online.microsoft.com> wrote in message > news:OfA1kmtCFHA.2884@TK2MSFTNGP15.phx.gbl... >> Hi Paul >> >> 1603 is a very generic error and it means 'Fatal error during >> installation.' To get exact message yu will have to look into VS setup >> log which is created in %TEMP% folder. >> >> Hope this helps. >> >> -- >> This posting is provided "AS IS" with no warranties, and confers no >> rights. >> >> >> "Paul Anderson" <paul.anderson@eaifhe.REMOVE_NOSPAM.ac.uk> wrote in >> message news:OxmgZCsCFHA.2156@TK2MSFTNGP10.phx.gbl... >>>I am setting up Visual Studio .NET 2003 using SMS by following this >>>Microsoft article: >>> >>> http://support.microsoft.com/default.aspx?scid=kb;en-us;327792 : "How to >>> deploy Visual Studio .NET 2003 by using Systems Management Server" >>> >>> I've created the collections, packages, programs and advertisements for >>> the prerequisites and the main application suite. However, although the >>> prerequisites deploy without a glitch, something strange is happening >>> when I deploy the main suite - Visual Studio .NET. >>> >>> As soon as the advertised program starts to run, the exit code 1603 is >>> returned to SMS and the following message appears in the advertisement >>> status. >>> >>> "The program for advertisement "NEW2008C" failed ("NEW0006C" - >>> "Microsoft Visual Studio .NET 2003"). A failure exit code of 1603 was >>> returned. >>> User context: NT AUTHORITY\SYSTEM >>> >>> Possible cause: Systems Management Server (SMS) determines status for >>> each program it executes. If SMS cannot find or correlate any >>> installation status Management Information Format (MIF) files for the >>> program, it uses the program's exit code to determine status. An exit >>> code of 1603 is considered a failure. >>> Solution: For more information on the exit code, refer to the >>> documentation for the program you are distributing." >>> >>> However, the strange thing is the setup process on the client continues >>> and, after the msiexec.exe process closes, I can run VS.NET. It loads >>> without error. If I go into the Control Panel and open the Run >>> Advertised Programs applet, VS .NET shows as failed. >>> >>> I'm deploying VS.NET for a large number of users and want to be able to >>> verify that each deployment is completely successful. This exit code >>> indicates failure, but gives no more information. I'm not familiar with >>> using VS.NET, so can't thoroughly test it. Also, I'm new to SMS and am >>> still learning the ropes. I'd really appreciate some help on this one >>> :) >>> >>> Here's the detail: >>> >>> Client O/S: Windows XP Pro SP2 >>> SMS server o/s: Windows Server 2003 >>> SMS version: 2.50.3174.1000 >>> Visual Studio .NET MSDE version 7.1.3088 >>> >>> I've double-checked the advertised program and tried specifying the >>> vs.ini file using the default folder (vs.ini), the setup folder >>> (setup\vs.ini) and the fully qualified UNC path (as given below) and all >>> produce the same result: >>> >>> smswrapper.exe setup\setup.exe /unattendfile >>> "\\campus\software$\microsoft\Visual Studio.net >>> 2003\VS72003\VS\Setup\vs.ini" /no_bsln_check >>> >>> I've searched the Net and found that exit code 1603 is an unspecified >>> failure. Has anyone else experienced this problem ? Can you help me >>> out as an SMS newbie ? >>> >>> Thanks. >>> >>> -- >>> Paul Anderson >>> IT Support >>> East Antrim Institute of Further & Higher Education >>> >>> >> >> > >
Shehzad,
We're still experiencing this problem (see other posts). Can you help at all ? The problem seems to be with smswrapper.exe. [quoted text, click to view] "Shehzad Khoja [MSFT]" <srkhoja@online.microsoft.com> wrote in message news:OfA1kmtCFHA.2884@TK2MSFTNGP15.phx.gbl... > Hi Paul > > 1603 is a very generic error and it means 'Fatal error during > installation.' To get exact message yu will have to look into VS setup log > which is created in %TEMP% folder. > > Hope this helps. > > -- > This posting is provided "AS IS" with no warranties, and confers no > rights. > > > "Paul Anderson" <paul.anderson@eaifhe.REMOVE_NOSPAM.ac.uk> wrote in > message news:OxmgZCsCFHA.2156@TK2MSFTNGP10.phx.gbl... >>I am setting up Visual Studio .NET 2003 using SMS by following this >>Microsoft article: >> >> http://support.microsoft.com/default.aspx?scid=kb;en-us;327792 : "How to >> deploy Visual Studio .NET 2003 by using Systems Management Server" >> >> I've created the collections, packages, programs and advertisements for >> the prerequisites and the main application suite. However, although the >> prerequisites deploy without a glitch, something strange is happening >> when I deploy the main suite - Visual Studio .NET. >> >> As soon as the advertised program starts to run, the exit code 1603 is >> returned to SMS and the following message appears in the advertisement >> status. >> >> "The program for advertisement "NEW2008C" failed ("NEW0006C" - "Microsoft >> Visual Studio .NET 2003"). A failure exit code of 1603 was returned. >> User context: NT AUTHORITY\SYSTEM >> >> Possible cause: Systems Management Server (SMS) determines status for >> each program it executes. If SMS cannot find or correlate any >> installation status Management Information Format (MIF) files for the >> program, it uses the program's exit code to determine status. An exit >> code of 1603 is considered a failure. >> Solution: For more information on the exit code, refer to the >> documentation for the program you are distributing." >> >> However, the strange thing is the setup process on the client continues >> and, after the msiexec.exe process closes, I can run VS.NET. It loads >> without error. If I go into the Control Panel and open the Run >> Advertised Programs applet, VS .NET shows as failed. >> >> I'm deploying VS.NET for a large number of users and want to be able to >> verify that each deployment is completely successful. This exit code >> indicates failure, but gives no more information. I'm not familiar with >> using VS.NET, so can't thoroughly test it. Also, I'm new to SMS and am >> still learning the ropes. I'd really appreciate some help on this one :) >> >> Here's the detail: >> >> Client O/S: Windows XP Pro SP2 >> SMS server o/s: Windows Server 2003 >> SMS version: 2.50.3174.1000 >> Visual Studio .NET MSDE version 7.1.3088 >> >> I've double-checked the advertised program and tried specifying the >> vs.ini file using the default folder (vs.ini), the setup folder >> (setup\vs.ini) and the fully qualified UNC path (as given below) and all >> produce the same result: >> >> smswrapper.exe setup\setup.exe /unattendfile >> "\\campus\software$\microsoft\Visual Studio.net >> 2003\VS72003\VS\Setup\vs.ini" /no_bsln_check >> >> I've searched the Net and found that exit code 1603 is an unspecified >> failure. Has anyone else experienced this problem ? Can you help me out >> as an SMS newbie ? >> >> Thanks. >> >> -- >> Paul Anderson >> IT Support >> East Antrim Institute of Further & Higher Education >> >> > >
i need help with installing msn messeger 6.2 it gives me a error 1603 and i need it now how do i get rid of the error
From http://www.developmentnow.com/g/58_2005_2_0_0_58796/Re_Exit_Code_1603_When_Setting_Up_Visual_Studio__NET_2003_Using_SMS.htm Posted via DevelopmentNow Groups www.developmentnow.com/g
Paul, Have you found a solution to this problem? I am experiencing the
same exact thing and, so far, yours is the only post I have found on the web regarding the issue. Since you are about a month ahead of me on this, any assistance would be appreciated. Thanks... --
No Laurie, I haven't.
I'm on the brink of giving up. Microsoft haven't really provided me with anything substantial here. Basically, I don't even know if the setup is working or not as SMSWrapper.exe isn't passing back any more information than 1603. I'm not the end user, so I don't know if the VS setup is satisfactory - all I know is it opens and the suite apps run. The whole idea of SMS is that you get feedback on the status of a deployment, only here you don't. I've scoured the web and various newsgroups and forums and although there are others like ourselves, MS are being unhelpful. Let me know if you have any luck yourself. "Laurie Wilcox via DotNetMonster.com" <forum@DotNetMonster.com> wrote in message news:22e8fdecd57e4e8fa15416823caedac2@DotNetMonster.com... [quoted text, click to view] > Paul, Have you found a solution to this problem? I am experiencing the > same exact thing and, so far, yours is the only post I have found on the > web regarding the issue. Since you are about a month ahead of me on this, > any assistance would be appreciated. Thanks... > > -- > Message posted via http://www.dotnetmonster.com
1603 is not a very helpful error number. It just means MSI install did not
complete. To get a better error, open up the MSI log for the installation; and search for "value 3". The actual error should be detalied in the 10-20 lines above that entry. -- Thanks, David James [MSFT] This posting is provided "AS IS" with no warranties, and confers no rights. [quoted text, click to view] "Paul Anderson" <paul.anderson@eaifhe.REMOVE_NOSPAM.ac.uk> wrote in message news:%23b2EM81OFHA.3380@TK2MSFTNGP15.phx.gbl... > No Laurie, I haven't. > > I'm on the brink of giving up. Microsoft haven't really provided me with > anything substantial here. > > Basically, I don't even know if the setup is working or not as > SMSWrapper.exe isn't passing back any more information than 1603. I'm not > the end user, so I don't know if the VS setup is satisfactory - all I know > is it opens and the suite apps run. The whole idea of SMS is that you get > feedback on the status of a deployment, only here you don't. I've scoured > the web and various newsgroups and forums and although there are others > like ourselves, MS are being unhelpful. > > Let me know if you have any luck yourself. > > "Laurie Wilcox via DotNetMonster.com" <forum@DotNetMonster.com> wrote in > message news:22e8fdecd57e4e8fa15416823caedac2@DotNetMonster.com... >> Paul, Have you found a solution to this problem? I am experiencing the >> same exact thing and, so far, yours is the only post I have found on the >> web regarding the issue. Since you are about a month ahead of me on >> this, >> any assistance would be appreciated. Thanks... >> >> -- >> Message posted via http://www.dotnetmonster.com > >
Thanks for you response David.
I've searched for "value 3" in c:\windows\temp\vsinstall71 and it's not there. However, line 679 reads: "[04/19/05,17:44:57] Visual Studio .NET Professional 2003 - English: MsiInstallProduct return code: 0." I've also searched for "value 3" in: C:\Program Files\Microsoft Visual Studio .NET 2003\Visual Studio .NET Professional 2003 - English\Logs\VSMsiLog3BCD.txt It is not in this log file either. It also appears to finish normally: " MSI (s) (18:C4) [17:44:44:291]: Note: 1: 1707 MSI (s) (18:C4) [17:44:44:502]: Product: Visual Studio .NET Professional 2003 - English -- Installation operation completed successfully. MSI (s) (18:C4) [17:44:52:348]: Cleaning up uninstalled install packages, if any exist MSI (s) (18:C4) [17:44:52:378]: MainEngineThread is returning 0 MSI (s) (18:9C) [17:44:52:639]: Destroying RemoteAPI object. MSI (s) (18:CC) [17:44:52:709]: Custom Action Manager thread ending. === Logging stopped: 19/04/2005 17:44:42 === MSI (c) (10:50) [17:44:54:652]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied. Counter after decrement: -1 MSI (c) (10:50) [17:44:55:003]: MainEngineThread is returning 0 === Verbose logging stopped: 19/04/2005 17:44:55 === " Am I searching the wrong logs ? Even if this is correct and the installation was successful, it isn't satisfactory. I need SMS to report back correctly success or failure of VS deployments as I have potentially over 100 to do. Can someone please help ??? As mentioned in previous posts, I think it may be a problem with smswrapper.exe not reporting back the results from setup. [quoted text, click to view] "David James [MSFT]" <djam@online.microsoft.com> wrote in message news:uLWyc$KQFHA.356@TK2MSFTNGP14.phx.gbl... > 1603 is not a very helpful error number. It just means MSI install did > not complete. > > To get a better error, open up the MSI log for the installation; and > search for "value 3". The actual error should be detalied in the 10-20 > lines above that entry. > > -- > > Thanks, > David James [MSFT] > This posting is provided "AS IS" with no warranties, and confers no > rights. > > > > "Paul Anderson" <paul.anderson@eaifhe.REMOVE_NOSPAM.ac.uk> wrote in > message news:%23b2EM81OFHA.3380@TK2MSFTNGP15.phx.gbl... >> No Laurie, I haven't. >> >> I'm on the brink of giving up. Microsoft haven't really provided me with >> anything substantial here. >> >> Basically, I don't even know if the setup is working or not as >> SMSWrapper.exe isn't passing back any more information than 1603. I'm >> not the end user, so I don't know if the VS setup is satisfactory - all I >> know is it opens and the suite apps run. The whole idea of SMS is that >> you get feedback on the status of a deployment, only here you don't. >> I've scoured the web and various newsgroups and forums and although there >> are others like ourselves, MS are being unhelpful. >> >> Let me know if you have any luck yourself. >> >> "Laurie Wilcox via DotNetMonster.com" <forum@DotNetMonster.com> wrote in >> message news:22e8fdecd57e4e8fa15416823caedac2@DotNetMonster.com... >>> Paul, Have you found a solution to this problem? I am experiencing the >>> same exact thing and, so far, yours is the only post I have found on the >>> web regarding the issue. Since you are about a month ahead of me on >>> this, >>> any assistance would be appreciated. Thanks... >>> >>> -- >>> Message posted via http://www.dotnetmonster.com >> >> > >
Finally, I've got a working solution to this problem. Our new third-party
support people have obtained a tool from Microsoft to replace smswrapper.exe and I've tested it successfully, although it hasn't been rigorously tested by either myself or MS. The resolution is to use a tool called VSUnattend.exe instead of smswrapper.exe in the package and adding 'NoInitialFileCopy=1' to Setup.SDB. Otherwise, if you follow the procedure outlined by MS in the original article, it should work: http://support.microsoft.com/default.aspx?scid=kb;en-us;327792 The package program command-line is the same, but with SMSWrapper.exe replaced with VSUnattend.exe. If anyone wants a copy of VSUnattend.exe, e-mail me and I'll send it to you. Note that we don't yet know how good this utility is at passing back errors. It certainly reports back a success code (0) and should also report back failure codes when the deployment doesn't go right. However, how informative these codes may be remains to be seen. What I do know is I can now do a successful deployment of VS and get a success code (0) back *after* the deployment completes. [quoted text, click to view] "Paul Anderson" <paul.anderson@eaifhe.REMOVE_NOSPAM.ac.uk> wrote in message news:uJZSiQaRFHA.2932@TK2MSFTNGP09.phx.gbl... > Thanks for you response David. > > I've searched for "value 3" in c:\windows\temp\vsinstall71 and it's not > there. However, line 679 reads: > > "[04/19/05,17:44:57] Visual Studio .NET Professional 2003 - English: > MsiInstallProduct return code: 0." > > I've also searched for "value 3" in: > > C:\Program Files\Microsoft Visual Studio .NET 2003\Visual Studio .NET > Professional 2003 - English\Logs\VSMsiLog3BCD.txt > > It is not in this log file either. It also appears to finish normally: > > " > MSI (s) (18:C4) [17:44:44:291]: Note: 1: 1707 > > MSI (s) (18:C4) [17:44:44:502]: Product: Visual Studio .NET Professional > 2003 - English -- Installation operation completed successfully. > > > > MSI (s) (18:C4) [17:44:52:348]: Cleaning up uninstalled install packages, > if any exist > > MSI (s) (18:C4) [17:44:52:378]: MainEngineThread is returning 0 > > MSI (s) (18:9C) [17:44:52:639]: Destroying RemoteAPI object. > > MSI (s) (18:CC) [17:44:52:709]: Custom Action Manager thread ending. > > === Logging stopped: 19/04/2005 17:44:42 === > > MSI (c) (10:50) [17:44:54:652]: Decrementing counter to disable shutdown. > If counter >= 0, shutdown will be denied. Counter after decrement: -1 > > MSI (c) (10:50) [17:44:55:003]: MainEngineThread is returning 0 > > === Verbose logging stopped: 19/04/2005 17:44:55 === > > " > > > > Am I searching the wrong logs ? > > > > Even if this is correct and the installation was successful, it isn't > satisfactory. I need SMS to report back correctly success or failure of > VS deployments as I have potentially over 100 to do. Can someone please > help ??? As mentioned in previous posts, I think it may be a problem with > smswrapper.exe not reporting back the results from setup. > > > > > > "David James [MSFT]" <djam@online.microsoft.com> wrote in message > news:uLWyc$KQFHA.356@TK2MSFTNGP14.phx.gbl... >> 1603 is not a very helpful error number. It just means MSI install did >> not complete. >> >> To get a better error, open up the MSI log for the installation; and >> search for "value 3". The actual error should be detalied in the 10-20 >> lines above that entry. >> >> -- >> >> Thanks, >> David James [MSFT] >> This posting is provided "AS IS" with no warranties, and confers no >> rights. >> >> >> >> "Paul Anderson" <paul.anderson@eaifhe.REMOVE_NOSPAM.ac.uk> wrote in >> message news:%23b2EM81OFHA.3380@TK2MSFTNGP15.phx.gbl... >>> No Laurie, I haven't. >>> >>> I'm on the brink of giving up. Microsoft haven't really provided me >>> with anything substantial here. >>> >>> Basically, I don't even know if the setup is working or not as >>> SMSWrapper.exe isn't passing back any more information than 1603. I'm >>> not the end user, so I don't know if the VS setup is satisfactory - all >>> I know is it opens and the suite apps run. The whole idea of SMS is >>> that you get feedback on the status of a deployment, only here you >>> don't. I've scoured the web and various newsgroups and forums and >>> although there are others like ourselves, MS are being unhelpful. >>> >>> Let me know if you have any luck yourself. >>> >>> "Laurie Wilcox via DotNetMonster.com" <forum@DotNetMonster.com> wrote in >>> message news:22e8fdecd57e4e8fa15416823caedac2@DotNetMonster.com... >>>> Paul, Have you found a solution to this problem? I am experiencing the >>>> same exact thing and, so far, yours is the only post I have found on >>>> the >>>> web regarding the issue. Since you are about a month ahead of me on >>>> this, >>>> any assistance would be appreciated. Thanks... >>>> >>>> -- >>>> Message posted via http://www.dotnetmonster.com >>> >>> >> >> > >
Does anyone know where I can find the VSUNATTEND.EXE file. I have looked on Microsoft.com and it returns no results. Other sites only mention the file and have NO download location.
If anyone could point me in the right direction I would be grateful, Thanks, Jason work@the4freemans.com From http://www.developmentnow.com/g/58_2005_2_0_0_58796/Re-Exit-Code-1603-When-Setting-Up-Visual-Studio--NET-2003-Using-SMS.htm Posted via DevelopmentNow.com Groups
Don't see what you're looking for? Try a search.
|
June 2003
July 2003
August 2003
September 2003
October 2003
November 2003
December 2003
January 2004
February 2004
March 2004
April 2004
May 2004
June 2004
July 2004
August 2004
September 2004
October 2004
November 2004
December 2004
January 2005
February 2005
March 2005
April 2005
May 2005
June 2005
July 2005
August 2005
September 2005
October 2005
November 2005
December 2005
January 2006
February 2006
March 2006
April 2006
May 2006
June 2006
July 2006
August 2006
September 2006
October 2006
November 2006
December 2006
January 2007
February 2007
March 2007
April 2007
May 2007
June 2007
July 2007
August 2007
September 2007
October 2007
November 2007
| home · blog · groups | Questions? Comments? Contact the dn |