Home Recent Sign up Sign in

Replicator for MS Dynamics NAV upgrade

2010-1-18

4.30.06

rep430.exe


Replicator for MS Dynamics NAV 4 30 06+Blurb

"REP430.exe" contains the same files as the Replicator 4.30 for MS Dynamics NAV end-user CD.
This is also the file to download if your customer has purchased an upgrade of Replicator for MS Dynamics NAV.

Click here to download: rep430.exe

 

Replicator for MS Dynamics NAV 4 30 06+Blog

The package includes the following files:
\
  - README.TXT    
  - ...           Other files are related to the
                  installation program.


\PROGRAM\
  - DB.ICO        Data Backbone Software A/S Icon file.
  - LICENSE.TXT   Replicator for MS Dynamics NAV license agreement.
  - REP.FOB       MS Dynamics NAV object file containing the Replicator
                  objects.
  - REP.OBJ       Navision 3.56 object file containing the
                  Replicator objects.
  - REPAG4.PDF  Replicator 4.22 for MS Dynamics NAV Administrator's
                  Guide. When you have installed Replicator, the
                  guide will be available within the help menu
                  (Start->Programs->Replicator for MS Dynamics NAV->Help).
  - REPCC4.PDF  Replicator 4.22 for MS Dynamics NAV Command Center Guide
                  4.22. When you have installed Replicator, the guide
                  will be available within the help menu
                  (Start->Programs->Replicator for MBS-Navision->Help).
  - REPCOM.EXE    Replicator Command Center executable file.
  - REPINI.EXE    The "Replicator INI Editor" executable file.
                  Specify here where Replicator should find
                  the Replicator setup information.
  - REPLICAT.DAT  The Replicator license file.
  - REPLICAT.INI  The Replicator initialization file. See also
                  the description of REPINI.EXE.
  - REPLICAT.UK   English language message file for Replicator.
  - REPLICATORFUNCTIONS 370.FOB
                  This MS Dynamics NAV object file contains a replacement
                  of Codeunit 64825 "Replicator Functions" with
                  additional functionality for use in MBS-Navision 3.70
                  or later.  
  - REPNT.CPL     The Replicator Service Manager.
  - REPNT.ISU     The uninstall file regarding Replicator for MBS-Navision.
  - REPNT.EXE     The Replicator executable file.
  - SCHED.CMD     A command file for starting the Replicator
                  Scheduler from the command line prompt.
  - TRACEON.CMD   A command file used in order to enable the "CTRACE"
                  environment variable. When enabled, information about
                  what Replicator has been doing while running is written
                  in the file "Trace.txt".
  - TRACEOFF.CMD  A command file that will disable the "CTRACE" environment
                  variable.
  - TRACE.TXT     Tracefile used by Trace system when active
  - CDB.PID       Files containing the System process id
  - CDB.CFG      CFG file used to enables different functionality.
  - CDB.MSG       Message file

 

Replicator for MS Dynamics NAV 4 30 06+upgrade notes

