Failed to load resource DLL

  • Thread starter Thread starter Scott Chandler
  • Start date Start date
S

Scott Chandler

Windows 2000 with Terminal Server.

When my users are in a folder such as "Shared" or
their "Home Directory" they sometimes get the following
message "Failed to load resource DLL" when they:

1. Try to open a document (any document ie: word, excel,
etc.) by mouse clicking it.
2. Try to click FILE on the folder window itself or try to
close it after accessing a document.
3. There may be other time this happens but this is what
we have identified up to date.

This issue has started in the past week or so and seems to
happen more often today than last week.

Most of the time my users can click past this message but
sometimes (more recently lately) get this message will
lock up their terminal server session requiring them to re-
logon.

Has anyone seen this type of issue and can anyone shed
some light onto it.

Thanks for your help,
Scott(removethis)@AcornNET.com
 
Is the name of the resource DLL displayed?
Is there anything in the EventLog when this happens?
 
Howdy Vera,

Thanks for the reply.

The total message in the dialog box is "Failed to Load
Resource DLL".

I haven't identified any Event Veiwer messages that go
along with this yet but I should dig deep into that side
(Thanks).

The Microsoft Support Knowledge Base deosn't mention much
but does suggests updating the Data Access engine which I
have done even though their tech note didn't directly
address my issue. This has not helped. By the way this
terminal server has the lastest and greatest Service
Packs.

Another Knowledge Base idea was that we're having a issue
with shared DLLs and that I should "register" (a command
prompt level tool) them but my considerations with this
idea are:

1. There are not always multiable users using the
terminal server when this issue arises so the sharing
idea might not be valid.
2. I don't know what applications that use the errant
DLLs might need to be registered.
3. And I'm not sure of my knowledge of when or how the
use the "register" command and if I should use
the "/system" or "/user" switches.
4. Also this is a new issue so to modify applications
without understanding the cause might not be the best
path.

Thanks for listening and for any help you might have,
Scott Chandler
AcornNET.com
Scott(RemoveThis)@AcornNET.com
 
I agree with you. Registering dlls without knowing why (or which
ones, since the error doesn't mention the particular dlls
involved), seems not the best option.

I have no solution, just some more questions:
* does this *only* happen when handling Office documents?
* do you have multiple versions of Office running? Or 3th party or
in-house developed applications that are based on a runtime
version of Access? Could one of your users run a runtime Access
application that is based on a different version than your full
Office installation?
* do you have other, seemingly unrelated, problems like
performance problems accessing shared network drives (where shared
documents, programs and home drives are located)?
 
Back
Top