GP & Lowercase Database IDs

Some days I feel like I’m on a game show, where troubleshooting is a contest… “I’ll take strange GP errors for $400 Alex!”.

Today is one of those days!

One of my clients imports in SOP and Payables transactions via eConnect and then uses Postmaster Enterprise to post the batches.  Today one of the QA users was doing some testing of GP and their integrations after a recent database refresh from the production company. She calls me and says something isn’t working right. Postmaster keeps logging posting errors but the batches look fine and nothing has changed except refreshing the environment.
Continue reading “GP & Lowercase Database IDs”

eConnect error, but not the real error!

One of my customers is doing some Sales Order Processing integrations with GP 2010… and for the most part, when we run into eConnect errors, it pretty much tells you what the issue is, and you fix it and move on.

We ran into one the other day and this error wasn’t even the real error, so it wasn’t until I looked at the XML they were trying to pass did I see what the real issue is.
Continue reading “eConnect error, but not the real error!”

eConnect error “configured identity is incorrect”

A client recently had an issue with their nightly eConnect integrations, getting an error about the username and password.

This integration had been live for nearly 2 years, running every night, and running without issue – or at least without this kind of issue. In other words, fairly stable.  They also never touch the service accounts, so the thought that the password might have been changed was nearly impossible.
Continue reading “eConnect error “configured identity is incorrect””

Scroll to top