 |
 | Home | Contact Us | FAQ | Search & Site Map | Link to Us |
 | Sign In | Join | Other 45 Sites in Network |
| HomeDiscussionsAccessExcelInfoPathOutlookPowerPointPublisherWordDirectoryUser Groups Related Topics Outlook ExpressInternet ExplorerWindowsMS Server ProductsMore Topics ... |
MS Office Forum / Outlook / Contacts / August 2006Scroll through Contacts causes Outlook 2000 to crash
When opening the address book and choosing my contacts list, Outlook freezes after scrolling down a few names. Shortly after an error message pops up to say that outlook.exe has generated errors and will be closed by Windows. Dr Watson reports the following: Application exception occurred: App: (pid=572) When: 09/09/2003 @ 09:58:19.961 Exception number: c00000fd (stack overflow) OS is Win2k sp4. Outlook 2000 sp3. The contacts folder has 371 entries. I have tried both Office Repair and Reinstall. Grateful for any help. Thanks. My apologies - I have jsut found the thread from 03Sept with same error. We run Exchange 5.5 with approx 60 users locally - almost 30,000 globally. Just this one user affected at this site. It was working fine until a short time ago. Only difference between this user and any other here is an ipaq synching to Outlook - but this was installed a long time ago and had no effect. Accessing the Contacts folder directly does not cause Outlook to crash. Only crashes when going through the "Address Book" either within a new message or from the menu bar. I do have a Dr Watson dump if you would like it. Rgds Alex >-----Original Message----- >When opening the address book and choosing my contacts [quoted text clipped - 18 lines] > >. Can you recall whether this ever happened before you applied SP3? If not, the more information you can give us about your installation the better. We're still looking for precise steps to repro this problem.  SignatureRuss Valentine [MVP-Outlook] > When opening the address book and choosing my contacts > list, Outlook freezes after scrolling down a few names. [quoted text clipped - 15 lines] > > Grateful for any help. Thanks. No - SP3 was installed several months before the problem occured. FYI I have finally cracked the problem. It appears that when the Address Book tried to display one particular entry on the address book list, the crash occured. The name started with an "E" so if I scrolled down from the beginning, as soon as it got to where this entry scrolled into the bottom of the window, Outlook crashed. If I jumped from the beginning of the list to entries beginning with "F" using the "Type name or select from list" box, there were no problems moving around the list until I scrolled up into the "E" entries. I examined the entry in question and could identify nothing wrong with it. It behaved normally in the Contacts folder with sending messages and display and showed no signs of corruption. Only in the Address Book listing display did it error. I have deleted the entry from Contacts and now the Address Book displays correctly. >-----Original Message----- >Can you recall whether this ever happened before you applied SP3? If not, [quoted text clipped - 22 lines] > >. So you have no way to determine what was corrupt about the entry in question? Just another random act of violence, then. SignatureRuss Valentine [MVP-Outlook] > No - SP3 was installed several months before the problem > occured. [quoted text clipped - 48 lines] > > > >. Same issue, deleted the offending contact. Freezes at the next contact after that. >-----Original Message----- >So you have no way to determine what was corrupt about the entry in [quoted text clipped - 53 lines] > >. What steps lead up to your problem? SignatureRuss Valentine [MVP-Outlook] > Same issue, deleted the offending contact. Freezes at > the next contact after that. [quoted text clipped - 67 lines] > > > >. >Same issue, deleted the offending contact. Freezes at >the next contact after that. [quoted text clipped - 4 lines] >> >>. Hi There, I had this exact issue and was able to resolve it. It did happen right after upgrading to SP3. We use Outlook 2000 with Exchange configured but I am sure this would work the same if it was just a .pst file. Seems like this problem though may be limited to just exchange clients and contact folders that are stored within the users mailbox on the exchange server. Before doing this export your contacts to a .pst file just in case. What I did was I went into the folder list in Outlook and highlighted Contacts so the contacts were listed. I selected all the contacts and pressed the delete key to move the contacts to the deleted items folder. Make sure that emptying the deleted items folder is TURNED OFF so when you close Outlook the contacts will remain in the deleted items folder. Close Outlook. Re-open Outlook. Now I have only had this problem once and have not been able to duplicate it again but what I did was then drag a few contacts at a time from the deleted items folder back into the Contacts folder. Once they were all moved back I then closed and re-opened Outlook again. I then went into the address book and was able to scroll to the bottom of the list without it freezing and then getting the Dr. Watson error. Now I didn't find this anywhere I was just lucky I guess but I am assuming the reason it worked was that when I moved the contacts completely out of the folder and then shut down Outlook while they were still in there possibly cleared some kind of corrupted index for the contacts folder because when Outlook shuts down it is supposed to do some kind of compact and repair type deal. Then once it was re-opened and the contacts moved from the deleted items to the contacts folder again it created a new index for the contacts folder. This is just a theory I have, I have no clue if that is how it works but it was the best I could come up with as an explanation as to why doing this would fix it. The reason stack overflow appears in the event viewer is that this corrupted index is probably loaded into RAM at some point. Anyways hope it works for you guys and maybe someone with a better understanding of programming can add their own theory or answer as to why this would indeed fix the issue. Sincerely, Lazy Government Worker |
Reply to this Message |
 Sign In
 Join
 My Latest Posts My Monitored Threads My Blog My Photo Gallery My Profile My Homepage Start New Thread Enable EMail Alerts Rate this Thread
|
©2008 Advenet LLC Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.