ERROR 13 OCCURRED AT FRMVOUCHER IN PROCEDURE SETMEMOSTATE TYPE MISMATCH

MAS500 V7.4

ONE USER IS GETTING THIS ERROR MESSAGE WHEN SHE OPENS THE AP VOUCHER ENTRY AND CLICKS "NEXT" VOUCHER NUMBER. 

IT APPEARS THAT THE VOUCHER NUMBER SHOULD BE ASSIGNED A NUMBER WITH A LEADING ZERO BUT THE ENTRIES THAT ERROR OUT DO NO HAVE A LEADING ZERO. 

THIS HAS NOT BEEN ABLE TO BE REPLICATED SO WE CANNOT DETERMINE WHEN TO RUN A TRACE. 

THIS HAPPENS QUITE OFTEN FOR THIS ONE USER BUT THERE IS NO PATTERN TO WHEN IT HAPPENS OR WHAT CAN BE CAUSING IT.

USER IS ACCESSING THROUGH A CITRIX ENVIRONMENT

NO CUSTOMIZATIONS IN AP

ANY SUGGESTIONS?

Parents Reply Children
  • 0 in reply to Arxis

    Have you tried deleting the Citrix profile and allowing it to rebuild?

    We get these weird issues in Windows Terminal Server from time to time and it's always user-specific. Deleting the user profile on the terminal server always solves the problem. The next time they login, the profile rebuilds. I'm not sure if Citrix works the same way though.

  • 0 in reply to Tim Rodman

    Sage has seen this issue occur on v.2013 with the July 2013 PU.  Unfortunately we don't have steps to duplicate this issue either, nor do we have a resolution at this time.  Please let us know if any of the suggestions work.  

    Thanks,

    Jennifer Pitt

  • 0 in reply to Jennifer Pitt

    I just saw this issue with another client who is running v.7.30. They have ALTEC's doc-Link integration in Process Vouchers. As soon as I disabled the Customizer settings used by doc-Link the issue went away. The odd thing is that there have been no recent changes to these Customizer settings and the client has been running fine for years. Color me confused!