BookmarkSubscribeRSS Feed
Lapis Lazuli | Level 10 woo
Lapis Lazuli | Level 10

We are running SAS (9.4 m5) MRM 7.3 application on Linux. while users are performing some tasks like creating model or so, they are getting 403 forbidden error. There is no error shown in sas mrm front end application (web app just hangs). f12 details while performing task shows below error. same task working fine on different environment with same settings.


Request URL:

request method: GET

StatusCode: 403 Forbidden

Referrer Policy: no-referrer-when-downgrade

Connection: Keep-Alive

Content Type: text/html; charset=iso-8859-1

Ammonite | Level 13 VDD
Ammonite | Level 13

HTTP 403 is a standard HTTP status code communicated to clients by an HTTP server to indicate that access to the requested URL by the client is Forbidden for some reason. The server understood the request, but will not fulfill it due to client related issues. There are a number of sub-status error codes that provide a more specific reason for responding with the 403 status code.

Lapis Lazuli | Level 10 woo
Lapis Lazuli | Level 10

one difference I sees from working vs non-working environment from f12 results is:


working fine environment

Response Headers

        Content-Type: application/json

not-working environment

       Content-Type: text/html; charset=iso-8859-1


do we need to change content type to application/json? if so how?

Obsidian | Level 7



Did you verified ModelRiskManagement Mid Tier logs for more details ?. Does screen shows any pop-up error message? 

suga badge.PNGThe SAS Users Group for Administrators (SUGA) is open to all SAS administrators and architects who install, update, manage or maintain a SAS deployment. 

Join SUGA 

CLI in SAS Viya

Learn how to install the SAS Viya CLI and a few commands you may find useful in this video by SAS’ Darrell Barton.

Find more tutorials on the SAS Users YouTube channel.

Discussion stats
  • 3 replies
  • 3 in conversation