| Groups | Blog | Home |
sql server programming : Can't get xp_hello sample to work
I try compiling the xp_hello.dll sample using the Visual C++ Toolkit, as follows: cl xp_hello.c /I "C:\program files\microsoft sql server\80\tools\devtools\include" /LD /nologo /MT /W3 /GX /O2 /D "WIN32" /D "NDEBUG" /D "_WINDOWS" /D "_MBCS" /D "_USRDLL" /D "XP_HELLO_EXPORTS" /YX /FD /link /dll /def:xp_hello.def ...\..\..\lib\opends60.lib /machine:I386 When I add to the server and then try to call the extended proc xp_hello, I get an error 127 that entry point xp_hello can't be found. But I have checked with depends.exe, and it is being exported from xp_hello! The builtin extended procs (e.g. those in xpstar.dll) all work fine, and running depends.exe on xpstar.dll I can't see any difference between them and xp_hello.dll.... Anyone able to help? Thanks
[quoted text, click to view]
"Simon Kissane" <skissane@gmail.com> wrote in message news:82fa6638.0410072215.77b87501@posting.google.com... > Hi, > > I try compiling the xp_hello.dll sample using the Visual C++ Toolkit, > as follows: > > cl xp_hello.c /I "C:\program files\microsoft sql > server\80\tools\devtools\include" /LD /nologo /MT /W3 /GX /O2 /D > "WIN32" /D "NDEBUG" /D "_WINDOWS" /D "_MBCS" /D "_USRDLL" /D > "XP_HELLO_EXPORTS" /YX /FD /link /dll /def:xp_hello.def > ..\..\..\lib\opends60.lib /machine:I386 > > When I add to the server and then try to call the extended proc > xp_hello, I get an error 127 that entry point xp_hello can't be > found. But I have checked with depends.exe, and it is being exported > from xp_hello! The builtin extended procs (e.g. those in xpstar.dll) > all work fine, and running depends.exe on xpstar.dll I can't see any > difference between them and xp_hello.dll.... > > Anyone able to help? > > Thanks > Simon Kissane Have you do these? 1. Register it in SQL with sp_addextendedproc command. 2. Copy your xp_hello.dll to your SQL Server \Binn directory
[quoted text, click to view]
"Jonathan Chong" <jonathan@3exp.com> wrote in message news:<ezw2kAQrEHA.4080@TK2MSFTNGP10.phx.gbl>... Yes, I have copied it to Binn and registered it with> "Simon Kissane" <skissane@gmail.com> wrote in message > news:82fa6638.0410072215.77b87501@posting.google.com... > > Hi, > > > > I try compiling the xp_hello.dll sample using the Visual C++ Toolkit, > > as follows: > > > > cl xp_hello.c /I "C:\program files\microsoft sql > > server\80\tools\devtools\include" /LD /nologo /MT /W3 /GX /O2 /D > > "WIN32" /D "NDEBUG" /D "_WINDOWS" /D "_MBCS" /D "_USRDLL" /D > > "XP_HELLO_EXPORTS" /YX /FD /link /dll /def:xp_hello.def > > ..\..\..\lib\opends60.lib /machine:I386 > > > > When I add to the server and then try to call the extended proc > > xp_hello, I get an error 127 that entry point xp_hello can't be > > found. But I have checked with depends.exe, and it is being exported > > from xp_hello! The builtin extended procs (e.g. those in xpstar.dll) > > all work fine, and running depends.exe on xpstar.dll I can't see any > > difference between them and xp_hello.dll.... > > > > Anyone able to help? > > > > Thanks > > Simon Kissane > > Have you do these? > 1. Register it in SQL with sp_addextendedproc command. > 2. Copy your xp_hello.dll to your SQL Server \Binn directory sp_addextendedproc. I know it is loading the DLL, because it gives me the message: ODBC: Msg 0, Level 16, State 1 Cannot find the function xp_hello in the library xp_hello.dll. Reason: 127(The specified procedure could not be found.). Whereas, if I use a non-existent name, e.g. xp_hello2.dll, I get the different message: ODBC: Msg 0, Level 16, State 1 Cannot load the DLL xp_hello2.dll, or one of the DLLs it references. Reason: 126(The specified module could not be found.). So the problem is not with loading the DLL; rather, it is with finding the entry point in the DLL. But depends.exe says the entry point is there. I have tried both using a .DEF file (the one supplied with the sample by MS), and with using __declspec(dllexport) before the __GetXpVersion and xp_hello functions, and neither seems to make a difference. (i.e. depends.exe reports dll entry point is there, but SQL Server, although it can find the DLL, it can't find the entry point....) Thanks
Check this out
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/odssql/ods_6_con_01_26hx.asp You might be facing the same problem as the link. Hope it helps. [quoted text, click to view] "Simon Kissane" <skissane@gmail.com> wrote in message news:82fa6638.0410101828.57adcf75@posting.google.com... > "Jonathan Chong" <jonathan@3exp.com> wrote in message news:<ezw2kAQrEHA.4080@TK2MSFTNGP10.phx.gbl>... > > "Simon Kissane" <skissane@gmail.com> wrote in message > > news:82fa6638.0410072215.77b87501@posting.google.com... > > > Hi, > > > > > > I try compiling the xp_hello.dll sample using the Visual C++ Toolkit, > > > as follows: > > > > > > cl xp_hello.c /I "C:\program files\microsoft sql > > > server\80\tools\devtools\include" /LD /nologo /MT /W3 /GX /O2 /D > > > "WIN32" /D "NDEBUG" /D "_WINDOWS" /D "_MBCS" /D "_USRDLL" /D > > > "XP_HELLO_EXPORTS" /YX /FD /link /dll /def:xp_hello.def > > > ..\..\..\lib\opends60.lib /machine:I386 > > > > > > When I add to the server and then try to call the extended proc > > > xp_hello, I get an error 127 that entry point xp_hello can't be > > > found. But I have checked with depends.exe, and it is being exported > > > from xp_hello! The builtin extended procs (e.g. those in xpstar.dll) > > > all work fine, and running depends.exe on xpstar.dll I can't see any > > > difference between them and xp_hello.dll.... > > > > > > Anyone able to help? > > > > > > Thanks > > > Simon Kissane > > > > Have you do these? > > 1. Register it in SQL with sp_addextendedproc command. > > 2. Copy your xp_hello.dll to your SQL Server \Binn directory > Yes, I have copied it to Binn and registered it with > sp_addextendedproc. I know it is loading the DLL, because it gives me > the message: > ODBC: Msg 0, Level 16, State 1 > Cannot find the function xp_hello in the library xp_hello.dll. Reason: > 127(The specified procedure could not be found.). > > Whereas, if I use a non-existent name, e.g. xp_hello2.dll, I get the > different message: > ODBC: Msg 0, Level 16, State 1 > Cannot load the DLL xp_hello2.dll, or one of the DLLs it references. > Reason: 126(The specified module could not be found.). > > So the problem is not with loading the DLL; rather, it is with finding > the entry point in the DLL. But depends.exe says the entry point is > there. > > I have tried both using a .DEF file (the one supplied with the sample > by MS), and with using __declspec(dllexport) before the __GetXpVersion > and xp_hello functions, and neither seems to make a difference. (i.e. > depends.exe reports dll entry point is there, but SQL Server, although > it can find the DLL, it can't find the entry point....) > > Thanks > Simon Kissane
[quoted text, click to view]
"Jonathan Chong" <jonathan@3exp.com> wrote in message news:<uCmQfk2rEHA.1204@TK2MSFTNGP12.phx.gbl>... > Check this out > http://msdn.microsoft.com/library/default.asp?url=/library/en-us/odssql/ods_6_con_01_26hx.asp > You might be facing the same problem as the link. Hope it helps. Thanks, but unfortunately not much help there either. The documentation says: """" If the name of the function specified in sp_addextendedproc does not exactly match the function name in the DLL, the new name will be registered in SQL Server, but the name will not be usable. For example, although xp_Hello is registered as a SQL Server extended stored procedure located in xp_hello.dll, SQL Server will not be able to find the function in the DLL if you use xp_Hello to call the function later. """" But, I checked, I am registering it as xp_hello (all lower case) using sp_addextendedproc, calling it as xp_hello (all lower case), and its exported from the dll as xp_hello (all lower case).... So that doesn't seem to be the problem, since I'm using exactly the same case
[quoted text, click to view]
"Jonathan Chong" <jonathan@3exp.com> wrote in message news:<O2msMtAsEHA.1164@TK2MSFTNGP10.phx.gbl>... No, I don't own a copy of that.> Are you using Microsoft Visual C++ 6.0? So far I have been using it to build > and compile extended stored proc without any problem. > May be you can try it from there. Just choose "Extended Stored Procedure > Wizard" in project selection dialog. I have been using the free Microsoft Visual C++ Toolkit 2003. It is basically the command line tools (cl.exe) for Visual Studio .NET 2003 C++, but without the IDE. Could you maybe email me or post on the web your xp_hello.dll, so we can see if it is my server or my compiler? Thanks
Are you using Microsoft Visual C++ 6.0? So far I have been using it to build
and compile extended stored proc without any problem. May be you can try it from there. Just choose "Extended Stored Procedure Wizard" in project selection dialog. [quoted text, click to view] "Simon Kissane" <skissane@gmail.com> wrote in message news:82fa6638.0410111607.2a49dca2@posting.google.com... > "Jonathan Chong" <jonathan@3exp.com> wrote in message news:<uCmQfk2rEHA.1204@TK2MSFTNGP12.phx.gbl>... > > Check this out > > http://msdn.microsoft.com/library/default.asp?url=/library/en-us/odssql/ods_6_con_01_26hx.asp > > You might be facing the same problem as the link. Hope it helps. > > Thanks, but unfortunately not much help there either. > > The documentation says: > """" If the name of the function specified in sp_addextendedproc does > not exactly match the function name in the DLL, the new name will be > registered in SQL Server, but the name will not be usable. For > example, although xp_Hello is registered as a SQL Server extended > stored procedure located in xp_hello.dll, SQL Server will not be able > to find the function in the DLL if you use xp_Hello to call the > function later. """" > > But, I checked, I am registering it as xp_hello (all lower case) using > sp_addextendedproc, calling it as xp_hello (all lower case), and its > exported from the dll as xp_hello (all lower case).... So that doesn't > seem to be the problem, since I'm using exactly the same case > throughout....
Don't see what you're looking for? Try a search.
|
January 2003
March 2003
April 2003
May 2003
June 2003
July 2003
August 2003
September 2003
October 2003
November 2003
December 2003
January 2004
February 2004
March 2004
April 2004
May 2004
June 2004
July 2004
August 2004
September 2004
October 2004
November 2004
December 2004
January 2005
February 2005
March 2005
April 2005
May 2005
June 2005
July 2005
August 2005
September 2005
October 2005
November 2005
December 2005
January 2006
February 2006
March 2006
April 2006
May 2006
June 2006
July 2006
August 2006
September 2006
October 2006
November 2006
December 2006
January 2007
February 2007
March 2007
April 2007
May 2007
June 2007
July 2007
August 2007
September 2007
October 2007
November 2007
April 2008
August 2008
| home · blog · groups | Questions? Comments? Contact the dn |