Archive for the ‘Farm’ Category

Add new Server in Farm with SharePoint, MSPS, OWS and LPs

Tuesday, May 13th, 2014
How to add a new server to the SharePoint Farm when the farm is running:
a. SharePoint 2010
b. MS Project Server 2010
c. Office Web App Server 2010
d. Language Packs

I ran through these steps.

1. Attach Setup files to new server [CD, Virtual Cd image, or setup files]
2. Start SharePoint setup and begin the SharePoint Pre-Req install
3. It failed listing update KB976462 as causing install error
4. Re-Ran the pre-req and it worked
5. Run the SharePoint 2010 setup
6. Change drive letter for Setup Data folder to D: drive. Leave the folder location with D drive as same. Also leave the SharePoint installation directory to C: drive default location
7. At the end of setup uncheck the option to Run Configuration Wizard and click close button.
8. Install Project Server 2010 setup (follow steps 6 & 7 during its setup and don’t run config wizard)
9. Install Office Web App 2010 setup (follow steps 6 & 7 during its setup and don’t run config wizard)
10. Install Language Packs for English, Chinese, Arabic or others. Install language packs for SharePoint 2010 Server version. (follow steps 6 & 7 during each setup and don’t run config wizard)
11. Install Service Pack 2 for SharePoint 2010 Server, Project Server 2010, Office Web Apps 2010, Language Packs SP 2 for each language listed in step 10 above. (follow steps 6 & 7 during its setup and don’t run config wizard)
12. Current Farm patch version was 14.0.7105.5000
13. Download Aug 2013 CU update that matches the version number for this patch.
14. Run SharePoint Config Wizard to join the server to the farm
15. Configure and verify the new server.

Database is too new and is not supported

Friday, April 11th, 2014
Issue Summary:
—————
In SharePoint Central Administration  > Upgrade and Migration > Database Status page, ProjectServer_Published DB is showing the status as “Database is too new and is not supported“.

Sometime ‘new’ is not good :o)

The farm had SP2 + August Cumulative Update applied to it.

‘Database is too new and is not supported’ status message
PWA Site Error:
The end user when go to Project Web Access (PWA) site get 503 – Service Unavailable error on page. Looking at the IIS Application Pool for PWA, you will see it is stopped. Even if you start, it will disable after sometime.
Server Side Event Viewer Errors:

Event Viewer Error 1:
In Application log of Event Viewer on Project Server Application server, following error is reported every minute:

Log Name:      Application
Source:        Microsoft-SharePoint Products-SharePoint Foundation
Date:          1/10/2014 12:33:18 PM
Event ID:      3759
Task Category: Database
Level:         Error
Keywords:      
User:          CompanyDomainSPFarmAct
Computer:      AppServer1.CompanyDomain.com
Description:
Database ‘ProjectServer_Published’ on SQL Server instance ‘SQLDBServer1’ is not empty and does not match current database schema.
Event Xml:
<Event xmlns=”http://schemas.microsoft.com/win/2004/08/events/event”>
  <System>
    <Provider Name=”Microsoft-SharePoint Products-SharePoint Foundation” Guid=”{E0CD6FB7-56E7-48DD-997A-

2413743931FT7}” />
    <EventID>3759</EventID>
    <Version>14</Version>
    <Level>2</Level>
    <Task>3</Task>
    <Opcode>0</Opcode>
    <Keywords>0x4000000000000000</Keywords>
    <TimeCreated SystemTime=”2014-01-10T17:33:18.835143500Z” />
    <EventRecordID>596174</EventRecordID>
    <Correlation />
    <Execution ProcessID=”5448″ ThreadID=”3644″ />
    <Channel>Application</Channel>
    <Computer>AppServer1.CompanyDomain.com</Computer>
    <Security UserID=”S-1-5-21-1627799274-1190182956-3998267559-1676″ />
  </System>
  <EventData>
    <Data Name=”string0″>ProjectServer_Published</Data>
    <Data Name=”string1″>SQLDBServer1</Data>
  </EventData>
</Event>

Event ID 3759

Event Viewer Error 2
Log Name:      Application
Source:        Microsoft-SharePoint Products-SharePoint Foundation
Date:          1/10/2014 11:41:25 AM
Event ID:      5586
Task Category: Database
Level:         Error
Keywords:      
User:          CompanyDomainSPFarmAct
Computer:      AppServer1.CompanyDomain.com
Description:
Unknown SQL Exception 0 occurred. Additional error information from SQL Server is included below.

Cannot generate SSPI context.
Event Xml:
<Event xmlns=”http://schemas.microsoft.com/win/2004/08/events/event”>
  <System>
    <Provider Name=”Microsoft-SharePoint Products-SharePoint Foundation” Guid=”{6FB7E0CD-52E7-47DD-997A-

241563931FC2}” />
    <EventID>5586</EventID>
    <Version>14</Version>
    <Level>2</Level>
    <Task>3</Task>
    <Opcode>0</Opcode>
    <Keywords>0x4000000000000000</Keywords>
    <TimeCreated SystemTime=”2014-01-10T16:41:25.298131300Z” />
    <EventRecordID>596117</EventRecordID>
    <Correlation />
    <Execution ProcessID=”3664″ ThreadID=”7240″ />
    <Channel>Application</Channel>
    <Computer>AppServer1.CompanyDomain.com</Computer>
    <Security UserID=”S-1-5-21-1627799274-1180182956-3999268559-1629″ />
  </System>
  <EventData>
    <Data Name=”int0″>0</Data>
    <Data Name=”string1″>Cannot generate SSPI context.</Data>
  </EventData>
</Event>

Event ID 5586

Event Viewer Error 1 on AppServer 2

Log Name:      Application
Source:        Microsoft-SharePoint Products-Project Server
Date:          1/10/2014 12:47:07 PM
Event ID:      7761
Task Category: Queue
Level:         Error
Keywords:      
User:          CompanyDomainSPFarmAct
Computer:      AppServer2.CompanyDomain.com
Description:
Standard Information:PSI Entry Point: 
Project User: CompanyDomainSPFarmAct
Correlation Id: f9863c76-c68f-4764-b51e-ad01dd237dd7
PWA Site URL: http://PS.CompanyDomain.com/PWA
SSP Name: Project Server Service Application
PSError: NoError (0)
An unxpected exception occurred in the Project Server Queue. Queue type (Project Queue/Timesheet Queue): 

ProjectQ. Exception details: PeriodicTasks failed.
Event Xml:
<Event xmlns=”http://schemas.microsoft.com/win/2004/08/events/event”>
  <System>
    <Provider Name=”Microsoft-SharePoint Products-Project Server” Guid=”{B2178104-1B5B-4C20-8C8F-

960678CED9E5}” />
    <EventID>7761</EventID>
    <Version>14</Version>
    <Level>2</Level>
    <Task>21</Task>
    <Opcode>0</Opcode>
    <Keywords>0x4000000000000000</Keywords>
    <TimeCreated SystemTime=”2014-01-10T17:47:07.776616700Z” />
    <EventRecordID>2026034</EventRecordID>
    <Correlation ActivityID=”{111A6951-5B30-454E-828C-73CC48CBD72A}” />
    <Execution ProcessID=”10012″ ThreadID=”1228″ />
    <Channel>Application</Channel>
    <Computer>AppServer2.CompanyDomain.com</Computer>
    <Security UserID=”S-1-5-21-1627799274-1180182956-3999268559-1629″ />
  </System>
  <EventData>
    <Data Name=”string0″>PSI Entry Point: 
Project User: CompanyDomainSPFarmAct
Correlation Id: f9863c76-c68f-4764-b51e-ad01dd237dd7
PWA Site URL: http://PS.CompanyDomain.com/PWA
SSP Name: Project Server Service Application
PSError: NoError (0)</Data>
    <Data Name=”string1″>ProjectQ</Data>
    <Data Name=”string2″>PeriodicTasks failed</Data>
  </EventData>
</Event>

