Re: Install VS .Net 2003 error 1603

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance




Paul Anderson had the same issue a while back, and posted this as a
solution.
Thread subject: Exit Code 1603 When Setting Up Visual Studio .NET 2003
Using SMS
Thread start date: 04/02/2005

From: Paul Anderson <paul.anderson@xxxxxxxxxxxxxxxxxxxxxxxxxx>

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.

In article <CF4BD72D-A8BA-4F86-B817-F07776191E0A@xxxxxxxxxxxxx>,
jasonf@xxxxxxxxxxxxxxxxxxxxxxxxx says...
> Does anyone know of such a utility or another work around to this.
> When you create your Visual Studio .Net Package and distribute, you may
> receive 1603 Errors when deploying the package indicating failure although
> the deployment is successful. This is a known bug and the fix is as follows:
> You must not use SMSWrapper.exe instead you must obtain another MS Utility
> called VSUnattend.exe and replace SMSWrapper with it.
> as posted on Appdeply.com
>

--
Kim Oppalfens
MVP SMS
Computacenter Belgium
.



Relevant Pages

  • Upgrades - Comp Confign - Software Settings - Assigned Application
    ... Template - LetterToolsWizard 5.9", this will then install a MSI onto the ... Deployment type Assigned ... Ignore language when deploying this package Disabled ... Required upgrade for existing packages Enabled ...
    (microsoft.public.windows.group_policy)
  • Re: Office 2007/B2 Group Policy Installation
    ... I suspect they may force us to use BDD for deployment. ... PS: Clarification of the error: Only happens after you add the .MSP file to ... the update folder. ... the proww.msi as a new package in a policy assigned to a workstation. ...
    (microsoft.public.office.setup)
  • Re: Office 2007/B2 Group Policy Installation
    ... PS: Clarification of the error: Only happens after you add the .MSP file to ... the update folder. ... the proww.msi as a new package in a policy assigned to a workstation. ... I have not touched the config.xml as from what I read in the deployment ...
    (microsoft.public.office.setup)
  • Re: Office 2007/B2 Group Policy Installation
    ... PS: Clarification of the error: Only happens after you add the .MSP file to ... the update folder. ... the proww.msi as a new package in a policy assigned to a workstation. ... I have not touched the config.xml as from what I read in the deployment ...
    (microsoft.public.office.setup)
  • Re: Office 2007/B2 Group Policy Installation
    ... PS: Clarification of the error: Only happens after you add the .MSP file to ... the update folder. ... the proww.msi as a new package in a policy assigned to a workstation. ... I have not touched the config.xml as from what I read in the deployment ...
    (microsoft.public.office.setup)