First, try to remove the extra jobs via AX Client.

1
o
o
o
o

Unlock the Engagements/Activities containing the analytics.

Open AX Core Client
Go to Admin => Unlock
Choose Unlock All
If your engagements and Activities have NOT become unlocked, some things
you may want to check:
That you have sufficient privileges for the Engagement
That the user who created the engagement is still valid
2 Following the unlock process, try to right-click and stop any running analytics
manually.
3 Restart the services on the AX server in the following order (skip AX Core
Postgres DB service if you use Oracle backend).
Stop services:
o AX Core Desktop Connector;
o AX Core Apache Geronimo;
o AX Core Postgres DB server
Start services:
o AX Core Postgres DB server;
o AX Core Apache Geronimo;
o AX Core Desktop Connector.
If this does not fix the problem, you need to remove the script jobs manually from
the database. Note that these instructions are for a PostgreSQL backend; Oracle
instructions are below.
1
2
3
4

5
6

If you dont have pgAdmin, download and install it. Instructions are here:
http://docs.acl.com/ax/310/topic/com.acl.ax.admin.help/system_administratio
n/c_administering_postgresql_with_pgadmin.html
Stop the Geronimo Service, then stop the Desktop Connector Service
Open Task Manager and make sure there are no ACLScript.exe processes still
running.
Using pgAdmin, connect to your PostgreSQL database and log in as
AclAuditExchangeRole. Instructions are here:
http://docs.acl.com/ax/310/topic/com.acl.ax.admin.help/system_administratio
n/t_connecting_to_the_ax_core_database.html
Navigate to Databases > AuditExchangeDB > Schemas > public > Tables
Click on the SQL icon at the top side:

7
8

Under SQL Editor, type in:

SELECT * FROM scriptjobs WHERE
status='initializingWaitingForLock'
Press the green playback icon to execute.
This shows you the analytics which have that particular state. You should see
one record there (the same one that you see in AX Core):

To delete this script job, execute this into the SQL Editor:
DELETE FROM scriptjobs WHERE
status='initializingWaitingForLock'
Or, if you identified the job number with the previous select command, you
can also do:
DELETE FROM scriptjobs WHERE jobnumber='number'
where number is the job number you saw with the select.
10 Close pgAdmin
11 Restart the Desktop Connector Service, then restart the Geronimo Service.
Alternate instructions if you are using an Oracle backend:
4 Stop the AX Geronimo service
5 Make sure no "ACLScript.exe *32" process is running
6 Connect to the AX database using the AX DB user account
7 Once connected, run the following query. This SQL statement has to be
executed under the AX DB user account:
o UPDATE scriptjobs SET returncode = -19, status='skipped' WHERE
((status = 'initializingWaitingForLock' AND returncode = -14) OR (status
= 'initializing' AND returncode = -18))
8 Start The AX Geronimo process