Microsoft Dynamics AX Support

This blog contains posts by the Microsoft Dynamics AX Support Teams Worldwide

Slow POS when no internet connectivity

 

Description:

When starting the POS it takes several minutes to launch. We traced this behavior with Netmon and saw that POS called unsuccessful VeriSign and Akamai. This caused a delay
in the POS startup.

 

 

 

 

Cause:

It is standard security behavior for Authenticode signed .NET applications to try and verify the certificate
authority. In the case of non-Internet connected machines this could cause this
behavior as it will time out trying to connect to the server.

 

 

Solutions:

1. First solution is to disable the publishers certificate revocation, but this solution disables it for the whole computer.

Internet Explorer
> Tools > Advanced > Check for publishers certificate revocation.

 

2. Second solution is to modify the Pos.Exe.Config file found in the POS directory,by adding the following XML string marked in black

<?xml version=”1.0″ encoding=”utf-8″?>
<configuration>
    <configSections>
        <section name=”AxRetailPOS” type=”LSRetailPosis.Settings.ConfigFile.AppConfiguration, SystemSettings, Version=6.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35″ />
    </configSections>
    <AxRetailPOS OfflineDatabaseConnectionString=””
        StoreDatabaseConnectionString=”Data Source=127.0.0.1;Initial Catalog=AXRetailSeattle1;Persist Security Info=true;Integrated Security=SSPI;Pooling=false;TrustServerCertificate=true;Encrypt=TRUE;”
        StoreId=”AW-SEATTLE” TerminalId=”SEATTLE-1″ DATAAREAID=”CERW” />
  <runtime>
    <generatePublisherEvidence enabled=”false”/>
</runtime>
</configuration>

 

 

Note:

The generatePublisherEvidence was introduced in .Net framwork 2.0. POS is compiled in :net framework 3.5 and therefore the key works there as well.

http://support.microsoft.com/kb/936707/en-us?fr=1

 

 

 

 

Author: Kim Truelsen

Date: 18/7-2012