Skip to main content
Kofax

SafeCom G4 520*10/*11 with SQL Server 2016: Replication setup through SafeCom does not work.

Problem:

On SafeCom G4 520*10/*11 with SQL Server 2016 "Setup replication" during "Add Server" and "repair replication" are giving an error message.

In the JobServer.trc file following error is seen:

Error: SMO Exception from scRMOLibManaged::scManagedReplication::GetSubscriptionStatus() : Cannot read property NetName.This property is not available on SQL Server 7.0.

Cause:

This error is seen if the SafeCom Server does not have the proper SQL SMO (Shared Management Objects) installed.

The SMO's are part of the SQL Management Studio.

Using a newer SQL Management Studio version (for example 17.x) will also result in this error.

Resolution:

When using SafeCom G4 520*10 with a full SQL Server 2016 (on same server as SafeCom or on external Server) it is required to install the correct SQL Management Studio version on the SafeCom Server for replication to be manageable by SafeCom.

When SafeCom and SQL are installed on the same server it is needed to install the SQL Management Studio 2016 version 16.5.3 (build version number 13.0.x.x) and SQL Management Studio 2014 version 14.x (build version number 12.0.x.x)

If SQL Management Studio 2017 version 17.x (build version number 14.0.x.x) has been installed in error, the following steps are needed to repair the installation.

- Remove all SQL 2017 installed packages.

- Run a repair installation for the SQL Server 2016 (Only required if installed on the same server as the SafeCom Server)

- Install SQL Management Studio 2016.

- Install SQL Management Studio 2014.

Important note: Should SQL Management Studio 2014 be installed before SQL Management Studio 2016, it would be required to run a repair on SQL Management Studio 2014 installation or remove SQL Management Studio 2016.

When SafeCom is connecting to an external SQL Server 2016 then you need to install SQL Server Management Studio 2014 on the SafeCom Server, please note SafeCom must be installed first then install SQL Server Management Studio 2014 last, it's wise to restart the whole server after SSMS has been installed rather than just restarting the SafeCom Server service.

Important note: Should SQL Management Studio 2014 be installed before SafeCom G4 Server, it would be required to run repair on SQL Management Studio 2014 installation, or remove and re-install SQL Management Studio 2014.