Frequently Asked Questions - Sign Live! CC

The current information about the operating systems and the tested hardware (e.g. signature cards and card readers) can always be found in   current data sheet. In addition, thin client scenarios based on Windows Terminal Server or Citrix Presentation Server are supported.

Status: July 2014

Created: 29.07.2015 - 13: 35
Stand: 28.06.2021 - 11: 27

The application runs smoothly. Problems arise only when processing large files. The decisive factor is the size of a file while processing in the application. This is due to the size in bytes and by their structure. Problematic are z. B. many pages (> 100), large pictures.

The following typical error messages can be seen in the log:

  1. too little memory
    java.lang.OutOfMemoryError: Java heap space
    -> Further information can be found in the FAQ Make more memory available
  2. SOAP
    e.g. B. Software caused connection abort: socket write error
    –> solution see below


These problems can occur when using the SOAP protocol.
In this case, limiting settings must be increased.

To do this, create the file /classes/cfx/ e.g. B. with the following content:

org.apache.cxf.stax.maxTextLength = 512000000

and restart the application.

This increases the message size from approx. 100 MB (standard) to 512 MB.
Note that the message size is always larger than the actual file size (factor approx. 64) due to the base1,3 encoding.

Created: 15.01.2021 - 11: 27
Stand: 01.12.2022 - 08: 01

When opening very large files, the Sign Live! CC or PDF/ A Live!-Application not enough main memory available (error message: ... "Java heap space"). The log provides information about the maximum amount of memory Java requires of the operating system. For example:
[2019.11.20-09: 29: 57.818] [I] [ditools.logging] [executor singleton] [] maxmemory = 477626368

First, check that the operating system can actually provide that much memory for Java. Operating system and other applications also require memory!
If there is enough memory available, please gradually increase the memory complained about by Java.

So put in the Sign Live! CC or PDF/A LIve! application more memory available:

  • Copy the fileINSTALLATION DIRECTORY> \ demo \ vmoptions \ more memory \* .vmoptions1 toINSTALLATION DIRECTORY> \ bin.
  • Start the Sign Live! or PDF/A Live! application New.
  • If the working memory is not yet sufficient, the value in the vmoptions file can be edited with an editor and the value can be increased to -Xmx2048m, for example. The maximum value depends on how much RAM is available on your computer.

Important note:

  • For operation as a Windows service, the signlivecc_service.exe file must also be created with identical content.

1) The name of the vmoptions file depends on the operating system used.

Created: 08.06.2017 - 13: 47
Stand: 08.07.2022 - 13: 50

Setting up a PDF printer is required for various actions. This is done in Sign Live! CC "Ghostscript" used.

  • When installing Sign Live! CC version 7.1.7 - or older - please use Ghostscript 9.53.3 or older.
  • Do you have Sign Live! CC in der Version 7.1.8 - or later - installed, the current version of Ghostscript can be used.


Created: 24.08.2021 - 12: 03
Stand: 07.10.2021 - 15: 34

Sign Live! CC starts with the language settings of the operating system.

To get the operating language of Sign Live! CC you need administrator rights to manipulate them.
Follow these steps:

  1. Quit Sign Live! CC.
  2. Use Windows Explorer to switch to the installation directory for Sign Live! CC. In most cases this is “C: \ Program Files \ Sign Live CC " or "C: \ Program Files (x86) \ Sign Live CC ".
  3. Navigate further into the subdirectory "demo \ vmoptions \ language english".
  4. Copy the “SignLiveCC.exe.vmoptions” file from this directory.
  5. Change to the “bin” subdirectory of the installation directory Sign Live! CC and put the “SignLiveCC.exe.vmoptions” file there.
  6. Starten Sie Sign Live! CC new so that the language settings are loaded.

By doing this, the entire user interface of Sign Live! CC shown in English.

To reset to German, delete the "SignLiveCC.exe.vmoptions" file from the bin directory and start it Sign Live! CC New.

Status: February 2015

Created: 29.07.2015 - 13: 18
Stand: 28.06.2021 - 11: 26

The standard configuration for the SLCC application log is stored under
\ classes \ config \ logback.xml

The appender "FILE" is responsible for the SLCC application log.
So adjustments have to be made there.

To adjust the location / number / size of the log files to be created, change and or .
You can find information on this under .

To adjust the layout of the log file, change this according to your needs.
Information on the variables used in it can be found under
% p /% le /% level are e.g. B. for the level designation.

Created: 16.02.2021 - 16: 47
Stand: 16.02.2021 - 16: 48

From different applications - for example ADDISON of the company "Wolters Kluwer" - you can in MAGPIE sign.

For this you need PKCS# 11 drivers we in Sign Live! CC provide.
You can find them in Sign Live! CC via menu item Tools> Settings> Libraries> PKCS#11.

Please note:

  • It will be one RSA-Signature card - for example the D-TRUST - needed. Signature cards that ECC (Elliptic curve cryptography) are not supported by this library.
  • Sign Live! CC is required at least version 7.1.9.

Please configure the driver directly in the application to be used.
Please note that you are alone with Sign Live! CC in MAGPIE cannot sign.

Created: 06.12.2021 - 14: 00
Stand: 15.11.2022 - 15: 09

Update of the trust lists fails.

With Brexit that has UK closed his trusted list. As a result, updating trusted lists may fail.

For Sign Live! CC Versions older than version 7.1 6 do not have a hotfix. In this case, you have to migrate to the current version.

Created: 29.03.2021 - 14: 34
Stand: 07.10.2021 - 15: 50

If trust center to a new one PKI By changing the infrastructure, it can happen that signatures that were created with very new signature cards are not validly validated. This is due to the fact that the new Trusted Lists (TSL) and / or root CAs were not yet implemented at the time our software was released.
The Update of the trust lists in Sign Live! CC these signatures are validated again.

Via menu item Tools> Certificates> Update Trust Lists trigger the update of the trust lists manually.

Created: 07.10.2021 - 15: 36
Stand: 07.10.2021 - 15: 53

If trust center to a new one PKI By changing the infrastructure, it can happen that signatures that were created with very new signature cards are not validly validated. This is due to the fact that the new Trusted Lists (TSL) and / or root CAs were not yet implemented at the time our software was released.
The Update of the trust lists in Sign Live! CC these signatures are validated again.

  • Via menu item Tools> Certificates> Update Trust Lists trigger the update of the trust lists manually.

In server installations it makes sense to have the update triggered time-controlled. To do this, adapt the preconfigured service container:

  • Via menu item Tools> Services> Service Container Management  Configure the schedule of the "Trusted List Update Scheduler" service container and automatically trigger the update of the trust lists:

    The setting "Start automatically" is important:


Updated: September 2021
Created: March 2020



Created: 18.03.2020 - 13: 28
Stand: 07.10.2021 - 15: 54

In cases where the validating Sign Live! CC-Instance has / may not have an Internet connection and therefore cannot reach the TSL server, the following workaround is available:

  1. Install a Sign Live! CCTSL instance on a computer that is permitted to access TSL servers on the Internet.
    Version and patch level should match those of the Sign Live! CCValidation instance.
  2. Run on the Sign Live! CCTSL instance the Update of the TSL .
    You can find the updated TSL in the directory \ tsl - for example C: \ Users \ \ .SignLiveCC_7. \ tsl
  3. Replace on the Sign Live! CC-Validation instance the contents of the directory \ tsl through the TSLs on the Sign Live! CC-TSL instance.
    It is important that the replacement takes place completely! Everything else requires detailed know-how about the internal structure of the TSLs.
  4. On the Sign Live! CC validation instance by restarting.

This workaround uses internal Sign Live! CC- Processes that you cannot influence.

Created: 21.09.2021 - 12: 05
Stand: 07.10.2021 - 16: 02

The blacklist status and online status are unknown in the validation result of a signature.

When validating, the validity of certificates is usually first checked via OCSP query (online status query). Access to the internet is necessary for this. A blacklist is only used for checking if this query fails. However, blacklists are not made available by all trust centers.
Please check the following settings when installing Sign Live! CC:

  • Extras> Settings> Signatures> Signature validation> Certificate validation: Is the "Perform online status check" option activated?
  • If you use a proxy to access the Internet, the access data must be configured under Extras> Settings> Internet connection.

If both settings are correct, please send a test document with the signature that showed the error during validation to for further error analysis Email to support. If this is not possible, carry out the incorrect validation again and send us the current log file.

Created: 10.05.2021 - 10: 29
Stand: 07.10.2021 - 15: 30

When reinstalling Sign Live! CC or when changing computers, it can be helpful to adopt settings from an existing installation.
The settings of Sign Live! CC are stored in the profile directory of the application.

  • (Windows client: C: \ Users \ .SignLiveCC_ . )
  • (Windows server: C: \ ProgramData.SignLiveCC_ . )

The following subdirectories can be adopted:
"Preferences" (includes settings made via "Extras> Preferences")
"Instruments" (includes configurations of service containers, signature pools, time stamps, configurations for signIT gears, etc.)
"Licenses" (may contain the license)
"Db" (should be used if you have your own certificates in the Sign Live! CC imported)

A quick guide to migration is available as a  Tutorial ready for download.

Created: 26.08.2021 - 15: 06
Stand: 07.10.2021 - 16: 11

Variables are used when Sign Live! CC with the help of the file “bin \ SignLiveCC.exe.vmoptions”. These are defined via the option "-Dproperty = value" and a value is set. Environment variables can also be specified as a value.


-Dmy.test = test -Dmy.profile = $ {USERPROFILE}

These variables can be used, for example, when configuring Sign Live! CC can be used via $ {} or $ {}.

WFurther information on using the VMoptions file can be found in the  Users Guide from exe4jused to create the Sign Live! CC Launchers for Windows is used.


Created: 15.08.2017/XNUMX/XNUMX

Created: 15.08.2017 - 14: 42
Stand: 07.10.2021 - 16: 21

Should several Windows services from Sign Live! CC are operated in parallel, a name must be specified when installing the service. To do this, adjust the “bin / SignLiveCC_service_install.bat” file by entering a name after the “/ install” option.


……. / Install MySLCCService

The same name must be specified in the bat files for starting, stopping and uninstalling the Windows service.

Parameters for use in Sign Live! CC Windows services are transferred using the "bin / SignLiveCC_service.exe.vmoptions" file.

You will receive further information  here .


Created: 15.08.2017/XNUMX/XNUMX

Created: 15.08.2017 - 14: 56
Stand: 19.11.2021 - 08: 09

Depending on the version of the license you are using, various actions may have restrictions. One example is the number of possible signatures per day. Once the limit is reached, the application continues to work very slowly.

  • If the license used is not sufficient for you, please contact us at the e-mail address about a license upgrade support in connection.
  • The best thing to do is to inform us of your currently used license key. You can find this under menu item EXTRAS > LICENSE MANAGEMENT far back right.

Status: July 2015

Created: 29.07.2015 - 13: 30
Stand: 16.02.2021 - 17: 07

Unt it makes sense in place of with Sign Live! CC to use your own JVM.
For example, if you access the Sign Live! CC Want to access MBeans or the application remotely debug want.


Follow these steps:

  1. Name the directory with Sign Live! CC delivered JVM around.
    Windows: C: \ Programs \ SignLiveCC_7.1 \ jre -> C: \ Programs \ SignLiveCC_7.1 \ jre_off
    Linux: /opt/intarsys/signlivecc-7.1.7/bin/jre -> /opt/intarsys/signlivecc-7.1.7/bin/jre_off
  2. Windows:
    Define via the Windows system settings in the system variables EXE4J_JAVA_HOME the root directory of the JVM (without a final "").

    If this does not lead to success, define additionally EXE4J_LOGyes to get information about the behavior of EXE4J to obtain:
    During operation, a message box provides information about where the log is stored.
    Put $CABARET_JAVA_HOME to the root directory of the desired JVM
    (see also information in /opt/intarsys\signlivecc-7.1.7/bin/
  3. Starten Sie Sign Live! CC New. In the log file you should now see the defined JVM .

Important NOTE

With Sign Live! CC delivered JRE uses the keystore.type = jks.
Installed separately JRE/JDK must be adjusted accordingly.
To do this, set -> keystore.type = jks in your Java installation.

Created: 25.06.2021 - 16: 22
Stand: 07.10.2021 - 16: 32

If you want to add your own keywords to the supplied e-mail text when using CoSIMA (e.g. invoice number, e-mail sender, etc.), you must first define the variables in the source document in your Office application. The procedure is described in a tutorial that here can be downloaded.

Status: October 2014

Created: 06.08.2015 - 11: 29
Stand: 08.02.2021 - 21: 36

Sign Live! CC 7.1.8 was already available for download as a Mac OS 12 Monterey was published. This is why Sign Live! CC version 7.1.8  for Mac OS 12 Monterey not Approved.
If you are using MacOS Monterey, please update to the current version Sign Live! CC 7.1.9.x (or higher).

If you are using Monterey and not updating to Sign Live! 7.1.9 can be done, then you can use the utility Monterey SignLive use that you here can download. Please note that the application SIgn Live! in your program folder must be as follows:

Sign Live CC

Should this read differently (e.g. Sign Live! CC 7.1), then you must absolutely rename the program to the given name before starting the utility program.
Users who are familiar with the command line and the terminal can also enter the following shell commands in a zsh in the terminal in order to Sign Live! CC to start on Monterey:

% export DYLD_FALLBACK_LIBRARY_PATH = / Applications / Sign \ Live \ / Applications / Sign \ Live \ / Applications / Sign \ Live \ \ Live \ CC \ Launcher

Please note that every new call of Sign Live! CC must be done from the terminal.

Depending on the installation name of Sign Live on your Mac in the directory Programme (Applications) the command lines may have to be adapted. However, we recommend the utility program until it is released for Monterey Monterey SignLive to use.

Created: 29.10.2021 - 08: 38
Stand: 03.06.2022 - 08: 49

Please note that through MAC OS - Updates the driver software for the company's card readers PURE SCT may need to be updated.



Created: 25.11.2019 - 09: 27
Stand: 29.10.2021 - 09: 04

SignLive! CC creates log files. These help us to analyze errors and to help you quickly.

  • Please post in SignLive! CC under Extras -> Settings -> Basic Settings set the 'Log Detail Level' to 'All Details'.
  • Then please reproduce the error again.
    Then go to Window -> Show log file.
    A dialog with the log files appears.
  • Note the dialog heading. The path to the log files is displayed there.
  • Go with the Finder -> Go to -> Go to folder ... to the displayed folder and please send us all files with the ending ".log".
    (Usually the log files are under / Users / / Library / Application Support / SignLiveCC_ / filed.)

Updated: September 2020
Created: November 2013

Created: 06.08.2015 - 14: 53
Stand: 08.02.2021 - 21: 32

A hotfix too Sign Live! CC is called ZIP-File provided. To apply the hotfix, the zip file must be extracted and the file (s) contained in it must be copied to a specific directory. In this FAQ explains how the files in the application directory of Sign Live! CC copied.

Please note the information in the hotfix to which directory the files should be copied.

  • If open, exit Sign Live! CC
  • For example, save the zip file on your desktop
  • Double click on the zip file. This is automatically extracted and the extracted folders and files are made available
  • Navigate to using the Finder Programme, Mark your choiche Sign Live! CC, Open the context menu and choose Show package contents. The “Contents” folder is displayed
  • Open the folders Contents / Resources
  • Copy the unzipped folders and files - which were made available in the previous step - into this or into the folder specified in the hotfix
  • Start Sign Live! CC new


Status: October 2020

Created: 23.10.2020 - 16: 04
Stand: 29.10.2021 - 09: 05

Takes place after the update of MAC OS X after installing Sign Live! CC the error message “Sign Live cannot be opened because Apple cannot search for malware in it. ”, Sign Live! CC opened as follows:

Right click, select Open, confirm dialog.


Updated: 10/2020
Recorded: 11/2019



Created: 20.11.2019 - 14: 32
Stand: 29.10.2021 - 09: 07

After updating to macOS High Sierra, Sign Live! CC the menus are no longer displayed correctly?
This is due to the fact that the key in the “Info.plist” setting file is YES stands, but is required "DO NOT".

In the settings file / Applications / Sign Live CC must be the key SFBCand all AllowMixedLocalizations on DO NOT be set.

Then it looks like this:

SFBCand all AllowMixedLocalizations
     DO NOT

Quick fix:

Run the following command in a terminal shell:
plutil -replace SFBCandallAllowMixedLocalizations -string DO NOT "/ Applications / Sign Live CC "

where the last argument is the path to the Info.plist file Your Mac system is.


Status: October 2017


Created: 04.10.2017 - 15: 12
Stand: 08.02.2021 - 21: 33

From Mac OS X 10.11 (El Capitan) the integration of TOKENEND not because Mac OS X no longer allows the installation.

Status: October 2015

Created: 21.10.2015 - 16: 21
Stand: 29.10.2021 - 09: 03

If you are from Sign Live! CC Click on the "Send current document" button, and on Mac OS X the file attachment is not created.
This is because the transfer of file attachments when using the mailto protocol of Mac OS X is not supported.

Save the file and attach it later.

Created: 07.08.2015 - 09: 15
Stand: 15.10.2021 - 09: 18
  • Please check before updating Sign Live! CC whether you need a new product key.
    In Sign Live! CC you can check the version of the version you are using via the menu item Extras> License Management.
    If you have a maintenance contract with us, updates are free. Updates are chargeable without a maintenance contract.
  • Please check whether the manufacturer of your card reader has drivers for MAC Is available.
    The company's card reader drivers PURE SCT are  here available.
  •  A list of the signature cards and card readers tested by us can be found in   Sign Live! CC data sheet.

Status: October 2017

Created: 06.08.2015 - 14: 29
Stand: 29.10.2021 - 09: 08

The card reader may be connected after the system has started, but not removed while the computer is in operation.

Status: January 2014

Created: 06.08.2015 - 11: 59
Stand: 08.02.2021 - 21: 33

Since Sign Live! CC version 5.1  CoSiMA can be used to trigger a complex conversion and signature workflow from any application by simply printing. A corresponding service must be set up for this.
This also works on Mac OS X.

You will find a detailed tutorial with information on installation and configuration here .

Status: January 2014

Created: 06.08.2015 - 11: 49
Stand: 29.10.2021 - 09: 09

The library, which is necessary for displaying a document, is no longer included in the standard deb packages for Ubuntu 12.x. The package libfreetype6-dev must be installed later.

Status: October 2015

Created: 30.07.2015 - 09: 38
Stand: 08.02.2021 - 21: 30

The libpcsclite library, which is required for communication with a card reader, is no longer included in the standard deb packages for Ubuntu 12.x. The package libpcsclite-dev must be installed later.

Status: October 2014


Created: 30.07.2015 - 09: 35
Stand: 08.02.2021 - 21: 30

The message in the receipt "Cannot parse signature of document 0 (" null "): java.text.ParseException: DigestMethod missing in SigningCertificate (V2): 2005" is only a receipt with the status INFO from the recipient's eANV system and therefore has no influence on the signature or the dispatch of the documents.
That means that with SignLive! CC The signature created is error-free.

Created: 04.06.2021 - 09: 35
Stand: 29.06.2021 - 13: 24

If you do the submissions in conjunction with Addison, you can go to the signature Sign Live! CC use.

Unfortunately, if you want to do this directly at ELSTER using the Elster Authenticator, you cannot use our solution.
In this case, please contact ELSTER directly.

Created: 16.02.2022 - 09: 04
Stand: 16.02.2022 - 09: 04

FAQ search