S
SG
Hi,
I Installed Office XP pro on a Win 2000 Pro workstation with service
pack 4. When a USER opens outlook for the first time, he gets the
message "Microsoft Outlook has not been installed for the current
user. Please run setup to install this application." Outlook then
closes. If the user reopens it again, outlook will open without
bitching on all subsequent times. If PC is left inactive for awhile,
and then I attempt to open outlook, it will show the same message,
close, and if i open it again, no problem.
As far as I can tell, there is a KB article on that but it applies to
Office 2003. Nevertheless, I tried removing and reinstalling Office
XP, it stopped doing it for awhile and now its back at it again. It
therefore turned out to be a BIG waste of time. Note that I did not
perform any weird installations, like for certain users only, and that
that perticular user was created well before office was installed for
the first time.
Having installed outlook successfully under win 2k before, I suspect
the new Win 2k SP4 to be the issue. Any suggestions?
I Installed Office XP pro on a Win 2000 Pro workstation with service
pack 4. When a USER opens outlook for the first time, he gets the
message "Microsoft Outlook has not been installed for the current
user. Please run setup to install this application." Outlook then
closes. If the user reopens it again, outlook will open without
bitching on all subsequent times. If PC is left inactive for awhile,
and then I attempt to open outlook, it will show the same message,
close, and if i open it again, no problem.
As far as I can tell, there is a KB article on that but it applies to
Office 2003. Nevertheless, I tried removing and reinstalling Office
XP, it stopped doing it for awhile and now its back at it again. It
therefore turned out to be a BIG waste of time. Note that I did not
perform any weird installations, like for certain users only, and that
that perticular user was created well before office was installed for
the first time.
Having installed outlook successfully under win 2k before, I suspect
the new Win 2k SP4 to be the issue. Any suggestions?