Beruflich Dokumente
Kultur Dokumente
30
Release Notes
February 2017
© Copyright 2015, LS Retail ehf. All rights reserved. All trademarks belong to their respective holders
Contents
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.
<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>
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.
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.
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.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.
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.
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.
LSRetail.DD.Common.dll
LSRetail.DD.Common.Data.dll
TransAutomClient.dll
DDConfigClient.dll
<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>
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).
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.
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