Site Server - Windows NT Events for Site Server 3.0, Commerce Edition

August 1999 

Introduction

Microsoft Site Server 3.0, Commerce Edition services can produce a large number of Microsoft Windows NT events. Solving the problems pinpointed by these event notifications can be difficult. This document can help alleviate these difficulties by providing a partial list of many service events along with actions that may help solve the problems.

Use Microsoft Event Viewer to monitor system events.

Events are grouped by service and listed in order of message identifier.

Each entry begins with the message identifier, followed by the event message string. The next line identifies the type of the event: Success, Informational, Warning, or Error.

Finally, possible remedies are provided under Recommended Action. Some events do not require administrator action.

The percentage (%) characters in the event message strings are placeholders for message variables. In actual event messages, these will be replaced by specific values or information.

List of Microsoft LDAP Static Store Events

The following list enumerates the static store events for the LDAP service.

1 Static Store Error: %1 

Type: Error
Recommended Action: No action is required.

2 Microsoft Lightweight Directory Access Protocol (LDAP) Static Store DLL Load Failed. 

Type: Error
Recommended Action: Ensure that %systemroot%\system32\inetsrv\storedb.dll is present, current, and valid. Reinstalling Microsoft® Site Server 3.0 may be the easiest way to do this.

3 Microsoft LDAP Static Store DLL Loaded. 

Type: Informational
Recommended Action: No action is required.

10 Memory Allocation Failed. 

Type: Error
Recommended Action: The system is low on memory. Close other applications on this server and try again. If this error occurs frequently, add memory to the computer running the LDAP Service.

11 Memory Allocation Failed. Additional Info: %1 

Type: Error
Recommended Action: The system is low on memory. Close other applications on this server and try again. If this error occurs frequently, add memory to the computer running the LDAP Service.

20 Unable to connect to database server with connect string: %1. 

Type: Error
Recommended Action: Ensure that both Named Pipes and TCP/IP connectivity is configured and working between the server computer running the LDAP Service and the server computer running Microsoft® SQL Server™ named in the error. Make sure server name, database name, login, and password information are correct. Make sure SQL Server is running.

21 LDAP Administrative Max Connections to database exceeded 100 times for %1. 

Type: Warning
Recommended Action: LDAP server has requested more than the configured maximum number of connections 100 times. This may not be a problem if the administrator is intentionally throttling LDAP connections to SQL Server. The administrator can change this default by going to the LDAP Control Panel, Directory Properties Page, selecting the appropriate SQL db, then choosing Edit.

30 SQL Error: %1. 

Type: Warning
Recommended Action: This is an informational error that indicates a problem of some kind in completing a SQL Server operation. Note these errors and report them to Microsoft Technical Support if the overall system performance is questionable.

41 Failed to back out group membership for Rdn: %1. 

Type: Error
Recommended Action: Validate the state of the named Relative Distinguised Name (RDN).

42 Succeeded backing out group membership for Rdn: %1. 

Type: Informational
Recommended Action: No action is required.

60 Unable to Add Partition: %1. 

Type: Error
Recommended Action: Validate the state of the container to be partitioned. Restart partitioning sequence after validating db state and parameters.

61 Maximum number of partitions exceeded. 

Type: Error
Recommended Action: The computer running the LDAP Service supports a maximum of 255 namespaces and 255 value partitions. Exceeding either of these limits will result in this error.

70 Failed to modify subref object. 

Type: Warning
Recommended Action: If namespace partition root objects appear to be inconsistent, run the modify operation again.

80 The Code Page for the Database could not be determined. %1 

Type: Error
Recommended Action: No action is required.

81 The database code page is not valid for this NT installation CodePage=%1. 

Type: Error
Recommended Action: If SQL Server is freshly installed, reinstall it with the appropriate code page. If data loss is an issue, contact Microsoft Technical Support.

100 Partitioning wizard unable to load setupstr.dll. 

Type: Error
Recommended Action: Verify that setupstr.dll is present and registered.

101 Partitioning wizard unable to setup tables, stored procedures, indices, and data on target db (%1). Verify target db is valid, stable, and empty. 

Type: Error
Recommended Action: Verify target database is valid, stable, and empty. Verify target SQL Server computer is configured with both Named Pipes and TCP/IP connectivity.

102 Partitioning wizard unable to load dscomobj.dll. 

Type: Error
Recommended Action: Verify that dscomobj.dll exists and is current and valid. The easiest way to do this is to refresh the installation.

103 Partitioning wizard: %1 appears to be invalid or out of date. Please refresh your install. 

Type: Error
Recommended Action: The named dll should be validated and reinstalled, if necessary.

104 Partitioning wizard has lost database integrity. Partition may be invalid. 

Type: Error
Recommended Action: Validate the state of target container. Validate the state of partition target databases. Restart the partitioning sequence, if necessary.

105 Partitioning setup failed to delete some objects from the source partition. 

Type: Warning
Recommended Action: No action is required..

106 Attempted to partition a non-existent container %1. 

Type: Warning
Recommended Action: Create the container before trying to partition it.

107 Attempted to partition a non-empty container %1. 

Type: Warning
Recommended Action: Target an empty container.

108 Attempted to partition a partitioned container %1. 

Type: Warning
Recommended Action: Target a container that has not already been partitioned.

110 Partitioning setup failed and the DSOGRID table could not be restored to its previous state. System unstable, consult documentation. 

Type: Error
Recommended Action: Consult documentation or contact support, as needed.

111 Partitioning setup failed and the SUBREFS table could not be restored to its previous state. System unstable, consult documentation. 

Type: Error
Recommended Action: Consult documentation or contact support, as needed.

120 Deleted a partitioned container but was unable to remove partition info from the DSOGRID table. System unstable, consult documentation. 

Type: Error
Recommended Action: Consult documentation or contact support, as needed.

121 Deleted a partitioned container but was unable to remove partition info from the DSOGRID table. System unstable, consult documentation. 

Type: Error
Recommended Action: Consult documentation or contact support, as needed.

122 Add Db Server admin call made with an invalid value partition id for container %1. 

Type: Error
Recommended Action: The most likely cause of this error is an attempt to configure more value partition databases than were specified in the initial partitioning configuration. Validate the scripts being used for partitioning setup.

123 Query failed attempting to determine the value partition count for container %1. 

Type: Error
Recommended Action: Verify the parameters being passed to the AddDbServer interface and target database state, and check the event log for SQL Server errors.

124 Could not find value partition count for container %1. 

Type: Error
Recommended Action: Verify the parameters being passed to the AddDbServer interface and administrative interface call sequence.

List of Microsoft Authentication Service Events

The Authentication Service validates user passwords against the Membership Directory passwords, creates security contexts for access control, and maps groups in the Membership Directory to groups in the Windows NT Server directory database.

0x1001 The Site Server Authentication Service has been started. 

Type: Informational
Recommended Action: No action is required.

0x1002 The Site Server Authentication Service has stopped. 

Type: Informational
Recommended Action: No action is required.

0x1003 The Site Server Authentication Service has started virtual server number %1. 

Type: Informational
Recommended Action: No action is required.

0x1004 The Site Server Authentication Service has stopped virtual server number %1. 

Type: Informational
Recommended Action: No action is required.

0x1005 Authentication could not proceed. Error: %1, virtual server number %2. 

Type: Error
Recommended Action: This event is never logged.

0x1006 The Site Server Authentication Service could not connect to the LDAP server. Error: %1, virtual server number %2. 

Type: Warning
Recommended Action: Check whether the computer running the LDAP Service is up and can be contacted.

0x1007 The Site Server Authentication Service has reconnected to the LDAP server, virtual server number %1. 

Type: Informational
Recommended Action: No action is required.

0x1008 The Site Server Authentication Service has created an NT group named %1 for virtual server number %2. 

Type: Informational
Recommended Action: No action is required.

0x1009 The Site Server Authentication Service could not find the group %1. Error: %2. If this machine is a Backup Domain Controller, please make sure that this group exists on the Primary Domain Controller. Please refer to P&M Operations Guide for more information. 

Type: Informational
Recommended Action: If this computer is a Backup Domain Controller, make sure that this group exists on the Primary Domain Controller. Refer to the P&M Operations Guide for more information.

0x100a The Site Server Authentication Service could not do an LDAP search. Error: %1, virtual server number %2. 

Type: Error
Recommended Action: This error is never logged.

0x100b The Site Server Authentication Service could not do an LDAP bind. Error: %1, virtual server number %2. 

Type: Error
Recommended Action: Check the Authentication service account.

0x100c The Site Server Authentication Service could not do an LDAP add. Error: %1, virtual server number %2. 

Type: Error
Recommended Action: Check the computer running the LDAP Service.

0x100d The Site Server Authentication Service could not do an LDAP add. Error: timeout, virtual server number %1. 

Type: Error
Recommended Action: The computer running the LDAP Service may be overloaded.

0x100e The Site Server Authentication Service blocklisted user %1 on virtual server number %2. 

Type: Informational
Recommended Action: No action is required.

0x100f The Site Server Authentication Service could not create a thread. Error: %1. 

Type: Error
Recommended Action: The Authentication service computer may need more RAM.

0x1010 The Site Server Authentication Service could not create an event. Error: %1. 

Type: Error
Recommended Action: The Authentication service computer may need more RAM.

0x1011 Site Server Authentication Service: The authentication messages received from %1 clients using proxies had incorrect checksums. If this server is one of multiple servers using the same DNS name, then one or more of the servers may have an incorrect Shared Authentication Key. The number of correct authentications using proxies is currently %2. 

Type: Warning
Recommended Action: If this server is one of multiple servers using the same DNS name, then one or more of the servers may have an incorrect Shared Authentication Key.

0x1012 Site Server Authentication Service: The authentication messages received from %1 clients using proxies were delayed. If this server is one of multiple servers using the same DNS name, then one or more of the servers may not be time-synchronized with each other. The number of correct authentications using proxies is currently %2. 

Type: Warning
Recommended Action: If this server is one of multiple servers using the same DNS name, then one or more of the servers may not be time-synchronized with each other.

0x1013 The Site Server Authentication Service impersonation account or password is incorrect. Please make sure that the account exists and that the password specified is correct. If this machine is a Backup Domain Controller, please make sure that this account exists on the Primary Domain Controller. Please refer to P&M Operations Guide for more information. 

Type: Warning
Recommended Action: Make sure that the account exists and that the password specified is correct. If this computer is a Backup Domain Controller, make sure that this account exists on the Primary Domain Controller. Refer to the P&M Operations Guide for more information.

List of Microsoft LDAP Service Events

This service provides a Lightweight Directory Access Protocol (LDAP) interface for industry standard, platform-independent access to the Membership Directory.

396 The evaluation period for this product has expired and could no longer be started. 

Type: Error
Recommended Action: Acquire a release version of the product.

397 LDAP server could not establish SSL channel. 

Type: Error
Recommended Action: Make sure the proper certification is installed correctly.

398 Cannot allocate %1 because there is not enough memory available. 

Type: Error
Recommended Action: Increase memory.

399 Cannot allocate %1 because the preallocated limit has been reached. 

Type: Error
Recommended Action: Increase the maximum number of dynamic objects allowed.

400 LDAP Service cannot initialize its security. 

Type: Error
Recommended Action: Check the Windows NT Server configuration and restart the computer.

401 LDAP Service cannot initialize the socket library. 

Type: Error
Recommended Action: Check the TCP/IP configuration.

402 LDAP Service rejected the connection attempt because there are too many users connected. 

Type: Warning
Recommended Action: Increase the available connections on the General tab of the LDAP Properties dialog box in MMC.

404 LDAP Service cannot open the LDAP/TCP service. The data area, shown below, contains the return error code. 

Type: Error
Recommended Action: No action is required. None.

405 LDAP Service cannot create the main connection socket. The data area contains the return error code. 

Type: Error
Recommended Action: Validate TCP/IP configuration and connectivity.

408 A call to a system service failed unexpectedly. The data area contains the return error code. 

Type: Error
Recommended Action: None.

417 LDAP Service cannot open the LDAP registry key %2. 

Type: Error
Recommended Action: Refresh the installation of the LDAP Service.

418 LDAP Service cannot read registry key %2 

Type: Error
Recommended Action: Refresh the installation of the LDAP Service.

481 The LDAP Service cannot initialize the following object: %1. 

Type: Error
Recommended Action: No action is required.

485 A system call (%1) failed unexpectedly. The data area contains the return error code. 

Type: Warning
Recommended Action: No action is required.

530 LDAP Service has been started. 

Type: Error
Recommended Action: No action is required.

531 LDAP Service has been stopped. 

Type: Informational
Recommended Action: No action is required.

532 LDAP Server instance %1 has been stopped. 

Type: Informational
Recommended Action: No action is required.

533 LDAP Server instance %1 has been paused. 

Type: Informational
Recommended Action: No action is required.

534 LDAP Server instance %1 has been unpaused. 

Type: Informational
Recommended Action: No action is required.

535 LDAP Server instance %1 has been created. 

Type: Informational
Recommended Action: No action is required.

536 LDAP Server instance %1 has been deleted. 

Type: Informational
Recommended Action: No action is required.

2133 The server has detected a previous instance and cannot boot until the old instance goes away. 

Type: Error
Recommended Action: Try to start the service after 120 seconds.

2500 The server failed to startup due to an initialization error. 

Type: Error
Recommended Action: Verify configuration. Consult other log entries. Refresh the installation.

2501 The server failed with a runtime error. 

Type: Error
Recommended Action: Contact Microsoft Technical Support.

2502 LDAP Service: %1. 

Type: Error
Recommended Action: The recommended action is message-dependent.

2600 LDAP Dynamic Replication failed due to an initialization error. 

Type: Error
Recommended Action: Verify configuration.

2601 LDAP Dynamic Replication failed with a runtime error. Error description is: %1. 

Type: Error
Recommended Action: No action is required.

2602 LDAP Dynamic Replication Info: %1. 

Type: Error
Recommended Action: No action is required.

2603 LDAP Dynamic Replication Warning: %1. 

Type: Error
Recommended Action: No action is required.

List of Microsoft LDAP Administration Service Events

The following list enumerates the administration events for the LDAP service.

300 An LDAP Service configuration has not been loaded. 

Type: Error
Recommended Action: Verify configuration. Check the LDAP property page.

301 Could not create Remote DCOM object: %1. 

Type: Error
Recommended Action: No action is required.

302 Could not create DCOM object: %1. 

Type: Error
Recommended Action: No action is required.

303 Could not convert parameter value to string: %1. 

Type: Error
Recommended Action: No action is required.

304 Could not convert parameter value to integer: %1. 

Type: Error
Recommended Action: No action is required.

305 Could not convert parameter value to boolean: %1. 

Type: Error
Recommended Action: No action is required.

306 The given IP address is not supported on the LDAP Service computer. 

Type: Error
Recommended Action: Check the LDAP property page.

307 Port numbers must be above 100. 

Type: Error
Recommended Action: Change the port number to 389 or any other valid port number above 100.

308 The given IP address is not valid. 

Type: Error
Recommended Action: Verify the IP address.

309 Could not initialize Winsock: %1 

