iMan Admin Deployment Errors

Hello,
I created a application that uses the iManAdmin.dll within a custom ASP.NET application. The application runs correctly in the dev environment but when deploying it in Test I get the error at the below. What I am doing is taking my custom dll and taking the Test box dlls for iMANADMIN.dll and Interop.iManAdmin.dll and placing them in the bin directory. Is it necessary to regeister the iManAdmin.dll and Interop.iManAdmin.dll?

Server Error in '/DMSAdmin' Application.
--------------------------------------------------------------------------------

The located assembly's manifest definition with name 'Interop.IMANADMIN' does not match the assembly reference.
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.

Exception Details: System.IO.FileLoadException: The located assembly's manifest definition with name 'Interop.IMANADMIN' does not match the assembly reference.

Source Error:

An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.

Assembly Load Trace: The following information can be helpful to determine why the assembly 'Interop.IMANADMIN' could not be loaded.

=== Pre-bind state information ===
LOG: DisplayName = Interop.IMANADMIN, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null
(Fully-specified)
LOG: Appbase = file:///E:/Inetpub/DMS/DMSAdmin
LOG: Initial PrivatePath = bin
Calling assembly : DMSAdmin, Version=1.0.2452.39283, Culture=neutral, PublicKeyToken=null.
===

LOG: Policy not being applied to reference at this time (private, custom, partial, or location-based assembly bind).
LOG: Post-policy reference: Interop.IMANADMIN, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null
LOG: Attempting download of new URL file:///C:/WINDOWS/Microsoft.NET/Framework/v1.1.4322/Temporary ASP.NET Files/dmsadmin/870b0484/859a09e8/Interop.IMANADMIN.DLL.
LOG: Attempting download of new URL file:///C:/WINDOWS/Microsoft.NET/Framework/v1.1.4322/Temporary ASP.NET Files/dmsadmin/870b0484/859a09e8/Interop.IMANADMIN/Interop.IMANADMIN.DLL.
LOG: Attempting download of new URL file:///E:/Inetpub/DMS/DMSAdmin/bin/Interop.IMANADMIN.DLL.
WRN: Comparing the assembly name resulted in the mismatch: PUBLIC KEY TOKEN

Stack Trace:

[FileLoadException: The located assembly's manifest definition with name 'Interop.IMANADMIN' does not match the assembly reference.]
DMSAdmin.WebForm1.btnLogin_Click(Object sender, EventArgs e) +0
System.Web.UI.WebControls.Button.OnClick(EventArgs e) +108
System.Web.UI.WebControls.Button.System.Web.UI.IPostBackEventHandler.RaisePostBackEvent(String eventArgument) +57
System.Web.UI.Page.RaisePostBackEvent(IPostBackEventHandler sourceControl, String eventArgument) +18
System.Web.UI.Page.RaisePostBackEvent(NameValueCollection postData) +33
System.Web.UI.Page.ProcessRequestMain() +1292

--------------------------------------------------------------------------------
Version Information: Microsoft .NET Framework Version:1.1.4322.2300; ASP.NET Version:1.1.4322.2300

Find more posts tagged with

Comments

jny

I believe either you would need to deploy it by .NET packaging or use Regasm to register the DLL's on the client machine.

jny

One more thing: check whether the client machine has the same .NET framework.

BIRTReport.png

kuruption213

thanks for the help the problem lied with the Interop.ImanAdmin dll not being the same as the one on production. Initially I thought they were by comparing the Interops of both that came with the product. However after I built it the dll changed. Once I put in my Interop dll it worked fine.