Logon for Citrix - Error=-3 during uncompression

[Peter]

What I installed:

Citrix MetaFrame Program Neighborhood V 9.00.32649 English
iKey Driver Version 3.4.7.118 English
Dekart Logon for Citrix ICA Client 2.02.10 English

Everything is working quite fine except when I connect a Rainbow iKey1000
I get the error=-3 during uncompression ICA Conection list occured.
After pressing OK the connection is started.

I am happy for any sugestions...

Cheers
Peter

[Alex Railean]

Peter, could you show a screenshot of the error message? [You can attach it to your post]

Also, let me know if the error is permanent (i.e. it occurs each time you initiate a connection) or not (it occurs in some cases only).

Have you tried the program with a different key? For instance, a USB flash disk? (this will help us determine if the error is Rainbow iKey1000 specific)

[PeterWeibel]

Hi Alex,

Yes the error is permanent, it occours every time you insert the token.
I just have two iKey1000 and it happend with both of them.

2

[Alex Railean]

The error means that some of the information read from the token is corrupt. This is strange, because after clicking OK, the authentication is successful.

- Is there any other data on the token, except the data written by Dekart Logon for Citrix?
- How many profiles are stored on the key?

The error should disappear if you erase all the data from the key and write your profiles 'from scratch' to it. But then, you say you have two keys... So obviously, the data was 'new' for one of the two keys; so the question is - how did you copy the key?

And, the final question, does the error occur with every profile you create, or only with a specific one?

[PeterWeibel]

No, there is no other data on the token.
Before I stored the data on the KSD, I used the key formatting utility to clear the token and then copied one application on it.

What kind of profile do you mean?

[Alex Railean]

By 'one application' you mean a Citrix connection (= profile)?

I need to know how you made a copy of the first key.

Here is a more efficient approach that will help us understand the problem.
Enable the program's logging mode by creating the following file: C:\DK_ICALogon.log (the file must be empty). Afterwards, follow these steps:
- Format the key with the Key Formatting Utility
- Run Dekart Logon for Citrix ICA Client
- Transfer your connection to the KSD
- Connect to the server using the connection stored on the KSD

The point is that the connection must be created from scratch, and not copied from the old key.


Once you follow these steps, the connection will either be successfully established, or the error will occur again. This time, all the actions will be logged, so send us the log-file; or post it here, but please use the [ code ] tag, so that formatting is preserved.

[PeterWeibel]

I followed your steps and here is the result:

3

[Alex Railean]

Thanks for the log, it did give us some extra details.

First of all, please download this updated version of the application: Dekart Logon for Citrix ICA Client (http://www.dekart.com/tools/ICALogon.ex_)

See whether the problem persists. If yes, we'll have to try and simulate this problem ourselves, and for that we will need the following file: ...\ICAClient\APPSRV.INI

Note that the file contains your password (though it is not in a plain text form). So it would be better if you changed the password to an incorrect one and tested the connection. If the problem persists, send us the above-mentioned file. To keep things private, do not attach this file to the forum, instead email it to support{AT#@$!@%}dekart{DOT$#^@}com.

We will not attempt to connect to the server, because the error is local, the reason we need this configuration file is that there is no other way for us to make sure that we run the simulation in the same circumstances as you do.

[PeterWeibel]

I tried it with the updated version, still the same error.
The email with attachement is on its way.

Cheers
Peter

[Alex Railean]

Peter, after a series of thorough tests (based on the file you emailed), we concluded that the problem shouldn't be connected with the program.

The profile you sent was successfully processed, so we are puzzled by the situation. However, there are several things that have to be analyzed before we can say that we're out of ideas.

In one of your screenshots [the one in which the program's interface is shown], we can see that there are two connections, one of them is the one you connect to - and the other one is a blank one. This is a weird situation, because a blank connection cannot be created [you'll be warned when you attempt that]. So it is a mistery how that connection ended up there.
Q1: If you remove that connection, does the problem remain?


Also, the key we tested your connection with was also a Rainbow iKey1000, the problem did not occur; hence it could be possible that there is a problem with the iKey driver.

To eliminate that possibility, please try the following:
Use a flash drive as a key, and try to store your profile on it. Attempt to connect to the server. If the problem is solved then it was either caused by the iKey drivers, or it had something to do with that misterious blank connection.

If the problem persists, then find the file called smartkey.dka located in the flash drive's root directory, and send it to us via email. This will help us eliminate another option (that data written to the key is already corrupt).

Note that if you do not have a USB flash drive at hand, you can use this trick - make your fixed drives be identified by Citrix Logon (http://www.dekart.com/support/faq/windows_user_authentication/#lexar-jumpdrive-secure) as well. (there is a REG file that has to be executed, afterwards the program will treat your hard drive partitions as if they were USB flash disks, and you'll find smartkey.dka in the root directory of the selected drive).

[PeterWeibel]

Alex,

After a few more unsuccessful tests I decided that I completely reinstall the workstation.
I have to admit that I probably wasted your time then now everything is working just fine…

Thank you for your help!

Peter

[Alex Railean]

Peter, no problem. I'm glad the issue was resolved.