DTerminator
Programmer
Hi,
I am new to the site, so forgive me if my question has already been answered. We have a dcom component, which issues our SQL calls to Oracle for us (instead of being in the ASP page). We have several methods in this dll, some pass disconnected recordsets, 1 passes a connected recordset (and allows the advanced features, such as beginTrans, customized cursors, etc.). A dll on the web server side makes the dcom call to another server, which actually makes the SQL call.
We used to be on NT4, everything has been working fine...
Now, we are attempting the upgrade to 2000, and I am getting a permission denied error when attempting to use the data back on my ASP page. If I look at the data in the dll, everything looks good, but once I get back to the ASP page, and pass the connection and the recordset, I get a permission denied, Error 70 (once I use the recordset). The parameters into the COM dll are:
Public Function xyz(SQL As Variant, ByVal OracleProperties As Dictionary, PassOracleConn As Variant) As ADODB.Recordset.
Parameters to DCOM dll are:
Public Sub DCOMxyz(SQL As Variant, Rs As ADODB.Recordset, varOraclePropertiesXML As Variant, Conn As ADODB.Connection)
Any ideas on this topic? I have searched many sites, and tried many things on this end, to no avail. However, I did register my DCOM dll on my web server (for grins), and everything worked fine. Therefore, if the call doesn't go across DCOM, things work just fine in 2000 and COM+. It seems to be that DCOM part that screws things up for me.
Thanks for any help you can provide.
I am new to the site, so forgive me if my question has already been answered. We have a dcom component, which issues our SQL calls to Oracle for us (instead of being in the ASP page). We have several methods in this dll, some pass disconnected recordsets, 1 passes a connected recordset (and allows the advanced features, such as beginTrans, customized cursors, etc.). A dll on the web server side makes the dcom call to another server, which actually makes the SQL call.
We used to be on NT4, everything has been working fine...
Now, we are attempting the upgrade to 2000, and I am getting a permission denied error when attempting to use the data back on my ASP page. If I look at the data in the dll, everything looks good, but once I get back to the ASP page, and pass the connection and the recordset, I get a permission denied, Error 70 (once I use the recordset). The parameters into the COM dll are:
Public Function xyz(SQL As Variant, ByVal OracleProperties As Dictionary, PassOracleConn As Variant) As ADODB.Recordset.
Parameters to DCOM dll are:
Public Sub DCOMxyz(SQL As Variant, Rs As ADODB.Recordset, varOraclePropertiesXML As Variant, Conn As ADODB.Connection)
Any ideas on this topic? I have searched many sites, and tried many things on this end, to no avail. However, I did register my DCOM dll on my web server (for grins), and everything worked fine. Therefore, if the call doesn't go across DCOM, things work just fine in 2000 and COM+. It seems to be that DCOM part that screws things up for me.
Thanks for any help you can provide.