Ivanti Secure Access Client Log Files

Ivanti Secure Access Client writes information to log files on Windows and Apple OS X endpoints. If you need to investigate a problem with connectivity on a Ivanti Secure Access Client endpoint, you can instruct the user to save the client logs and e-mail them to you.

The user saves logging information by opening Ivanti Secure Access Client and then clicking File > Logs > Save As. All relevant log files are added to a single file, LogsAndDiagnostics.zip. The user saves the .zip file and then makes it available to you.

Ivanti Secure Access Client maintains its own log files on all supported platforms. On Windows, Ivanti Secure Access Client also logs its major operational events into Windows Event Log. Network administrators can review the Ivanti Secure Access Client event log to help troubleshoot problems. Ivanti Secure Access Client Log Files lists the Ivanti Secure Access Client messages that can appear in the Windows event log.

To view the Ivanti Secure Access Client messages:

1. Open the Windows Event Viewer.

2. Click Applications and Services > Ivanti > Operational.

ID	Level	Message	Description
600	error	The connection <ID> failed authentication: Error <ID>.	802.1X EAP authentication failure.
601	informational	User has canceled authentication of the connection <ID>.	The user canceled 802.1X EAP authentication.
602	error	Failure writing wireless LAN profile for connection <ID> Error <ID>: Reason <ID>: Profile: <ID>.	A failure occurred while a wireless LAN profile was being created or modified.
603	error	Failure writing wireless LAN profile for connection <ID> Error <ID>.	A failure occurred while a wireless LAN profile was being deleted.
604	error	Failure writing wired LAN profile for connection <ID> Error <ID>: Profile: <ID>.	A failure occurred while a wired LAN profile was being created or modified.
605	error	Failure writing wired LAN profile for connection <ID> Error <ID>.	A failure while a wired LAN profile was being deleted.
500	informational	Pulse servicing has completed successfully. All components are up to date.	Ivanti Secure Access Client servicing was successful.
501	informational	Pulse servicing has completed successfully. All components are up to date.	Servicing was requested but all components were up to date.
502	error	Pulse servicing has failed. Failure summary:	Ivanti Secure Access Client servicing failed.
100	informational	User requested connection <ID> to start.	The user initiated a connect request.
101	informational	User requested connection <ID> to stop.	The user initiated a disconnect request.
102	informational	Connection <ID> is starting because its policy requirements have been met. Connection Policy: <ID>.	A connection was started because of a policy evaluation.
103	informational	Connection <ID>) is stopping because of its policy requirements. Connection Policy: <ID>.	A connection was stopped because of a policy evaluation.
104	informational	Connection <ID> is stopping because of transition to context <ID>.	The machine-to-user connection was disconnected to transition to another identity.
105	informational	Connection <ID> is starting because of transition to context <ID>.	The machine-to-user connection was connected as part of the transition to another identity.
106	informational	Connection <ID> is disconnected due to computer suspend.	The connection to Ivanti Connect Secure was disconnected because the computer is being suspended.
107	informational	Connection <ID> is disconnected due to login error.	A credential provider connection was disconnected because of a login error.
108	informational	Connection <ID> is disconnected because it was modified.	A connection was disconnected because it was modified.
109	informational	User requested connection <ID> to suspend.	The user initiated a suspend request.
110	informational	User requested connection <ID> to resume.	The user initiated a resume request.
1	informational	The Ivanti service version <ID> has successfully started.	The Ivanti Secure Access Client service started.
2	informational	The Ivanti service has stopped.	The Ivanti Secure Access Client service stopped.
200	error	No connections matching URL <ID> were found in Pulse database. Request to start a connection from the browser has failed.	Ivanti Secure Access Client failed to resume a connection from the browser.
400	error	The host check for connection <ID> has failed. Failed policies: <ID>.	Host Checker failed one or more policies.
300	informational	The connection <ID> was established successfully through web-proxy <ID>.	Ivanti Secure Access Client established a connection to Ivanti Connect Secure or Ivanti Policy Secure through a Web proxy.
301	informational	The connection <ID> was established successfully to address <ID>.	Ivanti Secure Access Client established a direct (nonproxy) connection to Ivanti Connect Secure or Ivanti Policy Secure.
302	informational	The connection <ID> was disconnected.	The Ivanti Secure Access Client connection was disconnected from the Ivanti server.
303	error	The connection <ID> encountered an error: <ID> Peer address: <ID>.	A connection encountered an error.
304	error	The connection <ID> was disconnected due to change in routing table. Interface address changed from <ID> to <ID>.	Ivanti Secure Access Client detected a change in the route to the Ivanti server.
305	informational	VPN tunnel transport for connection <ID> switched from ESP to SSL mode due to missing ESP heartbeat.	ESP to SSL fallback occurred because of missing ESP heartbeats.
306	informational	VPN tunnel for connection <ID> is switched to ESP mode.	Tunnel transport switched to ESP mode.
307	error	The connection <ID> encountered an error: System error: <ID> Peer address: <ID>.	The Ivanti Secure Access Client connection failed because of a system error.
308	error	The server disconnected connection <ID> Reason <ID>: Peer address: <ID>.	The server disconnected a connection.