Any time that a change is made to the compute server configuration, the affected compute servers and excel servers should be tested to make sure they will be ‘active’ and ready for use within EASA.
To test compute servers, go to:
As noted at the bottom of the page, the testing process may take several minutes depending on the traffic on your network and the number of Compute Servers being tested.
After the process is complete, all Compute Servers should have a status of ‘active’ in the table of Compute Servers on the current page.
If any of your Compute Servers has a status of ‘inactive’, you will need to view the results of the testing for that Compute Server by selecting the inactive link in the Status column.
Eight (8) distinct tests are run on each Compute Server, and all eight tests must ‘pass’ for to be made made ‘active’. These tests are as follows:
If any of these tests fails, then error messages should appear next to the ‘Standard Error -’ lines on the Test Results page.
Note: An error message of only ‘Process finished in *.* (s)’, where *.* will be a number, is indicative of a test passing and is not cause for concern.
Typically, error messages on the Test Results page will point to problems with the Compute Server’s SERVER PROCESSING object and its parameter settings. Another common problem is lack of access permission in the Working Directory, be it a shared folder for a Windows Compute Server or a network drive for a UNIX Compute Server. Please ensure that Read and Write permissions are granted in the Working Directory and all subdirectories to the UserIDs being used in the server processing.
If you are unable to determine the cause of failures in your Compute Server tests, please e-mail the contents of the Test Results page to your designated local EASA support office. This action can be accomplished by selecting Send → Page by E-mail under the File menu in Internet Explorer.
If changes are made in the Compute Server configuration that affect an Excel Server, this Excel Server will need to be updated, tested, and in some cases restarted. To update and test an Excel Server go to:
After the process is complete, all of your Excel Servers should have a status of ‘active’ in the table.
If any of your Excel servers has a status of ‘inactive’, you will need to look for causes within the log file for that Excel Server by selecting the inactive link in the Status column.
One possible way to fix an ‘inactive’ Excel Server is to use the Restart button. Also, the Restart button needs to be used when the Visibility parameter has been changed in the compute server configuration.
If you are unable to determine the cause of failures in your Excel Server tests, please e-mail the contents of the Log File for Excel Server page to your designated local EASA support office or firstname.lastname@example.org.