• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 2693
  • Last Modified:

How to finally stop Outlook errors, it's been reoccuring for months, several EE questions.

Hi everyone, I'd really appreciate some input as I'm losing my mind trying to troubleshoot this issue for a client.  I have a client who runs Outlook 2003.  About 4 months ago they got the first major error message that was preventing them from doing a send and recieve.  You could not even do an export of the data, it would give an "out of memory" error even though the machine was fine, plenty of RAM, etc.  We ended up making a new PST file and copying and pasting essential messages and exporting everything else to a .CSV file because like I said, it would give the out of memory error when trying to export to a PST.  

Fast forward a few months, the problem comes back . . . I started a second thread on EE and tried everything and low and behold, what ends up fixing it was installing the latest service pack for Office 2003?!?!?!??!  That fixed the problem for a few days.

Now, the problem is back again with two different messages.  For two weeks now the client gets one of two messages when doing a "send and recieve" within Outlook.  They either get "0x800CC13" or "0x800CC01B" and cannot do a send/recieve.  THE ODD THING IS THIS IS NOT ALWAYS THE CASE.  SOMETIMES OUTLOOK SENDS AND RECIEVES FINE AND SOMETIMES IT GIVES THESE ERRORS.  

I would assume if the PST file was corrupted this would come up all the time.  Could the Outlook program itself be corrupted?  The only third party variable I can come up with is the client does have a Blackberry they are syncing up to it.  Could the blackberry be transfering over corrupted data?  I'm at a loss here and the client is not happy as this has been happening on and off for months and I'm trying to find a long term fix.  

I'd appreciate any and all help!  I think the main factor that is puzzling to me is that the error is "on and off" . . . it doesn't ALWAYS do it.  
0
Jsmply
Asked:
Jsmply
  • 9
  • 2
  • 2
  • +1
3 Solutions
 
Gary CutriCommented:
From memory we use to get the 0x800CC13 error when Outlook couldn't connect to the server.  On one site I remember it was intermittently caused by their antivirus\firmware.  If the users PST file is close to or over 2GB this will cause a number of issues.
0
 
JsmplyAuthor Commented:
No, it's been reduced significantly and not at 2 GB.  I've also disabled the Norton scanning of e-mail messages.  Any other ideas?
0
 
JsmplyAuthor Commented:
Also, should this post be in the zone "Outlook" or "Outlook Groupware"  ?  I think I accidentally put it in Groupware.  If a mod would like to move it, please feel free!
0
Industry Leaders: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

 
JsmplyAuthor Commented:
Just to post further . . . I don't see how it could be an anti-virus/firmware issue because it won't let me export to a PST file the last times these errors occured?
0
 
westoneCommented:
You don't need me to tell you that disabling AV scanning of e-mail is a bad idea. Turn it off when the error occurs to see if it resolves the problem, but don't leave it off long term.

A new PST file has been created, so corruption of the PST does not seem likely, although it is possible one particular item in the data file is contributing to the error, and it was moved over into the new file. Perhaps creating a new PST with nothing in it, and making it the default receiving location may affect the error. Treat the existing PST as an archive.

The long time between occurrences of the error is huge problem in troubleshooting.
0
 
westoneCommented:
Any entries in the Event logs when the error occurs?
0
 
JsmplyAuthor Commented:
Thanks Westone, it was just off for troubleshooting.  

Regarding the next part, yes a new PST was made and messages were copied and pasted into the new file.  The problem is Outlook goes nuts when this happens.  I can't create a new .PST file and leave this .PST file open.  Once the PST starts having issues, it won't let me create a new PST, remove this PST, etc as long as that PST is open.  I can't even open it again in outlook.  The only way to even get it open to work with it or copy messages out is to rename whatever the PST file is to the current new PST file name.  Outlook won't even import it once the PST goes nuts.  

Nothing significant in the events log.  I can't really find anything on those error messages on Google either.
0
 
JsmplyAuthor Commented:
0
 
jderaCommented:
A few things, somewhat basic, but cannot elminate some possibilities.

1. Have you tried Detect and Repair?
2. If #1 does nothing, try these:
       Start>Run>Outlook.exe /cleanprofile
       Start>Run>Outlook.exe /clean rules
       Start>Run>Outlook.exe /cleanviews

3. If #2 still does not work, try to run Outlook in safe mode, the command is Start>Run>Outlook.exe /safe and test that.

4. Is no go, then recreate the profile.

5. Last option is just uninstall and re-install Outlook.

6. Outside of those Outlook scenarios, 70% of all IT issues are hardware related problems.  Next things I would do is replace the NIC if possible or replace the network cable that the user is using and get a known good cable.
0
 
JsmplyAuthor Commented:
The user is a laptop and always wireless. The internet and network connection (browsing, file shares, printing, etc) always works fine though. Woudlnt that mean its not the wireless card?  Could outlook itself be the problem?  Anyone seen that?  I figured the service pack upgrade would have fixed that though.
0
 
jderaCommented:
Well the best test for this would be to take it off the wireless for a week and see if the error keeps happening if not, then the issue is obvious its the wireless connection causing the problem.
0
 
JsmplyAuthor Commented:
Can't really do that, the user is always on the go and is hard headed. I have tested it myself though when its been in my hands and I did get the same thing on a nic.
0
 
JsmplyAuthor Commented:
Looks like I finally got this resolved.  I updated the user from Outlook 2003 to 2007 and used the same .PST file that was giving me errors and thus far I've had no problems!  I guess it was something in the Outlook version?  The service pack update on 2003 didn't seem to fix it, but it's been a few weeks now and no problems on the 2007, so I'm going to close this.  Thanks!
0
 
JsmplyAuthor Commented:
Everything else failed, but your last option of reinstalling Outlook (except with the newer version) took are of it!  Thx!
0

Featured Post

Windows Server 2016: All you need to know

Learn about Hyper-V features that increase functionality and usability of Microsoft Windows Server 2016. Also, throughout this eBook, you’ll find some basic PowerShell examples that will help you leverage the scripts in your environments!

  • 9
  • 2
  • 2
  • +1
Tackle projects and never again get stuck behind a technical roadblock.
Join Now