Link to home
Start Free TrialLog in
Avatar of javanic
javanic

asked on

two different copies of MSCOREE.DLL-Hell have been loaded

Help!

I've got a serious problem that I cannot get around. After installing Dundas Chart Windows Forms for .NET on my XP Pro system, I began to get a pop-up error message whenever I tried to work on any forms in my project (IDE is Visual Studio .NET 2003). I've since uninstalled the third party software, reinstalled it, reinstalled Visual Studio, and all to no effect. The complete error pop-up reads as follows:

--- begin ---
devenv.exe - MSCOREE.DLL load error (Error code = %X).
Two different copies of MSCOREE.DLL have been loaded.
First copy:
<Unknown>
Second copy:
C:\Windows\Microsoft.NET\Framework\v1.1.4322\mscorwks.dll
This is typically caused by having a registered MSCOREE.DLL that is different from the one that is statically linked to the application.
--- end ---

All the above appears on the pop-up. Then, after pressing OK on the pop-up, I get a message in the form designer space that says:

--- begin ---
An error occurred while loadign the document. Fix the error, and then try loading the document again. The error message follows:
Cannot create a file when that file already exists.
--- end ---

I'm about to go nuts fixing this, because I haven't a clue where to start. Does anyone out there have any knowledge of this problem? Is something corrupted in my XP system files? or is it something messed up in VS.NET 2003?

Thanks for your help,

javanic

Avatar of javanic
javanic

ASKER

BTW, the Dundas folks disclaim any part of this error. In their defense, their software install does not include an MSCOREE.DLL. It is possible that the problem comes from an earlier install some software, though I can't recall what I installed last before this problem started.

In any case, I've got this corrupted system in Visual Studio .NET and don't know how to fix it short of a HDD reformat and reinstall of everything.

Take a wander through the registry and see if you can find the references, and delete the *BAD* one.  

Yes, playing in the Registry is dangerous, but if you are going to nuke and resurrect the box anyway it's worth a shot before you take that step.
Avatar of javanic

ASKER

Your suggestion is well founded. However, I nuked the drive last night and started over. We'll see if the error is there after I put everything back on the drive.

I had looked through the registry before, however, and did see references to mscoree.dll versions 1.0~ and 1.1~. Probably versions related to .NET 1.0 and 1.1? Both versions appeared so many times that I thought that deleting one would most certainly impair something.

I did find that the Visual Studio .NET 2003 invokes mscoree.dll whenever a form is going to be displayed in the designer. There was a reference to this in some microsoft documentation that I stumbled across during my days of hair pulling and teeth gritting.
Hope you get it working in short order.
ASKER CERTIFIED SOLUTION
Avatar of Computer101
Computer101
Flag of United States of America image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial