Hi,

I currently have some issues that suddenly appeared after a potential error on my part (more further down)
I am running Vista and Office 2007 Small Business on my laptop.

1) My Outlook 2007 no longer opens. I just get the blank blue screen with the yellow Outlook 2007 stamp and I can't close it normally. When I force it closed via Task manager and then try again, I get an option to start in Safe mode, and I can open it in safe mode. From there I ran the diagnostics option under the help menu. No issues reported. I don't know what else I can do from within Outlook in Safe mode to rectify things ?

I ran the repair option for the Office 2007 package from the Add and remove window under the Control panel, but the Outlook start issue remains.

2) The other issue I've noted is that 50-70 % of CPU capacity is constantly used up by SearchIndexer.exe. No corresponding disc activity indicated though.
This also affects the general performance speed of the laptop of course.

Now, to my "potential error"

From an previous laptop running XP I remembered being able to improve processing performance by specifying the Virtual memory to be located on a different disk from the one where the OS is. So I tried doing the same in Vista, and after a restart I got the problems above. All other programs seem to work fine (although a bit slower), including other Office components.
Trying to remember what I actually did, and in what sequence, I am not 100 % sure that I actually closed Outlook 2007 before implementing the change in location of the Virtual memory.
I've reset the Virtual memory setting as they were originally, but Office 2007 still won't open, other than in safe mode.

I'm hoping someone has a quick and simple solution for me

Or will I have to remove and reinstall the complete Office package ?

Grateful for suggestions

Yeah.. I thought you may have hinted at the fact that Outlook was running when searchindexer.exe was disabled, but I wasn't sure of that. Thanks for clarifying.


Please read through this thread and try some of the suggestions and see if they help you identify anything further. It is very long and there are several knowledgeable people with some valuable information in there.

http://social.msdn.microsoft.com/Forums/en...3e-dcca7939e8b4

I would suggest that you first get the surface scan done on your hard drive.

You can read here about how to access the system recovery options that is probably pre-installed on your computer:

http://windowshelp.microsoft.com/Windows/e...351033.mspx#EHF

Expand the section, "How do I access the system recovery options menu," and follow the instructions for pre-installed computers.

Once you get to the system recovery options menu you can open a "command prompt." At the command prompt you can try the chkdsk /r command again. If that does not force the scan, try chkdsk /r /p. Note that there are spaces before those /r and /p flags.

Doing the chkdsk from the "recovery console," is a better way anyways because you'll get to see more detail about what is happening without it scrolling off the screen and being gone forever.

If the surface scan finds any "bad clusters," then this could be one of the problems with the searchindexer.


This post has been edited by appleoddity: Aug 1 2009, 09:54 AM