A Microsoft Office (Excel, Word) forum. OfficeFrustration

If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below.

Go Back   Home » OfficeFrustration forum » Microsoft Office » Setup, Installing & Configuration
Site Map Home Register Authors List Search Today's Posts Mark Forums Read  

Still need Help with O2k3 Admin Install



 
 
Thread Tools Display Modes
  #1  
Old June 3rd, 2005, 05:41 PM
Stephen Longmire
external usenet poster
 
Posts: n/a
Default Still need Help with O2k3 Admin Install

Sorry for the repost, but I am desperate for a solution to this problem
which is holding up deployment of Office 2003 Pro Enterprise Eidition.

Per Glenn's suggustion I have now attached three files: the CMD file I used
to try to apply the patches to the admin install point, as well as the two
log files generated during the failed patch attempts.

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 install? ANXIOUSLY awaiting enlightenment
.........

Steve








  #2  
Old June 7th, 2005, 06:01 PM
Bob Buckland ?:-\)
external usenet poster
 
Posts: n/a
Default

Hi Steve,

There is a 1314 error (bad path) in the log file
for the MainSP1 when it's trying to find the PRO11.MSI

If you look at the log file it appears that you're
pointing to the MSI at

D:Software...

rather than
D:\Software...

If so, there's no way for Windows to know to start at
the root level of the D:\ drive when it's trying to
follow the path.

As for the root names question. The MSI files are edition
specific (i.e. Professional, Standard, Basic, etc) where the
updates are usually Version (2003) wide.

=========
"Stephen Longmire" wrote in message ...
Sorry for the repost, but I am desperate for a solution to this problem
which is holding up deployment of Office 2003 Pro Enterprise Eidition.

Per Glenn's suggustion I have now attached three files: the CMD file I used
to try to apply the patches to the admin install point, as well as the two
log files generated during the failed patch attempts.

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 install? ANXIOUSLY awaiting enlightenment
.........

Steve
--
Let us know if this helped you,

Bob Buckland ?:-)
MS Office System Products MVP

*Courtesy is not expensive and can pay big dividends*

For Everyday MS Office tips to "use right away" -
http://microsoft.com/events/series/a...andtricks.mspx



  #3  
Old June 8th, 2005, 07:34 PM
Stephen Longmire
external usenet poster
 
Posts: n/a
Default

BOB!

I can't thank you enough, and boy am I ashamed to have missed that silly
little backslash!

The first part of the command file ran without errors to apply SP1 to the
main Office 2K3Pro file. However, the second line of the command file still
fails as before (the one that is supposed to spatch the OWC11.msi file). I
have tried to recheck all my typing on this second command line (and have
removed the ; from its beginning) , but can find no typo in it. There are
two OWC*.msp patches in the fullfile download. OWC11SP1ff.msi and OWC
10200SP1ff.msi. I have NO IDEA which to apply to the OWC11.msi file, but
assumed that I should use the one whose filename was most similar to the
original msi filename, since Microsoft provided such fine guidance in its KB
article about how to patch the admin instal ;{).

Any further guidance from you would be greatly appreciated -- and once
again, MANY THANKS for the enlightenment!

Steve
"Bob Buckland ?:-)" 75214.226(At Beautiful Downtown)compuserve.com wrote
in message ...
Hi Steve,

There is a 1314 error (bad path) in the log file
for the MainSP1 when it's trying to find the PRO11.MSI

If you look at the log file it appears that you're
pointing to the MSI at

D:Software...

rather than
D:\Software...

If so, there's no way for Windows to know to start at
the root level of the D:\ drive when it's trying to
follow the path.

As for the root names question. The MSI files are edition
specific (i.e. Professional, Standard, Basic, etc) where the
updates are usually Version (2003) wide.

=========
"Stephen Longmire" wrote in message
...
Sorry for the repost, but I am desperate for a solution to this problem
which is holding up deployment of Office 2003 Pro Enterprise Eidition.

Per Glenn's suggustion I have now attached three files: the CMD file I
used
to try to apply the patches to the admin install point, as well as the two
log files generated during the failed patch attempts.

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 install? ANXIOUSLY awaiting enlightenment
........

