emeadaxsupport: Troubleshooting Upgrade and CU Batch jobs stuck in a waiting status in Dynamics AX 2012

[Blog bot]

Источник: http://blogs.msdn.com/b/axsupport/ar...s-ax-2012.aspx
==============

There may be circumstances when you are testing a Full version upgrade, in place upgrade, or applying a Cumulative Update (CU) in Dynamics AX 2012 where the batch jobs never start and appear to be stuck in a waiting status.

Normally we see problems when the Dynamics AX databases is restored to a different environment and the batch framework settings have not been corrected. See this blog for a
larger discussion of this http://blogs.msdn.com/b/axsupport/ar...ironments.aspx

I have compiled a list of things to check to make sure the setup of the batch framework is correct:

1. As always make sure you can you through a Full X++ compile and Full CIL generation without errors in the developer workspace before moving on to any of the other Checklist items.

2. Make sure the user account logging into the Dynamics AX client to run the upgrade checklist is the Dynamics AX admin account, not just a member of the system administrator security role.

• If you check the batch form directly and the DataUpdate job has already scheduled as an account other than admin, you may need to start the upgrade over using the admin account. You may be able to change the records in the batch and batchjob tables to be the admin account.

Important: You should be very careful about updating the records in the SQL backend unless you are very careful to use a where clause in the SQL state, have a SQL backup, and are doing so in the test or dev environment.

The SQL statement you could use would be to set the EXECUTEDBY and CREATEDBY fields to the admin user id for the dataUpdate job.

3. Remove any records in the SysServerSessions table that are not valid in this environment, you may need to do this in SQL server so make sure to have a SQL backup first.

4. Check the setup under system administration | setup | system | Server configuration

• Delete any AOS instances here that are not valid in this environment
• Make sure the remaining AOS instance is marked “is batch server”
• Make sure batch server schedule is setup with proper start/end time i.e. Start time 12:00:00 am end time 11:59:59, so there are no gaps in the scheduled time.

5. Under system administration | setup | batch group

• Make sure that the remaining valid AOS server that is also marked for batch has the blank batch group and dataUpdate batch group assigned to it.

Источник: http://blogs.msdn.com/b/axsupport/ar...s-ax-2012.aspx