This week, a user came into my practice. He suffers because he is not able to import a specific .twx-file into two of his Process Center environments whereas (very curious) the same .twx-file can be imported on others.
When selecting the import, as usual the spinner with text “Uploading file…” is shown. However, after a while the window simply closes without any process application important (cannot be found).
Furthermore, the user explains that the affected Process Center environments are connected to a web server and that the .twx-file is quite big.
My first consideration was: The .twx-file should be fine since it can be successfully imported into other environments.
Then, let’s take a look at the SystemOut.log: Nothing. Nothing significant happens…
Well, the .twx-file should be fine and the logs show nothing interesting, so how to follow up?
As we know, there should some communication going on based on HTTP. With this background, we might either try to trace or capture the network traffic.
So I requested a network traffic capture (there are several ways like using Fiddler, Browser etc.).
Cool, the network traffic capture seems to give us a hit – a 404 HTTP response:
HTTP/1.1 404 Not Found
Content-Type: text/html; charset=utf-8
Title: IIS 7.5 Detailed Error - 404.13 - Not Found
Header: Server Error in Application "dummyApplication"
Server version: Internet Information Services 7.5
HTTP Error 404.13 - Not Found
The request filtering module is configured to deny a request that exceeds the request content length.
Error Code: 0x00000000
As you can see from the network traffic browser trace, request filtering (The request filtering module is configured to deny a request that exceeds the request content length.) is configured on the Web server to deny the request because the content length exceeds the configured value.
This is a web server security feature. Do not change this feature unless the scope of the change is fully understood, as Microsoft said. You can configure the Internet Information Server (IIS) to reject requests whose content length is greater than specified value.
If the request's content length is greater than the configured length, this error is returned. If the content length requires an increase, modify the configuration/system.webServer/security/requestFiltering/requestLimits@maxAllowedContentLength setting.
The following resources give you additional guidance where and how you can change configuration to solve that kind of problem:
(although for another product, the steps to resolution should work for BPM as well).
In our specific case customer used the Microsoft IIS, and after correcting the settings for the maxAllowedContentLength to a value > 50000000 because of
problem went away.
And if this does not help, take two of these and call me in the morning.
Your Dr. Debug