mscorwks.dll cannot be loaded.

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

This question has come up before and no one has yet answered it.

I have a VB.NET application distributed to about 100 users. Today, on of my
users received this message, along with the message ".NET Framework
Initialization Failed," the first time he tried to run it. No other user has
received this error. He's running XP.

There is one three-year old KB article about this error, which acknowledges
it's a bug, but offers no solution. What is this problem, and is there a
solutiuon.

TIA

James Brady
 
manually copy the dll to the system folder, then register it at the command
prompt. i suspect the application will be flakey from then on because msc*
has several dependencies that may not be correctly registered. The best bet
is to uninstall and re-install. Repeat until it works :-)

--
Regards,
Alvin Bruney - ASP.NET MVP

[Shameless Author Plug]
The Microsoft Office Web Components Black Book with .NET
Now available @ www.lulu.com/owc
 
Thanks, Alvin, this makes sense. My customer, though, is not real computer
savvy, and is getting impatient. It'll be a pain talking him through this.
:^(

Alvin Bruney said:
manually copy the dll to the system folder, then register it at the command
prompt. i suspect the application will be flakey from then on because msc*
has several dependencies that may not be correctly registered. The best bet
is to uninstall and re-install. Repeat until it works :-)

--
Regards,
Alvin Bruney - ASP.NET MVP

[Shameless Author Plug]
The Microsoft Office Web Components Black Book with .NET
Now available @ www.lulu.com/owc
[email protected] said:
This question has come up before and no one has yet answered it.

I have a VB.NET application distributed to about 100 users. Today, on of
my
users received this message, along with the message ".NET Framework
Initialization Failed," the first time he tried to run it. No other user
has
received this error. He's running XP.

There is one three-year old KB article about this error, which
acknowledges
it's a bug, but offers no solution. What is this problem, and is there a
solutiuon.

TIA

James Brady
Click to expand...
Click to expand...
 
Alvin Bruney said:
manually copy the dll to the system folder, then register it at the
command prompt. i suspect the application will be flakey from then on
because msc* has several dependencies that may not be correctly
registered. The best bet is to uninstall and re-install. Repeat until it
works :-)
Click to expand...

What exactly do you mean with register and system folder?
This DLL is not a COM server, and he doesn't belong in in the system folder.

Willy.
 
What exactly do you mean with register and system folder?
Click to expand...
It *does show up in the system folder, for instance on my machine a copy
runs in c:\windows\system32\URTTemp. I know that wasn't what you meant but i
got off on a technicality.
This DLL is not a COM server, and he doesn't belong in in the system
folder.
Click to expand...
True. My bad.

In OP's case, i believe a re-install is in order.

--
Regards,
Alvin Bruney - ASP.NET MVP

[Shameless Author Plug]
The Microsoft Office Web Components Black Book with .NET
Now available @ www.lulu.com/owc
 
Back
Top