Problem Note 65989: An error occurs when you use a model from SAS® Model Manager with SAS® Event Stream Processing
When you use SAS® Event Stream Processing Studio, you might encounter the following error when it deals with a model from SAS Model Manager.
[5037] The SAS Model Manager ASTORE code could not be loaded onto the ESP server because the ESP server was not able to add object to the SAS Micro Analytic Service store
This issue is caused by the corresponding champion model in a model repository that does not have its ASTORE code copied to a preconfigured directory. Typically, that directory is at /opt/sas/viya/config/data/modelsvr/astore.
You can examine this champion model by following these steps:
- Open the model.
- Click the Files tab.
- Open the AstoreMetadata.json file, which contains code similar to the following:
[
{
"name": "_1LA3UXOR00CO31HZUKMS9RF673",
"caslib": "ModelStore",
"uri":
"/dataTables/dataSources/cas~fs~cas-shared-default~fs~ModelStore/tables/_1LA3UXO
R00CO31HZUKMS9RF673",
"key": "FE93CC8BD5CEA0FBD1C2D4763785B9FC403DBB83"
}
]
Instead, it should code that looks similar to this:
[
{
"name": "_1LA3UXOR00CO31HZUKMS9RF673",
"uri":
"/dataTables/dataSources/cas~fs~cas-shared-default~fs~ModelStore/tables/_1LA3UXO
R00CO31HZUKMS9RF673",
"key": "FE93CC8BD5CEA0FBD1C2D4763785B9FC403DBB83",
"caslib": "ModelStore",
"location":
"file:///models/astores/viya/_1LA3UXOR00CO31HZUKMS9RF673.astore",
"host": "fall.edmt.sashq-d.openstack.sas.com",
"fullPath":
"/opt/sas/viya/config/data/modelsvr/astore/_1LA3UXOR00CO31HZUKMS9RF673.astore",
"state": "success"
}
]
To work around this issue, return to SAS Model Manager, manually clear the champion model flag, and reset that model as a champion model.
Click the Hot Fix tab in this note to access the hot fix for this issue.
Operating System and Release Information
SAS System | SAS Model Manager (on SAS Viya) | Linux for x64 | 15.3 | | Viya | |
*
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.
Type: | Problem Note |
Priority: | high |
Date Modified: | 2020-05-19 15:15:28 |
Date Created: | 2020-05-14 11:33:06 |