Sie sind auf Seite 1von 11

LS Data Director 3.02.

30
Release Notes

February 2017

© Copyright 2015, LS Retail ehf. All rights reserved. All trademarks belong to their respective holders
Contents

1 Installing Data Director .................................................................................................... 1


2 Improvements and Bug Fixes ......................................................................................... 2
2.1 Add Support for TCPS Certification .................................................................... 2
2.2 Scheduler service is not picking up network mode ........................................... 2
2.3 Filter does not work on linked table .................................................................... 2
2.4 SQL Command Timeout available in Config Tool .............................................. 2
2.5 Selecting all lines and cancel in Job Monitor ..................................................... 2
2.6 Table design fails if a dot is in the company name ............................................ 2
2.7 DD Setup does not pick NAV 2017 Add-ins path ............................................... 2
2.8 Return Routing path is wrong in pull job ............................................................ 2
2.9 Job to DD2 does not support Unicode text ........................................................ 2
3 Supported Systems .......................................................................................................... 3
3.1 Operating Systems ................................................................................................ 3
3.2 Databases Servers................................................................................................. 3
3.3 LS Retail Backend Systems ................................................................................. 3
4 FAQ and Known Issues ................................................................................................... 4
4.1 Empty path name is not legal ............................................................................... 4
4.2 NAV client or POS don’t see the data unless restarted ..................................... 4
4.3 Update DD when running Store Controller 2012 or older.................................. 4
4.4 CFront is not correct version, either too old or newer ...................................... 4
4.5 Cannot Query Data from Table: xxx >> Exception of type
'System.OutOfMemoryException' was thrown ................................................... 4
4.6 Moving Data Folder to different location............................................................. 4
4.7 NAV in languages other than English ................................................................. 5
4.8 Timeout expired when running job on SQL Server ............................................ 5
4.9 Replicate between NAV 2009 and 2013 ............................................................... 5
4.10 Replicate Unicode text from NAV 2013 to 2009 .................................................. 5
4.11 Test Connection doesn’t Work, I get Error 12305/12306 ................................... 5
4.12 Test Connection to DD2 location doesn’t Work ................................................. 5
4.13 NAV 2013 cannot create an instance of the following… ................................... 6
4.14 FOB Import with Service Tier or Multi Tenant .................................................... 6
4.15 Conversion overflows ........................................................................................... 6
4.16 DD looks for wrong version of AX DLL ............................................................... 6
5 What if I have Problems? ................................................................................................. 7
6 Release Track ................................................................................................................... 8
6.1 3.02.28 ..................................................................................................................... 8
6.2 3.02.26 ..................................................................................................................... 8
6.3 3.02.24 ..................................................................................................................... 8
6.4 3.02.22 ..................................................................................................................... 8
6.5 3.02.20 and earlier (see detail in earlier release notes) ..................................... 9

Katrinartun 2, 105 Reykjavík, Iceland


Tel: +354 414 5700 · Fax: +354 571 2728
Release Notes - LS Data Director 3.02.26

1 Installing Data Director


DD3 Runs on Framework 4.0 so you need to install it before you install DD3. Make sure to
install Full Framework 4.0, not only the Client Profile version.

Install DD3 by running LS.DataDirector.3.02.xx.Setup.exe.

If all options are deselected, only DD Client files are installed without the Client Tools. These
are the files needed for LS NAV or LS One to communicate with Data Director.

DD Service: DD Service that handles all the data transfer. If you are only installing client
controls for an LS Retail product such as LS NAV or LS One, to be able to connect to the DD
Service on another host, clear this option and only the Client files will be installed.

Client Tools: Configuration Tool and Monitoring Tools for Data Director. If you don’t want the
tools to be available on this host, then deselect this option. DD can be configured and
monitored remotely.

CFront Files: Files required making a connection to the NAV Database. If you are running an
upgrade and have manually updated the CFront files to match your NAV setup, then deselect
this so that the DD does not overwrite the current files.

DD2 Client for NAV: If you are installing controls for the LS NAV host and the CodeUnits, use
either CFront Controls or DD Controls from the previous version of DD (DD2), then select this
option. This installs all the DD2 Client files that are needed for NAV to communicate with DD.

DD Client files for NAV 201x RTC Add-ins: Add Client files to the Add-ins folder for latest
NAV RTC Client. If there are more than one version of NAV installed, only newest version will
get the files. You have to copy the files manually to the Add-ins folder for older versions.

