Sage 100

EES 1.4 - Selecting Check Printing and Electronic Payment in AP results in and Error r#12: File does not exist (or already exists). No line or program name provided. Ruled out possible issues with Fixed Assets and Bank Rec. Anyone seen this? Is it possible a program file was deleted?

Any possibility that there is a file lock? A server reboot may remove the lock.

How did you rule out Fixed Assets? Since it's EES, you might want to look at this: http://infosource.sagesoftwareonline.com/sw_attach/kdb.asp?isresolutionconceptid=516324

Is it only when trying to print checks? Could a check form code have been deleted? Or the form itself?

Check code exists. Manual check printing (Quick Print) is working.

Happen in ABC company?

Ruled out Fixed Assets issue as not activated for company. Step #8 on document

Did this just start happening? Any other mods/changes recently?

Prior partner didn't install ABC company. Error happens in all companies. Check printing was working a week ago.

Was anyone trying to print using that form code on the server? It will mess up the form if the physical printer does not exist in the server printer settings.

Just started. Not aware of any changes. Log shows nothing unusual. No third party mods.

Does it happen for all users or just one?

@alanniergarth may have a point - an invalid printer.

And so might @JeffSchwenk. Is it all workstations?

MAS 200 client is running on terminal server. This past weekend the IT vendor moved all servers (MAS200 and terminal server) from Hyper-V to VMWare. EES 1.3 also installed on servers and able to print checks. Trying XYZ company.

Happens in all terminal server logins.

Yes, it happens in ABC company.

Did a refresh install to alternate location and replaced the AP folder still have error message.

Just a thought...when you get the error - if you go into the Debug isn't' there a ? pgm command (not sure if that's exaclty it) you can type in to tell you the program that's being accessed? Or, if you recreate the error with no one else in - then check the system files, can you tell by the time stamp which file was being accessed?

No Debug button. Just the error with an OK button.

Checked open files. Check file not in use.

Did you reboot the server?

Weill reboot this evening.

Does the SY_Module table have any strange looking records?

Nothing unusual in SY_Module.

Did you try running it in MAS90 mode and see if the error shows differently?. Try it on the server

Just tried it. Ran in MAS 90 mode and same error.

Restart of server didn't resolve.

My guess is that it is related to permissions. Permission are a bear on new servers. Make sure the mas90 folder are shared properly, also what about printers. Make sure all the printers are valid

Also if you put mas into debug mode does it allow escaping?

Found this but not very helpful. http://infosource.sagesoftwareonline.com/sw_attach/kdb.asp?isresolutionconceptid=478639

RESOLUTION - Make a copy of the ACTIVATE.PVX file, reinstall AP module (just the AP module), install SU to previously installed level and then restore the ACTIVATE.PVX file. This resolved the error. It wasn't rights, printers, forms, Crystal DLLs, in use files or any of the other half of dozen things I tried.