We recently had a customer that was unable to do a final approval in Business Portal’s Requisition Management, a popular add-on to
First, check if there is a circular approval list where the final approver is also the creator of the requisition. Another similar issue would be if the final approver had two instances in the approval flow.
If this is the case, change the approval flow so each employee is only in the flow once.
This error is easily fixed by increasing the approvers spending limit or reassigning the requisition to a different approver with a higher limit.
Third, check if the requisition has more than 50 lines. Anything over 50 lines will result in an error. There needs to be a line added to the Web Config file that extends the time before the system times out. To do that,
- Make a backup of the current Web.config file
- Open the file in Notepad and do a search for MaxRequestLength
- You should find a line that states: <httpRuntime maxRequestLength=”51200”/>
- Change the line so that the timeout takes place after a longer period of time. Your new line should read: <httpRuntime maxRequestLength=’51200” executionTimeout=”300” />
The 300 equates to 300 seconds or five minutes.
- Reset IIS and try to do the final approval.