RE-POST: Office 2003 Always Configures when Starting as Non-admin

[TML]

I've installed Office Professional 2003 on an brand new Windows Server 2003
machine, as local administrator.

For security purposes, I created another user and put that user in the Power
Users group (it's definitely not in the Administrators group). The first
time I log in as this new user and run one of the Office 2003 apps, I get an
installer dialog telling me that Windows is configuring Office. I expect
this.

However, whenever I try to run our in-house developed VB6 applications (the
EXE files were simply copied, not installed through Windows installer), I
always get the installer dialog box saying:


"Please wait while Windows configures Microsoft Office Professional Edition
2003"

After 5 or 8 iterations of this dialog box and progress meter, the
application open and function just fine. Our VB6 apps have no connection
whatsoever with Office, let along Office 2003.

Further, if I take the new user account and put it in the Administrators
group, when I log on as that user, the VB6 applications run without any
problems or installer dialog boxes. Or, if I run the VB6 apps as the local
administrator, no problems either.

Any help/suggestions??????

Thanks

 

[Gordon Fecyk]

"Please wait while Windows configures Microsoft Office Professional
Edition

2003"

After 5 or 8 iterations of this dialog box and progress meter, the
application open and function just fine. Our VB6 apps have no connection
whatsoever with Office, let along Office 2003.

When you installed Office 2003, did you remove the temporary installation
files? If you did, you'll need to have the Office CD-ROM inserted when a
new user starts an Office app (or component) for the first time.

Office Setup asks you if you want to remove the temporary files after
installation. I would suggest, the next time you install Office 2003, you
leave those files in place. Limited users will be able to first-time
configure Office from those files instead of from the CD-ROM if they're
present.

Alternately, if there's an administrative installation of Office on a
server, install Office from there. But you need a special version of the
Office installation media to do an administrative installation, plus a
bulk-license product key for it.

 

[Gordon Fecyk]

"Please wait while Windows configures Microsoft Office Professional
Edition

2003"

After 5 or 8 iterations of this dialog box and progress meter, the
application open and function just fine. Our VB6 apps have no connection
whatsoever with Office, let along Office 2003.

When you installed Office 2003, did you remove the temporary installation
files? If you did, you'll need to have the Office CD-ROM inserted when a
new user starts an Office app (or component) for the first time.

Office Setup asks you if you want to remove the temporary files after
installation. I would suggest, the next time you install Office 2003, you
leave those files in place. Limited users will be able to first-time
configure Office from those files instead of from the CD-ROM if they're
present.

Alternately, if there's an administrative installation of Office on a
server, install Office from there. But you need a special version of the
Office installation media to do an administrative installation, plus a
bulk-license product key for it.

 

[Gordon Fecyk]

"Please wait while Windows configures Microsoft Office Professional
Edition

2003"

After 5 or 8 iterations of this dialog box and progress meter, the
application open and function just fine. Our VB6 apps have no connection
whatsoever with Office, let along Office 2003.

When you installed Office 2003, did you remove the temporary installation
files? If you did, you'll need to have the Office CD-ROM inserted when a
new user starts an Office app (or component) for the first time.

Office Setup asks you if you want to remove the temporary files after
installation. I would suggest, the next time you install Office 2003, you
leave those files in place. Limited users will be able to first-time
configure Office from those files instead of from the CD-ROM if they're
present.

Alternately, if there's an administrative installation of Office on a
server, install Office from there. But you need a special version of the
Office installation media to do an administrative installation, plus a
bulk-license product key for it.

 

[Gordon Fecyk]

"Please wait while Windows configures Microsoft Office Professional
Edition

2003"

After 5 or 8 iterations of this dialog box and progress meter, the
application open and function just fine. Our VB6 apps have no connection
whatsoever with Office, let along Office 2003.

When you installed Office 2003, did you remove the temporary installation
files? If you did, you'll need to have the Office CD-ROM inserted when a
new user starts an Office app (or component) for the first time.

Office Setup asks you if you want to remove the temporary files after
installation. I would suggest, the next time you install Office 2003, you
leave those files in place. Limited users will be able to first-time
configure Office from those files instead of from the CD-ROM if they're
present.

Alternately, if there's an administrative installation of Office on a
server, install Office from there. But you need a special version of the
Office installation media to do an administrative installation, plus a
bulk-license product key for it.

 

[Gordon Fecyk]

"Please wait while Windows configures Microsoft Office Professional
Edition

2003"

After 5 or 8 iterations of this dialog box and progress meter, the
application open and function just fine. Our VB6 apps have no connection
whatsoever with Office, let along Office 2003.

When you installed Office 2003, did you remove the temporary installation
files? If you did, you'll need to have the Office CD-ROM inserted when a
new user starts an Office app (or component) for the first time.

Office Setup asks you if you want to remove the temporary files after
installation. I would suggest, the next time you install Office 2003, you
leave those files in place. Limited users will be able to first-time
configure Office from those files instead of from the CD-ROM if they're
present.

Alternately, if there's an administrative installation of Office on a
server, install Office from there. But you need a special version of the
Office installation media to do an administrative installation, plus a
bulk-license product key for it.

 

[Gordon Fecyk]

"Please wait while Windows configures Microsoft Office Professional
Edition

2003"

After 5 or 8 iterations of this dialog box and progress meter, the
application open and function just fine. Our VB6 apps have no connection
whatsoever with Office, let along Office 2003.

When you installed Office 2003, did you remove the temporary installation
files? If you did, you'll need to have the Office CD-ROM inserted when a
new user starts an Office app (or component) for the first time.

Office Setup asks you if you want to remove the temporary files after
installation. I would suggest, the next time you install Office 2003, you
leave those files in place. Limited users will be able to first-time
configure Office from those files instead of from the CD-ROM if they're
present.

Alternately, if there's an administrative installation of Office on a
server, install Office from there. But you need a special version of the
Office installation media to do an administrative installation, plus a
bulk-license product key for it.

 

[Gordon Fecyk]

"Please wait while Windows configures Microsoft Office Professional
Edition

2003"

After 5 or 8 iterations of this dialog box and progress meter, the
application open and function just fine. Our VB6 apps have no connection
whatsoever with Office, let along Office 2003.

When you installed Office 2003, did you remove the temporary installation
files? If you did, you'll need to have the Office CD-ROM inserted when a
new user starts an Office app (or component) for the first time.

Office Setup asks you if you want to remove the temporary files after
installation. I would suggest, the next time you install Office 2003, you
leave those files in place. Limited users will be able to first-time
configure Office from those files instead of from the CD-ROM if they're
present.

Alternately, if there's an administrative installation of Office on a
server, install Office from there. But you need a special version of the
Office installation media to do an administrative installation, plus a
bulk-license product key for it.

 

[Gordon Fecyk]

"Please wait while Windows configures Microsoft Office Professional
Edition

2003"

After 5 or 8 iterations of this dialog box and progress meter, the
application open and function just fine. Our VB6 apps have no connection
whatsoever with Office, let along Office 2003.

When you installed Office 2003, did you remove the temporary installation
files? If you did, you'll need to have the Office CD-ROM inserted when a
new user starts an Office app (or component) for the first time.

Office Setup asks you if you want to remove the temporary files after
installation. I would suggest, the next time you install Office 2003, you
leave those files in place. Limited users will be able to first-time
configure Office from those files instead of from the CD-ROM if they're
present.

Alternately, if there's an administrative installation of Office on a
server, install Office from there. But you need a special version of the
Office installation media to do an administrative installation, plus a
bulk-license product key for it.

 

[Gordon Fecyk]

"Please wait while Windows configures Microsoft Office Professional
Edition

2003"

After 5 or 8 iterations of this dialog box and progress meter, the
application open and function just fine. Our VB6 apps have no connection
whatsoever with Office, let along Office 2003.

When you installed Office 2003, did you remove the temporary installation
files? If you did, you'll need to have the Office CD-ROM inserted when a
new user starts an Office app (or component) for the first time.

Office Setup asks you if you want to remove the temporary files after
installation. I would suggest, the next time you install Office 2003, you
leave those files in place. Limited users will be able to first-time
configure Office from those files instead of from the CD-ROM if they're
present.

Alternately, if there's an administrative installation of Office on a
server, install Office from there. But you need a special version of the
Office installation media to do an administrative installation, plus a
bulk-license product key for it.