After spending the last 8 hours on this,I thought I would post here, just in case somone has had a similar issue. I have googled for answers with solutions relating to permissions and registration of the DLL, however, since this was all working up until sometime during the night, I have no clue whether a Server 2012 R2 update was installed automatically (I dont look after the server, an off-site engineer does who is currently looking at event logs)
First the error:
Microsoft VBScript runtime error '800a01ad'
ActiveX component can't create object: 'Connman.ConnMan'
Connman is a custom VB.NET V4.0 Class DLL that is interop COM-Visible that goes onto our web server.
What I have tried:
Re-registered the DLL via Regasm in the framework v4.0.30319 folder, successfully registered types.
In IIS, enabled the 32bit in the application pool for the website, as we are running a 64bit server with 32bit DLLs. Also
Checking the folder of the DLLL to see is permissions have included IUSR, IWAM and of course web anonymous etc..
Stripping out the commands being used with Connman class, here are the several lines of code, of which it just falls over on the CreateObject.
Set CONN = CreateObject("Connman.ConnMan")
Set CONN = Nothing
So the code just create the object and disposes it. It doesnt get further than creating the object however before returning the 800a01ad error.
Using a VBS file and running through CSCRIPT, I am able to run the script without an issue, no error is returned and with some commands betewen the create and dispose, it operates as it should - but try and run it in ASP itself and it just falls over.
If anyone has any suggestions I would be happy to look at them and of course, I appreciate your time just reading this and /or suggesting something that might get this going.
** One thing to add to this, Windows update <has> installed several updated today, I am going to investigate them but the KB's are 4338815, 4339093, 433824, 4338613. 4338605, 4338419 and 4338424 - so one of these could be interfering, but before uninstalling anything, I will have a read and see if there is anything .net or IIS related in them. Will update this question once I have taken a read **