March 15, 2004 at 9:26 pm
Hi,
I made some extended strored procedures
and they goes well when they are placed at
c:/windows/system32 or the same derectory to
sqlservr.exe which is usualy in C:/Program Files/
Microsoft SQL Server/MSSQL/Binn.
I thought it's OK wherever they are placed
as long as I put them to the system path.
But actually they didn't work at all
when they were placed to the other path
that I had newly added as a system path.
Here is the contents of 'path' valiable:
%SystemRoot%/system32;%SystemRoot%;%SystemRoot%/Sy
stem32/Wbem;C:/WINDOWS/System32/AmiClick;C:/Progra
m Files/Microsoft SQL Server/80/Tools/BINN:C:/Program Files/INC
I just added only "C:/Program Files/INC",
placed the extended stored procedures there,
then called them through a trigger.
Can Somebody tell me what was wrong?
Please help me if you have any informations about this issue.
regards,
Takanobu Maekawa
March 17, 2004 at 12:04 am
It is not necessary to put dll in 'path'.
Registers the extended stored procedure with following, specify dllname with full path.
sp_addextendedproc [ @functname = ] 'procedure' ,
[ @dllname = ] 'dll'
March 28, 2004 at 7:19 am
Thanks for reply.
But there was the need to make the dll's path not exactly specified.
And finally, I've solved this problem.
I don't know this is the essential solution for this problem,
but today, once I rebooted the Server machine
(it's been long time --at least 2 months since I rebooted the server machine last time),then the system path which I added began to work well !!
March 28, 2004 at 9:58 am
It depends on how you set the path as to whether or not reboot is needed. I always do for safety but check with command promt by typing PATH and see if updated.
Viewing 4 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply