Re: Still need Help with O2k3 Admin Install

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" <none@xxxxxxxx> wrote in message news:e1SkqsFaFHA.3120@xxxxxxxxxxxxxxxxxxxxxxx
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/administrativetipsandtricks.mspx



.

Relevant Pages

  • Re: how to make my deamon depends on other
    ... No matter how your daemon is installed ... Does this make any sense in your app that the mydaemon's pid one more ... of the log file changed back to root who is the system-starting the ... I used in mydeamon script to change the owner of log file. ...
    (comp.unix.shell)
  • Re: how to make my deamon depends on other
    ... Does this make any sense in your app that the mydaemon's pid one more ... of the log file changed back to root who is the system-starting the ... I used in mydeamon script to change the owner of log file. ...
    (comp.unix.shell)
  • Re: [opensuse] Help - tmp full
    ... A log file with more then 23 GB! ... When root of file system is out of space then /tmp is useless too. ... It could be that enormous logs are result of mixed updates and factory usage. ... One can expect that default debug level of factory packages is elevated to ...
    (SuSE)
  • syslogd(8) Dropping Privs
    ... I made a quick change to syslogdso that it can drop root ... files and writing to users. ... modify your log file permissions appropriately. ... ttys generally are writeable by group tty. ...
    (FreeBSD-Security)