Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Add WCF Faulted EventHandler for automatic recovery from communication object faulted state #217

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
ddemeyer merged 4 commits into from
Oct 16, 2025
Merged

Add WCF Faulted EventHandler for automatic recovery from communication object faulted state #217

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
9bda2a2
Initial plan
Copilot Oct 2, 2025
d7744c4
Add WCF Faulted EventHandler for automatic recovery from communicatio…
Copilot Oct 2, 2025
23c0993
Address PR feedback: improve debug logging and clean up README
Copilot Oct 2, 2025
7f4c03f
#214 Mostly implemented by copilot although theoretical leading to PS…
ddemeyer Oct 15, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 0 additions & 4 deletions README.MD
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -65,10 +65,6 @@ Any feedback is welcome. Please log a GitHub issue, make sure you submit your ve
* If a `New-IshSession -IshUserName ...` results in `System.ServiceModel.FaultException` followed by `An error occurred when verifying security for the message.`, then you are using `-Protocol WcfSoapWithWsTrust` implicitly. A very likely candidate is that deprecated `/ISHSTS/` which authenticates the WS-Federation protocol was not part of your certificate rollover. A simple workaround is to stop the ISHSTS IIS App Pool, delete `\Web\InfoShareSTS\App_Data\IdentityServerConfiguration-2.3.sdf` and in turn start the IIS App Pool again - which will regenerate the local .sdf database.
* If you get `You cannot call a method on a null-valued expression.` or `The HTTP status code of the response was not expected (401).`, probably while using `$ishSession.OpenApiISH30Client` it means your token expired and requires a refresh.
* If you get `New-IshSession : Reference to undeclared entity 'raquo'. Line 98, position 121.`, most likely you specified an unexisting "Web Services API" url. Make sure your url ends with an ending slash `/`.
* If a test fails with `The communication object, System.ServiceModel.Channels.ServiceChannel, cannot be used for communication because it is in the Faulted state.`,
it probably means you didn't provide enough (mandatory) parameters to the WCF/SVC code so passing null parameters. Typically an `-IshPassword` is missing or using an existing username.
* ISHDeploy `Enable-ISHIntegrationSTSInternalAuthentication/Disable-ISHIntegrationSTSInternalAuthentication` adds a /ISHWS/Internal/connectionconfiguration.xml that a different issuer should be used. As ISHRemote doesn't have an app.config, all the artifacts are derived from the RelyingParty WSDL provided mex endpoint (e.g. /ISHSTS/issue/wstrust/mex).
If you get error `New-IshSession : The communication object, System.ServiceModel.Channels.ServiceChannel, cannot be used for communication because it is in the Faulted state.`, it probably means you initialized `-WsBaseUrl` without the `/Internal/` (or `/SDL/`) segment, meaning you are using the primary configured STS.

# Standards To Respect

Expand Down
Loading
Loading