HELP!!! Can't patch admin install of Office 2003 Pro Enterprise Edition

[Stephen Longmire]

I wish Bill Gates had to sit in from of a server and try to type this D@#n
command line installer patch routine to upgrade the administrative install
point of Office 2003 Pro to SP1.

I've read and read the KB articles. I've carefully fully specified the
filenames of the MSP and MSI files, but I get the same error message telling
me that "This is not a valid Windows Installer Image file." Well Both of
the files in question ARE, as I can run them on their own.

I am also frustrated by the fact that the Full File version of the SP1
extracts to MAINSP1ff.MSP, whereas the filename of the install file for
O2k3Pro is PRO11.MSI. Shouldn't M$ have made the root names at least
similar???

How can I patch this admin isntall, as I must deploy this app tomorrow
morning using a new GPO?????

HELP, PLEASE!!!

Steve

 

[glenn fincher]

I wish Bill Gates had to sit in from of a server and try to type this D@#n
command line installer patch routine to upgrade the administrative install
point of Office 2003 Pro to SP1.

He would just hire someone like yourself to do it for him!

I've read and read the KB articles. I've carefully fully specified the
filenames of the MSP and MSI files, but I get the same error message
telling
me that "This is not a valid Windows Installer Image file." Well Both of
the files in question ARE, as I can run them on their own.

I am also frustrated by the fact that the Full File version of the SP1
extracts to MAINSP1ff.MSP, whereas the filename of the install file for
O2k3Pro is PRO11.MSI. Shouldn't M$ have made the root names at least
similar???

How can I patch this admin isntall, as I must deploy this app tomorrow
morning using a new GPO?????

So, you are executing a command similar to this one:

msiexec.exe /p \\server1\OfficeShare\MAINSP1ff.MSP /a
\\server1\OfficeShare\Pro11\msi /qb /lv* \\server1\OfficeShare\update.log

IF so, take off the "/qb" so that you can see the process as it fails,
and... if you have the log file, let us see it so we can assist you. In the
meantime, check permissions to the share, extra spaces, etc. Finally,
please post your command line as well - an extra set of eyes sometimes
helps.

Hope this helps!

Glenn Fincher

 

[glenn fincher]

I wish Bill Gates had to sit in from of a server and try to type this D@#n
command line installer patch routine to upgrade the administrative install
point of Office 2003 Pro to SP1.

He would just hire someone like yourself to do it for him!

I've read and read the KB articles. I've carefully fully specified the
filenames of the MSP and MSI files, but I get the same error message
telling
me that "This is not a valid Windows Installer Image file." Well Both of
the files in question ARE, as I can run them on their own.

I am also frustrated by the fact that the Full File version of the SP1
extracts to MAINSP1ff.MSP, whereas the filename of the install file for
O2k3Pro is PRO11.MSI. Shouldn't M$ have made the root names at least
similar???

How can I patch this admin isntall, as I must deploy this app tomorrow
morning using a new GPO?????

So, you are executing a command similar to this one:

msiexec.exe /p \\server1\OfficeShare\MAINSP1ff.MSP /a
\\server1\OfficeShare\Pro11\msi /qb /lv* \\server1\OfficeShare\update.log

IF so, take off the "/qb" so that you can see the process as it fails,
and... if you have the log file, let us see it so we can assist you. In the
meantime, check permissions to the share, extra spaces, etc. Finally,
please post your command line as well - an extra set of eyes sometimes
helps.

Hope this helps!

Glenn Fincher

 

[glenn fincher]

I wish Bill Gates had to sit in from of a server and try to type this D@#n
command line installer patch routine to upgrade the administrative install
point of Office 2003 Pro to SP1.

He would just hire someone like yourself to do it for him!

I've read and read the KB articles. I've carefully fully specified the
filenames of the MSP and MSI files, but I get the same error message
telling
me that "This is not a valid Windows Installer Image file." Well Both of
the files in question ARE, as I can run them on their own.

I am also frustrated by the fact that the Full File version of the SP1
extracts to MAINSP1ff.MSP, whereas the filename of the install file for
O2k3Pro is PRO11.MSI. Shouldn't M$ have made the root names at least
similar???

