1618 error doing multiple Office 2007 component installs

[Bill Bradley]

I'm trying to install the ENT version of the Suite + VISIO Pro + Project Pro
+ SharePoint Designer. All are Volume Licensed versions and have the
appropriate CD Keys and are being installed silently.

Have not used Linked installs, but, am either using a batch file or multiple
SMS Packages.

Problem is I'm getting 1618 errors about multiple uses of MSIExec, and,
can't figure out why.

I have created MSP's for all products using OCT (setup.exe /admin for EACH
product), and, placed them in each product's Updates folder. I've also
extracted the SP1 MSP's for each product and also placed them in each
product's Updates folder. I've named the product's OCT MSP with a "1_", so,
it runs first, prior to the SP1 MSP's.

From what I've read, this should work, but, I'm getting the 1618 errors,
after the first product (the ENT Suite) starts to install.

I did see mention of a WAIT = -1 attribute, used within a commandline.
Should this be inserted in each product's MSP (CAN it be inserted...it's not
listed as an attribute)?

Thanks!

 

[Bob Buckland ?:-\)]

Hi Bill,

As a guess it could be that your batch file isn't setup to wait until one installation is complete, but rather it's moving down to
the next command in line as soon as it 'runs' the 'next' setup command.

Do you get the same result if you chain the installs?

Do you have all of the Office products in a single Office Network Installation Point (oNIP), or in separate ones (they can usually
be consolidated in one) that can be used to create the MSOCache on the clients, which sometimes works better with the final setup
then being run from the MSOCache.

=============
I'm trying to install the ENT version of the Suite + VISIO Pro + Project Pro
+ SharePoint Designer. All are Volume Licensed versions and have the
appropriate CD Keys and are being installed silently.

Have not used Linked installs, but, am either using a batch file or multiple
SMS Packages.

Problem is I'm getting 1618 errors about multiple uses of MSIExec, and,
can't figure out why.

I have created MSP's for all products using OCT (setup.exe /admin for EACH
product), and, placed them in each product's Updates folder. I've also
extracted the SP1 MSP's for each product and also placed them in each
product's Updates folder. I've named the product's OCT MSP with a "1_", so,
it runs first, prior to the SP1 MSP's.

From what I've read, this should work, but, I'm getting the 1618 errors,
after the first product (the ENT Suite) starts to install.

I did see mention of a WAIT = -1 attribute, used within a commandline.
Should this be inserted in each product's MSP (CAN it be inserted...it's not
listed as an attribute)?

Thanks!>>
--

Bob Buckland ?
MS Office System Products MVP

*Courtesy is not expensive and can pay big dividends*

 

[Bill Bradley]

Both the batch and the SMS packages (2003 SP3) fail with same 1618 error.

Not sure HOW "same" I can put VISIO, Project, and SPS Designer into the
suite location... I have a folder named VISIO that is added into the copy of
the Office 2007 CD, which is just copied up to the network--it's at the same
level as the Suite's Updates folder. Project and SPS Designer are same way.

Thanks.