|Applies To||RSA Product Set: Archer|
RSA Version/Condition: 6.x
|Issue||When trying to save a workflow (Creating a new one or save an already existing one) after clicking the save workflow button nothing happens. Normally you will find the processed saved pop up like below.|
However when you click save workflow you do not see this message. Then when you click save or apply for the application/questionnaire you receive the below error.
When getting this error run Browser Developer Tools (usually F12 key) before clicking the save or apply of the application and capture the Network traffic of the click of save.You will see the below and specifically note the PUT method 404 failure.
This does not provide much information on why it is failing so you should set up a trace to capture more information. Enabling a module in IIS called the Failed Request Tracing module can help get more details on why IIS isn't able to route certain requests. You can install it by following the steps below:
There's a step-by-step guide to setting up failed request tracing here: https://www.pluralsight.com/blog/it-ops/iis-7-troubleshooting
When the trace has been configured reproduce the error message so that it is captured. Navigate to the logging directory of the trace and you will see all of the files. Open the latest file and you will see the entry for the failed request. It will be like the below.
2017-02-20 07:45:42 127.0.0.1 PUT /RSAarcher/workpoint/rest/processes.svc/1003-CUST _dc=1487576742752&refresh=true&replace=false&checkSyntax= 80 - 127.0.0.1 Mozilla/5.0+(Windows+NT+6.3;+WOW64;+Trident/7.0;+rv:11.0)+like+Gecko http://localhost/RSAarcher/apps/ArcherAWF/AppClientArchitectDesktop/Home.aspx?
The end of the entry you will see 404 6 0 0 and this is specifically Verb denied. When request filtering blocks an HTTP request because of a denied HTTP verb, IIS will return an HTTP 404 error to the client and log the following HTTP status with a unique substatus that identifies the reason that the request was denied.
|Cause||This issue was caused due to there being server hardening in place which had been configured to only allow certain verbs.|
The configuration was the same as below.
|Resolution||As you can see from the above image, the PUT verb has not been added to the list of allowed verbs. When restricting verbs on the server you will need to add 4 verbs so that Archer functions as expected. You need to have the below verbs with allowed status:|
If you don't wish to list all the verbs within the HTTP verbs tab, you can edit feature settings.
Look at the second check box. If it is checked, no need to add the Verbs in HTTP Verbs tab. If it is unchecked, then we have to add these in HTTP Verbs tab.
If the above doesn't resolve the issue. Make sure that WebDav publishing is disabled on the server level.
The steps to do this can be found in KB000032507