Nostferatu
IS-IT--Management
Hi all...
This is a quite lengthy Tip, and one I hope you never have to use, but should you experience the above named errors you will be thankful for having read...
I had one of the most bizzare problems with an even more bizzare fix. Potentially it was a disasterous error and one that could have led to many days/weeks/ possibly months (as I have read in one or two places) but has a ridiculously simple fix, which i thought I should share with my fellow Citrix fans.
The problem manifests itself by the idle sessions dissapearing being replaced by 30+ "downed" sessions, with no idle sessions clients cannot log onto the server, and nothing short of rebooting the server (iincluding resetting the listener, enabling other protocols, deleting and removing the ICA client etc) rectifies this, however... a reboot is a short lived solution, as soon as the first client logs on, the server throws out numerous "downed sessions" again, preventing further logon, and the original user is shortly kicked off.
Checking the error logs shows NUMEROUS errors reported as SESSION permission errors, with event ID of 34, a quick search provided me with the fix.
OK... ready for this...
You should imediately check the environment path for the server and remove any UNC resolved paths (IE %systemroot%) statements and replace with their difinitive path (IE M:\WTSRV , M:\WTSRV\SYSTEM32 etc) AND make sure that system root and system 32 pathing statements appear at the start of the string... so your statement will read...
M:\WTSRV;M:\WTSRV\SYSTEM32;[rest of path statement]
and thats it.... problem solved...
apparently Micro$oft are aware of the problem, but can not shed any light onto why or how, and to be honest, I was COMPLETELY perplexed and even a little scheptical when I found this fix.. but IT WORKS !!! there were 3 or 4 documents inidicating this fix buried deep in the Citrix solution forums, all originating from one poor guy who reportedly found the solution, he had been in communication with MS for 6.5 months before HE found the solution himself, bet he was flavour of the month...
Hope this is of use to someone at sometime... I know It saved me a LOT of heartache and lost hair...
Steve Marshall
Group IT
Technical Support Supervisor
(aka General Meddler)
The Expro Group
Reading
UK
This is a quite lengthy Tip, and one I hope you never have to use, but should you experience the above named errors you will be thankful for having read...
I had one of the most bizzare problems with an even more bizzare fix. Potentially it was a disasterous error and one that could have led to many days/weeks/ possibly months (as I have read in one or two places) but has a ridiculously simple fix, which i thought I should share with my fellow Citrix fans.
The problem manifests itself by the idle sessions dissapearing being replaced by 30+ "downed" sessions, with no idle sessions clients cannot log onto the server, and nothing short of rebooting the server (iincluding resetting the listener, enabling other protocols, deleting and removing the ICA client etc) rectifies this, however... a reboot is a short lived solution, as soon as the first client logs on, the server throws out numerous "downed sessions" again, preventing further logon, and the original user is shortly kicked off.
Checking the error logs shows NUMEROUS errors reported as SESSION permission errors, with event ID of 34, a quick search provided me with the fix.
OK... ready for this...
You should imediately check the environment path for the server and remove any UNC resolved paths (IE %systemroot%) statements and replace with their difinitive path (IE M:\WTSRV , M:\WTSRV\SYSTEM32 etc) AND make sure that system root and system 32 pathing statements appear at the start of the string... so your statement will read...
M:\WTSRV;M:\WTSRV\SYSTEM32;[rest of path statement]
and thats it.... problem solved...
apparently Micro$oft are aware of the problem, but can not shed any light onto why or how, and to be honest, I was COMPLETELY perplexed and even a little scheptical when I found this fix.. but IT WORKS !!! there were 3 or 4 documents inidicating this fix buried deep in the Citrix solution forums, all originating from one poor guy who reportedly found the solution, he had been in communication with MS for 6.5 months before HE found the solution himself, bet he was flavour of the month...
Hope this is of use to someone at sometime... I know It saved me a LOT of heartache and lost hair...
Steve Marshall
Group IT
Technical Support Supervisor
(aka General Meddler)
The Expro Group
Reading
UK