Extended Stored Procedure DLL Problem on Win2k+3

[rawCoder]

Hi All,

Sorry for cross posting , but my neck on the line forced me to do this
disgusting act.

I have an Extended Stored Procedure DLL made in VC 7.0
It was working fine on my development PC (Windows 2000 Professional ) and
worked just fine on couple of other development PCS.
When the DLL was deployed on the Win2003 server its normal invokation raises
following error.
ODBC: Msg 0, Level 16, State 1
Cannot load the DLL MYESPDLL.dll, or one of the DLLs it references. Reason:
126(The specified module could not be found.).
Depends tool shows three dependancies MSCOREE.DLL, MSVCR70.DLL,
OPENDS60.DLL -
All of these are available either on system path or being copied where the
dll is along with .NET Framework 1.1 that comes with the server.
The dll uses configuration settings and sends intimation to client via
socket, but that should not be much of a problem as it worked fine on the
development PCs.

Please help me.

Thank You in Advance.
rawCoder

[Patrik Löwendahl [C# MVP]]

Don't know if this has with your problem to do, but you should never create
a extended stored proceudure built with the CLR. It collides with the SQL
server memory and thread managment.

Have a look at:

http://support.microsoft.com/default...b;en-us;322884

--
Patrik Löwendahl [C# MVP]
www.cshrp.net - "Elegant code by witty programmers"

"rawCoder" <ra******@hotmail.com> wrote in message
news:O2**************@TK2MSFTNGP15.phx.gbl...

Hi All,

Sorry for cross posting , but my neck on the line forced me to do this
disgusting act.

I have an Extended Stored Procedure DLL made in VC 7.0
It was working fine on my development PC (Windows 2000 Professional ) and
worked just fine on couple of other development PCS.
When the DLL was deployed on the Win2003 server its normal invokation raises following error.
ODBC: Msg 0, Level 16, State 1
Cannot load the DLL MYESPDLL.dll, or one of the DLLs it references. Reason: 126(The specified module could not be found.).
Depends tool shows three dependancies MSCOREE.DLL, MSVCR70.DLL,
OPENDS60.DLL -
All of these are available either on system path or being copied where the
dll is along with .NET Framework 1.1 that comes with the server.
The dll uses configuration settings and sends intimation to client via
socket, but that should not be much of a problem as it worked fine on the
development PCs.

Please help me.

Thank You in Advance.
rawCoder

[rawCoder]

Thanx for super prompt reply.
Well I just got to know about this problem.
The thing is that I used the wizard with VS.NET - so why is it provided ?

And the problem is solved , it was the dumbest of mistake.

Thanx anyways
rawCoder

"Patrik Löwendahl [C# MVP]" <pa**************@csharpsweden.com> wrote in
message news:%2******************@TK2MSFTNGP11.phx.gbl...

Don't know if this has with your problem to do, but you should never create a extended stored proceudure built with the CLR. It collides with the SQL
server memory and thread managment.

Have a look at:

http://support.microsoft.com/default...b;en-us;322884

--
Patrik Löwendahl [C# MVP]
www.cshrp.net - "Elegant code by witty programmers"

"rawCoder" <ra******@hotmail.com> wrote in message
news:O2**************@TK2MSFTNGP15.phx.gbl...

Hi All,

Sorry for cross posting , but my neck on the line forced me to do this
disgusting act.

I have an Extended Stored Procedure DLL made in VC 7.0
It was working fine on my development PC (Windows 2000 Professional ) and worked just fine on couple of other development PCS.
When the DLL was deployed on the Win2003 server its normal invokation

raises

following error.
ODBC: Msg 0, Level 16, State 1
Cannot load the DLL MYESPDLL.dll, or one of the DLLs it references.

Reason:

126(The specified module could not be found.).
Depends tool shows three dependancies MSCOREE.DLL, MSVCR70.DLL,
OPENDS60.DLL -
All of these are available either on system path or being copied where the dll is along with .NET Framework 1.1 that comes with the server.
The dll uses configuration settings and sends intimation to client via
socket, but that should not be much of a problem as it worked fine on the development PCs.

Please help me.

Thank You in Advance.
rawCoder

[Gert E.R. Drapers]

The Wizard is a C++ wizard, not a .NET wizard, but since you could include
MC++ code it can not prevent that. Any how Wizards are in general not smart
to begin with :)

Ge***@SQLDev.Net

Please reply only to the newsgroups.
This posting is provided "AS IS" with no warranties, and confers no rights.
You assume all risk for your use.
Copyright © SQLDev.Net 1991-2004 All rights reserved.

"rawCoder" <ra******@hotmail.com> wrote in message
news:Ok**************@TK2MSFTNGP11.phx.gbl...

Thanx for super prompt reply.
Well I just got to know about this problem.
The thing is that I used the wizard with VS.NET - so why is it provided ?

And the problem is solved , it was the dumbest of mistake.

Thanx anyways
rawCoder

"Patrik Löwendahl [C# MVP]" <pa**************@csharpsweden.com> wrote in
message news:%2******************@TK2MSFTNGP11.phx.gbl...

Don't know if this has with your problem to do, but you should never

create

a extended stored proceudure built with the CLR. It collides with the SQL
server memory and thread managment.

Have a look at:

http://support.microsoft.com/default...b;en-us;322884

--
Patrik Löwendahl [C# MVP]
www.cshrp.net - "Elegant code by witty programmers"

"rawCoder" <ra******@hotmail.com> wrote in message
news:O2**************@TK2MSFTNGP15.phx.gbl...

> Hi All,
>
> Sorry for cross posting , but my neck on the line forced me to do this
> disgusting act.
>
> I have an Extended Stored Procedure DLL made in VC 7.0
> It was working fine on my development PC (Windows 2000 Professional ) and > worked just fine on couple of other development PCS.
> When the DLL was deployed on the Win2003 server its normal invokation

raises

> following error.
>
>
> ODBC: Msg 0, Level 16, State 1
> Cannot load the DLL MYESPDLL.dll, or one of the DLLs it references.

Reason:

> 126(The specified module could not be found.).
>
>
> Depends tool shows three dependancies MSCOREE.DLL, MSVCR70.DLL,
> OPENDS60.DLL -
> All of these are available either on system path or being copied where the > dll is along with .NET Framework 1.1 that comes with the server.
> The dll uses configuration settings and sends intimation to client via
> socket, but that should not be much of a problem as it worked fine on the > development PCs.
>
> Please help me.
>
> Thank You in Advance.
> rawCoder
>
>