none
Error "the local farm is not accessible. cmdlets with featuredependencyid are not registered"

    Domanda

  • Setup:

    VMWare WorkStation 8

    4 VM's

    All servers running fully updated MS Server 2008 R2

    • 1 Dedicated Sharepoint Server 2010 Enterprise Edition Service Pack 1
    • 1 Dedicated SQL Server 2008 R2 (Windows Authentication)
    • 1 Dedicated DC
    • 1 Win7 Client

    Least privilege install (technet), skipped Wizard, no Service Applications running yet, except the ones that automatically get activated.

    Whenever I try to start PS on my SP Server (as administrator or any user known in SP) I get this error.

    All I find on the internet is always the same, rights on SQL Server, run as admin, tried everything everybody mentions, nothing works.

    ULS shows me an error that I cannot connect to the DB Server (from time to time I used to get "unable to connect to config db" when opening SP site), but that cleared up almost entirely after running service pack 1.

    "Unable to connect" error probably cuz I had to use multiple IP addresses to get Internet connectivity on my domain (in another domain).

    Threw those NIC settings away, disabled 2nd NAT NIC in VM's, cleared all cache including ARP, DNS etc etc.

    I'm at a loss, almost to the point of reinstalling entire setup.

    venerdì 16 marzo 2012 16:57

