NTBackup error: ‘%1’

Details
Product: Windows Operating System
Event ID: 8017
Source: ntbackup
Version: 5.2
Symbolic Name: EVENT_BKUP_BACKUPSTATUS_ERROR
Message: NTBackup error: ‘%1’
   
Explanation

Backup could not archive the data that you requested. This event provides general information about the type of problem that occurred.

   
User Action

No user action is required unless it is stated in the event message.

Related:

A request has been submitted to promote the computer to backup when it is already a master browser.

Details
Product: Windows Operating System
Event ID: 8004
Source: mrxsmb
Version: 5.2
Symbolic Name: EVENT_BOWSER_PROMOTED_WHILE_ALREADY_MASTER
Message: A request has been submitted to promote the computer to backup when it is already a
master browser.
   
Explanation

The master browser for My Network Places failed, and the browser service tried to promote a backup computer to be the master browser; however, the backup computer was already designated as a master browser.

Multiple master browsers could be the result of a previous network problem. The computer browser service will establish the correct master browser automatically.

   
User Action

No user action is required.

Related:

End Backup of ‘%1’ ‘%2’ Verify: %3 Mode: %4 Type: %5 Consult the backup report for more details.

Details
Product: Windows Operating System
Event ID: 8001
Source: ntbackup
Version: 5.2
Symbolic Name: EVENT_BKUP_ENDBACKUP
Message: End Backup of ‘%1’ ‘%2’
Verify: %3
Mode: %4
Type: %5
Consult the backup report for more details.
   
Explanation

The specified backup operation is completed. One End Backup event for each backup type is created during a backup operation. For example, two End Backup events appear if you started a backup of your C: drive and System State.

   
User Action

No user action is required.

Related:

The %1 service was successfully sent a %2 control.

Details
Product: Windows Operating System
Event ID: 7035
Source: Service Control Manager
Version: 5.2
Symbolic Name: EVENT_SERVICE_CONTROL_SUCCESS
Message: The %1 service was successfully sent a %2 control.
   
Explanation

A control code was correctly sent to the service. This message is logged for informational purposes only.

   
User Action

No user action is required.

Related:

The %1 service depends on the following nonexistent service: %2

Details
Product: Windows Operating System
Event ID: 7003
Source: Service Control Manager
Version: 5.2
Symbolic Name: EVENT_SERVICE_START_FAILED_NONE
Message: The %1 service depends on the following nonexistent service: %2
   
Explanation

The service first specified is configured to require a service that is not installed or is configured incorrectly.

   
User Action

To determine what the problem with the second service is, do one or all of the following:

  • Verify that the required service is installed.
  • Verify that the service is configured correctly.
  • Verify that the required service has been specified correctly.

Related:

DNS server has updated its own host (A) records. In order to ensure that its DS-integrated peer DNS servers are able to replicate with this server, an attempt was made to update them with the new records through dynamic update. An error was encountered during this update, the record data is the error code. If this DNS server does not have any DS-integrated peers, then this error should be ignored. If this DNS server’s Active Directory replication partners do not have the correct IP address(es) for this server, they will be unable to replicate with it. To ensure proper replication: 1) Find this server’s Active Directory replication partners that run the DNS server. 2) Open DnsManager and connect in turn to each of the replication partners. 3) On each server, check the host (A record) registration for THIS server. 4) Delete any A records that do NOT correspond to IP addresses of this server. 5) If there are no A records for this server, add at least one A record corresponding to an address on this server, that the replication partner can contact. (In other words, if there multiple IP addresses for this DNS server, add at least one that is on the same network as the Active Directory DNS server you are updating.) 6) Note, that is not necessary to update EVERY replication partner. It is only necessary that the records are fixed up on enough replication partners so that every server that replicates with this server will receive (through replication) the new data.

