x Want to participate? Join the group to interact

Sage 500

Welcome to the Sage 500 Support Group on Community Hub! Available 24/7, the Forums are a great place to ask and answer product questions, as well as share tips and tricks with Sage peers, partners, and pros.

Customization and Integration Sage 500 Upgrade - Error 13

Options

State Suggested Answer
Replies 17 replies
Answers 1 answer
Subscribers 46 subscribers
Views 11769 views
Users 0 members are here

Browse Forums

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

Sage 500 Upgrade - Error 13

SUGGESTED

Posted By Mykidz9598 over 10 years ago

upon trying to save an invoice I am receiving this error in my testing of Sage 500 2013:

Module: Company: TT1 AppName: ProcessInvoices Error <13> occurred at <frmInvcEntry> in Procedure <DMPostSave> Type mismatch.

happens on each and every invoice. Could anyone please advise?

Thank you.

Top Replies

KateRKL over 1 year ago in reply to jim_braun +1 suggested

We ran into this issue with a customer from Sweden. The resolution was to make sure the Region and the Unicode Language was set to English (USA)

Parents

0 jim_braun over 8 years ago

When I get this Error, I uninstall and reinstall the Avatax Client as Admin on the Client and the problem is fixed. Do you have any HotFixes from Avalera that you install?
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

Reply

0 jim_braun over 8 years ago

When I get this Error, I uninstall and reinstall the Avatax Client as Admin on the Client and the problem is fixed. Do you have any HotFixes from Avalera that you install?
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

Children

0 KateRKL over 1 year ago in reply to jim_braun

SUGGESTED

We ran into this issue with a customer from Sweden. The resolution was to make sure the Region and the Unicode Language was set to English (USA)
Cancel
Vote Up +1 Vote Down

Sign in to reply

Verify Answer

Reject Answer

Cancel