cancel
Showing results for 
Search instead for 
Did you mean: 

Pulse Secure repeatedly asking for credentials

dn123
Not applicable

Pulse Secure repeatedly asking for credentials

I am using pulse secure v 5.1.7.61533 on OSX Yosemite 10.10.5 on my corporate VPN. The client connects, but after a minute asks for a new token and repeatedly does this ever 20 seconds or so indefinitely. The VPN is basically unusable. Here are some log messages. Do any of these look like they may indicate a problem?

00179,09 2016/01/11 22:27:02.493 3 root dsAccessService ConnectionManager p39967 t4507 ConnectionManagerService.cpp:964 - 'LocationManager' network settled down, so handle network events
00220,09 2016/01/11 22:27:02.493 3 root dsAccessService ConnectionManager p39967 t4507 PolicyEvaluator.cpp:56 - 'ConnectionManager' PolicyEvaluator::evaluate policy [] auto kEvalResultInvalid connect 0 di
sconnect 1 transition 0
00322,09 2016/01/11 22:27:02.493 3 root dsAccessService ConnectionManager p39967 t4507 ConnectionEntry.cpp:1065 - 'ConnectionManager' onNetworkChange(ive:50bc00edaf2a4d5cadc8d826e5c3493c), manual: 1, hasI
p: 1, connect: 0/1, disconnect: 1/0, machineSuspended: 0, connSuspended: 0, context: 1, identity: user, state kStateConnected
00159,09 2016/01/11 22:27:04.747 3 root dsAccessService dsAccessService p39967 t220B accessPluginLoader.cpp:617 - 'AccessService' plugin eapService, unloading(0x0)...
00156,09 2016/01/11 22:27:04.747 3 root dsAccessService dsAccessService p39967 t220B accessPluginLoader.cpp:335 - 'AccessService' plugin eapService, stopping(0)...
00167,09 2016/01/11 22:27:04.747 3 root dsAccessService eapService p39967 t220B accessMonitorablePlugin.cpp:27 - 'PluginMonitor' Can't stop plugin monitoring. Code 0xe000000c
00152,09 2016/01/11 22:27:04.748 3 root dsAccessService dsAccessService p39967 t220B accessPluginLoader.cpp:388 - 'AccessService' plugin eapService has stopped
00156,09 2016/01/11 22:27:04.748 3 root dsAccessService dsAccessService p39967 t220B accessPluginLoader.cpp:291 - 'AccessService' plugin eapService, cleaning up...
00160,09 2016/01/11 22:27:04.748 3 root dsAccessService dsAccessService p39967 t220B accessPluginLoader.cpp:322 - 'AccessService' plugin eapService has been cleaned up
00151,09 2016/01/11 22:27:04.748 3 root dsAccessService dsAccessService p39967 t220B accessService.cpp:415 - 'AccessService' notify plugin eapService unloaded
00161,09 2016/01/11 22:27:18.705 3 root dsAccessService iveConnectionMethod p39967 tA707 connInstance.cpp:2011 - 'iveConnectionMethod' IVE fatal error message length 39
00160,09 2016/01/11 22:27:18.705 2 root dsAccessService iveConnectionMethod p39967 tA707 connInstance.cpp:2023 - 'iveConnectionMethod' received fatal error from IVE: 7
00173,09 2016/01/11 22:27:18.705 2 root dsAccessService iveConnectionMethod p39967 tA707 connInstance.cpp:2025 - 'iveConnectionMethod' received IVE fatal error string: agentd error
00158,09 2016/01/11 22:27:18.705 3 root dsAccessService iveConnectionMethod p39967 tA707 connInstance.cpp:1975 - 'iveConnectionMethod' Setting state to retry-connect
00154,09 2016/01/11 22:27:18.705 3 root dsAccessService iveConnectionMethod p39967 tA707 connInstance.cpp:2434 - 'iveConnectionMethod' Queuing schedule retry 2 0

Obviously PolicyEvaluator::evaluate returning kEvalResultInvalid and disconnect 1 seems to be at the start of the issue. Do you know what this means? Does this indicate a server configuration issue?
1 REPLY 1
jbeakley
Contributor

Re: Pulse Secure repeatedly asking for credentials

dn123,

"agentd error" is a message sent from the server, and generally means that something unexpected happened on the server side (on the Pulse Connect Secure gateway you are connecting to). Generally in these cases, the best course of action is to contact your system administrator and have him/her create a case with Pulse Secure's Global Support Center so that the proper diagnostic data from the server can be collected and analyzed.

http://www.pulsesecure.net/support

-JB