Hi
I am getting an error while backing up a particular database named "asset" . The error says ......
Server: Msg 3132, Level 16, State 1, Line 4
The media set for database 'Asset' has 2 family members but only 1 are provided. All members must be provided.
Server: Msg 3013, Level 16, State 1, Line 4
BACKUP DATABASE is terminating abnormally.
I have created two backup devices for this database ("asset") through enterprise manager.
AssetDMP
AssetLogDMP
I have total 9 databases out of which only this database throws error. All other database backups going fine.
Here is the query that I am using to backup the database and Log.
USE master
GO
IF EXISTS (SELECT * FROM sysdatabases WHERE name = 'Asset')
BACKUP DATABASE Asset TO AssetDMP WITH NOUNLOAD, STATS=10, INIT, SKIP
GO
IF EXISTS (SELECT * FROM sysdatabases WHERE name = 'Asset')
BACKUP LOG Asset TO AssetLogDMP WITH NOUNLOAD, STATS=10, INIT, SKIP
Please Help
Thank You / SsgThis error occurs if a member of the stripe set (the backup was performed to more than 1 backup file/device) that was originally used to create the backup, was not selected when you tried to perform the restore. The number that displays in the message shows the set or file number that is missing.
You need to provide all the backup devices, files in your restore command|||Originally posted by Satya
This error occurs if a member of the stripe set (the backup was performed to more than 1 backup file/device) that was originally used to create the backup, was not selected when you tried to perform the restore. The number that displays in the message shows the set or file number that is missing.
You need to provide all the backup devices, files in your restore command
Dear Satya,
Thanks a lot for your quick response. This issue has been resolved by re creating the devices ; but somehow I could not understand the root cause of the problem ;). Anyway, I wanted to ask one more question here...
I am using MS SQL 2000 Server. Can I move the dabases ( Master, Model , MSDB and tempdb) to a different drive location without re-installing SQL Server !!!
Waiting for an early reply...
Thanks again,
Ssg|||Here you go with this KBA (http://support.microsoft.com/default.aspx?scid=kb;EN-US;224071) .|||BTW where abouts you're in Bangalore??|||Originally posted by Satya
BTW where abouts you're in Bangalore??
Thanks Satya,
My Question has been answered. Great help !!!
I am in ShanthiNagar , Bangalore -27
R U Familiar with BLR ?? I mean r u a bangalorean ?
Tks / Ssg|||Glad this works... I sent you private message as its ideal for personal chat.|||Originally posted by Satya
Glad this works... I sent you private message as its ideal for personal chat.
satya,
I don't find any private mesg.. It shows empty..however you can mail me.
Thanks
Ssg|||My PM tracking confirms an email sent to you about this Private message, check the email when you registered to this site.
Showing posts with label msg. Show all posts
Showing posts with label msg. Show all posts
Wednesday, March 21, 2012
Monday, March 19, 2012
MS SQL Server
Hi Support,
I am unable to start the MS SQL Server.
Encountered error msg: "The system cannot find the file specified"
Please advise.
Thanks & Regards.
Vic..Hi John,
SQL Server version is 8.0
Where can I get the SQL logfile ?
Thanks & regards
"John Bell" wrote:
[vbcol=seagreen]
> Hi
> What version of SQL Server are you using? You should be able to find more
> information in the SQL Server log file. If you a want to start SQL Server
for
> a command prompt see [url]http://msdn2.microsoft.com/en-us/library/ms180965.aspx[/url
]
> John
> "Vic" wrote:
>|||Hi Vic
The SQL Server Event/Error Log File can be found in the <install
dir>\MSSQL\LOG directory and is called ERRORLOG older ones will have
ascending numeric prefixes.
John
"Vic" wrote:
[vbcol=seagreen]
> Hi John,
> SQL Server version is 8.0
> Where can I get the SQL logfile ?
> Thanks & regards
> "John Bell" wrote:
>|||Hi John,
My MSSQL Server is shown "Not Connected"
Errorlog msg "SQL terminated bcos of system shutdown"
Pls advise again. Thanks.
"John Bell" wrote:
[vbcol=seagreen]
> Hi Vic
> The SQL Server Event/Error Log File can be found in the <install
> dir>\MSSQL\LOG directory and is called ERRORLOG older ones will have
> ascending numeric prefixes.
> John
> "Vic" wrote:
>
I am unable to start the MS SQL Server.
Encountered error msg: "The system cannot find the file specified"
Please advise.
Thanks & Regards.
Vic..Hi John,
SQL Server version is 8.0
Where can I get the SQL logfile ?
Thanks & regards
"John Bell" wrote:
[vbcol=seagreen]
> Hi
> What version of SQL Server are you using? You should be able to find more
> information in the SQL Server log file. If you a want to start SQL Server
for
> a command prompt see [url]http://msdn2.microsoft.com/en-us/library/ms180965.aspx[/url
]
> John
> "Vic" wrote:
>|||Hi Vic
The SQL Server Event/Error Log File can be found in the <install
dir>\MSSQL\LOG directory and is called ERRORLOG older ones will have
ascending numeric prefixes.
John
"Vic" wrote:
[vbcol=seagreen]
> Hi John,
> SQL Server version is 8.0
> Where can I get the SQL logfile ?
> Thanks & regards
> "John Bell" wrote:
>|||Hi John,
My MSSQL Server is shown "Not Connected"
Errorlog msg "SQL terminated bcos of system shutdown"
Pls advise again. Thanks.
"John Bell" wrote:
[vbcol=seagreen]
> Hi Vic
> The SQL Server Event/Error Log File can be found in the <install
> dir>\MSSQL\LOG directory and is called ERRORLOG older ones will have
> ascending numeric prefixes.
> John
> "Vic" wrote:
>
MS SQL Server
Hi Support,
I am unable to start the MS SQL Server.
Encountered error msg: "The system cannot find the file specified"
Please advise.
Thanks & Regards.
Vic..
Hi John,
SQL Server version is 8.0
Where can I get the SQL logfile ?
Thanks & regards
"John Bell" wrote:
[vbcol=seagreen]
> Hi
> What version of SQL Server are you using? You should be able to find more
> information in the SQL Server log file. If you a want to start SQL Server for
> a command prompt see http://msdn2.microsoft.com/en-us/library/ms180965.aspx
> John
> "Vic" wrote:
|||Hi Vic
The SQL Server Event/Error Log File can be found in the <install
dir>\MSSQL\LOG directory and is called ERRORLOG older ones will have
ascending numeric prefixes.
John
"Vic" wrote:
[vbcol=seagreen]
> Hi John,
> SQL Server version is 8.0
> Where can I get the SQL logfile ?
> Thanks & regards
> "John Bell" wrote:
|||Hi John,
My MSSQL Server is shown "Not Connected"
Errorlog msg "SQL terminated bcos of system shutdown"
Pls advise again. Thanks.
"John Bell" wrote:
[vbcol=seagreen]
> Hi Vic
> The SQL Server Event/Error Log File can be found in the <install
> dir>\MSSQL\LOG directory and is called ERRORLOG older ones will have
> ascending numeric prefixes.
> John
> "Vic" wrote:
I am unable to start the MS SQL Server.
Encountered error msg: "The system cannot find the file specified"
Please advise.
Thanks & Regards.
Vic..
Hi John,
SQL Server version is 8.0
Where can I get the SQL logfile ?
Thanks & regards
"John Bell" wrote:
[vbcol=seagreen]
> Hi
> What version of SQL Server are you using? You should be able to find more
> information in the SQL Server log file. If you a want to start SQL Server for
> a command prompt see http://msdn2.microsoft.com/en-us/library/ms180965.aspx
> John
> "Vic" wrote:
|||Hi Vic
The SQL Server Event/Error Log File can be found in the <install
dir>\MSSQL\LOG directory and is called ERRORLOG older ones will have
ascending numeric prefixes.
John
"Vic" wrote:
[vbcol=seagreen]
> Hi John,
> SQL Server version is 8.0
> Where can I get the SQL logfile ?
> Thanks & regards
> "John Bell" wrote:
|||Hi John,
My MSSQL Server is shown "Not Connected"
Errorlog msg "SQL terminated bcos of system shutdown"
Pls advise again. Thanks.
"John Bell" wrote:
[vbcol=seagreen]
> Hi Vic
> The SQL Server Event/Error Log File can be found in the <install
> dir>\MSSQL\LOG directory and is called ERRORLOG older ones will have
> ascending numeric prefixes.
> John
> "Vic" wrote:
Monday, February 20, 2012
MS SQL & Msg 11, Level 16, State 1
Randomly, when trying to authenticate to a SQL server, whether via a
mmc connection, or via a SQL Query Analyzer, several DBAs / analysts
get the following error:
"Unable to connect to server <servername>:
Server: Msg 11, Level 16, State 1
[Microsoft][ODBC SQL Server Driver][DBNETLIB]General network error.
Check your network documentation."
This happens from variety of clients, whether XP or 2000. All of the
MS SQL servers are at 2000 SP3a. Everything is on the same LAN, no
firewalls in between.
This error always happens when integrated Windows authentication is
used; however, when using the SA account, no error occurs and the
account logs in.
Communication is established to the servers (green arrow is lit in the
mmc); however, when attempting authentication, that error randomly
occurs. The problem is, that the error will occur here and there, and
then the same server that had an issue with the integrated Windows
authentication with connect just fine via integrated Windows
authentication.
Where should I look? What could be a possible cause? Help.
General Network Errors are one of the most difficult to troubleshoot, due
to the randomness of the problem (and because this type of error can occur
for many different reasons) .
Below are some suggestions to help you diagnose the problem:
Problem Definition
=============================
(1) Has this worked in the past? If so, identify any changes that may have
occurred right before the problem started happening.
Did you apply any security patches or other upgrades?
Has the load changed on the web site or app that is receiving the errors?
Have there been any network configuration changes?
(2) Send us the exact error message with as much error information you can
get from it - with native error code if possible.
This will usually be a number like 10054 or 10061. This information is not
available from all data access technologies, but you should send us as much
as you can get. We need to get the exact error message, either from a log
file, screen shot, or any method that captures the specific error.
Collect :
(1) Exact error message and any error codes returned
(2) Time of day it occurred (*very* important). Does this seem to happen
only during certain times in the day?
(3) Is the problem consistent?
(i) No
"Does it reproduce repeatedly after it happens once?
"How often does it occur? (every 2 hours, once a week, etc)
"Have you noticed any patterns to what is being done on the server when
the problem occurs? For example, certain stored procedures, statements, etc.
"Do only certain clients experience the problem?
"Does it happen at certain times or the day, or under stress?
"Do multiple users experience the problem at the same time?
(ii) Yes
"Can you reproduce from another client like ODBC Test or Query Analyzer?
(4) How do you recover from the problem?
(a)If you are rebooting the entire machine where the error occurred, have
you tried recycling only the process that had the problem?
(b)Do you try to reconnect in code, and if so, does it work right away?
(5) What client are you using? i.e. ADO.NET (SqlClient), ADO, OLE DB, ODBC
(6)Are you using NIC teaming? Teaming means that all of the NICs are bound
together and appear as one IP/physical address.
The following is an example of a section of ipconfig output that indicates
that NIC teaming is being used:
Ethernet adapter public:
Connection-specific DNS Suffix . : [DNS server name]
Description . . . . . . . . . . . : Compaq Network Teaming Virtual Miniport
Physical Address. . . . . . . . . : [NIC address]
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : [IP address 1]
Subnet Mask . . . . . . . . . . . : 255.255.254.0
IP Address. . . . . . . . . . . . : [IP address 2]
Subnet Mask . . . . . . . . . . . : 255.255.254.0
IP Address. . . . . . . . . . . . : [IP address 3]
Subnet Mask . . . . . . . . . . . : 255.255.254.0
Default Gateway . . . . . . . . . : [gateway]
DNS Servers . . . . . . . . . . . : [DNS 1]
[DNS 2]
Primary WINS Server . . . . . . . : [WINS IP]
Secondary WINS Server . . . . . . : [WINS IP]
Note that the Description of the adapter includes the word "teaming", and
that there are multiple IP addresses all associated with this one adapter.
(7)If there are firewalls, do you have any timeout settings configured?
Connectivity problems can occur if a firewall times out a connection before
the client and SQL are done with it.
(8)For testing purposes, if possible:
i.Disable NIC teaming
ii.Eliminate routers or firewalls if possible to simplify the path between
the client and server. Move the server and client into the same subnet if
possible.
(9) Is there very heavy load on the SQL server when this happens?
Other troubleshotting steps
========================
What MDAC version are you on? if possible try upgrading to the latest MDAC
version
does this happen just from one client machine, some clients, or all client
machines? (you can register sql remotely)
is the issue tool specific? When trusted connections fail from enterprise
manager,do they also fail from query analyzer?
who are you looged on as when the trusted connections fail? Do trusted
connections fail - for all accounts - or just one specific account?
A network monitor trace will assist in determining what is going on in the
network level during this time. Run a network monitor trace from the CLIENT
and SERVER machien simultaneously and have your network admins analyze
these traces (to check for any network problems such as a bad NIC, bad
router,etc).
Please view these additional references as well (available at
http://support.microsoft.com):
TechNet Support WebCast: Known connectivity issues related to "General -
ID: 875285
You may not be able to connect to an instance of SQL Server 2000 Service -
ID: 884012
How to troubleshoot connectivity issues in SQL Server 2000 - ID: 827422
mmc connection, or via a SQL Query Analyzer, several DBAs / analysts
get the following error:
"Unable to connect to server <servername>:
Server: Msg 11, Level 16, State 1
[Microsoft][ODBC SQL Server Driver][DBNETLIB]General network error.
Check your network documentation."
This happens from variety of clients, whether XP or 2000. All of the
MS SQL servers are at 2000 SP3a. Everything is on the same LAN, no
firewalls in between.
This error always happens when integrated Windows authentication is
used; however, when using the SA account, no error occurs and the
account logs in.
Communication is established to the servers (green arrow is lit in the
mmc); however, when attempting authentication, that error randomly
occurs. The problem is, that the error will occur here and there, and
then the same server that had an issue with the integrated Windows
authentication with connect just fine via integrated Windows
authentication.
Where should I look? What could be a possible cause? Help.
General Network Errors are one of the most difficult to troubleshoot, due
to the randomness of the problem (and because this type of error can occur
for many different reasons) .
Below are some suggestions to help you diagnose the problem:
Problem Definition
=============================
(1) Has this worked in the past? If so, identify any changes that may have
occurred right before the problem started happening.
Did you apply any security patches or other upgrades?
Has the load changed on the web site or app that is receiving the errors?
Have there been any network configuration changes?
(2) Send us the exact error message with as much error information you can
get from it - with native error code if possible.
This will usually be a number like 10054 or 10061. This information is not
available from all data access technologies, but you should send us as much
as you can get. We need to get the exact error message, either from a log
file, screen shot, or any method that captures the specific error.
Collect :
(1) Exact error message and any error codes returned
(2) Time of day it occurred (*very* important). Does this seem to happen
only during certain times in the day?
(3) Is the problem consistent?
(i) No
"Does it reproduce repeatedly after it happens once?
"How often does it occur? (every 2 hours, once a week, etc)
"Have you noticed any patterns to what is being done on the server when
the problem occurs? For example, certain stored procedures, statements, etc.
"Do only certain clients experience the problem?
"Does it happen at certain times or the day, or under stress?
"Do multiple users experience the problem at the same time?
(ii) Yes
"Can you reproduce from another client like ODBC Test or Query Analyzer?
(4) How do you recover from the problem?
(a)If you are rebooting the entire machine where the error occurred, have
you tried recycling only the process that had the problem?
(b)Do you try to reconnect in code, and if so, does it work right away?
(5) What client are you using? i.e. ADO.NET (SqlClient), ADO, OLE DB, ODBC
(6)Are you using NIC teaming? Teaming means that all of the NICs are bound
together and appear as one IP/physical address.
The following is an example of a section of ipconfig output that indicates
that NIC teaming is being used:
Ethernet adapter public:
Connection-specific DNS Suffix . : [DNS server name]
Description . . . . . . . . . . . : Compaq Network Teaming Virtual Miniport
Physical Address. . . . . . . . . : [NIC address]
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : [IP address 1]
Subnet Mask . . . . . . . . . . . : 255.255.254.0
IP Address. . . . . . . . . . . . : [IP address 2]
Subnet Mask . . . . . . . . . . . : 255.255.254.0
IP Address. . . . . . . . . . . . : [IP address 3]
Subnet Mask . . . . . . . . . . . : 255.255.254.0
Default Gateway . . . . . . . . . : [gateway]
DNS Servers . . . . . . . . . . . : [DNS 1]
[DNS 2]
Primary WINS Server . . . . . . . : [WINS IP]
Secondary WINS Server . . . . . . : [WINS IP]
Note that the Description of the adapter includes the word "teaming", and
that there are multiple IP addresses all associated with this one adapter.
(7)If there are firewalls, do you have any timeout settings configured?
Connectivity problems can occur if a firewall times out a connection before
the client and SQL are done with it.
(8)For testing purposes, if possible:
i.Disable NIC teaming
ii.Eliminate routers or firewalls if possible to simplify the path between
the client and server. Move the server and client into the same subnet if
possible.
(9) Is there very heavy load on the SQL server when this happens?
Other troubleshotting steps
========================
What MDAC version are you on? if possible try upgrading to the latest MDAC
version
does this happen just from one client machine, some clients, or all client
machines? (you can register sql remotely)
is the issue tool specific? When trusted connections fail from enterprise
manager,do they also fail from query analyzer?
who are you looged on as when the trusted connections fail? Do trusted
connections fail - for all accounts - or just one specific account?
A network monitor trace will assist in determining what is going on in the
network level during this time. Run a network monitor trace from the CLIENT
and SERVER machien simultaneously and have your network admins analyze
these traces (to check for any network problems such as a bad NIC, bad
router,etc).
Please view these additional references as well (available at
http://support.microsoft.com):
TechNet Support WebCast: Known connectivity issues related to "General -
ID: 875285
You may not be able to connect to an instance of SQL Server 2000 Service -
ID: 884012
How to troubleshoot connectivity issues in SQL Server 2000 - ID: 827422
MS SQL & Msg 11, Level 16, State 1
Randomly, when trying to authenticate to a SQL server, whether via a
mmc connection, or via a SQL Query Analyzer, several DBAs / analysts
get the following error:
"Unable to connect to server <servername>:
Server: Msg 11, Level 16, State 1
[Microsoft][ODBC SQL Server Driver][DBNETLIB]General network err
or.
Check your network documentation."
This happens from variety of clients, whether XP or 2000. All of the
MS SQL servers are at 2000 SP3a. Everything is on the same LAN, no
firewalls in between.
This error always happens when integrated Windows authentication is
used; however, when using the SA account, no error occurs and the
account logs in.
Communication is established to the servers (green arrow is lit in the
mmc); however, when attempting authentication, that error randomly
occurs. The problem is, that the error will occur here and there, and
then the same server that had an issue with the integrated Windows
authentication with connect just fine via integrated Windows
authentication.
Where should I look? What could be a possible cause? Help.General Network Errors are one of the most difficult to troubleshoot, due
to the randomness of the problem (and because this type of error can occur
for many different reasons) .
Below are some suggestions to help you diagnose the problem:
Problem Definition
=============================
(1) Has this worked in the past? If so, identify any changes that may have
occurred right before the problem started happening.
Did you apply any security patches or other upgrades?
Has the load changed on the web site or app that is receiving the errors?
Have there been any network configuration changes?
(2) Send us the exact error message with as much error information you can
get from it - with native error code if possible.
This will usually be a number like 10054 or 10061. This information is not
available from all data access technologies, but you should send us as much
as you can get. We need to get the exact error message, either from a log
file, screen shot, or any method that captures the specific error.
Collect :
(1) Exact error message and any error codes returned
(2) Time of day it occurred (*very* important). Does this seem to happen
only during certain times in the day?
(3) Is the problem consistent?
(i) No
" Does it reproduce repeatedly after it happens once?
" How often does it occur? (every 2 hours, once a week, etc)
" Have you noticed any patterns to what is being done on the server when
the problem occurs? For example, certain stored procedures, statements, etc.
" Do only certain clients experience the problem?
" Does it happen at certain times or the day, or under stress?
" Do multiple users experience the problem at the same time?
(ii) Yes
" Can you reproduce from another client like ODBC Test or Query Analyzer?
(4) How do you recover from the problem?
(a) If you are rebooting the entire machine where the error occurred, have
you tried recycling only the process that had the problem?
(b) Do you try to reconnect in code, and if so, does it work right away?
(5) What client are you using? i.e. ADO.NET (SqlClient), ADO, OLE DB, ODBC
(6) Are you using NIC teaming? Teaming means that all of the NICs are bound
together and appear as one IP/physical address.
The following is an example of a section of ipconfig output that indicates
that NIC teaming is being used:
Ethernet adapter public:
Connection-specific DNS Suffix . : [DNS server name]
Description . . . . . . . . . . . : Compaq Network Teaming Virtual Miniport
Physical Address. . . . . . . . . : [NIC address]
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : [IP address 1]
Subnet Mask . . . . . . . . . . . : 255.255.254.0
IP Address. . . . . . . . . . . . : [IP address 2]
Subnet Mask . . . . . . . . . . . : 255.255.254.0
IP Address. . . . . . . . . . . . : [IP address 3]
Subnet Mask . . . . . . . . . . . : 255.255.254.0
Default Gateway . . . . . . . . . : [gateway]
DNS Servers . . . . . . . . . . . : [DNS 1]
[DNS 2]
Primary WINS Server . . . . . . . : [WINS IP]
Secondary WINS Server . . . . . . : [WINS IP]
Note that the Description of the adapter includes the word "teaming", and
that there are multiple IP addresses all associated with this one adapter.
(7) If there are firewalls, do you have any timeout settings configured?
Connectivity problems can occur if a firewall times out a connection before
the client and SQL are done with it.
(8) For testing purposes, if possible:
i. Disable NIC teaming
ii. Eliminate routers or firewalls if possible to simplify the path between
the client and server. Move the server and client into the same subnet if
possible.
(9) Is there very heavy load on the SQL server when this happens?
Other troubleshotting steps
========================
What MDAC version are you on? if possible try upgrading to the latest MDAC
version
does this happen just from one client machine, some clients, or all client
machines? (you can register sql remotely)
is the issue tool specific? When trusted connections fail from enterprise
manager,do they also fail from query analyzer?
who are you looged on as when the trusted connections fail? Do trusted
connections fail - for all accounts - or just one specific account?
A network monitor trace will assist in determining what is going on in the
network level during this time. Run a network monitor trace from the CLIENT
and SERVER machien simultaneously and have your network admins analyze
these traces (to check for any network problems such as a bad NIC, bad
router,etc).
Please view these additional references as well (available at
http://support.microsoft.com):
TechNet Support WebCast: Known connectivity issues related to "General -
ID: 875285
You may not be able to connect to an instance of SQL Server 2000 Service -
ID: 884012
How to troubleshoot connectivity issues in SQL Server 2000 - ID: 827422
mmc connection, or via a SQL Query Analyzer, several DBAs / analysts
get the following error:
"Unable to connect to server <servername>:
Server: Msg 11, Level 16, State 1
[Microsoft][ODBC SQL Server Driver][DBNETLIB]General network err
or.
Check your network documentation."
This happens from variety of clients, whether XP or 2000. All of the
MS SQL servers are at 2000 SP3a. Everything is on the same LAN, no
firewalls in between.
This error always happens when integrated Windows authentication is
used; however, when using the SA account, no error occurs and the
account logs in.
Communication is established to the servers (green arrow is lit in the
mmc); however, when attempting authentication, that error randomly
occurs. The problem is, that the error will occur here and there, and
then the same server that had an issue with the integrated Windows
authentication with connect just fine via integrated Windows
authentication.
Where should I look? What could be a possible cause? Help.General Network Errors are one of the most difficult to troubleshoot, due
to the randomness of the problem (and because this type of error can occur
for many different reasons) .
Below are some suggestions to help you diagnose the problem:
Problem Definition
=============================
(1) Has this worked in the past? If so, identify any changes that may have
occurred right before the problem started happening.
Did you apply any security patches or other upgrades?
Has the load changed on the web site or app that is receiving the errors?
Have there been any network configuration changes?
(2) Send us the exact error message with as much error information you can
get from it - with native error code if possible.
This will usually be a number like 10054 or 10061. This information is not
available from all data access technologies, but you should send us as much
as you can get. We need to get the exact error message, either from a log
file, screen shot, or any method that captures the specific error.
Collect :
(1) Exact error message and any error codes returned
(2) Time of day it occurred (*very* important). Does this seem to happen
only during certain times in the day?
(3) Is the problem consistent?
(i) No
" Does it reproduce repeatedly after it happens once?
" How often does it occur? (every 2 hours, once a week, etc)
" Have you noticed any patterns to what is being done on the server when
the problem occurs? For example, certain stored procedures, statements, etc.
" Do only certain clients experience the problem?
" Does it happen at certain times or the day, or under stress?
" Do multiple users experience the problem at the same time?
(ii) Yes
" Can you reproduce from another client like ODBC Test or Query Analyzer?
(4) How do you recover from the problem?
(a) If you are rebooting the entire machine where the error occurred, have
you tried recycling only the process that had the problem?
(b) Do you try to reconnect in code, and if so, does it work right away?
(5) What client are you using? i.e. ADO.NET (SqlClient), ADO, OLE DB, ODBC
(6) Are you using NIC teaming? Teaming means that all of the NICs are bound
together and appear as one IP/physical address.
The following is an example of a section of ipconfig output that indicates
that NIC teaming is being used:
Ethernet adapter public:
Connection-specific DNS Suffix . : [DNS server name]
Description . . . . . . . . . . . : Compaq Network Teaming Virtual Miniport
Physical Address. . . . . . . . . : [NIC address]
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : [IP address 1]
Subnet Mask . . . . . . . . . . . : 255.255.254.0
IP Address. . . . . . . . . . . . : [IP address 2]
Subnet Mask . . . . . . . . . . . : 255.255.254.0
IP Address. . . . . . . . . . . . : [IP address 3]
Subnet Mask . . . . . . . . . . . : 255.255.254.0
Default Gateway . . . . . . . . . : [gateway]
DNS Servers . . . . . . . . . . . : [DNS 1]
[DNS 2]
Primary WINS Server . . . . . . . : [WINS IP]
Secondary WINS Server . . . . . . : [WINS IP]
Note that the Description of the adapter includes the word "teaming", and
that there are multiple IP addresses all associated with this one adapter.
(7) If there are firewalls, do you have any timeout settings configured?
Connectivity problems can occur if a firewall times out a connection before
the client and SQL are done with it.
(8) For testing purposes, if possible:
i. Disable NIC teaming
ii. Eliminate routers or firewalls if possible to simplify the path between
the client and server. Move the server and client into the same subnet if
possible.
(9) Is there very heavy load on the SQL server when this happens?
Other troubleshotting steps
========================
What MDAC version are you on? if possible try upgrading to the latest MDAC
version
does this happen just from one client machine, some clients, or all client
machines? (you can register sql remotely)
is the issue tool specific? When trusted connections fail from enterprise
manager,do they also fail from query analyzer?
who are you looged on as when the trusted connections fail? Do trusted
connections fail - for all accounts - or just one specific account?
A network monitor trace will assist in determining what is going on in the
network level during this time. Run a network monitor trace from the CLIENT
and SERVER machien simultaneously and have your network admins analyze
these traces (to check for any network problems such as a bad NIC, bad
router,etc).
Please view these additional references as well (available at
http://support.microsoft.com):
TechNet Support WebCast: Known connectivity issues related to "General -
ID: 875285
You may not be able to connect to an instance of SQL Server 2000 Service -
ID: 884012
How to troubleshoot connectivity issues in SQL Server 2000 - ID: 827422
Subscribe to:
Posts (Atom)