Entry point RtlHashUnicodestring could not be located in t..

Dear all,

Tried to locate the solution, but not found from Internet.
Can someone advise how to elminate the error as subject?
Based on my experiences, the error is caused by another dll file which I
should rename.
However, I don't know which file is the cause?

Appreciate very much if someone can help

Thanks

I am having the same problem. I am getting the error when attempting to open
two .Net-built applications on multiple Windows 2000 machines. It doesn't
seem to affect the overall functionality of the applications but the annoying
message box MUST go. I built the .Net applications in XP and both contain
the web browser control (with references .

I believe I have narrowed it down to a set of system DLL's that probably
were installed on the Win2000 machines by another application (or a Windows
update), but are XP specific (albeit backwards-compatible) and are attempting
to call non-existent functions in the Win2000 version of ntdll.dll such as
RtlHashUnicodeString.

These system DLL's are:
xpsp2res.dll
apphelp.dll
comres.dll
msdmo.dll
mslbui.dll
sxs.dll
uxtheme.dll

I was also seeing another similar 'Entry point ... ntdll' error with my
applications attempting to call the RtlDuplicateUnicodeString function.
Taking apphelp.dll out of the picture fixed this (renamed apphelp.dll.bak), I
also renamed uxtheme.dll which is unnecessary in Win2000 and was causing the
same issue in another unrelated application.

I think the culprit DLL causing our error is sxs.dll, but this library can't
be renamed and disabled or more critical errors appear. The solution would
be to find the Win2000 'native' version of sxs.dll and replace the XP one.
The version of sxs.dll that is present is 5.1.2600.2180 and dated 8/4/2004 -
it is the same version as the one on XP. I haven't found that version yet,
but when I do I will post my results.

Pete Bronken

"Rico Ma" wrote:

> Dear all,
>
> Tried to locate the solution, but not found from Internet.
> Can someone advise how to elminate the error as subject?
> Based on my experiences, the error is caused by another dll file which I
> should rename.
> However, I don't know which file is the cause?
>
> Appreciate very much if someone can help
>
> Thanks