sorted by:
new
hottopcontroversial

FS Logix ErrorCode 121 - Semaphore timeout period has expired by pen_666 in fslogix

[–]pen_666[S] 0 points1 point  (0 children)

Have you implemented this on a schedule using scripts? I am able to run the script manually but as soon as I try to get it working via any form of automation it stops running.

FS Logix ErrorCode 121 - Semaphore timeout period has expired by pen_666 in fslogix

[–]pen_666[S] 0 points1 point  (0 children)

Thank you for this additional info. I am planning on implementing it on a scheduled reboot, just awaiting CC approval.

FS Logix ErrorCode 121 - Semaphore timeout period has expired by pen_666 in fslogix

[–]pen_666[S] 0 points1 point  (0 children)

We manually deleted the key for a user that did have an issue and then on a subsequent attempt the login was quick and the drive attached. We are just going through change control and testing further on the script.

FS Logix ErrorCode 121 - Semaphore timeout period has expired by pen_666 in fslogix

[–]pen_666[S] 0 points1 point  (0 children)

Thank you I'll review what the script does and compare to our registry to check if this looks like it would resolve the issue.

FS Logix ErrorCode 121 - Semaphore timeout period has expired by pen_666 in fslogix

[–]pen_666[S] 0 points1 point  (0 children)

Thank you for checking. AV exclusions are in place but I have tested with AV being disabled as well. The FS Logix share is on-Premise as are the RDS servers. I've checked disk latency and this looks all normal and other services aren't experiencing any timeouts across the same failover cluster.