the update was interrupted. select the journal program to continue the update

I have a client that gets the message 'A file is in use by another task. Update will continue to retry until record "" is available' when trying to print the Invoice Register in AP. There is no one else in AP. If you shut down and go back in you get the message. 'The update was interrupted. Select the journal program to continue the update'. And then you get into a vicious cycle. 

Contacted Sage and they first had me clear the records in gl_companyactivebatch. It looked like this might work, but when the client tried, she got the same error. Called back and was told to manually reinitialize the gl_companyactivebatch and the ap data entry files. This also did not resolve the issue.

Other modules are fine.

Their internal IT wanted to speak with Sage and preferred to do it without me on the phone so I gave him the ticket number and phone number. Not sure who he talked to, but the recommendation was to get a new business partner. Wow, still haven't gotten that knife out of my back!

Has anyone else had this issue? Did you have better luck getting it resolved?

Thanks

Parents
  • I'd be kinda shocked if that was truly the message from Sage support (...it sounds like the IT folks had an agenda...).  I've had nagging errors, and it is Sage's program to fix, which is absolutely not the Partner's problem.  Sage support escalates internally, unless the problem can be isolated to customizations / enhancements. 

    Hopefully someone from Sage will contact you, get the case number, and track down the rep to discuss what was really said on the call.  Log into the Partner Portal and bring up the case notes, to see status.

    For the posting error: AV exclusions is a very good thought.  Another thing to try is posting directly from the Sage server (not a workstation).

Reply
  • I'd be kinda shocked if that was truly the message from Sage support (...it sounds like the IT folks had an agenda...).  I've had nagging errors, and it is Sage's program to fix, which is absolutely not the Partner's problem.  Sage support escalates internally, unless the problem can be isolated to customizations / enhancements. 

    Hopefully someone from Sage will contact you, get the case number, and track down the rep to discuss what was really said on the call.  Log into the Partner Portal and bring up the case notes, to see status.

    For the posting error: AV exclusions is a very good thought.  Another thing to try is posting directly from the Sage server (not a workstation).

Children
  • in reply to Kevin M

    Agreed.  I was shocked when we received the email from their internal IT stating that this is what Sage told them.  I had Suzanne look up the case but there weren't any new notes.  I'll have her recheck it today.  Either way, it's out of character for Sage to say unless the IT tech got a newbie that didn't want to mess with a difficult issue.  Even if it was that though, it should have been escalated.  None of us need this stress in January!