I get this same error when posting GL Batch Pcs start error 1361 GL JPST1.C in SQL version 2008 R2. Just installed Sage ERP 2014. Batch still posted correctly tho.

Looking forward to any responses out there!  Thanks

We have the same issue and the problem occurs daily. What causes the problem?

Improper system setup. I've been using this product for 17 years and never once seen that error.

Hi Jay
Thanks for the useful reply. We suspect that the cause is a tightening of security in the Windows OS but we can't diagnose the cause. We've also been doing this for over 20 years and this is the first time we have a recurring problem. By the way scanisam is a much neater way of fixing the restart.ism file. What I was looking for was something more helpful like the GLJPST.DLL file is damaged/missing or possibly that the anti-virus has quarantined a file. Does anyone perhaps have something more specific to look for?

Hi Jay
Thanks for the useful reply. We suspect that the cause is a tightening of security in the Windows OS but we can't diagnose the cause. We've also been doing this for over 20 years and this is the first time we have a recurring problem. By the way scanisam is a much neater way of fixing the restart.ism file. What I was looking for was something more helpful like the GLJPST.DLL file is damaged/missing or possibly that the anti-virus has quarantined a file. Does anyone perhaps have something more specific to look for?

Make the security rights to the SITE folder Full for Everyone.

"Internal error. pcsStart error" always points to a damaged restart.ism - no sense in looking for something different. Unless you're into wasting time looking at irrelevant stuff.

We have a group for ACCPAC that has full rights to the ACCPAC folder. Thanks for your help guys. If we find the actual cause I'll post it on the forum.

The root cause is newer versions of windows and the ancient SMB disk protocol that Accpac uses for multi-user access to the ISM files. Windows 10 and Server 2012 can be flaky with it.