InstantForum.NET v2.9.0SQLServerCentralhttp://www.sqlservercentral.com/Forums/notifications@sqlservercentral.comThu, 20 Jun 2013 03:38:28 GMT20http://www.sqlservercentral.com/Forums/Topic657458-146-1.aspxKeep in mind you [size="4"]cannot[/size] connect [b][u]Object Browser[/u][/b] using and [b][i]admin:[/i]server\instance [/b]connection.You must use a [u]Query panel[/u] ( New Query ) and then connect using [b][i]admin:[/i]server\instance [/b].Fri, 11 Jan 2013 03:40:17 GMTALZDBAhttp://www.sqlservercentral.com/Forums/Topic657458-146-1.aspxThanks for the replyWe have went through just about everything only one DBA is able to connect using DAC we know there is only one connection allowed. Is there any changes need to be done in configuration manager or settings some where?I didnt beleive so but just curiousThu, 10 Jan 2013 08:50:33 GMTD-SQLhttp://www.sqlservercentral.com/Forums/Topic657458-146-1.aspxAlso with SQL2012, only a single active DAC is allowed ![quote]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.[/quote]ref [url=http://msdn.microsoft.com/en-us/library/ms189595.aspx]Diagnostic Connection for Database Administrators[/url]Wed, 09 Jan 2013 23:52:14 GMTALZDBAhttp://www.sqlservercentral.com/Forums/Topic657458-146-1.aspxIm facing the same issue and we are SQL 2012 Enterprise, one thing is that one person on the team is able to connect but none of the rest of the team is able to we get the message as if it can connect mentioned in the beginning of this post.Any solution Thanks in advanceWed, 09 Jan 2013 17:40:54 GMTD-SQLhttp://www.sqlservercentral.com/Forums/Topic657458-146-1.aspx[quote][b]ALZDBA (7/6/2009)[/b][hr]Just another thought: You are at the console, or are using a remote desktop solution to run SAC, right ?We now only have SP3 instances with sql2005 and are not experiencing the problem you state.How To apply SP3:[url]www.sqlservercentral.com/articles/Installation/66128/[/url][b]Play it safe: start with a full backup of your instance(s)[/b]fyi:We didn't encounter problems when upgrading from sp2 cu2 to SP3 on our 2-node sql-cluster (multiple instances).[b]We do pay attention for the cluster resource to reside on the same node as the sql instance to be upgraded.[/b]We even upgraded multiple instances in a single run. We moved all instances to the same node before starting the upgrade.Off course it will not hurt to have a spare/backup set of resource db files !We take a copy of them after every upgrade (because at that moment is planned downtime).One thing we did observer is the needed reboot after the first instance + the client software have been upgraded.[/quote]Yes .. i have took the virutal machine by mstsc console and trying to modify the SAC ...thks for your information ....Mon, 06 Jul 2009 10:55:30 GMTsudhakarahttp://www.sqlservercentral.com/Forums/Topic657458-146-1.aspxJust another thought: You are at the console, or are using a remote desktop solution to run SAC, right ?We now only have SP3 instances with sql2005 and are not experiencing the problem you state.How To apply SP3:[url]www.sqlservercentral.com/articles/Installation/66128/[/url][b]Play it safe: start with a full backup of your instance(s)[/b]fyi:We didn't encounter problems when upgrading from sp2 cu2 to SP3 on our 2-node sql-cluster (multiple instances).[b]We do pay attention for the cluster resource to reside on the same node as the sql instance to be upgraded.[/b]We even upgraded multiple instances in a single run. We moved all instances to the same node before starting the upgrade.Off course it will not hurt to have a spare/backup set of resource db files !We take a copy of them after every upgrade (because at that moment is planned downtime).One thing we did observer is the needed reboot after the first instance + the client software have been upgraded.Mon, 06 Jul 2009 07:31:27 GMTALZDBAhttp://www.sqlservercentral.com/Forums/Topic657458-146-1.aspx[quote][b]ALZDBA (7/6/2009)[/b][hr]Oh, you should !Why ? - bugs have been cleaned up- new features have been added (SSB, logon triggers,..)- performance optimisations- SSMS menu items have been shifted around (SP2) :sick: The current is SP3 and they did release some cumulative updates for that too.[url]http://support.microsoft.com/kb/913089[/url][/quote]ya ..i should apply the service pack soon...i have to apply the service pack in sql server clustering environment ..could you explain me what are rules & steps should i follow at the time of service pack apply in cluster environment ? are u sure that this problem will be resolved after applying this sp3 ?Mon, 06 Jul 2009 06:34:30 GMTsudhakarahttp://www.sqlservercentral.com/Forums/Topic657458-146-1.aspxOh, you should !Why ? - bugs have been cleaned up- new features have been added (SSB, logon triggers,..)- performance optimisations- SSMS menu items have been shifted around (SP2) :sick: The current is SP3 and they did release some cumulative updates for that too.[url]http://support.microsoft.com/kb/913089[/url]Mon, 06 Jul 2009 04:42:15 GMTALZDBAhttp://www.sqlservercentral.com/Forums/Topic657458-146-1.aspx[quote][b]ALZDBA (7/6/2009)[/b][hr]What service pack is your sqlinstance on ?[code]Select Serverproperty( 'ComputerNamePhysicalNetBIOS' ) as ComputerNamePhysicalNetBIOS , Serverproperty( 'Edition' ) as Edition , Serverproperty( 'InstanceName' ) as InstanceName , Serverproperty( 'IsClustered' ) as IsClustered , Serverproperty( 'MachineName' ) as MachineName , Serverproperty( 'ProductVersion' ) as ProductVersion , Serverproperty( 'ProductLevel' ) as ProductLevel , Serverproperty( 'ResourceLastUpdateDateTime' ) as ResourceLastUpdateDateTime , Serverproperty( 'ResourceVersion' ) as ResourceVersion , Serverproperty( 'ServerName' ) as ServerName , USER_ID() AS [USER_ID] , USER_NAME() AS [USER_NAME] , SUSER_ID() AS [SUSER_ID] , SUSER_SNAME() AS [SUSER_SNAME] , IS_SRVROLEMEMBER ('sysadmin') AS [Is_ServerAdmin_Sysadmin] , ORIGINAL_LOGIN() AS [ORIGINAL_LOGIN][/code][/quote]i have not applied any service pack after installing sql server 2005 cluster standard edition ....Mon, 06 Jul 2009 04:16:05 GMTsudhakarahttp://www.sqlservercentral.com/Forums/Topic657458-146-1.aspxWhat service pack is your sqlinstance on ?[code]Select Serverproperty( 'ComputerNamePhysicalNetBIOS' ) as ComputerNamePhysicalNetBIOS , Serverproperty( 'Edition' ) as Edition , Serverproperty( 'InstanceName' ) as InstanceName , Serverproperty( 'IsClustered' ) as IsClustered , Serverproperty( 'MachineName' ) as MachineName , Serverproperty( 'ProductVersion' ) as ProductVersion , Serverproperty( 'ProductLevel' ) as ProductLevel , Serverproperty( 'ResourceLastUpdateDateTime' ) as ResourceLastUpdateDateTime , Serverproperty( 'ResourceVersion' ) as ResourceVersion , Serverproperty( 'ServerName' ) as ServerName , USER_ID() AS [USER_ID] , USER_NAME() AS [USER_NAME] , SUSER_ID() AS [SUSER_ID] , SUSER_SNAME() AS [SUSER_SNAME] , IS_SRVROLEMEMBER ('sysadmin') AS [Is_ServerAdmin_Sysadmin] , ORIGINAL_LOGIN() AS [ORIGINAL_LOGIN][/code]Mon, 06 Jul 2009 02:54:54 GMTALZDBAhttp://www.sqlservercentral.com/Forums/Topic657458-146-1.aspx[quote][b]ALZDBA (7/5/2009)[/b][hr]Did you change the SAC connection from localhost to the logical server name of your sqlserver instance ?e.g. [i]mysqlserver[/i]\myinstance you should connect to mysqlserver.[/quote]Yes ...After that only its allowing me to open the SAC wizard but while doing the some modification like enable or disable the dac remote access on the wizard its giving the error message .Mon, 06 Jul 2009 02:02:56 GMTsudhakarahttp://www.sqlservercentral.com/Forums/Topic657458-146-1.aspxDid you change the SAC connection from localhost to the logical server name of your sqlserver instance ?e.g. [i]mysqlserver[/i]\myinstance you should connect to mysqlserver.Sun, 05 Jul 2009 23:49:17 GMTALZDBAhttp://www.sqlservercentral.com/Forums/Topic657458-146-1.aspx[quote][b]ALZDBA (7/5/2009)[/b][hr]did you try this in SSMS:EXEC sp_configure 'remote admin connections', 1;GORECONFIGURE;GO[/quote]Yes .. i have enabled that by executiing that query already ..but issue is i could not able to modify the anything by using the sac wizard in sql server clustering setup.Sun, 05 Jul 2009 03:24:43 GMTsudhakarahttp://www.sqlservercentral.com/Forums/Topic657458-146-1.aspxdid you try this in SSMS:EXEC sp_configure 'remote admin connections', 1;GORECONFIGURE;GOSun, 05 Jul 2009 03:04:16 GMTALZDBAhttp://www.sqlservercentral.com/Forums/Topic657458-146-1.aspx[quote][b]ALZDBA (7/4/2009)[/b][hr]With clustering stuff, many thing [b]must[/b] be managed using cluster administrator!What are you looking for ? (With regards to instance management)[/quote]i want enable the DAC remote acces from SACSat, 04 Jul 2009 06:13:18 GMTsudhakarahttp://www.sqlservercentral.com/Forums/Topic657458-146-1.aspxWith clustering stuff, many thing [b]must[/b] be managed using cluster administrator!What are you looking for ? (With regards to instance management)Sat, 04 Jul 2009 01:59:15 GMTALZDBAhttp://www.sqlservercentral.com/Forums/Topic657458-146-1.aspxi 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.Sat, 04 Jul 2009 00:57:10 GMTsudhakarahttp://www.sqlservercentral.com/Forums/Topic657458-146-1.aspxOut if interest is your environment a clustered server configuration?Sat, 21 Feb 2009 02:17:43 GMTJohn.Sansomhttp://www.sqlservercentral.com/Forums/Topic657458-146-1.aspxI 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.Fri, 20 Feb 2009 19:34:41 GMTSQL ORACLEhttp://www.sqlservercentral.com/Forums/Topic657458-146-1.aspxPlease 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.MJFri, 20 Feb 2009 19:10:32 GMTMANU-J.http://www.sqlservercentral.com/Forums/Topic657458-146-1.aspxI used a sa account.My SQL Server version is SQL 2005 enterprise edition with SP2.Fri, 20 Feb 2009 10:39:30 GMTSQL ORACLEhttp://www.sqlservercentral.com/Forums/Topic657458-146-1.aspxwhat software level are you on ?[code]select @@version[/code]You are using a login that is member of the sqlserver administrators group, right ?Fri, 20 Feb 2009 00:00:28 GMTALZDBAhttp://www.sqlservercentral.com/Forums/Topic657458-146-1.aspxThank you so much for the input above. I have tried all you recommended. It still does not work now, however.Thu, 19 Feb 2009 19:05:25 GMTSQL ORACLEhttp://www.sqlservercentral.com/Forums/Topic657458-146-1.aspxBooks online states these restrictions:[code]RestrictionsBecause 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.[b]To conserve resources, SQL Server 2005 Express Edition does not listen on the DAC port unless started with a trace flag 7806.[/b]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:RESTOREBACKUP 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.[/code]Do any of these match your case ?Tue, 17 Feb 2009 00:15:26 GMTALZDBAhttp://www.sqlservercentral.com/Forums/Topic657458-146-1.aspxHi, 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: ThanksChandra Mohan NSun, 15 Feb 2009 21:58:44 GMTChand00http://www.sqlservercentral.com/Forums/Topic657458-146-1.aspxI 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.[i]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]I checked the following spotsDAC 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.Sun, 15 Feb 2009 19:53:41 GMTSQL ORACLE