This SAS Note is part of a series of SAS Notes about diagnosing and resolving issues with SAS Micro Analytic Service (MAS) on SAS Viya 3.5 and SAS Viya. For additional information, see the related SAS Notes below:
- SAS Note 70241, “Using logging to diagnose and resolve issues with SAS® Micro Analytic Service (MAS) on SAS® Viya® 3.5 and SAS® Viya®”
- SAS Note 70229, “Database considerations for diagnosing and resolving issues with SAS® Micro Analytic Service on SAS® Viya® 3.5 and SAS® Viya®”
- SAS Note 70242, “Performance considerations for diagnosing and resolving issues with SAS® Micro Analytic Service on SAS® Viya® 3.5 and SAS® Viya®”
Note: Before opening a track with SAS Technical Support, answer the questions that are listed below. These responses are needed in order to report a problem with MAS.
When Does the Issue Occur?
There are two primary use cases for MAS--publishing and executing.
If the issue occurs when publishing to MAS, ask yourself the following questions:
What are you publishing from?
- SAS® Model Studio
- SAS® Model Manager
- SAS® Intelligent Decisioning
- a different application
Have you ever been able to publish anything to MAS successfully (either from the current application or any other application)?
Have you ever been able to publish this specific module to MAS successfully?
Are you republishing a module when the issue occurs, or does the issue occur the first time that you publish?
How do you know that something has gone wrong with the publishing to MAS? Is an error message displayed somewhere?
If the issue occurs when executing a module that has already been published to MAS, ask yourself the following questions:
How are you executing the module?
- Postman
- the cURL command
- SAS® Event Stream Processing (ESP)
- something else
What is the module name that is being executed?
What does this module do?
Does this module rely on any external resources (for example, a database or Python)?
When was this module published?
What application did you use to publish this module?
Has this module ever been executed successfully?
What happens if you try to execute a simple module that is published to MAS – a module that doesn’t require external resources (such as a database or Python)?
How do you know that something has gone wrong with the execution of the module?
If the issue with MAS does not occur when publishing or executing, ask yourself the following question:
What is the issue and when does it occur?
What Happens Once the Issue Occurs?
What happens if you try the action again? Does the same issue occur or is the behavior intermittent? By default, MAS has four worker threads. It is possible that some of these worker threads are problematic while others are not. This issue is one reason why it is important to try the problematic action several times in order to understand the issue more fully.
After the issue occurs, ask yourself the following questions:
What happens if you try to access the following URL? https://<server>/microanalyticScore/modules
- Is any output returned to the browser? If so, provide the results.
- Does the browser spin while attempting to access this URL? If so, provide a screenshot.
- Does the browser display an error? If so, provide a screenshot.
Is there anything that you can do to correct the behavior?
What happens if you restart MAS? Is the issue resolved after restarting MAS, even if just temporarily until the issue happens again?
Is MAS Connected to a Database?
If MAS is connected to a database, ask yourself the following questions:
What are the details of the database?
What is the connection string that was used to connect to the database as configured in SAS Environment Manager?
What is the configuration of the following configuration properties within SAS Environment Manager:
- dbconnretries
- dbconnretryintervalseconds
- connectioncheckstatement
Does the Database Administrator have any observations about what occurs from the database-server side at the time of the issue?
- Are the expected tables being accessed?
- Are the expected indices being used to return results?
Operating System and Release Information
SAS System | SAS Micro Analytic Service | Linux for x64 | Viya platform | |
*
For software releases that are not yet generally available, the Fixed
Release is the software release in which the problem is planned to be
fixed.