Norton win doctor can't access mscoree.dll

I did a norton one button check up and this error came up in program integrity scan said to run norton win doctor, So I did and
it wouldn't repair
This is what It said:
C:\Program Files\Common Files\InstallShield\Professional\RunTime\0701\Intel32\DotNetInstaller.exe" cannot access a necessary file, "mscoree.dll. "
Any help on this would be Great

Thanks All

 

WinDoctor is not perfect. If you are not experiencing any specific problem, you may as well ignore it.

There should be 2 copies of mscoree.dll: one in system32 and one in system32\URTTemp (at least on my machine).

You could try re-registering the library by going to Start > Run, and typing:

regsvr32 mscoree.dll

Click "OK ".

 

Have the exact same problem and look forward to some light being shed on this.

However, apart from the error showing up when running Win Doctor and not able to repair it, has not caused any problems so far.

Ran the regsvr32 as suggested and got a message

"LoadLibrary(*mscoree.dll*) failed - The specified module could not be found "

Would it be possible to check the .dll's properties to see which program it is associated with ?

 

Just found this on doing a search on Google.

"Error: "Missing File: C:/ProgramFiles/CommonFiles/InstallShield/Professional/Run
Time/0700/Intel32/DotNetInstaller.exe" cannot access a necessary file, "mscoree.dll."

Situation:
After running a diagnostic scan using the WinDoctor utility from within Norton SystemWorks, the following message may appear:

Missing File: C:/ProgramFiles/CommonFiles/InstallShield/Professional/RunTime/0700/Intel32/DotNetInstaller.exe" cannot access a necessary file, "mscoree.dll. "

Solution:
This message can safely be ignored. InstallShield is not really trying to use the file DotNetInstaller.exe without .NET Framework being installed. The DotNetInstaller.exe file is merely cached in the engine location for future use.

InstallShield installs DotNetInstaller.exe as part of its engine files, which is a .NET application that is used when a setup is installing .NET assemblies. DotNetInstaller.exe will not work on systems that do not have the .NET Framework, but the file is cached with the InstallShield engine files just in case it is needed in the future when the .NET Framework is installed. WinDoctor recognizes DotNetInstaller.exe as a .NET application that depends on the .NET Framework and reports its findings. WinDoctor's findings are technically correct, but InstallShield always checks for the Framework before trying to use it. "

Now we can all rest easy and ignore the error in Win Doctor.

 

Of course if the dll is missing, there won't be the ability to register it. It will need to be replaced.

Like most libraries, mscoree.dll is associated with multiple programs. It is used by 140 applications on my machine, aspnet_state.exe to DreamWeaver to mail programs to Visual Basic. It is part of the .NET runtime execution engine.

Do a search to see if it is anywhere on your machine.

EDIT---
We crossed in the mail . If .NET is not installed, the error can be safely ignored, but if it is installed, you will need to replace the copy or, better yet, since the absence of that one .NET file may point to other absences, reinstall .NET.

 

Thanks Abraxas for your reply.

For the moment I am content with answer from Symantec I posted above.

 

WinDoctor is one of the few Norton products I use. For the most part, it is a very good registry cleaner. But it does make mistakes (I need to put the serials back in a couple apps after using it, for example) and can't be expected to be correct always when it comes to things that didn't even exist when the program was written.

All its results should not be believed prima facie and some caution needs to be exercized with the automatic repair. At least it has a backup.

 

Where you guys saying this mscoree.dll can be found
How do I get there I looked in System 32 I do not see it should i be concerend lol

 

If you don't have .NET installed, forget the error.

If you do have .NET installed, reinstall it.

If you aren't sure, look in Add/Remove under Microsoft .NET Framework.

Either way, the error seems to be something of an exaggeration by WinDoctor. You should be fine.

 

OK thanks
I dont have net installed but this error just came up recently never had it before but if its no biggy then great LOL

Thanks again everyone for your help.

 

Helia

Never mind I missed a reply.

BillyBob