Smarts | EDAA REST call fails with 500 - Internal Server Error
Article ID: 331905
Updated On:
Products
VMware Smart Assurance
Issue/Introduction
Symptoms:
The following error is present in the Smarts-edaa.log
2018-01-09 06:39:00,635 ERROR MsaController http-nio-8080-exec-2 processMsaRequestException Processing - Msa Internal Se
rver Error. Reason: key=com.emc.msa.dmt.MsaDMTDataSource.ACTION_NOT_ALLOWED args=[ 'acknowledge' ]. Caused by: Internal
MSA error
The following error is present in the Smarts-edaa.log
rver Error. Reason: key=com.emc.msa.dmt.MsaDMTDataSource.ACTION_NOT_ALLOWED args=[ 'acknowledge' ]. Caused by: Internal
MSA error
Environment
VMware Smart Assurance - SMARTS
Cause
In looking through our code base SAM DIR/tomcat/webapps/smarts-edaa/WEB-INF/grails-app/i18n/DMT.properties
That error has the following additional information:
com.emc.msa.dmt.MsaDMTDataSource.ACTION_NOT_ALLOWED=Action {0} is not allowed for the user profile
This indicates that the action is not allowed by the user profile.
That error has the following additional information:
com.emc.msa.dmt.MsaDMTDataSource.ACTION_NOT_ALLOWED=Action {0} is not allowed for the user profile
This indicates that the action is not allowed by the user profile.
Resolution
In this instance the Watch4Net (W4N) user was using a profile that did not have the correct privileges as indicated by the full error found in the code.
To correct the issue please change the W4N profile to an Admin profile.
To correct the issue please change the W4N profile to an Admin profile.
Feedback
Yes
No
Powered by
