This SAS KB article contains structured instructions for diagnosing and resolving problems in SAS Micro Analytic Service on SAS Viya 3.5. The information in this article will help you define the problem clearly, collect essential diagnostic data, and identify the next steps toward resolution. 

The sections below outline standard data collection practices along with key questions to help define and scope the problem effectively. Establishing a detailed and complete problem description early in the investigation process can significantly reduce time to resolution. 

Note: This guide is designed for SAS Micro Analytic Service on SAS Viya 3.5. For SAS Micro Analytic Service on the SAS^® Viya^® platform, see SAS KB0046156.

Define the Problem

Context and Observations

• What were you doing when the problem first occurred? For example, were you publishing to SAS Micro Analytic Service or executing a module within SAS Micro Analytic Service?
• If the problem occurs when publishing to SAS Micro Analytic Service, which application are you publishing from?
• If the problem occurs when executing a module within SAS Micro Analytic Service, what do you use to execute the module?
• How many modules are published to SAS Micro Analytic Service?
• Which version of SAS Viya 3.5 do you use?

Error or Unexpected Behavior

• Was an error message displayed?
  • If yes, provide the full message and a screenshot if possible.
  • If no error was displayed, what unexpected behavior occurred?
• What occurred versus what did you expect? Provide a screenshot if possible.

Steps to Reproduce

• What sequence of steps led to the problem?
• Can you reproduce the issue consistently?

Scope of Impact

• Does this issue occur for all models or decisions or only specific models or decisions?
  • Have you tested with other models or decisions?
  • Have you tested with a simple model or decision?
• Does this issue affect all users or only certain users? If the issue affects only a certain user, have other users attempted the same action?

History and Changes

• Has this worked previously? If so, when was it last successful?
• Were there any recent changes? (For example, deployments, updates, configuration changes, data changes, or changes to models, decisions, or modules.)

Diagnostic Data to Collect

To support resolution, collect the following diagnostic data at the time the problem occurs. 

• logs from the following microservices at the time of the issue:

• • Publishing to SAS Micro Analytic Service:
    microanalyticscore
    modelpublish

• • Executing within SAS Micro Analytic Service:
    microanalyticscore

• screenshots of observations, errors, or unexpected results

You should provide these artifacts in addition to a clear problem description. 

Optional or Additional Data

• If SAS Micro Analytic Service is connected to a database, provide the connectionstring that is configured within SAS^® Environment Manager to make that connection. 

Providing complete diagnostic data in advance can significantly reduce time to resolution.

Next Steps: Navigate Resolution Paths

Once you clearly define the problem and collect diagnostic data, engage SAS Technical Support for further assistance. Provide the detailed and complete problem description along with the prescribed diagnostic data.