Visual Basic/VB, MTS DLL registration problem.

MTS DLL registration problem.

Author	Message
jeremy_ayers-h.. #1 / 3	MTS DLL registration problem. In MTS, when I try to register a DLL in any package I get the following error message: "One or more DLLS appear to be corrupt. Either a DLL threw an exception during install processing or the DLL and its embedded type library are out of sync. Ensure that the correct versions of all application runtime files or other dependent DLLs are available in the component DLL's directory or the system path." I compiled the DLLs on a windows 95 machine and I am trying to register the DLL on a NT Server. I do not get this problem registering under windows 95. This ends up with me not being able to register the DLL. Has anyone else come up against this problem, and if so is there a remedy? Jeremy Sent via Deja.com http://www.--*.com/ Share what you know. Learn what you don't.
Sat, 05 Jan 2002 03:00:00 GMT

Jamie Schatt #2 / 3	MTS DLL registration problem. I have encountered this problem when another DLL that is loaded by the DLL in question has changed (for example, the GUID in the 3rd DLL's type library changed because it was rebuild without using binary compatability). If I rebuild the DLL that I am trying to register, this usually solves the problem. Example: I want to register DLL A in MTS, which loads DLL's B, C, and D. I rebuild DLL B without using binary compatability, which changes the type library for DLL B. When I try to register DLL A in MTS, I get the error. If I rebuild DLL A, I can register it OK. Hope this helps! Jamie Schatte Millennia Systems www.millenniasystems.com Quote: >In MTS, when I try to register a DLL in any package I get the following >error message: >"One or more DLLS appear to be corrupt. Either a DLL threw an exception >during install processing or the DLL and its embedded type library are >out of sync. Ensure that the correct versions of all application >runtime files or other dependent DLLs are available in the component >DLL's directory or the system path." >I compiled the DLLs on a windows 95 machine and I am trying to register >the DLL on a NT Server. I do not get this problem registering under >windows 95. >This ends up with me not being able to register the DLL. Has anyone >else come up against this problem, and if so is there a remedy? >Jeremy >Sent via Deja.com http://www.deja.com/ >Share what you know. Learn what you don't.
Sat, 05 Jan 2002 03:00:00 GMT

Denis Gorshko #3 / 3	MTS DLL registration problem. To avoid these problems, you have to a) determine and dependency tree for all of your components and establish the build order b) Once you changed a DLL you have to recompile ALL the direct and indirect dependant components if you did maintain binary compatibility There is a tool designed specifically for this purpose: http://www.mobi-sys.com/prod01.htm -- Denis Gorshkov www.mobi-sys.com Quote: > I have encountered this problem when another DLL that is loaded by the DLL > in question has changed (for example, the GUID in the 3rd DLL's type library > changed because it was rebuild without using binary compatability). If I > rebuild the DLL that I am trying to register, this usually solves the > problem. > Example: I want to register DLL A in MTS, which loads DLL's B, C, and D. I > rebuild DLL B without using binary compatability, which changes the type > library for DLL B. When I try to register DLL A in MTS, I get the error. If > I rebuild DLL A, I can register it OK. > Hope this helps! > Jamie Schatte > Millennia Systems > www.millenniasystems.com
Mon, 07 Jan 2002 03:00:00 GMT

Page 1 of 1

[ 3 post ]