Skip to main content
Version: 4.1 (2026 H2)

primedocs server maintenance

This page contains information about the maintenance of the primedocs server applications and databases.

note

This page concerns the OnPremises option.
With the "Software as a Service" option, no server installations by the customer are necessary.

General​

primedocs is built on standard tools and technologies from Microsoft. Therefore, follow the instructions for operating the Internet Information Services and SQL servers.

Server migration​

In case of server migration, all steps of the Server installation should be executed on the new environment as well. After successful installation, the following artefacts of the existing installation must be transferred to the new server:

  • primedocs.config
  • cert.pfx (or the signing certificate, if in the certificate store — see Signing certificate)
  • Data protection keys (key-*.xml)
  • nlog.config (if adjusted)
note

Without the previous signing certificate and the data protection keys, existing tokens and sessions become invalid — all users have to sign in again.

Data protection keys cannot always be transferred by copying files

Copying the key-*.xml files only works if the data protection keys are stored unencrypted in the file system.

SQL database migration​

If the SQL database is migrated from one server to the other using SQL tooling, this should be done using a "full database backup" followed by a "restore" if possible.

Cause​

During synchronization between client and server, the "rowVersion" is used as a change feature. Only with a "backup" and "restore" the "rowVersion" remains the same.

If no "backup" and "restore" is possible and the migration can only be done via "SQL statements", all existing caches must be deleted or the id of the datasource in the primedocs.config must be changed. This means that the clients have to resynchronize completely.