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

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 through their structure. Problematic are e.g. E.g. many pages (>100), large images.

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

1. java.lang.OutOfMemoryError: Java heap space
   --> You can find more information on this in the FAQ – Make more memory available
2. e.g. B. java.net.SocketException: Software caused connection abort: socket write error
   --> 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/cxf/bus.properties 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.

When opening very large files, the Sign Live! CC The available memory is not sufficient (error message: ... "Java heap space"). The log provides information about the maximum memory Java requests from the operating system. Eg:

[2019.11.20-09:29:57.818][I][d.i.tools.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 enough memory is available, please gradually increase the memory claimed by Java.

So put in Sign Live! CC more memory available:

• Copy the fileINSTALLATION DIRECTORY> \ demo \ vmoptions \ more memory \* .vmoptions¹ after \bin.
• Starten Sie Sign Live! CC New.
• If the main memory is not 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 signivecc_service.exe file must also be created with identical content.

¹⁾ The name of the vmoptions file depends on the operating system used.

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 installed in the current version, the current version of Ghostscript can also be used.

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 drop 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 presented in English.

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

When trust centers switch to a new PKI 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.

When trust centers switch to a new PKI 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:

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! CC-TSL instance updating the TSL by using menu item Tools> Certificates> Update Trust Lists trigger the update of the trust lists manually.
   The updated trust lists (TSL) can usually be found 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 by 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. Run on the Sign Live! CC -Reboot validation instance.

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

When validating, the validity of certificates is usually first checked via OCSP query (online status query). This requires access to the Internet. Only if this query fails is a blocked list used for the check. However, blacklists are not made available by all trust centers.
Please check the following settings when installing Sign Live! CC:

• Tools > Settings > Signatures > Signature Validation > Certificate Validation:
  Is the "Perform online status check" option enabled?
• 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.

Depending on the characteristics of the license you are using, various actions may have restrictions. An 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@intarsys.de in connection.
• It is best if you let us know the license key you are currently using. You can find this under the menu item EXTRAS > LICENSE MANAGEMENT at the far right.

• Information about current versions (updates) is provided via newsletters. With the appropriate setting, an update check is carried out on the software side. The update is not installed automatically.
• Please note:
• If you use our software in connection with third-party software, please inquire advance at the manufacturer whether the update is to be carried out.
• The license is usually inherited within a master release. A new license is required when changing the master release. In any case, please note the release notes.
• If you obtained the software from one of our partners, you will normally be informed accordingly by this partner.
• Since January 01.01.2019st, XNUMX, our licenses have generally been so-called term licenses with a defined expiry date. Until this expiration date the update to the current version is free of charge. 

• Please check whether the manufacturer of your card reader provides drivers for MAC.
  The company's card reader drivers PURE SCT are here  available.
• You can find a list of the signature cards and card readers that we have tested in the Sign Live! CC data sheet.

A hotfix too Sign Live! CC is provided as a ZIP file. To install the hotfix, the zip file must be extracted and the file(s) it contains copied to a specific directory. This FAQ explains how to get the files into the application directory of Sign Live! CC be copied.

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

• If open, exit Sign Live! CC
• For example, save the zip file to the desktop
• Double click on the zip file. This is automatically unpacked and the unpacked 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 folder or into the folder specified in the hotfix
• Launch Sign Live! CC new

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

• In SignLive! CC under Extras -> Settings -> Basic settings set the 'Log level of detail' 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".
  (The log files are usually stored under /Users//Library/Application Support/SignLiveCC_/.)

Please note that the driver software of the REINER SCT card readers may have to be updated as a result of MAC OS X updates.

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

Solution:
Save file and attach later.

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

Occurs after updating MAC OS X after installing Sign Live! CC the error message "Sign Live CC.app can't be opened because Apple can't scan it for malware.", Sign Live! CC can be opened as follows:

Right-click, select Open, confirm dialog.

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

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 afterwards.

You can sign in ELSTER from various applications – for example ADDISON from the company “Wolters Kluwer”.

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

Please note:

• An RSA signature card – for example the D-TRUST – is required. Signature cards that use 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 cannot sign in ELSTER.

If you are doing the submissions in conjunction with Addison, you can go to the signature Sign Live! CC use. You can download the software from our shop at https://www.chipkartenleser-shop.de/intarsys/sign-live-cc relate.

Unfortunately, if you want to make the submissions directly to ELSTER using the Elster Authenticator, our solution is not suitable.
In this case, please contact ELSTER directly.