How can I patch this admin isntall, as I must deploy this app tomorrow
morning using a new GPO?????

So, you are executing a command similar to this one:

msiexec.exe /p \\server1\OfficeShare\MAINSP1ff.MSP /a
\\server1\OfficeShare\Pro11\msi /qb /lv* \\server1\OfficeShare\update.log

IF so, take off the "/qb" so that you can see the process as it fails,
and... if you have the log file, let us see it so we can assist you. In the
meantime, check permissions to the share, extra spaces, etc. Finally,
please post your command line as well - an extra set of eyes sometimes
helps.

Hope this helps!

Glenn Fincher

 

[glenn fincher]

I wish Bill Gates had to sit in from of a server and try to type this D@#n
command line installer patch routine to upgrade the administrative install
point of Office 2003 Pro to SP1.

He would just hire someone like yourself to do it for him!

I've read and read the KB articles. I've carefully fully specified the
filenames of the MSP and MSI files, but I get the same error message
telling
me that "This is not a valid Windows Installer Image file." Well Both of
the files in question ARE, as I can run them on their own.

I am also frustrated by the fact that the Full File version of the SP1
extracts to MAINSP1ff.MSP, whereas the filename of the install file for
O2k3Pro is PRO11.MSI. Shouldn't M$ have made the root names at least
similar???

How can I patch this admin isntall, as I must deploy this app tomorrow
morning using a new GPO?????

So, you are executing a command similar to this one:

msiexec.exe /p \\server1\OfficeShare\MAINSP1ff.MSP /a
\\server1\OfficeShare\Pro11\msi /qb /lv* \\server1\OfficeShare\update.log

IF so, take off the "/qb" so that you can see the process as it fails,
and... if you have the log file, let us see it so we can assist you. In the
meantime, check permissions to the share, extra spaces, etc. Finally,
please post your command line as well - an extra set of eyes sometimes
helps.

Hope this helps!

Glenn Fincher

 

[glenn fincher]

I wish Bill Gates had to sit in from of a server and try to type this D@#n
command line installer patch routine to upgrade the administrative install
point of Office 2003 Pro to SP1.

He would just hire someone like yourself to do it for him!

I've read and read the KB articles. I've carefully fully specified the
filenames of the MSP and MSI files, but I get the same error message
telling
me that "This is not a valid Windows Installer Image file." Well Both of
the files in question ARE, as I can run them on their own.

I am also frustrated by the fact that the Full File version of the SP1
extracts to MAINSP1ff.MSP, whereas the filename of the install file for
O2k3Pro is PRO11.MSI. Shouldn't M$ have made the root names at least
similar???

How can I patch this admin isntall, as I must deploy this app tomorrow
morning using a new GPO?????

So, you are executing a command similar to this one:

msiexec.exe /p \\server1\OfficeShare\MAINSP1ff.MSP /a
\\server1\OfficeShare\Pro11\msi /qb /lv* \\server1\OfficeShare\update.log

IF so, take off the "/qb" so that you can see the process as it fails,
and... if you have the log file, let us see it so we can assist you. In the
meantime, check permissions to the share, extra spaces, etc. Finally,
please post your command line as well - an extra set of eyes sometimes
helps.

Hope this helps!

Glenn Fincher

 

[glenn fincher]

I wish Bill Gates had to sit in from of a server and try to type this D@#n
command line installer patch routine to upgrade the administrative install
point of Office 2003 Pro to SP1.

He would just hire someone like yourself to do it for him!

I've read and read the KB articles. I've carefully fully specified the
filenames of the MSP and MSI files, but I get the same error message
telling
me that "This is not a valid Windows Installer Image file." Well Both of
the files in question ARE, as I can run them on their own.

I am also frustrated by the fact that the Full File version of the SP1
extracts to MAINSP1ff.MSP, whereas the filename of the install file for
O2k3Pro is PRO11.MSI. Shouldn't M$ have made the root names at least
similar???

How can I patch this admin isntall, as I must deploy this app tomorrow
morning using a new GPO?????

So, you are executing a command similar to this one:

msiexec.exe /p \\server1\OfficeShare\MAINSP1ff.MSP /a
\\server1\OfficeShare\Pro11\msi /qb /lv* \\server1\OfficeShare\update.log

