Re: Problem rolling out SOAPSDK with SMS 2003.


<mulhollands@xxxxxxxxxxxxxx> wrote in message
news:1161165213.905657.34500@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Hi all, I'm trying to install the SOAP SDK to about 1000 XP PCs using
SMS2003. Maybe someone could help me out here.


I've extracted the soapsdk.msi file from the SOAPSDK.EXE I downloaded
from Microsoft's site. I've placed the .msi file in a folder on the
SMS server (let's call it SOAPFOLDER).


In the SMS Admin Console, I select Packages/New/Package from
Definition, browse to the SOAPFOLDER folder and select soapsdk.msi.


NEXT - Source files. I select "This package does not contain any
files". Correct? I finish through the wizard, creating the package.


I have created a test collection called, surprisingly, TEST, and I want

to distribute the SOAPSDK to the TEST collection. So, I right-click on
the TEST collection and select All Tasks/Distribute Software, which
starts the relevant Wizard. I select the Microsoft SOAP Toolkit 3.0
package and advertise the "Per-system unattended" option, advertising
it only to the members of the TEST collection. I assign the program and

schedule it to install on logoff.


However, the SOAPSDK doesn't install when the machines in the TEST
collection log off. When I look at the Advertisement Status/Show
Messages/All, the following message is displayed :


"The program for advertisement "BC12000C" failed ("BC100007" -
"Per-system unattended"). A failure exit code of 1619 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 1619 is considered a failure.
Solution: For more information on the exit code, refer to the
documentation for the program you are distributing."


I can't seem to find any relevant documentation to sort out what's
going wrong.


Any ideas, folks? It's probably something simple, but I'm pretty new
to SMS, so grant me a little leeway!

Two things:
- Did you just specify the name of the <msifile.msi> as a program/command
line option? If so, you'll want to use the msi command line parameters
http://support.microsoft.com/kb/227091/EN-US/

- Change your install option to install whether or not a user is logged in.

Steve


.

Relevant Pages

  • Problem installing SOAPSDK with SMS 2003
    ... I'm trying to install the SOAP SDK to about 1000 XP PCs using ... SMS server. ... I have created a test collection called, surprisingly, TEST, and I want ... A failure exit code of 1619 was returned. ...
    (microsoft.public.sms.swdist)
  • Problem rolling out SOAPSDK with SMS 2003.
    ... I'm trying to install the SOAP SDK to about 1000 XP PCs using ... SMS server. ... I have created a test collection called, surprisingly, TEST, and I want ... A failure exit code of 1619 was returned. ...
    (microsoft.public.sms.misc)
  • Re: batch file wont run
    ... It should install correctly and should try to copy. ... Server (SMS) determines status for each program it executes. ... An exit code of 1 is considered a failure. ... default ini file on the clients workstation. ...
    (microsoft.public.sms.setup)
  • Re: batch file wont run
    ... You either need to run this with user rights, Grant guest access to the share and folder, or create a MSI/SMS Install Package with includes the files. ... Personally I would create a SMS Installer package for me it is very quick and simple to install the file and still run under the local system content. ... An exit code of 1 is considered a failure. ...
    (microsoft.public.sms.setup)
  • Deploying Office 2003 Failed
    ... Exit code was an error. ... Action ended 2:23:26: INSTALL. ... When I logged on to a client machine as a user with administrative privilege on the client and run the script, ... I used similar script to deploy Office XP using SMS 2.0 and it worked. ...
    (microsoft.public.sms.swdist)
Loading