• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1320
  • Last Modified:

Outlook 2003 error resolving name (Run DLL as an App)

Hello,
I am running Windows Small Business Server 2003 on the server.  Other users (Windows XP SP2) still running fine and connecting to Exchange fine.
One user has new (previously used at home by owner of company) pc (windows XP SP2), connected to domain fine.  Can setup a POP3 account, no problem.  When I try to resolve name to exchange server (using cached exchange mode or not) I get following error.
Run DLL as an APP which shows in event viewer as such.
Application Error
Faulting application rundll32.exe, version 5.1.2600.2180, faulting module msmapi32.dll, version 11.0.8002.0, fault address 0x00022026.

I have the dump file if anyone wants to see it.

The profile is then corrupted and I must remove profile and recreate a new one to do anything further with Outlook, even open the program for just the POP3 account.

What I have done:

I have uninstalled and reinstalled Outlook.

I updated to latest service packs and all security updates done for OS and Office.

Have also tried a different version of MSMAPI32.DLL file (one that was working on another station) originally had 11.0.8164.0.

I added Outlook program as an exception in firewall.

Tried to resolve other exchange names also, and logged on as other users and tried to resolve other names and the original name.  Same errors occurred.

Hope I gave the right info,
4rg
0
4rg
Asked:
4rg
  • 4
  • 4
1 Solution
 
4rgAuthor Commented:
More information,
Great, now I find out that client has had an issue (still pending) with Trojan_Downloader_Zlob.  Spysweeper finds pieces of it in various different places every day.  Mostly having to do with ActiveX_Access Enhancement 1.15 program that got installed when trojan issue began.  We are working with Webroot now to try and see why it keeps coming back.  
Original problem was with other user before it was on domain and they thought that it wouldn't influence when another user logged on to system.
I believe this could well be causing my issue.
Any comments?  Or just wait until this issue is resolved and then try to resolve name again?
Any thoughts are welcomed.
JG
0
 
Jeffrey Kane - TechSoEasyPrincipal ConsultantCommented:
"connected to domain fine"

If you connected to the domain using the SBS method of http://<servername>/connectcomputer then you wouldn't need to do anything at all with the Windows Firewall settings.  That's handled automatically by SBS.  SBS will also auto-configure the Exchange mailbox in Outlook.  Assuming that you didn't use this method, you now need to follow the steps outlined in http://sbsurl.com/rejoin to fix it.

Then... don't go messing around with MAPI versions... that will only cause you more problems.  The "11.0.8164.0" version is for MOOL (Microsoft Office Outlook Live), not regular Outlook 2003.  If you are having problems with Outlook running, just run the Detect & Repair from the Help menu and it'll fix itself.  http://support.microsoft.com/kb/938802 is Outlook 2003 SP3 which can be applied afterwards and that'll bring you back to MAPI v11.0.8002.0 which is correct for that product.

Also... why are you configuring a POP3 Account?  

Jeff
TechSoEasy
0
 
4rgAuthor Commented:
Jeff,
I had only set up a POP3 account to see if I could.  It worked fine and I removed.

I had connected properly and it did not have an exchange mailbox.

Only renamed old msmapi32.dll and copied and pasted other one because the other users on the network were all using 11.0.8002.0 and this system had 11.0.8164.0.  I understand you say this is for MS Outlook Live.  Well the installed program is Outlook 2003 and it is from Office 2003 Basic OEM.  How it got that version of MAPI, I have no idea.  In any case, I changed it back after the test.
Any other ideas...
The note I added about the spyware/malware/virus has been cleared up and had 3 days of clean scans.
JG
0
Concerto Cloud for Software Providers & ISVs

Can Concerto Cloud Services help you focus on evolving your application offerings, while delivering the best cloud experience to your customers? From DevOps to revenue models and customer support, the answer is yes!

Learn how Concerto can help you.

 
Jeffrey Kane - TechSoEasyPrincipal ConsultantCommented:
Did you run detect & repair as I had suggested?  Did you try applying Office 2003 SP3 as I had suggested?

Jeff
TechSoEasy
0
 
4rgAuthor Commented:
Jeff,
Yes, prior to uninstalling and reinstalling Outlook, I had tried safe mode and detect and repair (more than once).  Also I had mentioned that all my service packs and security updates had been applied in the original question.
What do you think of the possibility of a damaged registry due to the Trojan_Downloader_Zlob?
jlg
0
 
Jeffrey Kane - TechSoEasyPrincipal ConsultantCommented:
Sorry, but "latest service packs" isn't always a specific description.  Considering that SP3 was released just a couple of weeks ago, it's not a given that was what you had applied.  

It's very possible that you did not completely remove the Trojan.  For this reason, I would strongly suggest that you do a complete fresh reinstallation of your system (reformatting the hard drive), since it's been at least a week now since you've discovered it, and it could very well have replicated itself into other parts of your system without you knowing.

Jeff
TechSoEasy
0
 
Jeffrey Kane - TechSoEasyPrincipal ConsultantCommented:
FYI, if you do completely reinstall the system, be sure to use a different computer name than before so that SBS will recognize it properly as a newly installed system.

Jeff
TechSoEasy
0
 
4rgAuthor Commented:
I'm going to wrap this question up and give the points to Jeff TechSoEasy for the input.  I wiped the system and had no issues.  Must have been a corrupted registry as we suspected.  
0

Featured Post

Free Tool: Path Explorer

An intuitive utility to help find the CSS path to UI elements on a webpage. These paths are used frequently in a variety of front-end development and QA automation tasks.

One of a set of tools we're offering as a way of saying thank you for being a part of the community.

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