Has anyone had success trying to read SAP data through classic ASP using a .NET proxy exposed via COM.
It seemed simple enough; create a .NET class that manages all the connections via the SAP .NET Connector 2.0. Then expose this class to COM by creating a strong name and registering the assembly.
The trouble is, whenever we try and create the COM object in classic ASP we get the same error "can't create object" .... not particularly useful.
We have traced the issue to one line in the .NET code.
<b> SAP.Connector.SAPConnection connection = new SAP.Connector.SAPConnection((IDestination)destination);</b>
This works fine if you are creating the object from another .NET app, but not when run via a classic ASP call. Very strange.
I've seen the odd person run into the same problem but never any solutions.
Has anyone found a solution or even an explanation as to why it would error?