Skip to main content

One or more exceptions occurred while processing the subscribers to the 'item:creating' event

I was recently installing the packages from one of the QA environment to my local Sitecore instance, "Media library package" to be precise, And it started giving me this below error

One or more exceptions occurred while processing the subscribers to the 'item:creating' event

Looking at the sitecore logs, it gave me more info on the context and the actual inner exception was following
Solution: 'Name' should consist only of letters, digits, dashes or underscore

Now it was evident that some of my file names were violating the naming rule, I could see in the log just before exception from where the installer stopped creating items, and that file name had round braces "(" and ")" at the end of it, with my surprise I was able to create the item with those name in the content tree, but below was the solution for it,

Solution

I am using SC 9.0.1 and in that Go to Sitecore.Marketing.config file residing in 
"App_Config\Sitecore\Marketing.Operations.xMgmt" folder and find two entries as below
<event name="item:saving"> <handler type="Sitecore.Marketing.xMgmt.Definitions.ItemEventHandler, Sitecore.Marketing.xMgmt"
method="OnItemSaving"/> </event> <event name="item:creating"> <handler type="Sitecore.Marketing.xMgmt.Definitions.ItemEventHandler, Sitecore.Marketing.xMgmt"
method="OnItemCreating"/> </event>

Comment them out and try to import the package again, this time it will work, Once you are done restoring the package, You can revert that file back by uncommenting those entries.


Hope it helps !!!

Comments

  1. thanks that did the trick! SC 9.1.1

    ReplyDelete
  2. HI Daivag, just wanted to know it's impact if we kept both the lines commented.

    ReplyDelete
  3. I tried the process but after that too facing the same issue

    ReplyDelete
  4. I tried the process but after that too facing the same issue

    ReplyDelete
  5. Awesome ! It's Working 100 % fine. Thank you so much @Daivagna

    ReplyDelete
  6. Thanks and that i have a tremendous provide: Whole House Renovation Cost Calculator 1960 bungalow exterior makeover

    ReplyDelete

Post a Comment

Popular posts from this blog

High CPU to completely normal CPU - SXA issue, SXA pages not loading in mobile device

  Hi Team, Today i am going to share one of the nightmarish issue with you all, We are having Sitecore 9.1.1 hosted in azure PaaS environment Our site was working just fine and no noise, but we have been working on a feature release where 7-8 months of development needed to be released to production, Big GO LIVE event right?  Also to make the development smoother we also introduced BLUE/GREEN deployment slots in the same release, so we can easily SWAP slots and go live Everything went well, we went live, we even did load and performance testing on our staging and pre-prod and we were confident enough of results Very next day we started getting "SITE DOWN" alerts, and also product owners and clients mentioned that site is very slow for them in US time and in our morning when we were accessing it, it was working lighting fast so we were clue less at start, but we started digging  1) First thing caught our eyes were HIGH CPU spikes, in US time, also without any traffic CPU u...

An error occurred while receiving the HTTP response to This could be due to the service endpoint binding not using the HTTP protocol. This could also be due to an HTTP request context being aborted by the server (possibly due to the service shutting down). See server logs for more details.

You have noticed many times that everything was working fine and suddenly the below error starts coming and you find no way to work it out An error occurred while receiving the HTTP response to This could be due to the service endpoint binding not using the HTTP protocol. This could also be due to an HTTP request context being aborted by the server (possibly due to the service shutting down). See server logs for more details. The reason for this is the receiving size of WCF service is smaller then the data which is coming from service It was working before because it was small,So you will have to try to increase the receiving setting in your end point,Possible settings can be following maxStringContentLength="2147483647" maxReceivedMessageSize="2147483647" maxBufferSize="2147483647" maxArrayLength="2147483647" That would definately help you!!!