We have Windows XP pro running on a laptop. I can connect
to the server and our databases but when I try to open a
table I get the following message
"[Microsoft][ODBC Driver manager] Only SQL_DRIVER_NOPROMPT
is allowed when connection pooling is enabled"
Does anybody know why this is happening. I downloaded the
mdac 2.7 sp1 and installed it. Still the same issue.
thanksNormally this would happen when an application is written to ask the user
for his db credentials every time it needs to log on to the database, and at
the same time has connection pooling enabled. Those two options are
incompatible.
If the app in questions opens & closes many connections throughout it's
lifetime, you'll definitely want to have connection pooling enabled. You
might want to refer to online info such as
http://support.microsoft.com/defaul...kb;en-us;169470 or
_connection_pooling.asp." target="_blank">http://msdn.microsoft.com/library/d...on_pooling.asp.
SQL_DRIVER_NOPROMPT should be specified to your call to SQLDriverConnect
when connection pooling is enabled.
Hope that helps.
- Dave
"Steve" <sr@.vincentinc.com> wrote in message
news:f17101c43d9d$1ca5e350$a101280a@.phx.gbl...
> We have Windows XP pro running on a laptop. I can connect
> to the server and our databases but when I try to open a
> table I get the following message
>
> "[Microsoft][ODBC Driver manager] Only SQL_DRIVER_NOPROMPT
> is allowed when connection pooling is enabled"
> Does anybody know why this is happening. I downloaded the
> mdac 2.7 sp1 and installed it. Still the same issue.
> thanks
>|||Thanks for your help. upon further investigation it was
only happening when the added SQL enterprise manager to a
mmc console. We dreleted the MMC console and recreated it
and the problem has since gone away.
Again thank you.
Steve
>--Original Message--
>Normally this would happen when an application is written
to ask the user
>for his db credentials every time it needs to log on to
the database, and at
>the same time has connection pooling enabled. Those two
options are
>incompatible.
>If the app in questions opens & closes many connections
throughout it's
>lifetime, you'll definitely want to have connection
pooling enabled. You
>might want to refer to online info such as
>http://support.microsoft.com/default.aspx?scid=kb;en-
us;169470 or
>http://msdn.microsoft.com/library/default.asp?
url=/library/en-
us/odbc/htm/odbcodbc_connection_pooling.asp.
>SQL_DRIVER_NOPROMPT should be specified to your call to
SQLDriverConnect
>when connection pooling is enabled.
>Hope that helps.
>- Dave
>
>"Steve" <sr@.vincentinc.com> wrote in message
>news:f17101c43d9d$1ca5e350$a101280a@.phx.gbl...
connect[vbcol=seagreen]
SQL_DRIVER_NOPROMPT[vbcol=seagreen]
the[vbcol=seagreen]
>
>.
>|||Ok its back.
The Enterprise manager snap when used in a customized MMC
window... Very odd the default console that launches
with the Enterprise Manager icon works fine and only
fails intermittently with MMC. It is odd because it only
happens when I try reviewing all rows in a table. I can
change the structure of a table just not view the data?
>--Original Message--
>Thanks for your help. upon further investigation it was
>only happening when the added SQL enterprise manager to
a
>mmc console. We dreleted the MMC console and recreated
it
>and the problem has since gone away.
>Again thank you.
>Steve
written[vbcol=seagreen]
>to ask the user
>the database, and at
>options are
>throughout it's
>pooling enabled. You
>us;169470 or
>url=/library/en-
>us/odbc/htm/odbcodbc_connection_pooling.asp.
>SQLDriverConnect
>connect
open a[vbcol=seagreen]
>SQL_DRIVER_NOPROMPT
downloaded[vbcol=seagreen]
>the
>.
>
Showing posts with label databases. Show all posts
Showing posts with label databases. Show all posts
Thursday, March 22, 2012
Connection Pooling
Is there some way to use only a single connection pool for more than 10 diferent databases?No, you get a connection pool per unique connection string. (Any changes to the connection string, including parameter ordering, extra spaces, etc. will create a new connection pool. The connection pooling layer doesn't try to do any parsing to determine equivalent connection strings.)
Connections to databases are expensive to establish. Connection pooling keeps a connection open for a certain amount of time after you issue a conn.Close() assuming that you might want to use it again. You have a physical connection between your client and a specific database over some protocol, such as TCP/IP, named pipes, or other. So using the same connection pool across multiple databases doesn't make logical sense to me.
Could you explain in more detail what you're trying to accomplish? Maybe you are using the wrong terminology.|||First, thanx for your post James!
I do already know about a connection pool per connection string. I'm trying to figure out some way to eliminate this. Can be anything at low level. I'm studying the OLEDB technology to discover if it is possible and is plausible. I agree with you about "doesn't make logical sense". I'm playing with this :).
Thanx, once again... If you know anything else let me know.|||You can always turn off OLE DB connection pooling and then roll your own. Add the following to the connection string: "OLE DB Services=-4". (This also turns off automatic transaction enlistment.) More details can be found here:
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpguide/html/cpconconnectionpoolingforoledbnetdataprovider.asp
and here:
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/oledb/htm/oledbabout_the_ole_db_documentation.asp
Other providers use their own syntax for disabling connection pooling. For instance, the SQL Server Client Provider uses the syntax "Pooling=false".sqlsql
connection pooling
We have windows xp pro running on a laptop. I can connect
to the server and our databases but when I try to open a
table I get the following message
"[Microsoft][ODBC Driver manager] Only SQL_DRIVER_NOPROMPT
is allowed when connection pooling is enabled"
Does anybody know why this is happening. I downloaded the
mdac 2.7 sp1 and installed it. Still the same issue.
thanks
Normally this would happen when an application is written to ask the user
for his db credentials every time it needs to log on to the database, and at
the same time has connection pooling enabled. Those two options are
incompatible.
If the app in questions opens & closes many connections throughout it's
lifetime, you'll definitely want to have connection pooling enabled. You
might want to refer to online info such as
http://support.microsoft.com/default...b;en-us;169470 or
http://msdn.microsoft.com/library/de...n_pooling.asp.
SQL_DRIVER_NOPROMPT should be specified to your call to SQLDriverConnect
when connection pooling is enabled.
Hope that helps.
- Dave
"Steve" <sr@.vincentinc.com> wrote in message
news:f17101c43d9d$1ca5e350$a101280a@.phx.gbl...
> We have windows xp pro running on a laptop. I can connect
> to the server and our databases but when I try to open a
> table I get the following message
>
> "[Microsoft][ODBC Driver manager] Only SQL_DRIVER_NOPROMPT
> is allowed when connection pooling is enabled"
> Does anybody know why this is happening. I downloaded the
> mdac 2.7 sp1 and installed it. Still the same issue.
> thanks
>
|||Thanks for your help. upon further investigation it was
only happening when the added SQL enterprise manager to a
mmc console. We dreleted the MMC console and recreated it
and the problem has since gone away.
Again thank you.
Steve
>--Original Message--
>Normally this would happen when an application is written
to ask the user
>for his db credentials every time it needs to log on to
the database, and at
>the same time has connection pooling enabled. Those two
options are
>incompatible.
>If the app in questions opens & closes many connections
throughout it's
>lifetime, you'll definitely want to have connection
pooling enabled. You
>might want to refer to online info such as
>http://support.microsoft.com/default.aspx?scid=kb;en-
us;169470 or
>http://msdn.microsoft.com/library/default.asp?
url=/library/en-
us/odbc/htm/odbcodbc_connection_pooling.asp.
>SQL_DRIVER_NOPROMPT should be specified to your call to
SQLDriverConnect[vbcol=seagreen]
>when connection pooling is enabled.
>Hope that helps.
>- Dave
>
>"Steve" <sr@.vincentinc.com> wrote in message
>news:f17101c43d9d$1ca5e350$a101280a@.phx.gbl...
connect[vbcol=seagreen]
SQL_DRIVER_NOPROMPT[vbcol=seagreen]
the
>
>.
>
|||Ok its back.
The Enterprise manager snap when used in a customized MMC
window... Very odd the default console that launches
with the Enterprise Manager icon works fine and only
fails intermittently with MMC. It is odd because it only
happens when I try reviewing all rows in a table. I can
change the structure of a table just not view the data?
>--Original Message--
>Thanks for your help. upon further investigation it was
>only happening when the added SQL enterprise manager to
a
>mmc console. We dreleted the MMC console and recreated
it[vbcol=seagreen]
>and the problem has since gone away.
>Again thank you.
>Steve
written[vbcol=seagreen]
>to ask the user
>the database, and at
>options are
>throughout it's
>pooling enabled. You
>us;169470 or
>url=/library/en-
>us/odbc/htm/odbcodbc_connection_pooling.asp.
>SQLDriverConnect
>connect
open a[vbcol=seagreen]
>SQL_DRIVER_NOPROMPT
downloaded
>the
>.
>
to the server and our databases but when I try to open a
table I get the following message
"[Microsoft][ODBC Driver manager] Only SQL_DRIVER_NOPROMPT
is allowed when connection pooling is enabled"
Does anybody know why this is happening. I downloaded the
mdac 2.7 sp1 and installed it. Still the same issue.
thanks
Normally this would happen when an application is written to ask the user
for his db credentials every time it needs to log on to the database, and at
the same time has connection pooling enabled. Those two options are
incompatible.
If the app in questions opens & closes many connections throughout it's
lifetime, you'll definitely want to have connection pooling enabled. You
might want to refer to online info such as
http://support.microsoft.com/default...b;en-us;169470 or
http://msdn.microsoft.com/library/de...n_pooling.asp.
SQL_DRIVER_NOPROMPT should be specified to your call to SQLDriverConnect
when connection pooling is enabled.
Hope that helps.
- Dave
"Steve" <sr@.vincentinc.com> wrote in message
news:f17101c43d9d$1ca5e350$a101280a@.phx.gbl...
> We have windows xp pro running on a laptop. I can connect
> to the server and our databases but when I try to open a
> table I get the following message
>
> "[Microsoft][ODBC Driver manager] Only SQL_DRIVER_NOPROMPT
> is allowed when connection pooling is enabled"
> Does anybody know why this is happening. I downloaded the
> mdac 2.7 sp1 and installed it. Still the same issue.
> thanks
>
|||Thanks for your help. upon further investigation it was
only happening when the added SQL enterprise manager to a
mmc console. We dreleted the MMC console and recreated it
and the problem has since gone away.
Again thank you.
Steve
>--Original Message--
>Normally this would happen when an application is written
to ask the user
>for his db credentials every time it needs to log on to
the database, and at
>the same time has connection pooling enabled. Those two
options are
>incompatible.
>If the app in questions opens & closes many connections
throughout it's
>lifetime, you'll definitely want to have connection
pooling enabled. You
>might want to refer to online info such as
>http://support.microsoft.com/default.aspx?scid=kb;en-
us;169470 or
>http://msdn.microsoft.com/library/default.asp?
url=/library/en-
us/odbc/htm/odbcodbc_connection_pooling.asp.
>SQL_DRIVER_NOPROMPT should be specified to your call to
SQLDriverConnect[vbcol=seagreen]
>when connection pooling is enabled.
>Hope that helps.
>- Dave
>
>"Steve" <sr@.vincentinc.com> wrote in message
>news:f17101c43d9d$1ca5e350$a101280a@.phx.gbl...
connect[vbcol=seagreen]
SQL_DRIVER_NOPROMPT[vbcol=seagreen]
the
>
>.
>
|||Ok its back.
The Enterprise manager snap when used in a customized MMC
window... Very odd the default console that launches
with the Enterprise Manager icon works fine and only
fails intermittently with MMC. It is odd because it only
happens when I try reviewing all rows in a table. I can
change the structure of a table just not view the data?
>--Original Message--
>Thanks for your help. upon further investigation it was
>only happening when the added SQL enterprise manager to
a
>mmc console. We dreleted the MMC console and recreated
it[vbcol=seagreen]
>and the problem has since gone away.
>Again thank you.
>Steve
written[vbcol=seagreen]
>to ask the user
>the database, and at
>options are
>throughout it's
>pooling enabled. You
>us;169470 or
>url=/library/en-
>us/odbc/htm/odbcodbc_connection_pooling.asp.
>SQLDriverConnect
>connect
open a[vbcol=seagreen]
>SQL_DRIVER_NOPROMPT
downloaded
>the
>.
>
Sunday, March 11, 2012
Connection is busy with results for another command
We are migrating our databases from MS Access to SQL Server 2005 and using the SQL Native Client ODBC driver.
We also use a reporting tool called Actuate. Some of our Actuate reports use multiple datastreams to build the report.
When I run an Actuate report having multiple datastreams I get the following error message from SQL Server:
Error generated by the connected data source. Connection is busy with results for another command.
Is there a configuration setting in SQL Server to enable processing of multiple result sets?
Thanks.
sqlserver can handle thousands of connections. The error reported sounds like your application error/limitation. I suggest you take a look at the application configuration (i.e. connection or command method).
|||Thanks, oj.I think what's happening is that Actuate is attempting to execute multiple queries simultaneously against the same db connection. The error I'm getting looks to be an ODBC error generated from SQL Server.|||
It's typically the data access provider (odbc, .net, etc.) that the application uses that throws the error. For example, you cannot execute another sqlcommand on the same connection that is being used/processed by a sqldatareader.
http://msdn2.microsoft.com/en-us/library/system.data.sqlclient.sqldatareader.aspx
|||SQL Server introduced MARS which allows multiactive resultssets. have a look in the BOL and see have you can enabled it within your conenctionstring at www.connectionstrings.com
Jens K Suessmeyer
http://www.sqlserver2005.de
Connection is busy with results for another command
We are migrating our databases from MS Access to SQL Server 2005 and using the SQL Native Client ODBC driver.
We also use a reporting tool called Actuate. Some of our Actuate reports use multiple datastreams to build the report.
When I run an Actuate report having multiple datastreams I get the following error message from SQL Server:
Error generated by the connected data source. Connection is busy with results for another command.
Is there a configuration setting in SQL Server to enable processing of multiple result sets?
Thanks.
sqlserver can handle thousands of connections. The error reported sounds like your application error/limitation. I suggest you take a look at the application configuration (i.e. connection or command method).
|||Thanks, oj.I think what's happening is that Actuate is attempting to execute multiple queries simultaneously against the same db connection. The error I'm getting looks to be an ODBC error generated from SQL Server.|||
It's typically the data access provider (odbc, .net, etc.) that the application uses that throws the error. For example, you cannot execute another sqlcommand on the same connection that is being used/processed by a sqldatareader.
http://msdn2.microsoft.com/en-us/library/system.data.sqlclient.sqldatareader.aspx
|||SQL Server introduced MARS which allows multiactive resultssets. have a look in the BOL and see have you can enabled it within your conenctionstring at www.connectionstrings.com
Jens K Suessmeyer
http://www.sqlserver2005.de
Connection is busy with results for another command
We are migrating our databases from MS Access to SQL Server 2005 and using the SQL Native Client ODBC driver.
We also use a reporting tool called Actuate. Some of our Actuate reports use multiple datastreams to build the report.
When I run an Actuate report having multiple datastreams I get the following error message from SQL Server:
Error generated by the connected data source. Connection is busy with results for another command.
Is there a configuration setting in SQL Server to enable processing of multiple result sets?
Thanks.
sqlserver can handle thousands of connections. The error reported sounds like your application error/limitation. I suggest you take a look at the application configuration (i.e. connection or command method).
|||Thanks, oj.I think what's happening is that Actuate is attempting to execute multiple queries simultaneously against the same db connection. The error I'm getting looks to be an ODBC error generated from SQL Server.|||
It's typically the data access provider (odbc, .net, etc.) that the application uses that throws the error. For example, you cannot execute another sqlcommand on the same connection that is being used/processed by a sqldatareader.
http://msdn2.microsoft.com/en-us/library/system.data.sqlclient.sqldatareader.aspx
|||SQL Server introduced MARS which allows multiactive resultssets. have a look in the BOL and see have you can enabled it within your conenctionstring at www.connectionstrings.com
Jens K Suessmeyer
http://www.sqlserver2005.de
Connection is busy with results for another command
We are migrating our databases from MS Access to SQL Server 2005 and using the SQL Native Client ODBC driver.
We also use a reporting tool called Actuate. Some of our Actuate reports use multiple datastreams to build the report.
When I run an Actuate report having multiple datastreams I get the following error message from SQL Server:
Error generated by the connected data source. Connection is busy with results for another command.
Is there a configuration setting in SQL Server to enable processing of multiple result sets?
Thanks.
sqlserver can handle thousands of connections. The error reported sounds like your application error/limitation. I suggest you take a look at the application configuration (i.e. connection or command method).
|||Thanks, oj.I think what's happening is that Actuate is attempting to execute multiple queries simultaneously against the same db connection. The error I'm getting looks to be an ODBC error generated from SQL Server.|||
It's typically the data access provider (odbc, .net, etc.) that the application uses that throws the error. For example, you cannot execute another sqlcommand on the same connection that is being used/processed by a sqldatareader.
http://msdn2.microsoft.com/en-us/library/system.data.sqlclient.sqldatareader.aspx
|||SQL Server introduced MARS which allows multiactive resultssets. have a look in the BOL and see have you can enabled it within your conenctionstring at www.connectionstrings.com
Jens K Suessmeyer
http://www.sqlserver2005.de
Thursday, March 8, 2012
connection failure
Hi all,
Everything is fine until today.
I have two instances(both msde databases, but I have enterprise manager and
analyser installed) on my computer one instance is mssql and the other is
mssql$netsdk (asp.net starter kit database)
somehow the connection to mssql$netsdk is failed which display in enterprise
manager.
So I removed the origianl server registration and start a new one, I type
"BETTYPC\NETSDK" as server and using windows authentication when doing the
registration, but the message display at the last step:
sql server registration failed because of connection failure displayed
below:sqldumpexceptionhandler :process 53 generated a fatal exception
c0000005 EXCEPTION_ACCESS_VIOLATION, sql server is terminating this process.
what's the problem?
Can you help and I am desperated
Betty
Hi Bettys,
Welcome to use MSDN Managed Newsgroup!
From your descriptions, I understood you are not able to connect the SQL
Server named instance NETSDK with error message EXCEPTION_ACCESS_VIOLATION.
If I have misunderstood your concern, please feel free to point it out.
AV errors could be caused by various reasons, please perform the steps
below and let me know the result
1. Check the log file of NETSDK instance, make sure whether the instance
was started correctly.
Defautly, the log will be located at C:\Program Files\Microsoft SQL
Server\MSSQL$NETSDK\log, you may paste them here or send to me directly
v-mingqc@.ONLINEmicrosoft.com if you have concerns on security. (Note that
REMOVE ONLINE in my email address before you click SEND)
2. Is it possible to connect the instance via OSQL and Query Analyzer?
3. Is it possible for you to connect via SQL Authentication?
Sincerely yours,
Michael Cheng
Microsoft Online Partner Support
================================================== ====
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
================================================== ===
This posting is provided "AS IS" with no warranties, and confers no rights.
|||Hi Michael,
Thank you, this is the first post on this forum. I didn't know what went
wrong. The only thing I can do is googling. Then it came to my mind that I
can stop the mssql@.netsdk sql server then and I restarted. It just started
and stopped again somehow. And then I have to restart the computer. After
that I saw both instances have sqlservr.exe process. This time I register the
server again and it looks fine. Connection is OK.
(I didn't try to use osql and did try to use sql authentication, but when I
supplied one userID and password to this server, this password is set up to a
database on this server, it should be OK right? it didn't work either.)
If you can tell what was going on, that will be great.
Here is the paste from errorLog:
2006-02-02 13:12:54.28 server Microsoft SQL Server 2000 - 8.00.760
(Intel X86)
Dec 17 2002 14:22:05
Copyright (c) 1988-2003 Microsoft Corporation
Desktop Engine on Windows NT 5.1 (Build 2600: Service Pack 1)
2006-02-02 13:12:54.28 server Copyright (C) 1988-2002 Microsoft
Corporation.
2006-02-02 13:12:54.28 server All rights reserved.
2006-02-02 13:12:54.28 server Server Process ID is 2988.
2006-02-02 13:12:54.28 server Logging SQL Server messages in file
'C:\Program Files\Microsoft SQL Server\MSSQL$NETSDK\LOG\ERRORLOG'.
2006-02-02 13:12:54.32 server SQL Server is starting at priority class
'normal'(2 CPUs detected).
2006-02-02 13:12:54.50 server SQL Server configured for thread mode
processing.
2006-02-02 13:12:54.50 server Using dynamic lock allocation. [500] Lock
Blocks, [1000] Lock Owner Blocks.
2006-02-02 13:12:54.52 spid4 Starting up database 'master'.
2006-02-02 13:12:54.57 server Using 'SSNETLIB.DLL' version '8.0.766'.
2006-02-02 13:12:54.57 spid5 Starting up database 'model'.
2006-02-02 13:12:54.57 spid4 Server name is 'BETTYPC\NETSDK'.
2006-02-02 13:12:54.57 spid4 Skipping startup of clean database id 4
2006-02-02 13:12:54.57 spid4 Skipping startup of clean database id 5
2006-02-02 13:12:54.57 spid4 Skipping startup of clean database id 6
2006-02-02 13:12:54.57 spid4 Skipping startup of clean database id 7
2006-02-02 13:12:54.57 spid4 Skipping startup of clean database id 8
2006-02-02 13:12:54.57 spid4 Skipping startup of clean database id 9
2006-02-02 13:12:54.57 spid4 Skipping startup of clean database id 10
2006-02-02 13:12:54.57 spid4 Skipping startup of clean database id 11
2006-02-02 13:12:54.57 spid4 Starting up database 'subway'.
2006-02-02 13:12:54.66 spid5 Clearing tempdb database.
2006-02-02 13:12:55.72 server SQL server listening on .
2006-02-02 13:12:55.72 server Error: 17826, Severity: 18, State: 1
2006-02-02 13:12:55.72 server Could not set up Net-Library 'SSNETLIB'..
2006-02-02 13:12:55.72 server Unable to load any netlibs.
2006-02-02 13:12:55.72 server SQL Server could not spawn FRunCM thread.
Here is the sqldump file
================================================== ===================
BugCheck Dump
================================================== ===================
This file is generated by Microsoft SQL Server 8.00.760
upon detection of fatal unexpected error. Please return this file,
the query or program that produced the bugcheck, the database and
the error log, and any other pertinent information with a Service Request.
Betty
"Michael Cheng [MSFT]" wrote:
> Hi Bettys,
> Welcome to use MSDN Managed Newsgroup!
> From your descriptions, I understood you are not able to connect the SQL
> Server named instance NETSDK with error message EXCEPTION_ACCESS_VIOLATION.
> If I have misunderstood your concern, please feel free to point it out.
> AV errors could be caused by various reasons, please perform the steps
> below and let me know the result
> 1. Check the log file of NETSDK instance, make sure whether the instance
> was started correctly.
> Defautly, the log will be located at C:\Program Files\Microsoft SQL
> Server\MSSQL$NETSDK\log, you may paste them here or send to me directly
>if you have concerns on security. (Note that
> REMOVE ONLINE in my email address before you click SEND)
> 2. Is it possible to connect the instance via OSQL and Query Analyzer?
> 3. Is it possible for you to connect via SQL Authentication?
>
> Sincerely yours,
> Michael Cheng
> Microsoft Online Partner Support
> ================================================== ====
> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
> ================================================== ===
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
>
|||Hi Betty,
It seems your SQL Server is not stable. From the startup log, I believe
something internal is wrong. We may noticed "netlibs" is not loaded and
Dump file were also generated.
Although you could register SQL Server now, I would recommend you backup
all the data in this instnace and perform a reinstallation of NETSDK
instance. You may follow the link below to perform a complete uninstall
How to manually remove SQL Server 2000 default, named, or virtual instance
http://support.microsoft.com/kb/290991
If you have any questions or concerns, don't hesitate to let me know. We
are always here to be of assistance!
Sincerely yours,
Michael Cheng
Microsoft Online Partner Support
================================================== ====
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
================================================== ===
This posting is provided "AS IS" with no warranties, and confers no rights.
Everything is fine until today.
I have two instances(both msde databases, but I have enterprise manager and
analyser installed) on my computer one instance is mssql and the other is
mssql$netsdk (asp.net starter kit database)
somehow the connection to mssql$netsdk is failed which display in enterprise
manager.
So I removed the origianl server registration and start a new one, I type
"BETTYPC\NETSDK" as server and using windows authentication when doing the
registration, but the message display at the last step:
sql server registration failed because of connection failure displayed
below:sqldumpexceptionhandler :process 53 generated a fatal exception
c0000005 EXCEPTION_ACCESS_VIOLATION, sql server is terminating this process.
what's the problem?
Can you help and I am desperated
Betty
Hi Bettys,
Welcome to use MSDN Managed Newsgroup!
From your descriptions, I understood you are not able to connect the SQL
Server named instance NETSDK with error message EXCEPTION_ACCESS_VIOLATION.
If I have misunderstood your concern, please feel free to point it out.
AV errors could be caused by various reasons, please perform the steps
below and let me know the result
1. Check the log file of NETSDK instance, make sure whether the instance
was started correctly.
Defautly, the log will be located at C:\Program Files\Microsoft SQL
Server\MSSQL$NETSDK\log, you may paste them here or send to me directly
v-mingqc@.ONLINEmicrosoft.com if you have concerns on security. (Note that
REMOVE ONLINE in my email address before you click SEND)
2. Is it possible to connect the instance via OSQL and Query Analyzer?
3. Is it possible for you to connect via SQL Authentication?
Sincerely yours,
Michael Cheng
Microsoft Online Partner Support
================================================== ====
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
================================================== ===
This posting is provided "AS IS" with no warranties, and confers no rights.
|||Hi Michael,
Thank you, this is the first post on this forum. I didn't know what went
wrong. The only thing I can do is googling. Then it came to my mind that I
can stop the mssql@.netsdk sql server then and I restarted. It just started
and stopped again somehow. And then I have to restart the computer. After
that I saw both instances have sqlservr.exe process. This time I register the
server again and it looks fine. Connection is OK.
(I didn't try to use osql and did try to use sql authentication, but when I
supplied one userID and password to this server, this password is set up to a
database on this server, it should be OK right? it didn't work either.)
If you can tell what was going on, that will be great.
Here is the paste from errorLog:
2006-02-02 13:12:54.28 server Microsoft SQL Server 2000 - 8.00.760
(Intel X86)
Dec 17 2002 14:22:05
Copyright (c) 1988-2003 Microsoft Corporation
Desktop Engine on Windows NT 5.1 (Build 2600: Service Pack 1)
2006-02-02 13:12:54.28 server Copyright (C) 1988-2002 Microsoft
Corporation.
2006-02-02 13:12:54.28 server All rights reserved.
2006-02-02 13:12:54.28 server Server Process ID is 2988.
2006-02-02 13:12:54.28 server Logging SQL Server messages in file
'C:\Program Files\Microsoft SQL Server\MSSQL$NETSDK\LOG\ERRORLOG'.
2006-02-02 13:12:54.32 server SQL Server is starting at priority class
'normal'(2 CPUs detected).
2006-02-02 13:12:54.50 server SQL Server configured for thread mode
processing.
2006-02-02 13:12:54.50 server Using dynamic lock allocation. [500] Lock
Blocks, [1000] Lock Owner Blocks.
2006-02-02 13:12:54.52 spid4 Starting up database 'master'.
2006-02-02 13:12:54.57 server Using 'SSNETLIB.DLL' version '8.0.766'.
2006-02-02 13:12:54.57 spid5 Starting up database 'model'.
2006-02-02 13:12:54.57 spid4 Server name is 'BETTYPC\NETSDK'.
2006-02-02 13:12:54.57 spid4 Skipping startup of clean database id 4
2006-02-02 13:12:54.57 spid4 Skipping startup of clean database id 5
2006-02-02 13:12:54.57 spid4 Skipping startup of clean database id 6
2006-02-02 13:12:54.57 spid4 Skipping startup of clean database id 7
2006-02-02 13:12:54.57 spid4 Skipping startup of clean database id 8
2006-02-02 13:12:54.57 spid4 Skipping startup of clean database id 9
2006-02-02 13:12:54.57 spid4 Skipping startup of clean database id 10
2006-02-02 13:12:54.57 spid4 Skipping startup of clean database id 11
2006-02-02 13:12:54.57 spid4 Starting up database 'subway'.
2006-02-02 13:12:54.66 spid5 Clearing tempdb database.
2006-02-02 13:12:55.72 server SQL server listening on .
2006-02-02 13:12:55.72 server Error: 17826, Severity: 18, State: 1
2006-02-02 13:12:55.72 server Could not set up Net-Library 'SSNETLIB'..
2006-02-02 13:12:55.72 server Unable to load any netlibs.
2006-02-02 13:12:55.72 server SQL Server could not spawn FRunCM thread.
Here is the sqldump file
================================================== ===================
BugCheck Dump
================================================== ===================
This file is generated by Microsoft SQL Server 8.00.760
upon detection of fatal unexpected error. Please return this file,
the query or program that produced the bugcheck, the database and
the error log, and any other pertinent information with a Service Request.
Betty
"Michael Cheng [MSFT]" wrote:
> Hi Bettys,
> Welcome to use MSDN Managed Newsgroup!
> From your descriptions, I understood you are not able to connect the SQL
> Server named instance NETSDK with error message EXCEPTION_ACCESS_VIOLATION.
> If I have misunderstood your concern, please feel free to point it out.
> AV errors could be caused by various reasons, please perform the steps
> below and let me know the result
> 1. Check the log file of NETSDK instance, make sure whether the instance
> was started correctly.
> Defautly, the log will be located at C:\Program Files\Microsoft SQL
> Server\MSSQL$NETSDK\log, you may paste them here or send to me directly
>if you have concerns on security. (Note that
> REMOVE ONLINE in my email address before you click SEND)
> 2. Is it possible to connect the instance via OSQL and Query Analyzer?
> 3. Is it possible for you to connect via SQL Authentication?
>
> Sincerely yours,
> Michael Cheng
> Microsoft Online Partner Support
> ================================================== ====
> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
> ================================================== ===
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
>
|||Hi Betty,
It seems your SQL Server is not stable. From the startup log, I believe
something internal is wrong. We may noticed "netlibs" is not loaded and
Dump file were also generated.
Although you could register SQL Server now, I would recommend you backup
all the data in this instnace and perform a reinstallation of NETSDK
instance. You may follow the link below to perform a complete uninstall
How to manually remove SQL Server 2000 default, named, or virtual instance
http://support.microsoft.com/kb/290991
If you have any questions or concerns, don't hesitate to let me know. We
are always here to be of assistance!
Sincerely yours,
Michael Cheng
Microsoft Online Partner Support
================================================== ====
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
================================================== ===
This posting is provided "AS IS" with no warranties, and confers no rights.
Connection failure
When I try to connect one one of our SQL Server databases using SQL Server
2005 client tools I get the following error.
An error has occurred while establishing a connection to the server. When
connecting to SQL Server 2005, this failure may be caused by the fact that
inder the default setting SQL Server does not allow remote connections.
(Provider: TCP Provider, erro:0 - No connections could be made because the
target machine actively refused it.) (Microsoft SQL Server, Error: 10061).
I can connect to our other SQL Servers with no problem, and others users can
connect to the one I'm having problems with.
Any ideas?
Problem now solved.
Problem was caused by an alias setup for the previous version of sql server.
Deling the alias solved the problem.
Gary
"Gary Watson" wrote:
> When I try to connect one one of our SQL Server databases using SQL Server
> 2005 client tools I get the following error.
> An error has occurred while establishing a connection to the server. When
> connecting to SQL Server 2005, this failure may be caused by the fact that
> inder the default setting SQL Server does not allow remote connections.
> (Provider: TCP Provider, erro:0 - No connections could be made because the
> target machine actively refused it.) (Microsoft SQL Server, Error: 10061).
> I can connect to our other SQL Servers with no problem, and others users can
> connect to the one I'm having problems with.
> Any ideas?
2005 client tools I get the following error.
An error has occurred while establishing a connection to the server. When
connecting to SQL Server 2005, this failure may be caused by the fact that
inder the default setting SQL Server does not allow remote connections.
(Provider: TCP Provider, erro:0 - No connections could be made because the
target machine actively refused it.) (Microsoft SQL Server, Error: 10061).
I can connect to our other SQL Servers with no problem, and others users can
connect to the one I'm having problems with.
Any ideas?
Problem now solved.
Problem was caused by an alias setup for the previous version of sql server.
Deling the alias solved the problem.
Gary
"Gary Watson" wrote:
> When I try to connect one one of our SQL Server databases using SQL Server
> 2005 client tools I get the following error.
> An error has occurred while establishing a connection to the server. When
> connecting to SQL Server 2005, this failure may be caused by the fact that
> inder the default setting SQL Server does not allow remote connections.
> (Provider: TCP Provider, erro:0 - No connections could be made because the
> target machine actively refused it.) (Microsoft SQL Server, Error: 10061).
> I can connect to our other SQL Servers with no problem, and others users can
> connect to the one I'm having problems with.
> Any ideas?
Connection failure
When I try to connect one one of our SQL Server databases using SQL Server
2005 client tools I get the following error.
An error has occurred while establishing a connection to the server. When
connecting to SQL Server 2005, this failure may be caused by the fact that
inder the default setting SQL Server does not allow remote connections.
(Provider: TCP Provider, erro:0 - No connections could be made because the
target machine actively refused it.) (Microsoft SQL Server, Error: 10061).
I can connect to our other SQL Servers with no problem, and others users can
connect to the one I'm having problems with.
Any ideas?Problem now solved.
Problem was caused by an alias setup for the previous version of sql server.
Deling the alias solved the problem.
Gary
"Gary Watson" wrote:
> When I try to connect one one of our SQL Server databases using SQL Server
> 2005 client tools I get the following error.
> An error has occurred while establishing a connection to the server. When
> connecting to SQL Server 2005, this failure may be caused by the fact that
> inder the default setting SQL Server does not allow remote connections.
> (Provider: TCP Provider, erro:0 - No connections could be made because the
> target machine actively refused it.) (Microsoft SQL Server, Error: 10061).
> I can connect to our other SQL Servers with no problem, and others users c
an
> connect to the one I'm having problems with.
> Any ideas?
2005 client tools I get the following error.
An error has occurred while establishing a connection to the server. When
connecting to SQL Server 2005, this failure may be caused by the fact that
inder the default setting SQL Server does not allow remote connections.
(Provider: TCP Provider, erro:0 - No connections could be made because the
target machine actively refused it.) (Microsoft SQL Server, Error: 10061).
I can connect to our other SQL Servers with no problem, and others users can
connect to the one I'm having problems with.
Any ideas?Problem now solved.
Problem was caused by an alias setup for the previous version of sql server.
Deling the alias solved the problem.
Gary
"Gary Watson" wrote:
> When I try to connect one one of our SQL Server databases using SQL Server
> 2005 client tools I get the following error.
> An error has occurred while establishing a connection to the server. When
> connecting to SQL Server 2005, this failure may be caused by the fact that
> inder the default setting SQL Server does not allow remote connections.
> (Provider: TCP Provider, erro:0 - No connections could be made because the
> target machine actively refused it.) (Microsoft SQL Server, Error: 10061).
> I can connect to our other SQL Servers with no problem, and others users c
an
> connect to the one I'm having problems with.
> Any ideas?
Connection fails SQL 2000
One of our customers has SQl server 2000 installed
This has been working perfectly untill last Friday.
At this point various databases began to return errors
when querries were run on the data.
There appeasr to be no pattern to which databases still
work as I have two backup copies of the main databse they
use. The main one and one of the backups produce errors
yet the other backup, taken on the same day does not.
Looking at the error log (attached) there seems to be a
lot of "corrupt" entires.
Any suggestions
Date Source Message
---
--
---
--...
004 DC771 Module(sqlservr+000DC771) (ExecuteSql
(class CParamExchange *,class CXVariant *,
004 A9DE2 Module(sqlservr+000A9DE2)
(CXteHashMatch::ExecCompile(class CExecCompContext *)
004 A9E93 Module(sqlservr+000A9E93)
(CXteHashMatch::ExecCompile(class CExecCompContext *)
004 A70B6 Module(sqlservr+000A70B6)
(CXteHashMatch::IntermediateCompile(class IMemObj *,c
004 A8B35 Module(sqlservr+000A8B35)
(CXteHashMatch::CreateBailoutPlan(class CRemapContext
0041 F796 Module(sqlservr+0001F796)
(CSQLObject::FTransform(class CParamExchange *)+00000
0041 FDDD Module(sqlservr+0001FDDD)
(CSQLObject::FTransform2(class CSQLComment *,class CP
00415080 Module(sqlservr+00015080)
(CSQLSource::FTransform(class CParamExchange *)
+0000037C)
0041534 F Module(sqlservr+0001534F)
(CSQLSource::Execute(class CParamExchange *)+00000176
00415410 Module(sqlservr+00015410)
(CSQLSource::Execute(class CParamExchange *)
+00000343)
00415765 Module(sqlservr+00015765)
(CMsqlExecContext::Execute(class CCompPlan *,class
CParamExchange *)+000001C7)
004160 DB Module(sqlservr+000160DB)
(CMsqlExecContext::ExecuteStmts(class ExecutionContex
0041767 E Module(sqlservr+0001767E) (process_commands
(struct srv_proc *)+000001E7)
0043 B7EF Module(sqlservr+0003B7EF) (execute_rpc
(struct srv_proc *)+00000019)
00447078 Module(sqlservr+00047078)
(CCompPlan::FCompileStep(class CAlgStmt *,class
CStatement * *)+00000AE7)
004510 FE Module(sqlservr+000510FE)
(CProchdr::FCompile(class CCompPlan *,class CParamExc
0049 CB9F Module(sqlservr+0009CB9F)
(CStmtExec::XretExecute(class CMsqlExecContext *)cons
0049 CD0A Module(sqlservr+0009CD0A)
(CStmtExec::XretLocalExec(class CMsqlExecContext *,un
0049 C6F4 Module(sqlservr+0009C6F4)
(CSQLObject::FGetFromDisk(class CParamExchange *)+000
0049 DA48 Module(sqlservr+0009DA48)
(CStmtSelect::Init(class CAlgStmt *,class CCompPlan *
00563 F78 Module(sqlservr+00163F78)
(CStmtQuery::InitQuery(class CAlgStmt *,class CCompPl
00564019 Module(sqlservr+00164019)
(BuildQueryFromTree(class TREE *,class IMemObj
*,class IMemObj *,class IQueryOb
005642 CD Module(sqlservr+001642CD)
(CCvtTree::PqryFromTree(class TREE *,class IMemObj *,
0056701 F Module(sqlservr+0016701F)
(CBndOutputs::RemapValrefs(class CRemapContext *,int)
00567536 Module(sqlservr+00167536)
(CXte::ExecCompile(class CExecCompContext *)
+000000B7)
00567536 Module(sqlservr+00167536)
(CXte::ExecCompile(class CExecCompContext *)
+000000B7)
005688 A4 Module(sqlservr+001688A4) (CQuery::Prepare
(void)+00000116)
0061 DDB6 Module(sqlservr+0021DDB6)
(CSpecProc::Execute(class CParamExchange *)+00000092)
0061 DA3E Module(sqlservr+0021DA3E)
(CSpecProc::ExecuteSpecial(class CParamExchange *,uns
0063 C71D Module(sqlservr+0023C71D) (execrpc(struct
srv_proc *)+000004A8)
00703 A1C Module(sqlservr+00303A1C)
(CXteHashMatch::CreateInputScan(class IMemObj *,class
2003-11-05 12:36:10.29 server Microsoft SQL Server
2000 - 8.00.194 (Intel X86) ...
2003-11-05 12:36:10.54 server Logging SQL Server
messages in file 'd:\Program Files\Microsoft SQL
Server\MSSQ
2003-11-05 12:36:10.54 server Server Process ID is 1700.
2003-11-05 12:36:10.54 server All rights reserved.
2003-11-05 12:36:10.54 server Copyright (C) 1988-2000
Microsoft Corporation.
2003-11-05 12:36:10.99 server SQL Server is starting at
priority class 'normal'(4 CPUs detected).
2003-11-05 12:36:13.00 server SQL Server configured for
thread mode processing.
2003-11-05 12:36:13.23 server Using dynamic lock
allocation. [2500] Lock Blocks, [5000] Lock Owner Blocks.
2003-11-05 12:36:13.62 server Attempting to initialize
Distributed Transaction Coordinator.
2003-11-05 12:36:19.92 spid2 Starting up
database 'master'.
2003-11-05 12:36:27.70 spid5 Starting up
database 'model'.
2003-11-05 12:36:27.70 server Using 'SSNETLIB.DLL'
version '8.0.194'.
2003-11-05 12:36:27.73 spid2 Server name is 'WRLW2S002'.
2003-11-05 12:36:27.79 spid12 Starting up
database 'powerway'.
2003-11-05 12:36:27.79 spid11 Starting up
database 'dbWheelset_Live'.
2003-11-05 12:36:27.79 spid10 Starting up
database 'Northwind'.
2003-11-05 12:36:27.79 spid9 Starting up
database 'pubs'.
2003-11-05 12:36:27.79 spid8 Starting up
database 'msdb'.
2003-11-05 12:36:27.81 spid14 Starting up
database 'dbWheelSets_LIVE'.
2003-11-05 12:36:27.81 spid13 Starting up
database 'dbWheelSets_TEST'.
2003-11-05 12:36:27.89 spid16 Starting up
database 'dbWheelsets_ARCH_TEST'.
2003-11-05 12:36:27.89 spid15 Starting up
database 'dbWheelsets_BACKUP'.
2003-11-05 12:36:27.98 spid17 Starting up
database 'dbWheelsets_DATA_TEST'.
2003-11-05 12:36:28.43 spid5 Clearing tempdb database.
2003-11-05 12:36:28.51 spid11 Analysis of
database 'dbWheelset_Live' (7) is 100% complete
(approximately 0 mo
2003-11-05 12:36:28.65 spid12 Analysis of
database 'powerway' (8) is 100% complete (approximately 0
more seco
2003-11-05 12:36:28.87 server SQL Server is ready for
client connections
2003-11-05 12:36:28.87 server SQL server listening on
172.20.120.23:1433, 127.0.0.1:1433.
2003-11-05 12:36:28.87 server SQL server listening on
TCP, Shared Memory, Named Pipes.
2003-11-05 12:36:29.76 spid13 Analysis of
database 'dbWheelSets_TEST' (9) is 100% complete
(approximately 0 m
2003-11-05 12:36:38.67 spid5 Starting up
database 'tempdb'.
2003-11-05 12:36:41.85 spid2 Recovery complete.
2003-11-05 12:36:49.51 spid51 Using 'xpsqlbot.dll'
version '2000.80.194' to execute extended stored procedure
2003-11-05 12:36:51.96 spid51 Using 'xpstar.dll'
version '2000.80.194' to execute extended stored
procedure '
2003-11-05 13:15:27.45 spid55 Using 'sqlimage.dll'
version '4.0.5'...
2003-11-05 13:15:27.46 spid55 SqlDumpExceptionHandler:
Process 55 generated fatal exception c0000005 EXCEPTIO
2003-11-05 13:15:27.46 spid55 Error: 0, Severity: 19,
State: 0
410735 D0 Module(UMS+000035D0) (ProcessWorkRequests
(class UmsWorkQueue *)+00000264)
4107382 C Module(UMS+0000382C) (ThreadStartRoutine
(void *)+000000BC)
7 C57B382 Module(KERNEL32+0000B382)
(lstrcmpiW+000000B7)
78008454 Module(MSVCRT+00008454)
(_endthread+000000C1)Have you tried running DBCC CHECKDB
--
HTH
Ryan Waight, MCDBA, MCSE
"john kinghorn" <anonymous@.discussions.microsoft.com> wrote in message
news:076a01c3a787$7e28ea20$a401280a@.phx.gbl...
> One of our customers has SQl server 2000 installed
> This has been working perfectly untill last Friday.
> At this point various databases began to return errors
> when querries were run on the data.
> There appeasr to be no pattern to which databases still
> work as I have two backup copies of the main databse they
> use. The main one and one of the backups produce errors
> yet the other backup, taken on the same day does not.
> Looking at the error log (attached) there seems to be a
> lot of "corrupt" entires.
> Any suggestions
>
> Date Source Message
> ---
> --
> ---
> --...
> 004 DC771 Module(sqlservr+000DC771) (ExecuteSql
> (class CParamExchange *,class CXVariant *,
> 004 A9DE2 Module(sqlservr+000A9DE2)
> (CXteHashMatch::ExecCompile(class CExecCompContext *)
> 004 A9E93 Module(sqlservr+000A9E93)
> (CXteHashMatch::ExecCompile(class CExecCompContext *)
> 004 A70B6 Module(sqlservr+000A70B6)
> (CXteHashMatch::IntermediateCompile(class IMemObj *,c
> 004 A8B35 Module(sqlservr+000A8B35)
> (CXteHashMatch::CreateBailoutPlan(class CRemapContext
> 0041 F796 Module(sqlservr+0001F796)
> (CSQLObject::FTransform(class CParamExchange *)+00000
> 0041 FDDD Module(sqlservr+0001FDDD)
> (CSQLObject::FTransform2(class CSQLComment *,class CP
> 00415080 Module(sqlservr+00015080)
> (CSQLSource::FTransform(class CParamExchange *)
> +0000037C)
> 0041534 F Module(sqlservr+0001534F)
> (CSQLSource::Execute(class CParamExchange *)+00000176
> 00415410 Module(sqlservr+00015410)
> (CSQLSource::Execute(class CParamExchange *)
> +00000343)
> 00415765 Module(sqlservr+00015765)
> (CMsqlExecContext::Execute(class CCompPlan *,class
> CParamExchange *)+000001C7)
> 004160 DB Module(sqlservr+000160DB)
> (CMsqlExecContext::ExecuteStmts(class ExecutionContex
> 0041767 E Module(sqlservr+0001767E) (process_commands
> (struct srv_proc *)+000001E7)
> 0043 B7EF Module(sqlservr+0003B7EF) (execute_rpc
> (struct srv_proc *)+00000019)
> 00447078 Module(sqlservr+00047078)
> (CCompPlan::FCompileStep(class CAlgStmt *,class
> CStatement * *)+00000AE7)
> 004510 FE Module(sqlservr+000510FE)
> (CProchdr::FCompile(class CCompPlan *,class CParamExc
> 0049 CB9F Module(sqlservr+0009CB9F)
> (CStmtExec::XretExecute(class CMsqlExecContext *)cons
> 0049 CD0A Module(sqlservr+0009CD0A)
> (CStmtExec::XretLocalExec(class CMsqlExecContext *,un
> 0049 C6F4 Module(sqlservr+0009C6F4)
> (CSQLObject::FGetFromDisk(class CParamExchange *)+000
> 0049 DA48 Module(sqlservr+0009DA48)
> (CStmtSelect::Init(class CAlgStmt *,class CCompPlan *
> 00563 F78 Module(sqlservr+00163F78)
> (CStmtQuery::InitQuery(class CAlgStmt *,class CCompPl
> 00564019 Module(sqlservr+00164019)
> (BuildQueryFromTree(class TREE *,class IMemObj
> *,class IMemObj *,class IQueryOb
> 005642 CD Module(sqlservr+001642CD)
> (CCvtTree::PqryFromTree(class TREE *,class IMemObj *,
> 0056701 F Module(sqlservr+0016701F)
> (CBndOutputs::RemapValrefs(class CRemapContext *,int)
> 00567536 Module(sqlservr+00167536)
> (CXte::ExecCompile(class CExecCompContext *)
> +000000B7)
> 00567536 Module(sqlservr+00167536)
> (CXte::ExecCompile(class CExecCompContext *)
> +000000B7)
> 005688 A4 Module(sqlservr+001688A4) (CQuery::Prepare
> (void)+00000116)
> 0061 DDB6 Module(sqlservr+0021DDB6)
> (CSpecProc::Execute(class CParamExchange *)+00000092)
> 0061 DA3E Module(sqlservr+0021DA3E)
> (CSpecProc::ExecuteSpecial(class CParamExchange *,uns
> 0063 C71D Module(sqlservr+0023C71D) (execrpc(struct
> srv_proc *)+000004A8)
> 00703 A1C Module(sqlservr+00303A1C)
> (CXteHashMatch::CreateInputScan(class IMemObj *,class
> 2003-11-05 12:36:10.29 server Microsoft SQL Server
> 2000 - 8.00.194 (Intel X86) ...
> 2003-11-05 12:36:10.54 server Logging SQL Server
> messages in file 'd:\Program Files\Microsoft SQL
> Server\MSSQ
> 2003-11-05 12:36:10.54 server Server Process ID is 1700.
> 2003-11-05 12:36:10.54 server All rights reserved.
> 2003-11-05 12:36:10.54 server Copyright (C) 1988-2000
> Microsoft Corporation.
> 2003-11-05 12:36:10.99 server SQL Server is starting at
> priority class 'normal'(4 CPUs detected).
> 2003-11-05 12:36:13.00 server SQL Server configured for
> thread mode processing.
> 2003-11-05 12:36:13.23 server Using dynamic lock
> allocation. [2500] Lock Blocks, [5000] Lock Owner Blocks.
> 2003-11-05 12:36:13.62 server Attempting to initialize
> Distributed Transaction Coordinator.
> 2003-11-05 12:36:19.92 spid2 Starting up
> database 'master'.
> 2003-11-05 12:36:27.70 spid5 Starting up
> database 'model'.
> 2003-11-05 12:36:27.70 server Using 'SSNETLIB.DLL'
> version '8.0.194'.
> 2003-11-05 12:36:27.73 spid2 Server name is 'WRLW2S002'.
> 2003-11-05 12:36:27.79 spid12 Starting up
> database 'powerway'.
> 2003-11-05 12:36:27.79 spid11 Starting up
> database 'dbWheelset_Live'.
> 2003-11-05 12:36:27.79 spid10 Starting up
> database 'Northwind'.
> 2003-11-05 12:36:27.79 spid9 Starting up
> database 'pubs'.
> 2003-11-05 12:36:27.79 spid8 Starting up
> database 'msdb'.
> 2003-11-05 12:36:27.81 spid14 Starting up
> database 'dbWheelSets_LIVE'.
> 2003-11-05 12:36:27.81 spid13 Starting up
> database 'dbWheelSets_TEST'.
> 2003-11-05 12:36:27.89 spid16 Starting up
> database 'dbWheelsets_ARCH_TEST'.
> 2003-11-05 12:36:27.89 spid15 Starting up
> database 'dbWheelsets_BACKUP'.
> 2003-11-05 12:36:27.98 spid17 Starting up
> database 'dbWheelsets_DATA_TEST'.
> 2003-11-05 12:36:28.43 spid5 Clearing tempdb database.
> 2003-11-05 12:36:28.51 spid11 Analysis of
> database 'dbWheelset_Live' (7) is 100% complete
> (approximately 0 mo
> 2003-11-05 12:36:28.65 spid12 Analysis of
> database 'powerway' (8) is 100% complete (approximately 0
> more seco
> 2003-11-05 12:36:28.87 server SQL Server is ready for
> client connections
> 2003-11-05 12:36:28.87 server SQL server listening on
> 172.20.120.23:1433, 127.0.0.1:1433.
> 2003-11-05 12:36:28.87 server SQL server listening on
> TCP, Shared Memory, Named Pipes.
> 2003-11-05 12:36:29.76 spid13 Analysis of
> database 'dbWheelSets_TEST' (9) is 100% complete
> (approximately 0 m
> 2003-11-05 12:36:38.67 spid5 Starting up
> database 'tempdb'.
> 2003-11-05 12:36:41.85 spid2 Recovery complete.
> 2003-11-05 12:36:49.51 spid51 Using 'xpsqlbot.dll'
> version '2000.80.194' to execute extended stored procedure
> 2003-11-05 12:36:51.96 spid51 Using 'xpstar.dll'
> version '2000.80.194' to execute extended stored
> procedure '
> 2003-11-05 13:15:27.45 spid55 Using 'sqlimage.dll'
> version '4.0.5'...
> 2003-11-05 13:15:27.46 spid55 SqlDumpExceptionHandler:
> Process 55 generated fatal exception c0000005 EXCEPTIO
> 2003-11-05 13:15:27.46 spid55 Error: 0, Severity: 19,
> State: 0
> 410735 D0 Module(UMS+000035D0) (ProcessWorkRequests
> (class UmsWorkQueue *)+00000264)
> 4107382 C Module(UMS+0000382C) (ThreadStartRoutine
> (void *)+000000BC)
> 7 C57B382 Module(KERNEL32+0000B382)
> (lstrcmpiW+000000B7)
> 78008454 Module(MSVCRT+00008454)
> (_endthread+000000C1)
>
This has been working perfectly untill last Friday.
At this point various databases began to return errors
when querries were run on the data.
There appeasr to be no pattern to which databases still
work as I have two backup copies of the main databse they
use. The main one and one of the backups produce errors
yet the other backup, taken on the same day does not.
Looking at the error log (attached) there seems to be a
lot of "corrupt" entires.
Any suggestions
Date Source Message
---
--
---
--...
004 DC771 Module(sqlservr+000DC771) (ExecuteSql
(class CParamExchange *,class CXVariant *,
004 A9DE2 Module(sqlservr+000A9DE2)
(CXteHashMatch::ExecCompile(class CExecCompContext *)
004 A9E93 Module(sqlservr+000A9E93)
(CXteHashMatch::ExecCompile(class CExecCompContext *)
004 A70B6 Module(sqlservr+000A70B6)
(CXteHashMatch::IntermediateCompile(class IMemObj *,c
004 A8B35 Module(sqlservr+000A8B35)
(CXteHashMatch::CreateBailoutPlan(class CRemapContext
0041 F796 Module(sqlservr+0001F796)
(CSQLObject::FTransform(class CParamExchange *)+00000
0041 FDDD Module(sqlservr+0001FDDD)
(CSQLObject::FTransform2(class CSQLComment *,class CP
00415080 Module(sqlservr+00015080)
(CSQLSource::FTransform(class CParamExchange *)
+0000037C)
0041534 F Module(sqlservr+0001534F)
(CSQLSource::Execute(class CParamExchange *)+00000176
00415410 Module(sqlservr+00015410)
(CSQLSource::Execute(class CParamExchange *)
+00000343)
00415765 Module(sqlservr+00015765)
(CMsqlExecContext::Execute(class CCompPlan *,class
CParamExchange *)+000001C7)
004160 DB Module(sqlservr+000160DB)
(CMsqlExecContext::ExecuteStmts(class ExecutionContex
0041767 E Module(sqlservr+0001767E) (process_commands
(struct srv_proc *)+000001E7)
0043 B7EF Module(sqlservr+0003B7EF) (execute_rpc
(struct srv_proc *)+00000019)
00447078 Module(sqlservr+00047078)
(CCompPlan::FCompileStep(class CAlgStmt *,class
CStatement * *)+00000AE7)
004510 FE Module(sqlservr+000510FE)
(CProchdr::FCompile(class CCompPlan *,class CParamExc
0049 CB9F Module(sqlservr+0009CB9F)
(CStmtExec::XretExecute(class CMsqlExecContext *)cons
0049 CD0A Module(sqlservr+0009CD0A)
(CStmtExec::XretLocalExec(class CMsqlExecContext *,un
0049 C6F4 Module(sqlservr+0009C6F4)
(CSQLObject::FGetFromDisk(class CParamExchange *)+000
0049 DA48 Module(sqlservr+0009DA48)
(CStmtSelect::Init(class CAlgStmt *,class CCompPlan *
00563 F78 Module(sqlservr+00163F78)
(CStmtQuery::InitQuery(class CAlgStmt *,class CCompPl
00564019 Module(sqlservr+00164019)
(BuildQueryFromTree(class TREE *,class IMemObj
*,class IMemObj *,class IQueryOb
005642 CD Module(sqlservr+001642CD)
(CCvtTree::PqryFromTree(class TREE *,class IMemObj *,
0056701 F Module(sqlservr+0016701F)
(CBndOutputs::RemapValrefs(class CRemapContext *,int)
00567536 Module(sqlservr+00167536)
(CXte::ExecCompile(class CExecCompContext *)
+000000B7)
00567536 Module(sqlservr+00167536)
(CXte::ExecCompile(class CExecCompContext *)
+000000B7)
005688 A4 Module(sqlservr+001688A4) (CQuery::Prepare
(void)+00000116)
0061 DDB6 Module(sqlservr+0021DDB6)
(CSpecProc::Execute(class CParamExchange *)+00000092)
0061 DA3E Module(sqlservr+0021DA3E)
(CSpecProc::ExecuteSpecial(class CParamExchange *,uns
0063 C71D Module(sqlservr+0023C71D) (execrpc(struct
srv_proc *)+000004A8)
00703 A1C Module(sqlservr+00303A1C)
(CXteHashMatch::CreateInputScan(class IMemObj *,class
2003-11-05 12:36:10.29 server Microsoft SQL Server
2000 - 8.00.194 (Intel X86) ...
2003-11-05 12:36:10.54 server Logging SQL Server
messages in file 'd:\Program Files\Microsoft SQL
Server\MSSQ
2003-11-05 12:36:10.54 server Server Process ID is 1700.
2003-11-05 12:36:10.54 server All rights reserved.
2003-11-05 12:36:10.54 server Copyright (C) 1988-2000
Microsoft Corporation.
2003-11-05 12:36:10.99 server SQL Server is starting at
priority class 'normal'(4 CPUs detected).
2003-11-05 12:36:13.00 server SQL Server configured for
thread mode processing.
2003-11-05 12:36:13.23 server Using dynamic lock
allocation. [2500] Lock Blocks, [5000] Lock Owner Blocks.
2003-11-05 12:36:13.62 server Attempting to initialize
Distributed Transaction Coordinator.
2003-11-05 12:36:19.92 spid2 Starting up
database 'master'.
2003-11-05 12:36:27.70 spid5 Starting up
database 'model'.
2003-11-05 12:36:27.70 server Using 'SSNETLIB.DLL'
version '8.0.194'.
2003-11-05 12:36:27.73 spid2 Server name is 'WRLW2S002'.
2003-11-05 12:36:27.79 spid12 Starting up
database 'powerway'.
2003-11-05 12:36:27.79 spid11 Starting up
database 'dbWheelset_Live'.
2003-11-05 12:36:27.79 spid10 Starting up
database 'Northwind'.
2003-11-05 12:36:27.79 spid9 Starting up
database 'pubs'.
2003-11-05 12:36:27.79 spid8 Starting up
database 'msdb'.
2003-11-05 12:36:27.81 spid14 Starting up
database 'dbWheelSets_LIVE'.
2003-11-05 12:36:27.81 spid13 Starting up
database 'dbWheelSets_TEST'.
2003-11-05 12:36:27.89 spid16 Starting up
database 'dbWheelsets_ARCH_TEST'.
2003-11-05 12:36:27.89 spid15 Starting up
database 'dbWheelsets_BACKUP'.
2003-11-05 12:36:27.98 spid17 Starting up
database 'dbWheelsets_DATA_TEST'.
2003-11-05 12:36:28.43 spid5 Clearing tempdb database.
2003-11-05 12:36:28.51 spid11 Analysis of
database 'dbWheelset_Live' (7) is 100% complete
(approximately 0 mo
2003-11-05 12:36:28.65 spid12 Analysis of
database 'powerway' (8) is 100% complete (approximately 0
more seco
2003-11-05 12:36:28.87 server SQL Server is ready for
client connections
2003-11-05 12:36:28.87 server SQL server listening on
172.20.120.23:1433, 127.0.0.1:1433.
2003-11-05 12:36:28.87 server SQL server listening on
TCP, Shared Memory, Named Pipes.
2003-11-05 12:36:29.76 spid13 Analysis of
database 'dbWheelSets_TEST' (9) is 100% complete
(approximately 0 m
2003-11-05 12:36:38.67 spid5 Starting up
database 'tempdb'.
2003-11-05 12:36:41.85 spid2 Recovery complete.
2003-11-05 12:36:49.51 spid51 Using 'xpsqlbot.dll'
version '2000.80.194' to execute extended stored procedure
2003-11-05 12:36:51.96 spid51 Using 'xpstar.dll'
version '2000.80.194' to execute extended stored
procedure '
2003-11-05 13:15:27.45 spid55 Using 'sqlimage.dll'
version '4.0.5'...
2003-11-05 13:15:27.46 spid55 SqlDumpExceptionHandler:
Process 55 generated fatal exception c0000005 EXCEPTIO
2003-11-05 13:15:27.46 spid55 Error: 0, Severity: 19,
State: 0
410735 D0 Module(UMS+000035D0) (ProcessWorkRequests
(class UmsWorkQueue *)+00000264)
4107382 C Module(UMS+0000382C) (ThreadStartRoutine
(void *)+000000BC)
7 C57B382 Module(KERNEL32+0000B382)
(lstrcmpiW+000000B7)
78008454 Module(MSVCRT+00008454)
(_endthread+000000C1)Have you tried running DBCC CHECKDB
--
HTH
Ryan Waight, MCDBA, MCSE
"john kinghorn" <anonymous@.discussions.microsoft.com> wrote in message
news:076a01c3a787$7e28ea20$a401280a@.phx.gbl...
> One of our customers has SQl server 2000 installed
> This has been working perfectly untill last Friday.
> At this point various databases began to return errors
> when querries were run on the data.
> There appeasr to be no pattern to which databases still
> work as I have two backup copies of the main databse they
> use. The main one and one of the backups produce errors
> yet the other backup, taken on the same day does not.
> Looking at the error log (attached) there seems to be a
> lot of "corrupt" entires.
> Any suggestions
>
> Date Source Message
> ---
> --
> ---
> --...
> 004 DC771 Module(sqlservr+000DC771) (ExecuteSql
> (class CParamExchange *,class CXVariant *,
> 004 A9DE2 Module(sqlservr+000A9DE2)
> (CXteHashMatch::ExecCompile(class CExecCompContext *)
> 004 A9E93 Module(sqlservr+000A9E93)
> (CXteHashMatch::ExecCompile(class CExecCompContext *)
> 004 A70B6 Module(sqlservr+000A70B6)
> (CXteHashMatch::IntermediateCompile(class IMemObj *,c
> 004 A8B35 Module(sqlservr+000A8B35)
> (CXteHashMatch::CreateBailoutPlan(class CRemapContext
> 0041 F796 Module(sqlservr+0001F796)
> (CSQLObject::FTransform(class CParamExchange *)+00000
> 0041 FDDD Module(sqlservr+0001FDDD)
> (CSQLObject::FTransform2(class CSQLComment *,class CP
> 00415080 Module(sqlservr+00015080)
> (CSQLSource::FTransform(class CParamExchange *)
> +0000037C)
> 0041534 F Module(sqlservr+0001534F)
> (CSQLSource::Execute(class CParamExchange *)+00000176
> 00415410 Module(sqlservr+00015410)
> (CSQLSource::Execute(class CParamExchange *)
> +00000343)
> 00415765 Module(sqlservr+00015765)
> (CMsqlExecContext::Execute(class CCompPlan *,class
> CParamExchange *)+000001C7)
> 004160 DB Module(sqlservr+000160DB)
> (CMsqlExecContext::ExecuteStmts(class ExecutionContex
> 0041767 E Module(sqlservr+0001767E) (process_commands
> (struct srv_proc *)+000001E7)
> 0043 B7EF Module(sqlservr+0003B7EF) (execute_rpc
> (struct srv_proc *)+00000019)
> 00447078 Module(sqlservr+00047078)
> (CCompPlan::FCompileStep(class CAlgStmt *,class
> CStatement * *)+00000AE7)
> 004510 FE Module(sqlservr+000510FE)
> (CProchdr::FCompile(class CCompPlan *,class CParamExc
> 0049 CB9F Module(sqlservr+0009CB9F)
> (CStmtExec::XretExecute(class CMsqlExecContext *)cons
> 0049 CD0A Module(sqlservr+0009CD0A)
> (CStmtExec::XretLocalExec(class CMsqlExecContext *,un
> 0049 C6F4 Module(sqlservr+0009C6F4)
> (CSQLObject::FGetFromDisk(class CParamExchange *)+000
> 0049 DA48 Module(sqlservr+0009DA48)
> (CStmtSelect::Init(class CAlgStmt *,class CCompPlan *
> 00563 F78 Module(sqlservr+00163F78)
> (CStmtQuery::InitQuery(class CAlgStmt *,class CCompPl
> 00564019 Module(sqlservr+00164019)
> (BuildQueryFromTree(class TREE *,class IMemObj
> *,class IMemObj *,class IQueryOb
> 005642 CD Module(sqlservr+001642CD)
> (CCvtTree::PqryFromTree(class TREE *,class IMemObj *,
> 0056701 F Module(sqlservr+0016701F)
> (CBndOutputs::RemapValrefs(class CRemapContext *,int)
> 00567536 Module(sqlservr+00167536)
> (CXte::ExecCompile(class CExecCompContext *)
> +000000B7)
> 00567536 Module(sqlservr+00167536)
> (CXte::ExecCompile(class CExecCompContext *)
> +000000B7)
> 005688 A4 Module(sqlservr+001688A4) (CQuery::Prepare
> (void)+00000116)
> 0061 DDB6 Module(sqlservr+0021DDB6)
> (CSpecProc::Execute(class CParamExchange *)+00000092)
> 0061 DA3E Module(sqlservr+0021DA3E)
> (CSpecProc::ExecuteSpecial(class CParamExchange *,uns
> 0063 C71D Module(sqlservr+0023C71D) (execrpc(struct
> srv_proc *)+000004A8)
> 00703 A1C Module(sqlservr+00303A1C)
> (CXteHashMatch::CreateInputScan(class IMemObj *,class
> 2003-11-05 12:36:10.29 server Microsoft SQL Server
> 2000 - 8.00.194 (Intel X86) ...
> 2003-11-05 12:36:10.54 server Logging SQL Server
> messages in file 'd:\Program Files\Microsoft SQL
> Server\MSSQ
> 2003-11-05 12:36:10.54 server Server Process ID is 1700.
> 2003-11-05 12:36:10.54 server All rights reserved.
> 2003-11-05 12:36:10.54 server Copyright (C) 1988-2000
> Microsoft Corporation.
> 2003-11-05 12:36:10.99 server SQL Server is starting at
> priority class 'normal'(4 CPUs detected).
> 2003-11-05 12:36:13.00 server SQL Server configured for
> thread mode processing.
> 2003-11-05 12:36:13.23 server Using dynamic lock
> allocation. [2500] Lock Blocks, [5000] Lock Owner Blocks.
> 2003-11-05 12:36:13.62 server Attempting to initialize
> Distributed Transaction Coordinator.
> 2003-11-05 12:36:19.92 spid2 Starting up
> database 'master'.
> 2003-11-05 12:36:27.70 spid5 Starting up
> database 'model'.
> 2003-11-05 12:36:27.70 server Using 'SSNETLIB.DLL'
> version '8.0.194'.
> 2003-11-05 12:36:27.73 spid2 Server name is 'WRLW2S002'.
> 2003-11-05 12:36:27.79 spid12 Starting up
> database 'powerway'.
> 2003-11-05 12:36:27.79 spid11 Starting up
> database 'dbWheelset_Live'.
> 2003-11-05 12:36:27.79 spid10 Starting up
> database 'Northwind'.
> 2003-11-05 12:36:27.79 spid9 Starting up
> database 'pubs'.
> 2003-11-05 12:36:27.79 spid8 Starting up
> database 'msdb'.
> 2003-11-05 12:36:27.81 spid14 Starting up
> database 'dbWheelSets_LIVE'.
> 2003-11-05 12:36:27.81 spid13 Starting up
> database 'dbWheelSets_TEST'.
> 2003-11-05 12:36:27.89 spid16 Starting up
> database 'dbWheelsets_ARCH_TEST'.
> 2003-11-05 12:36:27.89 spid15 Starting up
> database 'dbWheelsets_BACKUP'.
> 2003-11-05 12:36:27.98 spid17 Starting up
> database 'dbWheelsets_DATA_TEST'.
> 2003-11-05 12:36:28.43 spid5 Clearing tempdb database.
> 2003-11-05 12:36:28.51 spid11 Analysis of
> database 'dbWheelset_Live' (7) is 100% complete
> (approximately 0 mo
> 2003-11-05 12:36:28.65 spid12 Analysis of
> database 'powerway' (8) is 100% complete (approximately 0
> more seco
> 2003-11-05 12:36:28.87 server SQL Server is ready for
> client connections
> 2003-11-05 12:36:28.87 server SQL server listening on
> 172.20.120.23:1433, 127.0.0.1:1433.
> 2003-11-05 12:36:28.87 server SQL server listening on
> TCP, Shared Memory, Named Pipes.
> 2003-11-05 12:36:29.76 spid13 Analysis of
> database 'dbWheelSets_TEST' (9) is 100% complete
> (approximately 0 m
> 2003-11-05 12:36:38.67 spid5 Starting up
> database 'tempdb'.
> 2003-11-05 12:36:41.85 spid2 Recovery complete.
> 2003-11-05 12:36:49.51 spid51 Using 'xpsqlbot.dll'
> version '2000.80.194' to execute extended stored procedure
> 2003-11-05 12:36:51.96 spid51 Using 'xpstar.dll'
> version '2000.80.194' to execute extended stored
> procedure '
> 2003-11-05 13:15:27.45 spid55 Using 'sqlimage.dll'
> version '4.0.5'...
> 2003-11-05 13:15:27.46 spid55 SqlDumpExceptionHandler:
> Process 55 generated fatal exception c0000005 EXCEPTIO
> 2003-11-05 13:15:27.46 spid55 Error: 0, Severity: 19,
> State: 0
> 410735 D0 Module(UMS+000035D0) (ProcessWorkRequests
> (class UmsWorkQueue *)+00000264)
> 4107382 C Module(UMS+0000382C) (ThreadStartRoutine
> (void *)+000000BC)
> 7 C57B382 Module(KERNEL32+0000B382)
> (lstrcmpiW+000000B7)
> 78008454 Module(MSVCRT+00008454)
> (_endthread+000000C1)
>
Connection fails and currupt log
One of our customers has SQL server 2000 installed
This has been working perfectly for over a year
Now various databases have started to return errors when queries are
run on the data from VB or Query Analyser.
A typical error is:
[Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionCheckForData
(CheckForData()).
Server: Msg 11, Level 16, State 1, Line 0
General Network Error. Check your network documentation
Connection broken
Not all the database produce errors but there appears to be no pattern
to which databases still work.
I have two backup copies of the main database they use. The main
database its self and one of the backups produce errors yet the other
backup, taken on the same day does not.
Looking at the error log (attached) there seems to be a lot of
"corrupt" entires.
Any suggestions* If you see corruption, then --
1. Check system and app event logs for details on any hardware corruption.
2. contact your hardware vendors to run some tests, diagnostics, etc and
also check for firmware upgrades.
3. Only then, RESTORE from your last healthy SQL Backup.
4. If you dont have a backup, then you could try to "Repair" the database
using "dbcc checkdb".
Thanks,
Vikram
Vikram Jayaram
Microsoft, SQL Server
This posting is provided "AS IS" with no warranties, and confers no rights.
Subscribe to MSDN & use http://msdn.microsoft.com/newsgroups.
This has been working perfectly for over a year
Now various databases have started to return errors when queries are
run on the data from VB or Query Analyser.
A typical error is:
[Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionCheckForData
(CheckForData()).
Server: Msg 11, Level 16, State 1, Line 0
General Network Error. Check your network documentation
Connection broken
Not all the database produce errors but there appears to be no pattern
to which databases still work.
I have two backup copies of the main database they use. The main
database its self and one of the backups produce errors yet the other
backup, taken on the same day does not.
Looking at the error log (attached) there seems to be a lot of
"corrupt" entires.
Any suggestions* If you see corruption, then --
1. Check system and app event logs for details on any hardware corruption.
2. contact your hardware vendors to run some tests, diagnostics, etc and
also check for firmware upgrades.
3. Only then, RESTORE from your last healthy SQL Backup.
4. If you dont have a backup, then you could try to "Repair" the database
using "dbcc checkdb".
Thanks,
Vikram
Vikram Jayaram
Microsoft, SQL Server
This posting is provided "AS IS" with no warranties, and confers no rights.
Subscribe to MSDN & use http://msdn.microsoft.com/newsgroups.
connection failed
Hi,
I have a program using ms sql. It worked fine for some time, but
now each time the program access the databases it outputs "Connection Failed
SQLState 28000, SQL Server Error 18456, Login failed for user 'sa'".
After pressing OK it gives an option to input a new password manually, and after
entering it - it works. But only for the current transaction. Next time it'll prompt again.
I've tried to change the password, I've chaned it in the system ODBC drivers, tried
different usernames, but the same error returns.
What could be the problem ?
Thanks.
It depends on the said program. How the program is configured or coded to
connect to the SQL Server database? It sounds the program is configured or
hard-coded (too bad!!!) with "sa/sapassword" to connect. The reason of error
is bacause "sa" account's password has been changed, which is good (maybe
the DB admin knew some apps use "sa" to access the SQL Server, which is bad
practice, and he changed it?).
You must find a way to reconfigure it to use new password. If the password
is hard coded, then you may out luck to change it easily.
"Marius Kaizerman" <marius@.kaizerman.org> wrote in message
news:e9e%23NcDMIHA.4712@.TK2MSFTNGP04.phx.gbl...
Hi,
I have a program using ms sql. It worked fine for some time, but
now each time the program access the databases it outputs "Connection Failed
SQLState 28000, SQL Server Error 18456, Login failed for user 'sa'".
After pressing OK it gives an option to input a new password manually, and
after
entering it - it works. But only for the current transaction. Next time
it'll prompt again.
I've tried to change the password, I've chaned it in the system ODBC
drivers, tried
different usernames, but the same error returns.
What could be the problem ?
Thanks.
|||Norman,
You were absolutely right.
Thanks alot!
"Norman Yuan" <NoAddress@.NoEmail.fake> wrote in message
news:OonyLvDMIHA.1164@.TK2MSFTNGP02.phx.gbl...
> It depends on the said program. How the program is configured or coded to
> connect to the SQL Server database? It sounds the program is configured or
> hard-coded (too bad!!!) with "sa/sapassword" to connect. The reason of
> error is bacause "sa" account's password has been changed, which is good
> (maybe the DB admin knew some apps use "sa" to access the SQL Server,
> which is bad practice, and he changed it?).
> You must find a way to reconfigure it to use new password. If the password
> is hard coded, then you may out luck to change it easily.
>
> "Marius Kaizerman" <marius@.kaizerman.org> wrote in message
> news:e9e%23NcDMIHA.4712@.TK2MSFTNGP04.phx.gbl...
> Hi,
> I have a program using ms sql. It worked fine for some time, but
> now each time the program access the databases it outputs "Connection
> Failed
> SQLState 28000, SQL Server Error 18456, Login failed for user 'sa'".
> After pressing OK it gives an option to input a new password manually, and
> after
> entering it - it works. But only for the current transaction. Next time
> it'll prompt again.
> I've tried to change the password, I've chaned it in the system ODBC
> drivers, tried
> different usernames, but the same error returns.
> What could be the problem ?
> Thanks.
I have a program using ms sql. It worked fine for some time, but
now each time the program access the databases it outputs "Connection Failed
SQLState 28000, SQL Server Error 18456, Login failed for user 'sa'".
After pressing OK it gives an option to input a new password manually, and after
entering it - it works. But only for the current transaction. Next time it'll prompt again.
I've tried to change the password, I've chaned it in the system ODBC drivers, tried
different usernames, but the same error returns.
What could be the problem ?
Thanks.
It depends on the said program. How the program is configured or coded to
connect to the SQL Server database? It sounds the program is configured or
hard-coded (too bad!!!) with "sa/sapassword" to connect. The reason of error
is bacause "sa" account's password has been changed, which is good (maybe
the DB admin knew some apps use "sa" to access the SQL Server, which is bad
practice, and he changed it?).
You must find a way to reconfigure it to use new password. If the password
is hard coded, then you may out luck to change it easily.
"Marius Kaizerman" <marius@.kaizerman.org> wrote in message
news:e9e%23NcDMIHA.4712@.TK2MSFTNGP04.phx.gbl...
Hi,
I have a program using ms sql. It worked fine for some time, but
now each time the program access the databases it outputs "Connection Failed
SQLState 28000, SQL Server Error 18456, Login failed for user 'sa'".
After pressing OK it gives an option to input a new password manually, and
after
entering it - it works. But only for the current transaction. Next time
it'll prompt again.
I've tried to change the password, I've chaned it in the system ODBC
drivers, tried
different usernames, but the same error returns.
What could be the problem ?
Thanks.
|||Norman,
You were absolutely right.
Thanks alot!
"Norman Yuan" <NoAddress@.NoEmail.fake> wrote in message
news:OonyLvDMIHA.1164@.TK2MSFTNGP02.phx.gbl...
> It depends on the said program. How the program is configured or coded to
> connect to the SQL Server database? It sounds the program is configured or
> hard-coded (too bad!!!) with "sa/sapassword" to connect. The reason of
> error is bacause "sa" account's password has been changed, which is good
> (maybe the DB admin knew some apps use "sa" to access the SQL Server,
> which is bad practice, and he changed it?).
> You must find a way to reconfigure it to use new password. If the password
> is hard coded, then you may out luck to change it easily.
>
> "Marius Kaizerman" <marius@.kaizerman.org> wrote in message
> news:e9e%23NcDMIHA.4712@.TK2MSFTNGP04.phx.gbl...
> Hi,
> I have a program using ms sql. It worked fine for some time, but
> now each time the program access the databases it outputs "Connection
> Failed
> SQLState 28000, SQL Server Error 18456, Login failed for user 'sa'".
> After pressing OK it gives an option to input a new password manually, and
> after
> entering it - it works. But only for the current transaction. Next time
> it'll prompt again.
> I've tried to change the password, I've chaned it in the system ODBC
> drivers, tried
> different usernames, but the same error returns.
> What could be the problem ?
> Thanks.
connection failed
Hi,
I have a program using ms sql. It worked fine for some time, but
now each time the program access the databases it outputs "Connection Failed
SQLState 28000, SQL Server Error 18456, Login failed for user 'sa'".
After pressing OK it gives an option to input a new password manually, and after
entering it - it works. But only for the current transaction. Next time it'll prompt again.
I've tried to change the password, I've chaned it in the system ODBC drivers, tried
different usernames, but the same error returns.
What could be the problem ?
Thanks.
It depends on the said program. How the program is configured or coded to
connect to the SQL Server database? It sounds the program is configured or
hard-coded (too bad!!!) with "sa/sapassword" to connect. The reason of error
is bacause "sa" account's password has been changed, which is good (maybe
the DB admin knew some apps use "sa" to access the SQL Server, which is bad
practice, and he changed it?).
You must find a way to reconfigure it to use new password. If the password
is hard coded, then you may out luck to change it easily.
"Marius Kaizerman" <marius@.kaizerman.org> wrote in message
news:e9e%23NcDMIHA.4712@.TK2MSFTNGP04.phx.gbl...
Hi,
I have a program using ms sql. It worked fine for some time, but
now each time the program access the databases it outputs "Connection Failed
SQLState 28000, SQL Server Error 18456, Login failed for user 'sa'".
After pressing OK it gives an option to input a new password manually, and
after
entering it - it works. But only for the current transaction. Next time
it'll prompt again.
I've tried to change the password, I've chaned it in the system ODBC
drivers, tried
different usernames, but the same error returns.
What could be the problem ?
Thanks.
|||Norman,
You were absolutely right.
Thanks alot!
"Norman Yuan" <NoAddress@.NoEmail.fake> wrote in message
news:OonyLvDMIHA.1164@.TK2MSFTNGP02.phx.gbl...
> It depends on the said program. How the program is configured or coded to
> connect to the SQL Server database? It sounds the program is configured or
> hard-coded (too bad!!!) with "sa/sapassword" to connect. The reason of
> error is bacause "sa" account's password has been changed, which is good
> (maybe the DB admin knew some apps use "sa" to access the SQL Server,
> which is bad practice, and he changed it?).
> You must find a way to reconfigure it to use new password. If the password
> is hard coded, then you may out luck to change it easily.
>
> "Marius Kaizerman" <marius@.kaizerman.org> wrote in message
> news:e9e%23NcDMIHA.4712@.TK2MSFTNGP04.phx.gbl...
> Hi,
> I have a program using ms sql. It worked fine for some time, but
> now each time the program access the databases it outputs "Connection
> Failed
> SQLState 28000, SQL Server Error 18456, Login failed for user 'sa'".
> After pressing OK it gives an option to input a new password manually, and
> after
> entering it - it works. But only for the current transaction. Next time
> it'll prompt again.
> I've tried to change the password, I've chaned it in the system ODBC
> drivers, tried
> different usernames, but the same error returns.
> What could be the problem ?
> Thanks.
I have a program using ms sql. It worked fine for some time, but
now each time the program access the databases it outputs "Connection Failed
SQLState 28000, SQL Server Error 18456, Login failed for user 'sa'".
After pressing OK it gives an option to input a new password manually, and after
entering it - it works. But only for the current transaction. Next time it'll prompt again.
I've tried to change the password, I've chaned it in the system ODBC drivers, tried
different usernames, but the same error returns.
What could be the problem ?
Thanks.
It depends on the said program. How the program is configured or coded to
connect to the SQL Server database? It sounds the program is configured or
hard-coded (too bad!!!) with "sa/sapassword" to connect. The reason of error
is bacause "sa" account's password has been changed, which is good (maybe
the DB admin knew some apps use "sa" to access the SQL Server, which is bad
practice, and he changed it?).
You must find a way to reconfigure it to use new password. If the password
is hard coded, then you may out luck to change it easily.
"Marius Kaizerman" <marius@.kaizerman.org> wrote in message
news:e9e%23NcDMIHA.4712@.TK2MSFTNGP04.phx.gbl...
Hi,
I have a program using ms sql. It worked fine for some time, but
now each time the program access the databases it outputs "Connection Failed
SQLState 28000, SQL Server Error 18456, Login failed for user 'sa'".
After pressing OK it gives an option to input a new password manually, and
after
entering it - it works. But only for the current transaction. Next time
it'll prompt again.
I've tried to change the password, I've chaned it in the system ODBC
drivers, tried
different usernames, but the same error returns.
What could be the problem ?
Thanks.
|||Norman,
You were absolutely right.
Thanks alot!
"Norman Yuan" <NoAddress@.NoEmail.fake> wrote in message
news:OonyLvDMIHA.1164@.TK2MSFTNGP02.phx.gbl...
> It depends on the said program. How the program is configured or coded to
> connect to the SQL Server database? It sounds the program is configured or
> hard-coded (too bad!!!) with "sa/sapassword" to connect. The reason of
> error is bacause "sa" account's password has been changed, which is good
> (maybe the DB admin knew some apps use "sa" to access the SQL Server,
> which is bad practice, and he changed it?).
> You must find a way to reconfigure it to use new password. If the password
> is hard coded, then you may out luck to change it easily.
>
> "Marius Kaizerman" <marius@.kaizerman.org> wrote in message
> news:e9e%23NcDMIHA.4712@.TK2MSFTNGP04.phx.gbl...
> Hi,
> I have a program using ms sql. It worked fine for some time, but
> now each time the program access the databases it outputs "Connection
> Failed
> SQLState 28000, SQL Server Error 18456, Login failed for user 'sa'".
> After pressing OK it gives an option to input a new password manually, and
> after
> entering it - it works. But only for the current transaction. Next time
> it'll prompt again.
> I've tried to change the password, I've chaned it in the system ODBC
> drivers, tried
> different usernames, but the same error returns.
> What could be the problem ?
> Thanks.
Wednesday, March 7, 2012
connection failed
Hi,
I have a program using ms sql. It worked fine for some time, but
now each time the program access the databases it outputs "Connection Failed
SQLState 28000, SQL Server Error 18456, Login failed for user 'sa'".
After pressing OK it gives an option to input a new password manually, and a
fter
entering it - it works. But only for the current transaction. Next time it'l
l prompt again.
I've tried to change the password, I've chaned it in the system ODBC drivers
, tried
different usernames, but the same error returns.
What could be the problem ?
Thanks.It depends on the said program. How the program is configured or coded to
connect to the SQL Server database? It sounds the program is configured or
hard-coded (too bad!!!) with "sa/sapassword" to connect. The reason of error
is bacause "sa" account's password has been changed, which is good (maybe
the DB admin knew some apps use "sa" to access the SQL Server, which is bad
practice, and he changed it?).
You must find a way to reconfigure it to use new password. If the password
is hard coded, then you may out luck to change it easily.
"Marius Kaizerman" <marius@.kaizerman.org> wrote in message
news:e9e%23NcDMIHA.4712@.TK2MSFTNGP04.phx.gbl...
Hi,
I have a program using ms sql. It worked fine for some time, but
now each time the program access the databases it outputs "Connection Failed
SQLState 28000, SQL Server Error 18456, Login failed for user 'sa'".
After pressing OK it gives an option to input a new password manually, and
after
entering it - it works. But only for the current transaction. Next time
it'll prompt again.
I've tried to change the password, I've chaned it in the system ODBC
drivers, tried
different usernames, but the same error returns.
What could be the problem ?
Thanks.|||Norman,
You were absolutely right.
Thanks alot!
"Norman Yuan" <NoAddress@.NoEmail.fake> wrote in message
news:OonyLvDMIHA.1164@.TK2MSFTNGP02.phx.gbl...
> It depends on the said program. How the program is configured or coded to
> connect to the SQL Server database? It sounds the program is configured or
> hard-coded (too bad!!!) with "sa/sapassword" to connect. The reason of
> error is bacause "sa" account's password has been changed, which is good
> (maybe the DB admin knew some apps use "sa" to access the SQL Server,
> which is bad practice, and he changed it?).
> You must find a way to reconfigure it to use new password. If the password
> is hard coded, then you may out luck to change it easily.
>
> "Marius Kaizerman" <marius@.kaizerman.org> wrote in message
> news:e9e%23NcDMIHA.4712@.TK2MSFTNGP04.phx.gbl...
> Hi,
> I have a program using ms sql. It worked fine for some time, but
> now each time the program access the databases it outputs "Connection
> Failed
> SQLState 28000, SQL Server Error 18456, Login failed for user 'sa'".
> After pressing OK it gives an option to input a new password manually, and
> after
> entering it - it works. But only for the current transaction. Next time
> it'll prompt again.
> I've tried to change the password, I've chaned it in the system ODBC
> drivers, tried
> different usernames, but the same error returns.
> What could be the problem ?
> Thanks.
I have a program using ms sql. It worked fine for some time, but
now each time the program access the databases it outputs "Connection Failed
SQLState 28000, SQL Server Error 18456, Login failed for user 'sa'".
After pressing OK it gives an option to input a new password manually, and a
fter
entering it - it works. But only for the current transaction. Next time it'l
l prompt again.
I've tried to change the password, I've chaned it in the system ODBC drivers
, tried
different usernames, but the same error returns.
What could be the problem ?
Thanks.It depends on the said program. How the program is configured or coded to
connect to the SQL Server database? It sounds the program is configured or
hard-coded (too bad!!!) with "sa/sapassword" to connect. The reason of error
is bacause "sa" account's password has been changed, which is good (maybe
the DB admin knew some apps use "sa" to access the SQL Server, which is bad
practice, and he changed it?).
You must find a way to reconfigure it to use new password. If the password
is hard coded, then you may out luck to change it easily.
"Marius Kaizerman" <marius@.kaizerman.org> wrote in message
news:e9e%23NcDMIHA.4712@.TK2MSFTNGP04.phx.gbl...
Hi,
I have a program using ms sql. It worked fine for some time, but
now each time the program access the databases it outputs "Connection Failed
SQLState 28000, SQL Server Error 18456, Login failed for user 'sa'".
After pressing OK it gives an option to input a new password manually, and
after
entering it - it works. But only for the current transaction. Next time
it'll prompt again.
I've tried to change the password, I've chaned it in the system ODBC
drivers, tried
different usernames, but the same error returns.
What could be the problem ?
Thanks.|||Norman,
You were absolutely right.
Thanks alot!
"Norman Yuan" <NoAddress@.NoEmail.fake> wrote in message
news:OonyLvDMIHA.1164@.TK2MSFTNGP02.phx.gbl...
> It depends on the said program. How the program is configured or coded to
> connect to the SQL Server database? It sounds the program is configured or
> hard-coded (too bad!!!) with "sa/sapassword" to connect. The reason of
> error is bacause "sa" account's password has been changed, which is good
> (maybe the DB admin knew some apps use "sa" to access the SQL Server,
> which is bad practice, and he changed it?).
> You must find a way to reconfigure it to use new password. If the password
> is hard coded, then you may out luck to change it easily.
>
> "Marius Kaizerman" <marius@.kaizerman.org> wrote in message
> news:e9e%23NcDMIHA.4712@.TK2MSFTNGP04.phx.gbl...
> Hi,
> I have a program using ms sql. It worked fine for some time, but
> now each time the program access the databases it outputs "Connection
> Failed
> SQLState 28000, SQL Server Error 18456, Login failed for user 'sa'".
> After pressing OK it gives an option to input a new password manually, and
> after
> entering it - it works. But only for the current transaction. Next time
> it'll prompt again.
> I've tried to change the password, I've chaned it in the system ODBC
> drivers, tried
> different usernames, but the same error returns.
> What could be the problem ?
> Thanks.
Friday, February 24, 2012
connection could not be established
Hi there,
Im running SQL server 2000 on SBS2k3. I have a couple of databases working
fine and then all of a sudden i was locked out of them when I go to server
enterprise manager with the following msg:
A connection could not be established to <server>
Reason: login failed for user '<domain>\administrator'
Please verify SQL Server is running and check your SQL Server registration
properties and try again.
Could someone please help me. I have checked and the service MSSQL Server
is running.
thank you
MikeMike
Perhasps you have changde a password for this login and your SQL Server was
registered (EM)by an old password.
"Mike Hunt" <ncc4@.hotmail.com> wrote in message
news:%23CXAyyprFHA.3836@.TK2MSFTNGP12.phx.gbl...
> Hi there,
> Im running SQL server 2000 on SBS2k3. I have a couple of databases
> working fine and then all of a sudden i was locked out of them when I go
> to server enterprise manager with the following msg:
> A connection could not be established to <server>
> Reason: login failed for user '<domain>\administrator'
> Please verify SQL Server is running and check your SQL Server registration
> properties and try again.
> Could someone please help me. I have checked and the service MSSQL Server
> is running.
> thank you
> Mike
>
Im running SQL server 2000 on SBS2k3. I have a couple of databases working
fine and then all of a sudden i was locked out of them when I go to server
enterprise manager with the following msg:
A connection could not be established to <server>
Reason: login failed for user '<domain>\administrator'
Please verify SQL Server is running and check your SQL Server registration
properties and try again.
Could someone please help me. I have checked and the service MSSQL Server
is running.
thank you
MikeMike
Perhasps you have changde a password for this login and your SQL Server was
registered (EM)by an old password.
"Mike Hunt" <ncc4@.hotmail.com> wrote in message
news:%23CXAyyprFHA.3836@.TK2MSFTNGP12.phx.gbl...
> Hi there,
> Im running SQL server 2000 on SBS2k3. I have a couple of databases
> working fine and then all of a sudden i was locked out of them when I go
> to server enterprise manager with the following msg:
> A connection could not be established to <server>
> Reason: login failed for user '<domain>\administrator'
> Please verify SQL Server is running and check your SQL Server registration
> properties and try again.
> Could someone please help me. I have checked and the service MSSQL Server
> is running.
> thank you
> Mike
>
connection could not be established
Hi there,
Im running SQL server 2000 on SBS2k3. I have a couple of databases working
fine and then all of a sudden i was locked out of them when I go to server
enterprise manager with the following msg:
A connection could not be established to <server>
Reason: login failed for user '<domain>\administrator'
Please verify SQL Server is running and check your SQL Server registration
properties and try again.
Could someone please help me. I have checked and the service MSSQL Server
is running.
thank you
Mike
Mike
Perhasps you have changde a password for this login and your SQL Server was
registered (EM)by an old password.
"Mike Hunt" <ncc4@.hotmail.com> wrote in message
news:%23CXAyyprFHA.3836@.TK2MSFTNGP12.phx.gbl...
> Hi there,
> Im running SQL server 2000 on SBS2k3. I have a couple of databases
> working fine and then all of a sudden i was locked out of them when I go
> to server enterprise manager with the following msg:
> A connection could not be established to <server>
> Reason: login failed for user '<domain>\administrator'
> Please verify SQL Server is running and check your SQL Server registration
> properties and try again.
> Could someone please help me. I have checked and the service MSSQL Server
> is running.
> thank you
> Mike
>
Im running SQL server 2000 on SBS2k3. I have a couple of databases working
fine and then all of a sudden i was locked out of them when I go to server
enterprise manager with the following msg:
A connection could not be established to <server>
Reason: login failed for user '<domain>\administrator'
Please verify SQL Server is running and check your SQL Server registration
properties and try again.
Could someone please help me. I have checked and the service MSSQL Server
is running.
thank you
Mike
Mike
Perhasps you have changde a password for this login and your SQL Server was
registered (EM)by an old password.
"Mike Hunt" <ncc4@.hotmail.com> wrote in message
news:%23CXAyyprFHA.3836@.TK2MSFTNGP12.phx.gbl...
> Hi there,
> Im running SQL server 2000 on SBS2k3. I have a couple of databases
> working fine and then all of a sudden i was locked out of them when I go
> to server enterprise manager with the following msg:
> A connection could not be established to <server>
> Reason: login failed for user '<domain>\administrator'
> Please verify SQL Server is running and check your SQL Server registration
> properties and try again.
> Could someone please help me. I have checked and the service MSSQL Server
> is running.
> thank you
> Mike
>
connection could not be established
Hi there,
Im running SQL server 2000 on SBS2k3. I have a couple of databases working
fine and then all of a sudden i was locked out of them when I go to server
enterprise manager with the following msg:
A connection could not be established to <server>
Reason: login failed for user '<domain>\administrator'
Please verify SQL Server is running and check your SQL Server registration
properties and try again.
Could someone please help me. I have checked and the service MSSQL Server
is running.
thank you
MikeMike
Perhasps you have changde a password for this login and your SQL Server was
registered (EM)by an old password.
"Mike Hunt" <ncc4@.hotmail.com> wrote in message
news:%23CXAyyprFHA.3836@.TK2MSFTNGP12.phx.gbl...
> Hi there,
> Im running SQL server 2000 on SBS2k3. I have a couple of databases
> working fine and then all of a sudden i was locked out of them when I go
> to server enterprise manager with the following msg:
> A connection could not be established to <server>
> Reason: login failed for user '<domain>\administrator'
> Please verify SQL Server is running and check your SQL Server registration
> properties and try again.
> Could someone please help me. I have checked and the service MSSQL Server
> is running.
> thank you
> Mike
>
Im running SQL server 2000 on SBS2k3. I have a couple of databases working
fine and then all of a sudden i was locked out of them when I go to server
enterprise manager with the following msg:
A connection could not be established to <server>
Reason: login failed for user '<domain>\administrator'
Please verify SQL Server is running and check your SQL Server registration
properties and try again.
Could someone please help me. I have checked and the service MSSQL Server
is running.
thank you
MikeMike
Perhasps you have changde a password for this login and your SQL Server was
registered (EM)by an old password.
"Mike Hunt" <ncc4@.hotmail.com> wrote in message
news:%23CXAyyprFHA.3836@.TK2MSFTNGP12.phx.gbl...
> Hi there,
> Im running SQL server 2000 on SBS2k3. I have a couple of databases
> working fine and then all of a sudden i was locked out of them when I go
> to server enterprise manager with the following msg:
> A connection could not be established to <server>
> Reason: login failed for user '<domain>\administrator'
> Please verify SQL Server is running and check your SQL Server registration
> properties and try again.
> Could someone please help me. I have checked and the service MSSQL Server
> is running.
> thank you
> Mike
>
Sunday, February 19, 2012
Connection between 2 databases in local sql server
Hi,
I have two different applications based on SQL server database.
In one of the applications I need to use the information stored in the second database, only for read purpose.
As I understand I need how some to make a link between the databases in order to share tables.
Can anybody advise me how to do that, if it is possible at all?
Thanks
Just use a fully qualified name i.e. Server.Database.Owner.Table
for example: Select * from MyServer.Northwind.dbo.Customers
Regards
Paul
|||Hi Paul,
Thanks for your replay, but maybe I'm not explained myself as well.
Because I'm accessing the database through ODBC, and when I'm using the specific DSN only the tables which are belongs to the specific database are available to me.
That’s the reason I though to make a link between the databases.
There is an option to do that?
|||The easy way would be to create a stored procedure and have it do the work for you.
The hard way would be to establish 2 connections and query the tables seperately. If you are using .NET you could them combine them in a DataSet as two DataTables and establish a DataRelation.
Regards
Paul
|||Hi Paul
Unfortunately I'm not using .NET, I'm working with VB6.
I'll appreciate it if you can be more specific about the stored procedure, how can I access the tables in the other database.
Thanks again
|||Something like:
Create Proc MyProcedure
AS
select * from Db1.dbo.Table1 as tb1
inner join Db2.dbo.OtherTable as tb2
on tb1.id = tb2.id
Set the command type in an ADO Command object to a Stored Procedure and the CommnandText to MyProcedure (the stored procedure name) and call the execute method.
Friday, February 17, 2012
connecting vb6 apps to sequel server 2005
We are currently migrating our sequel 6.5 databases to sequel 2005
We have a handful of vb6 apps that connect to the current 6.5 database.
Can anyone recommend the "best practice" for connecting vb6 apps to sequel 2005 databases ?
Thanks in advance.I dont find any difficulty in connection, still you can use the ADO connecting string to connect the server.
We have a handful of vb6 apps that connect to the current 6.5 database.
Can anyone recommend the "best practice" for connecting vb6 apps to sequel 2005 databases ?
Thanks in advance.I dont find any difficulty in connection, still you can use the ADO connecting string to connect the server.
Subscribe to:
Posts (Atom)