x Want to participate? Join the group to interact
Options
  • Replies 12 replies
  • Subscribers 110 subscribers
  • Views 3667 views
  • Users 0 members are here
Browse Forums
Announcements
293
topics
370
replies
Business Object Interface
1k
topics
7k
replies
Core Financial Modules
2k
topics
8k
replies
Customization and Productivity
3k
topics
12k
replies
Distribution, Manufacturing, and Applications
2k
topics
7k
replies
General Discussion
1k
topics
3k
replies
Partner Cloud
44
topics
91
replies
Payroll, Time Tracking, and Job Cost
777
topics
1k
replies
Reporting and Analytics
962
topics
3k
replies
Sage CRM for Sage 100
164
topics
357
replies
Technical and Installation
2k
topics
9k
replies
Year-end Forum
89
topics
237
replies
suzmwatson

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

Posted By

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

  • So this just happened one time, not repeatedly, right?  And I think you might still be bleeding - that was inexcusable!

  • What has changed to start this happening?  How long have they been on Sage 100?

    Have you tried disabling Antivirus on both the workstation and server to see if that stops the file lock?

  • Here is an update to what is happening at the client.  We had another user access the Invoice Register on his machine and was able to post.  We then had him enter an AP Invoice and he had no issue posting.  Went back to the original users machine and had her enter an invoice and she got the error message.  We are in the process of having the other user log into her machine and try it.  We suspect a Profile issue...unless anyone has any other suggestions.  Thanks!

  • 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).

  • in reply to sued2

    Uninstall Sage 100 from the problem workstation, reboot, then reinstall (As Admin, with UAC off... using autorun.exe, not the MSI).  It could be the workstation software install was done incorrectly.

  • in reply to Kevin M

    I know that Suzanne has uninstalled/reinstalled at this workstation, but I will have her do a "redo" as Admin with no UAC.  We always use the autorun.exe so we're good there.  Thanks.

  • 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!  

  • I am very sorry to hear that recommendation that was passed along!  

    A suggestion for "file in use" or error #12 "file already exists or does not exist" would be to check antivirus exclusions, backup programs, etc. that might have file in use.  (you can also check LOCK folder in MAS90 for records related to AP_Invoice).  For antivirus, make sure they are excluding not only MAS90 folder on server but on workstations the C:\Program Files (x86)\Common Files\Sage\Common Components (on Sage 100 2019 or earlier) and C:\ProgramData\Sage\Common Components\ (Sage 100 2020+) as well as the C:\Program Files (x86)\SAP BusinessObjects\ (Crystal Reports) folder and if using Paperless Office the directory where the PDF files are saved.

    Was there an INFO button on that original "file is in user by another task"?  sometimes this will show "Error: 0 SY_Session.pvc 5997" which is due to Permissions on the Share or a possible corrupt file - (Knowledgebase article 105620) which suggests: 

    1. Verify users have Full or Change Share permissions on the Sage 100 share folder and Full or Modify NTFS permissions on the MAS90 folder
      NOTE: Review 'Sage 100 Security Permissions' section in the Sage 100 Installation Guide for more information on the minimum Sage 100 Share and NT File System permission settings
    2. Rename the following files located under ...\MAS90\MAS_System\ folder
      • SY_Workstation.m4t
      • SY_Console.m4t

    Renaming the SY_workstation.M4T might be a good general suggestion (unless the client is using a POS (Point of Sale) or cash-drawer type software which does not like that file renamed).  

    If all users are out of Sage 100 and the application server and C/S ODBC Printing service are closed (Advanced) - then if there are remaining PVXWIN32.exe tasks they may need to be closed (or server restarted - which also clears the OPEN FILES on the server).  

    I would also be curious if the original message indicated 'record ""' (with a blank value).

  • in reply to DGR

    Thank you for the information above.  That was very informative!  When this user gets the error, I can have another user go to their own workstation and update the register for her.  We have proven out it is definitely this users login on her workstation.  Their internal IT dept is going to redo her profile and then we'll give it a try again.  Thanks much.

  • in reply to DGR

    So bummer news...we just had another user get the same error when attempting to post the AP Invoice Register.  We were able to have yet a different user update the register.  I have sent your suggestions above to their IT tech to review.  So the story continues...  :-(

*Community Hub is the new name for Sage City