error '80004003', Object reference not set to an instance of an object.
-
hopefully i am posting in the correct section. I have created a class in c# to replace a vb6 class used in an asp web page. Note I said asp and not asp.NET. I am running this in IIS 7.5 on a 64 bit Windows 7 machine. I compiled the program and all its support dlls as x86 and believe I got all the correct tags and check boxes for COM. I can create and use the class in VB6 but it still bombs in vbscript with can't create object. I found some articles on going to do tweaks in the registry to get it to work on 64 bit but alas no avail. The web application will run with the old VB6 object just fine. The configuration is an application with a separate pool set to pipeline mode classic, no managed code, enable 32 bit applications = true; Initially I was getting a can not create object when trying to use the new c# object but I copied the dll and its support dlls to the sysWOW64 directory and it changed it's tune to MaxRecall.Shared error '80004003' Object reference not set to an instance of an object. /mr/mrq.asp, line 193 the structure of the project is thus the object I am creating with createobject is dependent on a single assembly, MaxRecall.CORE, which is dependent on two assemblies, MaxRecall.CLIENTS and MaxRecall.Shared. None of the support assemblies are com exposed so this error is not a COM error at all I think. MaxRecall.Shared is totally static with zero objects to create. It only had two static doubles that were class scoped that were not instantiated but I set them to 0 in their declarations. To my thinking there are no objects in MaxRecall.Shared to gain an instance to so the error is odd. Sigh. Any and all insights are desperately welcomed. I cross posted this in the ASP.net section.