x Want to participate? Join the group to interact
Options
  • State Not Answered
  • Replies 7 replies
  • Subscribers 45 subscribers
  • Views 4993 views
  • Users 0 members are here
Browse Forums
Announcements
68
topics
93
replies
Customization and Integration
262
topics
822
replies
Financials, Projects, and Administration
382
topics
843
replies
General Discussion
327
topics
836
replies
Installation and Technical Issues
335
topics
1k
replies
Manufacturing, Distribution, and Applications
341
topics
696
replies
Reporting and Analytics
123
topics
480
replies
Arxis

ERROR 13 OCCURRED AT FRMVOUCHER IN PROCEDURE SETMEMOSTATE TYPE MISMATCH

Posted By

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?

  • 0

    An error 13 usually indicates an error is occurring on the client and not the database.  This issue looks familiar however, I could not find a related knowledgebase article on the issue on Sage's site.  You may want to contact your reseller to get them involved in troubleshooting this issue or Sage Support.

  • 0

    Hi,

    It seems when User clicks "Next Number", the system somehow sets the focus to the lkuVendID control because the SetMemoState sub is called upon Vendor validation/lost focus. Do you have any customization with Customizer which sets the focus to the Vendor lookup field?

    Garik Melkonyan

    www.garikmelkonyan.com

  • 0 in reply to LouDavis

    We are actually the reseller.  Through troubleshooting we have not been able to replicate the issue so we have been unable to run a trace or determine the cause.  The error is very generic which doesn't help either.  Looking for any possible suggestions to further our troubleshooting.

    You mention that this appears to be an issue on the client but based on what has been reported, they are running a Citrix environment and this is the only user experiencing this issue.

  • 0 in reply to garmel

    They do not have any customizer customizations in AP.

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

*Community Hub is the new name for Sage City