GP 2010 Web Services error: There was no endpoint listening at at http://server:48620/Dynamics/GPService

A partner recently asked me to help them troubleshoot a Dynamics GP 2010 Web Services error that they were receiving:

There was no endpoint listening at http://server:48620/Dynamics/GPService that could accept the message.

I've previously written about an eConnect 2010 error message that looks very similar.  In the case of eConnect 2010, you simply make sure the eConnect windows service is started.

But in this case, we checked the Windows services, and both eConnect 2010 Integration Service and the Microsoft Dynamics GP Service Host were both running.  There were no errors in the Event Viewer or the Dynamics GP Web Services Exceptions Console.

The partner had contacted GP support, and was asked to open the Dynamics Security Console to perform a test.  They recommended trying to add a Customer Entity ID Assignment, to see if customer IDs were listed in the window.  But when the partner tried to add the Entity ID assignment, the Company drop down list was empty.  This was the first clue.

This is what the Entity ID Assignment window should look like:

Once you select a Windows user, Entity Type, and Company, a list of IDs should appear.  But they couldn't even select a Company.

To try and diagnose the issue further, I installed GP 2010 Web Services on one of my servers and whipped up a test application that would use GP Web Services to retrieve customers, vendors, items, and accounts.  We could then use this app on different machines to see if it was a network issue or a problem with Web Services.

The partner tried my test application, and it didn't even work on the GP server where Web Services was installed, so that ruled out a network issue.

I then tried the Entity ID Assignment test on my server, and it worked fine.  The Fabrikam company was listed and I was able to see a list of customers. (as shown above)

So this told us that the problem was likely with the installation or configuration of Web Services.

I then asked the partner to try launching the GP Web Services Configuration Wizard to see if web services had been configured for the Fabrikam company.  When they launched the Configuration Wizard, no companies were listed.  They were unable to even proceed with the configuration or repair.

The window should list a company like this:

That pretty much told us that there was something wrong with the Web Services installation, and I recommended that they try completely uninstalling and reinstalling, making sure to follow the install guide step by step.

Once Web Services was reinstalled, things worked properly and their Web Services integration started working.

Steve Endow is a Dynamics GP Certified Trainer and Dynamics GP Certified IT Professional in Los Angeles.  He is also the owner of Precipio Services, which provides Dynamics GP integrations, customizations, and automation solutions.

http://www.precipioservices.com