Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase 123»»»

DAC issue Expand / Collapse
Author
Message
Posted Sunday, February 15, 2009 7:53 PM
UDP Broadcaster

UDP BroadcasterUDP BroadcasterUDP BroadcasterUDP BroadcasterUDP BroadcasterUDP BroadcasterUDP BroadcasterUDP Broadcaster

Group: General Forum Members
Last Login: Friday, April 5, 2013 4:43 PM
Points: 1,473, Visits: 1,314
I cannot connect an SQL instance using DAC from either a local machine or from a remote machine. The error I came across is as follow.

SQL Network Interfaces: An error occurred while obtaining the dedicated administrator connection (DAC) port. Make sure that SQL Browser is running, or check the error log for the port number [xFFFFFFFF].
Sqlcmd: Error: Microsoft SQL Native Client : 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 under the default settings SQL Server does not allow remote connections..
Sqlcmd: Error: Microsoft SQL Native Client : Login timeout expired.


I checked the following spots
DAC is enabled from the SQL Surface Area Configuration.
Remote Admin Connection is enabled from sp_configure.
SQL Server Browser is running.
I checked the port number 1434. It is open and is listening.

What did I miss here?
Any input will be greatly appreciated.
Post #657458
Posted Sunday, February 15, 2009 9:58 PM


Mr or Mrs. 500

Mr or Mrs. 500Mr or Mrs. 500Mr or Mrs. 500Mr or Mrs. 500Mr or Mrs. 500Mr or Mrs. 500Mr or Mrs. 500Mr or Mrs. 500

Group: General Forum Members
Last Login: Friday, April 25, 2014 2:52 AM
Points: 525, Visits: 1,125
Hi,

Can you execute this sp_configure 'remote admin connections', 1;

And DAC port is assigned dynamically it trys to connect using TCP on port 1434 and it is failing it tries to check with other ports. I think you have to execute that and try and if that does not work try connecting with
sqlcmd –Stcp:

Thanks
Chandra Mohan N





Thanks
Chandra Mohan
Post #657480
Posted Tuesday, February 17, 2009 12:15 AM


SSCertifiable

SSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiable

Group: General Forum Members
Last Login: Today @ 1:27 AM
Points: 7,001, Visits: 8,438
Books online states these restrictions:
Restrictions
Because the DAC exists solely for diagnosing server problems in rare
circumstances, there are some restrictions on the connection:

To guarantee that there are resources available for the connection,
only one DAC is allowed per instance of SQL Server.
If a DAC connection is already active, any new request
to connect through the DAC is denied with error 17810.


To conserve resources, SQL Server 2005 Express Edition does
not listen on the DAC port unless started with a trace flag 7806.


The DAC initially attempts to connect to the default database
associated with the login. After it is successfully connected,
you can connect to the master database. If the default database
is offline or otherwise not available, the connection will return
error 4060. However, it will succeed if you override the default database
to connect to the master database instead using the following
command:

sqlcmd –A –d master

We recommend that you connect to the master database with
the DAC because master is guaranteed to be available if the
instance of the Database Engine is started.


SQL Server prohibits running parallel queries or commands with the DAC.
For example, error 3637 is generated if you execute either of the
following statements with the DAC:
RESTORE
BACKUP

Only limited resources are guaranteed to be available with the DAC.
Do not use the DAC to run resource-intensive queries (for example.
a complex join on large table) or queries that may block.
This helps prevent the DAC from compounding any existing server
problems. To avoid potential blocking scenarios, if you have to run
queries that may block, run the query under snapshot-based isolation
levels if possible; otherwise, set the transaction isolation level to
READ UNCOMMITTED and set the LOCK_TIMEOUT value to a short
value such as 2000 milliseconds, or both. This will prevent the DAC
session from getting blocked. However, depending on the state that
the SQL Server is in, the DAC session might get blocked on a latch.
You might be able to terminate the DAC session using CNTRL-C but
it is not guaranteed. In that case, your only option may be to restart SQL Server.

Do any of these match your case ?


Johan


Don't drive faster than your guardian angel can fly ...
but keeping both feet on the ground won't get you anywhere

