/
System.ServiceModel.txt
2384 lines (2373 loc) · 316 KB
/
System.ServiceModel.txt
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
767
768
769
770
771
772
773
774
775
776
777
778
779
780
781
782
783
784
785
786
787
788
789
790
791
792
793
794
795
796
797
798
799
800
801
802
803
804
805
806
807
808
809
810
811
812
813
814
815
816
817
818
819
820
821
822
823
824
825
826
827
828
829
830
831
832
833
834
835
836
837
838
839
840
841
842
843
844
845
846
847
848
849
850
851
852
853
854
855
856
857
858
859
860
861
862
863
864
865
866
867
868
869
870
871
872
873
874
875
876
877
878
879
880
881
882
883
884
885
886
887
888
889
890
891
892
893
894
895
896
897
898
899
900
901
902
903
904
905
906
907
908
909
910
911
912
913
914
915
916
917
918
919
920
921
922
923
924
925
926
927
928
929
930
931
932
933
934
935
936
937
938
939
940
941
942
943
944
945
946
947
948
949
950
951
952
953
954
955
956
957
958
959
960
961
962
963
964
965
966
967
968
969
970
971
972
973
974
975
976
977
978
979
980
981
982
983
984
985
986
987
988
989
990
991
992
993
994
995
996
997
998
999
1000
#if INCLUDE_RUNTIME
MessageVersionToStringFormat={0} {1}
Addressing10ToStringFormat=Addressing10 ({0})
;Addressing200408ToStringFormat=Addressing200408 ({0})
AddressingNoneToStringFormat=AddressingNone ({0})
Soap11ToStringFormat=Soap11 ({0})
Soap12ToStringFormat=Soap12 ({0})
EnvelopeNoneToStringFormat=EnvelopeNone ({0})
MessageBodyIsUnknown=...
MessageBodyIsStream=... stream ...
#endif // INCLUDE_RUNTIME
#if INCLUDE_DEBUG
;NoIPEndpointsFoundForHost=No IPEndpoints were found for host {0}.
;DnsResolveFailed=No DNS entries exist for host {0}.
;RequiredAttributeMissing=Attribute '{0}' is required on element '{1}'.
;UnsupportedCryptoAlgorithm=Crypto algorithm '{0}' not supported in this context.
;NoKeyInfoClausesToWrite=The SecurityKeyIdentifier has no key identifier clauses to write.
;TokenSerializerNotSetonFederationProvider=The security token serializer must be specified on the security token provider.
;IssuerBindingNotPresentInTokenRequirement=The key length '{0}' is not a multiple of 8 for symmetric keys.
;IssuerChannelBehaviorsCannotContainSecurityCredentialsManager=The channel behaviors configured for the issuer address '{0}' cannot contain a behavior of type '{1}'.
;SecurityTokenManagerCannotCreateProviderForRequirement=The security token manager cannot create a token provider for requirement '{0}'.
;SecurityTokenManagerCannotCreateAuthenticatorForRequirement=The security token manager cannot create a token authenticator for requirement '{0}'.
;FailedSignatureVerification=The signature verification failed. Please see inner exception for fault details.
;SecurityTokenManagerCannotCreateSerializerForVersion=The security token manager cannot create a token serializer for security token version '{0}'.
;SupportingSignatureIsNotDerivedFrom=The supporting signature is not signed with a derived key. The binding's supporting token parameter '{0}' requires key derivation.
;PrimarySignatureWasNotSignedByDerivedKey=The primary signature is not signed with a derived key. The binding's primary token parameter '{0}' requires key derivation.
;PrimarySignatureWasNotSignedByDerivedWrappedKey=The primary signature is not signed with a key derived from the encrypted key. The binding's token parameter '{0}' requires key derivation.
;MessageWasNotEncryptedByDerivedWrappedKey=The message is not encrypted with a key derived from the encrypted key. The binding's token parameter '{0}' requires key derivation.
;MessageWasNotEncryptedByDerivedEncryptionToken=The message is not encrypted with a key derived from the encryption token. The binding's token parameter '{0}' requires key derivation.
;TokenAuthenticatorRequiresSecurityBindingElement=The security token manager requires the security binding element to be specified in order to create a token authenticator for requirement '{0}'.
;TokenProviderRequiresSecurityBindingElement=The security token manager requires the security binding element to be specified in order to create a token provider for requirement '{0}'.
;UnexpectedSecuritySessionCloseResponse=The security session received an unexpected close response from the other party.
;UnexpectedSecuritySessionClose=The security session received an unexpected close from the other party.
;CannotObtainSslConnectionInfo=The service was unable to verify the cipher strengths negotiated as part of the SSL handshake.
;HeaderEncryptionNotSupportedInWsSecurityJan2004=SecurityVersion.WSSecurityJan2004 does not support header encryption. Header with name '{0}' and namespace '{1}' is configured for encryption. Consider using SecurityVersion.WsSecurity11 and above or use transport security to encrypt the full message.
;EncryptedHeaderNotSigned=The Header ('{0}', '{1}') was encrypted but not signed. All encrypted headers outside the security header should be signed.
;EncodingBindingElementDoesNotHandleReaderQuotas=Unable to obtain XmlDictionaryReaderQuotas from the Binding. If you have specified a custom EncodingBindingElement, verify that the EncodingBindingElement can handle XmlDictionaryReaderQuotas in its GetProperty<T>() method.
;HeaderDecryptionNotSupportedInWsSecurityJan2004=SecurityVersion.WSSecurityJan2004 does not support header decryption. Use SecurityVersion.WsSecurity11 and above or use transport security to encrypt the full message.
;DecryptionFailed=Unable to decrypt an encrypted data block. Please verify that the encryption algorithm and keys used by the sender and receiver match.
;SamlUriCannotBeNullOrEmpty=The SAML uri specified as part of the SAML security key identifier clause cannot be null or empty.
;AssertionIdCannotBeNullOrEmpty=The assertion id specified as part of the SAML security key identifier clause cannot be null or empty.
;ErrorSerializingSecurityToken=There was an error serializing the security token. Please see the inner exception for more details.
;ErrorSerializingKeyIdentifier=There was an error serializing the security key identifier. Please see the inner exception for more details.
;ErrorSerializingKeyIdentifierClause=There was an error serializing the security key identifier clause. Please see the inner exception for more details.
;ErrorDeserializingKeyIdentifierClauseFromTokenXml=There was an error creating the security key identifier clause from the security token XML. Please see the inner exception for more details.
;ErrorDeserializingTokenXml=There was an error deserializing the security token XML. Please see the inner exception for more details.
;ErrorDeserializingKeyIdentifier=There was an error deserializing the security key identifier XML. Please see the inner exception for more details.
;ErrorDeserializingKeyIdentifierClause=There was an error deserializing the security key identifier clause XML. Please see the inner exception for more details.
;TokenRequirementDoesNotSpecifyTargetAddress=The token requirement '{0}' does not specify the target address. This is required by the token manager for creating the corresponding security token provider.
;DerivedKeyNotInitialized=The derived key has not been computed for the security token.
;IssuedKeySizeNotCompatibleWithAlgorithmSuite=The binding ('{0}', '{1}') has been configured with a security algorithm suite '{2}' that is incompatible with the issued token key size '{3}' specified on the binding.
;IssuedTokenAuthenticationModeRequiresSymmetricIssuedKey=The IssuedToken security authentication mode requires the issued token to contain a symmetric key.
;InvalidBearerKeyUsage=The binding ('{0}', '{1}') uses an Issued Token with Bearer Key Type in a invalid context. The Issued Token with a Bearer Key Type can only be used as a Signed Supporting token or a Signed Encrypted Supporting token. See the SecurityBindingElement.EndpointSupportingTokenParameters property.
;RsaSHA256NotSupported=The binding ('{0}', '{1}') has been configured with a security algorithm suite '{2}' that is not supported.
;MultipleIssuerEndpointsFound=Policy for multiple issuer endpoints was retrieved from '{0}' but the relying party's policy does not specify which issuer endpoint to use. One of the endpoints was selected as the issuer endpoint to use. If you are using svcutil, the other endpoints will be available in commented form in the configuration as <alternativeIssuedTokenParameters>. Check the configuration to ensure that the right issuer endpoint was selected.
;MultipleSamlAuthorityBindingsInReference=The SecurityTokenReference to the SAML assertion contains multiple AuthorityBinding elements.
;MultipleKeyIdentifiersInReference=The SecurityTokenReference contains multiple KeyIdentifier elements.
;DidNotFindKeyIdentifierInReference=The SecurityTokenReference does not contain a KeyIdentifier.
;MultipleSecurityCredentialsManagersInServiceBindingParameters=The ServiceCredentials cannot be added to the binding parameters because the binding parameters already contains a SecurityCredentialsManager '{0}'. If you are configuring custom credentials for the service, please first remove any existing ServiceCredentials from the behaviors collection before adding the custom credential.
;MultipleSecurityCredentialsManagersInChannelBindingParameters=The ClientCredentials cannot be added to the binding parameters because the binding parameters already contains a SecurityCredentialsManager '{0}'. If you are configuring custom credentials for the channel, please first remove any existing ClientCredentials from the behaviors collection before adding the custom credential.
;NoClientCertificate=The binding ('{0}', '{1}') has been configured with a MutualCertificateDuplexBindingElement that requires a client certificate. The client certificate is currently missing.
;SecurityTokenParametersHasIncompatibleInclusionMode=The binding ('{0}', '{1}') is configured with a security token parameter '{2}' that has an incompatible security token inclusion mode '{3}'. Specify an alternate security token inclusion mode (for example, '{4}').
;CannotCreateTwoWayListenerForNegotiation=Unable to create a bi-directional (request-reply or duplex) channel for security negotiation. Please ensure that the binding is capable of creating a bi-directional channel.
;NegotiationQuotasExceededFaultReason=There are too many active security negotiations or secure conversations at the service. Please retry later.
;PendingSessionsExceededFaultReason=There are too many pending secure conversations on the server. Please retry later.
;RequestSecurityTokenDoesNotMatchEndpointFilters=The RequestSecurityToken message does not match the endpoint filters the service '{0}' is expecting incoming messages to match. This may be because the RequestSecurityToken was intended to be sent to a different service.
;SecuritySessionRequiresIssuanceAuthenticator=The security session requires a security token authenticator that implements '{0}'. '{1}' does not implement '{0}'.
;SecuritySessionRequiresSecurityContextTokenCache=The security session requires a security token resolver that implements '{1}'. The security token resolver '{0}' does not implement '{1}'.
;SessionTokenIsNotSecurityContextToken=The session security token authenticator returned a token of type '{0}'. The token type expected is '{1}'.
;SessionTokenIsNotGenericXmlToken=The session security token provider returned a token of type '{0}'. The token type expected is '{1}'.
;SecurityStandardsManagerNotSet=The security standards manager was not specified on '{0}'.
;SecurityNegotiationMessageTooLarge=The security negotiation message with action '{0}' is larger than the maximum allowed buffer size '{1}'. If you are using a streamed transport consider increasing the maximum buffer size on the transport.
;PreviousChannelDemuxerOpenFailed=The channel demuxer Open failed previously with exception '{0}'.
;SecurityChannelListenerNotSet=The security channel listener was not specified on '{0}'.
;SecuritySettingsLifetimeManagerNotSet=The security settings lifetime manager was not specified on '{0}'.
;SecurityListenerClosing=The listener is not accepting new secure conversations because it is closing.
;SecurityListenerClosingFaultReason=The server is not accepting new secure conversations currently because it is closing. Please retry later.
;SslCipherKeyTooSmall=The cipher key negotiated by SSL is too small ('{0}' bits). Keys of such lengths are not allowed as they may result in information disclosure. Please configure the initiator machine to negotiate SSL cipher keys that are '{1}' bits or longer.
;DerivedKeyTokenNonceTooLong=The length ('{0}' bytes) of the derived key's Nonce exceeds the maximum length ('{1}' bytes) allowed.
;DerivedKeyTokenLabelTooLong=The length ('{0}' bytes) of the derived key's Label exceeds the maximum length ('{1}' bytes) allowed.
;DerivedKeyTokenOffsetTooHigh=The derived key's Offset ('{0}' bytes) exceeds the maximum offset ('{1}' bytes) allowed.
;DerivedKeyTokenGenerationAndLengthTooHigh=The derived key's generation ('{0}') and length ('{1}' bytes) result in a key derivation offset that is greater than the maximum offset ('{2}' bytes) allowed.
;DerivedKeyLimitExceeded=The number of derived keys in the message has exceeded the maximum allowed number '{0}'.
;WrappedKeyLimitExceeded=The number of encrypted keys in the message has exceeded the maximum allowed number '{0}'.
;BufferQuotaExceededReadingBase64=Unable to finish reading Base64 data as the given buffer quota has been exceeded. Buffer quota: {0}. Consider increasing the MaxReceivedMessageSize quota on the TransportBindingElement. Please note that a very high value for MaxReceivedMessageSize will result in buffering a large message and might open the system to DOS attacks.
;MessageSecurityDoesNotWorkWithManualAddressing=Manual addressing is not supported with message level security. Configure the binding ('{0}', '{1}') to use transport security or to not do manual addressing.
;TargetAddressIsNotSet=The target service address was not specified on '{0}'.
;IssuedTokenCacheNotSet=The issued token cache was not specified on '{0}'.
;SecurityAlgorithmSuiteNotSet=The security algorithm suite was not specified on '{0}'.
;SecurityTokenFoundOutsideSecurityHeader=A security token ('{0}', '{1}') was found outside the security header. The message may have been altered in transit.
;SecureConversationCancelNotAllowedFaultReason=A secure conversation cancellation is not allowed by the binding.
;BootstrapSecurityBindingElementNotSet=The security binding element for bootstrap security was not specified on '{0}'.
;IssuerBuildContextNotSet=The context for building the issuer channel was not specified on '{0}'.
;StsBindingNotSet=The binding to use to communicate to the federation service at '{0}' is not specified.
;SslServerCertMustDoKeyExchange=The certificate '{0}' must have a private key that is capable of key exchange. The process must have access rights for the private key.
;SslClientCertMustHavePrivateKey=The certificate '{0}' must have a private key. The process must have access rights for the private key.
;NoOutgoingEndpointAddressAvailableForDoingIdentityCheck=No outgoing EndpointAddress is available to check the identity on a message to be sent.
;NoOutgoingEndpointAddressAvailableForDoingIdentityCheckOnReply=No outgoing EndpointAddress is available to check the identity on a received reply.
;NoSigningTokenAvailableToDoIncomingIdentityCheck=No signing token is available to do an incoming identity check.
;Psha1KeyLengthInvalid=The PSHA1 key length '{0}' is invalid.
CloneNotImplementedCorrectly=Clone() was not implemented properly by '{0}'. The cloned object was '{1}'.
;BadIssuedTokenType=The issued token is of unexpected type '{0}'. Expected token type '{1}'.
;OperationDoesNotAllowImpersonation=The service operation '{0}' that belongs to the contract with the '{1}' name and the '{2}' namespace does not allow impersonation.
;RstrHasMultipleIssuedTokens=The RequestSecurityTokenResponse has multiple RequestedSecurityToken elements.
;RstrHasMultipleProofTokens=The RequestSecurityTokenResponse has multiple RequestedProofToken elements.
;ProofTokenXmlUnexpectedInRstr=The proof token XML element is not expected in the response.
;InvalidKeyLengthRequested=The key length '{0}' requested is invalid.
;IssuedSecurityTokenParametersNotSet=The security token parameters to use for the issued token are not set on '{0}'.
;InvalidOrUnrecognizedAction=The message could not be processed because the action '{0}' is invalid or unrecognized.
;UnsupportedTokenInclusionMode=Token inclusion mode '{0}' is not supported.
;CannotImportProtectionLevelForContract=The policy to import a process cannot import a binding for contract ({0},{1}). The protection requirements for the binding are not compatible with a binding already imported for the contract. You must reconfigure the binding.
;OnlyOneOfEncryptedKeyOrSymmetricBindingCanBeSelected=The symmetric security protocol can either be configured with a symmetric token provider and a symmetric token authenticator or an asymmetric token provider. It cannot be configured with both.
;ClientCredentialTypeMustBeSpecifiedForMixedMode=ClientCredentialType.None is not valid for the TransportWithMessageCredential security mode. Specify a message credential type or use a different security mode.
;SecuritySessionIdAlreadyPresentInFilterTable=The security session id '{0}' is already present in the filter table.
;SupportingTokenNotProvided=A supporting token that satisfies parameters '{0}' and attachment mode '{1}' was not provided.
;SupportingTokenIsNotEndorsing=The supporting token provided for parameters '{0}' did not endorse the primary signature.
;SupportingTokenIsNotSigned=The supporting token provided for parameters '{0}' was not signed as part of the primary signature.
;SupportingTokenIsNotEncrypted=The supporting token provided for parameters '{0}' was not encrypted.
;BasicTokenNotExpected=A basic token is not expected in the security header in this context.
;FailedAuthenticationTrustFaultCode=The request for security token could not be satisfied because authentication failed.
;AuthenticationOfClientFailed=The caller was not authenticated by the service.
;InvalidRequestTrustFaultCode=The request for security token has invalid or malformed elements.
;SignedSupportingTokenNotExpected=A signed supporting token is not expected in the security header in this context.
;SenderSideSupportingTokensMustSpecifySecurityTokenParameters=Security token parameters must be specified with supporting tokens for each message.
;SignatureAndEncryptionTokenMismatch=The signature token '{0}' is not the same token as the encryption token '{1}'.
;RevertingPrivilegeFailed=The reverting operation failed with the exception '{0}'.
;UnknownSupportingToken=Unrecognized supporting token '{0}' was encountered.
;MoreThanOneSupportingSignature=More than one supporting signature was encountered using the same supporting token '{0}'.
UnsecuredMessageFaultReceived=An unsecured or incorrectly secured fault was received from the other party. See the inner FaultException for the fault code and detail.
;FailedAuthenticationFaultReason=At least one security token in the message could not be validated.
;BadContextTokenOrActionFaultReason=The message could not be processed. This is most likely because the action '{0}' is incorrect or because the message contains an invalid or expired security context token or because there is a mismatch between bindings. The security context token would be invalid if the service aborted the channel due to inactivity. To prevent the service from aborting idle sessions prematurely increase the Receive timeout on the service endpoint's binding.
;BadContextTokenFaultReason=The security context token is expired or is not valid. The message was not processed.
;NegotiationFailedIO=Transport security negotiation failed due to an underlying IO error: {0}.
;SecurityNegotiationCannotProtectConfidentialEndpointHeader=The security negotiation with '{0}' cannot be initiated because the confidential endpoint address header ('{1}', '{2}') cannot be encrypted during the course of the negotiation.
;InvalidSecurityTokenFaultReason=An error occurred when processing the security tokens in the message.
;InvalidSecurityFaultReason=An error occurred when verifying security for the message.
;AnonymousLogonsAreNotAllowed=The service does not allow you to log on anonymously.
;UnableToObtainIssuerMetadata=Obtaining metadata from issuer '{0}' failed with error '{1}'.
;ErrorImportingIssuerMetadata=Importing metadata from issuer '{0}' failed with error '{1}'.
;MultipleCorrelationTokensFound=Multiple correlation tokens were found in the security correlation state.
;NoCorrelationTokenFound=No correlation token was found in the security correlation state.
;MultipleSupportingAuthenticatorsOfSameType=Multiple supporting token authenticators of the same type '{0}' cannot be specified. If more than one Supporting Token of the same type is expected in the response, then configure the supporting token collection with just one entry for that SecurityTokenParameters. The SecurityTokenAuthenticator that gets created from the SecurityTokenParameters will be used to authenticate multiple tokens. It is not possible to add SecurityTokenParameters of the same type in the SupportingTokenParameters collection or repeat it across EndpointSupportingTokenParameters and OperationSupportingTokenParameters.
;TooManyIssuedSecurityTokenParameters=A leg of the federated security chain contains multiple IssuedSecurityTokenParameters. The InfoCard system only supports one IssuedSecurityTokenParameters for each leg.
;UnknownTokenAuthenticatorUsedInTokenProcessing=An unrecognized token authenticator '{0}' was used for token processing.
;TokenMustBeNullWhenTokenParametersAre=The SecurityTokenParameters and SecurityToken tuple specified for use in the security header must both be null or must both be non-null.
;SecurityTokenParametersCloneInvalidResult=The CloneCore method of {0} type returned an invalid result.
;CertificateUnsupportedForHttpTransportCredentialOnly=Certificate-based client authentication is not supported in TransportCredentialOnly security mode. Select the Transport security mode.
;BasicHttpMessageSecurityRequiresCertificate=BasicHttp binding requires that BasicHttpBinding.Security.Message.ClientCredentialType be equivalent to the BasicHttpMessageCredentialType.Certificate credential type for secure messages. Select Transport or TransportWithMessageCredential security for UserName credentials.
;EntropyModeRequiresRequestorEntropy=The client must provide key entropy in key entropy mode '{0}'.
;BearerKeyTypeCannotHaveProofKey=A Proof Token was found in the response that was returned by the Security Token Service for a Bearer Key Type token request. Note that Proof Tokens should not be generated when a Bearer Key Type request is made.
;BearerKeyIncompatibleWithWSFederationHttpBinding=Bearer Key Type is not supported with WSFederationHttpBinding. Please use WS2007FederationHttpBinding.
;UnableToCreateKeyTypeElementForUnknownKeyType=Unable to create Key Type element for the Key Type '{0}'. This might be due to a wrong version of MessageSecurityVersion set on the SecurityBindingElement.
;EntropyModeCannotHaveProofTokenOrIssuerEntropy=The issuer cannot provide key entropy or a proof token in key entropy mode '{0}'.
;EntropyModeCannotHaveRequestorEntropy=The client cannot provide key entropy in key entropy mode '{0}'.
;EntropyModeRequiresProofToken=The issuer must provide a proof token in key entropy mode '{0}'.
;EntropyModeRequiresComputedKey=The issuer must provide a computed key in key entropy mode '{0}'.
;EntropyModeRequiresIssuerEntropy=The issuer must provide key entropy in key entropy mode '{0}'.
;EntropyModeCannotHaveComputedKey=The issuer cannot provide a computed key in key entropy mode '{0}'.
;UnknownComputedKeyAlgorithm=The computed key algorithm '{0}' is not supported.
;NoncesCachedInfinitely=The ReplayWindow and ClockSkew cannot be the maximum possible value when replay detection is enabled.
;ChannelMustBeOpenedToGetSessionId=The session channel must be opened before the session ID can be accessed.
;SecurityVersionDoesNotSupportEncryptedKeyBinding=The binding ('{0}','{1}') for contract ('{2}','{3}') has been configured with an incompatible security version that does not support unattached references to EncryptedKeys. Use '{4}' or higher as the security version for the binding.
;SecurityVersionDoesNotSupportThumbprintX509KeyIdentifierClause=The '{0}','{1}' binding for the '{2}','{3}' contract is configured with a security version that does not support external references to X.509 tokens using the certificate's thumbprint value. Use '{4}' or higher as the security version for the binding.
;SecurityBindingSupportsOneWayOnly=The SecurityBinding for the ('{0}','{1}') binding for the ('{2}','{3}') contract only supports the OneWay operation.
;DownlevelNameCannotMapToUpn=Cannot map Windows user '{0}' to a UserPrincipalName that can be used for S4U impersonation.
;ResolvingExternalTokensRequireSecurityTokenParameters=Resolving an External reference token requires appropriate SecurityTokenParameters to be specified.
;SecurityRenewFaultReason=The SecurityContextSecurityToken's key needs to be renewed.
;ClientSecurityOutputSessionCloseTimeout=The client's security session was not able to close its output session within the configured timeout ({0}).
;ClientSecurityNegotiationTimeout=Client is unable to finish the security negotiation within the configured timeout ({0}). The current negotiation leg is {1} ({2}).
;ClientSecuritySessionRequestTimeout=Client is unable to request the security session within the configured timeout ({0}).
;ServiceSecurityCloseOutputSessionTimeout=The service's security session was not able to close its output session within the configured timeout ({0}).
;ServiceSecurityCloseTimeout=The service's security session did not receive a 'close' message from the client within the configured timeout ({0}).
;ClientSecurityCloseTimeout=The client's security session did not receive a 'close response' message from the service within the configured timeout ({0}).
;UnableToRenewSessionKey=Cannot renew the security session key.
;SctCookieXmlParseError=Error parsing SecurityContextSecurityToken Cookie XML.
;SctCookieValueMissingOrIncorrect=The SecurityContextSecurityToken's Cookie element either does not contain '{0}' or has a wrong value for it.
;SctCookieBlobDecodeFailure=Error decoding the Cookie element of SecurityContextSecurityToken.
;SctCookieNotSupported=Issuing cookie SecurityContextSecurityToken is not supported.
;CannotImportSupportingTokensForOperationWithoutRequestAction=Security policy import failed. The security policy contains supporting token requirements at the operation scope. The contract description does not specify the action for the request message associated with this operation.
;SignatureConfirmationsNotExpected=Signature confirmation is not expected in the security header.
;SignatureConfirmationsOccursAfterPrimarySignature=The signature confirmation elements cannot occur after the primary signature.
;SecurityVersionDoesNotSupportSignatureConfirmation=The SecurityVersion '{0}' does not support signature confirmation. Use a later SecurityVersion.
;SignatureConfirmationRequiresRequestReply=The protocol factory must support Request/Reply security in order to offer signature confirmation.
;NotAllSignaturesConfirmed=Not all the signatures in the request message were confirmed in the reply message.
;FoundUnexpectedSignatureConfirmations=The request did not have any signatures but the reply has signature confirmations.
;TooManyPendingSessionKeys=There are too many renewed session keys that have not been used.
;SecuritySessionKeyIsStale=The session key must be renewed before it can secure application messages.
;MultipleMatchingCryptosFound=The token's crypto collection has multiple objects of type '{0}'.
;CannotFindMatchingCrypto=The token's crypto collection does not support algorithm '{0}'.
;SymmetricSecurityBindingElementNeedsProtectionTokenParameters=SymmetricSecurityBindingElement cannot build a channel or listener factory. The ProtectionTokenParameters property is required but not set. Binding element configuration: {0}
;AsymmetricSecurityBindingElementNeedsInitiatorTokenParameters=AsymmetricSecurityBindingElement cannot build a channel or listener factory. The InitiatorTokenParameters property is required but not set. Binding element configuration: {0}
;AsymmetricSecurityBindingElementNeedsRecipientTokenParameters=AsymmetricSecurityBindingElement cannot build a channel or listener factory. The RecipientTokenParameters property is required but not set. Binding element configuration: {0}
;CachedNegotiationStateQuotaReached=The service cannot cache the negotiation state as the capacity '{0}' has been reached. Retry the request.
;LsaAuthorityNotContacted=Internal SSL error (refer to Win32 status code for details). Check the server certificate to determine if it is capable of key exchange.
;KeyRolloverGreaterThanKeyRenewal=The key rollover interval cannot be greater than the key renewal interval.
;AtLeastOneContractOperationRequestRequiresProtectionLevelNotSupportedByBinding=The request message must be protected. This is required by an operation of the contract ('{0}','{1}'). The protection must be provided by the binding ('{2}','{3}').
;AtLeastOneContractOperationResponseRequiresProtectionLevelNotSupportedByBinding=The response message must be protected. This is required by an operation of the contract ('{0}', '{1}'). The protection must be provided by the binding ('{2}', '{3}').
;UnknownHeaderCannotProtected=The contract ('{0}','{1}') contains some unknown header ('{2}','{3}') which cannot be secured. Please choose ProtectionLevel.None for this header.
;NoStreamingWithSecurity=The binding ('{0}','{1}') supports streaming which cannot be configured together with message level security. Consider choosing a different transfer mode or choosing the transport level security.
;CurrentSessionTokenNotRenewed=The supporting token in the renew message has a different generation '{0}' than the current session token's generation '{1}'.
;IncorrectSpnOrUpnSpecified=Security Support Provider Interface (SSPI) authentication failed. The server may not be running in an account with identity '{0}'. If the server is running in a service account (Network Service for example), specify the account's ServicePrincipalName as the identity in the EndpointAddress for the server. If the server is running in a user account, specify the account's UserPrincipalName as the identity in the EndpointAddress for the server.
;IncomingSigningTokenMustBeAnEncryptedKey=For this security protocol, the incoming signing token must be an EncryptedKey.
;SecuritySessionAbortedFaultReason=The security session was terminated This may be because no messages were received on the session for too long.
;NoAppliesToPresent=No AppliesTo element is present in the deserialized RequestSecurityToken/RequestSecurityTokenResponse.
;UnsupportedKeyLength=Symmetric Key length {0} is not supported by the algorithm suite '{1}'.
;ForReplayDetectionToBeDoneRequireIntegrityMustBeSet=For replay detection to be done ProtectionLevel must be Sign or EncryptAndSign.
;CantInferReferenceForToken=Can't infer an external reference for '{0}' token type.
;TrustApr2004DoesNotSupportCertainIssuedTokens=WSTrustApr2004 does not support issuing X.509 certificates or EncryptedKeys. Use WsTrustFeb2005 or above.
;TrustDriverVersionDoesNotSupportSession=The configured Trust version does not support sessions. Use WSTrustFeb2005 or above.
;TrustDriverVersionDoesNotSupportIssuedTokens=The configured WS-Trust version does not support issued tokens. WS-Trust February 2005 or later is required.
;CannotPerformS4UImpersonationOnPlatform=The binding ('{0}','{1}') for contract ('{2}','{3}') supports impersonation only on Windows 2003 Server and newer version of Windows. Use SspiNegotiated authentication and a binding with Secure Conversation with cancellation enabled.
;CannotPerformImpersonationOnUsernameToken=Impersonation using the client token is not possible. The binding ('{0}', '{1}') for contract ('{2}', '{3}') uses the Username Security Token for client authentication with a Membership Provider registered. Use a different type of security token for the client.
;SecureConversationRequiredByReliableSession=Cannot establish a reliable session without secure conversation. Enable secure conversation.
;RevertImpersonationFailure=Failed to revert impersonation. {0}
;TransactionFlowRequiredIssuedTokens=In order to flow a transaction, flowing issued tokens must also be supported.
;SignatureConfirmationNotSupported=The configured SecurityVersion does not support signature confirmation. Use WsSecurity11 or above.
;SecureConversationDriverVersionDoesNotSupportSession=The configured SecureConversation version does not support sessions. Use WSSecureConversationFeb2005 or above.
;SoapSecurityNegotiationFailed=SOAP security negotiation failed. See inner exception for more details.
;SoapSecurityNegotiationFailedForIssuerAndTarget=SOAP security negotiation with '{0}' for target '{1}' failed. See inner exception for more details.
;OneWayOperationReturnedFault=The one-way operation returned a fault message. The reason for the fault was '{0}'.
;OneWayOperationReturnedLargeFault=The one-way operation returned a fault message with Action='{0}'.
OneWayOperationReturnedMessage=The one-way operation returned a non-null message with Action='{0}'.
;CannotFindSecuritySession=Cannot find the security session with the ID '{0}'.
;SecurityContextKeyExpired=The SecurityContextSecurityToken with Context-id={0} (generation-id={1}) has expired.
;SecurityContextKeyExpiredNoKeyGeneration=The SecurityContextSecurityToken with Context-id={0} (no key generation-id) has expired.
;SecuritySessionRequiresMessageIntegrity=Security sessions require all messages to be signed.
;RequiredTimestampMissingInSecurityHeader=Required timestamp missing in security header.
;ReceivedMessageInRequestContextNull=The request message in the request context received from channel '{0}' is null.
;KeyLifetimeNotWithinTokenLifetime=The key effective and expiration times must be bounded by the token effective and expiration times.
;EffectiveGreaterThanExpiration=The valid from time is greater than the valid to time.
;NoSessionTokenPresentInMessage=No session token was present in the message.
;KeyLengthMustBeMultipleOfEight=Key length '{0}' is not a multiple of 8 for symmetric keys.
;ExportOfBindingWithSymmetricAndTransportSecurityNotSupported=Security policy export failed. The binding contains both a SymmetricSecurityBindingElement and a secure transport binding element. Policy export for such a binding is not supported.
;InvalidX509RawData=Invalid binary representation of an X.509 certificate.
;ExportOfBindingWithAsymmetricAndTransportSecurityNotSupported=Security policy export failed. The binding contains both an AsymmetricSecurityBindingElement and a secure transport binding element. Policy export for such a binding is not supported.
;ExportOfBindingWithTransportSecurityBindingElementAndNoTransportSecurityNotSupported=Security policy export failed. The binding contains a TransportSecurityBindingElement but no transport binding element that implements ITransportTokenAssertionProvider. Policy export for such a binding is not supported. Make sure the transport binding element in the binding implements the ITransportTokenAssertionProvider interface.
;UnsupportedSecureConversationBootstrapProtectionRequirements=Cannot import the security policy. The protection requirements for the secure conversation bootstrap binding are not supported. Protection requirements for the secure conversation bootstrap must require both the request and the response to be signed and encrypted.
;UnsupportedBooleanAttribute=Cannot import the policy. The value of the attribute '{0}' must be either 'true', 'false', '1' or '0'. The following error occurred: '{1}'.
;NoTransportTokenAssertionProvided=The security policy expert failed. The provided transport token assertion of type '{0}' did not create a transport token assertion to include the sp:TransportBinding security policy assertion.
;PolicyRequiresConfidentialityWithoutIntegrity=Message security policy for the '{0}' action requires confidentiality without integrity. Confidentiality without integrity is not supported.
;PrimarySignatureIsRequiredToBeEncrypted=The primary signature must be encrypted.
;TokenCannotCreateSymmetricCrypto=A symmetric crypto could not be created from token '{0}'.
;TokenDoesNotMeetKeySizeRequirements=The key size requirements for the '{0}' algorithm suite are not met by the '{1}' token which has key size of '{2}'.
;MessageProtectionOrderMismatch=The received message does not meet the required message protection order '{0}'.
;PrimarySignatureMustBeComputedBeforeSupportingTokenSignatures=Primary signature must be computed before supporting token signatures.
;ElementToSignMustHaveId=Element to sign must have id.
;StandardsManagerCannotWriteObject=The token Serializer cannot serialize '{0}'. If this is a custom type you must supply a custom serializer.
;SigningWithoutPrimarySignatureRequiresTimestamp=Signing without primary signature requires timestamp.
;OperationCannotBeDoneAfterProcessingIsStarted=This operation cannot be done after processing is started.
;MaximumPolicyRedirectionsExceeded=The recursive policy fetching limit has been reached. Check to determine if there is a loop in the federation service chain.
;InvalidAttributeInSignedHeader=The ('{0}', '{1}') signed header contains the ('{2}', '{3}') attribute. The expected attribute is ('{4}', '{5}').
;StsAddressNotSet=The address of the security token issuer is not specified. An explicit issuer address must be specified in the binding for target '{0}' or the local issuer address must be configured in the credentials.
;MoreThanOneSecurityBindingElementInTheBinding=More than one SecurityBindingElement found in the binding ('{0}', '{1}) for contract ('{2}', '{3}'). Only one SecurityBindingElement is allowed.
;ClientCredentialsUnableToCreateLocalTokenProvider=ClientCredentials cannot create a local token provider for token requirement {0}.
;SecurityBindingElementCannotBeExpressedInConfig=A security policy was imported for the endpoint. The security policy contains requirements that cannot be represented in a Windows Communication Foundation configuration. Look for a comment about the SecurityBindingElement parameters that are required in the configuration file that was generated. Create the correct binding element with code. The binding configuration that is in the configuration file is not secure.
;ConfigurationSchemaInsuffientForSecurityBindingElementInstance=The configuration schema is insufficient to describe the non-standard configuration of the following security binding element:
;OperationCannotBeDoneOnReceiverSideSecurityHeaders=This operation cannot be done on the receiver security headers.
;SecurityProtocolCannotDoReplayDetection=The security protocol '{0}' cannot do replay detection.
;UnableToFindSecurityHeaderInMessage=Security processor was unable to find a security header with actor '{0}' in the message. This might be because the message is an unsecured fault or because there is a binding mismatch between the communicating parties. This can occur if the service is configured for security and the client is not using security.
UnableToFindSecurityHeaderInMessageNoActor=Security processor was unable to find a security header in the message. This might be because the message is an unsecured fault or because there is a binding mismatch between the communicating parties. This can occur if the service is configured for security and the client is not using security.
;NoPrimarySignatureAvailableForSupportingTokenSignatureVerification=No primary signature available for supporting token signature verification.
;SupportingTokenSignaturesNotExpected=Supporting token signatures not expected.
;CannotReadToken=Cannot read the token from the '{0}' element with the '{1}' namespace for BinarySecretSecurityToken, with a '{2}' ValueType. If this element is expected to be valid, ensure that security is configured to consume tokens with the name, namespace and value type specified.
ExpectedElementMissing=Element '{0}' with namespace '{1}' not found.
;ExpectedOneOfTwoElementsFromNamespace=Expected element '{0}' or element '{1}' (from namespace '{2}').
;RstDirectDoesNotExpectRstr=AcceleratedTokenAuthenticator does not expect RequestSecurityTokenResponse from the client.
;RequireNonCookieMode=The '{0}' binding with the '{1}' namespace is configured to issue cookie security context tokens. COM+ Integration services does not support cookie security context tokens.
;RequiredSignatureMissing=The signature must be in the security header.
;RequiredMessagePartNotSigned=The '{0}' required message part was not signed.
;RequiredMessagePartNotSignedNs=The '{0}', '{1}' required message part was not signed.
;RequiredMessagePartNotEncrypted=The '{0}' required message part was not encrypted.
;RequiredMessagePartNotEncryptedNs=The '{0}', '{1}' required message part was not encrypted.
;SignatureVerificationFailed=Signature verification failed.
;CannotIssueRstTokenType=Cannot issue the token type '{0}'.
;NoNegotiationMessageToSend=There is no negotiation message to send.
;InvalidIssuedTokenKeySize=The issued token has an invalid key size '{0}'.
;CannotObtainIssuedTokenKeySize=Cannot determine the key size of the issued token.
;NegotiationIsNotCompleted=The negotiation has not yet completed.
;NegotiationIsCompleted=The negotiation has already completed.
MissingMessageID=Request Message is missing a MessageID header. One is required to correlate a reply.
;SecuritySessionLimitReached=Cannot create a security session. Retry later.
;SecuritySessionAlreadyPending=The security session with id '{0}' is already pending.
;SecuritySessionNotPending=No security session with id '{0}' is pending.
;SecuritySessionListenerNotFound=No security session listener was found for message with action '{0}'.
;SessionTokenWasNotClosed=The session token was not closed by the server.
;ProtocolMustBeInitiator='{0}' protocol can only be used by the Initiator.
;ProtocolMustBeRecipient='{0}' protocol can only be used at the Recipient.
;SendingOutgoingmessageOnRecipient=Unexpected code path for server security application, sending outgoing message on Recipient.
;OnlyBodyReturnValuesSupported=Only body return values are supported currently for protection, MessagePartDescription was specified.
;UnknownTokenAttachmentMode=Unknown token attachment mode: {0}.
;ProtocolMisMatch=Security protocol must be '{0}', type is: '{1}'.;
;AttemptToCreateMultipleRequestContext=The initial request context was already specified. Can not create two for same message.
;ServerReceivedCloseMessageStateIsCreated={0}.OnCloseMessageReceived when state == Created.
;ShutdownRequestWasNotReceived=Shutdown request was not received.
;UnknownFilterType=Unknown filter type: '{0}'.
;StandardsManagerDoesNotMatch=Standards manager of filter does not match that of filter table. Can not have two different filters.
;FilterStrictModeDifferent=Session filter's isStrictMode differs from filter table's isStrictMode.
;SSSSCreateAcceptor=SecuritySessionServerSettings.CreateAcceptor, channelAcceptor must be null, can not create twice.
;TransactionFlowBadOption=Invalid TransactionFlowOption value.
;TokenManagerCouldNotReadToken=Security token manager could not parse token with name '{0}', namespace '{1}', valueType '{2}'.
;InvalidActionForNegotiationMessage=Security negotiation message has incorrect action '{0}'.
;InvalidKeySizeSpecifiedInNegotiation=The specified key size {0} is invalid. The key size must be between {1} and {2}.
;GetTokenInfoFailed=Could not get token information (error=0x{0:X}).
;UnexpectedEndOfFile=Unexpected end of file.
TimeStampHasCreationAheadOfExpiry=The security timestamp is invalid because its creation time ('{0}') is greater than or equal to its expiration time ('{1}').
TimeStampHasExpiryTimeInPast=The security timestamp is stale because its expiration time ('{0}') is in the past. Current time is '{1}' and allowed clock skew is '{2}'.
TimeStampHasCreationTimeInFuture=The security timestamp is invalid because its creation time ('{0}') is in the future. Current time is '{1}' and allowed clock skew is '{2}'.
TimeStampWasCreatedTooLongAgo=The security timestamp is stale because its creation time ('{0}') is too far back in the past. Current time is '{1}', maximum timestamp lifetime is '{2}' and allowed clock skew is '{3}'.
;InvalidOrReplayedNonce=The nonce is invalid or replayed.
;MessagePartSpecificationMustBeImmutable=Message part specification must be made constant before being set.
;UnsupportedIssuerEntropyType=Issuer entropy is not BinarySecretSecurityToken or WrappedKeySecurityToken.
;NoRequestSecurityTokenResponseElements=No RequestSecurityTokenResponse elements were found.
;NoCookieInSct=The SecurityContextSecurityToken does not have a cookie.
;TokenProviderReturnedBadToken=TokenProvider returned token of incorrect type '{0}'.
;ItemNotAvailableInDeserializedRST={0} is not available in deserialized RequestSecurityToken.
;ItemAvailableInDeserializedRSTOnly={0} is only available in a deserialized RequestSecurityToken.
;ItemNotAvailableInDeserializedRSTR={0} is not available in deserialized RequestSecurityTokenResponse.
;ItemAvailableInDeserializedRSTROnly={0} is only available in a deserialized RequestSecurityTokenResponse.
;MoreThanOneRSTRInRSTRC=The RequestSecurityTokenResponseCollection received has more than one RequestSecurityTokenResponse element. Only one RequestSecurityTokenResponse element was expected.
;Hosting_AddressIsAbsoluteUri=The full URI '{0}' is not allowed. Full URIs are not allowed for the ServiceHostingEnvironment.EnsureServiceAvailable API. Use virtual path for the corresponding service instead.
;Hosting_AddressPointsOutsideTheVirtualDirectory=The virtual path '{0}' points outside of the virtual application '{1}'.
;Hosting_AuthSchemesRequireWindowsAuth=Security settings for this service require Windows Authentication but it is not enabled for the IIS application that hosts this service.
;Hosting_AuthSchemesRequireOtherAuth=Security settings for this service require '{0}' Authentication but it is not enabled for the IIS application that hosts this service.
;Hosting_BadMetabaseSettingsIis7Type=Type '{0}' does not derive from the base type 'MetabaseSettings'.
;Hosting_BaseUriDeserializedNotValid=The BaseUriWithWildcard object has invalid fields after deserialization.
;Hosting_BuildProviderDirectiveMissing=The required directive '{0}' is missing.
;Hosting_BuildProviderMainAttributeMissing=The ServiceHost directive must specify either the 'Factory' or the 'Service' attribute.
;Hosting_BuildProviderDuplicateAttribute=The attribute '{0}' can be only specified once.
;Hosting_BuildProviderDirectiveNameMissing=The name of the directive is missing.
;Hosting_BuildProviderDirectiveEndBracketMissing=The ending bracket '>' for the '{0}' directive is missing in the '.svc' file.
;Hosting_BuildProviderDuplicateDirective=The directive '{0}' can be only specified once.
;Hosting_BuildProviderMutualExclusiveAttributes=Attributes '{0}' and '{1}' are mutually exclusive.
;Hosting_BuildProviderUnknownDirective=The unrecognized directive '{0}' is specified.
;SecureConversationNeedsBootstrapSecurity=Cannot create security binding element based on the configuration data. When secure conversation authentication mode is selected, the secure conversation bootstrap binding element must also be specified.
;Hosting_BuildProviderRequiredAttributesMissing=Required attributes '{0}' and '{1}' are missing.
;Hosting_BuildProviderCouldNotCreateType=The CLR Type '{0}' could not be loaded during service compilation. Verify that this type is either defined in a source file located in the application's \\App_Code directory, contained in a compiled assembly located in the application's \\bin directory, or present in an assembly installed in the Global Assembly Cache. Note that the type name is case-sensitive and that the directories such as \\App_Code and \\bin must be located in the application's root directory and cannot be nested in subdirectories.
;Hosting_BuildProviderAttributeMissing=The attribute '{0}' is missing.
;Hosting_BuildProviderUnknownAttribute=The unrecognized attribute '{0}' is specified.
;Hosting_BuildProviderInvalidValueForBooleanAttribute=The value '{0}' of attribute '{1}' is not a valid Boolean value.
;Hosting_BuildProviderInvalidValueForNonNegativeIntegerAttribute=The value '{0}' of attribute '{1}' is not a valid non-negative integer.
;Hosting_BuildProviderAmbiguousType=The referenced CLR type '{0}' is ambiguous. It is found both in assembly '{1}' and in assembly '{2}'.
;Hosting_BuildProviderAttributeEmpty=No file is specified in the '{0}' attribute.
;Hosting_ImpersonationFailed=An error occurred while attempting to impersonate. Execution of this request cannot continue.
;Hosting_MemoryGatesCheckFailed=Memory gates checking failed because the free memory ({0} bytes) is less than {1}% of total memory. As a result, the service will not be available for incoming requests. To resolve this, either reduce the load on the machine or adjust the value of minFreeMemoryPercentageToActivateService on the serviceHostingEnvironment config element.
;Hosting_GetGlobalMemoryFailed=Calling the API GlobalMemoryStatusEx failed. See inner exception for more details.
;Hosting_CompatibilityServiceNotHosted=This service requires ASP.NET compatibility and must be hosted in IIS. Either host the service in IIS with ASP.NET compatibility turned on in web.config or set the AspNetCompatibilityRequirementsAttribute.AspNetCompatibilityRequirementsMode property to a value other than Required.
;Hosting_CompilationResultEmpty=Compilation result for the service '{0}' is empty.
;Hosting_CompilationResultInvalid=Compilation result for the service '{0}' is of invalid format.
;Hosting_EnvironmentShuttingDown=Request to the service at '{0}' cannot be dispatched because the virtual application at '{1}' is shutting down.
;Hosting_ListenerNotFoundForActivation=There was no channel actively listening at '{0}'. This is often caused by an incorrect address URI. Ensure that the address to which the message is sent matches an address on which a service is listening.
;Hosting_ListenerNotFoundForActivationInRecycling=There was no channel actively listening at '{0}'. This might be because the service is closed due to application recycling.
;Hosting_MetabaseAccessError=An error occurred while accessing the IIS Metabase.
;Hosting_MetabaseDataStringsTerminate=The string array data for the property '{0}' retrieved from IIS Metabase has invalid length or is not null terminated.
;Hosting_MetabaseDataTypeUnsupported=The data type '{0}' is not supported for the property '{1}' in IIS Metabase.
;Hosting_MetabaseSettingsIis7TypeNotFound=Type '{0}' cannot be found in the assembly '{1}'.
;Hosting_MisformattedPort=The '{0}' protocol binding '{1}' specifies an invalid port number '{2}'.
;Hosting_MisformattedBinding=The protocol binding '{0}' does not conform to the syntax for '{1}'. The following is an example of valid '{1}' protocol bindings: '{2}'.
;Hosting_MisformattedBindingData=The protocol binding '{0}' is not valid for '{1}'. This might be because the port number is out of range.
;Hosting_NonHTTPInCompatibilityMode=Protocols other than HTTP/HTTPS are not supported under ASP.NET compatibility. Remove the endpoint '{0}' or disable ASP.NET compatibility for the application.
;Hosting_NoHttpTransportManagerForUri=There is no compatible TransportManager found for URI '{0}'. This may be because that you have used an absolute address which points outside of the virtual application. Please use a relative address instead.
;Hosting_NoTcpPipeTransportManagerForUri=There is no compatible TransportManager found for URI '{0}'. This may be because that you have used an absolute address which points outside of the virtual application, or the binding settings of the endpoint do not match those that have been set by other services or endpoints. Note that all bindings for the same protocol should have same settings in the same application.
;Hosting_NotSupportedAuthScheme=The authentication scheme '{0}' is not supported.
;Hosting_NotSupportedProtocol=The protocol '{0}' is not supported.
;Hosting_ProcessNotExecutingUnderHostedContext='{0}' cannot be invoked within the current hosting environment. This API requires that the calling application be hosted in IIS or WAS.
;Hosting_ProtocolNoConfiguration=The protocol '{0}' does not have an implementation of HostedTransportConfiguration type registered.
Hosting_ServiceActivationFailed=The requested service, '{0}' could not be activated. See the server's diagnostic trace logs for more information.
;Hosting_ServiceCompatibilityNotAllowed=The service cannot be activated because it does not support ASP.NET compatibility. ASP.NET compatibility is enabled for this application. Turn off ASP.NET compatibility mode in the web.config or add the AspNetCompatibilityRequirements attribute to the service type with RequirementsMode setting as 'Allowed' or 'Required'.
;Hosting_ServiceCompatibilityRequire=The service cannot be activated because it requires ASP.NET compatibility. ASP.NET compatibility is not enabled for this application. Either enable ASP.NET compatibility in web.config or set the AspNetCompatibilityRequirementsAttribute.AspNetCompatibilityRequirementsMode property to a value other than Required.
;Hosting_ServiceNotExist=The service '{0}' does not exist.
;Hosting_SslSettingsMisconfigured=The SSL settings for the service '{0}' does not match those of the IIS '{1}'.
;Hosting_TransportBindingNotFound=No protocol binding matches the given address '{0}'. Protocol bindings are configured at the Site level in IIS or WAS configuration.
;Hosting_IServiceHostNotImplemented=The CLR type '{0}', provided as the Factory attribute of the ServiceHost directive in the '.svc' file, does not derive from ServiceHostFactoryBase.
;Hosting_NoDefaultCtor=The type {0} provided as the Factory attribute value in the ServiceHost directive does not implement a default constructor.
;Hosting_ServiceTypeNotProvided=The value for the Service attribute was not provided in the ServiceHost directive.
;Hosting_ServiceTypeNotResolved=The type '{0}', provided as the Service attribute value in the ServiceHost directive could not be found.
;Hosting_ServiceHostBaseIsNull=The ServiceHostBase object returned from the CreateServiceHost method of type '{0}' is null.
;Hosting_ServiceCannotBeActivated=The service '{0}' cannot be activated due to an exception during compilation. The exception message is: {1}.
;Hosting_VirtualPathExtenstionCanNotBeDetached=VirtualPathExtension is not allowed to be removed.
;SharedEndpointReadDenied=The service endpoint failed to listen on the URI '{0}' because access was denied. Verify that the current user is granted access in the appropriate allowedAccounts section of SMSvcHost.exe.config.
;SharedEndpointReadNotFound=The service endpoint failed to listen on the URI '{0}' because the shared memory section was not found. Verify that the '{1}' service is running.
;SharedManagerBase=The TransportManager failed to listen on the supplied URI using the {0} service: {1}.
;SharedManagerServiceStartFailure=failed to start the service ({0}). Refer to the Event Log for more details
;SharedManagerServiceStartFailureDisabled=failed to start the service because it is disabled. An administrator can enable it by running 'sc.exe config {0} start= demand'.
;SharedManagerServiceStartFailureNoError=failed to start the service. Refer to the Event Log for more details
;SharedManagerServiceLookupFailure=failed to look up the service process in the SCM ({0})
;SharedManagerServiceSidLookupFailure=failed to look up the service SID in the SCM ({0})
;SharedManagerServiceEndpointReadFailure=failed to read the service's endpoint with native error code {0}. See inner exception for details
;SharedManagerServiceSecurityFailed=the service failed the security checks
;SharedManagerUserSidLookupFailure=failed to retrieve the UserSid of the service process ({0})
;SharedManagerCurrentUserSidLookupFailure=failed to retrieve the UserSid of the current process
;SharedManagerLogonSidLookupFailure=failed to retrieve the LogonSid of the service process ({0})
;SharedManagerDataConnectionFailure=failed to establish a data connection to the service
;SharedManagerDataConnectionCreateFailure=failed to create a data connection to the service
;SharedManagerDataConnectionTimeout=failed to establish the data connection to the service because of a timeout
;SharedManagerDataConnectionPipeFailed=failed to establish the data connection because of an I/O error
;SharedManagerVersionUnsupported=the version is not supported by the service
;SharedManagerAllowDupHandleFailed=failed to grant the PROCESS_DUP_HANDLE access right to the target service's account SID '{0}'.
;SharedManagerPathTooLong=the URI is too long
;SharedManagerRegistrationQuotaExceeded=the quota was exceeded
;SharedManagerProtocolUnsupported=the protocol is not supported
;SharedManagerConflictingRegistration=the URI is already registered with the service
;SharedManagerFailedToListen=the service failed to listen
;Sharing_ConnectionDispatchFailed=The message could not be dispatched to the service at address '{0}'. Refer to the server Event Log for more details
;Sharing_EndpointUnavailable=The message could not be dispatched because the service at the endpoint address '{0}' is unavailable for the protocol of the address.
;Sharing_EmptyListenerEndpoint=The endpoint address for the NT service '{0}' read from shared memory is empty.
;Sharing_ListenerProxyStopped=The message could not be dispatched because the transport manager has been stopped. This can happen if the application is being recycled or disabled.
;UnexpectedEmptyElementExpectingClaim=The '{0}' from the '{1}' namespace is empty and does not specify a valid identity claim.
UnexpectedElementExpectingElement='{0}' from namespace '{1}' is not expected. Expecting element '{2}' from namespace '{3}'
;UnexpectedDuplicateElement='{0}' from namespace '{1}' is not expected to appear more than once
;UnsupportedSecurityPolicyAssertion=An unsupported security policy assertion was detected during the security policy import: {0}
;MultipleIdentities=The extensions cannot contain an Identity if one is supplied as a constructor argument.
InvalidUriValue=Value '{0}' provided for '{1}' from namespace '{2}' is an invalid absolute URI.
;InvalidLockOperationStack=Object synchronization method was called from an unsynchronized block of code. Previous Exit(): {0}
;InvalidLockOperation=Object synchronization method was called from an unsynchronized block of code.
;BindingDoesNotSupportProtectionForRst=The binding ('{0}','{1}') for contract ('{2}','{3}') is configured with SecureConversation, but the authentication mode is not able to provide the request/reply-based integrity and confidentiality required for the negotiation.
TransportDoesNotProtectMessage=The '{0}'.'{1}' binding is configured with an authentication mode that requires transport level integrity and confidentiality. However the transport cannot provide integrity and confidentiality.
;BindingDoesNotSupportWindowsIdenityForImpersonation=The contract operation '{0}' requires Windows identity for automatic impersonation. A Windows identity that represents the caller is not provided by binding ('{1}','{2}') for contract ('{3}','{4}'.
;ListenUriNotSet=A listen URI must be specified in order to open this {0}.
UnsupportedChannelInterfaceType=Channel interface type '{0}' is not supported.
;TransportManagerOpen=This property cannot be changed after the transport manager has been opened.
;TransportManagerNotOpen=This operation is only valid after the transport manager has been opened.
;UnrecognizedIdentityType=Unrecognized identity type Name='{0}', Namespace='{1}'.
;InvalidIdentityElement=Cannot read the Identity element. The Identity type is not supported or the Identity element is empty.
;UnableToLoadCertificateIdentity=Cannot load the X.509 certificate identity specified in the configuration.
;UnrecognizedClaimTypeForIdentity=The ClaimType '{0}' is not recognized. Expected ClaimType '{1}'.
AsyncCallbackException=An AsyncCallback threw an exception.
;SendCannotBeCalledAfterCloseOutputSession=You cannot Send messages on a channel after CloseOutputSession has been called.
CommunicationObjectCannotBeModifiedInState=The communication object, {0}, cannot be modified while it is in the {1} state.
;CommunicationObjectCannotBeModified=The communication object, {0}, cannot be modified unless it is in the Created state.
CommunicationObjectCannotBeUsed=The communication object, {0}, is in the {1} state. Communication objects cannot be used for communication unless they are in the Opened state.
CommunicationObjectFaulted1=The communication object, {0}, cannot be used for communication because it is in the Faulted state.
CommunicationObjectFaultedStack2=The communication object, {0}, cannot be used for communication because it is in the Faulted state: {1}
CommunicationObjectAborted1=The communication object, {0}, cannot be used for communication because it has been Aborted.
CommunicationObjectAbortedStack2=The communication object, {0}, cannot be used for communication because it has been Aborted: {1}
CommunicationObjectBaseClassMethodNotCalled=The communication object, {0}, has overridden the virtual function {1} but it does not call version defined in the base class.
CommunicationObjectInInvalidState=The communication object, {0}, is not part of WCF and is in an unsupported state '{1}'. This indicates an internal error in the implementation of that communication object.
ChannelFactoryCannotBeUsedToCreateChannels=A call to IChannelFactory.CreateChannel made on an object of type {0} failed because Open has not been called on this object.
ChannelParametersCannotBeModified=Cannot modify channel parameters because the {0} is in the {1} state. This operation is only supported in the Created state.
ChannelParametersCannotBePropagated=Cannot propagate channel parameters because the {0} is in the {1} state. This operation is only supported in the Opening or Opened state when the collection is locked.
;OneWayInternalTypeNotSupported=Binding '{0}' is not configured properly. OneWayBindingElement requires an inner binding element that supports IRequestChannel/IReplyChannel or IDuplexSessionChannel.
ChannelTypeNotSupported=The specified channel type {0} is not supported by this channel manager.
;SecurityContextMissing=SecurityContext for the UltimateReceiver role is missing from the SecurityContextProperty of the request message with action '{0}'.
;SecurityContextDoesNotAllowImpersonation=Cannot start impersonation because the SecurityContext for the UltimateReceiver role from the request message with the '{0}' action is not mapped to a Windows identity.
InvalidEnumValue=Unexpected internal enum value: {0}.
;InvalidDecoderStateMachine=Invalid decoder state machine.
;OperationPropertyIsRequiredForAttributeGeneration=Operation property of OperationAttributeGenerationContext is required to generate an attribute based on settings.
;InvalidMembershipProviderSpecifiedInConfig=The username/password Membership provider {0} specified in the configuration is invalid. No such provider was found registered under system.web/membership/providers.
;InvalidRoleProviderSpecifiedInConfig=The RoleProvider {0} specified in the configuration is invalid. No such provider was found registered under system.web/roleManager/providers.
ObjectDisposed=The {0} object has been disposed.
InvalidReaderPositionOnCreateMessage=The XmlReader used for the body of the message must be positioned on an element.
DuplicateMessageProperty=A property with the name '{0}' already exists.
MessagePropertyNotFound=A property with the name '{0}' is not present.
;HeaderAlreadyUnderstood=The message header with name '{0}' and namespace '{1}' is already present in the set of understood headers.
;HeaderAlreadyNotUnderstood=The message header with name '{0}' and namespace '{1}' is not present in the set of understood headers.
MultipleMessageHeaders=Multiple headers with name '{0}' and namespace '{1}' found.
MultipleMessageHeadersWithActor=Multiple headers with name '{0}' and namespace '{1}' and role '{2}' found.
MultipleRelatesToHeaders= Multiple RelatesTo headers with relationship '{0}' found. Only one is allowed per relationship.
ExtraContentIsPresentInFaultDetail=Additional XML content is present in the fault detail element. Only a single element is allowed.
MessageIsEmpty=The body of the message cannot be read because it is empty.
MessageClosed=Message is closed.
BodyWriterReturnedIsNotBuffered=The body writer returned from OnCreateBufferedCopy was not buffered.
BodyWriterCanOnlyBeWrittenOnce=The body writer does not support writing more than once because it is not buffered.
;RstrKeySizeNotProvided=KeySize element not present in RequestSecurityTokenResponse.
;RequestMessageDoesNotHaveAMessageID=A reply message cannot be created because the request message does not have a MessageID.
HeaderNotFound=There is not a header with name {0} and namespace {1} in the message.
;BufferIsNotRightSizeForBufferManager=This buffer cannot be returned to the buffer manager because it is the wrong size.
MessageBufferIsClosed=MessageBuffer is closed.
MessageTextEncodingNotSupported=The text encoding '{0}' used in the text message format is not supported.
AtLeastOneFaultReasonMustBeSpecified=At least one fault reason must be specified.
NoNullTranslations=The translation set cannot contain nulls.
FaultDoesNotHaveAnyDetail=The fault does not have detail information.
InvalidXmlQualifiedName=Expected XML qualified name, found '{0}'.
UnboundPrefixInQName=Unbound prefix used in qualified name '{0}'.
MessageBodyToStringError=... Error reading body: {0}: {1} ...
NoMatchingTranslationFoundForFaultText=The fault reason does not contain any text translations.
;CannotDetermineSPNBasedOnAddress=Client cannot determine the Service Principal Name based on the identity in the target address '{0}' for the purpose of SspiNegotiation/Kerberos. The target address identity must be a UPN identity (like acmedomain\\alice) or SPN identity (like host/bobs-machine).
XmlLangAttributeMissing=Required xml:lang attribute value is missing.
;EncoderUnrecognizedCharSet=Unrecognized charSet '{0}' in contentType.
EncoderUnrecognizedContentType=Unrecognized contentType ({0}). Expected: {1}.
;EncoderBadContentType=Cannot process contentType.
EncoderEnvelopeVersionMismatch=The envelope version of the incoming message ({0}) does not match that of the encoder ({1}). Make sure the binding is configured with the same version as the expected messages.
EncoderMessageVersionMismatch=The message version of the outgoing message ({0}) does not match that of the encoder ({1}). Make sure the binding is configured with the same version as the message.
;MtomEncoderBadMessageVersion=MessageVersion '{0}' not supported by MTOM encoder.
ReadNotSupported=Read is not supported on this stream.
SeekNotSupported=Seek is not supported on this stream.
;ChannelInitializationTimeout=A newly accepted connection did not receive initialization data from the sender within the configured ChannelInitializationTimeout ({0}). As a result, the connection will be aborted. If you are on a highly congested network, or your sending machine is heavily loaded, consider increasing this value or load-balancing your server.
;SocketCloseReadTimeout=The remote endpoint of the socket ({0}) did not respond to a close request within the allotted timeout ({1}). It is likely that the remote endpoint is not calling Close after receiving the EOF signal (null) from Receive. The time allotted to this operation may have been a portion of a longer timeout.
;SocketCloseReadReceivedData=A graceful close was attempted on the socket, but the other side ({0}) is still sending data.
;PipeCantCloseWithPendingWrite=The pipe cannot be closed while a write to the pipe is pending.
;PipeShutdownWriteError=The shutdown indicator could not be written to the pipe. The application on the other end of the pipe may not be listening for it. The pipe will still be closed.
;PipeShutdownReadError=The shutdown indicator was not received from the pipe. The application on the other end of the pipe may not have sent it. The pipe will still be closed.
;PipeNameCanNotBeAccessed=The pipe name could not be obtained for the pipe URI: {0}
;PipeNameCanNotBeAccessed2=The pipe name could not be obtained for {0}.
;PipeModeChangeFailed=The pipe was not able to be set to message mode: {0}
;PipeCloseFailed=The pipe could not close gracefully. This may be caused by the application on the other end of the pipe exiting.
;PipeAlreadyShuttingDown=The pipe cannot be written to because it is already in the process of shutting down.
;PipeSignalExpected=The read from the pipe expected just a signal, but received actual data.
;PipeAlreadyClosing=The pipe cannot be written to or read from because it is already in the process of being closed.
;PipeAcceptFailed=Server cannot accept pipe: {0}
;PipeListenFailed=Cannot listen on pipe '{0}': {1}
;PipeNameInUse=Cannot listen on pipe name '{0}' because another pipe endpoint is already listening on that name.
;PipeNameCantBeReserved=Cannot listen on pipe '{0}' because the pipe name could not be reserved: {1}
;PipeListenerDisposed=The pipe listener has been disposed.
;PipeListenerNotListening=Connections cannot be created until the pipe has started listening. Call Listen() before attempting to accept a connection.
;PipeConnectAddressFailed=A pipe endpoint exists for '{0}', but the connect failed: {1}
;PipeConnectFailed=Cannot connect to endpoint '{0}'.
;PipeConnectTimedOut=Cannot connect to endpoint '{0}' within the allotted timeout of {1}. The time allotted to this operation may have been a portion of a longer timeout.
;PipeConnectTimedOutServerTooBusy=Cannot connect to endpoint '{0}' within the allotted timeout of {1}. The server has likely reached the MaxConnections quota and is too busy to accept new connections. The time allotted to this operation may have been a portion of a longer timeout.
;PipeEndpointNotFound=The pipe endpoint '{0}' could not be found on your local machine.
;PipeUriSchemeWrong=URIs used with pipes must use the scheme: 'net.pipe'.
;PipeWriteIncomplete=The pipe write did not write all the bytes.
;PipeClosed=The operation cannot be completed because the pipe was closed. This may have been caused by the application on the other end of the pipe exiting.
;PipeReadTimedOut=The read from the pipe did not complete within the allotted timeout of {0}. The time allotted to this operation may have been a portion of a longer timeout.
;PipeWriteTimedOut=The write to the pipe did not complete within the allotted timeout of {0}. The time allotted to this operation may have been a portion of a longer timeout.
;PipeConnectionAbortedReadTimedOut=The pipe connection was aborted because an asynchronous read from the pipe did not complete within the allotted timeout of {0}. The time allotted to this operation may have been a portion of a longer timeout.
;PipeConnectionAbortedWriteTimedOut=The pipe connection was aborted because an asynchronous write to the pipe did not complete within the allotted timeout of {0}. The time allotted to this operation may have been a portion of a longer timeout.
;PipeWriteError=There was an error writing to the pipe: {0}.
;PipeReadError=There was an error reading from the pipe: {0}.
;PipeUnknownWin32Error=Unrecognized error {0} (0x{1})
;PipeKnownWin32Error={0} ({1}, 0x{2})
;PipeWritePending=There is already a write in progress for the pipe. Wait for the first operation to complete before attempting to write again.
;PipeReadPending=There is already a read in progress for the pipe. Wait for the first operation to complete before attempting to read again.
;PipeDuplicationFailed=There was an error duplicating the.
;SocketAbortedReceiveTimedOut=The socket was aborted because an asynchronous receive from the socket did not complete within the allotted timeout of {0}. The time allotted to this operation may have been a portion of a longer timeout.
;SocketAbortedSendTimedOut=The socket connection was aborted because an asynchronous send to the socket did not complete within the allotted timeout of {0}. The time allotted to this operation may have been a portion of a longer timeout.
;ThreadAcquisitionTimedOut=Cannot claim lock within the allotted timeout of {0}. The time allotted to this operation may have been a portion of a longer timeout.
;OperationInvalidBeforeSecurityNegotiation=This operation is not valid until security negotiation is complete.
;FramingError=Error while reading message framing format at position {0} of stream (state: {1})
;FramingPrematureEOF=More data was expected, but EOF was reached.
;FramingRecordTypeMismatch=Expected record type '{0}', found '{1}'.
;FramingVersionNotSupported=Framing major version {0} is not supported.
;FramingModeNotSupported=Framing mode {0} is not supported.
FramingSizeTooLarge=Specified size is too large for this implementation.
;FramingViaTooLong=The framing via size ({0}) exceeds the quota.
;FramingViaNotUri=The framing via ({0}) is not a valid URI.
;FramingFaultTooLong=The framing fault size ({0}) exceeds the quota.
;FramingContentTypeTooLong=The framing content type size ({0}) exceeds the quota.
FramingValueNotAvailable=The value cannot be accessed because it has not yet been fully decoded.
;FramingAtEnd=An attempt was made to decode a value after the framing stream was ended.
;RemoteSecurityNotNegotiatedOnStreamUpgrade=Stream Security is required at {0}, but no security context was negotiated. This is likely caused by the remote endpoint missing a StreamSecurityBindingElement from its binding.
;BinaryEncoderSessionTooLarge=The binary encoder session information exceeded the maximum size quota ({0}). To increase this quota, use the MaxSessionSize property on the BinaryMessageEncodingBindingElement.
BinaryEncoderSessionInvalid=The binary encoder session is not valid. There was an error decoding a previous message.
BinaryEncoderSessionMalformed=The binary encoder session information is not properly formed.
ReceiveShutdownReturnedFault=The channel received an unexpected fault input message while closing. The fault reason given is: '{0}'
ReceiveShutdownReturnedLargeFault=The channel received an unexpected fault input message with Action = '{0}' while closing. You should only close your channel when you are not expecting any more input messages.
ReceiveShutdownReturnedMessage=The channel received an unexpected input message with Action '{0}' while closing. You should only close your channel when you are not expecting any more input messages.
MaxReceivedMessageSizeExceeded=The maximum message size quota for incoming messages ({0}) has been exceeded. To increase the quota, use the MaxReceivedMessageSize property on the appropriate binding element.
MaxSentMessageSizeExceeded=The maximum message size quota for outgoing messages ({0}) has been exceeded.
;FramingMaxMessageSizeExceeded=The maximum message size quota for incoming messages has been exceeded for the remote channel. See the server logs for more details.
;StreamDoesNotSupportTimeout=TimeoutStream requires an inner Stream that supports timeouts; its CanTimeout property must be true.
;FilterExists=The filter already exists in the filter table.
;FilterUnexpectedError=An internal error has occurred. Unexpected error modifying filter table.
;FilterNodeQuotaExceeded=The number of XML infoset nodes inspected by the navigator has exceeded the quota ({0}).
;FilterCapacityNegative=Value cannot be negative.
;ActionFilterEmptyList=The set of actions cannot be empty.
;FilterUndefinedPrefix=The prefix '{0}' is not defined.
;FilterMultipleMatches=Multiple filters matched.
;FilterTableTypeMismatch=The type of IMessageFilterTable created for a particular Filter type must always be the same.
;FilterTableInvalidForLookup=The MessageFilterTable state is corrupt. The requested lookup cannot be performed.
;FilterBadTableType=The IMessageFilterTable created for a Filter cannot be a MessageFilterTable or a subclass of MessageFilterTable.
;FilterQuotaRange=NodeQuota must be greater than 0.
;FilterEmptyString=Parameter value cannot be an empty string.
;FilterInvalidInner=Required inner element '{0}' was not found.
;FilterInvalidAttribute=Invalid attribute on the XPath.
;FilterInvalidDialect=When present, the dialect attribute must have the value '{0}'.
;FilterCouldNotCompile=Could not compile the XPath expression '{0}' with the given XsltContext.
;FilterReaderNotStartElem=XmlReader not positioned at a start element.
;SeekableMessageNavInvalidPosition=The position is not valid for this navigator.
;SeekableMessageNavNonAtomized=Cannot call '{0}' on a non-atomized navigator.
;SeekableMessageNavIDNotSupported=XML unique ID not supported.
;SeekableMessageNavBodyForbidden=A filter has attempted to access the body of a Message. Use a MessageBuffer instead if body filtering is required.
;SeekableMessageNavOverrideForbidden=Not allowed to override prefix '{0}'.
;QueryNotImplemented=The function '{0}' is not implemented.
;QueryNotSortable=XPathNavigator positions cannot be compared.
;QueryMustBeSeekable=XPathNavigator must be a SeekableXPathNavigator.
;QueryContextNotSupportedInSequences=Context node is not supported in node sequences.
;QueryFunctionTypeNotSupported=IXsltContextFunction return type '{0}' not supported.
;QueryVariableTypeNotSupported=IXsltContextVariable type '{0}' not supported.
;QueryVariableNull=IXsltContextVariables cannot return null.
;QueryFunctionStringArg=The argument to an IXsltContextFunction could not be converted to a string.
;QueryItemAlreadyExists=An internal error has occurred. Item already exists.
;QueryBeforeNodes=Positioned before first element.
;QueryAfterNodes=Positioned after last element.
;QueryIteratorOutOfScope=The XPathNodeIterator has been invalidated. XPathNodeIterators passed as arguments to IXsltContextFunctions are only valid within the function. They cannot be cached for later use or returned as the result of the function.
AddressingVersionNotSupported=Addressing Version '{0}' is not supported.
;SupportedAddressingModeNotSupported=The '{0}' addressing mode is not supported.
MessagePropertyReturnedNullCopy=The IMessageProperty could not be copied. CreateCopy returned null.
MessageVersionUnknown=Unrecognized message version.
EnvelopeVersionUnknown=Unrecognized envelope version: {0}.
EnvelopeVersionNotSupported=Envelope Version '{0}' is not supported.
CannotDetectAddressingVersion=Cannot detect WS-Addressing version. EndpointReference does not start with an Element.
HeadersCannotBeAddedToEnvelopeVersion=Envelope Version '{0}' does not support adding Message Headers.
AddressingHeadersCannotBeAddedToAddressingVersion=Addressing Version '{0}' does not support adding WS-Addressing headers.
;AddressingExtensionInBadNS=The element '{0}' in namespace '{1}' is not valid. This either means that element '{0}' is a duplicate element, or that it is not a legal extension because extension elements cannot be in the addressing namespace.
MessageHeaderVersionNotSupported=The '{0}' header cannot be added because it does not support the specified message version '{1}'.
MessageHasBeenCopied=This message cannot support the operation because it has been copied.
MessageHasBeenWritten=This message cannot support the operation because it has been written.
MessageHasBeenRead=This message cannot support the operation because it has been read.
InvalidMessageState=An internal error has occurred. Invalid MessageState.
MessageBodyReaderInvalidReadState=The body reader is in ReadState '{0}' and cannot be consumed.
XmlBufferQuotaExceeded=The size necessary to buffer the XML content exceeded the buffer quota.
XmlBufferInInvalidState=An internal error has occurred. The XML buffer is not in the correct state to perform the operation.
;GetComputerNameReturnedInvalidLenth=GetComputerName returned an invalid length: {0}.
MessageBodyMissing=A body element was not found inside the message envelope.
MessageHeaderVersionMismatch=The version of the header(s) ({0}) differs from the version of the message ({1}).
ManualAddressingRequiresAddressedMessages=Manual addressing is enabled on this factory, so all messages sent must be pre-addressed.
;OneWayHeaderNotFound=A one-way header was expected on this message and none was found. It is possible that your bindings are mismatched.
;ReceiveTimedOut=Receive on local address {0} timed out after {1}. The time allotted to this operation may have been a portion of a longer timeout.
;ReceiveTimedOut2=Receive timed out after {0}. The time allotted to this operation may have been a portion of a longer timeout.
;WaitForMessageTimedOut=WaitForMessage timed out after {0}. The time allotted to this operation may have been a portion of a longer timeout.
;ReceiveTimedOutNoLocalAddress=Receive timed out after {0}. The time allotted to this operation may have been a portion of a longer timeout.
;ReceiveRequestTimedOutNoLocalAddress=Receive request timed out after {0}. The time allotted to this operation may have been a portion of a longer timeout.
;ReceiveRequestTimedOut=Receive request on local address {0} timed out after {1}. The time allotted to this operation may have been a portion of a longer timeout.
;SendToViaTimedOut=Sending to via {0} timed out after {1}. The time allotted to this operation may have been a portion of a longer timeout.
;CloseTimedOut=Close timed out after {0}. Increase the timeout value passed to the call to Close or increase the CloseTimeout value on the Binding. The time allotted to this operation may have been a portion of a longer timeout.
;OpenTimedOutEstablishingTransportSession=Open timed out after {0} while establishing a transport session to {1}. The time allotted to this operation may have been a portion of a longer timeout.
;RequestTimedOutEstablishingTransportSession=Request timed out after {0} while establishing a transport connection to {1}. The time allotted to this operation may have been a portion of a longer timeout.
;TcpConnectingToViaTimedOut=Connecting to via {0} timed out after {1}. Connection attempts were made to {2} of {3} available addresses ({4}). Check the RemoteAddress of your channel and verify that the DNS records for this endpoint correspond to valid IP Addresses. The time allotted to this operation may have been a portion of a longer timeout.
;RequestChannelSendTimedOut=The request channel timed out attempting to send after {0}. Increase the timeout value passed to the call to Request or increase the SendTimeout value on the Binding. The time allotted to this operation may have been a portion of a longer timeout.
;RequestChannelWaitForReplyTimedOut=The request channel timed out while waiting for a reply after {0}. Increase the timeout value passed to the call to Request or increase the SendTimeout value on the Binding. The time allotted to this operation may have been a portion of a longer timeout.
;#if DEBUG // add performance counter instead in v.Next - see MessageBus bug #54117
;HttpConcurrentReceiveQuotaReached=The HTTP concurrent receive quota was reached. The quota is {0}.
;#endif
;HttpTransportCannotHaveMultipleAuthenticationSchemes=The policy being imported for contract '{0}:{1}' contains multiple HTTP authentication scheme assertions. Since at most one such assertion is allowed, policy import has failed. This may be resolved by updating the policy to contain no more than one HTTP authentication scheme assertion.
;HttpIfModifiedSinceParseError=The value specified, '{0}', for the If-Modified-Since header does not parse into a valid date. Check the property value and ensure that it is of the proper format.
HttpSoapActionMismatch=The SOAP action specified on the message, '{0}', does not match the action specified on the HttpRequestMessageProperty, '{1}'.
;HttpSoapActionMismatchContentType=The SOAP action specified on the message, '{0}', does not match the action specified in the content-type of the HttpRequestMessageProperty, '{1}'.
;HttpSoapActionMismatchFault=The SOAP action specified on the message, '{0}', does not match the HTTP SOAP Action, '{1}'.
;HttpContentTypeFormatException=An error ({0}) occurred while parsing the content type of the HTTP request. The content type was: {1}.
HttpServerTooBusy=The HTTP service located at {0} is too busy.
HttpRequestAborted=The HTTP request to '{0}' was aborted. This may be due to the local channel being closed while the request was still in progress. If this behavior is not desired, then update your code so that it does not close the channel while request operations are still in progress.
HttpRequestTimedOut=The HTTP request to '{0}' has exceeded the allotted timeout of {1}. The time allotted to this operation may have been a portion of a longer timeout.
HttpRequestTimedOutWithoutDetail=The HTTP request to '{0}' has exceeded the allotted timeout. The time allotted to this operation may have been a portion of a longer timeout.
;HttpResponseTimedOut=The HTTP request to '{0}' has exceeded the allotted timeout of {1} while reading the response. The time allotted to this operation may have been a portion of a longer timeout.
HttpTransferError=An error ({0}) occurred while transmitting data over the HTTP channel.
;HttpReceiveFailure=An error occurred while receiving the HTTP response to {0}. This could be due to the service endpoint binding not using the HTTP protocol. This could also be due to an HTTP request context being aborted by the server (possibly due to the service shutting down). See server logs for more details.
HttpSendFailure=An error occurred while making the HTTP request to {0}. This could be due to the fact that the server certificate is not configured properly with HTTP.SYS in the HTTPS case. This could also be caused by a mismatch of the security binding between the client and the server.
;HttpAuthDoesNotSupportRequestStreaming=HTTP request streaming cannot be used in conjunction with HTTP authentication. Either disable request streaming or specify anonymous HTTP authentication.
;ReplyAlreadySent=A reply has already been sent from this RequestContext.
;HttpInvalidListenURI=Unable to start the HTTP listener. The URI provided, '{0}', is invalid for listening. Check the base address of your service and verify that it is a valid URI.
;RequestContextAborted=The requestContext has been aborted.
;ThreadNeutralSemaphoreAborted=The ThreadNeutralSemaphore has been aborted.
;ThreadNeutralSemaphoreAsyncAbort=The ThreadNeutralSemaphore.Abort is not supported for the asynchronous usage.
;UnrecognizedHostNameComparisonMode=Invalid HostNameComparisonMode value: {0}.
;BadData=Invalid data buffer.
;InvalidRenewResponseAction=A security session renew response was received with an invalid action '{0}'.
;InvalidCloseResponseAction=A security session close response was received with an invalid action '{0}',
;NullSessionRequestMessage=Could not formulate request message for security session operation '{0}'.
;IssueSessionTokenHandlerNotSet=There is no handler registered for session token issuance event.
;RenewSessionTokenHandlerNotSet=There is no handler registered for session token renew event.
;WrongIdentityRenewingToken=The identity of the security session renew message does not match the identity of the session token.
;InvalidRstRequestType=The RequestSecurityToken has an invalid or unspecified RequestType '{0}'.
;NoCloseTargetSpecified=The RequestSecurityToken must specify a CloseTarget.
;FailedSspiNegotiation=Secure channel cannot be opened because security negotiation with the remote endpoint has failed. This may be due to absent or incorrectly specified EndpointIdentity in the EndpointAddress used to create the channel. Please verify the EndpointIdentity specified or implied by the EndpointAddress correctly identifies the remote endpoint.
;BadCloseTarget=The CloseTarget specified '{0}' does not identify the security token that signed the message.
;RenewSessionMissingSupportingToken=The renew security session message does not have the session token as a supporting token.
;NoRenewTargetSpecified=The RequestSecurityToken must specify a RenewTarget.
;BadRenewTarget=There is no endorsing session token that matches the specified RenewTarget '{0}'.
;ReferenceListCannotBeEmpty=The ReferenceList element must have at least one DataReference or KeyReference.
;BadEncryptedBody=Invalid format for encrypted body.
;BadEncryptionState=The EncryptedData or EncryptedKey is in an invalid state for this operation.
;NoSignaturePartsSpecified=No signature message parts were specified for messages with the '{0}' action.
;NoEncryptionPartsSpecified=No encryption message parts were specified for messages with the '{0}' action.
;SecuritySessionFaultReplyWasSent=The receiver sent back a security session fault message. Retry the request.
;InnerListenerFactoryNotSet=The Inner listener factory of {0} must be set before this operation.
;SecureConversationBootstrapCannotUseSecureConversation=Cannot create security binding element based on configuration data. The secure conversation bootstrap requires another secure conversation which is not supported.
InnerChannelFactoryWasNotSet=Cannot open ChannelFactory as the inner channel factory was not set during the initialization process.
;SecurityProtocolFactoryDoesNotSupportDuplex=Duplex security is not supported by the security protocol factory '{0}'.
;SecurityProtocolFactoryDoesNotSupportRequestReply=Request-reply security is not supported by the security protocol factory '{0}'.
;SecurityProtocolFactoryShouldBeSetBeforeThisOperation=The security protocol factory must be set before this operation is performed.
;SecuritySessionProtocolFactoryShouldBeSetBeforeThisOperation=Security session protocol factory must be set before this operation is performed.
;SecureConversationSecurityTokenParametersRequireBootstrapBinding=Security channel or listener factory creation failed. Secure conversation security token parameters do not specify the bootstrap security binding element.
;PropertySettingErrorOnProtocolFactory=The required '{0}' property on the '{1}' security protocol factory is not set or has an invalid value.
;ProtocolFactoryCouldNotCreateProtocol=The protocol factory cannot create a protocol.
;IdentityCheckFailedForOutgoingMessage=The identity check failed for the outgoing message. The expected identity is '{0}' for the '{1}' target endpoint.
;IdentityCheckFailedForIncomingMessage=The identity check failed for the incoming message. The expected identity is '{0}' for the '{1}' target endpoint.
;DnsIdentityCheckFailedForIncomingMessageLackOfDnsClaim=The Identity check failed for the incoming message. The remote endpoint did not provide a domain name system (DNS) claim and therefore did not satisfied DNS identity '{0}'. This may be caused by lack of DNS or CN name in the remote endpoint X.509 certificate's distinguished name.
;DnsIdentityCheckFailedForOutgoingMessageLackOfDnsClaim=The Identity check failed for the outgoing message. The remote endpoint did not provide a domain name system (DNS) claim and therefore did not satisfied DNS identity '{0}'. This may be caused by lack of DNS or CN name in the remote endpoint X.509 certificate's distinguished name.
;DnsIdentityCheckFailedForIncomingMessage=Identity check failed for incoming message. The expected DNS identity of the remote endpoint was '{0}' but the remote endpoint provided DNS claim '{1}'. If this is a legitimate remote endpoint, you can fix the problem by explicitly specifying DNS identity '{1}' as the Identity property of EndpointAddress when creating channel proxy.
;DnsIdentityCheckFailedForOutgoingMessage=Identity check failed for outgoing message. The expected DNS identity of the remote endpoint was '{0}' but the remote endpoint provided DNS claim '{1}'. If this is a legitimate remote endpoint, you can fix the problem by explicitly specifying DNS identity '{1}' as the Identity property of EndpointAddress when creating channel proxy.
;SerializedTokenVersionUnsupported=The serialized token version {0} is unsupported.
;AuthenticatorNotPresentInRSTRCollection=The RequestSecurityTokenResponseCollection does not contain an authenticator.
;RSTRAuthenticatorHasBadContext=The negotiation RequestSecurityTokenResponse has a different context from the authenticator RequestSecurityTokenResponse.
;ServerCertificateNotProvided=The recipient did not provide its certificate. This certificate is required by the TLS protocol. Both parties must have access to their certificates.
;RSTRAuthenticatorNotPresent=The authenticator was not included in the final leg of negotiation.
;RSTRAuthenticatorIncorrect=The RequestSecurityTokenResponse CombinedHash is incorrect.
;ClientCertificateNotProvided=The certificate for the client has not been provided. The certificate can be set on the ClientCredentials or ServiceCredentials.
;ClientCertificateNotProvidedOnServiceCredentials=The client certificate is not provided. Specify a client certificate in ServiceCredentials.
;ClientCertificateNotProvidedOnClientCredentials=The client certificate is not provided. Specify a client certificate in ClientCredentials.
;ServiceCertificateNotProvidedOnServiceCredentials=The service certificate is not provided. Specify a service certificate in ServiceCredentials.
;ServiceCertificateNotProvidedOnClientCredentials=The service certificate is not provided for target '{0}'. Specify a service certificate in ClientCredentials.
UserNamePasswordNotProvidedOnClientCredentials=The username is not provided. Specify username in ClientCredentials.
ObjectIsReadOnly=Object is read-only.
;EmptyXmlElementError=Element {0} cannot be empty.
;UnexpectedXmlChildNode=XML child node {0} of type {1} is unexpected for element {2}.
;ContextAlreadyRegistered=The context-id={0} (generation-id={1}) is already registered with SecurityContextSecurityTokenAuthenticator.
;ContextAlreadyRegisteredNoKeyGeneration=The context-id={0} (no key generation-id) is already registered with SecurityContextSecurityTokenAuthenticator.
;ContextNotPresent=There is no SecurityContextSecurityToken with context-id={0} (generation-id={1}) registered with SecurityContextSecurityTokenAuthenticator.
;ContextNotPresentNoKeyGeneration=There is no SecurityContextSecurityToken with context-id={0} (no key generation-id) registered with SecurityContextSecurityTokenAuthenticator.
;InvalidSecurityContextCookie=The SecurityContextSecurityToken has an invalid Cookie. The following error occurred when processing the Cookie: '{0}'.
;SecurityContextNotRegistered=The SecurityContextSecurityToken with context-id={0} (key generation-id={1}) is not registered.
;SecurityContextExpired=The SecurityContextSecurityToken with context-id={0} (key generation-id={1}) has expired.
;SecurityContextExpiredNoKeyGeneration=The SecurityContextSecurityToken with context-id={0} (no key generation-id) has expired.
;NoSecurityContextIdentifier=The SecurityContextSecurityToken does not have a context-id.
;MessageMustHaveViaOrToSetForSendingOnServerSideCompositeDuplexChannels=For sending a message on server side composite duplex channels, the message must have either the 'Via' property or the 'To' header set.
;MessageViaCannotBeAddressedToAnonymousOnServerSideCompositeDuplexChannels=The 'Via' property on the message is set to Anonymous Uri '{0}'. Please set the 'Via' property to a non-anonymous address as message cannot be addressed to anonymous Uri on server side composite duplex channels.
;MessageToCannotBeAddressedToAnonymousOnServerSideCompositeDuplexChannels=The 'To' header on the message is set to Anonymous Uri '{0}'. Please set the 'To' header to a non-anonymous address as message cannot be addressed to anonymous Uri on server side composite duplex channels.
;SecurityBindingNotSetUpToProcessOutgoingMessages=This SecurityProtocol instance was not set up to process outgoing messages.
;SecurityBindingNotSetUpToProcessIncomingMessages=This SecurityProtocol instance was not set up to process incoming messages.
;TokenProviderCannotGetTokensForTarget=The token provider cannot get tokens for target '{0}'.
;UnsupportedKeyDerivationAlgorithm=Key derivation algorithm '{0}' is not supported.
;CannotFindCorrelationStateForApplyingSecurity=Cannot find the correlation state for applying security to reply at the responder.
;ReplyWasNotSignedWithRequiredSigningToken=The reply was not signed with the required signing token.
;EncryptionNotExpected=Encryption not expected for this message.
;SignatureNotExpected=A signature is not expected for this message.
;InvalidQName=The QName is invalid.
;UnknownICryptoType=The ICrypto implementation '{0}' is not supported.
;SameProtocolFactoryCannotBeSetForBothDuplexDirections=On DuplexSecurityProtocolFactory, the same protocol factory cannot be set for the forward and reverse directions.
;SuiteDoesNotAcceptAlgorithm=The algorithm '{0}' is not accepted for operation '{1}' by algorithm suite {2}.
;TokenDoesNotSupportKeyIdentifierClauseCreation='{0}' does not support '{1}' creation.
;UnableToCreateICryptoFromTokenForSignatureVerification=Cannot create an ICrypto interface from the '{0}' token for signature verification.
MessageSecurityVerificationFailed=Message security verification failed.
;TransportSecurityRequireToHeader=Transport secured messages should have the 'To' header specified.
;TransportSecuredMessageMissingToHeader=The message received over Transport security was missing the 'To' header.
;UnsignedToHeaderInTransportSecuredMessage=The message received over Transport security has unsigned 'To' header.
;TransportSecuredMessageHasMoreThanOneToHeader=More than one 'To' header specified in a message secured by Transport Security.
;TokenNotExpectedInSecurityHeader=Received security header contains unexpected token '{0}'.
;CannotFindCert=Cannot find the X.509 certificate using the following search criteria: StoreName '{0}', StoreLocation '{1}', FindType '{2}', FindValue '{3}'.
;CannotFindCertForTarget=Cannot find The X.509 certificate using the following search criteria: StoreName '{0}', StoreLocation '{1}', FindType '{2}', FindValue '{3}' for target '{4}'.
;FoundMultipleCerts=Found multiple X.509 certificates using the following search criteria: StoreName '{0}', StoreLocation '{1}', FindType '{2}', FindValue '{3}'. Provide a more specific find value.
;FoundMultipleCertsForTarget=Found multiple X.509 certificates using the following search criteria: StoreName '{0}', StoreLocation '{1}', FindType '{2}', FindValue '{3}' for target '{4}'. Provide a more specific find value.
;MissingKeyInfoInEncryptedKey=The KeyInfo clause is missing or empty in EncryptedKey.
;EncryptedKeyWasNotEncryptedWithTheRequiredEncryptingToken=The EncryptedKey clause was not wrapped with the required encryption token '{0}'.
;MessageWasNotEncryptedWithTheRequiredEncryptingToken=The message was not encrypted with the required encryption token.
;TimestampMustOccurFirstInSecurityHeaderLayout=The timestamp must occur first in this security header layout.
;TimestampMustOccurLastInSecurityHeaderLayout=The timestamp must occur last in this security header layout.
;AtMostOnePrimarySignatureInReceiveSecurityHeader=Only one primary signature is allowed in a security header.
;SigningTokenHasNoKeys=The signing token {0} has no keys. The security token is used in a context that requires it to perform cryptographic operations, but the token contains no cryptographic keys. Either the token type does not support cryptographic operations, or the particular token instance does not contain cryptographic keys. Check your configuration to ensure that cryptographically disabled token types (for example, UserNameSecurityToken) are not specified in a context that requires cryptographic operations (for example, an endorsing supporting token).
;SigningTokenHasNoKeysSupportingTheAlgorithmSuite=The signing token {0} has no key that supports the algorithm suite {1}.
;DelayedSecurityApplicationAlreadyCompleted=Delayed security application has already been completed.
;UnableToResolveKeyInfoClauseInDerivedKeyToken=Cannot resolve KeyInfo in derived key token for resolving source token: KeyInfoClause '{0}'.
;UnableToDeriveKeyFromKeyInfoClause=KeyInfo clause '{0}' resolved to token '{1}', which does not contain a Symmetric key that can be used for derivation.
;UnableToResolveKeyInfoForVerifyingSignature=Cannot resolve KeyInfo for verifying signature: KeyInfo '{0}', available tokens '{1}'.
;UnableToResolveKeyInfoForUnwrappingToken=Cannot resolve KeyInfo for unwrapping key: KeyInfo '{0}', available tokens '{1}'.
;UnableToResolveKeyInfoForDecryption=Cannot resolve KeyInfo for decryption: KeyInfo '{0}', available tokens '{1}'.
;EmptyBase64Attribute=An empty value was found for the required base-64 attribute name '{0}', namespace '{1}'.
;RequiredSecurityHeaderElementNotSigned=The security header element '{0}' with the '{1}' id must be signed.
;RequiredSecurityTokenNotSigned=The '{0}' security token with the '{1}' attachment mode must be signed.
;RequiredSecurityTokenNotEncrypted=The '{0}' security token with the '{1}' attachment mode must be encrypted.
;MessageBodyOperationNotValidInBodyState=Operation '{0}' is not valid in message body state '{1}'.
;EncryptedKeyWithReferenceListNotAllowed=EncryptedKey with ReferenceList is not allowed according to the current settings.
;UnableToFindTokenAuthenticator=Cannot find a token authenticator for the '{0}' token type. Tokens of that type cannot be accepted according to current security settings.
;NoPartsOfMessageMatchedPartsToSign=No signature was created because not part of the message matched the supplied message part specification.
;BasicTokenCannotBeWrittenWithoutEncryption=Supporting SecurityToken cannot be written without encryption.
;DuplicateIdInMessageToBeVerified=The '{0}' id occurred twice in the message that is supplied for verification.
;UnsupportedCanonicalizationAlgorithm=Canonicalization algorithm '{0}' is not supported.
;NoKeyInfoInEncryptedItemToFindDecryptingToken=The KeyInfo value was not found in the encrypted item to find the decrypting token.
;NoKeyInfoInSignatureToFindVerificationToken=No KeyInfo in signature to find verification token.
;SecurityHeaderIsEmpty=Security header is empty.
;EncryptionMethodMissingInEncryptedData=The encryption method is missing in encrypted data.
;EncryptedHeaderAttributeMismatch=The Encrypted Header and the Security Header '{0}' attribute did not match. Encrypted Header: {1}. Security Header: {2}.
;AtMostOneReferenceListIsSupportedWithDefaultPolicyCheck=At most one reference list is supported with default policy check.
;AtMostOneSignatureIsSupportedWithDefaultPolicyCheck=At most one signature is supported with default policy check.
;UnexpectedEncryptedElementInSecurityHeader=Unexpected encrypted element in security header.
;MissingIdInEncryptedElement=Id is missing in encrypted item in security header.
;InvalidDataReferenceInReferenceList=The data reference '{0}' in encryption reference list is not valid.
;TokenManagerCannotCreateTokenReference=The supplied token manager cannot create a token reference.
;TimestampToSignHasNoId=The timestamp element added to security header to sign has no id.
;EncryptedHeaderXmlMustHaveId=An encrypted header must have an id.
;UnableToResolveDataReference=The data reference '{0}' could not be resolved in the received message.
;TimestampAlreadySetForSecurityHeader=A timestamp element has already been set for this security header.
;DuplicateTimestampInSecurityHeader=More than one Timestamp element was present in security header.
;MismatchInSecurityOperationToken=The incoming message was signed with a token which was different from what used to encrypt the body. This was not expected.
;UnableToCreateSymmetricAlgorithmFromToken=Cannot create the '{0}' symmetric algorithm from the token.
;UnknownEncodingInBinarySecurityToken=Unrecognized encoding occurred while reading the binary security token.
;UnableToResolveReferenceUriForSignature=Cannot resolve reference URI '{0}' in signature to compute digest.
;NoTimestampAvailableInSecurityHeaderToDoReplayDetection=No timestamp is available in the security header to do replay detection.
;NoSignatureAvailableInSecurityHeaderToDoReplayDetection=No signature is available in the security header to provide the nonce for replay detection.
;CouldNotFindNamespaceForPrefix=There is no namespace binding for prefix '{0}' in scope.
;DerivedKeyCannotDeriveFromSecret=Derived Key Token cannot derive key from the secret.
;DerivedKeyPosAndGenBothSpecified=Both offset and generation cannot be specified for Derived Key Token.
;DerivedKeyPosAndGenNotSpecified=Either offset or generation must be specified for Derived Key Token.
;DerivedKeyTokenRequiresTokenReference=DerivedKeyToken requires a reference to a token.
;DerivedKeyLengthTooLong=DerivedKey length ({0}) exceeds the allowed settings ({1}).
;DerivedKeyLengthSpecifiedInImplicitDerivedKeyClauseTooLong=The Implicit derived key clause '{0}' specifies a derivation key length ({1}) which exceeds the allowed maximum length ({2}).
;DerivedKeyInvalidOffsetSpecified=The received derived key token has a invalid offset value specified. Value: {0}. The value should be greater than or equal to zero.
;DerivedKeyInvalidGenerationSpecified=The received derived key token has a invalid generation value specified. Value: {0}. The value should be greater than or equal to zero.
;ChildNodeTypeMissing=The XML element {0} does not have a child of type {1}.
;NoLicenseXml=RequestedSecurityToken not specified in RequestSecurityTokenResponse.
;UnsupportedBinaryEncoding=Binary encoding {0} is not supported.
;BadKeyEncryptionAlgorithm=Invalid key encryption algorithm {0}.
AsyncObjectAlreadyEnded=End has already been called on this asynchronous result object.
InvalidAsyncResult=The asynchronous result object used to end this operation was not the object that was returned when the operation was initiated.
;UnableToCreateTokenReference=Unable to create token reference.
;ConfigNull=null
;NonceLengthTooShort=The specified nonce is too short. The minimum required nonce length is 4 bytes.
;NoBinaryNegoToSend=There is no binary negotiation to send to the other party.
;BadSecurityNegotiationContext=Security negotiation failure because an incorrect Context attribute specified in RequestSecurityToken/RequestSecurityTokenResponse from the other party.
;NoBinaryNegoToReceive=No binary negotiation was received from the other party.
;ProofTokenWasNotWrappedCorrectly=The proof token was not wrapped correctly in the RequestSecurityTokenResponse.
;NoServiceTokenReceived=Final RSTR from other party does not contain a service token.
;InvalidSspiNegotiation=The Security Support Provider Interface (SSPI) negotiation failed.
;CannotAuthenticateServer=Cannot authenticate the other party.
;IncorrectBinaryNegotiationValueType=Incoming binary negotiation has invalid ValueType {0}.
;ChannelNotOpen=The channel is not open.
;FailToRecieveReplyFromNegotiation=Security negotiation failed because the remote party did not send back a reply in a timely manner. This may be because the underlying transport connection was aborted.
;MessageSecurityVersionOutOfRange=SecurityVersion must be WsSecurity10 or WsSecurity11.
CreationTimeUtcIsAfterExpiryTime=Creation time must be before expiration time.
;NegotiationStateAlreadyPresent=Negotiation state already exists for context '{0}'.
;CannotFindNegotiationState=Cannot find the negotiation state for the context '{0}'.
;OutputNotExpected=Send cannot be called when the session does not expect output.
;SessionClosedBeforeDone=The session was closed before message transfer was complete.
;CacheQuotaReached=The item cannot be added. The maximum cache size is ({0} items).
;NoServerX509TokenProvider=The server's X509SecurityTokenProvider cannot be null.
;UnexpectedBinarySecretType=Expected binary secret of type {0} but got secret of type {1}.
;UnsupportedPasswordType=The '{0}' username token has an unsupported password type.
;NoPassword=No password specified for username '{0}'.
;UnrecognizedIdentityPropertyType=Unrecognized identity property type: '{0}'.
;UnableToDemuxChannel=There was no channel that could accept the message with action '{0}'.
EndpointNotFound=There was no endpoint listening at {0} that could accept the message. This is often caused by an incorrect address or SOAP action. See InnerException, if present, for more details. In Silverlight, a 404 response code may be reported even when the service sends a different error code.
MaxReceivedMessageSizeMustBeInIntegerRange=This factory buffers messages, so the message sizes must be in the range of an integer value.
MaxBufferSizeMustMatchMaxReceivedMessageSize=Because messages are being buffered, MaxReceivedMessageSize and MaxBufferSize must be the same value.
MaxBufferSizeMustNotExceedMaxReceivedMessageSize=MaxBufferSize must not exceed MaxReceivedMessageSize.
;MessageSizeMustBeInIntegerRange=This Factory buffers messages, so the message sizes must be in the range of a int value.
;UriLengthExceedsMaxSupportedSize=URI {0} could not be set because its size ({1}) exceeds the max supported size ({2}).
;InValidateIdPrefix=Expecting first char - c - to be in set [Char.IsLetter(c) && c == '_', found '{0}'.
;InValidateId=Expecting all chars - c - of id to be in set [Char.IsLetter(c), Char.IsNumber(c), '.', '_', '-'], found '{0}'.
;HttpRegistrationAlreadyExists=HTTP could not register URL {0}. Another application has already registered this URL with HTTP.SYS.
;HttpRegistrationAccessDenied=HTTP could not register URL {0}. Your process does not have access rights to this namespace (see http://go.microsoft.com/fwlink/?LinkId=70353 for details).
;HttpRegistrationPortInUse=HTTP could not register URL {0} because TCP port {1} is being used by another application.
;HttpRegistrationLimitExceeded=HTTP could not register URL {0} because the MaxEndpoints quota has been exceeded. To correct this, either close other HTTP-based services, or increase your MaxEndpoints registry key setting (see http://go.microsoft.com/fwlink/?LinkId=70352 for details).
UnexpectedHttpResponseCode=The remote server returned an unexpected response: ({0}) {1}. In Silverlight, a 404 response code may be reported even when the service sends a different error code.
;HttpContentLengthIncorrect=The number of bytes available is inconsistent with the HTTP Content-Length header. There may have been a network error or the client may be sending invalid requests.
;OneWayUnexpectedResponse=A response was received from a one-way send over the underlying IRequestChannel. Make sure the remote endpoint has a compatible binding at its endpoint (one that contains OneWayBindingElement).
MissingContentType=The receiver returned an error indicating that the content type was missing on the request to {0}. See the inner exception for more information.
;DuplexChannelAbortedDuringOpen=Duplex channel to {0} was aborted during the open process.
;OperationAbortedDuringConnectionEstablishment=Operation was aborted while establishing a connection to {0}.
HttpAddressingNoneHeaderOnWire=The incoming message contains a SOAP header representing the WS-Addressing '{0}', yet the HTTP transport is configured with AddressingVersion.None. As a result, the message is being dropped.
MessageXmlProtocolError=There is a problem with the XML that was received from the network. See inner exception for more details.
;TcpV4AddressInvalid=An IPv4 address was specified ({0}), but IPv4 is not enabled on this machine.
;TcpV6AddressInvalid=An IPv6 address was specified ({0}), but IPv6 is not enabled on this machine.
;UniquePortNotAvailable=Cannot find a unique port number that is available for both IPv4 and IPv6.
;TcpAddressInUse=There is already a listener on IP endpoint {0}. Make sure that you are not trying to use this endpoint multiple times in your application and that there are no other applications listening on this endpoint.
;TcpConnectNoBufs=Insufficient winsock resources available to complete socket connection initiation.
;InsufficentMemory=Insufficient memory avaliable to complete the operation.
;TcpConnectError=Could not connect to {0}. TCP error code {1}: {2}.
;TcpConnectErrorWithTimeSpan=Could not connect to {0}. The connection attempt lasted for a time span of {3}. TCP error code {1}: {2}.
;TcpListenError=A TCP error ({0}: {1}) occurred while listening on IP Endpoint={2}.
;TcpTransferError=A TCP error ({0}: {1}) occurred while transmitting data.
;TcpLocalConnectionAborted=The socket connection was aborted by your local machine. This could be caused by a channel Abort(), or a transmission error from another thread using this socket.
;HttpResponseAborted=The HTTP request context was aborted while writing the response. As a result, the response may not have been completely written to the network. This can be remedied by gracefully closing the request context rather than aborting it.
;TcpConnectionResetError=The socket connection was aborted. This could be caused by an error processing your message or a receive timeout being exceeded by the remote host, or an underlying network resource issue. Local socket timeout was '{0}'.
;TcpConnectionTimedOut=The socket transfer timed out after {0}. You have exceeded the timeout set on your binding. The time allotted to this operation may have been a portion of a longer timeout.
;SocketConnectionDisposed=The socket connection has been disposed.
;SocketListenerDisposed=The socket listener has been disposed.
;SocketListenerNotListening=The socket listener is not listening.
;DuplexSessionListenerNotFound=No duplex session listener was listening at {0}. This could be due to an incorrect via set on the client or a binding mismatch.
;HttpTargetNameDictionaryConflict=The entry found in AuthenticationManager's CustomTargetNameDictionary for {0} does not match the requested identity of {1}.
HttpContentTypeHeaderRequired=An HTTP Content-Type header is required for SOAP messaging and none was found.
ContentTypeMismatch=Content Type {0} was sent to a service expecting {1}. The client and service bindings may be mismatched.
ResponseContentTypeMismatch=The content type {0} of the response message does not match the content type of the binding ({1}). If using a custom encoder, be sure that the IsContentTypeSupported method is implemented properly. The first {2} bytes of the response were: '{3}'.
ResponseContentTypeNotSupported=The content type {0} of the message is not supported by the encoder.
HttpToMustEqualVia=The binding specified requires that the to and via URIs must match because the Addressing Version is set to None. The to URI specified was '{0}'. The via URI specified was '{1}'.
;NullReferenceOnHttpResponse=The server challenged this request and streamed requests cannot be resubmitted. To enable HTTP server challenges, set your TransferMode to Buffered or StreamedResponse.
FramingContentTypeMismatch=Content Type {0} was not supported by service {1}. The client and service bindings may be mismatched.
;FramingFaultUnrecognized=Server faulted with code '{0}'.
;FramingContentTypeTooLongFault=Content type '{0}' is too long to be processed by the remote host. See the server logs for more details.
;FramingViaTooLongFault=Via '{0}' is too long to be processed by the remote host. See the server logs for more details.
;FramingModeNotSupportedFault=The .Net Framing mode being used is not supported by '{0}'. See the server logs for more details.
;FramingVersionNotSupportedFault=The .Net Framing version being used is not supported by '{0}'. See the server logs for more details.
;FramingUpgradeInvalid=The requested upgrade is not supported by '{0}'. This could be due to mismatched bindings (for example security enabled on the client and not on the server).
;SecurityServerTooBusy=Server '{0}' sent back a fault indicating it is too busy to process the request. Please retry later. Please see the inner exception for fault details.
;SecurityEndpointNotFound=Server '{0}' sent back a fault indicating it is in the process of shutting down. Please see the inner exception for fault details.
;ServerTooBusy=Server '{0}' is too busy to process this request. Try again later.
;UpgradeProtocolNotSupported=Protocol Type {0} was sent to a service that does not support that type of upgrade.
;UpgradeRequestToNonupgradableService=.Net Framing upgrade request for {0} was sent to a service that is not setup to receive upgrades.
;PreambleAckIncorrect=You have tried to create a channel to a service that does not support .Net Framing.
;PreambleAckIncorrectMaybeHttp=You have tried to create a channel to a service that does not support .Net Framing. It is possible that you are encountering an HTTP endpoint.
;StreamError=An error occurred while transmitting data.
;ServerRejectedUpgradeRequest=The server rejected the upgrade request.
;ServerRejectedSessionPreamble=The server at {0} rejected the session-establishment request.
;UnableToResolveHost=Cannot resolve the host name of URI \"{0}\" using DNS.
;HttpRequiresSingleAuthScheme=The '{0}' authentication scheme has been specified on the HTTP factory. However, the factory only supports specification of exactly one authentication scheme. Valid authentication schemes are Digest, Negotiate, NTLM, Basic, or Anonymous.
;HttpProxyRequiresSingleAuthScheme=The '{0}' authentication scheme has been specified for the proxy on the HTTP factory. However, the factory only supports specification of exactly one authentication scheme. Valid authentication schemes are Digest, Negotiate, NTLM, Basic, or Anonymous.
;HttpMutualAuthNotSatisfied=The remote HTTP server did not satisfy the mutual authentication requirement.
;HttpAuthorizationFailed=The HTTP request is unauthorized with client authentication scheme '{0}'. The authentication header received from the server was '{1}'.
;HttpAuthenticationFailed=The HTTP request with client authentication scheme '{0}' failed with '{1}' status.
;HttpAuthorizationForbidden=The HTTP request was forbidden with client authentication scheme '{0}'.
InvalidUriScheme=The provided URI scheme '{0}' is invalid; expected '{1}'.
;HttpAuthSchemeAndClientCert=The HTTPS listener factory was configured to require a client certificate and the '{0}' authentication scheme. However, only one form of client authentication can be required at once.
;NoTransportManagerForUri=Could not find an appropriate transport manager for listen URI '{0}'.
;ListenerFactoryNotRegistered=The specified channel listener at '{0}' is not registered with this transport manager.
;HttpsExplicitIdentity=The HTTPS channel factory does not support explicit specification of an identity in the EndpointAddress unless the authentication scheme is NTLM or Negotiate.
;HttpsIdentityMultipleCerts=The endpoint identity specified when creating the HTTPS channel to '{0}' contains multiple server certificates. However, the HTTPS transport only supports the specification of a single server certificate. In order to create an HTTPS channel, please specify no more than one server certificate in the endpoint identity.
;HttpsServerCertThumbprintMismatch=The server certificate with name '{0}' failed identity verification because its thumbprint ('{1}') does not match the one specified in the endpoint identity ('{2}'). As a result, the current HTTPS request has failed. Please update the endpoint identity used on the client or the certificate used by the server.
;DuplicateRegistration=A registration already exists for URI '{0}'.
;SecureChannelFailure=Could not establish secure channel for SSL/TLS with authority '{0}'.
;TrustFailure=Could not establish trust relationship for the SSL/TLS secure channel with authority '{0}'.
;NoCompatibleTransportManagerForUri=Could not find a compatible transport manager for URI '{0}'.
;HttpSpnNotFound=The SPN for the responding server at URI '{0}' could not be determined.
;StreamMutualAuthNotSatisfied=The remote server did not satisfy the mutual authentication requirement.
;TransferModeNotSupported=Transfer mode {0} is not supported by {1}.
;InvalidTokenProvided=The token provider of type '{0}' did not return a token of type '{1}'. Check the credential configuration.
;NoUserNameTokenProvided=The required UserNameSecurityToken was not provided.
;RemoteIdentityFailedVerification=The following remote identity failed verification: '{0}'.
;UseDefaultWebProxyCantBeUsedWithExplicitProxyAddress=You cannot specify an explicit Proxy Address as well as UseDefaultWebProxy=true in your HTTP Transport Binding Element.
;ProxyImpersonationLevelMismatch=The HTTP proxy authentication credential specified an impersonation level restriction ({0}) that is stricter than the restriction for target server authentication ({1}).
;ProxyAuthenticationLevelMismatch=The HTTP proxy authentication credential specified an mutual authentication requirement ({0}) that is stricter than the requirement for target server authentication ({1}).
;CredentialDisallowsNtlm=The NTLM authentication scheme was specified, but the target credential does not allow NTLM.
;DigestExplicitCredsImpersonationLevel=The impersonation level '{0}' was specified, yet HTTP Digest authentication can only support 'Impersonation' level when used with an explicit credential.
;UriGeneratorSchemeMustNotBeEmpty=The scheme parameter must not be empty.
;UnsupportedSslProtectionLevel=The protection level '{0}' was specified, yet SSL transport security only supports EncryptAndSign.
;HttpNoTrackingService={0}. This often indicates that a service that HTTP.SYS depends upon (such as httpfilter) is not started.
;HttpNetnameDeleted={0}. This often indicates that the HTTP client has prematurely closed the underlying TCP connection.
;TimeoutInputQueueDequeue1=A Dequeue operation timed out after {0}. The time allotted to this operation may have been a portion of a longer timeout.
TimeoutServiceChannelConcurrentOpen1=Opening the channel timed out after {0}. The time allotted to this operation may have been a portion of a longer timeout.
TimeoutServiceChannelConcurrentOpen2=Opening the {0} channel timed out after {1}. The time allotted to this operation may have been a portion of a longer timeout.
;TimeSpanMustbeGreaterThanTimeSpanZero=TimeSpan must be greater than TimeSpan.Zero.
ValueMustBeNonNegative=The value of this argument must be non-negative.
ValueMustBePositive=The value of this argument must be positive.
;ValueMustBeGreaterThanZero=The value of this argument must be greater than 0.
ValueMustBeInRange=The value of this argument must fall within the range {0} to {1}.
OffsetExceedsBufferBound=The specified offset exceeds the upper bound of the buffer ({0}).
;OffsetExceedsBufferSize=The specified offset exceeds the buffer size ({0} bytes).
;SizeExceedsRemainingBufferSpace=The specified size exceeds the remaining buffer space ({0} bytes).
;SpaceNeededExceedsMessageFrameOffset=The space needed for encoding ({0} bytes) exceeds the message frame offset.
;FaultConverterDidNotCreateFaultMessage={0} returned true from OnTryCreateFaultMessage, but did not return a fault message.
;FaultConverterCreatedFaultMessage={0} returned false from OnTryCreateFaultMessage, but returned a non-null fault message.
FaultConverterDidNotCreateException={0} returned true from OnTryCreateException, but did not return an Exception.
FaultConverterCreatedException={0} returned false from OnTryCreateException, but returned a non-null Exception (See InnerException for details).
;InfoCardInvalidChain=Policy chain contains self issued URI or a managed issuer in the wrong position.
;FullTrustOnlyBindingElementSecurityCheck1=The Binding with name {0} failed validation because it contains a BindingElement with type {1} which is not supported in partial trust. Consider using BasicHttpBinding or WSHttpBinding, or hosting your application in a full-trust environment.
;FullTrustOnlyBindingElementSecurityCheckWSHttpBinding1=The WSHttpBinding with name {0} failed validation because it contains a BindingElement with type {1} which is not supported in partial trust. Consider disabling the message security and reliable session options, using BasicHttpBinding, or hosting your application in a full-trust environment.
;FullTrustOnlyBindingSecurityCheck1=The Binding with name {0} failed validation because the Binding type {1} is not supported in partial trust. Consider using BasicHttpBinding or WSHttpBinding, or hosting your application in a full-trust environment.
;PartialTrustServiceCtorNotVisible=The Service with name '{0}' could not be constructed because the application does not have permission to construct the type: both the Type and its default parameter-less constructor must be public.
;PartialTrustServiceMethodNotVisible=The Method with name '{1}' in Type '{0}' could not be invoked because the application does not have permission to invoke the method: both the Method and its containing Type must be public.
;PartialTrustNonHttpActivation=The operation is not supported because the protocol {0} is enabled for application '{1}' and the application is running in partial trust. Only the http and https protocols are supported in partial trust applications. Either remove the other protocols from the protocol list in the Windows Process Activation Service configuration or configure the application to run in full trust.
;PartialTrustPerformanceCountersNotEnabled=Access to performance counters is denied. Application may be running in partial trust. Either disable performance counters or configure the application to run in full trust.
; ---------------------------------------------------------------------------------------------------------------------
; RM
; ---------------------------------------------------------------------------------------------------------------------
;AcksToMustBeSameAsRemoteAddress=The remote endpoint requested an address for acknowledgements that is not the same as the address for application messages. The channel could not be opened because this is not supported. Ensure the endpoint address used to create the channel is identical to the one the remote endpoint was set up with.
;AcksToMustBeSameAsRemoteAddressReason=The address for acknowledgements must be the same as the address for application messages. Verify that your endpoint is configured to use the same URI for these two addresses.
;AssertionNotSupported=The {0}:{1} assertion is not supported.
;CloseOutputSessionErrorReason=An unexpected error occurred while attempting to close the output half of the duplex reliable session.
;ConflictingAddress=The remote endpoint sent conflicting requests to create a reliable session. The conflicting requests have inconsistent filter criteria such as address or action. The reliable session has been faulted.
;ConflictingOffer=The remote endpoint sent conflicting requests to create a reliable session. The remote endpoint requested both a one way and a two way session. The reliable session has been faulted.
;CouldNotParseWithAction=A message with action {0} could not be parsed.
;CSRefused=The request to create a reliable session has been refused by the RM Destination. {0} The channel could not be opened.
;CSRefusedAcksToMustEqualEndpoint=The endpoint processing requests to create a reliable session only supports sessions in which the AcksTo Uri and the Endpoint Uri are the same.
;CSRefusedAcksToMustEqualReplyTo=The endpoint processing requests to create a reliable session only supports sessions in which the AcksTo Uri and the ReplyTo Uri are the same.
;CSRefusedDuplexNoOffer=The endpoint at {0} processes duplex sessions. The create sequence request must contain an offer for a return sequence. This is likely caused by a binding mismatch.
;CSRefusedInputOffer=The endpoint at {0} processes input sessions. The create sequence request must not contain an offer for a return sequence. This is likely caused by a binding mismatch.
;CSRefusedInvalidIncompleteSequenceBehavior=The request to create a reliable session contains an invalid wsrm:IncompleteSequenceBehavior value. This is a WS-ReliableMessaging protocol violation.
;CSRefusedNoSTRWSSecurity=The request to create a reliable session contains the wsse:SecurityTokenReference but does not carry a wsrm:UsesSequenceSTR header. This is a WS-ReliableMessaging protocol violation. The session could not be created.
;CSRefusedReplyNoOffer=The endpoint at {0} processes reply sessions. The create sequence request must contain an offer for a return sequence. This is likely caused by a binding mismatch.
;CSRefusedRequiredSecurityElementMissing=The RM Destination requires the WS-SecureConversation protocol in the binding. This is likely caused by a binding mismatch.
;CSRefusedSSLNotSupported=The endpoint processing requests to create a reliable session does not support sessions that use SSL. This is likely caused by a binding mismatch. The session could not be created.
;CSRefusedSTRNoWSSecurity=The request to create a reliable session carries a wsrm:UsesSequenceSTR header, but does not contain the wsse:SecurityTokenReference. This is a WS-ReliableMessaging protocol violation. The session could not be created.
;CSRefusedUnexpectedElementAtEndOfCSMessage=The message is not a valid SOAP message. The body contains more than 1 root element.
;CSResponseOfferRejected=The remote endpoint replied to a request for a two way session with an offer for a one way session. This is likely caused by a binding mismatch. The channel could not be opened.
;CSResponseOfferRejectedReason=The client requested creation of a two way session. A one way session was created. The session cannot continue without as a one way session. This is likely caused by a binding mismatch.
;CSResponseWithInvalidIncompleteSequenceBehavior=The response to the request to create a reliable session contains an invalid wsrm:IncompleteSequenceBehavior value. This is a WS-ReliableMessaging protocol violation.
;CSResponseWithOffer=The remote endpoint replied to a request for a one way session with an offer for a two way session. This is a WS-ReliableMessaging protocol violation. The channel could not be opened.
;CSResponseWithOfferReason=A return sequence was not offered by the create sequence request. The create sequence response cannot accept a return sequence.
;CSResponseWithoutOffer=The remote endpoint replied to a request for a two way session with an offer for a one way session. This is a WS-ReliableMessaging protocol violation. The channel could not be opened.
;CSResponseWithoutOfferReason=A return sequence was offered by the create sequence request but the create sequence response did not accept this sequence.
;DeliveryAssuranceRequiredNothingFound=The WS-RM policy under the namespace {0} requires the wsrmp:ExactlyOnce, wsrmp:AtLeastOnce, or wsrmp:AtMostOnce assertion. Nothing was found.
;DeliveryAssuranceRequired=The WS-RM policy under the namespace {0} requires the wsrmp:ExactlyOnce, wsrmp:AtLeastOnce, or wsrmp:AtMostOnce assertion. The {1} element under the {2} namespace was found.
;EarlyRequestTerminateSequence=The remote endpoint sent a TerminateSequence protocol message before fully acknowledging all messages in the reply sequence. This is a violation of the reliable request reply protocol. The reliable session was faulted.
;EarlySecurityClose=The remote endpoint has closed the underlying secure session before the reliable session fully completed. The reliable session was faulted.
;EarlySecurityFaulted=The underlying secure session has faulted before the reliable session fully completed. The reliable session was faulted.
;EarlyTerminateSequence=The remote endpoint has errantly sent a TerminateSequence protocol message before the sequence finished.
;ElementFound=The {0}:{1} element requires a {2}:{3} child element but has the {4} child element under the {5} namespace.
;ElementRequired=The {0}:{1} element requires a {2}:{3} child element but has no child elements.
;InconsistentLastMsgNumberExceptionString=The remote endpoint specified two different last message numbers. The reliable session is in an inconsistent state since it cannot determine the actual last message. The reliable session was faulted.
;InvalidAcknowledgementFaultReason=The SequenceAcknowledgement violates the cumulative acknowledgement invariant.
;InvalidAcknowledgementReceived=A violation of acknowledgement protocol has been detected. An InvalidAcknowledgement fault was sent to the remote endpoint and the reliable session was faulted.
;InvalidBufferRemaining=An acknowledgement was received indicating the remaining buffer space on the remote endpoint is {0}. This number cannot be less than zero. The reliable session was faulted.
;InvalidSequenceNumber=A message was received with a sequence number of {0}. Sequence numbers cannot be less than 1. The reliable session was faulted.
;InvalidSequenceRange=An acknowledgement range starting at {0} and ending at {1} was received. This is an invalid acknowledgement range. The reliable session was faulted.
;InvalidWsrmResponseChannelNotOpened=The remote endpoint responded to the {0} request with a response with action {1}. The response must be a {0}Response with action {2}. The channel could not be opened.
;InvalidWsrmResponseSessionFaultedExceptionString=The remote endpoint responded to the {0} request with a response with action {1}. The response must be a {0}Response with action {2}. The channel was faulted.
;InvalidWsrmResponseSessionFaultedFaultString=The {0} request's response was a message with action {1}. The response must be a {0}Response with action {2}. The reliable session cannot continue.
;LastMessageNumberExceeded=A message was received with a sequence number higher than the sequence number of the last message in this sequence. This is a violation of the sequence number protocol. The reliable session was faulted.
;LastMessageNumberExceededFaultReason=The value for wsrm:MessageNumber exceeds the value of the MessageNumber accompanying a LastMessage element in this Sequence.
;ManualAddressingNotSupported=Binding validation failed because the TransportBindingElement's ManualAddressing property was set to true on a binding that is configured to create reliable sessions. This combination is not supported and the channel factory or service host was not opened.
;MaximumRetryCountExceeded=The maximum retry count has been exceeded with no response from the remote endpoint. The reliable session was faulted. This is often an indication that the remote endpoint is no longer available.
;MessageExceptionOccurred=A problem occurred while reading a message. See inner exception for details.
;MessageNumberRollover=The maximum message number for this sequence has been exceeded. The reliable session was faulted.
;MessageNumberRolloverFaultReason=The maximum value for wsrm:MessageNumber has been exceeded.
;MillisecondsNotConvertibleToBindingRange=The {0} assertion's Milliseconds attribute does not fall within the range this binding uses. The ReliableSessionBindingElement could not be created.
;MissingFinalAckExceptionString=The remote endpoint did not include a final acknowledgement in the reply to the close sequence request message. This is a violation of the WS-ReliableMessaging protocol. The reliable session was faulted.
;MissingMessageIdOnWsrmRequest=The wsa:MessageId header must be present on a wsrm:{0} message.
;MissingRelatesToOnWsrmResponseReason=The returned wsrm:{0}Response message was missing the required wsa:RelatesTo header. This is a violation of the WS-Addressing request reply protocol. The reliable session was faulted.
;MissingReplyToOnWsrmRequest=The wsa:ReplyTo header must be present on a wsrm:{0} message.
;MultipleVersionsFoundInPolicy=More than one version of the {0} assertion was found. The ReliableSessionBindingElement could not be created.
;NoActionNoSequenceHeaderReason=The endpoint only processes messages using the WS-ReliableMessaging protocol. The message sent to the endpoint does not have an action or any headers used by the protocol and cannot be processed.