Event ID 7761
Event Viewer Error 2 on AppServer 2
Log Name:      Application
Source:        Microsoft-SharePoint Products-Project Server
Date:          1/10/2014 12:47:07 PM
Event ID:      7758
Task Category: Queue
Level:         Critical
Keywords:      
User:          CompanyDomainSPFarmAct
Computer:      AppServer2.CompanyDomain.com
Description:
Standard Information:PSI Entry Point: 
Project User: CompanyDomainSPFarmAct
Correlation Id: f9863c76-c68f-4764-b51e-ad01dd237dd7
PWA Site URL: http://PS.CompanyDomain.com/PWA
SSP Name: Project Server Service Application
PSError: NoError (0)
Queue SQL call failed. Error: System.Data.SqlClient.SqlException: Invalid object name 

‘MSP_QUEUE_RENDEZVOUS’.
Invalid object name ‘dbo.MSP_QUEUE_RENDEZVOUS’.
Invalid object name ‘dbo.MSP_QUEUE_RENDEZVOUS’.
   at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection)
   at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj)
   at System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader 

dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj)
   at System.Data.SqlClient.SqlCommand.FinishExecuteReader(SqlDataReader ds, RunBehavior runBehavior, 

String resetOptionsString)
   at System.Data.SqlClient.SqlCommand.RunExecuteReaderTds(CommandBehavior cmdBehavior, RunBehavior 

runBehavior, Boolean returnStream, Boolean async)
   at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior 

runBehavior, Boolean returnStream, String method, DbAsyncResult result)
   at System.Data.SqlClient.SqlCommand.InternalExecuteNonQuery(DbAsyncResult result, String methodName, 

Boolean sendToPipe)
   at System.Data.SqlClient.SqlCommand.ExecuteNonQuery()
   at Microsoft.Office.Project.Server.DataAccessLayer.DAL.SubDal.ExecuteStoredProcedureReturnVal(String 

storedProcedureName, SqlParameter[] parameters)
   at Microsoft.Office.Project.Server.DataAccessLayer.QueueDal.PeriodicTasks(String prefix, Guid 

ServerUID, String machineName, String serviceName, Int32 queueId, Int32 TimeOut, Int32 recoverPriority, 

Nullable1 sendIncompleteTimeOut)
   at 

Microsoft.Office.Project.Server.BusinessLayer.Queue.BaseQueueAccess.SqlCallRetry.PeriodicTasksSqlCall.Exe

cute()
   at 

Microsoft.Office.Project.Server.BusinessLayer.Queue.BaseQueueAccess.SqlCallRetry.RetryableSqlCallBase.Exe

cuteRetryableSqlCall()
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Microsoft-SharePoint Products-Project Server" Guid="{B2178104-1B5B-4C20-8C8F-

960678CED9E5}" />
    <EventID>7758</EventID>
    <Version>14</Version>
    <Level>1</Level>
    <Task>21</Task>
    <Opcode>0</Opcode>
    <Keywords>0x4000000000000000</Keywords>
    <TimeCreated SystemTime="2014-01-10T17:47:07.776616700Z" />
    <EventRecordID>2026033</EventRecordID>
    <Correlation ActivityID="{111A6951-5B30-454E-828C-73CC48CBD72A}" />
    <Execution ProcessID="10012" ThreadID="1228" />
    <Channel>Application</Channel>
    <Computer>AppServer2.CompanyDomain.com</Computer>
    <Security UserID="S-1-5-21-1627799274-1180182956-3999268559-1629" />
  </System>
  <EventData>
    <Data Name="string0">PSI Entry Point: 
Project User: CompanyDomainSPFarmAct
Correlation Id: f9863c76-c68f-4764-b51e-ad01dd237dd7
PWA Site URL: http://PS.CompanyDomain.com/PWA
SSP Name: Project Server Service Application
PSError: NoError (0)</Data>
    <Data Name="string1">System.Data.SqlClient.SqlException: Invalid object name 'MSP_QUEUE_RENDEZVOUS'.
Invalid object name 'dbo.MSP_QUEUE_RENDEZVOUS'.
Invalid object name 'dbo.MSP_QUEUE_RENDEZVOUS'.
   at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection)
   at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj)
   at System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader 

dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj)
   at System.Data.SqlClient.SqlCommand.FinishExecuteReader(SqlDataReader ds, RunBehavior runBehavior, 

String resetOptionsString)
   at System.Data.SqlClient.SqlCommand.RunExecuteReaderTds(CommandBehavior cmdBehavior, RunBehavior 

runBehavior, Boolean returnStream, Boolean async)
   at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior 

runBehavior, Boolean returnStream, String method, DbAsyncResult result)
   at System.Data.SqlClient.SqlCommand.InternalExecuteNonQuery(DbAsyncResult result, String methodName, 

Boolean sendToPipe)
   at System.Data.SqlClient.SqlCommand.ExecuteNonQuery()
   at Microsoft.Office.Project.Server.DataAccessLayer.DAL.SubDal.ExecuteStoredProcedureReturnVal(String 

storedProcedureName, SqlParameter[] parameters)
   at Microsoft.Office.Project.Server.DataAccessLayer.QueueDal.PeriodicTasks(String prefix, Guid 

ServerUID, String machineName, String serviceName, Int32 queueId, Int32 TimeOut, Int32 recoverPriority, 

Nullable1 sendIncompleteTimeOut)
   at 

Microsoft.Office.Project.Server.BusinessLayer.Queue.BaseQueueAccess.SqlCallRetry.PeriodicTasksSqlCall.Exe

cute()
   at 

Microsoft.Office.Project.Server.BusinessLayer.Queue.BaseQueueAccess.SqlCallRetry.RetryableSqlCallBase.Exe

cuteRetryableSqlCall()</Data>
  </EventData>
</Event>
Event Viewer Error 3 on AppServer 2
Log Name:      Application
Source:        Microsoft-SharePoint Products-Project Server
Date:          1/10/2014 12:46:02 PM
Event ID:      7754
Task Category: Queue
Level:         Critical
Keywords:      
User:          CompanyDomainSPFarmAct
Computer:      AppServer2.CompanyDomain.com
Description:
Standard Information:PSI Entry Point: 
Project User: CompanyDomainSPFarmAct
Correlation Id: f9863c76-c68f-4764-b51e-ad01dd237dd7
PWA Site URL: http://PS.CompanyDomain.com/PWA
SSP Name: Project Server Service Application
PSError: NoError (0)
Queue unable to interact with SQL. Queue type (Project Queue, Timesheet Queue etc): ProjectQ Exception: 

Microsoft.Office.Project.Server.BusinessLayer.Queue.QueueSqlException: PeriodicTasks failed —> 

System.Data.SqlClient.SqlException: Invalid object name ‘MSP_QUEUE_RENDEZVOUS’.
Invalid object name ‘dbo.MSP_QUEUE_RENDEZVOUS’.
Invalid object name ‘dbo.MSP_QUEUE_RENDEZVOUS’.
   at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection)
   at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj)
   at System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader 

dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj)
   at System.Data.SqlClient.SqlCommand.FinishExecuteReader(SqlDataReader ds, RunBehavior runBehavior, 

String resetOptionsString)
   at System.Data.SqlClient.SqlCommand.RunExecuteReaderTds(CommandBehavior cmdBehavior, RunBehavior 

runBehavior, Boolean returnStream, Boolean async)
   at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior 

runBehavior, Boolean returnStream, String method, DbAsyncResult result)
   at System.Data.SqlClient.SqlCommand.InternalExecuteNonQuery(DbAsyncResult result, String methodName, 

Boolean sendToPipe)
   at System.Data.SqlClient.SqlCommand.ExecuteNonQuery()
   at Microsoft.Office.Project.Server.DataAccessLayer.DAL.SubDal.ExecuteStoredProcedureReturnVal(String 

storedProcedureName, SqlParameter[] parameters)
   at Microsoft.Office.Project.Server.DataAccessLayer.QueueDal.PeriodicTasks(String prefix, Guid 

ServerUID, String machineName, String serviceName, Int32 queueId, Int32 TimeOut, Int32 recoverPriority, 

Nullable1 sendIncompleteTimeOut)
   at 