Changes from version 4.22 to version 4.30
-----------------------------------------
- New Feature: Build in a timeout that makes the Scheduler restart after 5 minutes without communication with The Replicator Server to prevent the service from freezing.
-----------------------------------------------------------------------------------
- Fixed: Issues causing scheduler to hang.
-----------------------------------------------------------------------------------
- Fixed: Unspecified Error in RunTransfer when running Seq read = Source + Dest when reading via Replicator Server
-----------------------------------------------------------------------------------
- Fixed: Bufferoverun error p Action Delete Spec writing/deleting via Replicator Server happened randomly
-----------------------------------------------------------------------------------
- Fixed: 10: CdbField::operator = S64 not handled for this type. Error when running with Update Dest. SC  from remote via Replicator Server to Central Server.
-----------------------------------------------------------------------------------
- Object Replication without limitation:
In C/Front for MS Dynamics NAV 5.0 SP1, Microsoft has introduced a new
functionality that handles import and export of Objects in the same way as
it is done in the MS Dynamics NAV Client. This means that if you are using
MS Dynamics NAV 5.0 SP1 or later, all updated or new created objects can
be transferred regardless of your MS Dynamics NAV licence.
-----------------------------------------------------------------------------------
- Improved Object Replication performance:
Before all objects were sent to the Replicator Server which compared and
updated the objects in the destination.
This has been changed.
Now each object is checked for any differences and only if the fields are
different, Replicator will send the new objects to the destination. This
results in less data being sent, which improves the performance of Object
replication.
If using Navision on SQL, the Object Replication can be used with the
“Changes only SQL” feature and hence only the changed/new objects are
transferred. This dramatically reduces the time used for Object
Replication.
-----------------------------------------------------------------------------------
- New feature/fixed error:
Log Changes: When running ChangeLog on tables with many changes you
would get a “Memory allocation error (in componentList grow)” when the
computer runs out of memory. Or “An Unspecified error was found during
replication!”
Now max 10000 changed records are cashed at a time which eliminates
these errors.
The cache size can be adjusted in the Replicat.ini file with the line:
Changes Log max cache: :
Default is 10000 records
When running as a Service through the Replicator Service Manager,
default 10000 records is the only opportunity.
----------------------------------------------------------------------------------
- New feature:
Passwords in registry or in ini file can now be encrypted (disabled by
default).
-----------------------------------------------------------------------------------
- New feature/fixed error:
The Scheduler fields Last Date/Last Time were previously updated also if
the schedule failed.
This has been changed so that the Last Date/Last Time fields are only
updated if the schedule was completed successfully.
This means that now the fields Last Date/Last Time indicates the last time
the schedule was run successfully
-----------------------------------------------------------------------------------
- New feature:
The Scheduler fields “Start time” and “End time” can now be used to
specify an interval passing midnight. If you specify e.g. Start time as 21:00
and End time as 03:00 the schedules will run between 9 p.m. and 3 a.m.
-----------------------------------------------------------------------------------
- New feature:
A timeout has been built in to the Scheduler which makes it restart after 5
minutes without communicating with the Replicator Server. This prevents
the service from freezing.
-----------------------------------------------------------------------------------
- Changed functionality:
“Compare” has been changed to use cfront Text database compare
function for Navision 4.0 or later.
-----------------------------------------------------------------------------------
- Changed functionality:
Error handling has been revised to improve Replicator stability to make
Error responses better.
-----------------------------------------------------------------------------------
- Fixed error:
When Errortype in Scheduler was set to “skip”, the time was sometime
moved forward twice. This has been fixed.
-----------------------------------------------------------------------------------
- Fixed error:
An error in Scheduler caused it to freeze/hang when running as a Service.
This has been fixed.
-----------------------------------------------------------------------------------
-Fixed error:
SourceCounter from SQL - SQLChangesOnly now uses correct filter to limit
on timestamp values > Integer value limit.
Before it used datatype Integer which caused it to return negative values
when the SQL timestamp exceeded integer range.
-----------------------------------------------------------------------------------
- Changed: Datatypes one some integer fields in the Configurtaion Tables.
Following fields have been changed from INteger to BigInteger.

64826 ToDo:           Field 2, Entry No.

64827 Activity Register :  Field 1 Entry No.
                   Field 8 Source Counter
64832 Action:            Field 1, Entry No.
                 Field 5, Source Counter

64838 Change Register:       
               Field 1, Entry No.

64840 Last SourceCounter Numbers:
                   Field 2, Last SourceCounter.
NOTE: Replicator v. 4.30 is still able to run on v. 4.22 Configuration Objects.
-------------------------------------------------------------------------------------------------------------------------------------
New feature:
It's now possible to select the highest Table No. Replicator should read design on. Default it reads Design on all Tables.
-------------------------------------------------------------------------------------------------------------------------------------
Fixed:
Replicator was not able to replicate tables with ID higher that 2000000040 when connection was made through Replicator Server. This has been fixed.
-------------------------------------------------------------------------------------------------------------------------------------
Fixed:
On random occasions Replicator logged the following in the Activity Register on Error:

Customers to Department Specification
8 records Read
8 records Found
8 records Updated
ERRROR: < Error Message>
ERRROR: < Error Message>
ERRROR: < Error Message>
ERRROR: < Error Message>

NOTE: On Error the transaction rolled back as it should, and no records were updated.

This has now been fixed so that it will only log the Error message resulting in these log entries:
Customers to Department Specification
ERRROR: < Error Message>
ERRROR: < Error Message>
ERRROR: < Error Message>
ERRROR: < Error Message>

This should avoid confusion about, if records were actually updated/added or not.

 

Add +discussion