Sitecore Bulk Upload from the item itself - HTTP/2 error Resolution

-

We need to allow bulk image uploads directly from the Sitecore item rather than requiring users to navigate to the media library to upload images one by one or as a zip file. This feature enables the content author to be productive without going to the media library to upload images.

The image upload functionality works well when the content author uploads one or two images simultaneously, even when using a zip file. However, when attempting to upload a larger number of images, we encounter the following error




13380 09:38:06 ERROR Index was out of range. Must be non-negative and less than the size of the collection.

Parameter name: index
Exception: System.ArgumentOutOfRangeException
Message: Index was out of range. Must be non-negative and less than the size of the collection.
Parameter name: index
Source: mscorlib
at System.Collections.ArrayList.get_Item(Int32 index)
at System.Web.HttpFileCollection.Get(Int32 index)
at System.Web.HttpFileCollectionWrapper.get_Item(Int32 index)
at Sitecore.Controllers.MediaController.DoUpload(String database, String destinationUrl, Language itemLanguage)
at Sitecore.Controllers.MediaController.Upload(String database, String destinationUrl, String itemLanguage)


When we uploaded the same batch of images using the media library, all the images were successfully uploaded without any errors. 

It's important to note that we have set a maximum image size limit of 30MB for content authors. This means that a content author can upload any number of images, provided each image is 30MB or smaller.

We have configured the settings to allow for a maximum size of 30MB per image.


<setting name="Media.MaxSizeInDatabase" value="30MB" />

<requestLimits maxAllowedContentLength="524288000" />

<httpRuntime targetFramework="4.8" maxRequestLength="512000" executionTimeout="600" enableKernelOutputCache="false" relaxedUrlToFileSystemMapping="false" requestValidationMode="4.0" enableVersionHeader="false" requestValidationType="Sitecore.Web.RequestValidators.SitecoreBackendRequestValidator, Sitecore.Kernel" />

While uploading some of the images got uploaded and some got stuck and after some time it returned the error mentioned above.



We have tried various approaches and solutions but at last, we figured out the issue with the help of Sitecore Support.

The main reason for this issue is because of the HTTP/2 protocol error while uploading the images.

Solution:

To resolve this issue, we disabled HTTP/2 in IIS by following these steps.

  • Open Internet Information Services (IIS) Manager.
  • Select the CM instance of the Sitecore instance.
  • Click on the “Bindings” on the right panel.
  • Double-click on the site binding.
  • Tick “Disable HTTP/2”.
  • Click on “OK”.
  • Click on the server on the left panel.
  • Click on “Stop”.
  • Wait for a few seconds and then click on “Start”.



Let's learn and grow together, happy programming ðŸ˜Š






Comments

Post a Comment

Popular posts from this blog

Custom Item Url and resolving the item in Sitecore - Buckets

-
Image
I have a situation to update the Item URL to be SEO friendly as my items in content tree looks like below. In the above image in order to resolve the item, Sitecore will find the item from the below URL http://domainname/en/dine/nv/chicken but I need to form a URL that is more SEO friendly like http://domainname/en/chicken In Sitecore by Out of box, we can achieve this by using Aliases , we can create an Aliases under System à Aliases and in the Linked Item field select the target item. But this is very tedious as we need to go to every item in the content tree and create Aliases, instead of that we will be going to do it programmatically using custom pipelines. ·          Link Provider (Provides the custom URL for the item based on the templates) ·          Item Resolver (Resolves the item based on the custom URL generated by CustomLinkProvider , that we going to create later. Sitecore could not resolve the item in the specified path in the content tree
Read more

Exploring Sitecore XM Cloud Forms: A Comprehensive Overview

-
Image
  The most awaited news came from Sitecore about the release of XM Cloud Forms.  Previously Sitecore enthusiasts / Marketers used different ways of forms implementation in Sitecore to reach the target customers like WFFM (Web Form For Marketers) Sitecore Forms Embeddable Forms Framework(EFF) XM Cloud Form is the latest addition by Sitecore and especially used to create Forms on XM Cloud pages. It will only work with the latest version of Sitecore JSS (21.6) Note:  I have tried to use XM Cloud Forms in my local docker setup by cloning the starter   repo , but I couldn't see the option of Forms in the XM Cloud dashboard to get started. Lets explore together on the features of Forms. Similar to Sitecore Components, we can navigate to  https://forms.sitecorecloud.io/  to start creating the Forms There are 2 important tabs in creating Sitecore Forms  Forms  Webhook(for triggering the submit action) We can create, modify, delete, and activate the form from the Form tab.  Once the form is
Read more

Sitecore Custom Rule (Action and Condition)

-
Image
I have a situation to create a custom Sitecore rule and action for it. v   Goto /Sitecore/system/Settings/Rules/Definitions/Elements v   Create a new item base on the template “ ElementFolder ” with a name “ Custom Rule ” v   Click on the item and create condition and Actions that are necessary for your requirements Condition Template Item: It has two important sections v   Data ·          Text (This is the condition Text which will use tokens to evaluate the condition and user input which will be in [ ] brackets.The brackets contain four positional parameters separated by commas (“,”). 1. The name of the property that the parameter sets in the .NET class that implements the condition. 2. The name of an item beneath the /Sitecore/System/Settings/Rules/Common/Macros item providing predefined functionality, or an empty string. For example, to activate a user interface allowing the user to select an item from the content tree, specify the value tree. 3. URL param
Read more