Outlook 2010 will opens but immediately errors after moving PST file
I installed Outlook 2010 on one PC. I decided to try to use a network location instead of the local PC for backup reasons. I know this didn't work well with earlier versions of Outlook. It ran fine for a few weeks and then I got a back-up error saying the PST file was corrupt. But the user was still working fine with his file. So I decided to move it back to the local PC today. So I copied the outlook file, renamed it, and placed it in the usual folder on the PC. Then I changed that file to the default file and also the folder where email is delivered. The next time I opened Outlook it opens and then starts to send/receive and errors and has to close. I have tried to change the default file back and create a new one. I get the same result. Not I have a user down.
Please help.
Please help.
spiderwilk007
What is the send recieve error you are getting?
Have you checked the structure of the PST file using ScanPST ==> http://support.microsoft.com/kb/287497
Hope this helps
Priz
Hope this helps
Priz
Try to repair the PST with Scanpst.exe tool and check.
The Scanpst.exe file for Outlook 2010 is is typically located in the following folder:
<disk drive>\Program Files\Microsoft Office\Office14
To run the Inbox Repair Tool, follow these steps:
Double click the Scanpst.exe file to open the Inbox Repair Tool.
Type the path and the file name of the personal folders (.pst) file or click Browse to locate the file by using the Windows file system.
Click Start.
The Scanpst.exe file for Outlook 2010 is is typically located in the following folder:
<disk drive>\Program Files\Microsoft Office\Office14
To run the Inbox Repair Tool, follow these steps:
Double click the Scanpst.exe file to open the Inbox Repair Tool.
Type the path and the file name of the personal folders (.pst) file or click Browse to locate the file by using the Windows file system.
Click Start.
ASKER
A box that says "Microsoft Outlook has encountered a problem and needs to close" pops up right after Outlook launches.
It sounds like you need to recreate the users mail profile, Try creating it with a new pst and then open the old one and copy the items up. Close Outlook, go to control panel double click the mail icon, click Show Profiles, add a new profile, click "Always use this profile" and select the new profile you created. Click "OK" and then re-open Outlook and proceed to setup the Email account from scratch. Once the email account is setup, from the file menu open "browse to the old .pst file" and then open it. You can then begin to copy his items up to the currnet mail, calendar, tasks and contacts folders. Once completed close the old .pst file by right clicking and "close folder".
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
spiderwilk007: I just tried this. When I open Outlook with the fresh profile I get the same error and it still closes right away.
ASKER
Pr1z: The repair Outlook worked and gave me a fresh pst file but it was placed in mydocs (folder that is on server). So I created a new pst file in the Outlook folder and then imported all the email from the original pst file into there. Then I set it as the default file and told set it to deliver mail there as well. Then guess what? It just gave me the exact error I started with. Why cant I create, move, or copy a pst file into the Outlook folder on the local disk of the PC?
Do you have a group policy in place that is preventing it?
Why cant I create, move, or copy a pst file into the Outlook folder on the local disk of the PC?
file sharing issue...go to the lower right hand corner of outlook and right click over "Connected to Microsoft Exchange" and select work offline....do what you want..delete..move..whatev
file sharing issue...go to the lower right hand corner of outlook and right click over "Connected to Microsoft Exchange" and select work offline....do what you want..delete..move..whatev
ASKER
I ran repair again after I chose my default files and locations and it appears to be working fine now.