SYMPTOM:
When running a MDX report, user may encounter a similar error as below:
[Database Classes][Error] XMLA Discover failed. SOAP Error.
Error type: XMLA error. XMLAError[SOAP Fault]: <faultcode>soap:Client</faultcode><faultactor>http://localhost/StrategyMDX/StrategyMDX.asmx</faultactor><faultstring>System.Web.Services.Protocols.SoapException: Fault occurred
at Service.Discover(String RequestType, XmlElement Restrictions, XmlElement Properties)</faultstring><detail><MSTRXmlaErrorCode xmlns=urn:schemas-microsoft-com:xml-analysis Code="00000000" ></MSTRXmlaErrorCode><MSTRXmlaErrorString xmlns=urn:schemas-microsoft-com:xml-analysis String="invalid timestamp, replay attack detected" ></MSTRXmlaErrorString><InternalErrorCode xmlns=urn:schemas-microsoft-com:xml-analysis Code="0" ></InternalErrorCode><InternalErrorString xmlns=urn:schemas-microsoft-com:xml-analysis String="" ></InternalErrorString><StackTrace xmlns=urn:schemas-microsoft-com:xml-analysis String=" at XMLA.OCI.DiscoverHandler.DecryptCredentials(XmlElement irConnectionInfo, String iEncrypedCredentials, String& orUserID, String& orPwd)
CAUSE:
One possible cause for this issue is that the parameter “DecryptionDelay” has been reached. This value in Datasources.xml is used for checking the reply between the Intelligence Server and the MDX provider. If the network is poor and the waiting time is longer than this value, the error "invalid timestamp, replay attack detected" will be displayed. By default, this parameter is set to 10 seconds
ACTION:
Consider increasing the value of the "DecryptionDelay" parameter in Datasources.xml and restart the web application server to take effect.