Details
Product: Windows Operating System
Event ID: 6702
Source: DNS
Version: 5.2
Symbolic Name: DNS_EVENT_UPDATE_DS_PEERS_FAILURE
Message: DNS server has updated its own host (A) records. In order to ensure that its
DS-integrated peer DNS servers are able to replicate with this server, an attempt
was made to update them with the new records through dynamic update. An error
was encountered during this update, the record data is the error code.

If this DNS server does not have any DS-integrated peers, then this error
should be ignored.

If this DNS server’s Active Directory replication partners do not have the
correct IP address(es) for this server, they will be unable to replicate with it.

To ensure proper replication:
1) Find this server’s Active Directory replication partners that run the DNS
server.
2) Open DnsManager and connect in turn to each of the replication partners.
3) On each server, check the host (A record) registration for THIS server.
4) Delete any A records that do NOT correspond to IP addresses of this server.
5) If there are no A records for this server, add at least one A record
corresponding to an address on this server, that the replication partner can
contact. (In other words, if there multiple IP addresses for this DNS server,
add at least one that is on the same network as the Active Directory DNS server
you are updating.)
6) Note, that is not necessary to update EVERY replication partner. It is
only necessary that the records are fixed up on enough replication partners so
that every server that replicates with this server will receive (through
replication) the new data.

   
Explanation

Active Directory clients use DNS to locate domain controllers for administration and logon. A domain controller usually points to itself for DNS. When there are additional domain controllers in the domain, they must point to the first domain controller (called the DNS server in this message) that was installed in the domain and then to themselves as secondary. This server could not register its dynamically updated locator records with DNS on any other domain controller in its directory service (DS) forest.

Possible causes include:

  • There are no other domain controllers.
  • The other domain controllers in this forest do not have the correct IP address for this server.
   
User Action

If there are no other domain controllers in this forest, no user action is required.

If there are other domain controllers that are Active Directory replication partners in this forest, enable replication by ensuring that at least one correct DNS record is registered on each domain controller.

To ensure that a correct DNS record is registered on each domain controller

  • Find this server’s Active Directory replication partners that run DNS.
  • Open DNSManager and connect in turn to each of these replication partners.
  • Find the host (A) resource record registration for this server on each of the other replication partner domain controllers.
  • Delete those host (A) records that do not have IP addresses corresponding to any of this server’s IP addresses.
  • If a domain controller has no host (A) records for this server, add at least one that corresponds to an IP address on this server. (If there are multiple IP addresses for this server, add at least one that is on the same network as the domain controller you are updating.)

It is not necessary to update every replication partner. It is only necessary that the host (A) records be working on enough replication partners so that every domain controller that replicates with this server receives new data through replication.

For more information about DNS and DNS troubleshooting procedures, see
Domain Name System(DNS)Center.

Related:

The master browser has received a server announcement from the computer %2 that believes that it is the master browser for the domain on transport %3. The master browser is stopping or an election is being forced.

Details
Product: Windows Operating System
Event ID: 8003
Source: mrxsmb
Version: 5.2
Symbolic Name: EVENT_BOWSER_OTHER_MASTER_ON_NET
Message: The master browser has received a server announcement from the computer %2
that believes that it is the master browser for the domain on transport %3.
The master browser is stopping or an election is being forced.
   
Explanation

This computer is a master browser, and another computer has announced that it is the master browser. There can be only one master browser on a subnet at any given time. This message is logged for informational purposes only.

The existence of two browser masters occurs when a second computer cannot contact the master browser for some reason: for example, when there are name resolution problems or the master browser is too busy to respond. When the original master browser receives a master announcement from the second computer, the master browser tries to resolve the conflict by ending its status as a master server, forcing an election, or both.

The choice of these actions depends on the status of the two computers: for example, whether one or both are domain controllers, primary domain controllers or Windows for Workgroups computers, and whether this computer lost an election earlier. For more information about browsing, see Appendix I: Windows 2000 Server Browser Service on the Microsoft Technet Web site.

   
User Action

No user action is required.

Related:

Site ‘%2’ does not have any LDAP servers for non-domain NC ‘%3’. LDAP servers in site ‘%1’ have been automatically selected to cover site ‘%2’ for non-domain NC ‘%3’ based on configured Directory Server replication costs.

