MDM Error and Event Messages
10/3/2008
The following shows Microsoft System Center Mobile Device Manager (MDM) 2008 components that provide error and event messages, and the range of error codes that correspond with each component.
| System Center Mobile Device Manager (MDM) component | Error code range |
|---|---|
Setup |
9000-9033 |
MDM Gateway Server
|
N/A
|
MDM Enrollment Server |
2001-2201 |
Group Policy |
4001-4011 |
MDM Device Management Server
|
N/A
|
MDM software distribution |
8010-8054 |
Self Service Portal |
13000-13004 |
The following shows Microsoft System Center Mobile Device Manager (MDM) 2008 error and event messages in numeric sequence by error code.
| Error code | Error string | Description | Resolution |
|---|---|---|---|
1000 |
WIPE_LOAD_SUCCESS |
The Wipe Service driver for MDM Device Management Server has correctly loaded. |
N/A |
1001 |
WIPE_SERVICE_STARTED |
The Wipe Service driver started successfully. |
N/A |
1002 |
WIPE_SERVICE_STOPPED |
The Wipe Service driver stopped. |
Restart the wipe service. |
1003 |
WIPE_ENROLLMENT_CONNECTION_FAILURE |
The Wipe Service driver did not contact the Enrollment service to remove a device. |
Check connectivity with MDM Enrollment Server, and verify that MDM Service Connection Points (SCPs) are set correctly. |
1004 |
WIPE_ENROLLMENT_CONNECTION_SUCCESS |
The Wipe Service driver successfully connected to the Enrollment service to remove a device. |
N/A |
1005 |
WIPE_CONFIGURATION_CHANGE |
The Wipe Service driver configuration was changed successfully. |
N/A |
1006 |
WIPE_INVALID_CONFIGURATION |
Invalid configuration received for the Wipe Service driver. |
Correct the Wipe Service Driver Configuration. |
1007 |
WIPE_CONFIGURATION_VALID |
The Wipe Service driver received valid configuration settings. |
N/A |
1008 |
WIPE_DATABASE_CONNECTION_SUCCESS |
The Wipe Service driver successfully connected to the database. |
N/A |
1009 |
WIPE_DATABASE_CONNECTION_ERROR |
Wipe Service driver did not connect to the database. |
Check database connectivity and configuration. |
1010 |
WIPE_REQUEST_SUCCESS |
Device reported that it started the wipe process. |
N/A |
1011 |
WIPE_REQUEST_FAILURE |
Device reported a failure processing the wipe request. |
Wait for the wipe service driver to retry, or manually cancel the request and retry. |
1012 |
WIPE_REQUEST_INVALID |
The outstanding wipe request for device %1 is invalid. |
Cancel and reissue this wipe request. |
1013 |
WIPE_REQUEST_SUCESS |
A wipe request for device %1 was submitted successfully to the Task database. |
N/A |
1014 |
WIPE_REQUEST_CANCEL |
A wipe request for device %1 was canceled. |
N/A |
1015 |
WIPE_ALERTER_SUCCESS |
The Wipe Administration Web service successfully connected to the Alerter. |
N/A |
1016 |
WIPE_ALERTER_FAILURE |
The Wipe Administration Web Service did not connect to Alerter agent. |
Restart the wipe service, check database connectivity and configuration, and check database SCPs. |
1017 |
WIPE_DELAYED_POLLING |
The Wipe Service driver did not finish the last database poll in the polling period of %1 minute. Wipe removal may be delayed. |
Check for too many wipe requests and remove some, or add another MDM Device Management Server. |
1018 |
WIPE_LOCK_TIMEOUT |
Remote Wipe service did not finish the most recent database poll within X minutes. Wipe request status reporting and device enrollment revocation may be delayed. |
N/A |
1019 |
WIPE_REQUEST_SUBMITTED |
The Wipe Administration Web Service successfully submitted a wipe request for device %1. |
N/A |
1020 |
WIPE_GATEWAY_CONNECTION_SUCCESS |
Device %1 is blocked. Remote Wipe service is connected to MDM Gateway Server Administration service. |
N/A |
1021 |
WIPE_GATEWAY_CONNECTION_FAILURE |
Device %1 is not blocked. Remote Wipe service did not connect to MDM Gateway Server Administration service. |
Wait for the wipe service to retry the connection, or manually cancel and retry the connection. |
1022 |
WIPE_REQUEST_EXPIRED |
Wipe request for device %1 has expired. |
Retry the wipe request. |
2001 |
ENROLLMENT_CONFIG_REFRESH_SUCCEEDED |
Global configuration has been refreshed successfully. |
N/A |
2002 |
ENROLLMENT_CONFIG_REFRESH_FAILED |
Global configuration could not update. Missing Configuration: %1 |
Check the configuration of the Enrollment service. |
2011 |
ENROLLMENT_AD_CONNECTION_ERROR |
Operation to Active Directory failed. |
Check domain controller connectivity and configuration. |
2021 |
ENROLLMENT_SQL_CONNECTION_ERROR |
Cannot connect to SQL Server. |
Check database connectivity and configuration. |
2031 |
ENROLLMENT_CA_CONNECTION_ERROR |
Cannot connect to the certification authority. |
Check Certificate Services connectivity and configuration, and check the configuration of the Enrollment service. |
2032 |
ENROLLMENT_CA_DRIVER_INIT_FAILED |
The certification authority driver did not initialize. |
Check the configuration of the Enrollment service, or use the product disc to repair the installation. |
2034 |
ENROLLMENT_CA_CANNOT_LOAD_CUSTOMDATA |
The certification authority cannot load custom data. |
Check the configuration of the Enrollment service. |
2101 |
ENROLLMENT_CANNOT_CONNECT_SYSTEM_SERVICE |
The Enrollment Web service cannot connect to the enrollment system service. |
Check the status of the Enrollment service that uses the Services MMC snap-in. |
2102 |
ENROLLMENT_WEB_SQL_CONNECTION_ERROR |
The Enrollment Web service cannot connect to an SQL database. |
Check database connectivity and configuration. |
2103 |
ENROLLMENT_IIS_SETTINGS_ERROR |
Incorrect IIS settings. |
Check IIS configuration. For example, make sure that SSL is enabled on the Enrollment Web site and that IIS metadata is not corrupted. |
2201 |
ENROLLMENT_SEND_EMAIL_FAILED |
Did not send e-mail message after it created the pending enrollment request. |
Check the SMTP server configuration. |
3000 |
TEE_DB_CONNECTION_FAILURE |
Database connection failure. Did not read or write information from the Device Management Database. |
Check database connectivity and configuration. |
3001 |
TEE_DB_CONNECTION |
The first successful Device Management Database connection (from no state or error state). |
N/A |
3002 |
TEE_OMA_SESSION_DID_NOT_COMPLETE |
The management session with device %1 was not completed. The connection may have been lost, or the session timed because of inactivity. |
Restart the management session with the device. |
3003 |
TEE_OMA_SESSION_COMPLETED_SUCCESSFULLY |
The device management session with device %1 completed successfully. |
N/A |
3004 |
TEE_ERROR_PROCESSING_REQUEST |
An error occurred while management updates for device %1 processed. |
Check Windows Event Viewer. |
3005 |
TEE_SUCCESS_PROCESSING_REQUEST |
The first successful device management operation processing (from no state or error state). |
N/A |
3006 |
TEE_BAD_SYNCML_FROM_CLIENT |
Incorrect SyncML received from device %1 during management session. |
Check Windows Event Viewer. |
3007 |
TEE_GOOD_SYNCML_RECEIVED_FROM_CLIENT |
First correct SyncML message that is received from device (from no state or error state). |
N/A |
3008 |
TEE_INVALID_CONFIGURATION_SETTINGS |
Invalid configuration settings: %1, %2 |
Correct the configuration settings. |
3009 |
TEE_VALID_CONFIGURATION_SETTINGS |
The first time valid configuration settings are received for the device management engine (from no state or error state). |
N/A |
3010 |
TEE_LOW_DISK_SPACE |
Free disk space for the device management engine is low. |
Delete unnecessary and unused files to increase the available disk space. |
4001 |
ADGP_SERVICE_STARTED |
The ADGP windows service was started successfully. Initialization of the driver completed successfully. |
N/A |
4002 |
ADGP_SERVICE_STOPPED |
The Active Directory Group Policy Windows service stopped, either intentionally or indirectly, because of a system reboot. Un-initialization of the driver completed successfully. |
Restart the ADGP service. |
4003 |
ADGP_CONFIGURATION_CHANGE |
The Active Directory Group Policy service driver received a configuration change notification, and the change was processed and applied successfully. |
N/A |
4004 |
ADGP_INVALID_CONFIGURATION_RECEIVED |
The Active Directory Group Policy service driver received a configuration change notification, but the data is invalid. The Active Directory Group Policy configuration in the database is corrupted. The cmdlets have validation and prevent Administrators from entering invalid values. So this event means that someone modified the database directly and changed the configuration value to something invalid, or somehow the database table was corrupted. |
Correct the Active Directory Group Policy driver configuration in the database. Configuration is stored in the ConfigurationData table in the AdminServices database. In the Set-MobilePolicyConfig cmdlet, check the PolicyRefreshInterval parameter. Thisshould be in the form days.hours:mins:secs. |
4005 |
ADGP_PREFETCHER_QUEUES_WITHIN_LIMITS |
The Active Directory Group Policy pre-fetcher queues have returned to the usual limits (available queue space is greater than 20 percent of capacity). |
This error is only logged when the queue exceeds the 80 percent threshold (or the queue is full), and then the queue returns to usual limits. |
4006 |
ADGP_PREFETCHER_QUEUES_NEARING_LIMITS |
The Active Directory Group Policy pre-fetcher queues are above the 80% threshold, and approaching the maximum limit of 10,000. The driver is overloaded. |
This error can occur if more than 10,000 devices are enrolled and you try to update the policy for all devices at the same time, or there is a problem with the driver. Check the setup log and Windows Event Viewer. |
4007 |
ADGP_PREFETCHER_QUEUES_FULL |
The Active Directory Group Policy pre-fetcher queues are full. The driver is overloaded. Additional requests to process device policy will be ignored until queue space becomes available. |
Check the setup log and Windows Event Viewer. |
4008 |
ADGP_DATABASE_CONNECTION_SUCCESS |
The Active Directory Group Policy driver successfully connected to the database, after a previous failure. |
This error message indicates that database connectivity is restored. |
4009 |
ADGP_DATABASE_CONNECTION_ERROR |
The Active Directory Group Policy driver could not connect to the database. |
This error message occurs because of temporary network outages and when the database service is stopped. Check database connectivity and configuration. |
4010 |
ADGP_AD_CONNECTION_SUCCESS |
The Active Directory Group Policy driver successfully connected to Active Directory, after a previous failure. |
This error message indicates that Active Directory connectivity is restored. |
4011 |
ADGP_AD_CONNECTION_ERROR |
The Active Directory Group Policy driver could not connect to the domain controller. Mobile policies cannot be updated until this connection is restored. |
This error message occurs because of temporary network outages and when Active Directory service is stopped. Check domain controller connectivity and configuration. |
5000 |
ALERTER_SUBMIT_SUCCESS |
The Alerter service successfully submitted a message to the database and GCM service. |
N/A |
5001 |
ALERTER_DB_SUCCESS |
The Alerter service successfully connected to the database. |
N/A |
5002 |
ALERTER_DB_FAILURE |
The Alerter service could not connect to the database. |
Check database connectivity and configuration. |
5003 |
ALERTER_GCM_SUCCESS |
The Alerter service successfully connected to the GCM service. |
N/A |
5004 |
ALERTER_GCM_FAILURE |
The Alerter service could not connect to the GCM service. |
Check gateway connectivity and configuration. |
5250 |
GCM_UNABLE_TO_ACCESS_DATABASE |
The GCM service could not access the database. |
Validate that the Administration service on this computer is running and that the database DNS name resolves correctlyfrom this computer. |
5251 |
GCM_DATABASE_ACCESS_RESTORED |
The GCM service connected to the database successfully. |
N/A |
5252 |
GCM_GATEWAY_CONNECTION_FAILURE |
The GCM service could not to connect to MDM Gateway Server. |
Make sure MDM Gateway Server is running and that you can access it from this computer. Also, make sure that the MDM Gateway Server DNS name resolves correctly from this computer. |
5253 |
GCM_GATEWAY_AUTH_FAILURE |
MDM Gateway Server could not authenticate the GCM service. |
Make sure that the certificate that isused by this computer is valid and trusted by MDM Gateway Server. Use the GCM certificate template to issue a valid certificate. The GCM uses certificates to connect MDM Gateway Server. |
5254 |
GCM_GATEWAY_CLIENT_AUTH_FAILURE |
The GCM service could not authenticate MDM Gateway Server. |
Make sure that the gateway certificate is not expired, and that it is trusted by this computer. The gateway certificate should use a Web site certificate template with the appropriate gateway domain name. |
5255 |
GCM_SKIPPED_INVALID_MESSAGE |
The GCM service ignored an invalid message. |
This message may include an MDM Gateway Server configuration message alert requests. Make sure that the applied MDM Gateway Server configuration is not corrupted. |
5256 |
GCM_INVALID_GATEWAY_URL |
The GCM service could not access MDM Gateway Server because of an invalid URL. |
Make sure that the access point for remote MDM Gateway Server management is valid. |
5257 |
GCM_NO_CLIENT_CERT_AVAILABLE |
The GCM service cannot find a valid certificate to authenticate with the computers that are running MDM Gateway Server. The GCM service can automatically detect a valid installed certificate that was issued with the corresponding GCM template. |
Restart the service after a valid certificate is installed. |
5258 |
GCM_ALL_GATEWAY_CONNECTIONS_FAILED |
The GCM service cconnect all computers that are running MDM Gateway Server. |
Make sure that the computers that are running MDM Gateway Server are reachable from this computer. Also, make sure the gateways DNS names resolve correctly from this computer. |
5259 |
GCM_ALL_MESSAGES_DELIVERED |
The GCM service successfully delivered all outstanding messages to all computers that are running MDM Gateway Server . These messages may include gateways configuration and alert requests. |
N/A |
5260 |
GCM_GATEWAY_FAILURE |
The GCM service received an HTTP error code %1%n from Gateway %2%n. This MDM Gateway Server may have rejected a message, which may include the configuration and alert requests for the server. |
Make sure that the applied MDM Gateway Server configuration is valid. The GCM service will try to resend this message shortly. |
5261 |
GCM_NO_MESSAGES_IN_DATABASE |
The GCM service found no messages to send to the computers that are running MDM Gateway Server. A message may include the configuration and message requests for the server. |
Check the Setup log and Windows Event Viewer to see whether any messages were missed. |
5262 |
GCM_UNABLE_TO_FIND_SELF_IN_SERVICE_LIST |
The GCM service did not retrieve the list of deployed GCM services from the database. |
Make sure that the database is running and that you can access it. Make sure that the Administration service is authorized to access the database and that MDM Device Management Server was installed successfully. |
5263 |
GCM_FOUND_SELF_IN_SERVICE_LIST |
The GCM service successfully retrieved the list of all other deployed GCM services from the database. |
N/A |
5264 |
GCM_NO_GATEWAYS_IN_DATABASE |
The GCM service found no deployed MDM Gateway Server in the database. |
After you install MDM Gateway Server, use the Add Gateway Wizard in MMC Administration Console to add a new MDM Gateway Server to the database. |
5265 |
GCM_SHUTDOWN_TIMEOUT |
The GCM service shutdown is delayed because of an inconsistent service state. |
Try to stop the service or reboot the computer if the service cannot be stopped. |
5500 |
ALERTER_GATEWAY_ALL_OK |
The Alerter agent successfully received a message from MDM Device Management Server and connected successfully with the VPN. |
N/A |
5501 |
ALERTER_GATEWAY_UNHANDLED_EXCEPTION |
The Alerter agent encountered an unhandled exception. |
Restart the Alerter service. |
5502 |
ALERTER_GATEWAY_VPN_SUCCESS |
The Alerter agent successfully connected to the VPN gateway. |
N/A |
5503 |
ALERTER_GATEWAY_VPN_ERROR |
There was an error in the connection between the Alerter agent and the VPN gateway. |
Restart the VPN and Alerter services. |
5504 |
ALERTER_GATEWAY_GCM_SUCCESS |
The Alerter agent successfully received a valid message from the GCM component. |
N/A |
5505 |
ALERTER_GATEWAY_GCM_INVALID |
The Alerter agent received an invalid message from the GCM component. |
Restart the GCM service. |
5506 |
ALERTER_GATEWAY_RECEIVED_ACK |
The Alerter agent successfully received an acknowledgement of a message from device %1. |
N/A |
5507 |
ALERTER_GATEWAY_NO_ACK |
The Alerter agent sent the maximum number of retries to device %1 but received no acknowledgement. The device may be disconnected. |
Check device connectivity and configuration. |
6001 |
ADMIN_SERVICES_CONFIG_UPDATED |
The configuration loader for the %1 component has successfully updated the component's configuration. |
N/A |
6102 |
ADMIN_SERVICES_AUTHORIZATION_FAILURES |
%1 failed authorization attempts have occurred in the last %2. |
|
6103 |
ADMIN_SERVICES_ACTIVEDIRECTORY_FAILURES |
Active Directory operation has failed inside %1.%nDetail: %2. |
Check domain controller connectivity and configuration. |
6104 |
ADMIN_SERVICES_DATABASE_RETRY |
The %1 component could not connect to the Administration services database. The component will retry the connection. |
Check database connectivity and configuration. |
6105 |
SERVICE_UNINITIALIZATION_FAILURE |
The MDM service driver host could not uninitialize component %1 when it attempts to stop the service. |
|
6201 |
ADMIN_SERVICES_CONFIG_DB_FAILURE |
The configuration loader for the %1 component was unable to access the database. Configuration items for this component may be out of date. |
Check database connectivity and configuration. |
6202 |
SERVICE_MISSING_CONFIGURATION |
The MDM service driver host cannot install or start a service because it could not find the %1 configuration file. |
Use the MDM product disc to repair the installation and restore the original configuration files. |
6203 |
SERVICE_INVALID_CONFIGURATION |
The MDM service driver host cannot install or start a service because the contents of the %1 configuration file are invalid. |
Use the MDM installation disc to repair the installation and restore the original configuration files. |
6205 |
SERVICE_INITIALIZATION_FAILURE |
The MDM service driver host could not initialize component %1 when it attempts to start the service. |
|
7000 |
Inventory_Enabled |
Inventory Collection Enabled |
N/A |
7001 |
Inventory_Disabled |
Inventory collection disabled |
N/A |
7002 |
Inventory_Restore_Defaults |
Inventory data collection restored to default settings |
N/A |
8010 |
SWD_DRIVER_STARTED |
MDM software distribution driver started successfully. |
N/A |
8011 |
SWD_DRIVER_STOPPED |
MDM software distribution driver stopped successfully. |
N/A |
8012 |
SWD_DRIVER_EXCEPTION |
MDM software distribution driver encountered an exception when initializing the driver. |
Restart the MDM software distribution driver. |
8020 |
SWD_SUS_SYNC_SUCCESS |
The MDM software distribution driver successfully synchronized updates from Windows Software Update Service (WSUS). |
N/A |
8021 |
SWD_SUS_BAD_UPDATE |
MDM software distribution driver could not parse the update, which may be invalid or contains unknown elements. |
Check the update to see why it could not be parsed. |
8022 |
SWD_SUS_CONNECTION_LOST |
MDM software distribution driver lost its connection to the WSUS database. |
Check database connectivity and configuration. |
8024 |
SWD_SUS_MISSING_DEPENDENCY |
MDM software distribution driver received an invalid update. One of the update dependencies is missing, or a dependency cycle exists in the graph. |
Check the update and correct any dependency issues. |
8030 |
SWD_TEE_CONNECTION_RESTORED |
MDM software distribution driver restored its connection to MDM Device Management Server. |
N/A |
8031 |
SWD_TEE_CONNECTION_LOST |
MDM software distribution driver lost its connection to the MDM Device Management Server. |
Retry the connection to the Device Management Engine. |
8040 |
SWD_MATCHING_SUCCESS |
MDM software distribution driver completed the matching process successfully. |
N/A |
8041 |
SWD_MATCHING_INSUFFICIENT_RESULTS |
MDM software distribution driver received insufficient device results. One or more LocURI is missing. |
Check and correct the LocURI value. |
8042 |
SWD_MATCHING_UNKNOWN_GROUP |
MDM software distribution driver received an unknown target group from the device. |
Check and correct the target group. |
8043 |
SWD_MATCHING_EXCEPTION |
MDM software distribution driver encountered an unhandled exception within the Matching Process. |
Contact Microsoft Customer Service and Support (CSS) if the problem persists. |
8044 |
SWD_MATCHING_UNRECOVERABLE_EXCEPTION |
MDM software distribution driver encountered an unrecoverable exception during Update Matching. |
Restart the MDM Software Distribution Service, or restart the computer. |
8045 |
SWD_MATCHING_DEVICE_REGISTRATION_FAILED |
Device Registration failed for the device. Wsus threw an ArgumentException or SqlException. |
Check the registration settings and retry device registration. |
8050 |
SWD_REPORTING_SUCCESS |
MDM software distribution driver completed the reporting process successfully. |
N/A |
8051 |
SWD_REPORTING_EXPORT_SUCCESS |
MDM software distribution driver's reporting process successfully exported results in WSUS. |
N/A |
8052 |
SWD_REPORTING_EXCEPTION |
MDM software distribution driver encountered an unhandled exception within the Reporting Process. |
Contact a Microsoft representative if the problem persists. |
8053 |
SWD_REPORTING_EXPORT_FAILED |
TheMDM software distribution driver reporting process could not export results in WSUS. |
Contact a Microsoft representative if the problem persists. |
8054 |
SWD_REPORTING_UNRECOVERABLE_EXCEPTION |
MDM software distribution driver encountered an unrecoverable exception during reporting. |
Restart the MDM software distribution Service, or restart the computer. |
9000 |
SETUP_INITIATED |
Setup initiated successfully. |
N/A |
9001 |
SETUP_COMPLETED_SUCCESSFULLY |
Setup completed successfully. |
N/A |
9002 |
SETUP_COMPLETED_WITH_ERRORS |
Setup completed with errors. |
Check the setup logs and Windows Event Viewer. |
9003 |
SETUP_DATABASE_COMPLETED_SUCCESSFULLY |
Setup successfully provisioned the databases. |
N/A |
9004 |
SETUP_DATABASE_FAILED |
Setup could not provision the database. |
Check the setup logs and Windows Event Viewer. |
9005 |
SETUP_ROLLBACK_INITIATED |
Setup initiated a rollback because an error occurred. |
Check the setup logs and Windows Event Viewer. |
9006 |
SETUP_DATABASE_STARTED |
Setup has initiated database provisioning. |
N/A |
9007 |
SETUP_FAILED |
Setup failed because of an error. |
Check the setup logs and Windows Event Viewer. |
9008 |
SETUP_CERTIFICATES_FAILED |
Setup could not provision certificates for the services and Web sites. |
Check the Deployment Guide to configure certificates. |
9009 |
SETUP_CERTIFICATES_INITIATED |
Setup started the certificate request and installation process. |
N/A |
9010 |
SETUP_UNHANDLED_EXCEPTION |
Setup encountered an unhandled exception. Setup failed. |
Check the Setup logs and Windows Event Viewer. |
9011 |
SETUP_PREREQ_FAILURE |
Setup failed because of a missing prerequisite. |
Check the Planning Guide to make sure that all prerequisites are installed correctly. |
9012 |
SETUP_DATABASE_CONNECT_FAIL |
Setup could not connect to the database. |
Check database connectivity and configuration. |
9013 |
SETUP_AD_CONNECT_FAIL |
Setup could not connect to Active Directory. |
Check domain controller connectivity and configuration. |
9014 |
SETUP_AD_INITIATED |
Setup initiated Active Directory operations. |
N/A |
9015 |
SETUP_AD_COMPLETED_SUCCESSFULLY |
Setup successfully completed Active Directory operations. |
N/A |
9016 |
SETUP_INVALID_URI |
The URI specified is invalid. |
Check that the URI is valid. |
9017 |
SETUP_INVALID_DATABASE |
The specified database location is invalid. |
Check the database input and retry setup. |
9018 |
SETUP_INVALID_DATABASE_CREDENTIALS |
The database credentials specified were invalid. |
Check that the credentials are valid. |
9019 |
SETUP_INVALID_CA |
The specified certification authority location or name is invalid. |
Check the CA input and retry setup. |
9020 |
SETUP_AD_FAILED |
Setup could not finish Active Directory operations. |
Check domain controller connectivity and configuration. |
9021 |
SETUP_UNINSTALL_COMPLETED_SUCCESSFULLY |
Setup completed the uninstall process successfully. |
N/A |
9022 |
SETUP_UNINSTALL_FAILED |
Setup could not uninstall. |
Check the Setup logs and Windows Event Viewer. |
9023 |
SETUP_UNINSTALL_COMPLETED_ERRORS |
Setup completed the uninstall process with errors. |
Check the Setup logs and Windows Event Viewer. |
9024 |
SETUP_UNINSTALL_DB_REMOVE_STARTED |
Setup has initiated database removal. |
N/A |
9025 |
SETUP_UNINSTALL_DB_REMOVE_SUCCESSFUL |
Setup has successfully removed the databases. |
N/A |
9026 |
SETUP_TIME_EXPIRED |
The time limit to install has expired. |
Obtain a newer version of the product. |
9027 |
SETUP_VPN_DRIVER_FAILED |
The VPN driver could not install. |
Check the Setup logs and Windows Event Viewer. |
9028 |
SETUP_INVALID_CERTIFICATE |
A certificate specified is invalid. |
Check the certificate and try again. |
9029 |
SETUP_INVALID_IP |
The IP address specified is invalid. |
Specify a valid IP address. |
9030 |
SETUP_INVALID_PORT |
The port specified is invalid. |
Specify a valid port. |
9031 |
SETUP_AD_CONFIG_NOT_RUN |
The Active Directory Configuration Tool must be run before Setup. |
Check the Planning Guide for Setup prerequisites. |
9032 |
SETUP_AD_NOT_CONFIGURED |
Active Directory is not configured correctly. |
Check the Deployment Guide to correct this problem before uninstalling. |
9033 |
SETUP_CERTIFICATES_COMPLETED_SUCCESSFULLY |
Setup completed the certificate request and installation process successfully. |
N/A |
12000 |
VPNSERVICE_IKE_SA_ESTABLISHED |
Client connected successfully. |
N/A |
12001 |
VPNSERVICE_IKE_SA_ENDED |
Client connection ended. |
Retry the client connection. |
12002 |
VPNSERVICE_IKE_SA_RECONNECT |
Client is attempting to reconnect. An active session already exists. The active session will be deleted. |
N/A |
12003 |
VPNSERVICE_IKE_SA_REKEY |
Successfully rekeyed the security association with the client. |
N/A |
12004 |
VPNSERVICE_AUTH_FAILURE |
IKE security association creation failed due to authentication failure. |
This event indicates an invalid client certificate or certificate chain. Re-enroll the device and connect again. |
12005 |
VPNSERVICE_IKE_NEGOTIATION_FAILURE |
IKE security association negotiation failed. |
This event indicates a configuration mismatch between the device and MDM Gateway Server. For example, if the server does not support a Diffie-Hellman Group (DHGroup) that the client uses for key exchange, then negotiation failures may occur. Check the MDM Gateway Server configurations, particularly the DHgroup and encryption algorithms. They should support the client configurations. |
12006 |
VPNSERVICE_DEVICE_BLOCKED |
Device blocked. |
N/A |
12007 |
VPNSERVICE_IKE_HALF_CONNECTIONS_FAILURE |
Deleted x half open IKE connections due to no response from the peer. |
This event is a gateway engine internal audition event, and has no impact on MDM Gateway Server operation or configuration. |
12100 |
VPN_AGENT_INITIALIZED |
The VPN Agent initialized successfully, and is waiting for configuration updates. |
N/A |
12101 |
VPN_AGENT_INITIALIZATION_FAILED |
VPN Agent could not initialize. The VPN agent http handler class constructor gives this error when the system is out of memory. If IIS cannot start the http handler itself, this event is not raised. |
Check the Setup logs and Windows Event Viewer. |
12102 |
VPN_AGENT_UNAUTHORIZED_MESSAGE |
The gateway Agent could not authorize the message. The certificate generated by GCM could not be authorized by the VPN agent or Alerter because the certificate does not have the required Enhanced Key Usage (EKU) field. |
Check how the GCM certificate was generated. |
12103 |
VPN_AGENT_MALFORMED_MESSAGE |
The VPN Agent received invalid XML from Gateway Configuration Manager. |
Check MDM Gateway Server configuration and wait for the synchronization interval to be completed. Check how the GCM message in the Device Management database was corrupted. |
12104 |
VPN_AGENT_INVALID_CONFIGURATION |
The VPN configuration data that is received from Gateway Configuration Manager could not validate. |
Change the Gateway configuration and wait for the synchronization interval to be completed. Check GCM events for possible problems. |
12105 |
VPN_AGENT_API_ERROR |
The VPN Agent could not start the VPN runtime API. This error can occur if there is a problem with COM initialization, calling the runtime over COM fails, or the runtime returns an error. |
Enable agent, API, and VPN tracing. |
12106 |
VPN_AGENT_APPLIED_CONFIG |
The VPN Agent successfully applied %1. |
N/A |
12501 |
VPNSERVICE_DCOM_INIT_FAILED |
DCOM Initialization failed with error %1. Exiting service. |
Check the Setup logs and Windows Event Viewer. |
12502 |
VPNSERVICE_POLICY_MANAGER_INIT_FAILED |
Failed to initialize Mobile VPN Policy Engine due to error %1. Exiting service. |
Check the Setup logs and Windows Event Viewer. |
12503 |
VPNSERVICE_CERTIFICATE_IDENTITY_FAILURE |
Failed to identify IPSec certificate due to error %1. |
Check the Setup logs and Windows Event Viewer. |
12504 |
VPNSERVICE_LOCAL_CERTIFICATE_INIT_FAILURE |
Failed to initialize local certificate due to error %1. |
Check the Setup logs and Windows Event Viewer. |
12505 |
VPNSERVICE_CONFIGURATION_APPLY_FAILED |
Failed to apply new configuration due to error %1. |
Check the Setup logs and Windows Event Viewer. |
12506 |
VPNSERVICE_CONFIGURATION_APPLY_SUCCEEDED |
New configuration successfully applied. |
N/A |
12507 |
VPNSERVICE_OPERATIONAL_LOG_WRITE_FAILED |
Failed to write to operational log due to error %1. |
Consider changing properties of Mobile VPN Policy Engine operational log. |
12600 |
VPNSERVICE_ENGINE_FAILED_TO_START |
Failed to start the Mobile VPN Policy Engine. Reason: %2. |
Restart the Mobile VPN Policy Engine service. Check the Setup logs and Windows Event Viewer. |
12601 |
VPNSERVICE_ENGINE_STARTED_SUCCESSFULLY |
The Mobile VPN Policy Engine has successfully started. |
N/A |
13000 |
Near_Max_Log_File_Size |
Warning: Log file space usage is approaching the maximum space allocated. To free up space, the oldest log file will be deleted. |
Delete outdated log files, and configure your max log settings to a higher value. |
13001 |
Max_Log_File_Size_Exceeded |
Warning: Allocated log file space was exceeded. To free up space, the oldest log file was deleted. |
Delete outdated log files, and configure your max log settings to a higher value. |
13002 |
Log_File_Write_Error |
Cannot write to log file. |
Make sure that the disk is not full, the file and folder are writeable, and that the file is not corrupt. |
13003 |
Failure_Load_Config |
Cannot load configuration settings. |
Make sure that the file and folder are writeable, and that the file is not corrupt. |
13004 |
Failure_Save_Config |
Cannot save configuration settings. |
Make sure that the file and folder are writeable, and that the file is not corrupt. |