Where is “SQL server Surface Area configuration” in SQL Server 2008 R2 ?

Hello friends,

Many times you need to do SQL Server related configuration like, CLR enable, Xp_cmdShell, Remote Access etc.

 I am able to set this configuration in SQL server 2005 using “SQL server Surface Area configuration”. But I was surprised when I did not find this exe in SQL Server 2008 R2.

After little research I found how to get this “SQL Server Surface Area Configuration” in SQL server 2008 R2.

Step 1:- Right click the SQL Server 2008 Server in SQL Server Management Studio.

 Step 2:- Choose option “Facets


 Step 3:- You will get below screen. You just need to select “Surface Area Configuration” option from dropdown.

Step 4:- Once you have selected the “Surface Area Configuration “ then you will get following screen.


So now it is good to go and configure your setting.

Thanks & Best Regards

Rajat Jaiswal


6 thoughts on “Where is “SQL server Surface Area configuration” in SQL Server 2008 R2 ?

  1. is there other option to access the “SQL Server Surface Area Configuration”? when is not possible b/c is related to errors message

    Failed to connect to server WN7X64-7ZKSBS1. (Microsoft.SqlServer.ConnectionInfo)

    Program Location:

    at Microsoft.SqlServer.Management.Common.ConnectionManager.Connect()
    at Microsoft.SqlServer.Management.Common.ConnectionManager.PoolConnect()
    at Microsoft.SqlServer.Management.Common.ConnectionManager.get_DatabaseEngineType()
    at Microsoft.SqlServer.Management.Smo.Server.GetExecutionManager()
    at Microsoft.SqlServer.Management.Smo.Server.get_ExecutionManager()
    at Microsoft.SqlServer.Management.Smo.SqlSmoObject.get_ServerVersion()
    at Microsoft.SqlServer.Management.Smo.Information.get_Version()
    at Microsoft.SqlServer.Management.SqlMgmt.AgentAccess.IsAgentEnabled(Server server)
    at Microsoft.SqlServer.Management.UI.VSIntegration.ObjectExplorer.AgentPropertyHandler.PopulateProperties(INodeInformation source, INameObjectCollection properties)
    at Microsoft.SqlServer.Management.UI.VSIntegration.ObjectExplorer.NodeContext.PopulateProperties()
    at Microsoft.SqlServer.Management.UI.VSIntegration.ObjectExplorer.NavigableItemBuilder.SetStaticProperties(NodeContext nodeContext)
    at Microsoft.SqlServer.Management.UI.VSIntegration.ObjectExplorer.NavigableItemBuilder.BuildDynamicItemWithQuery(IList`1 nodes, INodeInformation source, INavigableItem sourceItem, String urnQuery, Boolean registerBuilder, Boolean registerBuiltItems)
    at Microsoft.SqlServer.Management.UI.VSIntegration.ObjectExplorer.NavigableItemBuilder.BuildDynamicItem(IList`1 nodes, INodeInformation source, INavigableItem sourceItem, IFilterProvider filter)
    at Microsoft.SqlServer.Management.UI.VSIntegration.ObjectExplorer.NavigableItemBuilder.Build(IList`1 nodes, INodeInformation source, INavigableItem sourceItem, IFilterProvider filter)
    at Microsoft.SqlServer.Management.UI.VSIntegration.ObjectExplorer.NavigableItem.RequestChildren(IGetChildrenRequest request)
    at Microsoft.SqlServer.Management.UI.VSIntegration.ObjectExplorer.ExplorerHierarchyNode.BuildChildren(WaitHandle quitEvent)


    A connection was successfully established with the server, but then an error occurred during the login process. (provider: Shared Memory Provider, error: 0 – No process is on the other end of the pipe.) (.Net SqlClient Data Provider)

    For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&EvtSrc=MSSQLServer&EvtID=233&LinkId=20476

    Server Name: WN7X64-XXXXX
    Error Number: 233
    Severity: 20
    State: 0

    Program Location:

    at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection)
    at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj)
    at System.Data.SqlClient.TdsParserStateObject.WriteSni()
    at System.Data.SqlClient.TdsParserStateObject.WritePacket(Byte flushMode)
    at System.Data.SqlClient.TdsParser.TdsLogin(SqlLogin rec)
    at System.Data.SqlClient.SqlInternalConnectionTds.Login(Int64 timerExpire, String newPassword)
    at System.Data.SqlClient.SqlInternalConnectionTds.AttemptOneLogin(ServerInfo serverInfo, String newPassword, Boolean ignoreSniOpenTimeout, Int64 timerExpire, SqlConnection owningObject)
    at System.Data.SqlClient.SqlInternalConnectionTds.LoginNoFailover(String host, String newPassword, Boolean redirectedUserInstance, SqlConnection owningObject, SqlConnectionString connectionOptions, Int64 timerStart)
    at System.Data.SqlClient.SqlInternalConnectionTds.OpenLoginEnlist(SqlConnection owningObject, SqlConnectionString connectionOptions, String newPassword, Boolean redirectedUserInstance)
    at System.Data.SqlClient.SqlInternalConnectionTds..ctor(DbConnectionPoolIdentity identity, SqlConnectionString connectionOptions, Object providerInfo, String newPassword, SqlConnection owningObject, Boolean redirectedUserInstance)
    at System.Data.SqlClient.SqlConnectionFactory.CreateConnection(DbConnectionOptions options, Object poolGroupProviderInfo, DbConnectionPool pool, DbConnection owningConnection)
    at System.Data.ProviderBase.DbConnectionFactory.CreateNonPooledConnection(DbConnection owningConnection, DbConnectionPoolGroup poolGroup)
    at System.Data.ProviderBase.DbConnectionFactory.GetConnection(DbConnection owningConnection)
    at System.Data.ProviderBase.DbConnectionClosed.OpenConnection(DbConnection outerConnection, DbConnectionFactory connectionFactory)
    at System.Data.SqlClient.SqlConnection.Open()
    at Microsoft.SqlServer.Management.Common.ConnectionManager.InternalConnect(WindowsIdentity impersonatedIdentity)
    at Microsoft.SqlServer.Management.Common.ConnectionManager.Connect()

    1. Hi Christina,

      Are you able to connect to the server using SQL SERVER Management studio ?

      Secondly which option from SQL Surface Area configuration you want to unable or disable. You can do with SQL Query also.


      1. HI Rajat,
        SQL SERVER Management studio is be able to do only remote connection ,but not for the local database that I used to do test development.

        This start to happen after run a system report from WIN7X64 b/c I did a wrong update to SQL 2008 r2
        I was tried to review the setting from SECURITY and PERMISION from the local server, but it is not possible any more

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

This site uses Akismet to reduce spam. Learn how your comment data is processed.