Tutte le risposte

  • Output ULS now says Upgrade, log file too big to post here

    Central Administration says everything is fine.

    03/16/2012 18:02:25.52 PowerShell.exe (0x0F08) 0x0BFC SharePoint Foundation Database 880j High SqlError: 'Timeout expired.  The timeout period elapsed prior to completion of the operation or the server is not responding.'    Source: '.Net SqlClient Data Provider' Number: -2 State: 0 Class: 11 Procedure: '' LineNumber: 0 Server: 'sql02\sharepoint'

    03/16/2012 18:02:25.52 PowerShell.exe (0x0F08) 0x0BFC SharePoint Foundation Database 3355 Critical Cannot connect to SQL Server. sql02\sharepoint not found. Additional error information from SQL Server is included below.  Timeout expired.  The timeout period elapsed prior to completion of the operation or the server is not responding.
    03/16/2012 18:02:25.52 PowerShell.exe (0x0F08) 0x0BFC SharePoint Foundation Database tzku High ConnectionString: 'Data Source=sql02\sharepoint;Initial Catalog=SharePoint_Config;Integrated Security=True;Enlist=False;Asynchronous Processing=False;Connect Timeout=15'    ConnectionState: Closed ConnectionTimeout: 15
    03/16/2012 18:02:25.52 PowerShell.exe (0x0F08) 0x0BFC SharePoint Foundation Upgrade fbv7 Unexpected [powershell] [SPUpgradeSession] [ERROR] [16/03/2012 18:02:25]: CanUpgrade [SPConfigurationDatabase] failed.
    03/16/2012 18:02:25.52 PowerShell.exe (0x0F08) 0x0BFC SharePoint Foundation Upgrade fbv7 Unexpected [powershell] [SPUpgradeSession] [ERROR] [16/03/2012 18:02:25]: Exception: Timeout expired.  The timeout period elapsed prior to completion of the operation or the server is not responding.
    03/16/2012 18:02:25.54 PowerShell.exe (0x0F08) 0x0BFC SharePoint Foundation Upgrade fbv7 Unexpected [powershell] [SPUpgradeSession] [ERROR] [16/03/2012 18:02:25]:    at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection)     at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj)     at System.Data.SqlClient.TdsParserStateObject.ReadSniError(TdsParserStateObject stateObj, UInt32 error)     at System.Data.SqlClient.TdsParserStateObject.ReadSni(DbAsyncResult asyncResult, TdsParserStateObject stateObj)     at System.Data.SqlClient.TdsParserStateObject.ReadNetworkPacket()     at System.Data.SqlClient.TdsParser.ConsumePreLoginHandshake(Boolean encrypt, Boolean trustServerCert, Boolean& marsCapable)     at System.Data.SqlClient.TdsParser.Connect(ServerInfo serverInfo, SqlInternalConnectionTds connHandler, Boolean ignoreSniOpenTimeout, Int64 timerExpire, Boolean encrypt, Boolean trustServerCert, Boolean integratedSecurity, SqlConnection owningObject)     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.CreatePooledConnection(DbConnection owningConnection, DbConnectionPool pool, DbConnectionOptions options)     at System.Data.ProviderBase.DbConnectionPool.CreateObject(DbConnection owningObject)     at System.Data.ProviderBase.DbConnectionPool.UserCreateRequest(DbConnection owningObject)     at System.Data.ProviderBase.DbConnectionPool.GetConnection(DbConnection owningObject)     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.SharePoint.Utilities.SqlSession.OpenConnection()     at Microsoft.SharePoint.Utilities.SqlSession.ExecuteReader(SqlCommand command, CommandBehavior behavior, SqlQueryData monitoringData, Boolean retryForDeadLock)     at Microsoft.SharePoint.Utilities.SqlSession.ExecuteReader(SqlCommand command, Boolean retryForDeadLock)     at Microsoft.SharePoint.Utilities.SqlSession.ExecuteReader(SqlCommand command)     at Microsoft.SharePoint.Upgrade.SPDatabaseSequence.GetVersion(SPDatabase database, Guid id, Version defaultVersion, SqlSession session, SPDatabaseSequence sequence)     at Microsoft.SharePoint.Upgrade.SPDatabaseWssSequence.get_BuildVersion()     at Microsoft.SharePoint.Upgrade.SPSequence.get_CanUpgrade()     at Microsoft.SharePoint.Upgrade.SPUpgradeSession.CanUpgrade(Object o)
    03/16/2012 18:02:25.54 PowerShell.exe (0x0F08) 0x0BFC SharePoint Foundation Upgrade fbv7 Medium [powershell] [SPUpgradeSession] [DEBUG] [16/03/2012 18:02:25]: Cannot upgrade [SPConfigurationDatabase].
    03/16/2012 18:02:25.54 PowerShell.exe (0x0F08) 0x0BFC SharePoint Foundation Upgrade fbv7 Medium [powershell] [SPUpgradeSession] [DEBUG] [16/03/2012 18:02:25]: Skip [SPConfigurationDatabase] NeedsUpgrade.
    03/16/2012 18:02:25.54 PowerShell.exe (0x0F08) 0x0BFC SharePoint Foundation Database tzku High ConnectionString: 'Data Source=sql02\sharepoint;Initial Catalog=SharePoint_Config;Integrated Security=True;Enlist=False;Asynchronous Processing=False;Connect Timeout=15'    ConnectionState: Closed ConnectionTimeout: 15
    03/16/2012 18:02:25.54 PowerShell.exe (0x0F08) 0x0BFC SharePoint Foundation Upgrade fbv7 Unexpected [powershell] [SPUpgradeSession] [ERROR] [16/03/2012 18:02:25]: IsBackwardsCompatible [SPConfigurationDatabase] failed.
    03/16/2012 18:02:25.54 PowerShell.exe (0x0F08) 0x0BFC SharePoint Foundation Upgrade fbv7 Unexpected [powershell] [SPUpgradeSession] [ERROR]


    Filip Bosmans

    venerdì 16 marzo 2012 17:10
  • Yeah if you triple checked all the rights and even tried giving the farm account full rights to everything and still having issues, you may want to reinstall from scratch. With only a bare bones install, that'd probably be faster than all the troubleshooting. And who knows what problems you may have down the line if you don't find a conclusive answer for this one.
    venerdì 16 marzo 2012 19:46
  • Well, would definitely like to find out what exactly it is, for future reference ...

    Found that several people have this issue after an update MS Server 2008, but every time it got fixed by giving the logged on user sufficient rights or 'Run as administrator'.


    Filip Bosmans

    domenica 18 marzo 2012 12:44
  • Hi,

    At least for the "Cannot connect to configuration database" I found out what was causing it.

    My students installed a complete new farm, after running the initial wizard they immediately got this error.

    Even when creating a Webapp or subsequent Site Collection it returned this error but luckily it created the webapp/sc and db's nevertheless.

    After troubleshooting - several hours of going through log files I saw a ULS 'high' saying "Unable to create firewall rule for www.webapp.com:80, try creating the firewall rule manually".

    So it seems that the sql server is unable to go through the firewall (outbound?) when it wants to give "web application or site collection created successfully" onscreen. Strange thing is, whenever I started the farm in the morning I had to F5 2,3 times to get rid of the "Cannot" message".

    After manually opening the firewall 80 port (just to be sure I did it on SP as well as SQL but SQL should be enough) the error went away.

    Unfortunately I had little time to document and find out exactly what was going on, next time I encounter this I will put all info in this thread.

    My guess is rights issue (in SP when is it not a rights issue???) or connectivity with DC or something.


    Filip Bosmans

    giovedì 10 maggio 2012 07:32
  • Named Instance with custom TCP port not set on IP1-IPAll in the TCP/IP settings in SQL Configuration Manager was the cause, after correcting that, none of my farms had the issue.

    Firewall on 'Program' instead of 'Ports' avoids the issue as well.

     

    Filip Bosmans

    giovedì 13 settembre 2012 17:47