Outlook 2003: Run Dll error when changing proxy settings for excha

[jmfgegr]

I have a remote user that cannot remotely connect to our single exchange 2007
server with outlook 2003 (OS = Windows XP SP3). She has an HP\Compaq nc6220
laptop which is about 3 years old. She was configured internally here when
setup, with a rpc over http connection. When she attempted to login to
outlook at her home office, she could not conect. After further research,
her exchange proxy settings were incorrect - under proxy authentication
settings she had NTLM authentication instead of basic.

Here's the problem: In the drop down, when I try to change from NTLM to
basic, I receive a pop-up error message that reads the following:

"An exception occurred while trying to run
"C:\WINDOW\system32\shell32.dll,Control_RunDLL
"C\PROGRA~1\COMMON~1\System\MSMAPI\1033\MLCFG32.CPL", @0"

I have 7 other remote users that can connect without any issue. Please
help! I can not find any good documentation for this specific problem.

Thank you

 

[Roady [MVP]]

Does it work when you start off with a clean mail profile?
See http://www.howto-outlook.com/faq/newprofile.htm

 

[jmfgegr]

No - deleting and creating a new profile does not resolve the issue.

 

[Roady [MVP]]

Does it work when you logon to the computer giving the issues with a
different account? Create a test account if needed.
If it doesn't work then either, it might be something installed on the
system giving you this issue or a corruption in of the Office 2003
installation. In that case, run a repair on Office.

 

[jmfgegr]

Ok, thanks for the advice. I'll test this tomorrow when I have remote access
to her laptop.

I'll report back the results here.

 

[jmfgegr]

Ok, this is what I've done to no avail:

1) Created a new "test" account in XP and tried to create her profile there.
Same dll error
2) Uninstalled then reinstalled office 2003 - same dll error

What's left? This is extremely frustrating!!

 

[jmfgegr]

After many wasted hours, I finally found a solution!!!!

I can't take the credit though.... I found it here:
http://www.pcworld.com/article/1261...dows_glitches_by_reregistering_your_dlls.html

I have been directing my attention towards the MLCFG32.cpl file in the
error, but this was wrong and useless... instead, I focused on the
shell32.dll portion of the error.

As stated in the article, "Many problems can be fixed simply by
re-registering Shell32.dll, which stores information about Windows' interface
and is used to open files and Web pages."

So, from the run menu I typed the following command:
regsvr32 /i shell32.dll


.... and presto! Problem solved.

Now that I have that solved, I have to go teach someone what "drag-and-drop"
means. Hopefully this new issue will be much easier to solve.