You need to sign in to do that
Don't have an account?
Sabrent
INACTIVE_OWNER_OR_USER, operation performed with inactive user:
I don't see any inactive user, neither is there a trigger that chnages ownership. Yes i keep getting this error.
Any thought?? Thakns.
|FATAL_ERROR|System.DmlException: Insert failed. First exception on row 16; first error: INACTIVE_OWNER_OR_USER, operation performed with inactive user: []
What action are you attempting to perform? What record is row 16?
Check if there are any workflows which change the ownership, Assignment rules(case/Lead), Default case owner etc
The code is inserting records. Basically granting portal access to the users.
There is no workflow that is changing ownership.
I tried a small subset of records, even that fails.
I checked all users and none is inactive.
Post your code please.
Any clue.. me too getting same error while doing insert on custom object
In my case customObject's ownerId is set to event ownerId before insert..
is this causing the problem.. in that case what are the possible scenarios to replicate the error..
check if the event owner that you are assigning is active or inactive?
Also, check your test class. Are you using test owner which is inactive?
Put some debug logs to get a better idea.
Can you post your trigger snippet?
due to some reasons I cannot copy my code..
this issue happened to the user while doing some opertations from frontend..
am trying to recreate the exception by making Event owner inactive.. but am not getting this exception
//so below line is not creating the issue
customObject.OwnerId = someEvent.OwnerId;
I would like to know what all scenarios will create INACTIVE_OWNER_OR_USER exception.
: The solution was this: I created a log file and reran the test and found that our SFDC Admin had made the approver account inactive for an employer who is no longer employed with us however he name is still defined within the Work Flow to approve processes. So I went to the Approver Work flow and substituted Maria's name with a current employer. So always check to see that the Execution Contex is not prohibting your test cases or classes for functioning. I hope this helps someone.