Clarity Task Error - Maximum Request Length Exceeded

Update:  10/1/2024 with preferred method

Error
That error means that the file is too large to send back to the host via http so the config file needs to be modified to allow for larger file sizes.

Task Error
There was an exception running the extensions specified in the config file. ---> Maximum request length exceeded.

If you exceed the default maximum file size which is 400000 you will need to fix a config file to accommodate processing larger file sizes, or enable uploading in chunks (preferred method).



Resolution Options

Preferred Method 

On the Task Server

Enable Upload in Chunks

Make sure the Clarity Task Server is fully updated

Log onto the Task Server as the designated Clarity Account.

  1. Exit the Clarity Task Tray by right clicking on the Clarity icon in the Windows Task Tray and Exit
  2. Through File Explorer Browse to C:\ProgramData\IMAGINiT Technologies\Clarity Task Server 202#\ClarityTaskService.config
  3. Right click on ClarityTaskService.config and copy, then paste into the same folder.  Rename the extension to .ORIG as shown below
  4. Edit the ClarityTaskService.config in Notepad
  5. Toward the bottom of the file, locate the line:
    <add key="UploadFilesInChunks" value="False" />
  6. Change its value to “True”.
  7. Save the file
    1. If you get an error saving the file, save it to the desktop
    2. Make sure the save dialog shows All Files it is still seen in the screenshot and Append extension is not toggled, then save
  8. Move the file back into the original folder and overwrite
  9. Restart the Task Server Tray from the desktop icon Clarity Task Tray for Revit
  10. From the desktop icon "Launch Task Server" for any version of Revit and make sure it picks up tasks

Alternate Methods on Host 

You can modify a config file to allow for larger file sizes.

To change the Config File

1.  On the Host Server, browse to the following folder:  C:\inetpub\wwwroot\CentralWebServices

2.  Make a copy of the Web.config file and rename it to Web.orig in case you ever need to revert back to the original file.

3.  Modify the:  Web.config

4.  Change the highlighted value below between the "400000".  Please make sure that you make the max request length high enough...perhaps go up to 800000

Example

   <add key="AllowOverrideTaskParams" value="No" />

  </appSettings>

  <!-- specific config for allowing large uploads to the Task Webservice -->

      <system.web>

      <!-- max Request Length, in KB -->

      <httpRuntime maxRequestLength="800000" executionTimeout="600" />

    </system.web>

   <!--

Screenshot of file

image-1732126561075.png

5.  Save the file, if you get an error about saving to the original folder, do a save as to the desktop.  Make sure to match the settings below before saving. 

We do not want anything appended to the end, so make sure that is not checked.

6.  Drag the file from the desktop back into the original folder and overwrite.

Follow
Was this article helpful?
1 out of 1 found this helpful

1 reply

Newest Oldest

In reference to the suggestion to change the Artifacts path to a UNC path, are you saying that if we use a path such as \\<host server>\etc. that there should be no file size limitation and that we don't need to edit the config file?

Comment

While true, I feel that setting the task server artifact path to a UNC path (so that it matches the host) - it creates some problems additionally.

Let me see if there's a newer version of this note: I think the better answer is modify the task server configuration file to use a chunked file upload.

Reply