Sage 300

Sage 300 2014 creation of a new GL batch is today often but not always timing out. It appears on several occasions that it incremented the next GL batch by 2 instead of one. All while desperately trying to get 2016 closed, of course. Deleting the xxx_P.ism files did not help.

Are there any other tasks going on when you are trying to create the batch?

It even happened to the admin when I had everyone out to try deleting the _P.ism files

Phil, it's not really the *_P.ism files that control that function. Those files hold the printing configuration for the user bu each UI. Each posting attempt creates a record in the restart.ism in the site folder. Perhaps you have corruption in that file or another of the ISM files. Run the SCANISM utility to see if any record shows up bad.

It did fix restart.ism and I think that did it, but I can't be sure because it did sometimes work today...

in some of the older versions of Sage 300 the ism files were flaky. We used to run scanism at least monthly and that's the most often we ever ran any data utility of Sage's.

Argghh..not the fix..Sage support suggests reinstalling GL - waiting for everyone to get out of the system...

reinstalling and applying latest service pack did not fix either, and it does not appear to happen in a history company. Are we looking at another dump & load?

Phil - I don't think DUMP and LOAD will fix this issue. I would contact Bob @ Musick International (http://www.musick-int.com/). If anyone knows about this issue, it would be them. IO just haven't seen or heard about this type of issue before.