Microsoft Dynamics GPI’ve seen this error at two different clients now when configuring Web Services for Microsoft Dynamics GP 2018:

A loader exception has occurred.
Loader Errors:
- System.Data.SqlClient.SqlException (0x80131904): There is already an object named 'taRequesterWSDynamicsOnlineConfiguration1' in the database.
   at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection, Action`1 wrapCloseInAction)
   at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj, Boolean callerHasConnectionLock, Boolean asyncClose)
   at System.Data.SqlClient.TdsParser.TryRun(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj, Boolean& dataReady)
   at System.Data.SqlClient.SqlCommand.RunExecuteNonQueryTds(String methodName, Boolean async, Int32 timeout, Boolean asyncWrite)
   at System.Data.SqlClient.SqlCommand.InternalExecuteNonQuery(TaskCompletionSource`1 completion, String methodName, Boolean sendToPipe, Int32 timeout, Boolean& usedCache, Boolean asyncWrite, Boolean inRetry)
   at System.Data.SqlClient.SqlCommand.ExecuteNonQuery()
   at Microsoft.Dynamics.InstallData.SqlObjectLoader.DoSqlFromResource(String resourceName)
   at Microsoft.Dynamics.GP.GPSystemWebServiceObjectLoader.PerformActionOnEConnectStoredProcedures(Action action)
   at Microsoft.Dynamics.InstallData.Loader.Process(String[] args)
ClientConnectionId:04c704d2-d12c-40f3-9ccc-1444c4b529d9
Error Number:2714,State:3,Class:16

Both clients have previously had the Web Services implemented so that they could use Email Actions for Workflow approval. The first client got the error while we were doing the initial installation and confguration of the Web Services for Microsoft Dynamics GP 2018 and the second got them when we did a redeploy of the Web Services on the test system after refreshing the databases, but hadn;t received the error during the initial installation and configuration.

The solution isn’t too cimplicated; there are (up to) three stored procedures which need to be deleted prior to the web services being configured:

SSMS

The three stored procedures which need to be deleted are:

  • taRequesterWSDynamicsOnlineConfiguration1
  • taRequesterWSDynamicsOnlineConfiguration2
  • taRequesterWSDynamicsOnlineConfiguration3

Once the stored procedures have been deleted, the configuration will run through without issue and will recreate the deleted stored procedures.

Read original post Error Configuring Web Services for Microsoft Dynamics GP 2018 at azurecurve|Ramblings of a Dynamics GP Consultant