Steve
--
Let us know if this helped you,

Bob Buckland ?:-)
MS Office System Products MVP

*Courtesy is not expensive and can pay big dividends*

For Everyday MS Office tips to "use right away" -
http://microsoft.com/events/series/a...andtricks.mspx





  #4  
Old June 10th, 2005, 05:38 AM
Bob Buckland ?:-\)
external usenet poster
 
Posts: n/a
Default

Hi Steve,

The basic command line for OWC11 is in step 4 of
http://support.microsoft.com/default...b;en-us;555215
Steps 1-3 are now completed successfully?

You may also find this SP1 whitepaper useful in updating
the Office Web Components in an Office Admin Point.
http://microsoft.com/downloads/detai...DisplayLang=en
in addition to the information in
http://microsoft.com/office/ork/2003

======
"Stephen Longmire" wrote in message ...
BOB!

I can't thank you enough, and boy am I ashamed to have missed that silly
little backslash!

The first part of the command file ran without errors to apply SP1 to the
main Office 2K3Pro file. However, the second line of the command file still
fails as before (the one that is supposed to spatch the OWC11.msi file). I
have tried to recheck all my typing on this second command line (and have
removed the ; from its beginning) , but can find no typo in it. There are
two OWC*.msp patches in the fullfile download. OWC11SP1ff.msi and OWC
10200SP1ff.msi. I have NO IDEA which to apply to the OWC11.msi file, but
assumed that I should use the one whose filename was most similar to the
original msi filename, since Microsoft provided such fine guidance in its KB
article about how to patch the admin instal ;{).

Any further guidance from you would be greatly appreciated -- and once
again, MANY THANKS for the enlightenment!
--
Bob Buckland ?:-)
MS Office System Products MVP

*Courtesy is not expensive and can pay big dividends*


  #5  
Old June 10th, 2005, 05:10 PM
Stephen Longmire
external usenet poster
 
Posts: n/a
Default

Thanks, again, Bob. I still have a "left-over" SP1.MSP file
(OWC10something.MSP) that I did not try to apply because I could not find
anything even close to it in my Admin Install path. The other two patches
are now successfully applied according to their logfiles.

Steve


"Bob Buckland ?:-)" 75214.226(At Beautiful Downtown)compuserve.com wrote
in message ...
Hi Steve,

The basic command line for OWC11 is in step 4 of
http://support.microsoft.com/default...b;en-us;555215
Steps 1-3 are now completed successfully?

You may also find this SP1 whitepaper useful in updating
the Office Web Components in an Office Admin Point.
http://microsoft.com/downloads/detai...DisplayLang=en
in addition to the information in
http://microsoft.com/office/ork/2003

======
"Stephen Longmire" wrote in message
...
BOB!

I can't thank you enough, and boy am I ashamed to have missed that silly
little backslash!

The first part of the command file ran without errors to apply SP1 to the
main Office 2K3Pro file. However, the second line of the command file
still
fails as before (the one that is supposed to spatch the OWC11.msi file). I
have tried to recheck all my typing on this second command line (and have
removed the ; from its beginning) , but can find no typo in it. There are
two OWC*.msp patches in the fullfile download. OWC11SP1ff.msi and OWC
10200SP1ff.msi. I have NO IDEA which to apply to the OWC11.msi file, but
assumed that I should use the one whose filename was most similar to the
original msi filename, since Microsoft provided such fine guidance in its
KB
article about how to patch the admin instal ;{).

Any further guidance from you would be greatly appreciated -- and once
again, MANY THANKS for the enlightenment!
--
Bob Buckland ?:-)
MS Office System Products MVP

*Courtesy is not expensive and can pay big dividends*




  #6  
Old June 11th, 2005, 05:18 PM
Stephen Longmire
external usenet poster
 
Posts: n/a
Default

I finally found the answer to the left-over OWC10xxxSP1.MSP. It seems taht
if you had an old installation of Office XP on the machine when you install
Office 2003, it leaves the OWC 10 components, even if you instruct Office
2003 to unistall prior apps. It is this left-over OWC10 component that must
be upgraded with the third MSP file in the Fullfile Service Pack. As we had
no leftover components, it did not apply to our situation. I post this for
general information in case someone else finds themselves similarly baffled.

