Developer Script Exception : Entity is not api accessible

[thenryST]

I create a roll up yesterday to have the MIN of a score field on Contacts rolled up to a field on their related Account. I've received the error via email but the user ID doesn't exist in our Org. Has anyone seen this error?

Email Subject: Developer script exception from ST : dlrs_AccountTrigger : dlrs_AccountTrigger: execution of AfterUpdate caused by: System.NoAccessException: Entity is not api accessible Class.dlrs.fflib_SObjectSelector: line 36, column 1 Class.dlrs.RollupSummariesSelector.CustomObjectSelector.: line 102, column 1 Class.dlrs.RollupSummariesSelector.: line 43, column 1 Class.dlrs.RollupService.describeRollups: line 990, column 1 Class.dlrs.RollupService.handleRollups: line 673, column 1 Class.dlrs.RollupService.triggerHandler: line 307, column 1 Trigger.dlrs_AccountTrigger: line 7, column 1

Message:
Apex script unhandled trigger exception by user/organization: 0051a000001c0q9/

dlrs_AccountTrigger: execution of AfterUpdate

caused by: System.NoAccessException: Entity is not api accessible

Class.dlrs.fflib_SObjectSelector: line 36, column 1
Class.dlrs.RollupSummariesSelector.CustomObjectSelector.: line 102, column 1
Class.dlrs.RollupSummariesSelector.: line 43, column 1
Class.dlrs.RollupService.describeRollups: line 990, column 1
Class.dlrs.RollupService.handleRollups: line 673, column 1
Class.dlrs.RollupService.triggerHandler: line 307, column 1
Trigger.dlrs_AccountTrigger: line 7, column 1

[afawcett]

Are you in Professional Edition?

[afawcett]

I'll close this issue out for now, however you can still add comments and if needed we can re-open. Thanks. 👍

[jhoosemans]

I have the same error. I first installed the Tool in our Full Sanbox, with no errors. Now I have done the same in production and I get two emails a day with this error. So far I have created two RollUps that rollup Opportunity data to Account.

Good to know, we have person account activated.

[afawcett]

This is the error

Entity is not api accessible 

This is the code failing...

AsyncApexJob.SObjectType.getDescribe().getName()
,ApexTrigger.SObjectType.getDescribe().getName()
,ApexClass.SObjectType.getDescribe().getName()
,Attachment.SObjectType.getDescribe().getName()
,RecordType.SObjectType.getDescribe().getName() 

In this case 'Entity' is an object, some of these you will recognise like Attachment. Others maybe less so. Other than in PE edition, all these objects should exist in EE and above. So i do not quite understand the error.

I note that the latest version of the fflib_SObjectSelector class does not use the above code. Maybe this will resolve the issue. I'll mark this as a bug (and update to the latest version of this class) and we can make a speculative fix perhaps, see if this works. Since i cannot reproduce. it.

Meanwhile, can you confirm what Salesforce edition your on? Also how recent is your sandbox copy of production?

[shawnholt]

receiving this error since winter 17 upgrade. using managed release (2.4.2). not sure 1) how to upgrade managed and 2) if this issues is resolved. thx

[afawcett]

Thanks @shawnholt , added priority tag on this one, i had not appreciated until now it was a regression caused by the platform upgrade, thanks for sharing! 👍

[StephanieKing]

Hi @afawcett , yes, this sounds like my issue. I am getting various errors from 6 Nonprofit orgs every night. All Nonprofit orgs are on Enterprise edition.

ONE ERROR EMAIL LOOKS LIKE THIS:
Apex script unhandled trigger exception by user/organization: 005j000000BvWLz/00Dj0000001pS6d
dlrs_ContactTrigger: execution of AfterUpdate

caused by: System.NoAccessException: Entity is not api accessible

Class.dlrs.fflib_SObjectSelector: line 36, column 1
Class.dlrs.RollupSummariesSelector.CustomObjectSelector.: line 102, column 1
Class.dlrs.RollupSummariesSelector.: line 43, column 1
Class.dlrs.RollupService.describeRollups: line 943, column 1
Class.dlrs.RollupService.handleRollups: line 635, column 1
Class.dlrs.RollupService.triggerHandler: line 307, column 1
Trigger.dlrs_ContactTrigger: line 7, column 1

AND THE OTHER ERROR EMAIL LOOKS LIKE THIS:
Error #2:
Error Type: Batch Apex error
Error Date: 2016-12-02 06:01:55
Message: "First error: Update failed. First exception on row 0 with id 003j000000HwBSEAA3; first error: CANNOT_INSERT_UPDATE_ACTIVATE_ENTITY, dlrs_ContactTrigger: execution of AfterUpdate
caused by: System.NoAccessException: Entity is not api accessible
Class...."
Context: npsp__RLLP_OppContactRollup_BATCH
Stack Trace:
null

Error #3:
Error Type: Batch Apex error
Error Date: 2016-12-03 06:01:17
Message: "First error: Update failed. First exception on row 0 with id 003j000000HwBSEAA3; first error: CANNOT_INSERT_UPDATE_ACTIVATE_ENTITY, dlrs_ContactTrigger: execution of AfterUpdate
caused by: System.NoAccessException: Entity is not api accessible
Class...."
Context: npsp__RLLP_OppContactRollup_BATCH
Stack Trace:
null

Error #4:
Error Type: Batch Apex error
Error Date: 2016-12-04 06:01:15
Message: "First error: Update failed. First exception on row 0 with id 003j000000HwBSEAA3; first error: CANNOT_INSERT_UPDATE_ACTIVATE_ENTITY, dlrs_ContactTrigger: execution of AfterUpdate

caused by: System.NoAccessException: Entity is not api accessible

Class...."
Context: npsp__RLLP_OppContactRollup_BATCH
Stack Trace:
null

NOTE: I have not yet been able to determine if the rollups are actually NOT WORKING, or if they are working, but just sending me these mysterious errors.
I am going to post on the HUB as well to see if someone can help from the NPSP side....

[cdcarter]

Asked this question of @StephanieKing in the HUB but it's probably better to keep this troubleshooting here, as I anticipate this is not NPSP related.

@stephanie King (Redpath Consulting Group, LLC) - what occurs when you execute the following block of code in Developer Console?

System.debug(AsyncApexJob.SObjectType.getDescribe().getName());
System.debug(ApexTrigger.SObjectType.getDescribe().getName());
System.debug(ApexClass.SObjectType.getDescribe().getName());
System.debug(Attachment.SObjectType.getDescribe().getName());
System.debug(RecordType.SObjectType.getDescribe().getName());

Can you upload the full debug log from that execution?

[shawnholt]

Have you tried changing the execution time for scheduled jobs? May have a conflict.

…

On Dec 5, 2016 10:10 AM, "StephanieKing" ***@***.***> wrote: Hi @afawcett <https://github.com/afawcett> , yes, this sounds like my issue. I am getting various errors from 6 Nonprofit orgs every night. All Nonprofit orgs are on Enterprise edition. *ONE ERROR EMAIL LOOKS LIKE THIS:* Apex script unhandled trigger exception by user/organization: 005j000000BvWLz/00Dj0000001pS6d dlrs_ContactTrigger: execution of AfterUpdate caused by: System.NoAccessException: Entity is not api accessible Class.dlrs.fflib_SObjectSelector: line 36, column 1 Class.dlrs.RollupSummariesSelector.CustomObjectSelector.: line 102, column 1 Class.dlrs.RollupSummariesSelector.: line 43, column 1 Class.dlrs.RollupService.describeRollups: line 943, column 1 Class.dlrs.RollupService.handleRollups: line 635, column 1 Class.dlrs.RollupService.triggerHandler: line 307, column 1 Trigger.dlrs_ContactTrigger: line 7, column 1 *AND THE OTHER ERROR EMAIL LOOKS LIKE THIS:* Error #2 <#2> : Error Type: Batch Apex error Error Date: 2016-12-02 06:01:55 Message: "First error: Update failed. First exception on row 0 with id 003j000000HwBSEAA3; first error: CANNOT_INSERT_UPDATE_ACTIVATE_ENTITY, dlrs_ContactTrigger: execution of AfterUpdate caused by: System.NoAccessException: Entity is not api accessible Class...." Context: npsp__RLLP_OppContactRollup_BATCH Stack Trace: null Error #3 <#3> : Error Type: Batch Apex error Error Date: 2016-12-03 06:01:17 Message: "First error: Update failed. First exception on row 0 with id 003j000000HwBSEAA3; first error: CANNOT_INSERT_UPDATE_ACTIVATE_ENTITY, dlrs_ContactTrigger: execution of AfterUpdate caused by: System.NoAccessException: Entity is not api accessible Class...." Context: npsp__RLLP_OppContactRollup_BATCH Stack Trace: null Error #4 <#4> : Error Type: Batch Apex error Error Date: 2016-12-04 06:01:15 Message: "First error: Update failed. First exception on row 0 with id 003j000000HwBSEAA3; first error: CANNOT_INSERT_UPDATE_ACTIVATE_ENTITY, dlrs_ContactTrigger: execution of AfterUpdate caused by: System.NoAccessException: Entity is not api accessible Class...." Context: npsp__RLLP_OppContactRollup_BATCH Stack Trace: null NOTE: I have not yet been able to determine if the rollups are actually NOT WORKING, or if they are working, but just sending me these mysterious errors. I am going to post on the HUB as well to see if someone can help from the NPSP side.... — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#360 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AB-Q6jgs8zg23IvfXgjsHARKIH1Ac7LJks5rFCmCgaJpZM4JWXwO> .

