Abort loop

[Howard Brazee]

I have Windows 2003 on a W2K machine.
When I start Outlook it appears to start - and I can see new messages, but then
I get a window:

Microsoft Office Outlook has encountered a promise and needs to close.

The "Please tell Microsoft about the problem" error report is short. I have to
uncheck the restart Outlook or it continues to happen.


Checking the event viewer, I find:

Information:
Bucket 124789978, bucket table 1, faulting application outlook.exe, version
11.0.6353.0, stamp 408f2937, faulting module outex.dll, version 11.0.6354.0,
stamp 409a5b8b, debug? 0, fault address 0x0006c05b.


Error
Faulting application outlook.exe, version 11.0.6353.0, stamp 408f2937, faulting
module outex.dll, version 11.0.6354.0, stamp 409a5b8b, debug? 0, fault address
0x0006c05b.

We've uninstalled Office several times - and at least one time it ran - until we
installed the critical upgrades.

 

[Guest]

What are the event id numbers and sources?

 

[Brian Tillman]

I have Windows 2003 on a W2K machine.
When I start Outlook it appears to start - and I can see new
messages, but then I get a window:

Microsoft Office Outlook has encountered a promise and needs to close.

Does the problem happen if you start Outlook in safe mode?

 

[Howard Brazee]

On 29-Jun-2005, "=?Utf-8?B?S09ybGFuZA==?=" <[email protected]>
wrote:

Error = 1000, Microsoft Office 11
Information = 1001, Microsoft Office 11

 

[Howard Brazee]

I just tried something.

The Outlook icon on my W2K desktop points to:
"C:\Program Files\Microsoft Office\OFFICE11\OUTLOOK.EXE" /recycle


I did a search on Outlook which didn't find this, but instead found one in
C:\WINNT\Installer\$PatchCache$\Managed\9040110900063D11C8EF10054038389C\11.0.5614

I clicked on that, and Outlook started up successfully.

I tested it, it still worked. I closed it and then started the Outlook on my
desktop. It aborted again.

I'll continue to use the web version of Exchange.

 

[Howard Brazee]

Does the problem happen if you start Outlook in safe mode?
--

Same thing.

We tried installing again after deleting some files. The abort still happened.
Then I looked for OUTLOOK.EXE and found the following:
Volume in drive C has no label.
Volume Serial Number is EC2D-38F5

Directory of
C:\WINNT\Installer\$PatchCache$\Managed\9040110900063D11C8EF10054038389C\11.0.5614

07/14/2003 10:45p 196,152 OUTLOOK.EXE
1 File(s) 196,152 bytes

Directory of
C:\WINNT\Installer\$PatchCache$\Managed\9040110900063D11C8EF10054038389C\11.0.6361

04/28/2004 12:10a 196,296 OUTLOOK.EXE
1 File(s) 196,296 bytes

Directory of C:\Program Files\Microsoft Office\OFFICE11

04/28/2004 12:10a 196,296 OUTLOOK.EXE
1 File(s) 196,296 bytes

Total Files Listed:
3 File(s) 588,744 bytes
0 Dir(s) 3,010,363,392 bytes free

Actually, the search results did not find the one in OFFICE11 (anybody know why
not?), but when I clicked on the other two, I got different results. The
04/28/2004 version aborted. The 07/14/2003 runs Outlook 2003 just fine.

I don't know whether this is a safe thing or not.

 

[Howard Brazee]

Interesting, when I use the W2K search looking for OUTLOOK, I get the first two
files below (and some others). If I look for OUTLOOK.EXE, it finds all three
files below. There is some search rule that I am not familiar with here.

 

[Brian Tillman]

The 04/28/2004 version aborted. The 07/14/2003
runs Outlook 2003 just fine.

The files in the Windows\Installer folder are placed there by Service Packs
and Hotfixes. My version of Outlook.exe is also dated 04/28/2004, is
196,296 bytes, but its version is 11.0.6353. This is an SP1 Outlook 2003.

 

[Howard Brazee]

Something weird.


It appears that if I open Word and use Word to e-mail a message to myself, and
keep Word open, I can open the proper desktop Outlook icon and it works just
fine.

My guess is that Outlook and Office aren't talking to each other correctly.

 

[Bob I]

I suggest Help, Detect and Repair.

 

[Howard Brazee]

I suggest Help, Detect and Repair.

That was the first thing we did. And maybe the 5th and 8th. But we've only
uninstalled and reinstalled it 3 times since the problem began.