Cannot add network place by browse - crash on Run DLL as an App.

[Bluto]

When I try to add a network place by browse I get an exception. "Run DLL as
an App has encountered a problem and needs to close." I have sent multiple
error reports to MS with no results. I also have been unable to locate
anything on this in the KB. I also get a notification that rundll is not
responding.

Error signature:
szAppName : rundll32.exe szAppVer : 5.1.2600.2180 szModName : hungapp

szModVer : 0.0.0.0 offset : 00000000

The following files are supposedly sent.

C:\DOCUME~1\user\LOCALS~1\Temp\WER6c74.dir00\rundll32.exe.mdmp

C:\DOCUME~1\user\LOCALS~1\Temp\WER6c74.dir00\appcompat.txt

The "user" above is a replacement for the real user name. Can someone help
me troubleshoot this problem?

Thanks,
Bluto

 

[Guest]

There is a rather complex procedure to repair tcp/ip. In your case it may be
worth a shot.

Q299357 - How to Reset Internet Protocol (TCP-IP) in Windows XP:
http://support.microsoft.com/default.aspx?scid=kb;en-us;Q299357

 

[Bluto]

Unfortunately that did not do it. The problem still remains the same. The
unfortunate thing is that I cannot restore this RAID drive using Drive Image
since it does not recognoze the C: drive under the restore utility. I have a
promise RAID controller and I have heard that there are problems doing this.
Usually it is a simple process to restore a complete drive image using Drive
Image but on this system it does not work. For this reason I need to try and
fix this problem some other way.

Any other ideas?

Thanks,
TH

 

[Bluto]

I could not see this box until I used msconfig to stop most of the stuff
that starts with windows, but I got this info:
An exception occurred while trying to run "netplwiz.dll,AddNetPlaceRunDLL"

 

[Bluto]

I tried the following:

regsvr32 /i netplwiz.dll - OK

regsvr32 /i mshtml.dll - Failed with mshrml.dll was loaded, but the
DllRegisterServer entry point was not found. This file can not be
registered.

regsvr32 /i shell32.dll - OK

 

[Bluto]

I finally found that this problem is related to IE7. When I uninstalled IE7
and went back to IE6, the problem was cured. I think it has something to do
with the "mshtml.dll" file which is first installed with IE7 and then
updated with a security update. With IE6, the file is dated from 2004, and
all worked OK. Once I updated to IE7, it installed a file with a date of
late 2006. Then I did an update and the file date changed to Jan. 2007.
Whatever the case may be, it appears that something in my system does not
agree with the newer mshtml.dll files.

If anyone has seen a problem like this and knows the fix, other than
reverting to IE6, please let me know. I have gone back to IE7 and the
problem has returned.

Thanks,

Bluto

 

[Guest]

In my expierence, the failure of the updates files is almost always some
corruption acquired during the download of the file. I think you might
consider another shot at the update. Set some restore point, and give it a
go, falling back on failure.

 

[Bluto]

Unfortunately, I reinstalled the update and the problem returned. Previously
I had problems with this computer when I installed the IE7 beta 2 and could
not install beta 3. I got permission problems which I believe were mentioned
in a user group in MS. As I recall I could not even go back to IE6 at that
time, so I stuck with beta 2 until the official update came out. That seemed
to install cleanly, and I figured all was good until I discovered this
browsing problem.

Recalling the experience with the beta install reminds me that I will never
do another beta test for anyone. That was a bad experience and when I could
not even back it out that was really aggravating. And this one is extra
frustrating since it is my main computer with RAID 0 drive for performance
but I cannot restore the thing using drive image the way I usually do if
needed on one of my non RAID machines.

That means if I really want to fix this problem, I need to restore to the
original out of box setup. Go through removing more than half of the crap
the vendor puts on there, and then reinstalling all of the updates and
software I have installed over the last 2 to 3 years. FUN!

Any other ideas would certainly be appreciated. Or I will live with the
current situation unless something more serious comes up and I have to
rebuild from scratch. Actually since MS beta started all of this they should
help me solve it.

Regards,
Bluto