Microsoft.Office.Project.Server.BusinessLayer.Queue.BaseQueueAccess.SqlCallRetry.PeriodicTasksSqlCall.Exe

cute()
   at 

Microsoft.Office.Project.Server.BusinessLayer.Queue.BaseQueueAccess.SqlCallRetry.RetryableSqlCallBase.Exe

cuteRetryableSqlCall()
   --- End of inner exception stack trace ---
   at 

Microsoft.Office.Project.Server.BusinessLayer.Queue.BaseQueueAccess.SqlCallRetry.RetryableSqlCallBase.Exe

cuteRetryableSqlCall()
   at 

Microsoft.Office.Project.Server.BusinessLayer.Queue.BaseQueueAccess.SqlCallRetry.PeriodicTasksSqlCall.Per

iodicTasksRetry(Guid serverUID, String machineName, String serviceName, Int32 queueId, Int32 timeOut, 

Int32 recoverPriority, Nullable1 sendIncompleteTimeOut)
   at Microsoft.Office.Project.Server.BusinessLayer.Queue.BaseQueueAccess.PeriodicTasks(Guid serverUID, 

String machineName, String serviceName, QueueID queueId, Int32 timeOut, QueueMsgPriority recoverPriority, 

Nullable1 sendIncompleteTimeout)
   at Microsoft.Office.Project.Server.BusinessLayer.Queue.Receiver.PeriodicTasks()
   at Microsoft.Office.Project.Server.BusinessLayer.Queue.Receiver.ThreadEntry()
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Microsoft-SharePoint Products-Project Server" Guid="{B2289104-1A7B-4C80-8C8F-

960357WED9E5}" />
    <EventID>7754</EventID>
    <Version>14</Version>
    <Level>1</Level>
    <Task>21</Task>
    <Opcode>0</Opcode>
    <Keywords>0x4000000000000000</Keywords>
    <TimeCreated SystemTime="2014-01-10T17:46:02.761407800Z" />
    <EventRecordID>2026032</EventRecordID>
    <Correlation ActivityID="{111A6951-5B30-454E-828C-73CC48CBD72A}" />
    <Execution ProcessID="10012" ThreadID="1228" />
    <Channel>Application</Channel>
    <Computer>AppServer2.CompanyDomain.com</Computer>
    <Security UserID="S-1-5-21-1627799274-1180182956-3999268559-1629" />
  </System>
  <EventData>
    <Data Name="string0">PSI Entry Point: 
Project User: CompanyDomainSPFarmAct
Correlation Id: f9863c76-c68f-4764-b51e-ad01dd237dd7
PWA Site URL: http://PS.CompanyDomain.com/PWA
SSP Name: Project Server Service Application
PSError: NoError (0)</Data>
    <Data Name="string1">ProjectQ</Data>
    <Data Name="string2">Microsoft.Office.Project.Server.BusinessLayer.Queue.QueueSqlException: 

PeriodicTasks failed ---&gt; System.Data.SqlClient.SqlException: Invalid object name 

'MSP_QUEUE_RENDEZVOUS'.
Invalid object name 'dbo.MSP_QUEUE_RENDEZVOUS'.
Invalid object name 'dbo.MSP_QUEUE_RENDEZVOUS'.
   at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection)
   at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj)
   at System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader 

dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj)
   at System.Data.SqlClient.SqlCommand.FinishExecuteReader(SqlDataReader ds, RunBehavior runBehavior, 

String resetOptionsString)
   at System.Data.SqlClient.SqlCommand.RunExecuteReaderTds(CommandBehavior cmdBehavior, RunBehavior 

runBehavior, Boolean returnStream, Boolean async)
   at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior 

runBehavior, Boolean returnStream, String method, DbAsyncResult result)
   at System.Data.SqlClient.SqlCommand.InternalExecuteNonQuery(DbAsyncResult result, String methodName, 

Boolean sendToPipe)
   at System.Data.SqlClient.SqlCommand.ExecuteNonQuery()
   at Microsoft.Office.Project.Server.DataAccessLayer.DAL.SubDal.ExecuteStoredProcedureReturnVal(String 

storedProcedureName, SqlParameter[] parameters)
   at Microsoft.Office.Project.Server.DataAccessLayer.QueueDal.PeriodicTasks(String prefix, Guid 

ServerUID, String machineName, String serviceName, Int32 queueId, Int32 TimeOut, Int32 recoverPriority, 

Nullable1 sendIncompleteTimeOut)
   at 

