Skip to main content

We changed the connection string on the MWS (using middleware server admin console) as we are hosting the database on another server. Verified the connection and can run ifs.fnd_explorer.exe on the MWS to connect to the database with no issues. We copy the runtime folder (E:\IFS\repository\client\runtime) to a terminal server where users will run the application. The application fails to launch and returns the error ‘No authenticate header from the server’. So the application will run on MWS but not on the terminal server. This worked well until we changed the connection string. I have restarted both the database and MWS as well as running a reconfigure.

 

Error

Ifs.Fnd.FndSystemException: Unexpected error while calling server method AccessPlsql/Invoke

   at Ifs.Fnd.AccessProvider.FndConnection.InvokeInternal(Object requestBody, Object responseBody, String intface, String operation, FndRequestContext requestContext, FndManualDecisionCollection decisions, Boolean forcedSync, Boolean integrationGateway)
   at Ifs.Fnd.AccessProvider.FndConnection.InvokeInternal(String intface, String operation, Object requestBody, Object responseBody, FndRequestContext requestContext, Boolean forcedSync, Boolean integrationGateway)
   at Ifs.Fnd.AccessProvider.PLSQL.FndPLSQLCommandCollection.Invoke()
   at Ifs.Fnd.AccessProvider.PLSQL.FndPLSQLCommand.ExecuteNonQuery()
   at Ifs.Fnd.AccessProvider.PLSQL.FndPLSQLSelectCommand.ExecuteReader(String recordType, Int32 fetchsize)
   at Ifs.Fnd.AccessProvider.PLSQL.FndPLSQLSelectCommand.ExecuteReader()
   at Ifs.Fnd.AccessProvider.Interactive.FndLoginDialog.checkLanguage(FndLoginCredentials loginCreds)
   at Ifs.Fnd.AccessProvider.Interactive.FndLoginDialog.AuthenticateCredentials(FndLoginCredentials loginCreds) ---> Ifs.Fnd.FndSystemException: No authenticate header from the server
   at Ifs.Fnd.AccessProvider.FndConnection.CallGetResponse(String intface, String operation, FndRequestContext requestContext, FndManualDecisionCollection decisions, Bytel] requestHeaderBytes, Bytee] requestBodyBytes, FndApfAsyncInvoke asyncInvokeHandle, Boolean integrationGateway)
   at Ifs.Fnd.AccessProvider.FndConnection.InvokeGetResponse(String intface, String operation, FndRequestContext requestContext, FndManualDecisionCollection decisions, Byteo] requestHeaderBytes, Byte ] requestBodyBytes, Boolean& abandoned, Boolean forcedSync, Boolean integrationGateway)
   at Ifs.Fnd.AccessProvider.FndConnection.InvokeInternal(Object requestBody, Object responseBody, String intface, String operation, FndRequestContext requestContext, FndManualDecisionCollection decisions, Boolean forcedSync, Boolean integrationGateway)
   --- End of inner exception stack trace ---

 

 

We are using nginx as a reverse proxy and get this same error.  Did you ever find out what causes it or how to fix it?

For us this seemed to be caused by the fact that we were temporarily using a self-sign certificate. To resolve we imported the the security certificate from MWS Home\security\certs via Google Chrome security settings on both the application server and terminal server. This was a temporary solution as we were working on obtaining an SSL wildcard certificate for our domain. We have since configured SSL passthrough on the MWS using this wildcard certificate 

Reply


Terms & ConditionsCookie settings