.NET Runtime DLL Problem, Revisited

Jesse__Wolfe_(ApolloUser4_(Delete)_2153026)

HiI'm getting a familiar error when I try and run my LAPI application in the .NET environment:File or assembly name LAPI_SSPIp, or one of its dependencies, was not found.I posted this question last month, and learned that due to an unmanaged code portion of one of the libraries, the LAPI library path must be in the system PATH variable. That fixed it the first time, and I have been using it successfully. But several things happened at once... we installed some hardware diagnostic software (which munged the system path a bit) and, I changed how the reference to one of my own developed libraries was set up for the solution.Is there ANYTHING else that anyone can suggest to check as to what might be causing this error? I've included the stack trace on the error page below.Thanks, Jesse Wolfe=== Pre-bind state information ===LOG: DisplayName = LAPI_SSPIp (Partial)LOG: Appbase = file:///C:/Inetpub/wwwroot/LLSLOG: Initial PrivatePath = binCalling assembly : (Unknown).===LOG: Policy not being applied to reference at this time (private, custom, partial, or location-based assembly bind).LOG: Post-policy reference: LAPI_SSPIpLOG: Attempting download of new URL file:///C:/WINNT/Microsoft.NET/Framework/v1.1.4322/Temporary ASP.NET Files/lls/497da6f1/5f750ac7/LAPI_SSPIp.DLL.LOG: Attempting download of new URL file:///C:/WINNT/Microsoft.NET/Framework/v1.1.4322/Temporary ASP.NET Files/llshortcut/497da6f1/5f750ac7/LAPI_SSPIp/LAPI_SSPIp.DLL.LOG: Attempting download of new URL file:///C:/Inetpub/wwwroot/LLS/bin/LAPI_SSPIp.DLL.LOG: Policy not being applied to reference at this time (private, custom, partial, or location-based assembly bind).LOG: Post-policy reference: LAPI_SSPIp, Version=9.1.0.3, Culture=neutral, PublicKeyToken=null

Find more posts tagged with

Comments

Ann_Minton

The LAPI 9.1.0 SP3 Release Notes (12/17/02) state: "LAPI_NETp.dll is dependent upon LAPI_SSPIp.dll. LAPI_SSPIp.dll is dependent upon LAPI_BASE.dll and LLKERNEL.dll. In some LAPI .NET deployment scenarios, such as deploying a LAPI ASP.NET application, LAPI_BASE.dll and LLKERNEL.dll must be located by the system via the PATH environment variable."This statement is true for both .NET 1.0 and .NET 1.1. However, we have since discovered that for .NET 1.1, you must place the Microsoft file MSVCR70.DLL in the system path as well. We recommend placing the file in the \winnt\system32 directory. I have attached the required file to this message.For future releases of LAPI we will ask the user during installation if they would like the installer to put the LAPI bin directory into their system PATH. We will also redistribute MSVCR70.DLL and install it into the system32 directory (if needed), just as we do with the MSVCP60.DLL and MSVCRT.DLL files.

Jesse__Wolfe_(ApolloUser4_(Delete)_2153026)

Hi Ann,Unfortunately, things don't seem to be working with this solution.... just get the same error. :(Is this supplied DLL compatible with Windows .NET Server 2003? That's the platform I'm running 1.1 on.Jesse

Jesse__Wolfe_(ApolloUser4_(Delete)_2153026)

I put the DLL in \WINDOWS\SYSTEM32.