Microsoft.Office.Project.Server.BusinessLayer.Queue.BaseQueueAccess.SqlCallRetry.PeriodicTasksSqlCall.Exe

cute()
   at 

Microsoft.Office.Project.Server.BusinessLayer.Queue.BaseQueueAccess.SqlCallRetry.RetryableSqlCallBase.Exe

cuteRetryableSqlCall()
   — End of inner exception stack trace —
   at 

Microsoft.Office.Project.Server.BusinessLayer.Queue.BaseQueueAccess.SqlCallRetry.RetryableSqlCallBase.Exe

cuteRetryableSqlCall()
   at 

Microsoft.Office.Project.Server.BusinessLayer.Queue.BaseQueueAccess.SqlCallRetry.PeriodicTasksSqlCall.Per

iodicTasksRetry(Guid serverUID, String machineName, String serviceName, Int32 queueId, Int32 timeOut, 

Int32 recoverPriority, Nullable1 sendIncompleteTimeOut)
   at Microsoft.Office.Project.Server.BusinessLayer.Queue.BaseQueueAccess.PeriodicTasks(Guid serverUID, 

String machineName, String serviceName, QueueID queueId, Int32 timeOut, QueueMsgPriority recoverPriority, 

Nullable1 sendIncompleteTimeout)
   at Microsoft.Office.Project.Server.BusinessLayer.Queue.Receiver.PeriodicTasks()
   at Microsoft.Office.Project.Server.BusinessLayer.Queue.Receiver.ThreadEntry()</Data>
  </EventData>
</Event>
Event Viewer System Error 4 on AppServer 2
Log Name:      System
Source:        Microsoft-Windows-WAS
Date:          1/10/2014 11:19:16 AM
Event ID:      5059
Task Category: None
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      AppServer2.CompanyDomain.com
Description:
Application pool SharePoint – PS.CompanyDomain.com80 has been disabled. Windows Process Activation 

Service (WAS) encountered a failure when it started a worker process to serve the application pool.
Event Xml:
<Event xmlns=”http://schemas.microsoft.com/win/2004/08/events/event”>
  <System>
    <Provider Name=”Microsoft-Windows-WAS” Guid=”{524B5D04-133C-4A62-8362-64E8EDB9CE40}” 

EventSourceName=”WAS” />
    <EventID Qualifiers=”49152″>5059</EventID>
    <Version>0</Version>
    <Level>2</Level>
    <Task>0</Task>
    <Opcode>0</Opcode>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime=”2014-01-10T16:19:16.000000000Z” />
    <EventRecordID>132221</EventRecordID>
    <Correlation />
    <Execution ProcessID=”0″ ThreadID=”0″ />
    <Channel>System</Channel>
    <Computer>AppServer2.CompanyDomain.com</Computer>
    <Security />
  </System>
  <EventData>
    <Data Name=”AppPoolID”>SharePoint – PS.CompanyDomain.com80</Data>
    <Binary>
    </Binary>
  </EventData>
</Event>
Event ID 5059

Event Viewer System Error 5 on AppServer 2:
Log Name:      System
Source:        Microsoft-Windows-WAS
Date:          1/10/2014 11:19:16 AM
Event ID:      5057
Task Category: None
Level:         Warning
Keywords:      Classic
User:          N/A
Computer:      AppServer2.CompanyDomain.com
Description:
Application pool SharePoint – PS.CompanyDomain.com80 has been disabled. Windows Process Activation 

Service (WAS) did not create a worker process to serve the application pool because the application pool 

identity is invalid.
Event Xml:
<Event xmlns=”http://schemas.microsoft.com/win/2004/08/events/event”>
  <System>
    <Provider Name=”Microsoft-Windows-WAS” Guid=”{524B5D04-133C-4A62-8362-64E8EDB9CE40}” 

