Accessing COM dll. Works in Visual Studio but not when published in IIS.

I have a simple ASP.NET test page that calls a method in a COM dll.  When running from within Visual Studio, using Visual Studio's web server, things work fine.  When I attempt to run the page outside of Visual Studio via IIS, the pagel errors with the HRESULT: 0x80020009 (DISP_E_EXCEPTION) error.  The error occurs at the line of the COM method call.

I don't understand what's different when executing through IIS.  The dll is registered, otherwise it wouldn't work within VS.  I've tried copying the dll locally to my website's bin folder but that doesn't help.
Protected Sub Button1_Click(ByVal sender As Object, ByVal e As System.EventArgs) Handles Button1.Click
 
        Dim i As Integer
        Dim strUserid As Object
        Dim strUserName As Object
'
'
        strUserid = "DEMO"
        strUserName = "PASSWORD"
'
        mRMCom = New RMIFCLLib.Client
'
        Try
            i = mRMCom.Logon("AUTOSTORE", strUserid, strUserName ) ' ERROR OCCURS HERE
        Catch Ex As Exception
            Me.Label1.Text = Ex.Message
            Return
        End Try
'
        i = mRMCom.GetFirstUserID(strUserid, strUserName)
        While (i >= 0)
            Me.ListBox1.Items.Add(strUserid & ", " & strUserName)
            i = mRMCom.GetNextUserID(strUserid, strUserName)
        End While
'
 End Sub

Open in new window

cdsouthernAsked:
Who is Participating?

Improve company productivity with a Business Account.Sign Up

x
 
SStoryConnect With a Mentor Commented:
I'm sorry, I don't know why. Most of the things I found on MSDN and Google were related to SharePoint and this doesn't seem to be SharePoint.

Possibilities.  Does the COM object read the registry? If so does IUSR have rights to those keys?

You might go to sysinternals.com and download filemon and regmon, run them on the IIS server and when you hit this page see what it is trying to access and if there are any access denied messages.

Other than this I don't know what more to suggest.
0
 
SStoryCommented:
Things like this are usually a permissions problem.  When you run in Visual Studio, I guess you are running as you, but when you hit it from IIS you are running as

IUSR_<yourmachinename> user account.
This account must have permissions to the DLL....if it is in another location.

See this:
http://support.softartisans.com/kbview_883.aspx

be sure the above user account has proper permissions for the .dll and folder it is in
0
 
cdsouthernAuthor Commented:
I have provided Full Access to both the ASPNET user and IUSR_<machinename> accounts for the folder containing the COM dll.  I also tried copying the dll to the bin folder in the website.  No luck with either.
0
Free Tool: Subnet Calculator

The subnet calculator helps you design networks by taking an IP address and network mask and returning information such as network, broadcast address, and host range.

One of a set of tools we're offering as a way of saying thank you for being a part of the community.

 
SStoryCommented:
OK. how about permissions on the com dll itself. Does IUSR have permissions to the file?
0
 
cdsouthernAuthor Commented:
Yes, it has the same permissions as the containing folder.  Looks like it inherited the folder permissions.
0
 
cdsouthernAuthor Commented:
The COM dll does read from the registry.  The solution was to give the local user ASPNET proper access to the appropriate registry key (RMCLIENT32 in our case).
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.