MSSQL2005 SP2 and DB-Lib Connection

We have some legacy processes written in C with embedded SQL. They were
compiled with MSSQL2000 libraries and used db-lib for database connections.
After the database was upgraded to MSSQL2005, they could still make the
connection. Recently we have applied MSSQL2005 service pack 2 on the test
server and these processes can no longer connect (error message: SQL Server
is unavailable or does not exist). All other apps using the native client
work OK. Is there anything I can do at the MSSQL side to allow those legacy
processes to connect? Thanks.
Wow... it's been awhile since I supported C and DBLib. I taught this at MSU
for 5 years or so but that was a LONG time ago...
Ok, consider that DBLib requires a matched set of the named pipes DLL and
the dblib dll. If these get out of sync then you're pooched.
I'm really surprised that you've been able to hold out this long. I would
get up on Connect and report a bug but I doubt if they support DBLib any
longer. I don't think there is anything you can do on the server side to fix
it--except rolling back SP2. I expect the tightened the TDS in some way that
made it incompatible with legacy DBLib apps.
hth
____________________________________
William (Bill) Vaughn
Author, Mentor, Consultant
Microsoft MVP
INETA Speaker
www.betav.com/blog/billva
www.betav.com
Please reply only to the newsgroup so that others can benefit.
This posting is provided "AS IS" with no warranties, and confers no rights.
__________________________________
Visit www.hitchhikerguides.net to get more information on my latest book:
Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition)
and Hitchhiker's Guide to SQL Server 2005 Compact Edition (EBook)
------
"mason" <masonliu@.msn.com> wrote in message
news:O8MZ$FsdHHA.984@.TK2MSFTNGP04.phx.gbl...
> We have some legacy processes written in C with embedded SQL. They were
> compiled with MSSQL2000 libraries and used db-lib for database
> connections. After the database was upgraded to MSSQL2005, they could
> still make the connection. Recently we have applied MSSQL2005 service pack
> 2 on the test server and these processes can no longer connect (error
> message: SQL Server is unavailable or does not exist). All other apps
> using the native client work OK. Is there anything I can do at the MSSQL
> side to allow those legacy processes to connect? Thanks.
|||We will rewrite them if we have to, but if there is a way to give them
another life, ... Thanks.
"William (Bill) Vaughn" <billvaRemoveThis@.betav.com> wrote in message
news:ubW7bCudHHA.3272@.TK2MSFTNGP03.phx.gbl...[vbcol=seagreen]
> Wow... it's been awhile since I supported C and DBLib. I taught this at
> MSU for 5 years or so but that was a LONG time ago...
> Ok, consider that DBLib requires a matched set of the named pipes DLL and
> the dblib dll. If these get out of sync then you're pooched.
> I'm really surprised that you've been able to hold out this long. I would
> get up on Connect and report a bug but I doubt if they support DBLib any
> longer. I don't think there is anything you can do on the server side to
> fix it--except rolling back SP2. I expect the tightened the TDS in some
> way that made it incompatible with legacy DBLib apps.
> hth
> --
> ____________________________________
> William (Bill) Vaughn
> Author, Mentor, Consultant
> Microsoft MVP
> INETA Speaker
> www.betav.com/blog/billva
> www.betav.com
> Please reply only to the newsgroup so that others can benefit.
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
> __________________________________
> Visit www.hitchhikerguides.net to get more information on my latest book:
> Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition)
> and Hitchhiker's Guide to SQL Server 2005 Compact Edition (EBook)
> ------
> "mason" <masonliu@.msn.com> wrote in message
> news:O8MZ$FsdHHA.984@.TK2MSFTNGP04.phx.gbl...
|||Did the test server work before you applied SP@. and did you also upgrade the
test server from SQL 2000? The reason I ask is that SQL Server 2005 doesn't
include the dblib dll anymore so the only way it would have worked is if the
dll was left over from SQL Server 2000.
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
"mason" <masonliu@.msn.com> wrote in message
news:O8MZ$FsdHHA.984@.TK2MSFTNGP04.phx.gbl...
> We have some legacy processes written in C with embedded SQL. They were
> compiled with MSSQL2000 libraries and used db-lib for database
> connections. After the database was upgraded to MSSQL2005, they could
> still make the connection. Recently we have applied MSSQL2005 service pack
> 2 on the test server and these processes can no longer connect (error
> message: SQL Server is unavailable or does not exist). All other apps
> using the native client work OK. Is there anything I can do at the MSSQL
> side to allow those legacy processes to connect? Thanks.
|||Yes. It worked with MSSQL2005 SP1. The test server was created from scratch
with MSSQL2005. We copied two DLLs (ntwdblib.dll and sqlakw32.dll) from
MSSQL2000 client.
"Roger Wolter[MSFT]" <rwolter@.online.microsoft.com> wrote in message
news:70709573-251D-4E13-8F60-75AF6858DD62@.microsoft.com...
> Did the test server work before you applied SP@. and did you also upgrade
> the test server from SQL 2000? The reason I ask is that SQL Server 2005
> doesn't include the dblib dll anymore so the only way it would have worked
> is if the dll was left over from SQL Server 2000.
> --
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
> Use of included script samples are subject to the terms specified at
> http://www.microsoft.com/info/cpyright.htm
> "mason" <masonliu@.msn.com> wrote in message
> news:O8MZ$FsdHHA.984@.TK2MSFTNGP04.phx.gbl...
>
|||Did you register both DLLs?
____________________________________
William (Bill) Vaughn
Author, Mentor, Consultant
Microsoft MVP
INETA Speaker
www.betav.com/blog/billva
www.betav.com
Please reply only to the newsgroup so that others can benefit.
This posting is provided "AS IS" with no warranties, and confers no rights.
__________________________________
Visit www.hitchhikerguides.net to get more information on my latest book:
Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition)
and Hitchhiker's Guide to SQL Server 2005 Compact Edition (EBook)
------
"mason" <masonliu@.msn.com> wrote in message
news:%2301l8PvdHHA.5056@.TK2MSFTNGP02.phx.gbl...
> Yes. It worked with MSSQL2005 SP1. The test server was created from
> scratch with MSSQL2005. We copied two DLLs (ntwdblib.dll and sqlakw32.dll)
> from MSSQL2000 client.
>
> "Roger Wolter[MSFT]" <rwolter@.online.microsoft.com> wrote in message
> news:70709573-251D-4E13-8F60-75AF6858DD62@.microsoft.com...
>
|||No. Tried to register now and got error msgs such as
DllRegisterServer/DllInstall entry points not found.
Those processes are working fine under MSSQL2005 SP1 in production.
"William (Bill) Vaughn" <billvaRemoveThis@.betav.com> wrote in message
news:e4nA%23i5dHHA.984@.TK2MSFTNGP04.phx.gbl...[vbcol=seagreen]
> Did you register both DLLs?
> --
> ____________________________________
> William (Bill) Vaughn
> Author, Mentor, Consultant
> Microsoft MVP
> INETA Speaker
> www.betav.com/blog/billva
> www.betav.com
> Please reply only to the newsgroup so that others can benefit.
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
> __________________________________
> Visit www.hitchhikerguides.net to get more information on my latest book:
> Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition)
> and Hitchhiker's Guide to SQL Server 2005 Compact Edition (EBook)
> ------
> "mason" <masonliu@.msn.com> wrote in message
> news:%2301l8PvdHHA.5056@.TK2MSFTNGP02.phx.gbl...