Steve


"Stephen Longmire" wrote in message
...
Thanks, again, Bob. I still have a "left-over" SP1.MSP file
(OWC10something.MSP) that I did not try to apply because I could not find
anything even close to it in my Admin Install path. The other two patches
are now successfully applied according to their logfiles.

Steve


"Bob Buckland ?:-)" 75214.226(At Beautiful Downtown)compuserve.com wrote
in message ...
Hi Steve,

The basic command line for OWC11 is in step 4 of
http://support.microsoft.com/default...b;en-us;555215
Steps 1-3 are now completed successfully?

You may also find this SP1 whitepaper useful in updating
the Office Web Components in an Office Admin Point.
http://microsoft.com/downloads/detai...DisplayLang=en
in addition to the information in
http://microsoft.com/office/ork/2003

======
"Stephen Longmire" wrote in message
...
BOB!

I can't thank you enough, and boy am I ashamed to have missed that silly
little backslash!

The first part of the command file ran without errors to apply SP1 to the
main Office 2K3Pro file. However, the second line of the command file
still
fails as before (the one that is supposed to spatch the OWC11.msi file).
I
have tried to recheck all my typing on this second command line (and have
removed the ; from its beginning) , but can find no typo in it. There are
two OWC*.msp patches in the fullfile download. OWC11SP1ff.msi and OWC
10200SP1ff.msi. I have NO IDEA which to apply to the OWC11.msi file, but
assumed that I should use the one whose filename was most similar to the
original msi filename, since Microsoft provided such fine guidance in its
KB
article about how to patch the admin instal ;{).

Any further guidance from you would be greatly appreciated -- and once
again, MANY THANKS for the enlightenment!
--
Bob Buckland ?:-)
MS Office System Products MVP

*Courtesy is not expensive and can pay big dividends*






  #7  
Old June 11th, 2005, 07:04 PM
Bob Buckland ?:-\)
external usenet poster
 
Posts: n/a
Default

Hi Steve,

That is one scenario, the other is that Office 2003
ships with both the Office XP (v10) and Office 2003 (v11)
Office Web Components . The Office XP web components
have their own setup program to create an Admin image
(see Workaround section of this article)
http://support.microsoft.com/default...us;889369&FR=1
but may not have been installed, in which case the MSP patch
file for them wouldn't be needed

==========
"Stephen Longmire" wrote in message ...
I finally found the answer to the left-over OWC10xxxSP1.MSP. It seems taht
if you had an old installation of Office XP on the machine when you install
Office 2003, it leaves the OWC 10 components, even if you instruct Office
2003 to unistall prior apps. It is this left-over OWC10 component that must
be upgraded with the third MSP file in the Fullfile Service Pack. As we had
no leftover components, it did not apply to our situation. I post this for
general information in case someone else finds themselves similarly baffled.

Steve
--
Let us know if this helped you,

Bob Buckland ?:-)
MS Office System Products MVP

*Courtesy is not expensive and can pay big dividends*

For Everyday MS Office tips to "use right away" -
http://microsoft.com/events/series/a...andtricks.mspx




 




Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is Off
HTML code is Off
Forum Jump

Similar Threads
Thread Thread Starter Forum Replies Last Post
Create an install of Office 2003 with SP1 Jon Osborn Setup, Installing & Configuration 3 March 28th, 2005 09:11 PM
Office won't install for all users - KNow what but not why? Bruce Musgrove Setup, Installing & Configuration 5 December 22nd, 2004 05:38 PM
Why install older version of Office first? Apply to Tools? Chad Harris General Discussions 0 June 22nd, 2004 08:04 AM


All times are GMT +1. The time now is 05:47 PM.


Powered by vBulletin® Version 3.6.4
Copyright ©2000 - 2024, Jelsoft Enterprises Ltd.
Copyright ©2004-2024 OfficeFrustration.
The comments are property of their posters.