Type: Error
Recommended Action: Reinstall Winsock.

310 Could not obtain IP Address from Host Name. 

Type: Error
Recommended Action: Check TCP/IP configuration, DNS configuration, and target host name.

311 The given parameter value must be positive. 

Type: Error
Recommended Action: Validate the referenced parameter.

312 Invalid authorization mode selected. 

Type: Error
Recommended Action: Consult the documentation.

313 Invalid Database type selected. 

Type: Error
Recommended Action: Re-set the database types on the Root Database tab and Directory Properties tab of the LDAP Properties dialog box in MMC.

350 LDAP Administration Failure: %1. 

Type: Error
Recommended Action: No action is required.

400 Could not access configuration database: %1. 

Type: Error
Recommended Action: No action is required.

401 Could not open server configuration information. Server instance may not exist. 

Type: Error
Recommended Action: Recheck the server instance.

402 Failed to write to the configuration database. 

Type: Warning
Recommended Action: No action is required.

404 Could not save configuration changes. 

Type: Error
Recommended Action: No action is required.

405 Could not add new server instance to the configuration database. 

Type: Error
Recommended Action: No action is required.

406 Could not obtain server installation directory: %1 

Type: Error
Recommended Action: No action is required.

407 Could not create default data store: %1 

Type: Error
Recommended Action: No action is required.

408 Could not delete server instance information. Specified instance may not exist. 

Type: Error
Recommended Action: No action is required.

409 Data Store Administration Failure. 

Type: Warning
Recommended Action: No action is required.

410 Could not obtain server host name. 

Type: Error
Recommended Action: Check connectivity and network configuration.

411 Could not resolve server host to obtain IP address. 

Type: Error
Recommended Action: Check connectivity and network configuration.

412 Only Access database can be Compacted/Repaired. 

Type: Error
Recommended Action: No action is required.

413 The Compact/Repair operation has failed. 

Type: Error
Recommended Action: No action is required.

414 Could not replace database with compacted version: %1 

Type: Error
Recommended Action: No action is required.

415 Could not obtain server ID. Specified server instance may not exist. 

Type: Error
Recommended Action: No action is required.

416 Could not obtain server state. Specified server instance may not exist. 

Type: Error
Recommended Action: Recheck the server instance.

List of Microsoft Message Builder Service Events

This service constructs bulk direct mailings using templates and information from the Membership Directory and is capable of updating user data in the Membership Directory.

0x1000 The Site Server Message Builder Service started successfully. 

Type: Success
Recommended Action: No action is required.

0x1001 The Direct Mail List Builder Service stopped successfully. 

Type: Success
Recommended Action: No action is required.

0x1002 The Message Builder Virtual Service %1 started successfully. 

Type: Success
Recommended Action: No action is required.

0x1003 The Message Builder Virtual Service %1 stopped successfully. 

Type: Success
Recommended Action: No action is required.

0x1004 The Message Builder Mailing Receiving ISAPI loaded successfully. 

Type: Success
Recommended Action: No action is required.

0x1005 The Message Builder Mailing Receiving ISAPI unloaded successfully. 

Type: Success
Recommended Action: No action is required.

0x1006 The Mailing "%1" (GUID: %2) is received successfully by instance#:%3 

Type: Success
Recommended Action: No action is required.

0x2000 The volume containing the package repository directory, %1, is full. 

Type: Warning
Recommended Action: Free up some space on the volume (disk) by deleting files.

0x3000 The Message Builder Mailing Receiving ISAPI failed to load. 

Type: Error
Recommended Action: No action is required.

0x3001 Failed to receive the Mailing "%1" (GUID: %2), since a mailing with the same GUID already exists. 

Type: Error
Recommended Action: Delete or restart the package in the error state of the same name ("%1").

0x3002 Failed to write to the hard disk while receiving the Mailing "%1" (GUID: %2). 

