Ntds General Error 1136

(עברית)المملكة العربية السعودية (العربية)ไทย (ไทย)대한민국 (한국어)中华人民共和国 (中文)台灣 (中文)日本 (日本語)  HomeOnline20132010Other VersionsRelated ProductsLibraryForumsGallery Ask a question Quick access Forums home Browse forums users FAQ Search related threads Remove From My Forums Answered by: NTDS Error 1136 on Windows 2003 DC's after 2012 R2 Schema Extensions Windows Server > Directory Services Question 0 Sign in to vote Guys, Hoping someone can help me out on this one, currently working on Windows 2003 to 2012 R2 upgrade and have extended the schema for Windows 2012 and added my first DC to the domain without issue. When looking at the Directory Services logs in Event viewer on the Windows 2003 DC's I see that an NTDS error 1136 is being logged every 5 minutes. The issue is very similar to http://support.microsoft.com/kb/932862but the attribute that is throwing the error is msTPM-SrkPubThumbprint rather than those listed in this. I am assuming this is akin to the attributes in the article in that the Win 2K3 servers just do not support this. I have trawled the net to try and find a workaround similar to that in the article but have found nothing of use. There are 2 Windows 2003Domain Controllers in the environment and these need tobe retained in the short term but these errors are a pain that I would like to dispense of. Anybody got any ideas? Thanks in advance, Mark Friday, March 28, 2014 12:55 AM Reply | Quote Answers 0 Sign in to vote Hi, tried disabling the indexing for that attribute? CK Proposed as answer by CanKILIC Wednesday, April 02, 2014 7:02 PM Marked as answer by Amy Wang_Microsoft contingent staff, Moderator Monday, April 07, 2014 3:41 AM Friday, March 28, 2014 1:29 AM Reply | Quote 0 Sign in to vote Hi Mark, Have you tried CK�

Active Directory failed to create an index for the following attribute. Attribute identifier: 591789 Attribute name: msFVE-RecoveryGuid A schema cache update will occur 5 minutes after the logging of this event and will attempt to create an index for the attribute. Additional Data Error value: -1403 JET_errIndexDuplicate, Index is already defined After a bit of extensive searching I discovered that one of our Domain Admins had done a Schema update on https://social.technet.microsoft.com/Forums/sharepoint/en-US/f1e8eeb2-4697-41c5-a47d-b664fc8af36e/ntds-error-1136-on-windows-2003-dcs-after-2012-r2-schema-extensions?forum=winserverDS the forest to add BitLocker Drive encryption. BitLocker Drive encryption is not supported on a 2003 domain and this is what's causing the problems. Below is the solution on how to fix these errors: To work around this problem, you must determine which domain controller is the schema operations master, and then remove the https://wearethechosen.wordpress.com/2010/04/21/ntds-1136-errors-on-domain-controllers/ containerized index for the msFVE-VolumeGuid schema object and for the msFVE-RecoveryGuid schema object. To do this, follow these steps: On a domain controller, click Start, click Run, type cmd, and then click OK. To determine which domain controller is the schema operations master, type the following command at the command prompt, and then press ENTER: netdom query fsmo Log on to the domain controller that is hosting the schema operations master role by using an account that is a member of the Schema Admins security group. Note By default, the built-in Administrator account in the root domain of the forest is a member of the Schema Admins group. Click Start, click Run, type adsiedit.msc, and then click OK. Note The ADSIEdit Microsoft Management Console (MMC) snap-in is included in the Windows Support Tools for Windows Server 2003. To download the Windows Support Tools for Windows Server 2003 with Service Pack 1, visit the following Microsoft Web site: http://go.microsoft.com/fwlink/?LinkID=70775 (http://g

for Help Receive Real-Time Help Create a Freelance Project Hire for a Full Time Job Ways to Get Help Ask a Question Ask for Help Receive Real-Time https://www.experts-exchange.com/questions/24897400/NTDS-General-1136-error-in-windows-log-after-upgrade-the-shema-ad-with-the-exchange-2007-sp2.html Help Create a Freelance Project Hire for a Full Time Job Ways to Get Help Expand Search Submit Close Search Login Join Today Products BackProducts Gigs Live Careers http://www.open-a-socket.com/index.php/2009/01/23/error-event-1136-following-windows-server-2008-forestprep/ Vendor Services Groups Website Testing Store Headlines Experts Exchange > Questions > NTDS General 1136 error in windows log after upgrade the shema ad with the exchange 2007 ntds general sp2 Want to Advertise Here? Solved NTDS General 1136 error in windows log after upgrade the shema ad with the exchange 2007 sp2 Posted on 2009-11-13 Exchange Active Directory Windows Server 2003 1 Verified Solution 6 Comments 3,916 Views Last Modified: 2012-05-08 I got the error bellow with different attribut identifer after a upgrade the shema of ntds general error my active directory with the setup /prep... command. What I can do for reslove that? It's append every five minutes.... I also tried to upgrade the shema with windows 2008 server shema without success.... Thanks for your help Event Type: Error Event Source: NTDS General Event Category: DS Schema Event ID: 1136 Date: 13.11.2009 Time: 14:00:04 User: NT AUTHORITY\ANONYMOUS LOGON Computer: MESSINE Description: Active Directory failed to create an index for the following attribute. Attribute identifier: 2215993406 Attribute name: msExchRoleEntries A schema cache update will occur 5 minutes after the logging of this event and will attempt to create an index for the attribute. Additional Data Error value: -1403 JET_errIndexDuplicate, Index is already defined For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp. .... Event Type: Error Event Source: NTDS General Event Category: DS Schema Event ID: 1136 Date: 13.11.2009 Time: 14:15:05 User: NT AUTHORITY\ANONYMOUS LOGON Computer: MESSINE Description: Active Directory failed to create an index for the following attribute. Attribute identifier: 591822 A

(quite rightly) terrified of seeing a whole bunch of errors in the DS event log following a schema update.   This happened to me in a lab environment at a customer recently and I thought I would share the information here. I ran Windows Server 2008 adprep /forestprep on a Windows Server 2003 SP1 DC.  All seemed to go well and the schema update completed successfully.  Before moving on I checked the Directory Service event log and found a large number of 1136 error events.  There were effectively two events that were recurring, as shown below. Event Type: Error Event Source: NTDS General Event Category: DS Schema Event ID: 1136 Date:  23/01/2009 Time:  1:02:38 p.m. User:  NT AUTHORITY\ANONYMOUS LOGON Computer: DC1 Description: Active Directory failed to create an index for the following attribute. � Attribute identifier: 591789 Attribute name: msFVE-RecoveryGuid � A schema cache update will occur 5 minutes after the logging of this event and will attempt to create an index for the attribute. � Additional Data Error value: -1403 JET_errIndexDuplicate, Index is already defined For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp. Event Type: Error Event Source: NTDS General Event Category: DS Schema Event ID: 1136 Date:  23/01/2009 Time:  1:01:53 p.m. User:  NT AUTHORITY\ANONYMOUS LOGON Computer: DC1 Description: Active Directory failed to create an index for the following attribute. � Attribute identifier: 591822 Attribute name: msFVE-VolumeGuid � A schema cache update will occur 5 minutes after the logging of this event and will attempt to create an index for the attribute. � Additional Data Error value: -1403 JET_errIndexDuplicate, Index is already defined For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.  Some Googling revealed the problem to be to do with a combination of the BitLocker Drive Encryption schema updates that are included as part of the Windows Server 2008 schema extensions together with certain language locales (New Zealand English in my case). The resolution of the issue involves removing the CONTAINER_INDEX setting within the searchFlags attribute value of the msFVE-VolumeGuid and msFVE-RecoveryGuid attribute schema objects.  To do this you can use ADSIEdit to modify the value for both attributes from 27 to 25, as shown in the screenshot below.   Once the modifications have been made, the errors no longer recur. Interestingly, I could not reproduce the problem when running Windows Server 2008 forestprep on a Windows Server 2003 R2 SP2 DC with the same language locale. For more i