[Webinar] Streamline your web hosting managementRegister Today

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 3921
  • Last Modified:

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.
0
preshomesc
Asked:
preshomesc
  • 8
  • 3
2 Solutions
 
war1Commented:
Hello preshomesc,

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
0
 
preshomescAuthor Commented:
Sorry, War1, no help what-so-ever.
0
 
preshomescAuthor Commented:
I NEED HELP WITH THIS ... ANY BODY OUT THERE???????
0
Easily manage email signatures in Office 365

Managing email signatures in Office 365 can be a challenging task if you don't have the right tool. CodeTwo Email Signatures for Office 365 will help you implement a unified email signature look, no matter what email client is used by users. Test it for free!

 
war1Commented:
preshomesc,, outex.dll is part of Outlook of Office Assistance.  Turn Out of Office Assistant OFF and test.

If no joy, try the solution posted in this other question
http://www.experts-exchange.com/Applications/MS_Office/Outlook/Q_21918235.html
0
 
preshomescAuthor Commented:
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 http://www.experts-exchange.com/Applications/MS_Office/Outlook/Q_21918235.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.
0
 
war1Commented:
No, I saying try which step works for your situation and use that one step to correct your problem.
0
 
preshomescAuthor Commented:
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?????
0
 
preshomescAuthor Commented:
If one of the steps work, you're suggesting to use it on all 120 profiles?
0
 
preshomescAuthor Commented:
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
0
 
preshomescAuthor Commented:
How many points do I get for solving it myself?

The cumulative answers, thus far, were only pointers with no "cookbook" solution.

The closest answer referred to the "Resiliency" registry entry.  The only problem ... you MUST have the OUTEX.DLL in "disabled" mode to find it.  ie - if you Enable the Add-In, all traces of what you're looking for in the registry are deleted by Windows.

You must:
1. leave it diabled
2. close Outlook
3. launch Regedit
4. highlight My Computer
5. click Edit / Find
6. enter Resiliency in the "Find what:" box
7. click the "Find Next" button

When the "Find Next" function finds an instance of "Resiliency" that is a sub-item of Outlook, you'll need to right-click on the "Resiliency" item and choose "Delete" ...

You should, again, invoke the "Find Next" function, using the F3 key.  If the function finds another instance of "Resiliency" that is a sub-item of Outlook, you'll need to right-click on the "Resiliency" item, choose "Delete", and repeat this step.  Repeat this step until all instances of the Outlook associated "Resiliency" items are completely removed from the registry.

Now for the "Andy Rooney" questions: Why is it that Microsoft caused this to happen in the first place?  And why is it that Microsoft doesn't have a solution posted and a patch to download?  What about the poor innocents (unfortunately-dumb-end-users) that have NO chance at solving this, should it happen to them?

Thanks for the pointers ... but no points awarded this time ... unless I get them.
0
 
preshomescAuthor Commented:
Oh ... one last item ... the fix, explained above, must be performed on each-and-every profile on the terminal server ... THANK YOU, MICROSOFT ... @#&*^@#*&^!@#&*!^@##^&@ ! ! ! ! ! !
0

Featured Post

Free tool for managing users' photos in Office 365

Easily upload multiple users’ photos to Office 365. Manage them with an intuitive GUI and use handy built-in cropping and resizing options. Link photos with users based on Azure AD attributes. Free tool!

  • 8
  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now