Thursday 13 November 2014

XCP 2.1 - Consistent Errors

It’s been a year now, I am working on XCP designer and the only consistent thing I have noticed in this product is with every new patch release EMC is coming up with some new issues.

Yes, we are never sure if our application will work fine whenever there is an upgrade.

Is EMC engineering team facing some issues in maintaining versions for the product they are releasing? How can fixes done is older patch found missing in later one? Well, in that case I will suggest EMC Engineering team to do some homework on basics of versioning. A very basic concept in Documentum :P

8 comments:

  1. Hi Vaishali,

    We are constantly working on xCP 2.1 products, however we are getting the following error, every now and then.

    errorCode=E_ECM_PROCESS_STATELESSPROCESS_FAILED errorMessage=Failure in stateless process urn:

    After the recycling the app server, the error went off... but after sometime it is coming again. Do you have any resolution on this.

    Regards,
    Rajkumar Sukumar

    ReplyDelete
  2. Hi Rajkumar,

    Can you provide the detailed error message log? It's difficult to debug with Error Code only.


    Regards,
    Vaishali

    ReplyDelete
    Replies
    1. .... and apart from this, i'm getting this error constantly... [when ever i try to delete/update my previous datas]

      DfAspectOperationException:: THREAD: main; MSG: [DFC_BOF_ASPECT_INVALID_SET] An attempt to create incompatible aspect set:
      IBVDocumentAspect,cis_annotation_aspect,defaultdatatypeaspect,dmc_topic_aspect.; ERRORCODE: ff; NEXT: null
      at com.documentum.fc.client.DfAspectOperationException.makeInvalidAspectSetException(DfAspectOperationException.java:31)
      at com.documentum.fc.client.impl.bof.compoundclass.AspectRulesProcessor.indexCategories(AspectRulesProcessor.java:158)
      at com.documentum.fc.client.impl.bof.compoundclass.AspectRulesProcessor.checkCategoryCompatibility(AspectRulesProcessor.java:29)
      at com.documentum.fc.client.impl.bof.compoundclass.AspectMgr.getValidatedAndOrderedAspectSet(AspectMgr.java:472)
      at com.documentum.fc.client.impl.bof.compoundclass.AspectMgr.getAllAspects(AspectMgr.java:72)
      at com.documentum.fc.client.impl.bof.compoundclass.AspectMgr.getAllAspectTypeInfoMap(AspectMgr.java:41)
      at com.documentum.fc.client.impl.objectmanager.PObjectFactoryWithAspects.makeObject(PObjectFactoryWithAspects.java:46)
      at com.documentum.fc.client.impl.objectmanager.PersistentObjectManager.getObjectFromServer(PersistentObjectManager.java:356)
      at com.documentum.fc.client.impl.objectmanager.PersistentObjectManager.getObject(PersistentObjectManager.java:311)
      at com.documentum.fc.client.impl.session.Session.getObject(Session.java:906)

      Regards,
      Raj

      Delete
    2. Hi,

      DFC_BOF_ASPECT_INVALID_SET - Check if the User has permission to Update/Delete the object. The error is coming because of the aspects associated with object(IBVDocumentAspect,cis_annotation_aspect,defaultdatatypeaspect,dmc_topic_aspect).

      Stateless processes always run with User sessions and not with Docbase Owner or Superuser. Check permissions of the User invoking stateless process.


      Regards,
      Vaishali

      Delete
    3. Hi,
      Its failing even i try to delete the object using DA as super user.

      Finally, I have found the solution, that it is because of bad acl_domain set for few of the objects, once i update the acl with right acl domin, the issue is resolved.

      Regards,
      Raj

      Delete
    4. Can you elaborate object_type of objects which has wronge acl_domain when your stales processes were failing. We are getting similar error when we upgread our software to XCP2.3 patch 11 .

      Delete
  3. For the E_ECM_PROCESS_STATELESSPROCESS_FAILED you can check below:
    1) Detailed error log
    2) If all stateless processes are failing, check space on your application server
    3) Try to run the application using preview mode.

    ReplyDelete
    Replies
    1. Correct, thats what we are doing, just clear the temp/cahce directory and restart the app server, but not sure why xCP put tons of dars in temp directory which fill up the memory easily.

      Delete