ErrMsg: Entry point not located

[Guest]

In an effort to try and resolve problems with IE shutting down at random
after installing XP SP2, I reinstalled IE 6 from the OEM disk. In now shows
version 6.00.2600.0000. I tried to then download and install IE 6 SP1 but
got the error message: "Procedure entry point InternetGetConnectedState could
not be located in the dynamic link library WININET.dll." The message connot
be cleared from the screen. The IE problem has been going on for over a
month and am at a loss as to how to fix the unexpected shutdowns. HELP!

 

[Robert Aldwinckle]

In an effort to try and resolve problems with IE shutting down at random
after installing XP SP2, I reinstalled IE 6 from the OEM disk.

Does this mean that you backed out all XP maintenance?
If so and you didn't at least activate the XP firewall before connecting
you are likely infected by malware.

An alternative would be get the MS Security CD and get updated
without unprotected exposure to the Internet that way.

In now shows
version 6.00.2600.0000. I tried to then download and install IE 6 SP1 but
got the error message: "Procedure entry point InternetGetConnectedState could
not be located in the dynamic link library WININET.dll." The message connot
be cleared from the screen.

If instead you would prefer to diagnose your symptoms
tell us the properties of your wininet.dll (version, size, and date)

You should also try to find out which program is issuing the error message.
E.g. use Task Manager's Go to Process command to find that.
Then tell us the properties of that module (version, size, and date)
Hopefully, Task Manager's Option, Always on Top can override
the same option on your error message window. If not, although
the "message cannot be cleared", perhaps you will find that it can
at least be Moved. (E.g. press Alt-Space to check for that possibility.)


HTH

Robert Aldwinckle
---

 

[Guest]

Does this mean that you backed out all XP maintenance?

I guess that is beyond me. I removed SP2 then started the OEM disk,
selected add or remove programs and unchecked the box for IE 6.

If so and you didn't at least activate the XP firewall before connecting
you are likely infected by malware.

I have run all the various recommended options here - cwshredder, spybot,
adaware and scannow, multiple times.

An alternative would be get the MS Security CD and get updated
without unprotected exposure to the Internet that way.



If instead you would prefer to diagnose your symptoms
tell us the properties of your wininet.dll (version, size, and date)

Wininet.dll (6.0.2737.800; 585,216 kb; 11-18-2004 created date)

You should also try to find out which program is issuing the error message.
E.g. use Task Manager's Go to Process command to find that.
Then tell us the properties of that module (version, size, and date)

Task manager show the last process as winzip32.exe.
winzip32.exe (13.0.0.0; 1,425,471 kb; 1-26-2002 created date)

 

[Robert Aldwinckle]

: ....
I removed SP2 then started the OEM disk,

Removed, as in uninstalled, I think is what happened?
That would revert you to whatever maintenance level
you happened to be at before you installed XPsp2.

If so, you would not be able to download and install IE6.
If you had backed out all XP maintenance, e.g. putting you back
to XP base level, your IE level would be IE6 base level also.
In that case you *would* be able to download and install IE6sp1
(which is what is available at the download site).

I'm not sure how well a base IE6sp1 would integrate with an
IE6 which had a higher level of maintenance that it implied.
It's possible that it might be necessary to uninstall some
of that maintenance separately to get everything down to
a compatible level.

The install procedure is known to give rather odd error messages
in order to signal to the user that the version which failed to install
would regress the current version. I'm wondering if that might be
what your message means.

selected add or remove programs and unchecked the box for IE 6.

If you check the help in the description box for this item
I think you'll see that this does nothing but remove the IE icons
from the Desktop and the Start menu.

The only way to remove IE6 from XP and start over
is given by the procedure at the bottom of KB318378.
Again, it is unclear what you are supposed to do about
maintenance. Logically, uninstalling the base product
would uninstall all the maintenance for it too but the article
doesn't say that or make any reference to it so it's possible
that it may be necessary there too to uninstall individual
patches to achieve the state that the article is referring to.

Wininet.dll (6.0.2737.800; 585,216 kb; 11-18-2004 created date)

This looks as if you have 834707 applied to IE6 base.
BTW instead of created date I think the Date Modified
is what will be significant. E.g. is it 08-Jan-2004?

What does your Help, About show for Update versions: ?
You can capture that string by executing the following script fragment
in your Address bar:

javascript:navigator.appMinorVersion

Note: the property name is case sensitive.

Task manager show the last process as winzip32.exe.

"Last process" may not be what I was thinking of.
Just to be clear, Go to Process, is a right-click option
on items in the Applications tab. So, select the item which represents
the error message window, press the Menu key and use Go to Process.
That should switch you to the Processes tab with the relevant PID
highlighted and the Image Name would be the program
which issued the error message. Was that really winzip32.exe?
Or ie6setup.exe instead?


HTH

Robert
---

 

[Guest]

If you check the help in the description box for this item
I think you'll see that this does nothing but remove the IE icons
from the Desktop and the Start menu.

If I understand, I have IE6, based upon the version, but various maintenance
that goes with IE SP1 - so I ended up with a hybrid of sorts.

The only way to remove IE6 from XP and start over
is given by the procedure at the bottom of KB318378.

I have used this procedure and the isinstall code is set to 0. But to no
avail.

This looks as if you have 834707 applied to IE6 base.
BTW instead of created date I think the Date Modified
is what will be significant. E.g. is it 08-Jan-2004?

The modify date of Wininet.dll is 8/4/04.

What does your Help, About show for Update versions: ?
You can capture that string by executing the following script fragment
in your Address bar:

javascript:navigator.appMinorVersion
;Q313675;Q316059;q319182;Q321232;Q323759;Q328676;Q328970;Q324929;Q813489;Q330994;Q818529;Q822925;Q828750;Q824145;Q832894;Q837009;Q823353;
Note that there is no SP in front.

Following your latest advice, the application is ie6wzd.exe and the process
is csrss.exe

I still cannot install IE 6 SP1 and the unexpected shut-downs continue. I
have to use another computer for these reponses because it always caused a
shutdown whenever I hit reply for instance.
KB315341 descibes an In-Place reinstallation of windows XP. Am I down to
that as the only possible solution?

Regards, Tim

 

[Robert Aldwinckle]

....

If I understand, I have IE6, based upon the version, but various maintenance
that goes with IE SP1 - so I ended up with a hybrid of sorts.

More correctly I think it is "maintenance that goes with IE6 preSP1"
As your Update versions: string below proves, you were applying
individual patches to IE6 base and never went to IE6sp1.
(Or did you try to uninstall something before installing XPsp2?)
When you installed XPsp2 all of that was superseded but saved
in case you wanted to uninstall back to the level of maintenance
you had when you installed it. If you had installed XPsp1
much of it would be superseded and the IE6 level patches
replaced by IE6sp1 level patches. The hybrid that you were
attempting to create by installing IE6sp1 would have been
XP (without SP1) plus IE6sp1.

I have used this procedure and the isinstall code is set to 0. But to no
avail.

You mean you're in the middle of it because you are still trying to
reinstall IE6sp1.

The modify date of Wininet.dll is 8/4/04.

Ah good. Now we're getting somewhere. That came from MS04-004
(832894). The reason I didn't find it is because I was misled by that
single digit in the version release field. For some reason that field
is documented as having two digits, e.g. 6.00.2737.800

Excellent. (I should have guessed it would be everything.)

What I would try next is uninstalling 832894 which is where your current wininet.dll came from.

Following your latest advice, the application is ie6wzd.exe and the process
is csrss.exe

Good. That was extracted out of the ie6setup.exe you have.

I still cannot install IE 6 SP1 and the unexpected shut-downs continue.

If reverting to the previous version of wininet.dll doesn't fix the symptoms
please describe in detail what they are. Also look in the Active Setup Log.txt
and IE Setup Log.txt to see if there are any specific clues about what is
happening to your install attempt.

I have to use another computer for these reponses because it always caused a
shutdown whenever I hit reply for instance.

Really another computer or just a different partition on your machine?
A parallel install is a very handy thing to have...

KB315341 descibes an In-Place reinstallation of windows XP. Am I down to
that as the only possible solution?

Try to uninstall the last patch first.

Regards, Tim

