We have scheduled jobs that are automatically scheduled when a user runs our install script. From what I have been able to find in the documentation, these jobs are scheduled by a fake "installation user" with a certain level of permissions. (Does anybody know what these permissions are?)

One of our scheduled jobs is failing because the installation user appears to have insufficient privileges to access some of the fields on the Account object, and the scheduled job is trying to update those fields. If I delete the scheduled job and reschedule it when logged in as the system administrator, the scheduled job executes fine.

This doesn't appear to be an issue with all of our scheduled jobs, just one in particular right now.

The error that we're seeing is System.SObjectException: Field is not writeable: Account.BillingState - I've already verified that the BillingAddress is editable by all profiles.

Another error is then caused when the scheduled job tries to schedule a follow up job that we have run in the finish() method:

System.UnexpectedException: Insufficient Privileges

Has anybody ran into any issues like this? Our solution will probably be to remove the scheduled job from the install script and have the user schedule the jobs via our Configure page.

Has anyone seen an issue in Summer13 sandboxes where a VisualForce page will fail when it accesses an Apex Property with the datatype of "ID"?

The error message that I am getting is "java.lang.ClassCastException: java.lang.String cannot be cast to lib.id.ID".  The debug logs do not show any error at all.

This error was first noticed on Monday, May 13 in a Summer13 sandbox.  The specific code was created last summer (July 2012) and we have had no issue with it.  The same code is working correctly in Spring13 orgs.

The issue appears to be related to Summer '13 now working always with 18 char IDs. This can cause code issues.

We have scheduled jobs that are automatically scheduled when a user runs our install script. From what I have been able to find in the documentation, these jobs are scheduled by a fake "installation user" with a certain level of permissions. (Does anybody know what these permissions are?)

One of our scheduled jobs is failing because the installation user appears to have insufficient privileges to access some of the fields on the Account object, and the scheduled job is trying to update those fields. If I delete the scheduled job and reschedule it when logged in as the system administrator, the scheduled job executes fine.

This doesn't appear to be an issue with all of our scheduled jobs, just one in particular right now.

The error that we're seeing is System.SObjectException: Field is not writeable: Account.BillingState - I've already verified that the BillingAddress is editable by all profiles.

Another error is then caused when the scheduled job tries to schedule a follow up job that we have run in the finish() method:

System.UnexpectedException: Insufficient Privileges

Has anybody ran into any issues like this? Our solution will probably be to remove the scheduled job from the install script and have the user schedule the jobs via our Configure page.