LAPI and .NET (x64)

Hi, I have a .NET LAPI program that was running fine on our old windows 2000 servers. However, now that it has been moved to a Windows 2003 Server running on a dual core x64 AMD Opteron it has been throwing exceptions when it tries to connect. I should note: our other non-.NET programs will work fine on that machine(W2003/x64); also, the affected .NET program will work fine on a non-x64 machine connecting to that same x64 server it crashes on (it just won't run ON the server as it used to). The exception sometimes change to a BIFE error, but this exception is more common: StackTrace " at com.opentext.api.LLConnect..ctor(String host, Int32 port, String user, String password)\r\n at com.opentext.api.LLSession..ctor(String host, Int32 port, String database, String user, String password) string LAPI_NETp.dll threw exception... Message " is not a valid Win32 application. (Exception from HRESULT: 0x800700C1)" string Various forums suggest that the problem might be that for some reason it is expecting an x64 version of LAPI_NETp.dll and I've already confirmed with Opentext support that an x86 version isn't ready yet, only the 32-bit version. Anyone else using LAPI and .NET (and more importantly, anyone else using LAPI and .NET on a non-x86 bit processor)?

Find more posts tagged with

Comments

Michael_Grantham

Hi, we're facing the same situation on a Windows 2003 x64 server. Wondering if you found a resolution to your problem?

Appreciate your help.

Marko_Genzel

Have you tried to force your LAPI application to run in 32 bit mode?

http://blogs.intesoft.net/post/2007/12/Running-NET-Apps-in-32-bit-mode-on-64-bit-Windows.aspx

Another option might be to install a .NET 32 bit runtime environment on that 64 bit box.

However, I never tried either one of these option because we haven't run into this issue yet.

Marko

Ferdinand Prantl

Have a look at the thread https://knowledge.opentext.com/go/17261369 which discussed the 64-bit LAPI too.

--- Ferda

Michael_Grantham

Quoted Marko Genzel (marko.genzel@vwcredit.com) on 2010/04/15 11:25:

Have you tried to force your LAPI application to run in 32 bit mode?

http://blogs.intesoft.net/post/2007/12/Running-NET-Apps-in-32-bit-mode-on-64-bit-Windows.aspx

Another option might be to install a .NET 32 bit runtime environment on that 64 bit box.

However, I never tried either one of these option because we haven't run into this issue yet.

Marko

Thanks Marko. Will look into your tip.

Michael_Grantham

Quoted Ferdinand Prantl (ferdipr) on 2010/04/15 11:29:

Have a look at the thread https://knowledge.opentext.com/go/17261369 which discussed the 64-bit LAPI too.

--- Ferda

Thanks Ferda. I had gone through your suggested post and unfortunately none of the alternatives are applicable to the scenario that we're facing. Our problem is that the application can't load the LAPI_NETp dll in memory on a x64 box.