Event ID 3152 — DNS Server Service Status

Event ID 3152 — DNS Server Service Status

Updated: November 13, 2007

Applies To: Windows Server 2008

The DNS Server service responds to requests from DNS client computers for name resolution services. Domain Name System (DNS) is a protocol that enables a computer to obtain the numeric IP address of another computer by submitting the target computer’s name to a DNS server. Problems with the DNS Server service can cause network performance to degrade or even prevent network computers from being able to locate each other.

Event Details

Product: Windows Operating System
ID: 3152
Source: Microsoft-Windows-DNS-Server-Service
Version: 6.0
Symbolic Name: DNS_EVENT_FILE_NOT_OPENED_FOR_WRITE
Message: The DNS server was unable to open file %1 for write. Most likely the file is a zone file that is already open. Close the zone file and re-initiate zone write.

Resolve
Close the open file

Close the locked open file, and then try the operation again. To close the locked file, close any applications that might be using the file, and then try the operation again.

If it is not possible to determine which process holds the lock, or to force the process to release the lock, restart the computer to release the lock.

To perform this procedure, you must have membership in Administrators, or you must have been delegated the appropriate authority.

To restart the computer:

  • Click Start, click the arrow next to the Lock button, and then click Restart.

To verify that the DNS Server service has started:

  1. On the DNS server, start Server Manager.
  2. In the console tree, expand Roles, and then click DNS Server.

The System Services list shows the state of the DNS Server service.

Verify

To verify that the DNS Server service is running properly, ensure that the DNS Server event log contains Event ID 2 and that the event log does not contain the following Domain Name System (DNS) error events:

  • 111
  • 403-407
  • 1001
  • 3151-3153
  • 6533
  • 7502-7504

Related Management Information

DNS Server Service Status

DNS Infrastructure

Related:

An internal MTA error occurred: transfer out failure. Object ID: id. Entity name: object name. [valuevaluevaluevalue] (14)

Details
Product: Exchange
Event ID: 3152
Source: MSExchangeMTA
Version: 6.5.0000.0
Message: An internal MTA error occurred: transfer out failure. Object ID: id. Entity name: object name. [valuevaluevaluevalue] (14)
   
Explanation
The message transfer agent (MTA) database may be corrupted.
   
User Action
Stop and restart the MTA service. If the error persists, run the Mtacheck.exe utility. Stop the MTA service, open a command prompt, and type Mtacheck/v /f c:\mta.txt.

If Mtacheck removes objects from a database queue, it places each damaged object in a Db*.dat file in \Exchsrvr\Mtadata\Mtacheck.out. Check your drives and verify that core *.dat files are in the \Exchsrvr\Mtadata directories. The \Exchsrvr\Mtadata directory with *.dat files may be on more than one drive. Contact Microsoft Product Support Services for assistance.

Related:

An internal MTA error occurred: transfer out failure. Object ID: . Entity name: . [ ] (14)

Details
Product: Exchange
Event ID: 3152
Source: MSExchangeMTA
Version: 6.5.6940.0
Component: Microsoft Exchange Message Transfer Agent
Message: An internal MTA error occurred: transfer out failure. Object ID: <id>. Entity name: <object name>. [<value> <value> <value> <value>] (14)
   
Explanation

The message transfer agent (MTA) database may be corrupted.

   
User Action

Stop and restart the MTA service. If the error persists, run the Mtacheck.exe utility. Stop the MTA service, open a command prompt, and type Mtacheck/v /f c:\mta.txt.

If Mtacheck removes objects from a database queue, it places each damaged object in a Db*.dat file in \Exchsrvr\Mtadata\Mtacheck.out. Check your drives and verify that core *.dat files are in the \Exchsrvr\Mtadata directories. The \Exchsrvr\Mtadata directory with *.dat files may be on more than one drive. Contact Microsoft Product Support Services for assistance.

Related:

An internal MTA error occurred: transfer out failure. Object ID: {id}. Entity name: {object name}. [{value}{value}{value}{value}] (14)

Details
Product: Exchange
Event ID: 3152
Source: MSExchangeMTA
Version: 6.0
Component: Message Transfer Agent
Symbolic Name: MTA03152
Message: An internal MTA error occurred: transfer out failure. Object ID: {id}. Entity name: {object name}. [{value}{value}{value}{value}] (14)
   
Explanation
The message transfer agent (MTA) database may be corrupted.
   
User Action
Stop and restart the MTA service. If the error persists, run the Mtacheck.exe utility. Stop the MTA service, open a command prompt, and type Mtacheck/v /f c:\mta.txt. If Mtacheck removes objects from a database queue, it places each damaged object in a Db*.dat file in \Exchsrvr\Mtadata\Mtacheck.out. Check your drives and verify that core *.dat files are in the \Exchsrvr\Mtadata directories. The \Exchsrvr\Mtadata directory with *.dat files may be on more than one drive. Contact Microsoft Product Support Services for assistance.

Related:

The DNS server was unable to open file %1 for write. Most likely the file is a zone file that is already open. Close the zone file and re-initiate zone write.

Details
Product: Windows Operating System
Event ID: 3152
Source: DNS
Version: 5.0
Symbolic Name: DNS_EVENT_FILE_NOT_OPENED_FOR_WRITE
Message: The DNS server was unable to open file %1 for write. Most likely the file is a zone file that is already open. Close the zone file and re-initiate zone write.
   
Explanation

You might not have permission to access this file.

   
User Action

Check the permissions on the specified file:

1) In Windows Explorer, go to the Systemroot\System32\Dns folder.
2) Right-click the specified database file, and then click Properties.
3) Click the Security tab, and then click Permissions.
4) Verify that you have the proper permissions to read, write, and then run the file.

Related: