Skip to main content

We are using IFS Apps 10 + Update 11. We had a connection problem a few days ago and nobody was able to access Aurena (web interface) and Entreprise Explorer anymore. Usually restarting the services correct this kind of problem but it was not enough this time. We restarted the server as well but it took a long time and Windows completed some updates during that reboot. Once completed, the reboot lead to no result as well.

The error message returned when trying to access Aurena is: Error 404--Not Found

The error message returned when trying to start EE is:
    Below is a summary of the errors, details of these errors are listed later in the log.
    * Activation of https://ispd-agni1.irisco.local:48080/client/runtime/Ifs.Fnd.Explorer.application resulted in exception. Following failure messages were detected:
        + Downloading https://ispd-agni1.irisco.local:48080/client/runtime/Ifs.Fnd.Explorer.application did not succeed.
        + The remote server returned an error: (404) Not Found.

We realized that the server lacked disk space and we did some cleanup and add some extra space and reboot but nobody gained his access back after these steps. The database itself is accessible and we can query data from it using SQL Developer. We tried to reinstall the latest update (11) but the problem is still there. We tried to reconfigure IFS - as mentionned in other topics in this forum - but it failed with that error message:

2021-08-17 10:13:51 Configuring IFS Middleware Server 10.11.11.0
2021-08-17 10:13:51 Running ant script D:\ifs\APPS10\ifs_home\repository\server\install_fndmws.xml, target configure for component server
mjava]: Java Result: 1
Error in Ant-script: server\install_fndmws.xml
Reported error is: The following error occurred while executing this line:
D:\ifs\APPS10\ifs_home\repository\server\install_fndmws.xml:311: Failed to reconfigure middleware server. Error is: Error when reconfiguring IFS Middleware Domain: java.lang.NullPointerException

What can be attempted next?

My first thought is that since this started with “a connection problem a few days ago” and since then you are unable to get to the site address properly, maybe you have a network DNS issue or perhaps a firewall was changed (or turned on) that is preventing access to the server/port where the IFS Application Server is running.  It might even be a change to security settings in the web browser on all client PCs if they are no longer able to access (or can’t trust) the server, but that is perhaps less likely.

It does not look like a database issue to me, and that is backed up by the fact that you can connect to the DB directly.

The only other thing I can think is that the services might not be fully started for some reason.  If you go to the server and run the mws-svr command in the instance home directory and use the STATUS option for ALL targets, does it show all of the services as RUNNING?  I believe you should see 5 statuses in your noted version (for AdminServer, NodeManager, MainServer, IntegrationCluster, HttpServer).  One or more of these may not be in status ‘running’.  If they are not all running, use mws-svr to perform a STOP on all services, then check the STATUS to ensure they are all stopped, then run it again to START all services.  Sometimes it can take a couple of stops and starts to get things synchronized for some reason.

Nick

Hi @MicLabElmo,

We usually get the 404 error when trying to login when the deployments on Middleware Server are not active. 

I am assuming you have access to IFS Middleware Server Admin Console. Check whether any of the deployments are inactive and try to start them. 

 

If you are unable to activate any of these, then do the following. 

  1. Login to the Application Server host machine and navigate to following directory
\\<IFS_HOME>\wls_domain\<InstanceID>\servers\MainServer1\stage\
  1. Here you would find directories for each deployment deployed to MainServer1 like below.
  1.  If you go inside ifsapp-main folder for an example, you would find one or many folders with different timestamps as folder names. Go inside the folder with most recent date and check whether you can find a file with the extension “.ear” or “.war”. In this example, it would be ifsapp-main.ear.
  2. If the file is not there, then copy it from following folder and paste it to the correct folder. 
\\<IFS_HOME>\repository\server\apps\main
  1. Do this for all the deployments in both Main Server and Integration Server. Integration Server apps will be under “\\<IFS_HOME>\repository\server\apps\int” folder. If you have more than one Main Server or Int Server, do it for all of them. 
  2. Once this is done you can try to start the deployments again from IFS Middleware Server Admin Console. 
  3. If that doesn’t work, do a reconfiguration of the application server and see if the issue gets resolved. 

Since you have mentioned that there was a disk space issue on the application server host, it could be that the deployments were not copied properly to the stage directory due to space issues. 

Hope this helps!

The .ear and .war were missing, effectively. That was not enough to correct the problem so we had to reapply the latest update (11) over IFS to gain back the access to the Middleware Server Admin Console (we lost it a few days after Aurena and EE, maybe due to all the correction attempts done). After update 11, the .ear and .war files were erased again so we had to put them back a  second time and we were able to complete the procedure of Charith Epitawatta. We can now access Aurena et EE (as well as the Middleware Server Admin Console). Thank you for the help.

Terms & ConditionsCookie settings