Object failed to run due to insufficient security privileges

security CMC
1

Starting to see a few of these crop up. User is scheduling to default enterprise location, a public folder she has read/write/modify rights to. Has been running fine for a few weeks and tossed error this morning and also killed the scheduling for the job. User was able to do a schedule run now a couple of hours after the scheduled job had failed.

Is there a log anywhere that would tell me why this failed or where the insufficient security privilege is? :hb:

Mike Murray :us: (BOB member since 2005-12-23)

2

When you schedule to a destination, if you use the default then you will be using the username and password set up throught the cmc. The schedule runs under the account specified either in the default or what the user types in when using the non-default.

You should also be able to click on the word ‘failed’ when looing at history. This will bring up the error which is usually quite meaningful.

jonathanstokes (BOB member since 2004-09-17)

3

Object failed to run due to insufficient security privileges is the exact error message it gives. Not to meaningful to me.

As I also stated these have been running successfully for weeks. Both user and application have permission to the share drive.

Mike Murray :us: (BOB member since 2005-12-23)

4

Apologies, I misread the post. That is a bo security error rather than a permissions on the destination folder.

Make sure they have the appropriate rights set on the public folder. You should have to grant the following:

Schedule to destinations
Schedule the document to run

Alos make sure that the report inherits its rights from the folder. Sometimes the report have its own rights attached.

I found the best way to test is to create a user in the same groups and test it out by making changes where appropriate. However, if the error is intermittent then you are probably looking at a bug somewhere. You would have to turn on tracing to the job server to get some more information written to the log.

jonathanstokes (BOB member since 2004-09-17)

5

Are you sure that you have no object / row level security set up?

Mak 1 :uk: (BOB member since 2005-01-06)

6

No I do not have any row level security and reports had been running fine for a couple of months.

Mike Murray :us: (BOB member since 2005-12-23)

7

Ok, then, was has changed?

Either a fix, SP or Fixpack has been applied or someone has changed the security rights.

I thought that maybe someone had been tinkering with Object Properties>Advanced>Security Access Level.

There is a way to make the object “Restricted” in the dropdown…

Mak 1 :uk: (BOB member since 2005-01-06)

8

Nothing in the XI software has changed and the user can do a run now schedule of the same report and it runs fine.

Once they rescheduled the reports they so far have run fine.

Mike Murray :us: (BOB member since 2005-12-23)

9

Sounds like the schedule got messed up / corrupted, somewhere, then…yet another “feature” :cuss: .

Thanks for the update, Mike, I have had the schedules get messed up, but this is usually down to an incorrect “End Time” being assigned BO, which then expires the schedule :flush:.

Mak 1 :uk: (BOB member since 2005-01-06)