Is anyone running Outlook 2000 in Windows XP PRo???
Microsoft claims to support it.......
Here's my setup.
- Freshly partitioned and formated HD.
- Clean install of Windows XP Pro.
- Satelite USB software for internet connection.
- Completely web updated XP from Microsoft Update.
- Fresh install of Office 2000 (default)
- Completely web updated Office 2000 from Microsoft
Office Update.
- All other Office 2K apps work fine.
- Fresh Outlook config - with Personal Folder & Internet
Mail Account.
- Tested Outlook Express - works fine.
- All of the above done while logged on as Administrator.
I get the following message when trying to start Outlook
2000.
---------------------------
Microsoft Outlook
---------------------------
Cannot start Microsoft Outlook. Outlook cannot be
configured because Administrator privileges are required
for you to install some types of software on this
computer. Before you can use Outlook, you must either log
on to your computer as an Administrator and finish
configuring Outlook, or ask your System Administrator to
configure Outlook e-mail support for you.
---------------------------
OK
---------------------------
Thanx in advance for ANY response.
Stacey - 02 Jan 2004 22:43 GMT
I am using it .. and so is my entire company. No problems. Is the user that
you have a local administrator? Was Outlook installed from CD or from a
hard drive? You may need access to the install the first time you start it
up.
> Is anyone running Outlook 2000 in Windows XP PRo???
> Microsoft claims to support it.......
[quoted text clipped - 32 lines]
>
> Thanx in advance for ANY response.
Mark - 02 Jan 2004 22:56 GMT
Thanx Stacey
It is a stand alone system, and I'm using the
administrator account created during the Win XP Pro
installation. The office installation was done using the
Office 2000 Premium SR-1 CD. The CD was in the drive
during all Office/Outlook testing.
Mark
>-----Original Message-----
>I am using it .. and so is my entire company. No problems. Is the user that
[quoted text clipped - 40 lines]
>
>.
Kevin - 05 Jan 2004 19:21 GMT
While this KB article specifically mentions this exact problem on a WINNT machine, it might be worth a try for your problem:
http://support.microsoft.com/default.aspx?scid=kb;en-us;235530&Product=out2K