Solved

Error Mesage when changing event throttling (diagnostic logging) in Central Administration

Posted on 2009-05-12
11
578 Views
Last Modified: 2012-05-06
On our MOSS 2007 Testsystem we get the following error message when I change someting in the diagnostic loggin section of central administration:
An update conflict has occured, and you must re-try this action. The object DiagnosticService Parent=SPFarm Name=SharePoint is being updated by username, in the w3wp process, on machine servername. View the tracing log for more information about the conflict.

In the log I was able to find the following:
Updating SPPersistedObject SPDiagnosticsService Parent=SPFarm Name=SharePoint Version: 8047 Ensure: 0, HashCode: 39209369, Id: 52174321-59ba-46ef-9ca9-c40bd148c2c9, Stack:    at Microsoft.SharePoint.Administration.SPPersistedObject.Update()     at Microsoft.SharePoint.Administration.SPService.Update()     at Microsoft.SharePoint.Administration.SPDiagnosticsService.Update()     at Microsoft.SharePoint.ApplicationPages.MetricsPage.BtnSave_Click(Object sender, EventArgs e)     at System.Web.UI.WebControls.Button.OnClick(EventArgs e)     at System.Web.UI.WebControls.Button.RaisePostBackEvent(String eventArgument)     at System.Web.UI.WebControls.Button.System.Web.UI.IPostBackEventHandler.RaisePostBackEvent(String eventArgument)     at System.Web.UI.Page.RaisePostBackEvent(IPostBackEventHandler sourceControl, String eventArgument)     at System.Web.UI.Page.RaisePostBackEvent(NameValueCollection postData)     at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)     at System.Web.UI.Page.ProcessRequest(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)     at System.Web.UI.Page.ProcessRequest()     at System.Web.UI.Page.ProcessRequestWithNoAssert(HttpContext context)     at System.Web.UI.Page.ProcessRequest(HttpContext context)     at ASP._admin_metrics_aspx.ProcessRequest(HttpContext context)     at System.Web.HttpApplication.CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute()     at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously)     at System.Web.HttpApplication.ApplicationStepManager.ResumeSteps(Exception error)     at System.Web.HttpApplication.System.Web.IHttpAsyncHandler.BeginProcessRequest(HttpContext context, AsyncCallback cb, Object extraData)     at System.Web.HttpRuntime.ProcessRequestInternal(HttpWorkerRequest wr)     at System.Web.HttpRuntime.ProcessRequestNoDemand(HttpWorkerRequest wr)     at System.Web.Hosting.ISAPIRuntime.ProcessRequest(IntPtr ecb, Int32 iWRType)  

Thanks for helping.
0
Comment
Question by:MedResearch
  • 6
  • 5
11 Comments
 
LVL 51

Expert Comment

by:tedbilly
ID: 24371874
Have you tried completely turning it off, then reactivating it?
0
 

Author Comment

by:MedResearch
ID: 24375461
Do you mean that process?

I've even restarted the server several times.
0
 
LVL 51

Expert Comment

by:tedbilly
ID: 24381701
Yes I mean go into Central Admin, completely turn off Diagnostic Logging, then reactivate it.

Did you change anything on the farm recently?
0
 

Author Comment

by:MedResearch
ID: 24382559
Yes. I've set up an new farm for testing purpose. In order to have similar configuration on this testsystem I've copied a lot of files out of the 12 Hive folder. Actually both systems should have had the same versions installed (sp1 without infrastructure update).

After I've noticed this problem with the logging configuration, I've installed the infrastructure update and restartet the configuration wizard. Unfortunately the problem still remained.
0
 
LVL 51

Expert Comment

by:tedbilly
ID: 24392715
Wait a minute, you can't clone Sharepoint that way.  So these problems are on the clone?

Sharepoint cannot be cloned.  If you treat it like a disaster recovery you can setup a second farm and copy site collections using stsadm backup/restore or copy content databases and attach them to duplicate web applications (Described on other questions on this site)

Customization should be completed using Sharepoint Deployment solutions which also must be installed on both farms.
0
How to improve team productivity

Quip adds documents, spreadsheets, and tasklists to your Slack experience
- Elevate ideas to Quip docs
- Share Quip docs in Slack
- Get notified of changes to your docs
- Available on iOS/Android/Desktop/Web
- Online/Offline

 

Author Comment

by:MedResearch
ID: 24392992
I did not clone the servers. All the solutions / features have been reinstalled. The settings of CA were reconfigured manually. I've restored the SSP from a backup of the productive systeme and adapted configuration for the test system afterwards. But since we also made a couple of customizations within the 12 hive folder, I copied these files to the test system (templates, bin, layouts, ...).

Do you think my only chance is a completly new setup of the front end server?
0
 
LVL 51

Expert Comment

by:tedbilly
ID: 24400411
Hard to say, it depends what you've done.  In our farm no one is allowed to touch the 12 hive folder at all.   It is mandatory to do all customization via WSP files.  They have their own local development copy of Sharepoint running in a virtual machine at each desk and they can do what they want there, but everything else MUST be deployed properlyl.

When we've restored the SSP we found a number of problems, BDC's and mapped properties didn't come with the restoration process.  
0
 

Author Comment

by:MedResearch
ID: 24419184
Ok. So I will deinstall SharePoint with all realated language packs. Then I will clean up the 12 hive folder and start a new installation.

This time I will configure ssp and ca manually. I will deploy all solutions.

The only thing I have to deploy manually is all layout modification in the /12/Template Folder, because we did these modifications directly in this folder.

Are there some files in the /12/template Folder which should definitively not be copied?
0
 
LVL 51

Expert Comment

by:tedbilly
ID: 24419219
I would strongly recommend against applying any files in the /12/template folder manually.  The problem is that backups don't include manual customizations.  I'll admit it's a pain to learn how to do it, but in the long run it's safer especially if you add more servers to the farm.
0
 

Author Comment

by:MedResearch
ID: 24464999
Ok. Now I've reinstalled MOSS. I've deleted the complete 12 hive folder before the new installation of MOSS.

Unfortunately, the problem still exists.
0
 
LVL 51

Accepted Solution

by:
tedbilly earned 125 total points
ID: 25885262
Did you do any manual changes again or is this an untouched installation of MOSS?
0

Featured Post

Complete VMware vSphere® ESX(i) & Hyper-V Backup

Capture your entire system, including the host, with patented disk imaging integrated with VMware VADP / Microsoft VSS and RCT. RTOs is as low as 15 seconds with Acronis Active Restore™. You can enjoy unlimited P2V/V2V migrations from any source (even from a different hypervisor)

Join & Write a Comment

Summary In SharePoint 2010 it is easy to create custom color themes to jazz up a site. Theme colors can also be created in PowerPoint 2010 with a few clicks. But how do the chosen colors actually look in the SharePoint site? The attached PowerPoint…
These days socially coordinated efforts have turned into a critical requirement for enterprises.
Sending a Secure fax is easy with eFax Corporate (http://www.enterprise.efax.com). First, Just open a new email message.  In the To field, type your recipient's fax number @efaxsend.com. You can even send a secure international fax — just include t…
This tutorial demonstrates a quick way of adding group price to multiple Magento products.

746 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

12 Experts available now in Live!

Get 1:1 Help Now