Serious error - outex.dll
1. 120 thin-clients
2. Windows Server 2003 running Terminal Services
3. Microsoft Office 2003 Professional running on Terminal Server
"Outlook experienced a serious error the last time the add-in 'outex.dll' was opened. Would you like to disable this add-in? To re-activate this add-in, click About Microsoft Outlook on the Help Menu, and then click Disabled Items."
Found nothing on any sites (yet) ... "Resiliency" solution does not solve this error.
2. Windows Server 2003 running Terminal Services
3. Microsoft Office 2003 Professional running on Terminal Server
"Outlook experienced a serious error the last time the add-in 'outex.dll' was opened. Would you like to disable this add-in? To re-activate this add-in, click About Microsoft Outlook on the Help Menu, and then click Disabled Items."
Found nothing on any sites (yet) ... "Resiliency" solution does not solve this error.
ASKER
Sorry, War1, no help what-so-ever.
ASKER
I NEED HELP WITH THIS ... ANY BODY OUT THERE???????
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
I have 120 thin client logging in to this terminal server. Are you suggesting that the only way to fix this is to perform the 7 step process,
at https://www.experts-exchange.com/questions/21918235/Outlook-2003-crashes-outex-dll-and-ntdll-dll-are-suspects.html,
on EACH AND EVERY PROFILE?
That borders on insane. Somebody's GOT to have a better solution than that!
Going off to try it on my "test" user's profile ... I'll let you know the outcome.
at https://www.experts-exchange.com/questions/21918235/Outlook-2003-crashes-outex-dll-and-ntdll-dll-are-suspects.html,
on EACH AND EVERY PROFILE?
That borders on insane. Somebody's GOT to have a better solution than that!
Going off to try it on my "test" user's profile ... I'll let you know the outcome.
No, I saying try which step works for your situation and use that one step to correct your problem.
ASKER
Interesting additional item ... just registering the DLLs ...
Startup Folder has the Outlook shortcut in it. Launching the session brings up Outlook without the error message. Closing Outlook and attempting to reopen causes error message to reappear. Tried re-launching Outlook with shortcut in Startup Folder, on Quick Launch toolbar, shortcut on desktop, and double-clicking on the actual executable, and STILL get the error message.
Quit session. Launch new session. Same story.
HUH?????
Startup Folder has the Outlook shortcut in it. Launching the session brings up Outlook without the error message. Closing Outlook and attempting to reopen causes error message to reappear. Tried re-launching Outlook with shortcut in Startup Folder, on Quick Launch toolbar, shortcut on desktop, and double-clicking on the actual executable, and STILL get the error message.
Quit session. Launch new session. Same story.
HUH?????
ASKER
If one of the steps work, you're suggesting to use it on all 120 profiles?
ASKER
OK.
I printed out the Q article and tried steps 1, 2, 4, 5, and 6. Since this is a production Terminal Server, steps 3 and 7 are NOT viable options. While step 3 works just fine, my client would be calling me every freakin' time they wanted to set the Out Of Office Assistant options. Step 6 is completely unacceptable.
After step 2, every OTHER time Outlook is opened, there is no error ... weird!
What, if anything, can you and the other experts find out from Microsoft as to what part of Office 2003 SP2 or SP3 could cause this behavior?
Hey, Moderator, can you lend an opinion here?
OutExDotDLL.doc
I printed out the Q article and tried steps 1, 2, 4, 5, and 6. Since this is a production Terminal Server, steps 3 and 7 are NOT viable options. While step 3 works just fine, my client would be calling me every freakin' time they wanted to set the Out Of Office Assistant options. Step 6 is completely unacceptable.
After step 2, every OTHER time Outlook is opened, there is no error ... weird!
What, if anything, can you and the other experts find out from Microsoft as to what part of Office 2003 SP2 or SP3 could cause this behavior?
Hey, Moderator, can you lend an opinion here?
OutExDotDLL.doc
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Oh ... one last item ... the fix, explained above, must be performed on each-and-every profile on the terminal server ... THANK YOU, MICROSOFT ... @#&*^@#*&^!@#&*!^@##^&@ ! ! ! ! ! !
Disable Outlook Addins. Go to Tools > Options > Other > Advanced Options > Addin Manager or COMM/Addins and disable the addins.
If you cannot open Outlook, do a search for and rename extend.dat file.
Hope this helps!
war1