EventSourceName=”WAS” />
    <EventID Qualifiers=”32768″>5057</EventID>
    <Version>0</Version>
    <Level>3</Level>
    <Task>0</Task>
    <Opcode>0</Opcode>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime=”2014-01-10T16:19:16.000000000Z” />
    <EventRecordID>132220</EventRecordID>
    <Correlation />
    <Execution ProcessID=”0″ ThreadID=”0″ />
    <Channel>System</Channel>
    <Computer>AppServer2.CompanyDomain.com</Computer>
    <Security />
  </System>
  <EventData>
    <Data Name=”AppPoolID”>SharePoint – PS.CompanyDomain.com80</Data>
    <Binary>
    </Binary>
  </EventData>
</Event>

Event ID 5057

Event Viewer System Error 6 on AppServer 2:
Log Name:      System
Source:        Microsoft-Windows-WAS
Date:          1/10/2014 11:19:16 AM
Event ID:      5021
Task Category: None
Level:         Warning
Keywords:      Classic
User:          N/A
Computer:      AppServer2.CompanyDomain.com
Description:
The identity of application pool SharePoint – PS.CompanyDomain.com80 is invalid. The user name or 

password that is specified for the identity may be incorrect, or the user may not have batch logon 

rights. If the identity is not corrected, the application pool will be disabled when the application pool 

receives its first request.  If batch logon rights are causing the problem, the identity in the IIS 

configuration store must be changed after rights have been granted before Windows Process Activation 

Service (WAS) can retry the logon. If the identity remains invalid after the first request for the 

application pool is processed, the application pool will be disabled. The data field contains the error 

number.
Event Xml:
<Event xmlns=”http://schemas.microsoft.com/win/2004/08/events/event”>
  <System>
    <Provider Name=”Microsoft-Windows-WAS” Guid=”{524B5D04-133C-4A62-8362-64E8EDB9CE40}” 

EventSourceName=”WAS” />
    <EventID Qualifiers=”32768″>5021</EventID>
    <Version>0</Version>
    <Level>3</Level>
    <Task>0</Task>
    <Opcode>0</Opcode>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime=”2014-01-10T16:19:16.000000000Z” />
    <EventRecordID>132219</EventRecordID>
    <Correlation />
    <Execution ProcessID=”0″ ThreadID=”0″ />
    <Channel>System</Channel>
    <Computer>AppServer2.CompanyDomain.com</Computer>
    <Security />
  </System>
  <EventData>
    <Data Name=”AppPoolID”>SharePoint – PS.CompanyDomain.com80</Data>
    <Binary>75070780</Binary>
  </EventData>
</Event>

Event ID 5021

Resolution:
The Sharepoint / Project Server farm had SP2 and August 2013 Cumulative Update.

A quick run of the following SQL statement against ProjectServer_Published database verified its schema version.

select * from versions

ProjectServer_Published Database Schema in SQL Server

I then created a SQL update query to update the schema version of last row under ProjectServer_Published database – above screenshot. I changed the version from 14.2.151.0 to 14.1.653.0.

SQL Update Statement:

select * from Versions 
where VersionId = ‘AE40B1C1-23C6-4FA5-95D0-29FD61DDB2DA’
— Change from current version 14.2.151.0 to version 14.1.653.0

/* 
— Make sure to backup your databases and farm before modifying SQL tables.
update Versions
set Version = ‘14.1.653.0’
where VersionId = ‘AE40B1C1-23C6-4FA5-95D0-29FD61DDB2DA’
*/

ProjectServer_Published Database Schema in SQL Server before change – SQL Update statement above

After changing the schema version in database, I ran the following SharePoint command.
psconfig -cmd upgrade -inplace b2b  -wait -force

Sharepoint PSConfig Upgrade Force command status

At this point looking at the schema version in the ProjectServer_Published database’s Versions table showed new updated version. See below screenshot.

ProjectServer_Published Database Schema in SQL Server after manual change and PSConfig

Now looking at the SharePoint Central Administration  > Upgrade and Migration > Database Status page, I found that the database was showing as ‘No Action Required‘ – the target achieved.

ProjectServer_Published database with ‘No Action Required’ status

References:

  1. http://blogs.msdn.com/b/projectengineeringde/archive/2013/09/16/patchen-august-2013-cu-amp-sp2-beim-project-server-2010.aspx
  2. http://blogs.technet.com/b/projectsupport/archive/2013/09/12/project-server-2010-service-pack2-and-august-2013-cumulative-update-installation-issues.aspx
  3. http://blogs.msdn.com/b/projectengineeringde/archive/2013/09/16/patchen-august-2013-cu-amp-sp2-beim-project-server-2010.aspx

Adding new SharePoint ProjectServer to Farm Issue

Friday, April 11th, 2014
Scenario:

SharePoint 2010 farm with multiple servers in web and App layer. You want to add a new Web server for Microsoft SharePoint / Microsoft Project Server, and SharePoint Configuration fails on the new server. The farm has been running Sharepoint 2010, MS Project Server 2010, Office Web Apps and Language Packs. 
Error Message:
SharePoint Products Configuration Wizard brings the following message after you select the SQL Database server and then the SharePoint Farm Configuration DB.
Server Farm Products and Patch Status
The following SharePoint Technologies based products and patches were detected on your server farm.

Error:
Some farm products and patches were not detected on this or other servers. If products or patches are missing locally, you must quit this program and install the required products and patches on this server before restarting the wizard. If products or patches are missing on other servers, you must install the required products and patches on the specific servers, and you may then click the Refresh button to perform the status check again.

Scroll down the list and you will see other updates as missing as well. In my case it listed the following updates as missing on three existing servers and the new server.
Server Farm Products Status
——————————————————–
1. Microsoft Word Server
———————
HotFix for Sharepoint Server 2010 x64    Missing on SPServer01, 02 and 03
KB2825949
Security Update for Sharepoint 2010        Missing Locally [SPServer07new]
KB2837577
2. Excel Services Components
————————–
Hotfix for Sharepoint 2010 x64              Missing on SPServer01, 02 and 03
KB2825949
Security Update for Ms Sharepoint X64 Missing Locally [SPServer07new]
KB2826029
3. Access Services
——————–
Hotfix for Sharepoint 2010 x64 Missing on SPServer01, 02 and 03
KB2825949
Security Update for 2010 MS Business Missing Locally [SPServer07new]
Productivity Servers
KB2553298
The error listed basically the MS KB 2825949 patch as missing on all existing servers. That error was misleading. That patch was existed on existing servers.
I then looked for the three patches on local server – i.e the new server. The local server was missing these updates:
The new server is missing three MS KB updates.
a. KB2826029 – Excel Services Update
b. KB2553298 – Access Services / MS Business Productivity Update
c. KB2837577 – Word Automation Service Update
I went to Microsoft Knowledge base (KB) article page for KB 2826029 – Excel Services Patch to begin with. http://support.microsoft.com/kb/2826029
There wasn’t a patch download link on that KB article. I went to the IT Professional page link on that KB article and that took me to http://technet.microsoft.com/security/bulletin/MS13-084. Under ‘Affected and Non-Affected Software’ section, click the link for the SharePoint 2010 server SP2 related links. There are links for WSS, Excel Services, Word Automation. In our case the missing update KB number matches the Excel update 2826029. I downloaded and installed the Excel update. The same way I found the other two patches.
KB2826029 – Excel Services Patch – Download Link
KB2553298 – Access / Business Productivity – Download Link
KB2837577 – Word Automation Service – Download Link
I re-ran the Sharepoint Configuration wizard and it completed successfully. New Server was now part of the farm. 
Final Conclusion:
In my case, it was key to pay attention to ‘Missing Locally’ patches in the error screen. I confirmed the missing patches on new server by using Control Panel > Uninstall a Program > View Installed Updates section.
Some blogs suggest running following command to fix the issue. In my case, those smaller patches were indeed missing.
Get-SPProduct –local
psconfig -cmd installcheck -noinstallcheck
psconfig -cmd upgrade -inplace b2b -force -cmd -installcheck -noinstallcheck