web
You’re offline. This is a read only version of the page.
close
Skip to main content

Notifications

Announcements

No record found.

News and Announcements icon
Community site session details

Community site session details

Session Id :
Dynamics 365 Community / Forums / Microsoft Dynamics AX (Archived) / The communication obje...
Microsoft Dynamics AX (Archived)

The communication object, System.ServiceModel.Channels.ServiceChannel, cannot be used for communication because it is in the Faulted state.

(0) ShareShare
ReportReport
Posted on by Peter Chan 125

Product: Dynamics AX 2012 R3, Retail Online Channel

Path: Online channel site > Sign in > Account > View all orders

Issue details: A few seconds ago, the "View all orders" works fine, but after restarted the IIS, the error occur. Restarting the IIS & AOS several times, didn't helps either. But after a period of time (without touching anything), hit F5 to refresh the page, it works again.

Stack trace:

  • We cannot process your request at this time. Please try again later.
  • Error Code:
  • Source: Microsoft.Dynamics.Commerce.Runtime
  • Message Detail: Exception while calling invoke method SearchOrderList: The communication object, System.ServiceModel.Channels.ServiceChannel, cannot be used for communication because it is in the Faulted state.
  • Stack Trace: at Microsoft.Dynamics.Commerce.Runtime.TransactionService.TransactionServiceClient.GetResponseFromMethod(String methodName, Object[] parameterList, Boolean useExtensionMethod)
    at Microsoft.Dynamics.Commerce.Runtime.TransactionService.TransactionServiceClient.InvokeMethod(String methodName, Object[] parameters)
    at Microsoft.Dynamics.Commerce.Runtime.TransactionService.TransactionServiceClient.SearchOrders(SalesOrderSearchCriteria criteria, Int32 maxTransactionSearchResults)
    at Microsoft.Dynamics.Commerce.Runtime.Services.SalesOrderService.GetOrders(GetOrdersServiceRequest request)
    at Microsoft.Dynamics.Commerce.Runtime.Services.SalesOrderService.ExecuteRequest[TResponse](ServiceRequest request)
    at Microsoft.Dynamics.Commerce.Runtime.Services.Service.Execute[TResponse](ServiceRequest request)
    at Microsoft.Dynamics.Commerce.Runtime.Workflow.GetOrdersRequestHandler.Process(GetOrdersRequest request)
    at Microsoft.Dynamics.Commerce.Runtime.Workflow.WorkflowRequestHandler`2.Execute(RequestContext context)
    at Microsoft.Dynamics.Commerce.Runtime.Workflow.Composition.PipelineRequestHandler.Execute(RequestContext context)
    at Microsoft.Dynamics.Commerce.Runtime.CommerceRuntime.Execute[T](Request request)
    at Microsoft.Dynamics.Commerce.Runtime.Client.OrderManager.SearchOrders(QueryResultSettings settings, SalesOrderSearchCriteria criteria)
    at Microsoft.Dynamics.Commerce.Runtime.Client.OrderManager.GetOrdersByCustomer(QueryResultSettings settings, String customerAccountNumber)
    at Microsoft.Dynamics.Retail.SharePoint.Web.Services.ObjectModel.OrderController.GetSalesOrdersByCustomer(String accountNumber)
    at Microsoft.Dynamics.Retail.SharePoint.Web.Services.OrderService.<>c__DisplayClass1.b__0(String accountNumber)
    at Microsoft.Dynamics.Retail.SharePoint.Web.Services.ObjectModel.ServiceHelper.<>c__DisplayClass7.b__4()
    at Microsoft.Dynamics.Retail.SharePoint.Web.Services.ObjectModel.ServiceHelper.<>c__DisplayClass2.b__0()
    at Microsoft.SharePoint.SPSecurity.<>c__DisplayClass5.b__3()
    at Microsoft.SharePoint.Utilities.SecurityContext.RunAsProcess(CodeToRunElevated secureCode)
    at Microsoft.SharePoint.SPSecurity.RunWithElevatedPrivileges(WaitCallback secureCode, Object param)
    at Microsoft.SharePoint.SPSecurity.RunWithElevatedPrivileges(CodeToRunElevated secureCode)
    at Microsoft.Dynamics.Retail.SharePoint.Web.Services.ObjectModel.ServiceHelper.Execute(ServiceResponse response, ServiceExecutionHandler executionHandler)

*This post is locked for comments

I have the same question (0)
  • Brandon Ahmad Profile Picture
    Brandon Ahmad 2,465 User Group Leader on at

    Very interesting.  I hate guessing on these without being able to actually debug myself, but let me give it a try here based upon what I see.  

    So, when a service goes into a faulted state it means that it can't be used because it has an open connection to whatever it is trying to connect with in this case or we say unhandled exception.  

    You also reported the error as occurring immediately after doing an IIS restart but working after a few minutes.  

    That would make sense because when you restart IIS, the application pools have to start up also and that takes some time.  There are also configurations for websites within AX that follow the same principle.  Many websites will only start when they are accessed the first time after the app pool starts up.  Thus, all the powershell scripts floating around the web with a warmup period or autostart option to change this mechanism.  

    I'd look here based upon the way that you describe the problem:

    msdn.microsoft.com/.../ee677285(v=azure.10).aspx

    You can also easily see timeout faults by turning on logging for the service.  That would confirm the issue -- to either wait for everything to start after rebooting IIS or use a powershell warmup script if everything doesn't start.

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Responsible AI policies

As AI tools become more common, we’re introducing a Responsible AI Use…

Neeraj Kumar – Community Spotlight

We are honored to recognize Neeraj Kumar as our Community Spotlight honoree for…

Congratulations to the November Top 10 Community Leaders!

These are the community rock stars!

Leaderboard > 🔒一 Microsoft Dynamics AX (Archived)

#1
Martin Dráb Profile Picture

Martin Dráb 4 Most Valuable Professional

#1
Priya_K Profile Picture

Priya_K 4

#3
MyDynamicsNAV Profile Picture

MyDynamicsNAV 2

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans