System.ServiceModel.Channels.ServiceChannel Faulted State

Andy_Smith · 2012-11-14

I have a 2009R2 (Build 32012) client that has started getting the following error:
(Edit: forgot to mention, she's using the role tailored client)

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

Which crashes her out of NAV. According to the client this is happening randomly, but it appears to be only happening to one user on one workstation. I've got their IT staff checking the computer in question, but was curious if anybody else had seen this error with NAV and had any insight. I've seen from googling the terms "System.ServiceModel.Channels.ServiceChannel Faulted state" that there are a few MSDN articles that talk about how this error occurs in the WCF service with C# or .NET code that is improperly formulated, but it isn't clear how this applies to Navision.

plc5700 · 2012-12-20

Hi

I have a similar problem - did you ever find a solution for this?

tinoruijs · 2014-03-25

I'm getting this message in the Development Enviroment since I installed build 36281 on NAV2013R2.
Maybe because I'm developing on another server than where the servicetier is installed.

ara3n · 2014-03-25

the service tier and cc have to be on same box

Arndt_Loermann · 2014-03-26

with the Hotfix 2934572, Build 36310 after Rollup 5 for NAV 2013 R2 is it possible now again to develop over 3 machines

request: https://support.microsoft.com/hotfix/KB ... um=2934572

tinoruijs · 2014-03-26

Thanks.

tinoruijs · 2014-03-26

ara3n wrote:

the service tier and cc have to be on same box

cc?

ara3n · 2014-03-26

the classic client , also known as development client.

tinoruijs · 2014-03-26

ara3n wrote:

the classic client , also known as development client.

Off course.

Never saw or used the abbreviation. Strange, because rtc is used often. :-k

Rob_Hansen · 2014-03-29

We have build 36310 installed and are still getting the "System.ServiceModel.Channels.ServiceChannel cannot be used for communication because it is in the Faulted state" error when trying to save/compile table changes. We have the service tier on a separate machine from the development environment, but with build 36310 this should work. Does anyone know what steps we should take to diagnose/address this?

Rob_Hansen · 2014-03-31

I contacted Microsoft about this and they are aware that not all scenarios with the ServiceChannel faulted state issue have been fixed. They are working on it.

eYe · 2014-04-17

Still an issue on Cumulative Update 6 (Build 36366) too

Sasa · 2014-04-24

There is one "solution" for this - you need to be only user on database when compiling objects...

Rob_Hansen · 2014-04-24

That doesn't work for me. I have a database for a new implementation where I've been the only person using it to this point and I get the faulted state error when compiling/saving tables unless I have the option turned off to prevent data loss from table changes. Still haven't heard any more from Microsoft on this one.

Sasa · 2014-04-24

rdhansen wrote:

That doesn't work for me. I have a database for a new implementation where I've been the only person using it to this point and I get the faulted state error when compiling/saving tables unless I have the option turned off to prevent data loss from table changes. Still haven't heard any more from Microsoft on this one.

You can try to add Management Service Port to Firewall as enabled port, this going to do the trick...

eYe · 2014-04-25

Tried it, no luck. Even tried it with firewall disabled

ycman · 2014-05-12

Tools - Options - Prevent data loss from table changes set to No
try after

deV.ch · 2014-05-16

ycman wrote:

Tools - Options - Prevent data loss from table changes set to No
try after

You should do that only as a last resort! It can create more problems then is solves...

We had the same issue but with the newest builds we have no issues anymore. If you still have issues i would say there is some wrong configuration, maybe management port not activated?

vaprog · 2014-05-19

Sasa wrote:

You can try to add Management Service Port to Firewall as enabled port, this going to do the trick...

Yes \:D/ , that did the trick for me.

Rob_Hansen · 2014-05-20

That worked for us as well. Now...why couldn't Microsoft tell us that? When I reported the ongoing issue they just said they were aware of it and did not have a resolution yet. Frustrating...

Joe_Mathis · 2014-06-25

Adding the port to the firewall didn't make a difference for me, but specifying the management port in the options did.

Hope it helps someone...

abinashphuel · 2015-03-03

This error occur because of change madein the objectes. Like adding some fields, changing name or size of fields.
Solution: Compile the objects especially table.

yedi · 2015-11-16

Awesome! adding the port did the trick. Thanks a lot!!

System.ServiceModel.Channels.ServiceChannel Faulted State

Comments

Categories