Hello Vadim,
We still need to get confirmation from the external consultants who developed the BPC solution, but as far as I can understand it :
We do not use use member formulas
We are indeed talking about EPM (without EPMRetrieveData functions)
The perfromance problems occur in DEV and QAS , after a restore of the BPC environment (backup from PRD)
We already had the problem in the past, but we never knew precisely how to solve it, it is as if there was some missing links between the restored BPC environment from PRD and the DEV/QAS system
One additional information, we checked the EPM CLient Log , and here are the errors displayed while refreshing the input schedule :
The thing is that I have no idea what it means ...
?FILE_TYPE:DAAA96DE-B0FB-4c6e-AF7B-A445F5BF9BE2
RECORD_SEPARATOR:35
COLUMN_SEPARATOR:124
COLUMNS:Time|Severity|Category|Method|User|DSRRootContextID|DSRTransactionID|DSRConnectionID|DSRCounter|Thread|Text
SEVERITY_MAP:DEBUG|Debug|INFO|Information|VERBOSE|Verbose|WARNING|Warning|ERROR|Error|FATAL|Fatal
HEADER_END
2014-04-18 08:41:17,446|ERROR|ReportManagement|FPMXLClient.Office.EPMExcelReportManagerRepository.GetReportManager|BPCUSER|||||1|Unable to get the Object property of the OLEObject class#
2014-04-18 08:41:18,613|ERROR|ReportManagement|FPMXLClient.Office.EPMExcelReportManagerRepository.GetReportManager|BPCUSER|||||1|Unable to get the Object property of the OLEObject class#
2014-04-18 08:41:18,630|ERROR|ReportManagement|FPMXLClient.Office.EPMExcelReportManagerRepository.GetReportManager|BPCUSER|||||1|Unable to get the Object property of the OLEObject class#
2014-04-18 08:41:18,648|ERROR|ReportManagement|FPMXLClient.Office.EPMExcelReportManagerRepository.GetReportManager|BPCUSER|||||1|Unable to get the Object property of the OLEObject class#
2014-04-18 08:41:18,731|ERROR|ReportManagement|FPMXLClient.Office.EPMExcelReportManagerRepository.GetReportManager|BPCUSER|||||1|Unable to get the Object property of the OLEObject class#
2014-04-18 08:41:37,171|ERROR|ReportManagement|FPMXLClient.ReportManagement.DynamicReport.Load|BPCUSER|||||1|bytes = 1#
2014-04-18 08:41:39,348|ERROR|ReportManagement|FPMXLClient.ReportManagement.DynamicReport.Load|BPCUSER|||||1|bytes = 0#
2014-04-18 08:41:39,474|ERROR|ReportManagement|FPMXLClient.ReportManagement.DynamicReport.Load|BPCUSER|||||1|bytes = 0#
2014-04-18 08:41:39,536|ERROR|ReportManagement|FPMXLClient.ReportManagement.DynamicReport.Load|BPCUSER|||||1|bytes = 0#
2014-04-18 08:41:39,597|ERROR|ReportManagement|FPMXLClient.ReportManagement.DynamicReport.Load|BPCUSER|||||1|bytes = 0#
2014-04-18 09:00:22,088|ERROR|Dataservice|FPMXLClient.BPCProxy.MetaData_Data.DataServiceHelper.ExecuteReportAsStream|BPCUSER|||||ServerCallThread_666f378d-d824-4a8a-bf38-0da8493e2382|An error has occured on the server#
2014-04-18 09:00:22,252|ERROR|BPC10Connection|FPMXLClient.Connection.RESTConnection.ExecuteReport|BPCUSER|||||ServerCallThread_666f378d-d824-4a8a-bf38-0da8493e2382|An error has occured on the server#
2014-04-18 09:00:22,268|ERROR|OfficeWrappers|FPMXLClient.Office.EPMReportManager.ExecuteReport|BPCUSER|||||1|An error has occured on the server#
2014-04-18 09:00:22,317|ERROR|OfficeWrappers|FPMXLClient.Office.EPMExcelReportManager.RefreshReports|BPCUSER|||||1|An error has occured on the server#
2014-04-18 09:00:22,447|ERROR|AnalyzerOne|FPMXLClient.AddIn.RefreshSheetWithScan|BPCUSER|||||1|Execution of Report Default Report failed : #
2014-04-18 09:00:22,537|ERROR|Automation|FPMXLClient.EPMAddInAutomation.RefreshActiveSheet|BPCUSER|||||1|Execution of Report Default Report failed : #