Details
Product: Windows Operating System
Event ID: 5792
Source: NetLogon
Version: 5.2
Symbolic Name: NELOG_NetlogonNdncSiteCovered
Message: Site ‘%2’ does not have any LDAP servers for non-domain NC ‘%3’. LDAP servers in site ‘%1’ have been automatically selected to cover site ‘%2’ for non-domain NC ‘%3’ based on configured Directory Server replication costs.
   
Explanation

No LDAP servers are available for the non-domain network computer; therefore, LDAP servers from another site have been automatically assigned the task of managing non-domain NC traffic for this site.

   
User Action

No user action is required. Servers have been automatically selected to cover the site. If you do not want these LDAP servers to cover the site, use the Sites and Subnet snap-in to configure them.

Related:

WMI ADAP was unable to create object index %1 for Performance Library %2 because no value was found in the 009 subkey

Details
Product: Windows Operating System
Event ID: 41
Source: WinMgmt
Version: 5.2
Symbolic Name: WBEM_MC_ADAP_MISSING_OBJECT_INDEX
Message: WMI ADAP was unable to create object index %1 for Performance Library %2 because no value was found in the 009 subkey
   
Explanation

Windows Management Instrumentation (WMI) could not locate the specified object because it was not listed in the registry key. The Performance Monitor object and counter names are stored in the Counters section of the following registry key:
HKEY LOCAL MACHINE\Software\Microsoft\WindowsNT\ CurrentVersion\Perflib\ (Lang ID 009 = U.S. English)

To prevent this error, the indicated performance counter has to be listed here.

   
User Action

  1. At the command prompt, typewinmgmt /clearadap
  2. At the command prompt, typewinmgmt /resyncperf winmgmt service pid To find the winmgmt service pid, in Task Manager, click the Processes tab and note the image name displayed.

If this error persists, it might be caused by a slow startup. To prevent this, add a DWORD key Collect Timeout with value 10000 to HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\\Performance.

Related:

WMI ADAP was unable to retrieve data from the PerfLib subkey: %1, error code: %2

Details
Product: Windows Operating System
Event ID: 47
Source: WinMgmt
Version: 5.2
Symbolic Name: WBEM_MC_ADAP_PERFLIB_REG_VALUE_FAILURE
Message: WMI ADAP was unable to retrieve data from the PerfLib subkey: %1, error code: %2
   
Explanation

This is not a performance library error but may indicate other problems, such as missing performance counter classes in Windows Management Instrumentation (WMI).

The AutoDiscovery/AutoPurge (ADAP) process transfers performance libraries to the WMI repository.

ADAP runs as a separate process in Wmiadap.exe when the user:

  • Restarts the operating system or runs the net stop and net start commands.
  • Runs the lodctr or unlodctr utilities.
  • Runs the Wmiadap.exe /resyncperf command.

ADAP also runs when a new Windows Driver Model (WDM) -enabled driver is added or removed.

Depending on the switches, running Wmiadap.exe can transfer all performance libraries or WDM drivers. For information on the command switches for ADAP, see the MSDN article wmiadap.

For information on how ADAP parses the performance libraries and the meaning of performance library status values such as -1, see the MSDN articles Parsing the Performance Libraries and Changing the Status of a Performance Library.

   
User Action

ADAP marks a library by setting the WbemADAPStatus registry value to -1 in the performance subkey of the service. ADAP then ignores the library until the file size and date of the library change or someone re-enables the library, at which time ADAP attempts to load the library.

In some cases, a valid performance library may be incorrectly marked as disabled. You can manually re-enable a performance library by using the /clearadap command-line switch with the winmgmt utility. For more information, see the MSDN article winmgmt.

ADAP logs events for libraries that time out or whose WbemADAPStatus value is set to -1. For details on how to view ADAP errors in Event Viewer, see MSDN article Viewing ADAP Errors.

Related: