Ntds General Error 1228

Analyzer Sample report Advanced filtering Direct links to www.eventid.net Email notifications Scheduled reporting Free for subscribers EventReader Event Viewer Sample report Custom views/filters Servers list, organized in groups Integration with EventID.Net Consolidated view for all logs Free for subscribers Event ID: 1228 Source: NTDS General Source: NTDS General Type: Error Description:System Monitor was unable to open Active Directory performance counters. An attempt to query the following performance counter registry key failed. Registry key: SYSTEM\CurrentControlSet\Services\NTDS\Performance\First Counter Additional Data Error value: 2 The system cannot find the file specified. English: Request a translation of the event description in plain English. Comments: EventID.Net From a newsgroup post: "To reload the NTDS extensible counter (one that is not installed by default on a Windows 2000 installation, since NTDS is installed during promotion to a DC) perform the following steps: 1. Open a command prompt window. 2. At the command prompt, enter "cd %Systemroot%\System32" 3. Enter the following line: "lodctr ntdsctrs.ini" Refer to KB article ME300956 for this and more info on rebuilding performance counters". Verify that the registry key exists. x 9 Private comment: Subscribers only. See example of private comment Links: ME300956 Search: Google - Bing - Microsoft - Yahoo - EventID.Net Queue (0) - More links... Feedback: Send comments or solutions - Notify me when updated Printer friendly Subscribe Subscribe to EventID.Net now!Already a subscriber? Login here! Recommend Us Quick Tip Connect to EventID.Net directly from the Microsoft Event Viewer!Instructions Customer services Contact usSupportTerms of Use Help & FAQ Sales FAQEventID.Net FAQ Advertise with us Articles Managing logsRecommended booksNewsletter Links Follow us on FacebookFiregen Log Analyzers Link to us © Copyright 2001-2016 EventID.Net

was unable to open Active Directory http://www.wincert.net/microsoft-windows/windows-7/ntds-general-error-1173/ performance counters. An attempt to query the following performance counter registry key failed.Registry key:SYSTEM\CurrentControlSet\Services\NTDS\Performance\First CounterAdditional DataError value:2 The system cannot find the file specified.Following DWORD ntds general values may be missing:First Counter, First Help, Last Counter, and Last HelpTo correct this issue, under the same key, locate the string "PerfIniFile" and copy the file name listed.Open the command line ntds general error and type: LODCTR [filename] at 6:21 AM 1 comment: lee wooDecember 21, 2015 at 10:21 PMIt is impossible to live without failing at something, unless you live so cautiously that you might as well not have lived at all, in which case you have failed by default. See the link below for more info. #failed www.ufgop.orgReplyDeleteAdd commentLoad more... Older Post Home Subscribe to: Post Comments (Atom) Droves Blog Archive ▼ 2009 (9) ▼ October (1) System Monitor was unable to open Active Directory... ► September (1) ► July (2) ► May (5)

0 NTDS General error 1173 by Nik · Published October 28, 2009 · Updated February 20, 2015 If you're getting this error in the event log "NTDS General error 1173" on domain controllers followed by Internal event: Active Directory has encountered the following exception and associated parameters. Exception: e0010004 Parameter: 0 Additional Data Error value: -1603 Internal ID: 2050344 You are probably having replication issues, here's what you should do: Run the following repadmin command on the primary domain controller (PDC) to create a .csv file that contains the list of destination domain controllers: repadmin /showrepl * /csv >showrepl.csv Open the .csv file in Microsoft Excel, and then identify replication failures on destination domain controllers that have failed the incoming replication process and that display Win32 error 8451. On the domain controllers that log the "Win32 error 8451" error message, make sure that diagnostic logging for the 5 Replication Events registry entry is set to a value of 1. To do this, follow these steps: Click Start, and then click Run. In the Open box, type regedit, and then click OK. Locate and then click the following registry key: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\NTDS\Diagnostics In the details pane, double-click 5 Replication Events, type 1 in the Value data box, and then click OK. Close Registry Editor. On the destination domain controllers, verify that Directory Service event 1692 is logged in the Directory Service log. The event displays changes to the “member” attribute of the security group or to other LVR-replicated attributes and to the lingering object GUIDs. Remove the lingering objects from the Windows Server 2008-based or Windows Server 2003-based destination domain controllers by using the repadmin /removelingeringobjects command. For more information about the Repadmin /removelingeringobjects command, click the following article number to view the article in the Microsoft Knowledge Base: Disabling strict replication consistency functionality in the registry of Windows Server 2008-based or Windows Server 2003-based destination domain controllers does not resume replication. You must not set the value of the Strict Replication Consistency registry entry to 0 to unblock replication of directory partitions. Do not force replication of directory partitions on source domain controllers by using the repadmin /sync command or an