I can't register VB DLLs on IIS - what to do?

Created 1998-07-14 by Rainer Gerhards.


I am in the process of moving existing webs from IIS3 to 4. We have a web that has custom DLL's that were written in C and VB. I can register the DLL's written in C, but any of the DLL's written in VB fail to register on the IIS4 box. The only differences between the machines are the versions of IIS, ODBC (3.0 vs 3.5) and the IIS3 box has VB5 loaded on it. (I dont want to load VB5 on the new machine unless necessary). Does anyone have any clues as to what could be the problem?  Could there be some dependency that the install of VB 5 provided?


You need the VB runtime libraries on the new server. The simplest way to get these is to create a setup program using the VB setup wizard and run this on the new machine.


Back to Non-Printer Version