jmeyer98
asked on
Need shwapi.dll?
I get an error message as follows: The procedure entry point UrlCanonicalizeA could not be
located in the dynamic link library SHLWAPI.dll. Anyone help me get rid of this error message?
located in the dynamic link library SHLWAPI.dll. Anyone help me get rid of this error message?
Try c:\winnt\system32\REGSVR32 .EXE c:\winnt\system32\SHLWAPI. dll /u
Try c:\winnt\system32\REGSVR32 .EXE c:\winnt\system32\SHLWAPI. dll
This will unregister the dll and then reregister the dll this will solve most problems with dll not being registered.
Substitute the paths for your windows nt folder.
Good luck and let me know
Try c:\winnt\system32\REGSVR32
This will unregister the dll and then reregister the dll this will solve most problems with dll not being registered.
Substitute the paths for your windows nt folder.
Good luck and let me know
What's your browser version? Saw something with this dll when trying to access compiled htm's with pre 3.02 IE.
ASKER
I tried the unregister command and it said that it could not find the entry point for the unregister command. I then tried it without the /u and is said it could't find the entry point for the register command. It added a comment in the box that said that I should try PVIEW to see if shlwapi.dll was corrupted in memory so I could unload it and reload it. I ran PVIEW and shlwapi.dll was not in memory at all. And that's where I stand right now. ( I also don't see where the option to awrd points appears if this had been completed)
Do you have Ie 4.0 installed on your machine, and if yes then try to reinstall it as this file is apart of ie 4.0. This will most likely solve your problem and beable to reregister the dll. Had this been an answer there would be an option to grade it and accept this answer, but so far these are only comments and not an answer.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
It was the wininet.dll file. The urlmon file was not the "bad" version. The wininet file was the "bad" version. I had a different wininet file in a different location on the hard drive. Copied into the system32 directory and all seems OK. Will feel better when I try other programs. Great job though.
ASKER