Type: Error
Recommended Action: Check authentication methods and ACL settings on Direct Mail ISAPIs, i.e., TMCPMSG.DLL, TMMSGIIS.DLL.

0x3003 Failed to receive the Mailing "%1" (GUID: %2) due to network connection problems. 

Type: Error
Recommended Action: Check the integrity of the network connection between the List Builder and the Message Builder.

0x3004 Failed to receive the Mailing "%1" (GUID: %2) due to internal errors. 

Type: Error
Recommended Action: No action is required.

0x4000 Failed to connect to the directory server %1. 

Type: Error
Recommended Action: Check directory server, DataStore (DS) account/password, and network connectivity between message builder and directory server.

0x4001 Failed to connect to the SMTP server %1. 

Type: Error
Recommended Action: Check the status of the computer running the SMTP Service, and network connectivity between Message Builder and the computer running the SMTP Service.

0x4002 Failed to connect to the POP3 server %1. Check POP3 server and network connectivity between message builder and POP3 server. 

Type: Error
Recommended Action: Check the computer running the SMTP service and network connectivity between Message Builder and the computer running the SMTP service. This message will never be seen, because POP3 support was disabled in the product.

0x4003 The message builder encountered an error while creating message for task %1. If recurring, check web server and DS. 

Type: Error
Recommended Action: Check the operating status of the web server and DS and the network connectivity between each.

0x4004 Entry could not be added to transaction log. 

Type: Error
Recommended Action: Check to see whether the transaction log file system is full.

0x4005 Transaction log could not be opened. 

Type: Error
Recommended Action: Check to see whether the transaction log file system is full.

0x4006 Failed to install service handler. 

Type: Error
Recommended Action: No action is required.

0x4007 Service Handler received a bad request. It is ignored. 

Type: Error
Recommended Action: No action is required.

0x4008 The Message Builder Service failed to start properly. 

Type: Error
Recommended Action: Check to see if the Message Builder service is installed.

0x4009 Mailing "%1" completed. %2 out of %3 messages have been successfully processed (%5 have been successfully sent). Time started: %4. 

Type: Informational
Recommended Action: No action is required.

0x400A Mailing "%1" completed with errors. %2 out of %3 messages have been processed (%9 have been successfully sent). %4 messages failed due to errors in retrieving or processing template. %5 messages failed due to errors in retrieving attachments. %6 messages failed due to other errors. See Logs (%7) for details of errors. Time started: %8. 

Type: Error
Recommended Action: For "%4 messages failed due to errors in retrieving or processing template" and "%5 messages failed due to errors in retrieving attachments," check the status of the web server, the existence and security of the specified URL, and check the Direct Mail log file for the specific error code.Check the specified Direct Mail log file for additional error information.

0x400B Mailing "%1" stopped. %2 out of %3 messages have been successfully processed (%5 have been successfully sent). Time started: %4. 

Type: Informational
Recommended Action: No action is required.

0x400C Mailing "%1" stopped with errors. %2 out of %3 messages have been processed (%9 have been successfully sent). %4 messages failed due to errors in retrieving or processing template. %5 messages failed due to errors in retrieving attachments. %6 messages failed due to other errors. See Logs (%7) for details of errors. Time started: %8. 

Type: Error
Recommended Action: For "%4 messages failed due to errors in retrieving or processing template" and "%5 messages failed due to errors in retrieving attachments," check the status of the web server, the existence and security of the specified URL, and check the Direct Mail log file for the specific error code.Check the specified Direct Mail log file for additional error info.

0x400D Mailing "%1" cancelled. %2 out of %3 messages have been successfully processed (%5 have been successfully sent). Time started: %4. 

Type: Informational
Recommended Action: No action is required.

0x400E Mailing "%1" cancelled with errors. %2 out of %3 messages have been processed (%9 have been successfully sent). %4 messages failed due to errors in retrieving or processing template. %5 messages failed due to errors in retrieving attachments. %6 messages failed due to other errors. See Logs (%7) for details of errors. Time started: %8. 

Type: Error
Recommended Action: For "%4 messages failed due to errors in retrieving or processing template" and "%5 messages failed due to errors in retrieving attachments," check the status of the web server, the existence and security of the specified URL, and check the Direct Mail log file for the specific error code.Check the specified Direct Mail log file for additional error info.

0x400F Mailing "%1" failed due to various errors. %2 out of %3 messages have been processed (%9 have been successfully sent). %4 messages failed due to errors in retrieving or processing template. %5 messages failed due to errors in retrieving attachments. %6 messages failed due to other errors. See Logs (%7) for details of errors. Time started: %8. 

Type: Error
Recommended Action: For "%4 messages failed due to errors in retrieving or processing template" and "%5 messages failed due to errors in retrieving attachments," check the status of the web server, the existence and security of the specified URL, and check the Direct Mail log file for the specific error code.Check the specified Direct Mail log file for additional error info.

0x4010 Mailing "%1" failed since mail server is not available. %2 out of %3 messages have been processed (%9 have been successfully sent). %4 messages failed due to errors in retrieving or processing template. %5 messages failed due to errors in retrieving attachments. %6 messages failed due to other errors. See Logs (%7) for details of errors. Time started: %8. 

Type: Error
Recommended Action: Check the status of the computer running the SMTP service and the network connection between the computer running the SMTP serviceand the Message Builder Service.For "%4 messages failed due to errors in retrieving or processing template" and "%5 messages failed due to errors in retrieving attachments," check the status of the web server, the existence and security of the specified URL, and check the Direct Mail log file for the specific error code.Check the specified Direct Mail log file for additional error info.

0x4011 Mailing "%1" failed since DS is not available. %2 out of %3 messages have been processed (%9 have been successfully sent). %4 messages failed due to errors in retrieving or processing template. %5 messages failed due to errors in retrieving attachments. %6 messages failed due to other errors. See Logs (%7) for details of errors. Time started: %8. 

Type: Error
Recommended Action: Check the status of the computer running the Membership Directory Service server and the network connection between the computer running the Membership Directory service and the Message Builder service.For "%4 messages failed due to errors in retrieving or processing template" and "%5 messages failed due to errors in retrieving attachments," check the status of the web server, the existence and security of the specified URL, and check the Direct Mail log file for the specific error code.Check the specified Direct Mail log file for additional error info.

0x4012 Mailing "%1" failed due to internal errors in message builder, such as out of memory. %2 out of %3 messages have been processed (%9 have been successfully sent). %4 messages failed due to errors in retrieving or processing template. %5 messages failed due to errors in retrieving attachments. %6 messages failed due to other errors. See Logs (%7) for details of errors. Time started: %8. 

Type: Error
Recommended Action: For "%4 messages failed due to errors in retrieving or processing template" and "%5 messages failed due to errors in retrieving attachments," check the status of the web server, the existence and security of the specified URL, and check the Direct Mail log file for the specific error code.Check the specified Direct Mail log file for additional error info.

0x4013 Mailing "%1" failed due to internal errors in message builder, such as out of memory. 

Type: Error
Recommended Action: Check the memory available on the computer and increase it, if necessary.

0x4014 Mailing "%1" failed due to failure in resolving distribution lists. Please check directory server, DS account/password, and network connectivity between message builder and directory server. 

Type: Error
Recommended Action: Check the computer running the Membership Directory Service, the DS account/password, and network connectivity between the computer running the Message Builder service and Membership Directory service.

0x4015 Message builder runs out of memory. Close other applications. If the problem persists, restart the Message Builder service. 

Type: Error
Recommended Action: Close other applications. If the problem persists, restart the Message Builder service.

0x4016 Message Builder failed in moving Mailing "%1" file into the package process queue, because a Mailing file with the same name already exists. 

Type: Error
Recommended Action: No action is required.

0x4017 Message Builder hit some error conditions when recovering packages left in the package process queue. 

Type: Error
Recommended Action: No action is required.

0x4018 Mailing "%1" is left from last service run. %2 out of %3 messages have been successfully processed (%6 have been successfully sent). See Logs (%4) for details of errors. Time started: %5. 

Type: Error
Recommended Action: Restart the mailings the user wants to finish processing or delete the mailing.

0x4019 Restart the mailings the user wants to finish processing or simply delete the mailing. 

Type: Error
Recommended Action: No action is required.

0x401A Message Builder failed to make %1 connections to %2 HTTP server. 

Type: Error
Recommended Action: Check the status of the web server and the network connection between the web server and the computer running the Message Builder service.

0x401B Mimeole components have not been registered properly. No mailings can be handled. 

Type: Error
Recommended Action: Check the installation and restart the computer.

0x401D Mailing "%1" failed since #%2 virtual instance of Message Builder is not available.%n 

Type: Error
Recommended Action: Restart the web service and Message Builder service.

0x401E Mailing "%1" failed since no valid email addresses are found from the given mail aliases (aka Distribution List). 

Type: Error
Recommended Action: The problem could also be related to Membership Directory service configurations.

0x401F Mailing "%1" (GUID: %2) has an invalid mail alias (aka Distribution List): %3. %n 

Type: Error
Recommended Action: No action is required.

0x4020 Message Builder is aborted due to failure in initializing Mimeole components. 

Type: Error
Recommended Action: Reinstall the Message Builder service.

0x4021 Message Builder failed in waiting for flow control rate (messages/second) changes. 

Type: Error
Recommended Action: This product behavior was removed from the product, so the user should never encounter this error message.

0x4022 Message Builder failed in sending status mail to %2 for Mailing %1. 

Type: Error
Recommended Action: Verify that the e-mail address is correct.Verify that the SMTP server is operating correctly.

0x4023 The mailing "%1" (GUID: %2) is denied, since the virtual instance for the mailing (#%3) does not exist. 

Type: Error
Recommended Action: Restart the web service and Message Builder service.

0x4024 The mailing "%1" (GUID: %2) is denied, since the virtual instance for the mailing (#%3) has not been started. 

Type: Error
Recommended Action: Restart the web service and Message Builder service.

0x4025 Message Builder failed in resolving distribution lists for the mailing "%1" (GUID: %2), the error code is: %3. 

Type: Error
Recommended Action: Check the status of the computer running the Membership Directory service and whether the distribution list exists.

0x4026 Message Builder failed because account registry keys are missing. 

Type: Error
Recommended Action: Reinstall Microsoft® Site Server 3.0.

0x4027 Message Builder failed to read settings from metabasei, service couldn't start. 

Type: Error
Recommended Action: Reinstall Direct Mail.

0x4028 Message Builder ran out of disk space while resolving distribution lists for the mailing "%1" (GUID: %2). 

Type: Error
Recommended Action: Free up disk space.

0x4029 Message Builder ran out of disk space while processing the mailing "%1" (GUID: %2). 

Type: Error
Recommended Action: Free up disk space.

0x402A Message Builder ran into an unknown disk write error while processing the mailing "%1" (GUID: %2). 

Type: Error
Recommended Action: No action is required.

0x402B Mailing "%1" failed since mime encoding failed. %2 out of %3 messages have been processed (%9 have been successfully sent). %4 messages failed due to errors in retrieving or processing template. %5 messages failed due to errors in retrieving attachments. %6 messages failed due to other errors. See Logs (%7) for details of errors. Time started: %8. 

Type: Error
Recommended Action: No action is required.

0x402C Failed to retrieve Web Site mapping information for the mailing "%1" (GUID: %2). Use #1 instance as default. 

Type: Error
Recommended Action: No action is required.