web
You’re offline. This is a read only version of the page.
close
Skip to main content

Notifications

Announcements

No record found.

News and Announcements icon
Community site session details

Community site session details

Session Id :
Dynamics 365 Community / Forums / Microsoft Dynamics CRM (Archived) / CRM2016 Problem trying...
Microsoft Dynamics CRM (Archived)

CRM2016 Problem trying to create Child Case using OOTB functionality

(0) ShareShare
ReportReport
Posted on by ChrisC 630

Hi, I am trying to use the OOTB functionality to create a child case. My case entity has some custom fields but they are mapped in the parent-child relationship, which I can see both in the Service Settings and in the Solution Entity Relationship mapping as you would expect. When clicking on the ribbon button a new case is presented in a new window with the fields populated as expected, but when trying to save there is a message saying not more than 10 child cases can be created (there are none) and downloading the error xml the message is not more than 0 (zero) child cases may be created???? Anyone seen this? Thanks

*This post is locked for comments

I have the same question (0)
  • a33ik Profile Picture
    a33ik 84,331 Most Valuable Professional on at

    Hello,

    That's a really weird behavior. Tried my dev environment and I don't see the same result. Can you please publish error.xml content? Also how many customizations have you done on case entity?

  • Suggested answer
    ChrisC Profile Picture
    ChrisC 630 on at

    Well I have quickview forms linked to the customer and contract lookups but these appear in the new case as expected and the auto complete works OK, problem is only on saving. In fact I didn't really want a child case, more a sibling case, so I implemented my own functionality based on ribbon button, which works fine. So just a mystery that's all.

  • Sabrina Di Bartolomeo Profile Picture
    Sabrina Di Bartolomeo 60 on at

    I'm getting the same error. When I try to create a child case I get: "Child Cases limit Exceeded. A Parent Case cannot have more than 10 child cases." In the Log File there is following error: <ErrorCode>-2147224492</ErrorCode> A Parent Case cannot have more than 0 child cases. Initially I solved the issue creating a new organization but after a while I got the error again.

  • Suggested answer
    razdynamics Profile Picture
    razdynamics 17,308 User Group Leader on at

    Hi is this error occuring with On premise? Anyone had this issue with crm online?

  • Sabrina Di Bartolomeo Profile Picture
    Sabrina Di Bartolomeo 60 on at

    Dynamics CRM 2016 On Premise. I installed update 0.1 to see if it solves the issue but it didn't. It doesn't matter if I try to create the child case from the quick form or from the subgrid. Even just trying to relate an existing case as a child case using the "child cases" subgrid is not working. I always get the same error. 

  • Inogic Profile Picture
    Inogic 709 on at

    Are you facing this issue for all the Cases in your CRM or based on particular condition for a case, cause we tried to replicate this issue with Online and On-premises but we did not face this error.

    Could you please mention the Customizations you performed for the Case entity or if you had used either plug-in or Workflow for “Case”.

    Thanks,

    Sam

  • Sabrina Di Bartolomeo Profile Picture
    Sabrina Di Bartolomeo 60 on at

    No plugin, no workflow, just normal customizations of new few fields in the case form. But I have not added those custom fields in the Parent and Child case Settings. The selected attibutes are only: Case Title and Customer and no cascade closure preferences are selected.

    I have some Queues configured with incoming emails address that are using the automatic record creation and update rules but I'm facing the issue for all cases, also the ones created manually.

    No security roles are involved because I'm using the System Administrator user.

    However, here is the downloaded error log:

    Unhandled Exception: System.ServiceModel.FaultException`1[[Microsoft.Xrm.Sdk.OrganizationServiceFault, Microsoft.Xrm.Sdk, Version=8.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35]]: A Parent Case cannot have more than 0 child cases. Contact your administrator for more details.Detail:
    <OrganizationServiceFault xmlns:i="www.w3.org/.../XMLSchema-instance" xmlns="schemas.microsoft.com/.../Contracts">
      <ErrorCode>-2147224492</ErrorCode>
      <ErrorDetails xmlns:d2p1="schemas.datacontract.org/.../System.Collections.Generic">
        <KeyValuePairOfstringanyType>
          <d2p1:key>0</d2p1:key>
          <d2p1:value xmlns:d4p1="www.w3.org/.../XMLSchema" i:type="d4p1:string">0</d2p1:value>
        </KeyValuePairOfstringanyType>
      </ErrorDetails>
      <Message>A Parent Case cannot have more than 0 child cases. Contact your administrator for more details.</Message>
      <Timestamp>2016-05-16T13:43:52.2974388Z</Timestamp>
      <InnerFault i:nil="true" />
      <TraceText i:nil="true" />
    </OrganizationServiceFault>

    And here the last activity traced before the error occured:

    [2016-05-16 14:53:28.529] Process: w3wp |Organization:eb48f044-d215-e611-80e4-005056b528c9 |Thread:  909 |Category: Exception |User: 328035f1-5cfe-4aed-ac1c-b9173da65be7 |Level: Error |ReqId: e7decf00-b065-4d78-bf76-34bcac2d295d | CrmException..ctor  ilOffset = 0xA
     at CrmException..ctor(String formattedErrorMessage, Int32 errorCode, Object[] arguments)  ilOffset = 0xA
     at IncidentService.CheckMaxChildAssosciationLimit(IBusinessEntity incident, ExecutionContext context)  ilOffset = 0x93
     at IncidentService.Create(IBusinessEntity incident, ExecutionContext context)  ilOffset = 0xD5
     at RuntimeMethodHandle.InvokeMethod(Object target, Object[] arguments, Signature sig, Boolean constructor)  ilOffset = 0xFFFFFFFF
     at RuntimeMethodInfo.UnsafeInvokeInternal(Object obj, Object[] parameters, Object[] arguments)  ilOffset = 0x16
     at RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture)  ilOffset = 0x7F
     at LogicalMethodInfo.Invoke(Object target, Object[] values)  ilOffset = 0x3F
     at InternalOperationPlugin.Execute(IServiceProvider serviceProvider)  ilOffset = 0x43
     at V5PluginProxyStep.ExecuteInternal(PipelineExecutionContext context)  ilOffset = 0x0
     at VersionedPluginProxyStepBase.Execute(PipelineExecutionContext context)  ilOffset = 0x65
     at Pipeline.Execute(PipelineExecutionContext context)  ilOffset = 0xDD
     at MessageProcessor.Execute(PipelineExecutionContext context)  ilOffset = 0x1E6
     at InternalMessageDispatcher.Execute(PipelineExecutionContext context)  ilOffset = 0xE4
     at ExternalMessageDispatcher.ExecuteInternal(IInProcessOrganizationServiceFactory serviceFactory, IPlatformMessageDispatcherFactory dispatcherFactory, String messageName, String requestName, Int32 primaryObjectTypeCode, Int32 secondaryObjectTypeCode, ParameterCollection fields, CorrelationToken

    correlationToken, CallerOriginToken originToken, UserAuth userAuth, Guid callerId, Guid callerRegardingObjectId, UserType userType, Guid transactionContextId, Int32 invocationSource, Nullable`1 requestId, Version endpointVersion)  ilOffset = 0x1F2
     at ExternalMessageDispatcher.Execute(IInProcessOrganizationServiceFactory serviceFactory, IPlatformMessageDispatcherFactory dispatcherFactory, String messageName, String requestName, Int32 primaryObjectTypeCode, Int32 secondaryObjectTypeCode, ParameterCollection fields, CorrelationToken correlationToken,

    CallerOriginToken originToken, UserAuth userAuth, Guid callerId, Guid callerRegardingObjectId, UserType userType, Guid transactionContextId, Int32 invocationSource, Nullable`1 requestId)  ilOffset = 0x0
     at OrganizationSdkServiceInternal.ExecuteRequestRequestWithInstrumentation(OrganizationRequest request, CorrelationToken correlationToken, CallerOriginToken callerOriginToken, WebServiceType serviceType, UserAuth userAuth, Guid targetUserId, OrganizationContext context, Boolean returnResponse, Boolean

    checkAdminMode, Object operation, UserType targetUserType)  ilOffset = 0x0
     at OrganizationSdkServiceInternal.ExecuteRequest(OrganizationRequest request, CorrelationToken correlationToken, CallerOriginToken callerOriginToken, WebServiceType serviceType, Boolean checkAdminMode, ExecutionContext executionContext)  ilOffset = 0x4B
     at OrganizationSdkServiceInternal.Execute(OrganizationRequest request, CorrelationToken correlationToken, CallerOriginToken callerOriginToken, WebServiceType serviceType, Boolean checkAdminMode, ExecutionContext executionContext)  ilOffset = 0x0
     at InprocessServiceProxy.ExecuteCore(OrganizationRequest request)  ilOffset = 0x34
     at PlatformCommand.XrmExecuteInternal()  ilOffset = 0xBC
     at CreateCommand.Execute()  ilOffset = 0x6
     at EntityProxy.Create(Boolean performDuplicateCheck, Guid auditingTransactionId)  ilOffset = 0x0
     at EntityProxy.Create(Boolean performDuplicateCheck)  ilOffset = 0xC
     at EntityProxy.CreateAndRetrieve(String[] columnSet, Boolean performDuplicateCheck)  ilOffset = 0x0
     at CommandBase.UpdateEntity(Entity entity, Boolean retrieve)  ilOffset = 0x97
     at SaveCommand.ExecuteCommand(String commandXml)  ilOffset = 0x10E
     at CommandBase.Execute(String commandXml, Boolean encodeValues)  ilOffset = 0x6
     at InlineEditWebService.Execute(Int32 command, String commandXml, Nullable`1 encodeValues)  ilOffset = 0xAC
     at RuntimeMethodHandle.InvokeMethod(Object target, Object[] arguments, Signature sig, Boolean constructor)  ilOffset = 0xFFFFFFFF
     at RuntimeMethodInfo.UnsafeInvokeInternal(Object obj, Object[] parameters, Object[] arguments)  ilOffset = 0x16
     at RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture)  ilOffset = 0x7F
     at LogicalMethodInfo.Invoke(Object target, Object[] values)  ilOffset = 0x3F
     at WebServiceHandler.Invoke()  ilOffset = 0xAE
     at WebServiceHandler.CoreProcessRequest()  ilOffset = 0x134
     at SyncSessionlessHandler.ProcessRequest(HttpContext context)  ilOffset = 0x3F
     at CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute()  ilOffset = 0x187
     at HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously)  ilOffset = 0x15
     at PipelineStepManager.ResumeSteps(Exception error)  ilOffset = 0x27A
     at HttpApplication.BeginProcessRequestNotification(HttpContext context, AsyncCallback cb)  ilOffset = 0x31
     at HttpRuntime.ProcessRequestNotificationPrivate(IIS7WorkerRequest wr, HttpContext context)  ilOffset = 0xB0
     at PipelineRuntime.ProcessRequestNotificationHelper(IntPtr rootedObjectsPointer, IntPtr nativeRequestContext, IntPtr moduleData, Int32 flags)  ilOffset = 0x131
     at PipelineRuntime.ProcessRequestNotification(IntPtr rootedObjectsPointer, IntPtr nativeRequestContext, IntPtr moduleData, Int32 flags)  ilOffset = 0x0
     at UnsafeIISMethods.MgdIndicateCompletion(IntPtr pHandler, RequestNotificationStatus& notificationStatus)  ilOffset = 0xFFFFFFFF
     at UnsafeIISMethods.MgdIndicateCompletion(IntPtr pHandler, RequestNotificationStatus& notificationStatus)  ilOffset = 0xFFFFFFFF
     at PipelineRuntime.ProcessRequestNotificationHelper(IntPtr rootedObjectsPointer, IntPtr nativeRequestContext, IntPtr moduleData, Int32 flags)  ilOffset = 0x1E7
     at PipelineRuntime.ProcessRequestNotification(IntPtr rootedObjectsPointer, IntPtr nativeRequestContext, IntPtr moduleData, Int32 flags)  ilOffset = 0x0
    >Crm Exception: Message: A Parent Case cannot have more than 0 child cases. Contact your administrator for more details., ErrorCode: -2147224492

    To me it seems that the maximun number of child cases is stored somewhere and for a reason that I don't know it is 0 instead of 100. Indeed the Dynamics documentation says: <<Each incident can have up to 100 child incidents. If you try to create too many child incidents you will get error -2147224492 with the message: “A Parent Case cannot have more than 100 child cases. Contact your administrator for more details.”>> This message is using a Parameter {0}

  • Suggested answer
    Sabrina Di Bartolomeo Profile Picture
    Sabrina Di Bartolomeo 60 on at

    I've found the property!

    In MSCRM_CONFIG table OrganizationProperties, the MaxChildIncidentNumber was missing for my organization. It was not just set to 0, the row was completely missing. I noticed that because when I created a new organization, for that new one the property MaxChildIncidentNumber was there.

    There is somewhere a bug that is deleting the row.

    However, a insert solved my problem. I know that this fix is not supported but I'm just preparing a demo for a customer and I don't have time to further investigate the issue at the moment with Microsoft.

    One of the reason I lost a lot of time is also the name of error number -2147224492.

    The error is connented with a message called MaxChildCasesLimitExceeded (https://msdn.microsoft.com/en-us/library/gg328182.aspx), so I was looking for a property called MaxChildCases ... instead of MaxChildIncidentNumber.

  • Suggested answer
    razdynamics Profile Picture
    razdynamics 17,308 User Group Leader on at

    Glad you Managed to resolve this issue Sabrina Well done :)

  • Community Member Profile Picture
    Community Member on at

    Hi Sabrina, Can you please explain the process that you used for the insert? I have inserted a row with the same ID as all the others, that name and an IntColumn of 10 but i still get the same error.

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Responsible AI policies

As AI tools become more common, we’re introducing a Responsible AI Use…

Neeraj Kumar – Community Spotlight

We are honored to recognize Neeraj Kumar as our Community Spotlight honoree for…

Congratulations to the November Top 10 Community Leaders!

These are the community rock stars!

Leaderboard > 🔒一 Microsoft Dynamics CRM (Archived)

#1
SA-08121319-0 Profile Picture

SA-08121319-0 4

#1
Calum MacFarlane Profile Picture

Calum MacFarlane 4

#3
Alex Fun Wei Jie Profile Picture

Alex Fun Wei Jie 2

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans