Citrix does not connect 1

[SHardy]

Hi,

We have an external client for whom we provide reporting via an Acces DB. This is setup as a Citrix app, which is then accessed through our secure web site using the Citrix ICA Client (version 7).

This client has been accessing these reports without problems for sometime now. However, now when they try to launch the database they get the Citrix "Connecting to..." dialog for a few seconds, then it disappears and the Citrix icon disappears from the system tray.

I know that having a large amount of temporary internet files sometimes causes strange problems, so I got them to delete these, but no change.

I would be grateful for any suggestions as to what may cause this.

I am of the opinion that this is probably an issue at their end, rather than with us (they are able to log on to our network with no problems).

Thanks,
Simon

 

[ascotta]

I think you will find that they don't have a TS-CAL. WHat operating system are they and you running ?

[blue]Arguably the best cat skinner around ! [/blue]

Cheers
Scott

 

[SHardy]

What is a TS-CAL?

Our DB and Citrix app is on a Windows2000Server.

If I remember correctly, I think they were running Windows NT on their machines. Definitely some Windows variant anyway.

 

[ascotta]

Sorry, I will expand.

In order to use Citrix, you must have citrix licenses. These are concurrent. i.e next user gets on if there is one available. Whne user is finished with it it goes back in the pot so to speak.

You also must have Terminal Services Client Access Licesnes(TS-CAL'S).

These are not concurrent. They are issued to the workstation the user is at(in Win2K). If the workstation does not have one and cannot get one, or their temporary one has timed out(90 days) You will get the message you have described.

You need a Win2K Terminal Services licensing server in your domain. If it is an NT4 domain then an Win2K server will suffice. If you are AD then it has to go on a DC.

This has to be activated, and then you add your TS-CALS)licenses in to it.

If there are no licenses left available a temporary license is issued but will run out after 90 days.

If the clients are XP or Win2K wkstn then they are deemed to have a built in TS-CAL and a license is not required. All other O/s must have a TS-CAL.



[blue]Arguably the best cat skinner around ! [/blue]

Cheers
Scott

 

[SHardy]

OK. Our network is NT & Netware. A majority of our workstations are NT4. We use Citrix quite a lot for running "delivered" applications.

From what you have described, I'd guess that we must already have a Terminal Services licensing server. Does that sound probable?

Does this mean that the problems is going to be at our end, rather than with the client? This being based on OUR server issuing the license t otheir machine.

Sorry, I must explain. I am not (as you no doubt have guessed) involved in setting up the Citrix servers, applications, etc. However, as I produce/ update the database(s) in question, that makes me the ponit of contact for the client. As such, I don't have any real technical knowledge of Citrix.

 

[ascotta]

Yes I would suggest that the problem is at your end. You need to get the people responsible for Citrix to check the availability of new TS-CAL's. I would guess that you have one. The fact that your customer/supplier ran ok for a while suggests that they had a temporary TS-CAL allocated and it has now timed out. It may be that they need access to the TS-CAL server too. Your Citrix/TS guys should sort it put for them tho. Or post here and we will help too

[blue]Arguably the best cat skinner around ! [/blue]

Cheers
Scott

 

[SHardy]

So how do the temporary ones get allocated? They have had access to this app for about 7 months now. It's certainly not something that they use on a daily basis.

Is it possible that they started of with a temporary license, and another temporary license was allocated after that?

If that is possible, then why would another temporary license not be allocated?

In the mean time, I shall try and chase this up with our technical guys. If they are not "too busy" still.

 

[ascotta]

OK the one thing you might try is on the client computer/s

Delete the following Registry key

HKEY_LOCAL_MACHINE\Software\Microsoft\MSLicensing\Store\licensennn

This is where it is stored. It could just mean the TS license server is not started. Get your guys to stop and start the license server service.

[blue]Arguably the best cat skinner around ! [/blue]

Cheers
Scott

 

[SHardy]

Thanks for all your help. I will update this post when (or if) I get anywhere with our tech guys.

I may also try that last suggestion.

Thanks again,
Simon

 

[ascotta]

Erm seeing as you admit to not being too au-fait with Citrix may I suggest you get the client to backup that bit of the registry before commencing the delete seing it is a customer/supplier n'all.

[blue]Arguably the best cat skinner around ! [/blue]

Cheers
Scott

 

[SHardy]

Hi,

Finally got a result. After speaking to the guy who has the main responsibility for setting up/ maintaining Citrix apps, he suggested that if it were a licensing issue, then more users would be affected (as it would be an issue with our licensing server).

Then it was back to head scratching. However, I thought I would ask the client to remove the ICA client and then re-install it, on the off chance that this might have an effect... and Hey Presto! That got it working again.

So to summarize:

Connection wasn't completing, and app was therefore not loading.
No error was returned.
Removing and re-installing client software fixed problem.
However, still no idea what the actual problem was.

Oh well, it's working now and I suppose that's all that matters.

 

[ascotta]

Here is a possibility, I have done that too. You had a goosed pn.ini or appsrv.ini. By reinstalling you got a pucker new version.

[blue]Arguably the best cat skinner around ! [/blue]

Cheers
Scott

 

[lb63640]

I was going to suggest re-installing the client, as this was a fix once for me---but you were already ahead of me