Forum Discussion

Axel_Lemaitre's avatar
Axel_Lemaitre
Copper Contributor
Jan 05, 2023

Project Server 2019 - Reporting Database Refresh fails

Dear,

We are using Project Server 2019 on-prem (16.0.10394.20016 - November 2022).

We tried to restore Enterprise Custom Fields using Administrative Restore in Central Admin to fix an issue with one custom field. But the Reporting Database Refresh job always fails with this message:

ReportingRDBRefreshMessageFailed (24023) - RDB area: Epm, error mode: ContinueOnErrors, lock RDB on errors: False, refresh sleep time: 00:05:00. Details: id='24023'
name='ReportingRDBRefreshMessageFailed'
uid='eb66d8b7-158d-ed11-9d0d-f44f4203e4b8'
QueueMessageBody='SPValidatingBinder: blocked type Microsoft.Office.Project.Server.BusinessLayer.ReportingLayer.RefreshStorageData denied.'
Error='RDB area: Epm, error mode: ContinueOnErrors, lock RDB on errors: False, refresh sleep time: 00:05:00'

Now the reporting schema is broken with missing data and columns in tables. We tried a lot of things found on different articles, but none was mentioning this specific error or solved the issue.

Can someone help?

Detailed error messages from ULS:

Medium PWA:https://pwa.com, ServiceApp:Project Server, PSI: [RDS] Start processing RDS job a1adf5f8-f68c-ed11-9d0d-f44f4203e4b8. Message type ReportRefreshMessage. Message: RDB area: Epm, error mode: ContinueOnErrors, lock RDB on errors: False, refresh sleep time: 00:05:00. 4c4289a0-fdb9-f036-0d63-a09ab044bc7d
Medium Entering Monitored Scope (Project Server SubDal:FillTypedDataSet -- pjdraft.MSP_ProjQ_Get_Queue_Local_Storage(StoredProcedure)). Parent=processing HandleMessage for message ReportRefreshMessage, message id 1, message group ReportingRefresh, uid a3adf5f8-f68c-ed11-9d0d-f44f4203e4b8 4c4289a0-fdb9-f036-0d63-a09ab044bc7d
Medium Leaving Monitored Scope: (Project Server SubDal:FillTypedDataSet -- pjdraft.MSP_ProjQ_Get_Queue_Local_Storage(StoredProcedure)) Execution Time=2.3948; CPU Milliseconds=0; SQL Query Count=1; Parent=processing HandleMessage for message ReportRefreshMessage, message id 1, message group ReportingRefresh, uid a3adf5f8-f68c-ed11-9d0d-f44f4203e4b8 4c4289a0-fdb9-f036-0d63-a09ab044bc7d
Unexpected SPValidatingBinder: blocked type Microsoft.Office.Project.Server.BusinessLayer.ReportingLayer.RefreshStorageData denied. 4c4289a0-fdb9-f036-0d63-a09ab044bc7d
Unexpected SPValidatingBinder: blocked type Microsoft.Office.Project.Server.BusinessLayer.ReportingLayer.RefreshStorageData denied. Class: QueueBlobObject Method: QueueBlob.get 4c4289a0-fdb9-f036-0d63-a09ab044bc7d
High PWA:https://pwa.com, ServiceApp:Project Server, PSI: [RDS] ULS Event: ReportingRDBRefreshMessageFailed was associated with exception: Microsoft.Office.Server.Security.SafeSerialization+BlockedTypeException: SPValidatingBinder: blocked type Microsoft.Office.Project.Server.BusinessLayer.ReportingLayer.RefreshStorageData denied. at Microsoft.SharePoint.SPValidatingBinder.BindToType(String assemblyName, String typeName) at System.Runtime.Serialization.Formatters.Binary.ObjectReader.Bind(String assemblyString, String typeString) at System.Runtime.Serialization.Formatters.Binary.ObjectReader.GetType(BinaryAssemblyInfo assemblyInfo, String name) at System.Runtime.Serialization.Formatters.Binary.ObjectMap..ctor(String objectName, String[] memberNames, BinaryTypeEnum[] binaryTypeEnumA, Object[] typeInformationA, Int32[] memberAssemIds, ObjectReader objectReader, Int32 objectId, BinaryAssemblyInfo assemblyInfo, SizedArray assemIdToAssemblyTable) at System.Runtime.Serialization.Formatters.Binary.__BinaryParser.ReadObjectWithMapTyped(BinaryObjectWithMapTyped record) at System.Runtime.Serialization.Formatters.Binary.__BinaryParser.Run() at System.Runtime.Serialization.Formatters.Binary.ObjectReader.Deserialize(HeaderHandler handler, __BinaryParser serParser, Boolean fCheck, Boolean isCrossAppDomain, IMethodCallMessage methodCallMessage) at System.Runtime.Serialization.Formatters.Binary.BinaryFormatter.Deserialize(Stream serializationStream, HeaderHandler handler, Boolean fCheck, Boolean isCrossAppDomain, IMethodCallMessage methodCallMessage) at Microsoft.Office.Project.Server.BusinessLayer.QueueMsg.QueueBlobObject.get_QueueBlob() at Microsoft.Office.Project.Server.BusinessLayer.ReportingLayer.RdsRefreshMessageProcessor.HandleMessage(Message msg, Group messageGroup, JobTicket jobTicket, MessageContext mContext) 4c4289a0-fdb9-f036-0d63-a09ab044bc7d
Medium PWA:https://pwa.com, ServiceApp:Project Server, PSI: [QUEUE] Message not processed: Group: a3adf5f8-f68c-ed11-9d0d-f44f4203e4b8 MsgId: 1 Type: ReportingRefresh 4c4289a0-fdb9-f036-0d63-a09ab044bc7d
Medium PWA:https://pwa.com, ServiceApp:Project Server, PSI: [QUEUE] [BlockPolicy] GroupType: ReportingRefresh MessageObject: Microsoft.Office.Project.Server.BusinessLayer.QueueMsg.ReportRefreshMessage Did not set Blocking Policy. Using Queue default. 4c4289a0-fdb9-f036-0d63-a09ab044bc7d
Medium Leaving Monitored Scope: ([QUEUE] Processing message group ReportingRefresh, message id 1, message type ReportRefreshMessage) Execution Time=4.7586; CPU Milliseconds=2; SQL Query Count=1; Parent=Processing message group ReportingRefresh, uid a3adf5f8-f68c-ed11-9d0d-f44f4203e4b8 4c4289a0-fdb9-f036-0d63-a09ab044bc7d
Warning Standard Information:PSI Entry Point: <unknown> Project User: <unknown> Correlation Id: <unknown> PWA Site URL: SA Name: <unknown> PSError: <unknown> A queue job has failed. This is a general error logged by the Project Server Queue everytime a job fails - for effective troubleshooting use this error message with other more specific error messages (if any), the Operations guide (which documents more details about queued jobs) and the trace log (which could provide more detailed context). More information about the failed job follows. GUID of the failed job: a1adf5f8-f68c-ed11-9d0d-f44f4203e4b8. Name of the computer that processed this job: 6ef98eb8-8a22-45c8-94e5-77e4c7a0d63a (to debug further, you need to look at the trace log from this computer). Failed job type: ReportingRefresh. Failed sub-job type: ReportRefreshMessage. Failed sub-job ID: 1. Stage where sub-job failed: (this is useful when one sub-job has more than one logical processing stages). 4c4289a0-fdb9-f036-0d63-a09ab044bc7d
Medium Error is: GeneralQueueJobFailed. Details: Queue Attributes: a1adf5f8-f68c-ed11-9d0d-f44f4203e4b8 6ef98eb8-8a22-45c8-94e5-77e4c7a0d63a ReportingRefresh ReportRefreshMessage 1 4c4289a0-fdb9-f036-0d63-a09ab044bc7d <null> . Standard Information: 4c4289a0-fdb9-f036-0d63-a09ab044bc7d

No RepliesBe the first to reply

Resources