Errors using the eConnect Transaction Requestor

* This article, and all our great eConnect documentation, Is available on the eConnect menu

I love my job. Really. Every day is something new.

Yesterday a major ISV contacted us for help with what appeared to be a failed eConnect install, they were using the Transaction Requestor functionality in eConnect to get data about a Vendor in GP and it was failing with an odd error. I've seen a great number of eConnect errors <smiles>, this one was new.

The error said (in part):

Error getting Vendor for vendor ID '<vendor name>': The specified schema name "dbo" either does not exist or you do not have permission to use it.
Cannot find the object 'raRequesterVendor2', because it does not exist or you do not have permission.
Could not find stored procedure 'dbo.taRequesterVendor2'

During the troubleshooting, we discovered that the eConnect_out_setup table had only 1 line. It should have around 500. In our case, it only had the Cash_Receipt line, which is the first one in our demo install.

There should also be two or three stored procedure in the database that start with 'taRequester' for each line in eConnect_out_setup. We had only three, the three that go with Cash_Receipt: taRequesterCash_Receipt0, taRequesterCash_Receipt1, taRequesterCash_Receipt2.

This article discusses how to troubleshoot and repair this failed eConnect install.