A jakarta error occurred while reading a list of objects. Egais not working: pki partition blocked

The Jacarta PKI/GOST media is blocked by multiple attempts to enter the wrong pin code. In this case, the connection with the FSRAR server is lost, and invoice data is not sent to your accounting system. How to quickly unlock the key and restore work with EGAIS?

By default, the following passwords are set on all new media:

To unlock the computer, the Jacarta Unified Client program must be installed. If the setup and installation of EGAIS was carried out by our specialists, then you already have this program.

Run the program and wait until information about the Jacarta PKI/GOST media appears in the Unified Client window.

Unblock GOST

The GOST section contains a QEP certificate issued by a certification authority. be careful- you can not remove any components from this section. After deletion, you will have to re-apply to the certification authority to issue the key.

To unlock the GOST pin code, in the top menu “Application operations”, select the first item “Unlock user PIN code”. A notification will appear on the screen that unlocking will reset the counter of erroneous input attempts.

Click "OK" and in the newly opened window enter administrator pin code Jacarta GOST 1234567890. After resetting the error counter, enter the standard user pin code GOST 0987654321.

Important: this procedure will only help reset the counter, but not change forgotten password on new. If you changed the default GOST password and forgot it, you will have to initialize and write the key again in the certification authority.

Unblock PKI

The PKI container contains an RSA key, which is generated in personal account egais.ru website. In case of loss of the pin code, this section can be initialized (completely cleared), since you can rewrite the key yourself and for free, without contacting a certification authority.

Good afternoon!. The last two days I had an interesting task of finding a solution to such a situation, is there a physical or virtual server, it probably has the well-known CryptoPRO installed on it. Connected to the server , which is used to sign documents for VTB24 DBO. Locally on Windows 10 everything works, but on the server Windows platform Server 2016 and 2012 R2, Cryptopro does not see the JaCarta key. Let's figure out what the problem is and how to fix it.

Description of the environment

There is a virtual machine Vmware ESXi 6.5, as operating system installed Windows Server 2012 R2. The server is running CryptoPRO 4.0.9944, the latest version at the moment. From the network USB hub, using USB over ip technology, a JaCarta dongle is connected. Key in the system sees, but not in CryptoPRO.

Algorithm for solving problems with JaCarta

CryptoPRO very often causes various errors in Windows, a simple example (Windows installer service could not be accessed). This is how the situation looks when the CryptoPRO utility does not see the certificate in the container.

As you can see in the UTN Manager utility, the key is connected, it is seen in the system in smart cards in Microsoft Usbccid (WUDF) devices, but CryptoPRO, this container does not detect and you have no way to install a certificate. Locally, the token was connected, everything was the same. Began to think what to do.

Possible causes with container definition

1. First, this is a driver issue, for example in Windows Server 2012 R2, JaCarta should ideally be listed as JaCarta Usbccid Smartcard in the smart card list, not Microsoft Usbccid (WUDF)
2. Secondly, if the device is seen as Microsoft Usbccid (WUDF), then the driver version may be outdated, and because of which your utilities will not detect the protected USB drive.
3. Legacy version of CryptoPRO

How to solve the problem that the cryptopro does not see the USB key?

We created a new virtual machine and began to install the software all in sequence.

Before installing any software working with USB media containing certificates and private keys. Necessary NECESSARILY disable the token, if stuck locally, then disable it, if over the network, break the session

• First of all, we update your operating system with all available updates, as Microsoft fixes many errors and bugs, including drivers.
• The second point is, in the case of a physical server, install all the latest drivers on the motherboard and that's it. periphery equipment.
• Next, install the JaCarta Unified Client.
• Install the latest version of CryptoPRO

Installing a single JaCarta PKI client

Single Client JaCarta- this special utility from the Aladdin company, for proper work with JaCarta tokens. Download the latest version given software product, you can from the official site, or from my cloud, if suddenly it doesn’t work out from the manufacturer’s website.

