Database is too new and is not supported

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

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 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