Resolving Problems with the Service Architecture

Check the logs produced by the service architecture for detailed information about the error. The service architecture logs are stored in the /emi-framework/Logs directory.

Select ManagePlug-in Manager. Use the Plug-in Manager table to verify that the sas - servers plugin is installed. If the plugin is not installed, contact SAS Technical Support.

Select ManagePlug-in Manager. Use the Plug-in Manager table to verify that the emi-framework plugin is installed. If the plugin is not installed, contact SAS Technical Support.

Select ManageList Roles and then select the Super User Role entry. Check to see whether the user entry is listed in the Assigned User table as a member of the Super User Role. If it is not, select Add to List to open the Assign Users to Role page, where you can add the user to the role.

Confirm that the SAS Environment Manager agent is running properly on both the local and host machines. If an agent is not running properly, restart the agent. Go to < levelroot > /Web/SASEnvironmentManager/ag ent - 5.8.8 - EE/bin and issue the command hq - agent.(sh/bat) restart.

The local copy of the [scriptname] script has been changed, either because it has been edited or because it is corrupt. If the script was edited, remove the edits. If the script has been corrupted, contact SAS Contact Technical Support for a replacement script.

The SAS Metadata Server did not response to a ping request to its IP address. To restart the server, run the command sas.servers start or MetadataServers. (sh/bat).

An error was detected in one of the ETL processes (ACM or APM). Review the log messages in the emi-framework/Logs directory to determine the error and the specific ETL process that is reporting the error. Possible causes include inadequate storage, permissions errors, or the SAS Environment Manager server or SAS Metadata server not running. After you have fixed the error, run either master_acm_etl .(sh/ bat) or master_apm_etl.(sh/bat) to verify that the error has been corrected.

You attempted to enable APM ETL without having first initialized it. See Enabling and Initializing the APM ETL for the complete procedure.

An error occurred when enabling the APM ARM. Run the command bin/apm_i nit.(sh/bat) -f.

For multi-machine deployments, you must edit the file emi-framework/Conf/log_definitions_json and specify the local paths to mount points for the SAS levelroot directories on the remote machines.

The log_centralize.sh script cannot gather log archives from remote hosts if the SAS Deployment Agent on the remote host is running in secured mode. To collect the logs, you can either use a method such as file mounts or manual transfer, or you can run SAS Deployment Agent in unsecured mode.

To run the SAS Deployment Agent without security, follow these steps:

This message appears if the processes for log collection and log processing encounter a partial log from a different SAS deployment that is missing header information. It also appears if you run the command emi_init – resetDB – f without stopping and restarting the SAS Application server. To re-create the rolling logs and the log headers, restart the SAS Application server.

If you have never previously enabled or initialized the service architecture in your deployment, you can ignore this message. Run the command emi_init.sh --status to check whether the service architecture has been enabled.

If you previously enabled the service architecture in the deployment that you are upgrading and the deployment contains multiple machines, an upgrade-in-place of the service architecture will fail. To resolve this error, first complete the upgrade process on all machines in your deployment. After you have upgraded all the machines, use the ugipInit command to upgrade the service architecture. See Updating a Modified Data Mart By Using ugipInit.

If neither of these conditions apply, review the log files identified in the UpdateInstructions.html message to determine the cause of the error. Also review the files ugipInit_{TimeStamp}.log and ugipInit_{TimeStamp}.sas.log, which are located in the emi-framework/Logs directory.

The SAS Environment Manager Agent must be configured because validate.sh relies on class org.apache.http.conn.HttpHostConnectException, which is provided by the SAS Environment Manager Agent. Verify that the Environment Manager Agent is configured and <levelroot>/Web/SASEnvironmentManager/agent-5.8.8–EE exists.