000038703 - Globalization issues when Windows Server settings are configured to Non US In RSA Archer

Document created by RSA Customer Support Employee on Apr 27, 2020
Version 1Show Document
  • View in full screen mode

Article Content

Article Number000038703
Applies ToPRODUCT VERSION: RSA Archer 6.x
IssueWhen using RSA Archer with Windows Server configuration that is not configured to US standards there are some issues that occur with Archer functionality. 

Currently, the following are known issues:
  1. Required field pop up is displayed incorrectly with Windows Configuration set for Non US (German) and Archer user profile configured with USA Locale and manually selected German Language.
    User-added image


     

  2. Date field value does not get saved when the record is saved Windows Configuration set for Non-US (German) and Archer user profile configured with USA Locale and manually selected German Language.
    Data loss also occurs if there is a date value already populated before save.
     
    Before Save (Value is present):
     


    User-added image



    After Save (Value is removed):
     


    User-added image


     


     

  3. USA Locale is not respected when Windows set for Non-US (German) Configuration and Archer user profile configured with USA Locale and manually selected German Language.
    User-added image
     


     


    Items 1-3 above occurred with the following Windows configuration:
     


    User-added image


    And the following User Profile configuration in Archer:
     


    User-added image


     

  4. Data imports fail to complete despite using the same import file and data import configuration within Archer, with the only difference being the server locale being Non-US.
    Error:




    User-added image

    Log:


     



    <E2ETraceEvent xmlns="http://schemas.microsoft.com/2004/06/E2ETraceEvent">
        <System xmlns="http://schemas.microsoft.com/2004/06/windows/eventlog/system">
            <EventID>3</EventID>
            <Type>3</Type>
            <SubType Name="Error">0</SubType>
            <Level>2</Level>
            <TimeCreated SystemTime="2020-02-20T11:11:01.4232076Z" />
            <Source Name="ArcherTech.DataFeed" />
            <Correlation ActivityID="{51d6f216-f0e1-44f7-9c46-65dfe537e71f}" />
            <Execution ProcessName="ArcherTech.JobFramework.Job" ProcessID="6744" ThreadID="1" />
            <AssemblyVersion>6.4.0.1135</AssemblyVersion>
            <Channel />
            <Computer>V16KROSCI</Computer>
        </System>
        <ApplicationData>
            <TraceData>
                <DataItem>
                    <TraceRecord Severity="Error" xmlns="http://schemas.microsoft.com/2004/10/E2ETraceEvent/TraceRecord">
                        <TraceIdentifier>ArcherTech.DataFeed</TraceIdentifier>
                        <Description>The source file is not a valid XML file.</Description>
                        <AppDomain>ArcherTech.JobFramework.Job.exe</AppDomain>
                        <ContextData>
                            <LogReferenceId>022020-111101-3919</LogReferenceId>
                            <DataFeedId>1363</DataFeedId>
                            <DataFeedName>Data_Import_Feed_20022020_1110</DataFeedName>
                            <DataFeedHistoryId>18561</DataFeedHistoryId>
                        </ContextData>
                        <Exception>
                            <ExceptionType>System.Xml.XmlException, System.Xml, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089</ExceptionType>
                            <Message>Content cannot be converted to the type System.Decimal. Line 1, position 440.</Message>
                            <Source>System.Xml</Source>
                            <StackTrace>   at System.Xml.XmlReader.ReadContentAs(Type returnType, IXmlNamespaceResolver namespaceResolver)
       at ArcherTech.ChannelFramework.Xml.XmlEntityMetadata.&lt;&gt;c__DisplayClass33_0.&lt;BuildEntityListAction&gt;b__1(XmlReader r)
       at ArcherTech.ChannelFramework.Readers.XmlReaderExtensions.ProcessChildElements(XmlReader reader, Boolean throwOnUnexpected, NamedAction[] actions)
       at ArcherTech.ChannelFramework.Xml.XmlEntityMetadata.&lt;&gt;c__DisplayClass36_0.&lt;BuildStandardParseDataDelegate&gt;b__1(XmlReader reader)
       at ArcherTech.ChannelFramework.Readers.XmlReaderExtensions.&lt;ConvertChildElements&gt;d__3`1.MoveNext()
       at System.Linq.Enumerable.&lt;SelectManyIterator&gt;d__17`2.MoveNext()
       at ArcherTech.ChannelFramework.ITimedEnumerableBase`1.IEnumeratorBase`1.MoveNext()
       at ArcherTech.DataFeed.Channel.Components.ContentWriterEnumerable.&lt;GetEnumerable&gt;d__7.MoveNext()
       at ArcherTech.DataFeed.Channel.Components.ContentWriterComponent.Execute()</StackTrace>
                            <InnerException>
                                <ExceptionType>System.FormatException, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089</ExceptionType>
                                <Message>Input string was not in a correct format.</Message>
                                <Source>mscorlib</Source>
                                <StackTrace>   at System.Number.StringToNumber(String str, NumberStyles options, NumberBuffer&amp; number, NumberFormatInfo info, Boolean parseDecimal)
       at System.Number.ParseDecimal(String value, NumberStyles options, NumberFormatInfo numfmt)
       at System.Xml.Schema.XmlUntypedConverter.ChangeType(String value, Type destinationType, IXmlNamespaceResolver nsResolver)
       at System.Xml.XmlReader.ReadContentAs(Type returnType, IXmlNamespaceResolver namespaceResolver)</StackTrace>
                            </InnerException>
                        </Exception>
                    </TraceRecord>
                </DataItem>
            </TraceData>
        </ApplicationData>
    </E2ETraceEvent>


     

CauseThe cause of these issues is currently being determined by engineering as part of ARCHER-85154.
ResolutionThe resolution is currently being determined by engineering. At the time of writing the last version of Archer is 6.7 P5 and these issues still exist.
WorkaroundAs a workaround, you can change the server configuration to be English (United States). It is very important to understand which section applies to your environment. If you are using LocalSystem to run your Archer Services then the Welcome Screen section applies. If you use a Domain Account you can log into the server and validate the Current User section. If this is not possible you can update via Group Policy.

User-added image

Attachments

    Outcomes