Solved

Unable to connect to IFS 10 - Due to Error 500

  • 5 April 2024
  • 2 replies
  • 69 views
R
Rank
Badge +4

Hi Community,

 

After IFS Installation I'm getting this error message. Environment hosted in Azure. 

Also, I'm thinking that this issue is similar to this Unable to connect to IFS 10 - Due to Error 500 | IFS Community

 

There is no deployments failure

 

And no issues with JDBC connection string.

 

Any idea about this issue.?

 

Ifs.Fnd.FndSystemException: Unexpected error while calling server method ClientApplication/IdentifyCurrentUser

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.Interactive.FndLoginDialog.AuthenticateCredentials(FndLoginCredentials loginCreds) ---> Ifs.Fnd.FndSystemException: 500
at Ifs.Fnd.AccessProvider.FndConnection.CallGetResponse(String intface, String operation, FndRequestContext requestContext, FndManualDecisionCollection decisions, Byte[] requestHeaderBytes, Byte[] requestBodyBytes, FndApfAsyncInvoke asyncInvokeHandle, Boolean integrationGateway)
at Ifs.Fnd.AccessProvider.FndConnection.InvokeGetResponse(String intface, String operation, FndRequestContext requestContext, FndManualDecisionCollection decisions, Byte[] 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 ---

icon

Best answer by Rusiiiru 5 April 2024, 21:58

View original

2 replies

E
Rank
Userlevel 4
Badge +7

This error can have varying causes.  The 500 error message at login is a generic message.

Since you have already checked on the deployments and found them to be “green” you could also run the mws-svr script which is found at the root directory of the middleware home of the host server where your application’s middleware is deployed.  Be sure to run it as administrator.  You’d use the same user credential as what you’ve used to log into the IFS Admin Console to run this script (you’ll be prompted for that user & password).  Run this script with the STATUS option and ask for ALL when prompted.

If this script replies and says “RUNNING” for all mws servers then you will have eliminated another possible cause of the error.  But if any of the server responses show a status other than RUNNING you may need to restart or even reconfigure the mws.  Restart can also be done by using the same mws-svr.exe script.  Reconfigure is done with the IFS Installer application (found at the same location in the mws home as mws-svr.exe).

Let us know how you are fare with these steps.

Eugene Wager - IFS Unified Support

R
Rank
Badge +4

Hi,

This issue resolved after adding IFS Application URL add to trusted site and untick Enable Protection Mode.

 

Reply


Terms & ConditionsCookie settings