July 22, 2009 at 2:32 pm
Hi,
What I have is a SQL 2005 32 bit running 32 bit dll and we are upgrading to SQL 2005 64 bit. The dll is being call from a system extended stored procedure. When it gets call I get an error "Could not load the DLL C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Binn\xp_ept.dll, or one of the DLLs it references. Reason: 193(%1 is not a valid Win32 application.)." I tried putting the dll into the syswow64 and changing the stored procedure and get the same error. I can't convert the dll to 64 because I do not have the source.
Thanks
Mark
July 28, 2009 at 8:21 pm
I am 99.999% sure that you can't get around this, 64bit sql demands 64bit extended stored procedures..
CEWII
July 29, 2009 at 2:17 pm
If the DLL is .net, you can use .net reflector to grab the source code and recompile it for x64. Be carefull doing this in case the original code or reflector uses 32 bit specific logic. i.e. bitwise operations, or I think some methods of implementing serialization
Dan Guzman - Not the MVP (7/22/2010)
All questions have to be prefaced by Server version and 'according to MS Docs' or 'my own personal opinion based on how much detail I felt like digging into at the time.'
July 31, 2009 at 8:44 am
I didn't think you could write extended stored procedures in .Net.. Maybe it was just you coldn't do it in C# or VB..
CEWII
May 5, 2011 at 9:07 am
Yes, you can write extended stored procedures in .NET without a problem.
But you really need to make it in 64bit for 64bit SQL Server.
I have about 6 extended stored procs writen in C++ .NET but i could do it in C# if i want to or VB.NET
In .NET if you can write something in one language you can write it in another becouse all that matters is the IL that it makes in the compilation.
Just recompile it in a 64bit enviroment and you are done.
I am just replying here to answer to this .NET problem. It's not cool to keep a Thread with wrong information, ppl can google into here and find a wrong info.
Cya.
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply