Still celebrating National IT Professionals Day with 3 months of free Premium Membership. Use Code ITDAY17

x
?
Solved

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

Posted on 2013-06-23
2
Medium Priority
?
798 Views
Last Modified: 2013-06-25
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
0
Comment
Question by:TBSupport
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
2 Comments
 
LVL 18

Accepted Solution

by:
Steve Endow earned 2000 total points
ID: 39269545
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
 
LVL 1

Author Comment

by:TBSupport
ID: 39274803
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

Featured Post

Prepare for your VMware VCP6-DCV exam.

Josh Coen and Jason Langer have prepared the latest edition of VCP study guide. Both authors have been working in the IT field for more than a decade, and both hold VMware certifications. This 163-page guide covers all 10 of the exam blueprint sections.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

This is a walkthrough guide I wrote whilst upgrading my on-premise MS Dynamics CRM 3.0 deployment to 4.0. This covers the actual installation of the product to a working level for my system, I ran into a lot of issues that the steps below fixed so h…
Desired Skill Set for Microsoft Dynamics CRM Technical Resources – Part I
Video by: ITPro.TV
In this episode Don builds upon the troubleshooting techniques by demonstrating how to properly monitor a vSphere deployment to detect problems before they occur. He begins the show using tools found within the vSphere suite as ends the show demonst…
This is my first video review of Microsoft Bookings, I will be doing a part two with a bit more information, but wanted to get this out to you folks.

715 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question