eConnect Error: Cannot Find a Stored Procedure in the Microsoft Dynamics GP Database

Hello:

When using eConnect for GP 2010 to import Project Accounting projects into the Project Cards, I get an error that says, "The stored procedure taPAProjects doesn't exist."

But, we took a look in the company database in SQL.  Indeed, this stored procedure is there.  How can we convince eConnect of that?

Thanks!  Much appreciated!

TBSupport
LVL 1
TBSupportAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Steve EndowMicrosoft MVP - Dynamics GPCommented:
Hi,

I have run into this error before.

There are three possible reasons that I'm aware of for this error, and there may be others.  Do you have any other eConnect integrations that work properly for this particular database?


First, you should output / display your eConnect connection string to double check that you are sending the correct SQL instance name and correct database name.

Data Source=SERVERNAME;Initial Catalog=COMPANYDB;Integrated Security=SSPI


Next, verify that the company database DYNGRP role includes EXEC access to the stored procedure


If that looks correct, open SQL Server Management Studio, expand Security -> Logins and locate the eConnect login, then double click on the eConnect login.

Select the User Mapping page.  Verify that the Default Schema is set to "dbo" for all of the mapped GP databases.  If there is a Default Schema other than dbo for any of the databases, you will need to delete the eConnect user schema from all databases, and then delete the eConnect SQL login.  You can then re-created the eConnect login and users, making sure that the Default Schema is dbo.

Please let me know one of these seems relevant to your issue.

Thanks,

Steve Endow
Dynamics GP Certified Trainer
Dynamics GP Certified IT Professional
eConnectLoginSchema.jpg
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
TBSupportAuthor Commented:
Hi Steve:

Yes, the client did not have the correct DSN being used.  Therefore, I was not connecting to the correct server nor the correct database.

Thanks, so much!

TBSupport
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft Dynamics

From novice to tech pro — start learning today.