Added new application server after creating a database and receive endpoint address failure

Epicor ERP 10
1

After navigating to the administrative console and completing the following I received the endpoint error below?

  1. Open Epicor Administrative Console as admin (logged into windows account as domain admin)
  2. Right clicked SQL server under “Database server management” and created a new database called “EpicorPOC10”
  3. Database was generated correctly and shows up under “database server management”
  4. Right clicked server instance under “server management” and clicked “add application server”
  5. on the first window I specified “EpicorPOC10” gave the IIS a custom user account we use
  6. 2nd page for database connection was used a SQL authentication and tested ok
  7. Linked SSRS database and tested ok
  8. Deployed action worked fine and all jobs gave green check mark.
  9. Clicked on new application server and following error is presented?

The message could not be dispatched because the service at the endpoint address System.ServiceModel.EndpointNotFoundException: The message could not be dispatched because the service at the endpoint address ‘net.tcp://rase10prod/EpicorPOC10/Ice/BO/UserFile.svc’ is unavailable for the protocol of the address.

Server stack trace:

at System.ServiceModel.Channels.ConnectionUpgradeHelper.DecodeFramingFault(ClientFramingDecoder decoder, IConnection connection, Uri via, String contentType, TimeoutHelper& timeoutHelper)

at System.ServiceModel.Channels.ClientFramingDuplexSessionChannel.SendPreamble(IConnection connection, ArraySegment`1 preamble, TimeoutHelper& timeoutHelper)

at System.ServiceModel.Channels.ClientFramingDuplexSessionChannel.DuplexConnectionPoolHelper.AcceptPooledConnection(IConnection connection, TimeoutHelper& timeoutHelper)

at System.ServiceModel.Channels.ConnectionPoolHelper.EstablishConnection(TimeSpan timeout)

at System.ServiceModel.Channels.ClientFramingDuplexSessionChannel.OnOpen(TimeSpan timeout)

at System.ServiceModel.Channels.CommunicationObject.Open(TimeSpan timeout)

at System.ServiceModel.Channels.SecurityChannelFactory1.ClientSecurityChannel1.OnOpen(TimeSpan timeout)

at System.ServiceModel.Channels.CommunicationObject.Open(TimeSpan timeout)

at System.ServiceModel.Channels.ServiceChannel.OnOpen(TimeSpan timeout)

at System.ServiceModel.Channels.CommunicationObject.Open(TimeSpan timeout)

at System.ServiceModel.Channels.CommunicationObject.Open()

Exception rethrown at [0]:

at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg)

at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type)

at System.ServiceModel.ICommunicationObject.Open()

at Epicor.ServiceModel.Channels.ChannelEntry`1.CreateNewChannel()

at Epicor.ServiceModel.Channels.ImplBase`1.GetChannel()

at Epicor.ServiceModel.Channels.ImplBase`1.HandleContractBeforeCall()

at Ice.Proxy.BO.UserFileImpl.IsPasswordExpired(String userID, Int32& graceCount)

at Epicor.Mfg.Administration.ServerManagement.ApplicationServerManager.Forms.NewSessionForm.BackgroundWorker_DoWork(Object sender, DoWorkEventArgs e)

at System.ComponentModel.BackgroundWorker.OnDoWork(DoWorkEventArgs e)

at System.ComponentModel.BackgroundWorker.WorkerThreadStart(Object argument)

2

Check your application pool and make sure your pool is running and that your custom account is specified.

3

Attached is the current console display and I have stopped and started the IIS pool for the Epicor POC 10 but when i go select connect to application server i keep getting the same error.

Error.PNG909×637 44.3 KB

Error1.PNG816×710 21.4 KB

4

I did find one mistake i made was the web site directory was wrong and needed to be pointed to the E drive and after another deployment i received the same error again.

5

I noticed your binding is Windows. Is that what your other application servers are using. Are you setup correctly to use that binding? You have plenty of available memory on this server, correct?

6

That is my fault its supposed to be “usernamewindowschannel” as the others are setup that way. And the server has 80GB of RAM. Sorry for the older confusing screenshot. I mocked up the new application server as the other existing servers that have worked for some time. There must be something small I am missing

7

I would triple check the username / password you have. If you can I would IISRESET or reboot the machine. Typically, I have found this error to be related to the user I specified.

8

Thanks ill check around.

9

Yep you were right it was user account credentials. Had to run appcmd.exe list apppool <<app_pool_name>> /text:* to find the IIS password for the pool.

1 Like
10

So glad to see RAS using this great resource here. So you guys will have me a 10.1.600 with REST test server spun up in no time :wink: