Responding to event IDs

Delegated Administration Console events

Although Delegated Administration Console does not create Event IDs, it does provide error numbers that point to records in the error table in the configuration database. An error that is marked as "Fatal Error" is posted to the event log. The source column will display "WSH," an abbreviation for Windows Script Host.

For more information about error handling in Delegated Administration Console, see "Working with errors" and "View error information" in Delegated Administration Console Help.

Microsoft Provisioning Framework events

The following table describes all Event IDs for Microsoft Provisioning Framework (MPF).

Event ID	Description	Response
4103	The provisioning engine successfully updated the named procedure definitions from the configuration database.	No action is required.
4104	The provisioning engine successfully updated the properties from the configuration database.	No action is required.
4105	The provisioning engine successfully updated the list of transaction log servers from the configuration database.	No action is required.
4107	The provisioning engine failed while committing transaction ID = ######. The transaction might be in an inconsistent state. Check the transaction log database to determine the exact state of the transaction.	This event indicates a code or design error. The Microsoft Provisioning Framework Software Development Kit (SDK) contains useful information about transaction processing. For more information on the SDK and how to use it, see Microsoft Provisioning Framework SDK and documentation.
4108	The provisioning engine failed while aborting transaction ID = #####. The transaction might be in an inconsistent state. Check the transaction log database to determine the exact state of the transaction.	This event indicates a code or design error.
4109	The provisioning engine failed while aborting the transaction picked by the background thread for cleanup. TransactionID = ID, transaction log server = Server name database = Database name. The transaction might be in an inconsistent state. Check the transaction log database to determine the exact state of the transaction.	This event indicates a code or design error.
4110	Failed to load namespace=Message.	Restore the configuration database from the last good backup.
4111	Failed to load step definition=Message for namespace=Message.	Restore the configuration database from the last good backup.
4113	The provisioning engine failed while updating the batch status for the transaction with ID = Message.	This event indicates a code or design error.
4359	No security descriptor was set for SubmitTrustedRequest. Calls using SubmitTrustedRequest will be rejected from all users.	This event indicates a code or design error.
4360	No security descriptor was set for SubmitRequest. All users will be allowed to submit MPF requests using SubmitRequest.	This event indicates a code or design error.
4361	The transaction log database on server = name is not responding correctly. The server will be marked as unavailable. Attempts will be made periodically to check the availability of the server.	Check connectivity to the transaction log database from the computer that reported the event. The system might be under severe stress. Check the SQL performance counters on the computer.
4362	The transaction log database on server = Server Name is marked as available.	No action is required.
4364	A failure occurred on user authentication. The Active Directory server might be down. If you see this error again, contact the system administrator.	Check for connectivity to the domain controller from the computer that reported the error.
4365	Could not find the PasswordEncryptionKey property in the configuration database. Procedures marked to run under specific MPF credentials will not be executed.	This event indicates a code or design problem.
4366	Could not find the AuditValidityData property in the configuration database.	Verify that the Microsoft SQL Server hosting the configuration database is running and that the server reporting the error has network connectivity to the configuration database computer.
4608	A failure occurred while connecting to the configuration database. Previously cached configuration settings will be used. SQL connection string, SQL server name reported errors: error messages.	Check the network connection between the computer that generates the errors and the database. Check the SQL Server error log for more details. The server might be in the process of restarting, it might be turned off, or it might not be accessible through the network.
4609	A failure occurred while connecting the transaction log database, SQL connection string, SQL server name reported errors: error messages.	Check the network connection between the computer that generates the error and the database. Check the SQL Server error log for more details. The server might be in the process of restarting, it might be turned off, or it might not be accessible through the network.
4610	A transaction log failed to execute the command=command. The SQL server reported errors: error message. The following command cannot execute against the audit log database: SQL command. SQL server reported errors: Error messages.	This event indicates a code or design problem.
5119	A file system command failed to execute. Reason: Message	Check the network connections. This event appears only if a serious network or disk error has occurred.
5120	The required cleanup of the system failed. Reason: Message	This failure is often the result of the user not having appropriate permissions to perform specific actions.
5121	A backup operation failed. Reason: Message	This failure is often the result of the user not having appropriate permissions to perform specific actions.
5134	Resolution of execute statements failed from a procedure=Message namespace=Message executing procedure=Message namespace=Message. Check Event Viewer for additional namespace load errors.	Restore the configuration database from the last good backup.
5403	Calling user (Message) is not authorized to invoke secured interface method (Message).	The error is generated when the calling user does not have appropriate permissions to submit requests to provisioning engines or queue managers. Check the user's permissions in Provisioning Manager under the provisioning engines and queue managers properties. Important This failure might indicate a security attack. Corrective action can include blocking the Internet Protocol (IP) address that issued this request.
5404	Calling user User Name is not authorized to invoke the secured procedure Procedure Name.	This error is generated when the calling user does not have appropriate permissions to invoke the specified provisioning procedure. To authorize the caller, configure the procedure to grant the caller the required permissions.
5633	Error Message	This is an error generated by the operating system. Check the operating system documentation for additional information.
5635	The Provisioning Queue Manager service is paused.	If the operator has deliberately paused the Provisioning Queue Manager service, no action is required. Otherwise, restart the service.
5636	The Provisioning Queue Manager service is stopped.	If the operator has deliberately stopped the Provisioning Queue Manager service, no action is required. Otherwise, restart the service.
5638	The Provisioning Queue Manager service is started.	No action is required.
5640	The Provisioning Queue Manager service continued.	No action is required.
5641	The Provisioning Queue Manager service stability thread is ending.	No action is required.
5647	The Provisioning Queue Manager service failed to open the connection to the main log. The attempted connection string was: connection string.	Check the SQL server connection to the transaction log database. It might be that the server is not functioning or access is denied.
5648	The Provisioning Queue Manager service failed to create the log command: connection string.	Check the SQL server connection to the transaction log database. It might be that the server is down or access is denied.
5654	The Provisioning Queue Manager service failed to retrieve values from the log. The connection string was connection string.	Check the SQL server connection to the transaction log database. It might be that the server is down or access is denied.
5660	The Provisioning Queue Manager service successfully updated properties from the configuration database.	No action is required.
5661	The Provisioning Queue Manager service successfully updated the list of transaction log servers in the configuration database.	No action is required.
5888	The Provisioning Auditing and Recovery service is not able to connect to any provisioning engines of the site name.	There are no active provisioning engines. Activate at least one provisioning engine by doing the following: On all computers on which provisioning engines are installed, click Start, point to Programs, point to Administrative Tools, and then click Component Services. In the console tree, double-click Component Services, double-click Computers, double-click My Computer, and then double-click COM+ Applications. Right-click Provisioning Engines, and then click Start.
5889	The following command cannot execute against the audit log database: command. SQL server reported errors: error string.	Check the SQL Server errors to determine the reason for this failure. It might be that the server is off or access is denied. The corresponding table or stored procedure might be missing.
5890	The Provisioning Auditing and Recovery service is started.	No action is required.
5891	The Provisioning Auditing and Recovery service is stopped.	If the operator has deliberately stopped the service, no action is required. Otherwise, use Provisioning Manager to restart the service .
5892	The Provisioning Auditing and Recovery service cannot be started because it has not been installed properly.	There is a problem with the Provisioning Auditing and Recovery service registration. Try to reinstall the service.
5893	The Provisioning Auditing and Recovery service received a bad request.	The service received a request other than start or stop. Use Provisioning Manager to try again.
5894	The provisioning engine has called RollbackRequest on a provider that has failed and generated an exception. This indicates a problem with the provider. Notify the developer of this component that a failure has occurred. Transaction with ID=name on transaction log server = name and database = name will be marked IN_DOUBT and no future attempts to roll back the transaction will be made. Notify the system administrator to verify the consistency of various resources involved in the transaction. More information about the nature of the error might be available on the provisioning engine server.	Check the connection to the transaction log server.
5895	Failed while connecting to the audit log database. Connection String= connection string. SQL server reported errors: error message.	Check the SQL Server errors on the computer hosting the audit log database to determine the reason. Either the server is turned off or access is denied.
5896	An error occurred while moving records to the audit log database. SQL server reported errors: error message.	Check the SQL server errors to determine the reason. Either the server is down or access is denied.
6144	The SQL Provider encountered a connection error while executing a command. Connection String=message. The server reported errors:message.	Check the SQL server errors to determine the reason. The server is probably is down.
6145	The SQL Provider cannot create more than number connections with connection string=message.	Increase the maximum number of connections, which is defined by the MaxConnCount registry value, or increase the connect time-out by adding the following XML code to to ExecuteData: `<timeout connect=<n>/>`.
6400	The provisioning engine on server = name is not responding correctly. The server will be marked as unavailable. Attempts will be made periodically to check the availability of the server.	This event is generated when a client fails while communicating with a provisioning engine. Check the status of provisioning engine servers and the connectivity from the computer where the client is installed. Also, check for possible failures reported in Windows Event Viewer on the provisioning engine server.
6401	Provisioning Queue Manager service on server = name is not responding correctly. The server will be marked as unavailable. Attempts will be made periodically to check the availability of the server.	The event occurs when a client fails while communicating with the Provisioning Queue Manager service. Check status of servers running this service and the connectivity from the computer where the client is installed. Also, check for possible failures reported in Windows Event Viewer on the server running the Provisioning Queue Manager service.
6402	The provisioning engine on server = name is marked as available. Provisioning requests will now be sent to the server.	No action is required.
6403	Queue Manager on server = name is marked as available. Queued provisioning requests will now be sent to the server.	No action is required.
6404	Client successfully updated engine pool properties from the configuration database.	No action is required.
6405	Client successfully updated the list of provisioning engine servers from the configuration database.	No action is required.
6406	Client successfully updated the queue manager pool properties from the configuration database.	No action is required.
6407	Client successfully updated the list of queue manager servers from the configuration database.	No action is required.