Outlook 2007 - shuts down when using

P

proulette

I just got 2007 last week on a brand new computer and sometimes when I open
Outlook and try to click on an e-mail, it just "disappears" not even an error
message saying it needs to shut down. Any ideas from anyone?
 
K

K. Orland

Are there any Office-related errors in your Application Event Viewer? Is this
an existing email you've already received or a new one? Did Outlook work
before this problem started?

Also, try the following:

With Outlook closed, search for the following files:

outcmd.dat
frmcache.dat
extend.dat
*.SRS

Rename them (example outcmd.dat_old) and then open Outlook to see if that
has resolved the problem. The above are hidden files so make sure that you
use Windows Explorer to unhide hidden files and folders and also make sure it
allows you to view known file extensions.

You also have the option of scanning your PST for errors as well.
 
P

proulette

I renamed all the files you suggested. Then reopened Outlook, clicked on an
e-mail and - poof, it was gone again.
I did look in the Applicatoin Event Viewer next and found this error:
The store C:\Documents and Settings\Pam\Local Settings\Application
Data\Microsoft\Outlook\Archive.pst has detected a catalog checkpoint

It says it is "ID 32"

This error is happening quite often and has been since I began using the new
program on a new computer last week. No rhyme or reason as far as I can tell.
sometime when I try to delete an e-mail - it is gone - sometimes when trying
to read a new e-mail - it's gone - sometimes closing an opened e-mail - it's
gone. By "it's gone" - I mean - it just closes, no warning, no nothing. the
first time I thought I just closed it in error. It is very random. Please
help!
 
P

proulette

I sent too soon, I should also tell you that there is another event
classified as an error - the previous was under information.

I'm getting "ID 35" Failed to determine if the store is in the crawl scope
(error=0x8001010d).

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp."

Thanks for your help!
Pam
 
K

K. Orland

The fix came from the MSDN forums here:
http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1214407&SiteID=1

Specifically:
Try to rebuild the index when you have WDS installed. If that doesn't
solve it the do these steps:

1. Stop Indexing service "cmd: net stop wsearch" and check in
TaskManager's process list that SearchIndexer.exe was really stopped.
2. Delete %SystemDrive%\ProgramData\Microsoft\Search\Data
\Applications\Windows (Vista) or %AllUsersProfile%\Application Data
\Microsoft\Search\Data\Applications\Windows (XP) folder with all its
files and subfolders.
3. Delete the following registry keys:
- "HKLM\Software\Microsoft\Windows Search\Applications\windows"
- "HKLM\Software\Microsoft\Windows Search\CatalogName\windows"
- "HKLM\Software\Microsoft\Windows Search\Databases\windows"
- "HKLM\Software\Microsoft\Windows Search\Gather\windows"
- "HKLM\Software\Microsoft\Windows Search\Gathering manager
\Applications\windows"
- "HKLM\Software\Microsoft\Windows Search\UsnNotifier\windows"
You'll have to change reg key ownership and change permission
first.
4. In registry in key "HKLM\Software\Microsoft\Windows Search"
switch "SetupCompletedSuccessfully" subkey to "0" - you'll have to
change reg key ownership and change permission first.
5. Start Indexing service back "cmd: net start wsearch"
6. Wait until "SetupCompletedSuccessfully" subkey switch back to 1.
If it's still "0" after 5 minutes, it means the setup is failed again.
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top