Troubleshooting installation and configuration deployment errors in SAS® Risk Governance Framework 7.3


This KB article explains what information, log files, and so on to collect and send to SAS Technical Support to troubleshoot installation and configuration errors in SAS Risk Governance Framework 7.3.

Step 1: Collect Information about Your Deployed SAS® Solutions and SAS® Code Level

Collect the information about your deployed SAS® solutions and current SAS code level for further review by executing the following SETINIT procedure in your Base SAS® software:

proc setinit;
run;

To collect additional information (software releases, installed hot fixes, and so on), see SAS KB0036131, "Using the ViewRegistry Report and other methods to determine the SAS® 9.2 and later software releases and hot fixes that are installed."

Step 2: Include a Problem Description

Include a description of the general task that you are trying to accomplish, your role and capabilities, and what has happened during the SAS session. Also, provide answers to the following questions:

Step 3: Collect Log and Configuration Files

To troubleshoot unexpected behavior in the SAS Risk Governance Framework installation and configuration task, collect the following logs and configuration files, which contain data that is useful diagnosing problems: 

SAS® Deployment Wizard or SAS® Deployment Manager log files from machines with the failing SAS® tier:

Note: If the error occurs during the startMidtierServers, load-content, or update-content stages of the installation wizard, you also need to collect any SAS 9.4 Web Server and SAS® Web Application Server logs and files.

Middle Tier: SAS® Risk Governance Framework web application log files:

Execute the code in the Code section of this article to extract the software and server-component metadata. This task is valid only if the configuration task for the metadata-server component completes successfully.

Note: You can retrieve many of the files that are listed above by running the log-sweeper tool that is described in SAS Note 54813, "Using the PDATool for automated log, configuration data collection, and relevant health-check analysis for the deployed SAS® 9.4 environment services." Before you send the package of files to Technical Support, you must inventory the sweeper's output and ensure that ALL files and logs that are listed above are found in the package. 

Code

Execute the following code to extract the metadata properties for the SAS Infrastructure for Risk Management application. Update the MetaServer and MetaPass parameters in the file according to your SAS environment before you execute the code.

/*%put Current path is %curdir;*/
%macro slash;
%global slash;
%*** If the program is run on Windows;
%if (&sysscp = WIN) %then %do;
%let slash = %str(\);
%end;
%*** If the program is run on UNIX;
%else %do;
%let slash = %str(/);
%end;
%mend;
%slash;


/* create dir for files */
options dlcreatedir;
libname makeme ".&slash.analysisresults&slash.IRMConfig";


/* define input and output xml files for PROC METADATA */
filename INXML ".&slash.analysisresults&slash.IRMConfig&slash.IRMMetaDataInput.xml" LRECL=256;
filename OUTXML ".&slash.analysisresults&slash.IRMConfig&slash.IRMMetaDataPropsResult.xml" lrecl=1024 encoding="UTF-8";

data _null_;
   file INXML;
   input;
   put _infile_;
   datalines;
<GetMetadataObjects>
<Reposid>$METAREPOSITORY</Reposid>
<Type>SoftwareComponent</Type>
<Objects/>
<NS>SAS</NS>
<Flags>388</Flags>
<Options>
<XMLSelect Search="@Name='IRM Mid-Tier Server' or @Name='SAS Application Infrastructure'"/>
<Templates>
<SoftwareComponent Id="" Name="" ClassIdentifier="" Desc="" ProductName="" SoftwareVersion="">
<PropertySets/>
</SoftwareComponent>
<PropertySet Id="" Name="" >
<SetProperties/>
</PropertySet>
<Property Id="" PropertyName="" Name="" DefaultValue=""/>
</Templates>
</Options>
</GetMetadataObjects>
;;
run;

PROC METADATA
metaserver=""
metaport=
metauser=""
metapass=""
METAREPOSITORY="Foundation"
PROTOCOL=BRIDGE
IN=INXML
OUT=OUTXML;
RUN;

/********************************************************************************
  Create the Map file.
  Libref has to be the same as the Fileref for the XML output from PROC METADATA
********************************************************************************/
filename MAP temp lrecl=1024 encoding="UTF-8";
libname OUTXML xmlv2 xmlmap=MAP automap=replace;