Hi All,
I have Downloaded both MSXML 4.0 SP2 and SQLXML.
Are they are same. If not can any one please tell me what for that both are
used?
Thanks
PrabhatHi
MSXML 4.0 SDK is a development environment to create XML applications
http://msdn.microsoft.com/library/d...xmloverview.asp
SQLXML enables XML support for SQL Server 2000
http://msdn.microsoft.com/library/d...>
h_SQLXML.asp
SQLXML will use MSXML and you will need both to use SQLXML, for instance
SqlXml 3.0 SP2 has a dependency on MSXML version 4.0 SP2, so MSXML version
4.0 SP2 is included in it's download.
HTH
John
"Prabhat Nath" wrote:
> Hi All,
> I have Downloaded both MSXML 4.0 SP2 and SQLXML.
> Are they are same. If not can any one please tell me what for that both ar
e
> used?
> Thanks
> Prabhat
>
>|||Hi John, Thanks for your Information.
Prabhat
"John Bell" <JohnBell@.discussions.microsoft.com> wrote in message
news:B40F325B-6C3A-4FE4-8FCE-4B65463CE8BE@.microsoft.com...
> Hi
> MSXML 4.0 SDK is a development environment to create XML applications
>
http://msdn.microsoft.com/library/d...-us/xmlsdk/html
/xmmscxmloverview.asp
> SQLXML enables XML support for SQL Server 2000
>
http://msdn.microsoft.com/library/d...-us/dnanchor/ht
ml/anch_SQLXML.asp
> SQLXML will use MSXML and you will need both to use SQLXML, for instance
> SqlXml 3.0 SP2 has a dependency on MSXML version 4.0 SP2, so MSXML version
> 4.0 SP2 is included in it's download.
> HTH
> John
>
> "Prabhat Nath" wrote:
>
are
Showing posts with label sp2. Show all posts
Showing posts with label sp2. Show all posts
Wednesday, March 21, 2012
Monday, March 19, 2012
MSSQLSERVER Service Shuts down
For the past few days, our SQL Server 2005 SP2 has been shutting down. The
Exchange and IIS services are still running. Restarting the service works,
but there are no events recorded in the event log. The SQL server is
hosting a single, small database that supports the navigation controls for a
developmental web-site and other than the security updates released last
week, no changes have been made to SQL Server itself.
Mike Ober.Hi
Is it open to internet ? What is an account that MSSQLSERVER run under?
"Michael D. Ober" <obermd.@..alum.mit.edu.nospam> wrote in message
news:uhVm38reHHA.4704@.TK2MSFTNGP06.phx.gbl...
> For the past few days, our SQL Server 2005 SP2 has been shutting down.
> The Exchange and IIS services are still running. Restarting the service
> works, but there are no events recorded in the event log. The SQL server
> is hosting a single, small database that supports the navigation controls
> for a developmental web-site and other than the security updates released
> last week, no changes have been made to SQL Server itself.
> Mike Ober.
>
Exchange and IIS services are still running. Restarting the service works,
but there are no events recorded in the event log. The SQL server is
hosting a single, small database that supports the navigation controls for a
developmental web-site and other than the security updates released last
week, no changes have been made to SQL Server itself.
Mike Ober.Hi
Is it open to internet ? What is an account that MSSQLSERVER run under?
"Michael D. Ober" <obermd.@..alum.mit.edu.nospam> wrote in message
news:uhVm38reHHA.4704@.TK2MSFTNGP06.phx.gbl...
> For the past few days, our SQL Server 2005 SP2 has been shutting down.
> The Exchange and IIS services are still running. Restarting the service
> works, but there are no events recorded in the event log. The SQL server
> is hosting a single, small database that supports the navigation controls
> for a developmental web-site and other than the security updates released
> last week, no changes have been made to SQL Server itself.
> Mike Ober.
>
MSSQLSERVER Service Shuts down
For the past few days, our SQL Server 2005 SP2 has been shutting down. The
Exchange and IIS services are still running. Restarting the service works,
but there are no events recorded in the event log. The SQL server is
hosting a single, small database that supports the navigation controls for a
developmental web-site and other than the security updates released last
week, no changes have been made to SQL Server itself.
Mike Ober.
Hi
Is it open to internet ? What is an account that MSSQLSERVER run under?
"Michael D. Ober" <obermd.@..alum.mit.edu.nospam> wrote in message
news:uhVm38reHHA.4704@.TK2MSFTNGP06.phx.gbl...
> For the past few days, our SQL Server 2005 SP2 has been shutting down.
> The Exchange and IIS services are still running. Restarting the service
> works, but there are no events recorded in the event log. The SQL server
> is hosting a single, small database that supports the navigation controls
> for a developmental web-site and other than the security updates released
> last week, no changes have been made to SQL Server itself.
> Mike Ober.
>
Exchange and IIS services are still running. Restarting the service works,
but there are no events recorded in the event log. The SQL server is
hosting a single, small database that supports the navigation controls for a
developmental web-site and other than the security updates released last
week, no changes have been made to SQL Server itself.
Mike Ober.
Hi
Is it open to internet ? What is an account that MSSQLSERVER run under?
"Michael D. Ober" <obermd.@..alum.mit.edu.nospam> wrote in message
news:uhVm38reHHA.4704@.TK2MSFTNGP06.phx.gbl...
> For the past few days, our SQL Server 2005 SP2 has been shutting down.
> The Exchange and IIS services are still running. Restarting the service
> works, but there are no events recorded in the event log. The SQL server
> is hosting a single, small database that supports the navigation controls
> for a developmental web-site and other than the security updates released
> last week, no changes have been made to SQL Server itself.
> Mike Ober.
>
MSSQLSERVER Service Shuts down
For the past few days, our SQL Server 2005 SP2 has been shutting down. The
Exchange and IIS services are still running. Restarting the service works,
but there are no events recorded in the event log. The SQL server is
hosting a single, small database that supports the navigation controls for a
developmental web-site and other than the security updates released last
week, no changes have been made to SQL Server itself.
Mike Ober.Hi
Is it open to internet ? What is an account that MSSQLSERVER run under?
"Michael D. Ober" <obermd.@..alum.mit.edu.nospam> wrote in message
news:uhVm38reHHA.4704@.TK2MSFTNGP06.phx.gbl...
> For the past few days, our SQL Server 2005 SP2 has been shutting down.
> The Exchange and IIS services are still running. Restarting the service
> works, but there are no events recorded in the event log. The SQL server
> is hosting a single, small database that supports the navigation controls
> for a developmental web-site and other than the security updates released
> last week, no changes have been made to SQL Server itself.
> Mike Ober.
>
Exchange and IIS services are still running. Restarting the service works,
but there are no events recorded in the event log. The SQL server is
hosting a single, small database that supports the navigation controls for a
developmental web-site and other than the security updates released last
week, no changes have been made to SQL Server itself.
Mike Ober.Hi
Is it open to internet ? What is an account that MSSQLSERVER run under?
"Michael D. Ober" <obermd.@..alum.mit.edu.nospam> wrote in message
news:uhVm38reHHA.4704@.TK2MSFTNGP06.phx.gbl...
> For the past few days, our SQL Server 2005 SP2 has been shutting down.
> The Exchange and IIS services are still running. Restarting the service
> works, but there are no events recorded in the event log. The SQL server
> is hosting a single, small database that supports the navigation controls
> for a developmental web-site and other than the security updates released
> last week, no changes have been made to SQL Server itself.
> Mike Ober.
>
mssqlserver service doesn't start
after installing report services and sp2 , the service mssqlserver does not
start in automatic mode and remain in starting. Only in manual mode.
Version
Sql server 2000 with sp3
Thank you
Gianluca
Make SQL Service is set to auto-start.
Paul Zanbaka
DBA, Programmer Analyst
"Gianluca Danielli" wrote:
> after installing report services and sp2 , the service mssqlserver does not
> start in automatic mode and remain in starting. Only in manual mode.
> Version
> Sql server 2000 with sp3
> Thank you
|||Yes it is
"Paul Zanbaka" wrote:
[vbcol=seagreen]
> Gianluca
> Make SQL Service is set to auto-start.
> --
> Paul Zanbaka
> DBA, Programmer Analyst
>
> "Gianluca Danielli" wrote:
|||Have you rebooted the server? Did you check the event logs?
"Gianluca Danielli" wrote:
[vbcol=seagreen]
> Yes it is
> "Paul Zanbaka" wrote:
|||yes there are not errors in the event log
"fnguy" wrote:
[vbcol=seagreen]
> Have you rebooted the server? Did you check the event logs?
> "Gianluca Danielli" wrote:
|||If the service attempts to start but fails then there should be an error in
the NT System log. Is there?
If not, and it is set to stat automatically (Verify through control panel
services) then I think you need to speak with MPSS. My guess is that there
are errors in the system event log.
"Gianluca Danielli" wrote:
[vbcol=seagreen]
> yes there are not errors in the event log
> "fnguy" wrote:
start in automatic mode and remain in starting. Only in manual mode.
Version
Sql server 2000 with sp3
Thank you
Gianluca
Make SQL Service is set to auto-start.
Paul Zanbaka
DBA, Programmer Analyst
"Gianluca Danielli" wrote:
> after installing report services and sp2 , the service mssqlserver does not
> start in automatic mode and remain in starting. Only in manual mode.
> Version
> Sql server 2000 with sp3
> Thank you
|||Yes it is
"Paul Zanbaka" wrote:
[vbcol=seagreen]
> Gianluca
> Make SQL Service is set to auto-start.
> --
> Paul Zanbaka
> DBA, Programmer Analyst
>
> "Gianluca Danielli" wrote:
|||Have you rebooted the server? Did you check the event logs?
"Gianluca Danielli" wrote:
[vbcol=seagreen]
> Yes it is
> "Paul Zanbaka" wrote:
|||yes there are not errors in the event log
"fnguy" wrote:
[vbcol=seagreen]
> Have you rebooted the server? Did you check the event logs?
> "Gianluca Danielli" wrote:
|||If the service attempts to start but fails then there should be an error in
the NT System log. Is there?
If not, and it is set to stat automatically (Verify through control panel
services) then I think you need to speak with MPSS. My guess is that there
are errors in the system event log.
"Gianluca Danielli" wrote:
[vbcol=seagreen]
> yes there are not errors in the event log
> "fnguy" wrote:
mssqlserver service doesn't start
after installing report services and sp2 , the service mssqlserver does not
start in automatic mode and remain in starting. Only in manual mode.
Version
Sql server 2000 with sp3
Thank youGianluca
Make SQL Service is set to auto-start.
--
Paul Zanbaka
DBA, Programmer Analyst
"Gianluca Danielli" wrote:
> after installing report services and sp2 , the service mssqlserver does no
t
> start in automatic mode and remain in starting. Only in manual mode.
> Version
> Sql server 2000 with sp3
> Thank you|||Yes it is
"Paul Zanbaka" wrote:
[vbcol=seagreen]
> Gianluca
> Make SQL Service is set to auto-start.
> --
> Paul Zanbaka
> DBA, Programmer Analyst
>
> "Gianluca Danielli" wrote:
>|||Have you rebooted the server? Did you check the event logs?
"Gianluca Danielli" wrote:
[vbcol=seagreen]
> Yes it is
> "Paul Zanbaka" wrote:
>|||yes there are not errors in the event log
"fnguy" wrote:
[vbcol=seagreen]
> Have you rebooted the server? Did you check the event logs?
> "Gianluca Danielli" wrote:
>|||If the service attempts to start but fails then there should be an error in
the NT System log. Is there?
If not, and it is set to stat automatically (Verify through control panel
services) then I think you need to speak with MPSS. My guess is that there
are errors in the system event log.
"Gianluca Danielli" wrote:
[vbcol=seagreen]
> yes there are not errors in the event log
> "fnguy" wrote:
>
start in automatic mode and remain in starting. Only in manual mode.
Version
Sql server 2000 with sp3
Thank youGianluca
Make SQL Service is set to auto-start.
--
Paul Zanbaka
DBA, Programmer Analyst
"Gianluca Danielli" wrote:
> after installing report services and sp2 , the service mssqlserver does no
t
> start in automatic mode and remain in starting. Only in manual mode.
> Version
> Sql server 2000 with sp3
> Thank you|||Yes it is
"Paul Zanbaka" wrote:
[vbcol=seagreen]
> Gianluca
> Make SQL Service is set to auto-start.
> --
> Paul Zanbaka
> DBA, Programmer Analyst
>
> "Gianluca Danielli" wrote:
>|||Have you rebooted the server? Did you check the event logs?
"Gianluca Danielli" wrote:
[vbcol=seagreen]
> Yes it is
> "Paul Zanbaka" wrote:
>|||yes there are not errors in the event log
"fnguy" wrote:
[vbcol=seagreen]
> Have you rebooted the server? Did you check the event logs?
> "Gianluca Danielli" wrote:
>|||If the service attempts to start but fails then there should be an error in
the NT System log. Is there?
If not, and it is set to stat automatically (Verify through control panel
services) then I think you need to speak with MPSS. My guess is that there
are errors in the system event log.
"Gianluca Danielli" wrote:
[vbcol=seagreen]
> yes there are not errors in the event log
> "fnguy" wrote:
>
mssqlserver service doesn't start
after installing report services and sp2 , the service mssqlserver does not
start in automatic mode and remain in starting. Only in manual mode.
Version
Sql server 2000 with sp3
Thank youGianluca
Make SQL Service is set to auto-start.
--
Paul Zanbaka
DBA, Programmer Analyst
"Gianluca Danielli" wrote:
> after installing report services and sp2 , the service mssqlserver does not
> start in automatic mode and remain in starting. Only in manual mode.
> Version
> Sql server 2000 with sp3
> Thank you|||Yes it is
"Paul Zanbaka" wrote:
> Gianluca
> Make SQL Service is set to auto-start.
> --
> Paul Zanbaka
> DBA, Programmer Analyst
>
> "Gianluca Danielli" wrote:
> > after installing report services and sp2 , the service mssqlserver does not
> > start in automatic mode and remain in starting. Only in manual mode.
> > Version
> > Sql server 2000 with sp3
> >
> > Thank you|||Have you rebooted the server? Did you check the event logs?
"Gianluca Danielli" wrote:
> Yes it is
> "Paul Zanbaka" wrote:
> > Gianluca
> > Make SQL Service is set to auto-start.
> > --
> > Paul Zanbaka
> > DBA, Programmer Analyst
> >
> >
> > "Gianluca Danielli" wrote:
> >
> > > after installing report services and sp2 , the service mssqlserver does not
> > > start in automatic mode and remain in starting. Only in manual mode.
> > > Version
> > > Sql server 2000 with sp3
> > >
> > > Thank you|||yes there are not errors in the event log
"fnguy" wrote:
> Have you rebooted the server? Did you check the event logs?
> "Gianluca Danielli" wrote:
> > Yes it is
> >
> > "Paul Zanbaka" wrote:
> >
> > > Gianluca
> > > Make SQL Service is set to auto-start.
> > > --
> > > Paul Zanbaka
> > > DBA, Programmer Analyst
> > >
> > >
> > > "Gianluca Danielli" wrote:
> > >
> > > > after installing report services and sp2 , the service mssqlserver does not
> > > > start in automatic mode and remain in starting. Only in manual mode.
> > > > Version
> > > > Sql server 2000 with sp3
> > > >
> > > > Thank you|||If the service attempts to start but fails then there should be an error in
the NT System log. Is there?
If not, and it is set to stat automatically (Verify through control panel
services) then I think you need to speak with MPSS. My guess is that there
are errors in the system event log.
"Gianluca Danielli" wrote:
> yes there are not errors in the event log
> "fnguy" wrote:
> > Have you rebooted the server? Did you check the event logs?
> >
> > "Gianluca Danielli" wrote:
> >
> > > Yes it is
> > >
> > > "Paul Zanbaka" wrote:
> > >
> > > > Gianluca
> > > > Make SQL Service is set to auto-start.
> > > > --
> > > > Paul Zanbaka
> > > > DBA, Programmer Analyst
> > > >
> > > >
> > > > "Gianluca Danielli" wrote:
> > > >
> > > > > after installing report services and sp2 , the service mssqlserver does not
> > > > > start in automatic mode and remain in starting. Only in manual mode.
> > > > > Version
> > > > > Sql server 2000 with sp3
> > > > >
> > > > > Thank you
start in automatic mode and remain in starting. Only in manual mode.
Version
Sql server 2000 with sp3
Thank youGianluca
Make SQL Service is set to auto-start.
--
Paul Zanbaka
DBA, Programmer Analyst
"Gianluca Danielli" wrote:
> after installing report services and sp2 , the service mssqlserver does not
> start in automatic mode and remain in starting. Only in manual mode.
> Version
> Sql server 2000 with sp3
> Thank you|||Yes it is
"Paul Zanbaka" wrote:
> Gianluca
> Make SQL Service is set to auto-start.
> --
> Paul Zanbaka
> DBA, Programmer Analyst
>
> "Gianluca Danielli" wrote:
> > after installing report services and sp2 , the service mssqlserver does not
> > start in automatic mode and remain in starting. Only in manual mode.
> > Version
> > Sql server 2000 with sp3
> >
> > Thank you|||Have you rebooted the server? Did you check the event logs?
"Gianluca Danielli" wrote:
> Yes it is
> "Paul Zanbaka" wrote:
> > Gianluca
> > Make SQL Service is set to auto-start.
> > --
> > Paul Zanbaka
> > DBA, Programmer Analyst
> >
> >
> > "Gianluca Danielli" wrote:
> >
> > > after installing report services and sp2 , the service mssqlserver does not
> > > start in automatic mode and remain in starting. Only in manual mode.
> > > Version
> > > Sql server 2000 with sp3
> > >
> > > Thank you|||yes there are not errors in the event log
"fnguy" wrote:
> Have you rebooted the server? Did you check the event logs?
> "Gianluca Danielli" wrote:
> > Yes it is
> >
> > "Paul Zanbaka" wrote:
> >
> > > Gianluca
> > > Make SQL Service is set to auto-start.
> > > --
> > > Paul Zanbaka
> > > DBA, Programmer Analyst
> > >
> > >
> > > "Gianluca Danielli" wrote:
> > >
> > > > after installing report services and sp2 , the service mssqlserver does not
> > > > start in automatic mode and remain in starting. Only in manual mode.
> > > > Version
> > > > Sql server 2000 with sp3
> > > >
> > > > Thank you|||If the service attempts to start but fails then there should be an error in
the NT System log. Is there?
If not, and it is set to stat automatically (Verify through control panel
services) then I think you need to speak with MPSS. My guess is that there
are errors in the system event log.
"Gianluca Danielli" wrote:
> yes there are not errors in the event log
> "fnguy" wrote:
> > Have you rebooted the server? Did you check the event logs?
> >
> > "Gianluca Danielli" wrote:
> >
> > > Yes it is
> > >
> > > "Paul Zanbaka" wrote:
> > >
> > > > Gianluca
> > > > Make SQL Service is set to auto-start.
> > > > --
> > > > Paul Zanbaka
> > > > DBA, Programmer Analyst
> > > >
> > > >
> > > > "Gianluca Danielli" wrote:
> > > >
> > > > > after installing report services and sp2 , the service mssqlserver does not
> > > > > start in automatic mode and remain in starting. Only in manual mode.
> > > > > Version
> > > > > Sql server 2000 with sp3
> > > > >
> > > > > Thank you
Monday, March 12, 2012
MSSQLSERVER Error 17830
Hi,
Please help me with this before I get crazy....
Please help me with this before I get crazy....
I have VS 2005 and SQL server 2005 installed on XP ( with SP2 ) I create a new web project. Make a SQL connection to my database and configure the advanced options. Drag gridview component to my form and configure it to use the connection with edit option checked. When I run my form I can scroll and view the data with no problem at all. Even edit works fine BUT the changes to the row NEVER gets to the database. No error messages what so ever. XP:s Event View reports this:
Type: Error
Source: MSSQLSERVER
Class: Logon
Code: 17830
A network error occurred while establishing a connection; the connection has been closed. This may have been caused by client or server login timeout expiration. Time spent during login: total 31 ms, enqueued 1 ms, network writes 1 ms, network reads 30 ms, establishing SSL 29 ms, negotiating SSPI 0 ms, validating login 0 ms. [CLIENT: <local machine>]
Any ideas what is wrong?
Regards, Jarmo
Is it possible that in the connection string in the client application you've specified the option to require encryption?If this is the case and the server doesn't have an SSL certificate configured from a trusted authority then the client driver may be dropping the connection during the SSL handshake because it doesn't trust the server's SSL certificate.
Hope this helps,
Vaughn
Friday, March 9, 2012
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...
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...
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...
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...
MSSQL2005 Express SP2 on Vista Professional does not support Extended SP?
Can you explain please why Extended SP does not work under Vista ?
Microsoft SQL Server 2005 - 9.00.3042.00 (Intel X86) Feb 9 2007 22:47:07 Copyright (c) 1988-2005 Microsoft Corporation Express Edition on Windows NT 6.0 (Build 6000: )
UAC turned off. MSQSL runs under Administrator account.
Any call of user esp - and SQL server goes to loop.
If I call system esp - all works fine.
If I try to read properties of ESP from Management Studio - I have the same effect - SQL server is in loop.
select object_id('dbo.xp_mylog')
-- works.
EXEC('sp_helpextendedproc ''xp_mylog''')
xp_mylog c:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Binn\LogEsp.dll
exec master..xp_mylog
die forever
Konstantin
Hi Konstantin,
Have you enabled extended sprocs? They are disabled by default.
Mike
|||No I did not. How to do this ? I know how to do in Stanard Edition. But this option not visible in Express edition.
There is a TSQL statement to change it or change it in the registry ?
|||is any body can halp me ?
|||Is there is anybody from Microsoft who knows how to enable ESP ?
|||I guess, this is what Mike means:
Open SAC > ...for features ... Navigate your instance ... OLE Automation > enable
Jens K. Suessmeyer
http://www.sqlserver2005.de
Extended Stored Procedure is not ActiveX
MSSQL2005 Express SP2 on Vista Professional does not support Extended SP?
Can you explain please why Extended SP does not work under Vista ?
Microsoft SQL Server 2005 - 9.00.3042.00 (Intel X86) Feb 9 2007 22:47:07 Copyright (c) 1988-2005 Microsoft Corporation Express Edition on Windows NT 6.0 (Build 6000: )
UAC turned off. MSQSL runs under Administrator account.
Any call of user esp - and SQL server goes to loop.
If I call system esp - all works fine.
If I try to read properties of ESP from Management Studio - I have the same effect - SQL server is in loop.
select object_id('dbo.xp_mylog')
-- works.
EXEC('sp_helpextendedproc ''xp_mylog''')
xp_mylog c:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Binn\LogEsp.dll
exec master..xp_mylog
die forever
Konstantin
Hi Konstantin,
Have you enabled extended sprocs? They are disabled by default.
Mike
|||No I did not. How to do this ? I know how to do in Stanard Edition. But this option not visible in Express edition.
There is a TSQL statement to change it or change it in the registry ?
|||is any body can halp me ?
|||Is there is anybody from Microsoft who knows how to enable ESP ?
|||I guess, this is what Mike means:
Open SAC > ...for features ... Navigate your instance ... OLE Automation > enable
Jens K. Suessmeyer
http://www.sqlserver2005.de
Extended Stored Procedure is not ActiveX
MSSQL2005 Express SP2 on Vista Professional does not support Extended SP?
Can you explain please why Extended SP does not work under Vista ?
Microsoft SQL Server 2005 - 9.00.3042.00 (Intel X86) Feb 9 2007 22:47:07 Copyright (c) 1988-2005 Microsoft Corporation Express Edition on Windows NT 6.0 (Build 6000: )
UAC turned off. MSQSL runs under Administrator account.
Any call of user esp - and SQL server goes to loop.
If I call system esp - all works fine.
If I try to read properties of ESP from Management Studio - I have the same effect - SQL server is in loop.
select object_id('dbo.xp_mylog')
-- works.
EXEC('sp_helpextendedproc ''xp_mylog''')
xp_mylog c:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Binn\LogEsp.dll
exec master..xp_mylog
die forever
Konstantin
Hi Konstantin,
Have you enabled extended sprocs? They are disabled by default.
Mike
|||No I did not. How to do this ? I know how to do in Stanard Edition. But this option not visible in Express edition.
There is a TSQL statement to change it or change it in the registry ?
|||is any body can halp me ?
|||Is there is anybody from Microsoft who knows how to enable ESP ?
|||I guess, this is what Mike means:
Open SAC > ...for features ... Navigate your instance ... OLE Automation > enable
Jens K. Suessmeyer
http://www.sqlserver2005.de
Extended Stored Procedure is not ActiveX
MSSQL2005 Express SP2 on Vista Professional does not support Extended SP?
Can you explain please why Extended SP does not work under Vista ?
Microsoft SQL Server 2005 - 9.00.3042.00 (Intel X86) Feb 9 2007 22:47:07 Copyright (c) 1988-2005 Microsoft Corporation Express Edition on Windows NT 6.0 (Build 6000: )
UAC turned off. MSQSL runs under Administrator account.
Any call of user esp - and SQL server goes to loop.
If I call system esp - all works fine.
If I try to read properties of ESP from Management Studio - I have the same effect - SQL server is in loop.
select object_id('dbo.xp_mylog')
-- works.
EXEC('sp_helpextendedproc ''xp_mylog''')
xp_mylog c:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Binn\LogEsp.dll
exec master..xp_mylog
die forever
Konstantin
Hi Konstantin,
Have you enabled extended sprocs? They are disabled by default.
Mike
|||No I did not. How to do this ? I know how to do in Stanard Edition. But this option not visible in Express edition.
There is a TSQL statement to change it or change it in the registry ?
|||is any body can halp me ?
|||Is there is anybody from Microsoft who knows how to enable ESP ?
|||I guess, this is what Mike means:
Open SAC > ...for features ... Navigate your instance ... OLE Automation > enable
Jens K. Suessmeyer
http://www.sqlserver2005.de
Extended Stored Procedure is not ActiveX
Subscribe to:
Posts (Atom)