Job Queue failing same time every night

amkdmk · 2010-09-29

I'm trying to get 2 Job Queue entries to run from Midnight to 11:00 p.m. every day. They are set as recurring entries and are executing a codeunit. Every night at midnight they fail with the following error found in Event Viewer:

The Job Queue Entry table cannot be changed because it is locked by another user.

Every morning I'll restart NAS and they execute immediately and work fine until midnight when they get the error again. Any ideas?

-Jon

geronimo · 2010-09-29

i suppose you have set the codeunit to a single instance codeunit?

ara3n · 2010-09-30

are you running a backup at night or running some rebuilding index job?

bbrown · 2010-09-30

Rashed raises a good point. Is there another process accessing this table? I recently had a client with this same error. Turned out they had decided to move NAS to a new server. But forgot to shutdown the original one.

matttrax · 2010-09-30

Should be an easy way to check, especially if you are on SQL.

Come in in the morning and it should be blocked. Drill down into the sessions from File --> Database --> Information and check the blocking ID. Or run an SP_WHO query in SQL Server Management Studio.

From there you can trace back to the user / service that is blocking the NAS.

amkdmk · 2010-09-30

I just found out that IT had set a new backup procedure to run every 2 hours. I'll change my startup time tonight and see if that fixes the issue.

amkdmk · 2010-10-13

Looks like this is still failing. I ran the debugger last night and it's failing on CU448 Job Queue Dispatcher Function UpdateJobQueueSession when the Job Queue Process table is modified. The table is locked due to the fact it's being backed up.

I don't have any Job Queue Processes set to run at this time but it looks to be checking the Job Queue Process record and updating it.

matttrax · 2010-10-13

Every two hours seems a little excessive. Do you have people in the database all the time? If no one is logged in at night there should only be a need to take one backup instead of every two hours. That way you don't have processes competing with each other.

ara3n · 2010-10-13

Are you using outlook integration by any chance? Outlook integration uses that table to sync contacts etc.

bbrown · 2010-10-13

Is this SQL or Native? If SQL, what sort of backup are you doing that would be locking tables?

amkdmk · 2010-10-13

It's a SQL backup. I'll find out the details this afternoon.

bbrown · 2010-10-13

a SQL backup is not going to lock tables. Your problem is likely elsewhere.

amkdmk · 2010-10-13

What's odd is the error comes between 12:00 and 12:02 every night and that's when the SQL backup starts.

davmac1 · 2010-10-13

Are you using SQL Server to do thebackup or a third party product?

amkdmk · 2010-10-13

It's a SQL backup. Just found out they are doing a database replication at midnight. Not sure if the backup is done first or the replication.

bbrown · 2010-10-13

amkdmk wrote:

It's a SQL backup. Just found out they are doing a database replication at midnight. Not sure if the backup is done first or the replication.

Can you elaborate on this? What do you mean by "Database Replication"? No such thing. Do you mean a backup and restore to another server?

amkdmk · 2010-10-13

They're replicating the database to be used for reporting.

bbrown · 2010-10-13

amkdmk wrote:

They're replicating the database to be used for reporting.

What I meant is how is it being replicated?

kine · 2010-10-14

There are more ways how to "replicate" database, it is why we are asking...

e.g. you can detach DB, copy DB files, attach DB back etc... and during that the DB is not accessible...

amkdmk · 2010-10-14

The client said they are using "snapshot replication". I'll ask him if they are detaching the database when they are doing that.

bbrown · 2010-10-14

Change the snapshot schedule

Howdy, Stranger!

Quick Links

Categories

Job Queue failing same time every night

Comments