[StephanieKing]

@cdcarter --
Here is what the debug log looks like:

@shawnholt - I have not tried that... is there a way to tell if that is a factor, or do I just change the time and see if it helps?

[cdcarter]

@afawcett - is there any chance asyncapexjob is no longer API accessible from within an async job?

[StephanieKing]

Just checking in again. I am getting this error daily from multiple organizations. All of them are Enterprise orgs with the NPSP. Here is one from today, from a different org:

Apex script unhandled trigger exception by user/organization: 00512000005wJS2/00DA0000000BgL6

dlrs_OpportunityTrigger: execution of AfterInsert

caused by: System.NoAccessException: Entity is not api accessible

Class.dlrs.fflib_SObjectSelector: line 36, column 1
Class.dlrs.RollupSummariesSelector.CustomObjectSelector.: line 102, column 1
Class.dlrs.RollupSummariesSelector.: line 43, column 1
Class.dlrs.RollupService.describeRollups: line 992, column 1
Class.dlrs.RollupService.handleRollups: line 673, column 1
Class.dlrs.RollupService.triggerHandler: line 307, column 1
Trigger.dlrs_OpportunityTrigger: line 7, column 1

[afawcett]

Ok i have upgraded fflib_SObjectSelector which does not use the above code to detect currency mode and avoids referencing the above objects all together. Not having been able to reproduce this (its spooky that not everyone is getting it, yet its clearly on a line of code that should apply to all orgs?!?). Anyway, i'm calling this a speculative fix...

[afawcett]

Fixed in v2.6, we can re-open in this speculative fix does not work.

[StephanieKing]

Thanks @afawcett I'm installing v2.6 in 5 orgs this morning, and crossing my fingers for less error messages in my inbox tomorrow! :-) I appreciate it, and will let you know!

[afawcett]

Same here, really hope this solves this illusive issue! 👍

[StephanieKing]

Success! No more DLRS errors! Thanks a BUSHEL for the fix!

[emilyhillis]

@afawcett @StephanieKing We're having the same issue and it sounds like we need to install v2.6. Did you have to make any changes after installing the new version? How did you install the new version? I'm looking on the App Exchange and it looks like the version out there was last release on 6/29/2016. https://appexchange.salesforce.com/listingDetail?listingId=a0N30000009i3UpEAI

[StephanieKing]

@emilyhillis just download it right here from GitHub - on the main page just scroll down a little ways until you see the latest version with download links! https://github.com/afawcett/declarative-lookup-rollup-summaries
Right under the heading "Packaged Release History"

[afawcett]

@emilyhillis thats the wrong tool, that tool is commercial and is called Rollup Helper. @StephanieKing is correct, please find the latest package install link in the README file of the repo. Just click it and the platform will upgrade your current package install to the latest.