Next, you unpack the resulting archive and run setup file, for my Windows architecture, I have it 64-bit. Let's start installing the Jacarta driver. A single Jacarta client, very easy to install (REMINDER your token at the time of installation, must be disabled). On the first window of the installation wizard, just click next.

Accept license agreement and click "Next"

In order for JaCarta token drivers to work correctly for you, it is enough to perform a standard installation.

If you choose "Custom installation", then be sure to check the boxes:

• Drivers
• Support modules
• Support module for CryptoPRO

After a couple of seconds, the Jacarta Unified Client is successfully installed.

Be sure to restart the server or computer so that the system sees the latest drivers.

After installing JaCarta PKI, you need to install CryptoPRO, for this go to the official website.

https://www.cryptopro.ru/downloads

At the moment the most latest version CryptoPro CSP 4.0.9944. Run the installer, check "Install root certificates" and click "Install (Recommended)"

CryptoPRO installation will be performed in background, after which you will see a suggestion to restart the browser, but I advise you to completely restart.

After reboot connect your JaCarta USB token. I have a network connection, from a DIGI device, via . In the Anywhere View client, my Jacarta USB drive is successfully defined, but as Microsoft Usbccid (WUDF), and ideally it should be defined as JaCarta Usbccid Smartcard, but you need to check anyway, since everything can work like that.

When opening the "Jacarta PKI Unified Client" utility, the connected token was not found, which means that something is wrong with the drivers.

Microsoft Usbccid (WUDF) is standard driver Microsoft, which is installed by default on various tokens, and it happens that everything works, but not always. operating room Windows system by default, puts them in mind for its architecture and settings, for me, personally, in this moment this is not necessary. What we do is we need to uninstall the Microsoft Usbccid (WUDF) drivers and install the drivers for the Jacarta media.

Open the dispatcher Windows devices, find Smart card readers, click Microsoft Usbccid (WUDF) and select Properties. Click the Drivers tab and click Uninstall

Agree to remove the Microsoft Usbccid (WUDF) driver.

You will be notified that for the changes to take effect, you need to restart the system, be sure to agree.

After rebooting the system, you can see the installation of the ARDS Jacarta device and drivers.

Open the device manager, you should see that your device is now defined as JaCarta Usbccid Smartcar and if you go to its properties, you will see that the jacarta smart card is now using driver version 6.1.7601 from ALADDIN RDZAO, as it should be .

If you open the Jacarta single client, you will see your electronic signature, this means that the smart card was detected normally.

We open CryptoPRO, and we see that the cryptopro does not see the certificate in the container, although all the drivers are defined as needed. There is one more feature.

1. In the RDP session, you will not see your token, only locally, this is how the token works, or I did not find how to fix it. You can try the suggestions to resolve the error "Unable to connect to the smart card management service".
2. You need to uncheck one checkbox in CryptoPRO

MUST uncheck "Do not use outdated cipher suites" and reboot.

After these manipulations, CryptoPRO saw my certificate and the jacarta smart card became working, you can sign documents.

You can also see your JaCarta device in Devices and Printers,

If you, like me, have the jacarta token installed in the virtual machine, then you will have to install the certificate via console virtual machine, and also give rights to it to the responsible person. If this is a physical server, then you will have to give rights to the control port, which also has a virtual console.

When you have installed all the drivers for Jacarta tokens, you may see the following error message when connecting via RDP and opening the Jacarta PKI Unified Client utility:

1. The smart card service is not running on the local machine. Microsoft's RDP session architecture does not provide for the use key carriers connected to the remote computer, so in the RDP session, the remote computer uses the local computer's smart card service. It follows from this that starting the smart card service inside an RDP session is not enough for normal operation.
2. Smart Card Management Service on local computer started, but not available to the program inside the RDP session due to Windows settings and/or RDP client.\

How to fix "Unable to connect to smart card management service" error.

• Start the smart card service on the local machine you are initiating the session with remote access. Customize it automatic start when starting the computer.
• Allow the use of local devices and resources during the remote session (in particular, smart cards). To do this, in the "Remote Desktop Connection" dialog, select the "Local Resources" tab in the settings, then in the "Local Devices and Resources" group, click the "Details..." button, and in the dialog that opens, select the "Smart cards" item and click "OK", then "Connect".

• Make sure the RDP connection settings are saved. By default, they are saved in the Default.rdp file in the My Documents directory. given file there was a line "redirectsmartcards: i: 1".
• Make sure on remote computer to which you are making an RDP connection is not activated group policy
  -[Computer Configuration\Administrative Templates\Windows Components\Remote Desktop Services\Remote Desktop Session Host\Device and Resource Redirection\Do not allow smart card reader redirection]. If it is enabled (Enabled), then disable it and restart the computer.
• If you have Windows 7 SP1 or Windows 2008 R2 SP1 installed and you are using RDC 8.1 to connect to computers running Windows control 8 and above, then you need to install the update for the operating system https://support.microsoft.com/en-us/kb/2913751

Here was the troubleshooting for setting up the Jacarta token, CryptoPRO on the terminal server, for signing documents in VTB24 RBS. If you have comments or corrections, then write them in the comments.

All functions from the implementation of the PKCS#11 standard return various error codes. All returned error codes are divided into two large groups:

All functions from the implementation of the PKCS#11 standard return special error codes (manufacturer-defined).

All functions from the implementation of the PKCS#11 standard extension return special error codes (manufacturer-defined).

Standard error codes

Due to the implementation of the rtPKCS11 and rtPKCS11ECP libraries, some standard functions may return a PKCS#11 standard error code that is not in the list of valid codes for this function. This situation is an exception. Standard error codes returned by each function in exceptional situations are listed in the description for each function separately.

Table 2.29 lists the PKCS#11 standard error codes and their descriptions supported by Rutoken devices. Detailed information on each error code can be found in the standard ( English language) or application (Russian language).

table2.29 . Standard Error Codes

Special error codes

Table 2.30 lists all PKCS #11 extended error codes along with their descriptions. Extended error codes can return both standard functions and extension functions.

Table 2.30. Standard Error CodesPKCS #11 supported by Rutoken devices

Description of the problem. To work with EGAIS, the JaCarta PKI / GOST / SE carrier is used. Often one of the partitions is blocked (the PKI partition). In this case, further work with EGAIS is impossible.

Reason for blocking– frequent access of the universal transport module to the JaCarta carrier. With ten unsuccessful authorization attempts, the media locks the partition and excludes further work.

There are two ways to solve the problem:

1. Contact the certification authority that issued the carrier.
2. Unlock the JaCarta media on your own according to the instructions.

Instruction by example Microsoft Windows 10.

Step-by-step instructions on how to unlock a PKI partition

Step 1: Switching to admin mode

From the Start menu, find the JaCarta Unified Client app and open it.

Rice. 1. Single client JaCarta

The workspace of the program will open.

Rice. 2. Switch to administration mode

The workspace of the program will open. If the PKI section is locked, the PKI tab will be red.

Rice. 3. Information about the token

Step 2: Checking the PKI lock on the partition

To understand that the PKI section is indeed blocked, click on the "Token Information" tab on the link " Full information…».

Opens " detailed information about the token. In the new window, find the "PKI Application Information" section. If the status in the "PIN-code" line is "Blocked", then close the window and proceed to the next paragraph of the instruction.

Rice. 4. Detailed information about the token

Step 3Unlock the PKI Partition

Go to the "PKI" tab. In the Application Actions panel, select the Unlock User PIN... option.

The "User PIN Unlock" window will open, in which you can specify:

1. The current administrator PIN is 00000000 by default;
2. The new user PIN is 11111111 by default;
3. Confirmation of the code (meaning the user's PIN code).

Rice. 6. User PIN Unlock

After specifying the PIN codes, click "Run".

If everything is entered correctly, a notification will appear. Click "OK" to complete.

Rice. 7. Notification of successful unlock

Go to the "Token Information" tab and click on the "Full Information" link to check the current status of the PKI application. The status should be "Installed".

Rice. 8. Status check

If the status has changed, the unlock is complete.