DD Client files for NAV 201x SRV Add-ins: Add Client files to the Add-ins folder for latest
NAV Middle Tier Server.

The install for LS One Site Manager Scheduler plugin (Store Controller Plugin) have been
moved into the Site Manager installation and is part of the main Site Manager installation now.

NOTE: When upgrading from older Versions of DD3 it’s recommended after the
installation to open DD Configuration Tool, and press Get Config and then Send Config
to update the configuration data to match the latest version.

Chapter 1 - Installing Data Director 1


Release Notes - LS Data Director 3.02.26

2 Improvements and Bug Fixes


This version includes the following improvements and bug fixes.

2.1 Add Support for TCPS Certification


There are new entries in the DD config file only (not visible in Configuration Tool) that can be
used to configure TCPS Certification mode when using TCPS Mode.

<UseTCPCred>true</UseTCPCred>
<TCPSecMode>TransportWithMessageCredential</TCPSecMode>
<TCPMsgCredType>Certificate</TCPMsgCredType>
<TCPStoreLoc>LocalMachine</TCPStoreLoc>
<TCPStoreName>My</TCPStoreName>
<TCPFindType>FindByIssuerName</TCPFindType>
<TCPIssuer>Contoso Inc</TCPIssuer>
<DnsIdentity>contoso.com</DnsIdentity>

2.2 Scheduler service is not picking up network mode


If network mode was set to other than TCP in Site manager, DD Scheduler did not pick up the
new setting for DD Mode/Port for that location.

2.3 Filter does not work on linked table


Adding filter for Linked Table in Linked Table Setup caused error if more than one record
came from the linked table (Error: Select Command: SELECT xxx FROM xxxx WHERE xx =
@0 >> Must declare the scalar variable "@0"

2.4 SQL Command Timeout available in Config Tool


DD has a setting in the Config file called SQLTimeout and this was not visible in the
Configuration tool. What it does is adds Connection Timeout value to the SQL connection
string and also sets internal CommandTimeout value when deleting records. If a large
Normal jobs, with Update-Add-Delete, runs into timeout error it can be solved by set this
value.

2.5 Selecting all lines and cancel in Job Monitor


Using Ctrl-A to select all lines in Job Monitor would also select the last empty line in the list
and it caused Error: Object reference not set to an instance of an object.

2.6 Table design fails if a dot is in the company name


Reading Table and Field design in NAV failed if the Company name included a dot (.) or any
other special characters in the name.

2.7 DD Setup does not pick NAV 2017 Add-ins path


DD did not pick NAV 2017 Add-ins path if other older versions of NAV were also installed on
same host.

2.8 Return Routing path is wrong in pull job


If Pull job sent the job to Source location using routing path (F.ex.Job should go to DD3 using
routing path DD1;DD2;DD3) the routing path back to DD1 would come out wrong and job got
lost. This only affected Pull jobs, not Push jobs.

2.9 Job to DD2 does not support Unicode text


Sending jobs from NAV 2016 or later using DD3 to send to DD2 caused only the first character
of the text to be inserted in at the DD2 location. NAV 2016 and later have all text as Unicode
and the conversion from DD2 to DD3 did not support Unicode transfer. It worked the other way
around from DD2 to DD3.

Chapter 2 - Improvements and Bug Fixes 2


Release Notes - LS Data Director 3.02.26

3 Supported Systems
3.1 Operating Systems
The following operating systems are supported and tested:
- MS Windows Server 2012
- MS Windows Server 2014
- MS Windows 8.x
- MS Windows 10.x
Both IPv4 and IPv6 are supported for all operating systems.

The following operation systems are supported but not tested:


- MS Windows XP Professional x86 & x64
- MS Windows Vista, 7
- MS Windows Server 2000, 2003, 2008

3.2 Databases Servers


The following databases are fully supported and tested:
- MS Dynamics NAV 2016, 2017
- MS SQL Server/Express 2012, 2014
The following databases are supported but not tested:
- MS Dynamics NAV (4.01, 4.02, 4.03, 5.01, 6.00, 6.01)
Note FOB Replication (Import/Export) does not work with NAV version 4.xx.

- MS Dynamics NAV 2009, 2013 (R2), 2015


- MS Dynamics AX 2009/SP1, 2012, 2012 R2
- MS SQL Server/Express 2000, 2005, 2008
- MySQL Server
- Any Database that supports either ODBC or OleDB connection.

3.3 LS Retail Backend Systems


The following back-end systems are fully supported:
 LS NAV 9.x (2016), 10.x (2017)
 LS One 2014, 2015

The following back-end systems are supported, but not tested:


 LS Retail Store Controller 2.x (LS Retail Suite 20xx)
 LS One 2013
 LS Retail NAV 4.x, 5.x, 6.x, 7.x, 8.x
 LS Retail AX 2009

Chapter 3 - Supported Systems 3


Release Notes - LS Data Director 3.02.26

4 FAQ and Known Issues


4.1 Empty path name is not legal
When running job mixed with Action jobs, Normal jobs, with our without Replication counters,
the scheduler may pop up with this error, and not be able to run the job. This happens using
CU 99001474 in LS NAV 7.00.3 and earlier. To fix this change the CU 99001474.

Function: OnAfterReadReplCounters() : Boolean


DataClient.Disconnect;
Initialized := FALSE; //<-add this line
EXIT(TRUE);

4.2 NAV client or POS don’t see the data unless restarted
When DD sends data to NAV 2013, it inserts the data directly into the SQL Database, so in
some cases the NAV Client is still working on the old data set and does not see the updated
data unless it’s restarted.

This can be solved by add the command SELECTLATESTVERSION into the NAV Code to
instruct it to read new data to the buffer. This is not issue with NAV 2013 R2 or later.

4.3 Update DD when running Store Controller 2012 or older


There are no SC plugins any more that come with DD 3.2.8 install. To be able to run new DD,
you need to set up both versions in separate folder.

First uninstall the old DD, remove all leftover files from program files and ProgramData folder.
Install the old DD again that came with SC, and only select the SC Plugins, deselect everything
else. Install the new DD and place it in different folder than the default one. Now you have the
old plugins that work for SC 2012 and new DD running, and they should not conflict with each
other.

4.4 CFront is not correct version, either too old or newer


The files in the cfront folder are pulled from the NAV installation or Hotfixes that may have been
applied. To match the version of the current NAV Server, update the files in the cfront folder
with files from your installation. Most files can be found in the NAV Client folder and the cfront
dll files are located in Devkit folder on the NAV CD or in the latest Hotfix that may have been
applied.

4.5 Cannot Query Data from Table: xxx >> Exception of type
'System.OutOfMemoryException' was thrown
This may show up using Linked table job and the amount of data be replicated is extremely
large or the table include blob field with large data. The way DD works with linked table is it has
to load the main table data to memory to process the linked tables, and in this case the main
table data is too large for the computer memory.

You can fix this either by exclude the blob field or split up the job in separate sub jobs, and not
use linked table job. Linked table jobs are only useful for smaller jobs using replication counter.

4.6 Moving Data Folder to different location


Type in new path into Data Folder field. Restart DD. Upload DD license file again. DD will use
the new folder to store working, temp and log files in the new location. If you have unprocessed
jobs in the Work folder, move the files to the new location before starting up DD Service.

NOTE: The configuration file will still be located on default location, it’s not moved, so do not
delete the default folder and the configuration file, you can delete other folders within, like work,
log, cfront and archive from the default location.

Chapter 4 - FAQ and Known Issues 4


Release Notes - LS Data Director 3.02.26

4.7 NAV in languages other than English


If you are running NAV in a different language than English, you need to copy the fin.etx and
fin.stx files from the language folder where the NAV Client is installed to the correct CFront
folder for Data Director. This is necessary so that CFront can find values like Boolean, where it
is Yes in English but Sí in Spanish. The CFront files that come with Data Director Install are
from the English W1 install of NAV.

4.8 Timeout expired when running job on SQL Server


If database process it taking very long time on SQL server the error: Timeout expired. The
timeout period elapsed prior to completion of the operation or the server is not responding may
pop up. This is SQL Timeout and this can be adjusted in LS NAV 2013 by set the DD Timeout
value or add to the Connection String: Connect Timeout=xxx;

4.9 Replicate between NAV 2009 and 2013


Replicating data between NAV 2009 and older to and from NAV 2013 and newer does not
require any different setup than when doing replication between same versions of NAV. DD
knows how to handle the differences between the two versions. As long as the Table and Field
names are same between the versions, as in 99% time it is, no mapping is needed. Difference
in amount of fields between versions is not an issue. There is only known table name difference
between NAV 3.80 and later versions, and in that case only that table needs to be added to
Table Design setup and have special table name mapping, fields do not need mapping setup.

4.10 Replicate Unicode text from NAV 2013 to 2009


When replicating text other than English, like Chinese or Arabic text between NAV 2013 and
2009, the text has to be converted from Unicode (2013) text to Double byte (2009) text. If Code
page of the operating system is set to same as the Collation or Code page of the SQL Database,
this should work using |ms| mode in connection string and the text should show up correctly
both in SQL and NAV Client.

If the Collation is set to Latin and the Code page of the OS is other than 1252 you will run into
problems and get “????” instead of the text. The work around is to use the CFront mode |fin|
in the connection string for the NAV 2009 location, and then the text should appear correctly in
the NAV Client even if it does not show up correct in the SQL Database or in SQL Manager.

4.11 Test Connection doesn’t Work, I get Error 12305/12306


Open up the DD Config and go to the Debugging tab. Press the Open button next to the Debug
Level Value for the Database and DD Old (if you are using older TransAutomClient or DD2)
and click on Connect in all debug windows. You should see detailed error text describing what
is wrong there. If you don’t get any data in the debug window, it means that there is no incoming
connection. Check the Distribution Server name in a Location setup only includes the Host
Name where the DD is running, not HOST:16860:TCP. You only need to apply the port number
and mode when connecting to older DD2 or if DD3 is not running on default 16860 or 16750
port.

4.12 Test Connection to DD2 location doesn’t Work


Test Connection to DD2 location from NAV 2013 and later does not work, and also Reading
Database design as NAV 2013 does not include the old Codeunits needed to talk to DD2. You
get Error You have tried to create a channel to a service that does not support .Net Framing.
This error also comes up if a job is sending data to DD2 location and the location does not have
correct distribution host info <Host>:16750:DDOLD

Chapter 4 - FAQ and Known Issues 5


Release Notes - LS Data Director 3.02.26

4.13 NAV 2013 cannot create an instance of the following…


If you get this error: This message is for C/AL programmers: Cannot create an instance of the
following .NET Framework object:” when doing Test Connection or running a Job in NAV 2013
and later, you are missing the DD Client files in the NAV Add-ins folders. When installing DD
check the “Install DD Client files for NAV 2013 xx”. If you still get this error, then you can
manually copy the files to the Add-ins folders, both for the NAV Service and NAV Role-Tailor
Client. The files can be found in the DD bin installation folder and these are the files that need
to be copied:

LSRetail.DD.Common.dll
LSRetail.DD.Common.Data.dll
TransAutomClient.dll
DDConfigClient.dll

4.14 FOB Import with Service Tier or Multi Tenant


Importing FOB object to Dynamic NAV 2013 and later in multi- server tier/tenant environment
requires extra parameters in the connection string, to include which service tier you need to
connect to when compiling fob objects. The new parameters are:

;navsrv=xxx; navinst=xxx; navport=7045; navten=xxx;

Which will set these parameters for finsql

[navservername=<server name>,] [navserverinstance=<instance>,]


[navservermanagementport=<port>,] [tenant=<tenant ID>]

4.15 Conversion overflows


This error come because there is too big number in Int or Decimal field in this table or because
of wrong Field mapping types. If you look at the DD debug log for Database process, you may
also see what record DD stops on. Most common case is a barcode that has been scanned
into Qty field. Find the record, and fix the value to valid number. If the number is a decimal
number and needs to be this big, then you can change the setting in DD Configuration tool and
set the Decimal Fix value to BIG under App Config. BIG setting allows larger number but only
supports 4 decimal places.

4.16 DD looks for wrong version of AX DLL


DD is set to use version 6.3.0.0 of Business Connector DLL for AX (2012R3). If newer version
is in place this can be changed via dddatabase.exe.config file that is located under DD\bin
folder. Add this section to the file:

<runtime>
<assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
<dependentAssembly>
<assemblyIdentity name="Microsoft.Dynamics.BusinessConnectorNet"
publicKeyToken="31bf3856ad364e35" culture="neutral" />
<bindingRedirect oldVersion="6.3.0.0" newVersion="6.4.0.0" />
</dependentAssembly>
</assemblyBinding>
</runtime>

Chapter 4 - FAQ and Known Issues 6


Release Notes - LS Data Director 3.02.26

5 What if I have Problems?


If you run into any problems or find a bug or just have some idea of what we could do better,
please contact us at LS Retail via the Support feature on the LS Retail Partner Portal
(http://partners.lsretail.com). Under LS Data Director section on the Partner Portal site, you
can find FAQ sections that are updated with latest information on fixes or workaround that have
been reported. Also under Latest Version, there are few Quick Guides that shows how to set
up DD to handle different setups, and other useful information on how to operate DD.

If you are sending in a bug report, it is very helpful to us if you attach the debug and other files
that could help us to find out what could be wrong. These files are located under the Data
folder path (see Configuration tool for location).

 Log: Includes all Debug files from DD Processes


 Work: Includes Job and Data files that are waiting to be processed
 Keep: Data job files kept after job has been processed
 Archive: Includes Job files of processed jobs
 Temp: If you dump the Queue data from the Config Tool this is where you would find
that file.

It very helpful to include the Log files with the support that show the error or process before the
error happens. Log files are found in the Log folder. Activate the Debug Logging in DD
Configuration Tool under Debugging Tab by type in the Debug level values for the processes
or client control files.

If the problem is a Job that always gets a processing error from the Database, then include the
job files from the work folder. You will find 3-4 files for each job, and they are marked HOST-
PAKID-XXXX.xml. These files include the HEAD File, which has the information that used be
stored in the Incoming/Outgoing table, the IDAT file that has the Incoming Data, and RDAT that
has the Outgoing data. You also see a ZIP file there and that is the file that is going to be sent
over to the next host, or a zip file coming in from a remote host.

NOTE: Do not play with the files in the work folder, or lock them with other applications.
This will affect the working behavior of the DD. If you need to cancel a job or check for
job statuses, use the Job Monitor Application.

If you want DD to start with fresh startup, shutdown the DD system, and delete all files in the
work folder, reset the Queue status and clear out all jobs, and then start it up again.

Because the DD3 does not report error numbers in the same way as the DD2 did, you will not
always get an error number that tells you much. Error 12288 still comes if the DD is not
responding, but error 12306 is just a general error from the Database. To find out what is going
on, open up the Configuration Tool, go to the Debug tab, open up the Debug on the Database
application, and connect to it. You will see a more detailed error log there stating why the DD
cannot process the request. See the Manual for information on using the DD3
TransAutomClient that can display the real error message to the NAV Client.

Chapter 5 - What if I have Problems? 7


Release Notes - LS Data Director 3.02.26

6 Release Track

6.1 3.02.28
 Offline functionality
 Fix problem with Boolean field replication
 Fixed a bug in clean up logic
 Scheduler External Commands
6.2 3.02.26
 NAV 2015 Object Replication changes
 Keep Old Debug files for x days
 Fixed error when change Host path on ErrInsert Queue
 Specified cast is not valid
 Job stops if source and destination have different localhost name
6.3 3.02.24
 Added new Monitor jobs -SCHLOG
 Fixed Status on Sub Locations
 Delete Action error in LS One Scheduler
 NAV Multi-tenant Test Connection error
 LS One Scheduler fails on database connection error
 DD Job Monitor checks connection
 Added new NAV Database convert characters
 DNS Lookup in Configuration tools show Aliases
 Fixed Context ID usage with LS One data
 Nonexistence decimal field error
 Linked table are replicated if no header data is found
6.4 3.02.22
 Time field fixes
 Missing jobs due to bad network
 Extra characters in DateFormula field
 DD Schedule fixes
 FOB Import changes
 Check for double host entries in Host path
 Read Database design fixes
 DLL Files for Dynamics NAV Add-ins folder
 Field case sensitive and Codepage changes

Chapter 6 - Release Track 8


Release Notes - LS Data Director 3.02.26

6.5 3.02.20 and earlier (see detail in earlier release notes)


 Jobs get stuck on PreProcess
 Record Results from Manual Job transfer
 DDPullMon Program
 Text File and XML Import / Export
 Replication between different Collation databases
 License update to offline locations
 Date Errors on Thai Windows OS
 Offline to Manual
 Multi zip supported in Offline and Manual mode
 FOB Processing timeout
 Hide Connection string in Job Monitor
 Support for large Decimal values
 Reduce CPU load for DDRouter
 Replacement Chars for SQL to NAV in Config
 Field Convert using C# string.format
 Split Job Data Zip file into smaller files
 Check for zombie jobs
 Read View Design from SQL Database
 Retry Now for jobs on error
 Add table schema parameter for SQL connection string
 Speed Improvement on SQL Processing
 Status check updates & Check if Destinations are Valid
 Static and Dynamic IP Address processing
 DD Scheduler Service can Read from LS NAV
 The Table can’t be updated until the Transaction has been started
 GPMail.ocx added to DD2 Client files
 NAV 2013 Unicode support
 Monitor Collection & Service
 ODBC Support

Chapter 6 - Release Track 9

Das könnte Ihnen auch gefallen