<?xml version="1.0" encoding="utf-8"?>
<root>
  <!-- 
    Microsoft ResX Schema 
    
    Version 1.3
    
    The primary goals of this format is to allow a simple XML format 
    that is mostly human readable. The generation and parsing of the 
    various data types are done through the TypeConverter classes 
    associated with the data types.
    
    Example:
    
    ... ado.net/XML headers & schema ...
    <resheader name="resmimetype">text/microsoft-resx</resheader>
    <resheader name="version">1.3</resheader>
    <resheader name="reader">System.Resources.ResXResourceReader, System.Windows.Forms, ...</resheader>
    <resheader name="writer">System.Resources.ResXResourceWriter, System.Windows.Forms, ...</resheader>
    <data name="Name1">this is my long string</data>
    <data name="Color1" type="System.Drawing.Color, System.Drawing">Blue</data>
    <data name="Bitmap1" mimetype="application/x-microsoft.net.object.binary.base64">
        [base64 mime encoded serialized .NET Framework object]
    </data>
    <data name="Icon1" type="System.Drawing.Icon, System.Drawing" mimetype="application/x-microsoft.net.object.bytearray.base64">
        [base64 mime encoded string representing a byte array form of the .NET Framework object]
    </data>
                
    There are any number of "resheader" rows that contain simple 
    name/value pairs.
    
    Each data row contains a name, and value. The row also contains a 
    type or mimetype. Type corresponds to a .NET class that support 
    text/value conversion through the TypeConverter architecture. 
    Classes that don't support this are serialized and stored with the 
    mimetype set.
    
    The mimetype is used forserialized objects, and tells the 
    ResXResourceReader how to depersist the object. This is currently not 
    extensible. For a given mimetype the value must be set accordingly:
    
    Note - application/x-microsoft.net.object.binary.base64 is the format 
    that the ResXResourceWriter will generate, however the reader can 
    read any of the formats listed below.
    
    mimetype: application/x-microsoft.net.object.binary.base64
    value   : The object must be serialized with 
            : System.Serialization.Formatters.Binary.BinaryFormatter
            : and then encoded with base64 encoding.
    
    mimetype: application/x-microsoft.net.object.soap.base64
    value   : The object must be serialized with 
            : System.Runtime.Serialization.Formatters.Soap.SoapFormatter
            : and then encoded with base64 encoding.

    mimetype: application/x-microsoft.net.object.bytearray.base64
    value   : The object must be serialized into a byte array 
            : using a System.ComponentModel.TypeConverter
            : and then encoded with base64 encoding.
    -->
  <xsd:schema id="root" xmlns="" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:msdata="urn:schemas-microsoft-com:xml-msdata">
    <xsd:element name="root" msdata:IsDataSet="true">
      <xsd:complexType>
        <xsd:choice maxOccurs="unbounded">
          <xsd:element name="data">
            <xsd:complexType>
              <xsd:sequence>
                <xsd:element name="value" type="xsd:string" minOccurs="0" msdata:Ordinal="1" />
                <xsd:element name="comment" type="xsd:string" minOccurs="0" msdata:Ordinal="2" />
              </xsd:sequence>
              <xsd:attribute name="name" type="xsd:string" msdata:Ordinal="1" />
              <xsd:attribute name="type" type="xsd:string" msdata:Ordinal="3" />
              <xsd:attribute name="mimetype" type="xsd:string" msdata:Ordinal="4" />
            </xsd:complexType>
          </xsd:element>
          <xsd:element name="resheader">
            <xsd:complexType>
              <xsd:sequence>
                <xsd:element name="value" type="xsd:string" minOccurs="0" msdata:Ordinal="1" />
              </xsd:sequence>
              <xsd:attribute name="name" type="xsd:string" use="required" />
            </xsd:complexType>
          </xsd:element>
        </xsd:choice>
      </xsd:complexType>
    </xsd:element>
  </xsd:schema>
  <resheader name="resmimetype">
    <value>text/microsoft-resx</value>
  </resheader>
  <resheader name="version">
    <value>1.3</value>
  </resheader>
  <resheader name="reader">
    <value>System.Resources.ResXResourceReader, System.Windows.Forms, Version=1.0.5000.0, Culture=neutral, PublicKeyToken=b77a5c561934e089</value>
  </resheader>
  <resheader name="writer">
    <value>System.Resources.ResXResourceWriter, System.Windows.Forms, Version=1.0.5000.0, Culture=neutral, PublicKeyToken=b77a5c561934e089</value>
  </resheader>
  <data name="SecSetupAndInroInvalidResponseStatus">
    <value>Response status '{0}' is not a valid status for SecuritySetupAndIntroResponseMessage. The only acceptable status is 'success'.</value>
  </data>
  <data name="VlSimpleResponseMsgWrongResponseStatus">
    <value>This response status ({0}) is not a valid status for VistALink simple response messages. 'success' and 'failure' are the only acceptable status values. </value>
  </data>
  <data name="SecurityResponseFailureMsgInvalidResponseStatus">
    <value>Response status '{0}' is not valid for SecurityLogonResponseFailureMessage. The only accepted response status is 'failure'.</value>
  </data>
  <data name="XmlParseCDataNotFoundWhereExpected">
    <value>CDATA node was not found where expected. It was expected to be a child node of the element '{0}'.</value>
  </data>
  <data name="VistAObfuscatorStringToDeobufscateIsTooShort">
    <value>Input string to deobfuscate must be at least 2 byte long. </value>
  </data>
  <data name="VistALinkCloseSocketRequestMsgIncorrectHandlerMode">
    <value>VistALink close socket request message must be always in '{0}' mode, but was in '{1}' mode.</value>
  </data>
  <data name="PartialSuccessInvalidResponseStatus">
    <value>Response status '{0}' is not a valid status for a SecurityBasePartialSuccessResponseMessage message or its children. 'partialSuccess' is the only acceptable response status.</value>
  </data>
  <data name="ServerConnectionInfoPortNumberIsOutOfRange">
    <value>M server port number is out of allowed range. Port number must be a represented with a natural number between {0} and {1}. </value>
  </data>
  <data name="RpcParameterCollectionDuplicateParameterPosition">
    <value>RPC parameter with position {0} already exists in the RPC parameters collection. Since RPC parameter position is used as a unique key identifying parameter in collection, no parameters with duplicate positions are allowed within single RPC parameters collection instance.</value>
  </data>
  <data name="VistAObfuscatorStringToDeobufscateIsInvalid">
    <value>Source string to deobfuscate appears to be invalid, malformed or obfuscated with another version of VistA hash algorithm. It cannot be deobfuscated because either decoded associator or identifier offset (or both) is out of the bounds of the cipherpad.</value>
  </data>
  <data name="MalformedVistALinkMessageXmlString">
    <value>Unable to load XML document and create VistALink message object from the supplied string. Probably, string does not contain well-formed XML.</value>
  </data>
  <data name="VistASecurityCodeInputStringIsTooShort">
    <value>The supplied string is too short ({0} character(s) long). VistA security code must be at least {1} characters long.</value>
  </data>
  <data name="XmlParseMoreThanOneElementWasFound">
    <value>More than one XML element with tag name '{0}' was found under node '{1}' while only one was expected.</value>
  </data>
  <data name="DivisionListAtLeastTwoEntriesRequired">
    <value>There must be at least 2 divisions specified in divisions list.</value>
  </data>
  <data name="VistASecurityCodeSuppliedSecurityStringWasInvalid">
    <value>The supplied security code string was invalid. {0}</value>
  </data>
  <data name="InvalidRpcParameterPosition">
    <value>Parameter position must be a positive integer value between '{0}' and '{1}', but was '{2}'.</value>
  </data>
  <data name="SecDivisionRequestMessageInvalidIEN">
    <value>Specified internal entry number (IEN) of division ({0}) is invalid. Division IEN must be represented with non-empty string value.</value>
  </data>
  <data name="ServerConnectionInfoCollectionDuplicateHandle">
    <value>{0} object with the same handle ({1}) already exists in the collection.</value>
  </data>
  <data name="TimeoutInputStringIsNotNumeric">
    <value>Input string cannot be converted to positive integer. Timeout must be represented with all-digits non-empty string (e.g. '323' or '4', but not '-2', '2.2') specyfing positive integer.</value>
  </data>
  <data name="MaxNumberOfRpcParametersReached">
    <value>The maximum number of RPC parameters ({0}) was reached. To modify this number use application configuration file. Be aware that VistALink server must support the maximum number of parameters you specify. </value>
  </data>
  <data name="XmlDeserializationFailedDueToInnerException">
    <value>Failed to create an instance of {0} while deserializing object from XML. XML parse of element '{1}' caused an exception. Please review an inner exception information to get more details.</value>
  </data>
  <data name="VersionNumberIncorrectInputStringFormat">
    <value>The supplied string ({0}) could not be converted to version number because it was not in correct format. Version number must consist of numbers no longer than 5 digits each separated with dots.</value>
  </data>
  <data name="XmlMessageParseCausedExceptionInConstructor">
    <value>Failed to create {0} VistaLink message. Source XML string for the {0} VistALinkMessage message was either malformed  or contained wrong values that were out of acceptable range. This caused the initial exception: {1}</value>
  </data>
  <data name="SecLogonSuccessRespMsgInvalidStatus">
    <value>Response status '{0}' is not a valid status for SecurityLogonSuccessResponseMessage. The only acceptable status is 'success'.</value>
  </data>
  <data name="VistALinkMessageXmlDocumentElementNotFound">
    <value>Document element ('{0}' was expected) was not found in source XML while deserializing VistALink message.</value>
  </data>
  <data name="ParameterCannotBeBlankOrSpacesOnly">
    <value>{0} cannot be blank or consist of spaces only.</value>
  </data>
  <data name="VersionNumberObjectToCompareIsOfWrongType">
    <value>Objects can not be compared: supplied object is not of {0} type.</value>
  </data>
  <data name="FaultExceptionFaultMessageReceived">
    <value>Fault message was received from the server: {0}\n{1}</value>
  </data>
  <data name="VistASecurityCodeDisallowedCharFoundInInputString">
    <value>Disallowed character '{0}' was found at position {1} in the input string. VistA security code can not contain any of the following characters: ';', '^', ':'.</value>
  </data>
  <data name="VistALinkSecurityVersionMismatch">
    <value>VistALink security handler version specified in source XML document for the VistALink message ({0}) is lower than the supported security handler version ({1}).</value>
  </data>
  <data name="SecurityLogonRequestUnableToParseAccessCodes">
    <value>Unable to parse VistA access and verify codes. Access and verify codes should be separated by a single semicolon, so splitting concatenated must return exactly 2 elements. {0} were returned for a given string.</value>
  </data>
  <data name="TimeoutInputStringIsNull">
    <value>Input string is null and null is not a valid timeout value.</value>
  </data>
  <data name="RpcParametersCollectionInconsistencyFound">
    <value>Inconsistent RPC parameters collection: parameter is missing at position {0}.</value>
  </data>
  <data name="InvalidNumberOfAttempts">
    <value>Number of attempts must be a positive integer number, but was {0}.</value>
  </data>
  <data name="DuplicateIndexKeyDuringRpcArrayParameterDeserialization">
    <value>Duplicate index key '{0}' was encountered while deserializing RpcArrayParameter from XML.</value>
  </data>
  <data name="TimeoutSuppliedValueIsInvalid">
    <value>The supplied timeout value is invalid. {0}</value>
  </data>
  <data name="ServerConnectionInfoBlankIpString">
    <value>IP address string supplied to {0} was blank. Please use valid IP address.</value>
  </data>
  <data name="RpcParameterNullValuesAreNotAllowed">
    <value>RPC parameter's (at position {0}) value is null, while RPC parameters with null values are not allowed in current configuration.</value>
  </data>
  <data name="FaultExceptionCorruptedFaultMessageReceived">
    <value>Corrupted fault message was received from the server: it didn't contain extended fault information.</value>
  </data>
  <data name="UnknownRpcParameterXmlFound">
    <value>Unknown RPC parameter XML was encountered while deserializing {0}. The problem XML was: {1}.</value>
  </data>
  <data name="VistASecurityCodeCannotBeConstructedFromNullObject">
    <value>Input string parameter was null. VistA security code can not be created from null object. </value>
  </data>
  <data name="UnableToFindXSDSchemaInResources">
    <value>Unable to find XSD file '{0}' in assembly resources. This file is required to perform VistALink XML messages validation.</value>
  </data>
  <data name="XmlParseRequiredElementNotFound">
    <value>Required XML element '{0}' was not found in source XML during message deserialization.</value>
  </data>
  <data name="SecSimpleResponseMessageWrongResponseStatus">
    <value>This response status ({0}) is not a valid status for {1} security message. 'success' and 'failure' are the only acceptable status values.</value>
  </data>
  <data name="FaultExceptionNoFaultInfoAvailable">
    <value>There is no server fault information available: unknown server error occured.</value>
  </data>
  <data name="RpcHandlerVersionMismatch">
    <value>RPC handler version specified in source XML document for the VistALink message ({0}) is lower than the supported RPC handler version ({1}).</value>
  </data>
  <data name="XmlParseRequiredAttributeMissing">
    <value>The node '{0}' in source XML document does not have a required attribute '{1}'.</value>
  </data>
  <data name="VistAMFormatterDisallowedCharEncountered">
    <value>String '{0}' contains prohibited character at position {1} and cannot be formatted as a part of    r a .</value>
  </data>
  <data name="TimeoutValueInInputStringIsTooLarge">
    <value>The supplied value is too large. Timeout value must be less than {0} milliseconds.</value>
  </data>
  <data name="UnableToLoadXSDSchema">
    <value>Unable to load XSD schema from assembly resources (required to perform VistALink XML messages validation) due to unexpected exception. Please review inner exception.</value>
  </data>
  <data name="VlMessageFormatIncorrectDocumentElement">
    <value>XML document element for the VistALink messages must be '{0}', but was '{1}'.</value>
  </data>
  <data name="VistAObfuscatorInvalidCharacterInStringToObfuscate">
    <value>Invalid character (ASCII code {0}) was encountered in input string. This character can not be translated with VistALink obfuscation algorithm. </value>
  </data>
  <data name="DivisionInfoCollectionDuplicateIEN">
    <value>Two divisions with the same IENs ({0}) may not be added to the same division info collection.</value>
  </data>
  <data name="VistALinkMessageXmlCannotBeXsdValidated">
    <value>Supplied XML string (that is expected to be VistALink message XML) does not conform to the specified XSD {0} and cannot be validated.</value>
  </data>
  <data name="SecGetUserDemoResponseMsg3ChildNodesAreRequired">
    <value>Xml element '{0}' must contain exactly 3 child nodes ({1} were found) in order to be parsed by {2} message's constructor.</value>
  </data>
  <data name="TimeoutInputValueIsNotPositiveInteger">
    <value>Input value is not a positive integer. Timeout must be a positive integer. value. It cannot be negative or zero.</value>
  </data>
  <data name="XmlParseCheckAttributeValueMismatch">
    <value>Attribute '{0}' of source XML node '{1}' has value '{2}' instead of expected '{3}'.</value>
  </data>
  <data name="InvalidResponseStatusFoundDuringDeserialization">
    <value>Response status '{0}' was encountered during {1} message serialization. This status is not valid for {1} or its children. The only acceptable status is '{2}'.</value>
  </data>
  <data name="StringEnumValueNotFound">
    <value>{0} with underlying string signature {1} was not found.</value>
  </data>
  <data name="TimeoutInputStringSecondsValueIsTooLarge">
    <value>Input string value in seconds is too large. It must be less than {0} seconds.</value>
  </data>
  <data name="FaultMessageFaultStringCannotBeEmpty">
    <value>Fault string in the fault message cannot be empty.</value>
  </data>
  <data name="ServerConnectionInfoCollectionNullHandle">
    <value>{0}'s handle cannot be null when an instance of {0} is added to collection.</value>
  </data>
  <data name="VistaALinkProtocolVersionMismatch">
    <value>VistALink protocol version specified in source XML document for the VistALink message ({0}) is lower than the supported protocol version ({1}).</value>
  </data>
  <data name="VistALinkMessageSourceXmlDocPreservesWhiteSpace">
    <value>XML document used as a source for the VistALink message constructor must not preserve whitespace.</value>
  </data>
</root>