toleary

Blueprint 4.1 Server Configuration Tool fails for the Tracker Web Service and/ EDI Web Service components with the following error: 403: Forbidden. Re-applying the Server Configuration settings does not fix the problem, what do I do now?

Blog Post created by toleary on Aug 8, 2013

OS:

Windows Server 2008, Windows Server 2008 x64

Symptom:

The 'Tracker Web Service' and/or 'EDI Web Service' health tests fail with a '403: Forbidden' error. Trackers can fail to send job data and terminals can fail to login due to this error. Re-applying the Server Configuration settings does not fix the problem.

 

Possible Cause:

This can be caused by certain permission settings being modified manually using the IIS 7 management console. Specifically, changing the 'Feature Permissions' of the 'Handler Mappings' for a Blueprint virtual directory and removing either the 'Read' or 'Script' permissions will cause this.

If the relevant 'web.config' file (located in the Blueprint 'Services\BediService' and 'Services\TrackerService' subdirectories) contains the following section:

<system.webServer>

...

</system.webServer>

Then this indicates manual configuration changes have been made.

 

 

 

Fix:

Either:

1) Reverse the manual changes made.

2) Remove the entire <system.webServer> section from the relevant 'web.config' file.

Outcomes