rolfejr
asked on
"SAS window: winlogon.exe" error on Citrix server
This is more of a Citrix question, but their support site is not very helpful and I can't find a specific Citrix forum on this site.
When our users log in to our Citrix server (Citrix Metaframe XP Feature Release 3 on Windows 2003) they get the following error:
SAS window: winlogon.exe - Application Error
The instaruction at "ox..." referenced memory at "0x..". The memory
could not be "written".
Click OK to terminate the application.
When they click OK, the session closes. We have applied every hotfix available on Citrix's site.
When our users log in to our Citrix server (Citrix Metaframe XP Feature Release 3 on Windows 2003) they get the following error:
SAS window: winlogon.exe - Application Error
The instaruction at "ox..." referenced memory at "0x..". The memory
could not be "written".
Click OK to terminate the application.
When they click OK, the session closes. We have applied every hotfix available on Citrix's site.
Do you have PCAnywhere installed on the server?
ASKER
No, and I checked the registry to see if it had been installed ever (it hasn't). However, we do use a program called NetOp Remote Control, which we use to get access to the console and to remote control other machines. While it could certainly be part of the problem, it has been installed on the server since before we were having this problem. This problem has been particularly difficult to track because it will only surface about once a week. Most of the time it is fine, and a reboot generally fixes it.
Is it feasible to try removing that software for a week to see if it helps with the problem? Maybe it only surfaces after the remote control is actually used?
ASKER
This is possible. I will first remove and reinstall the software. If the problem comes back, then I will just remove the software and leave it off for awhile.
ASKER
We have resolved this issue. It turned out to be a DNS misconfiguration. For anyone else who may encounter this, make sure that the DNS servers that your citrix server point to are ALL serving up internal DNS addresses. Also, make sure your DNS client is enabled. We had our primary DNS server giving out internal addresses, but the secondary was giving out external addresses, and our DNS client service on the citrix server was disabled. We removed the secondary DNS server, reenabled the DNS client service, and all was happy.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.