dll registration problem [modified]: Problem Fixed
-
We have fixed this problem. It required reinstalling Windows XP SE. This ended up being the only way to get the .dll reinstalled and correctly registered. March 12, 2007. We have been running two visual basic.net routines with out any problems for a few months when suddenly they stopped running with the following error (below). Both routines make use of the scripting.dll. The error messages are as follows: 'EFFAFileListCreator.exe': Loaded 'f:\effa file list generator_vbnet\bin\interop.scripting.dll', No symbols loaded. 'EFFAFileListCreator.exe': Loaded 'c:\windows\assembly\gac\microsoft.visualbasic\7.0.5000.0__b03f5f7f11d50a3a\microsoft.visualbasic.dll', No symbols loaded. An unhandled exception of type 'System.Runtime.InteropServices.COMException' occurred in EFFAFileListCreator.exe Additional information: COM object with CLSID {0D43FE01-F093-11CF-8940-00A0C9054228} is either not valid or not registered. Unhandled Exception: System.Runtime.InteropServices.COMException (0x80040154): COM object with CLSID {0D43FE01-F093-11CF-8940-00A0C9054228} is either not valid or not registered. at EFFAFileListCreator.frmMain..ctor() in F:\EFFA File List Generator_VBnet\EFFALIST.vb:line 553 at EFFAFileListCreator.frmMain.Main() in F:\EFFA File List Generator_VBnet\EFFALIST.vb:line 2The program '[42384] EFFAFileListCreator.exe' has exited with code 0 (0x0). ===================================================================================================================== We have not been able to solve this problem. Anyone have any suggestions? Pete -- modified at 19:19 Monday 12th March, 2007
-
We have fixed this problem. It required reinstalling Windows XP SE. This ended up being the only way to get the .dll reinstalled and correctly registered. March 12, 2007. We have been running two visual basic.net routines with out any problems for a few months when suddenly they stopped running with the following error (below). Both routines make use of the scripting.dll. The error messages are as follows: 'EFFAFileListCreator.exe': Loaded 'f:\effa file list generator_vbnet\bin\interop.scripting.dll', No symbols loaded. 'EFFAFileListCreator.exe': Loaded 'c:\windows\assembly\gac\microsoft.visualbasic\7.0.5000.0__b03f5f7f11d50a3a\microsoft.visualbasic.dll', No symbols loaded. An unhandled exception of type 'System.Runtime.InteropServices.COMException' occurred in EFFAFileListCreator.exe Additional information: COM object with CLSID {0D43FE01-F093-11CF-8940-00A0C9054228} is either not valid or not registered. Unhandled Exception: System.Runtime.InteropServices.COMException (0x80040154): COM object with CLSID {0D43FE01-F093-11CF-8940-00A0C9054228} is either not valid or not registered. at EFFAFileListCreator.frmMain..ctor() in F:\EFFA File List Generator_VBnet\EFFALIST.vb:line 553 at EFFAFileListCreator.frmMain.Main() in F:\EFFA File List Generator_VBnet\EFFALIST.vb:line 2The program '[42384] EFFAFileListCreator.exe' has exited with code 0 (0x0). ===================================================================================================================== We have not been able to solve this problem. Anyone have any suggestions? Pete -- modified at 19:19 Monday 12th March, 2007
hope you might have made some changes in scripting.dll and registered freshly and in existing .Net you might have not included the fresh reference. 1. Remove existing reference from the VB.net application 2. Add reference of the dll 3. Recompile. This should solve. if the above reason is true.
Regards KP
-
We have fixed this problem. It required reinstalling Windows XP SE. This ended up being the only way to get the .dll reinstalled and correctly registered. March 12, 2007. We have been running two visual basic.net routines with out any problems for a few months when suddenly they stopped running with the following error (below). Both routines make use of the scripting.dll. The error messages are as follows: 'EFFAFileListCreator.exe': Loaded 'f:\effa file list generator_vbnet\bin\interop.scripting.dll', No symbols loaded. 'EFFAFileListCreator.exe': Loaded 'c:\windows\assembly\gac\microsoft.visualbasic\7.0.5000.0__b03f5f7f11d50a3a\microsoft.visualbasic.dll', No symbols loaded. An unhandled exception of type 'System.Runtime.InteropServices.COMException' occurred in EFFAFileListCreator.exe Additional information: COM object with CLSID {0D43FE01-F093-11CF-8940-00A0C9054228} is either not valid or not registered. Unhandled Exception: System.Runtime.InteropServices.COMException (0x80040154): COM object with CLSID {0D43FE01-F093-11CF-8940-00A0C9054228} is either not valid or not registered. at EFFAFileListCreator.frmMain..ctor() in F:\EFFA File List Generator_VBnet\EFFALIST.vb:line 553 at EFFAFileListCreator.frmMain.Main() in F:\EFFA File List Generator_VBnet\EFFALIST.vb:line 2The program '[42384] EFFAFileListCreator.exe' has exited with code 0 (0x0). ===================================================================================================================== We have not been able to solve this problem. Anyone have any suggestions? Pete -- modified at 19:19 Monday 12th March, 2007
Just to add a bit to Pete's description of the problem -- I'm his "cohort" in crime... We had two VB.NET programs running on this particular machine. They suddnly stopped working with the indicated error messages. Nothing new was done to the programs or to the machine: no updates of the programs, no change to .Net, etc. The program's die on the following line, which they have in common. Dim sw As IO.StreamWriter = IO.File.CreateText(str_FileName) We tried reinstalling the programs using the install CD (.msi files, etc.). The installs were OK, but the same errors happen. It appears that something to do with StreamWriter or Scrippting in general has disapeared from the machine. We tried to copy the programs from another machine via Laplink: same error. We copied the entire subdirectory including the VB project and the installation project, etc. The copied folder on this machine had a dll missing from the Detected Dependencies. Why the dependency was lost is also a puzzle. Everything should have been identical in the copy folder as in the original. Don't know why not. This does seem to be a case where something got clobbered by, perhaps, cosmic rays, which changed something on the hard drive so the required dll is missing. We tried to find the "missing" .dll and then (re)register it. But there is no dll with the exact name shown. That is, we can't find a "bad" entry for the CLSID in the registry. And can't figure out which dll corresponds to the CLSID. We tried using Visual Studio Repair from Add/Remove Programs. We tried reinstalling XP SE. So at this point, we are fully frustrated. Is it time for Remove Visual Studio, Fully reinstall VS? All suggestions welcome. -- modified at 21:30 Tuesday 27th February, 2007
Charles Wolfe C. Wolfe Software Engineering