All Topics » Pulse Connect Secure



dsSamProxy.exe crashes unexpectedly very frequently


jyankowski
Contributor (0)
Oct 23, 2017 9:07pm
I want to start off by saying that I'm just an end user of Pulse Secure in a large company, so I don't have a ton of access or information to give about this issue, however the company's technology help desk hasn't been very helpful.

We connect to the corporate network using Pulse Secure as a part of the login process (the ultimate endpoints being a virtual machine VDI). At random times after login, the process called dsSamProxy.exe will close unexpectedly (and a message popup will state as much). When this happens, the connection terminates and the full login process has to be reinitiated (which is inconvenient because I have to log into 3 different prompts before I can even get to my virtual machine). This can happen as frequently as every few minutes or as infrequently as every few hours.

I have a dsSamproxy.dmp file that might be of use. Is there any way I can provide this to someone to look at?

Thank you!



zanyterp
Pulse Secure Contributor (40)
Oct 26, 2017 1:44pm
Unfortunately, without going through your IT team who has a support account with us, there is not
Are there others seeing the same behavior?
I am sorry to hear that you are experiencing failures with the client
    jyankowski
    Contributor (0)
    Oct 26, 2017 2:17pm
    Yes. Everyone in our office who uses this method of connectivity has this problem (about 10 people or so). The tech org seems very uninterested in solving this problem, hence why I decided to reach out here.
    zanyterp
    Pulse Secure Contributor (40)
    Oct 26, 2017 5:02pm
    Thank you for the update; I am sorry to hear that
    Does this happen to everyone around the same time?
    When the failure happens, is more than one person logged in to the service at the same time?
    Does it happen without that being true?
jyankowski
Contributor (0)
Oct 26, 2017 6:57pm
It happens to everyone at different times, there doesn't seem to be any correlation between users. It can happen if all of us are logged in or if only one is logged in too.

After some more playing around, it seems like it has something to do with other applications running on the machine at the time. When looking at the debug logs, it seems like WSAM is always proxying Chrome.exe right before it crashes. Our WSAM policy has certain processes which are allow bypassing the proxy, one such exception is that any executable named apache*.exe is bypassed. I renamed my Chrome's executable to be apachechrome.exe and since I've done this I haven't seen WSAM crash.

I had a co-worker try the above as well and it seems to be working for them too. I'm not sure if other processes will cause a similar crash, but it seems like something about Google Chrome doesn't agree with WSAM and causes WSAM to crash.