May 18, 2007 at 5:33 am
The error list below is the one we are getting when attemping to run the extended stored procedure
Msg 17750, Level 16, State 0, Procedure sp_HVC_helpDLL, Line 1
Could not load the DLL C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Binn\sp_hvc.dll, or one of the DLLs it references. Reason: 126(The specified module could not be found.).
As per earlier test to run the extended stored procedure in SQL SERVER 2005 server, it was successful, latter we found that edition of the SQL SERVER 2005 was Microsoft SQL Server 2005 - 9.00.1406.00 (Intel X86) Mar 3 2007 18:40:02 Copyright (c) 1988-2005 Microsoft Corporation Developer Edition on Windows NT 5.2 (Build 3790: Service Pack 1).
The extended stored procedures are running fine even without the registering them with full path of the dll i.e. “C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Binn\sp_hvc.dll”.
We suspect that the failure of extended stored procedures might be due to the difference in SQL SERVER 2005 Editions. The Editions available in other servers where the extended stored procedures fail is listed below
Ø Microsoft SQL Server 2005 - 9.00.1406.00 (Intel X86) Mar 3 2007 18:40:02 Copyright (c) 1988-2005 Microsoft Corporation
Standard Edition on Windows NT 5.2 (Build 3790: Service Pack 1).
Ø Microsoft SQL Server 2005 - 9.00.3054.00 (Intel X86) Mar 23 2007 16:28:52 Copyright (c) 1988-2005 Microsoft Corporation
Standard Edition on Windows NT 5.2 (Build 3790: Service Pack 1).
Ø Microsoft SQL Server 2005 - 9.00.1399.06 (Intel X86) Oct 14 2005 00:33:37 Copyright (c) 1988-2005 Microsoft Corporation
May 18, 2007 at 4:04 pm
Is the Mismatch between the Procedure name that SQL has on the error, and the actual assembly name a problem?
Are you running SQL Server as an account that has permission to access the DLL / Local File System?
If this is a .NET Assembly, are all the CAS permissions set properly on the server and in the application? I have tried to run assemblies before and the OS thinks they are in the InternetZone (because I dragged and dropped the file and did not copy and paste) and does not give them permission to run (moved files do not inherit thier parent objects permissions!). Try Taking Ownership or resetting the permissions on the file (and in CAS / .NET config admin) and see if it works.
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply