Errors using the eConnect Transaction Requestor

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.


 
 
 

Related Articles

... and you 'll find more on the eConnect Menu

I'm not given to long explanations, I'll cut right to the chase:

In order to replace the missing stored procedures, navigate to

C:Program Files (x86)\Microsoft Dynamics\eConnect 14.0\Custom Procedures\Requester

Run every stored procedure in this folder, it will replace all the missing lines in eConnect_out_setup.

Then, run this code:

 

set nocount on
declare @NAME varchar(100)
declare @TEXT varchar(8000)
declare @a int
declare @t varchar(1)
 
declare taCreateRequesterProcs insensitive cursor for
    select  DOCTYPE
        from eConnect_Out_Setup (nolock)
        where MAIN = 1
            and DOCTYPE not like '%GetList'
 
open taCreateRequesterProcs
while 1 = 1
begin
    fetch next from taCreateRequesterProcs into @NAME
    if @@fetch_status <> 0 begin
        break
    end
 
    set @a = 0
    while @a < 3 begin
        set @t = @a
        select @TEXT = 'if exists (select 1 from information_schema.routines where routine_name = ' + quotename('tarequester' + @name + @t,char(39))  + ' ) drop procedure taRequester' + @NAME + @t
        print @text
        exec (@TEXT)
        --this is the money line. This sproc will create the 'taRequester' procs that we're missing
        select @TEXT = 'exec eConnectOutCreate '+ @NAME + ', ' + @t
        print @text
        exec (@TEXT)
 
        set @a = @a + 1
    end
end
close taCreateRequesterProcs
deallocate taCreateRequesterProcs

As a side note, when I started my demo db had 332 taRequester procs and when the code above finished I had 475. Not all the lines in eConnect_out_setup had three taRequester procs. I don't know the logic there... so I created them all. Didn't seem to hurt.

 

 

RealWorldCode gives developers practical, real‑world solutions with clean, working code — no fluff, no theory, just answers.
Links
Home
Knowledge Areas
Sitemap
Contact
Et cetera
Privacy Policy
Terms and Conditions
Cookie Preferences