- How to post Performance Problems
- How to post data/code to get the best help


- How to prevent a sore throat after hours of presenting ppt ?


"press F1 for solution", "press shift+F1 for urgent solution"


Need a bit of Powershell? How about this

Who am I ? Sometimes this is me but most of the time this is me
Post #658241
Posted Thursday, February 19, 2009 7:05 PM
UDP Broadcaster

UDP BroadcasterUDP BroadcasterUDP BroadcasterUDP BroadcasterUDP BroadcasterUDP BroadcasterUDP BroadcasterUDP Broadcaster

Group: General Forum Members
Last Login: Friday, April 5, 2013 4:43 PM
Points: 1,473, Visits: 1,314
Thank you so much for the input above. I have tried all you recommended. It still does not work now, however.
Post #661022
Posted Friday, February 20, 2009 12:00 AM


SSCertifiable

SSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiable

Group: General Forum Members
Last Login: Today @ 1:27 AM
Points: 7,001, Visits: 8,438
what software level are you on ?
select @@version

You are using a login that is member of the sqlserver administrators group, right ?


Johan


Don't drive faster than your guardian angel can fly ...
but keeping both feet on the ground won't get you anywhere

- How to post Performance Problems
- How to post data/code to get the best help


- How to prevent a sore throat after hours of presenting ppt ?


"press F1 for solution", "press shift+F1 for urgent solution"


Need a bit of Powershell? How about this

Who am I ? Sometimes this is me but most of the time this is me
Post #661068
Posted Friday, February 20, 2009 10:39 AM
UDP Broadcaster

UDP BroadcasterUDP BroadcasterUDP BroadcasterUDP BroadcasterUDP BroadcasterUDP BroadcasterUDP BroadcasterUDP Broadcaster

Group: General Forum Members
Last Login: Friday, April 5, 2013 4:43 PM
Points: 1,473, Visits: 1,314
I used a sa account.
My SQL Server version is SQL 2005 enterprise edition with SP2.
Post #661510
Posted Friday, February 20, 2009 7:10 PM
SSCommitted

SSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommitted

Group: General Forum Members
Last Login: Thursday, May 22, 2014 7:04 AM
Points: 1,688, Visits: 8,766
Please look thru sql logs to find the port DAC is listening to and mention that port number wth the server name while taking DAC connection.

MJ
Post #661916
Posted Friday, February 20, 2009 7:34 PM
UDP Broadcaster

UDP BroadcasterUDP BroadcasterUDP BroadcasterUDP BroadcasterUDP BroadcasterUDP BroadcasterUDP BroadcasterUDP Broadcaster

Group: General Forum Members
Last Login: Friday, April 5, 2013 4:43 PM
Points: 1,473, Visits: 1,314
I did check. BOL states that DAC check default port first. If the default port does not exist, it will automatically check the open port for DAC.

Post #661923
Posted Saturday, February 21, 2009 2:17 AM


Old Hand

Old HandOld HandOld HandOld HandOld HandOld HandOld HandOld Hand

Group: General Forum Members
Last Login: Wednesday, June 18, 2014 10:33 AM
Points: 344, Visits: 1,543
Out if interest is your environment a clustered server configuration?


John Sansom (@sqlBrit) | www.johnsansom.com
Post #661986
Posted Saturday, July 4, 2009 12:57 AM
SSChasing Mays

SSChasing MaysSSChasing MaysSSChasing MaysSSChasing MaysSSChasing MaysSSChasing MaysSSChasing MaysSSChasing Mays

Group: General Forum Members
Last Login: Yesterday @ 12:24 PM
Points: 604, Visits: 1,306
i am also facing the similar problem in my sql server clustering configuration . it was not allowing me to open the surface area configuration wizard after changing the remote machine name as virtual machine name its allowing to open the surface area window now but its not allowing to modify the settings in the surface area configuration wizard ...its giving the error message you cannot modify the surface area configuration for clustering services ...

Thnks in Advance.
Post #747161
« Prev Topic | Next Topic »

Add to briefcase 123»»»

Permissions Expand / Collapse