Software

Ask something
Discussion Locked

Office 2003 Outlook stops responding

0 helpful
5 replies

by sceva 1 view

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

I just upgraded about 20 Windows 2000 Pro workstations (all with same patches, programs, etc) from Office 2000 Pro to Office 2003 Pro. Everything is fine except on ONE machine Outlook is malfunctioning. It stops responding with the "Configuring Outlook Accounts" or "Migrating Account Setting" on the screen. It also stops responding if I try and access the mail profile using the control panel, so I can't remove the profile that way.

I have tried opening Outlook in safe mode, detect and repair Office, uninstall/reinstall office 2003, (uninstall O2003, reinstall O2000, uninstall 02000, reinstall o2003), running outlook /cleanfreebusy, but nothing has seemed to help.

I can go into an admin account and set up a mail profile (where one did not exist prior) and that will work.

I have found several posts with this problem on the internet, but most of them are unanswered, and I have tried the couple of suggestions listed above, but to no avail.

Thanks for the help.

5 replies

by 1stladytech

Have you checked the size of the pst file? If it is to large, it can give you trouble. Also try to run the pst file checker and repair tool.

V

by sceva

Didn't work. It affects any user who logs in, even a brand new user. Their accounts work fine on other similar computers.

by edlockett

Try the following :
c:\documents and settings\\application data\microsoft\outlook rename to outlook1
c:\documents and settings\\local settings\application data\microsoft\outlook rename to outlook1
Then try to start outlook. Hopefully this will get around your problem, you can then import the old .pst file (from the second directory you renamed above).

Hope this makes sense. :-)
Ed

by sceva

See above. I ended up doing a clean install of Windows and the applications and it is ok now. It must have been something installed on the computer that was causing the problem.

This discussion is closed to new replies.