Good luck

Robert
---

 

[Guest]

More correctly I think it is "maintenance that goes with IE6 preSP1"
As your Update versions: string below proves, you were applying
individual patches to IE6 base and never went to IE6sp1.
(Or did you try to uninstall something before installing XPsp2?)
When you installed XPsp2 all of that was superseded but saved
in case you wanted to uninstall back to the level of maintenance
you had when you installed it. If you had installed XPsp1
much of it would be superseded and the IE6 level patches
replaced by IE6sp1 level patches. The hybrid that you were
attempting to create by installing IE6sp1 would have been
XP (without SP1) plus IE6sp1.



You mean you're in the middle of it because you are still trying to
reinstall IE6sp1.



Ah good. Now we're getting somewhere. That came from MS04-004
(832894). The reason I didn't find it is because I was misled by that
single digit in the version release field. For some reason that field
is documented as having two digits, e.g. 6.00.2737.800


Excellent. (I should have guessed it would be everything.)

What I would try next is uninstalling 832894 which is where your current wininet.dll came from.

I'm sorry, I don't know how to do this?

Good. That was extracted out of the ie6setup.exe you have.


If reverting to the previous version of wininet.dll doesn't fix the symptoms
please describe in detail what they are. Also look in the Active Setup Log.txt
and IE Setup Log.txt to see if there are any specific clues about what is
happening to your install attempt.



Really another computer or just a different partition on your machine?
A parallel install is a very handy thing to have...

Really another computer. Thanks, Regards Tim

 

[Guest]

Robert-Q832894 is not listed among all of the items shown in Add/Remove
programs. At this point I am at a loss as to what to do next. Do you have
any further advice. Regards, Tim

 

[Robert Aldwinckle]

....

Robert-Q832894 is not listed among all of the items shown in Add/Remove
programs. At this point I am at a loss as to what to do next. Do you have
any further advice. Regards, Tim

Hmm... that's strange. Which of those patches *do* you have
uninstall control of? Perhaps one of them will have its own wininet.dll
that you could extract and install manually. Also just do a Win-F search
of your harddrive to see what all wininet.dll you have to play with right away.

Just to try to keep sight of your objective here: all we are doing is trying
to find a compatible version of wininet.dll which will work long enough
for you to complete the install of IE6sp1 using ie6setup. Right?
Having an uninstall procedure properly back out the problem version
and install the last old version would have been preferable but really
all you need to do is find one, install it, and see if it works.

BTW just in case you want to try to get ahead of me, watch out that
you replace both the one that is in DllCache and System32 at the
same time and in that order. You can't replace it on a live system
but it should be easy to do both changes from an alternate partition.


Good luck

Robert
---

 

[Guest]

....

Someone at my work advised I us ieuninst with Q832894.inf in the command
line. I did and it removed the patch but I still could not install IE 6.1.

Just to try to keep sight of your objective here: all we are doing is trying
to find a compatible version of wininet.dll which will work long enough
for you to complete the install of IE6sp1 using ie6setup. Right?

Good point. About 6 wks ago IE began shutting down with the message that it
had encountered a problem and needed to close. This occured regularly but
without a pattern and when it closed is closed all open IE windows. I had
just installed XP SP2 and thought there might be a connection but after
uninstalling and reinstalling the problem persisted. I began reading posts
to the newsgroup of similar situations and worked through all the spyware and
other scan suggestions. One post suggested reinstalling IE6. That's when I
got the error message that started this post.

The real problem is IE shutting down. Last night in frustration I
reinstalled XP (upgrade option) from the OEM CD and then installed all the
updates and SP2. Well that did not help either. When I tried to reply to
your post to me it gave the "encounter a proble" message and shut down. I am
really at a loss at this point.

Regards, Tim

 

[Robert Aldwinckle]

....

Someone at my work advised I us ieuninst with Q832894.inf in the command
line. I did and it removed the patch

Really? What version of the modules listed in MS04-004 do you have now?

but I still could not install IE 6.1.

Tim, I am not a psychic. You need to give us details if you need help.
What are your symptoms? Look for "after the fact" clues in the *log.txt
files.


Good luck

Robert
---