IF so, take off the "/qb" so that you can see the process as it fails,
and... if you have the log file, let us see it so we can assist you. In the
meantime, check permissions to the share, extra spaces, etc. Finally,
please post your command line as well - an extra set of eyes sometimes
helps.

Hope this helps!

Glenn Fincher

 

[glenn fincher]

I wish Bill Gates had to sit in from of a server and try to type this D@#n
command line installer patch routine to upgrade the administrative install
point of Office 2003 Pro to SP1.

He would just hire someone like yourself to do it for him!

I've read and read the KB articles. I've carefully fully specified the
filenames of the MSP and MSI files, but I get the same error message
telling
me that "This is not a valid Windows Installer Image file." Well Both of
the files in question ARE, as I can run them on their own.

I am also frustrated by the fact that the Full File version of the SP1
extracts to MAINSP1ff.MSP, whereas the filename of the install file for
O2k3Pro is PRO11.MSI. Shouldn't M$ have made the root names at least
similar???

How can I patch this admin isntall, as I must deploy this app tomorrow
morning using a new GPO?????

So, you are executing a command similar to this one:

msiexec.exe /p \\server1\OfficeShare\MAINSP1ff.MSP /a
\\server1\OfficeShare\Pro11\msi /qb /lv* \\server1\OfficeShare\update.log

IF so, take off the "/qb" so that you can see the process as it fails,
and... if you have the log file, let us see it so we can assist you. In the
meantime, check permissions to the share, extra spaces, etc. Finally,
please post your command line as well - an extra set of eyes sometimes
helps.

Hope this helps!

Glenn Fincher

 

[glenn fincher]

I wish Bill Gates had to sit in from of a server and try to type this D@#n
command line installer patch routine to upgrade the administrative install
point of Office 2003 Pro to SP1.

He would just hire someone like yourself to do it for him!

I've read and read the KB articles. I've carefully fully specified the
filenames of the MSP and MSI files, but I get the same error message
telling
me that "This is not a valid Windows Installer Image file." Well Both of
the files in question ARE, as I can run them on their own.

I am also frustrated by the fact that the Full File version of the SP1
extracts to MAINSP1ff.MSP, whereas the filename of the install file for
O2k3Pro is PRO11.MSI. Shouldn't M$ have made the root names at least
similar???

How can I patch this admin isntall, as I must deploy this app tomorrow
morning using a new GPO?????

So, you are executing a command similar to this one:

msiexec.exe /p \\server1\OfficeShare\MAINSP1ff.MSP /a
\\server1\OfficeShare\Pro11\msi /qb /lv* \\server1\OfficeShare\update.log

IF so, take off the "/qb" so that you can see the process as it fails,
and... if you have the log file, let us see it so we can assist you. In the
meantime, check permissions to the share, extra spaces, etc. Finally,
please post your command line as well - an extra set of eyes sometimes
helps.

Hope this helps!

Glenn Fincher

 

[glenn fincher]

I wish Bill Gates had to sit in from of a server and try to type this D@#n
command line installer patch routine to upgrade the administrative install
point of Office 2003 Pro to SP1.

He would just hire someone like yourself to do it for him!

I've read and read the KB articles. I've carefully fully specified the
filenames of the MSP and MSI files, but I get the same error message
telling
me that "This is not a valid Windows Installer Image file." Well Both of
the files in question ARE, as I can run them on their own.

I am also frustrated by the fact that the Full File version of the SP1
extracts to MAINSP1ff.MSP, whereas the filename of the install file for
O2k3Pro is PRO11.MSI. Shouldn't M$ have made the root names at least
similar???

How can I patch this admin isntall, as I must deploy this app tomorrow
morning using a new GPO?????

So, you are executing a command similar to this one:

msiexec.exe /p \\server1\OfficeShare\MAINSP1ff.MSP /a
\\server1\OfficeShare\Pro11\msi /qb /lv* \\server1\OfficeShare\update.log

IF so, take off the "/qb" so that you can see the process as it fails,
and... if you have the log file, let us see it so we can assist you. In the
meantime, check permissions to the share, extra spaces, etc. Finally,
please post your command line as well - an extra set of eyes sometimes
helps.

Hope this helps!

Glenn Fincher