Basically, here is the summary of what you need to do.
<![if !supportLists]>1. <![endif]>Copy the long ID from the event log
<![if !supportLists]>2. <![endif]>Search the ID in SharePoint Config DB
<![if !supportLists]>3. <![endif]>Retrieve the Column ID
<![if !supportLists]>4. <![endif]>Then run stsadm -o deleteconfigurationobject command
<![if !supportLists]>5. <![endif]>Done!
Here are all the details how you can continue,
<![if !supportLists]>1. <![endif]>Copy the long ID from the event 8031, just like the blue highlight in the image above
<![if !supportLists]>2. <![endif]>Logon to SQL Server and lunch SQL Management Studio
<![if !supportLists]>3. <![endif]>Navigate to SharePoint_Config database, create a new SQL Query, and enter the following statement
SELECT ID, Properties FROM [Objects] WHERE [Name] LIKE '%24ca5db5-9a2f-4a3d-9e52-38ab5a1a7ab0_735388cb-9769-4d37-b212-0b17a5db02f8%'
<![if !supportLists]>4. <![endif]>Note the id was copied from the screen above.
<![if !supportLists]>5. <![endif]>The query result returned with one record found. (screen below)
Feel free to look into the XML contents if you are interested.
<![if !supportLists]>6. <![endif]>Then I copy the column id from the above image (highlighted in purple)
<![if !supportLists]>7. <![endif]>Go back to the Web server and run the following stsadm.
STSADM -o deleteconfigurationobject -id C8D9F11F-D129-41D7-9248-D54DE43059D2
<![if !supportLists]>8. <![endif]>The operation completed successfully,
Hope you manage to do these steps.
This comment has been removed by the author.
ReplyDeleteI have noticed the same errors on SP2013 Application event logs.
ReplyDelete5errors are generated for every 15min . After I run the stsadm command the errors disappears but a new set of errors with 8031 ID appears
muş
ReplyDeleteyozgat
manisa
nevşehir
çankırı
7GİQPC