Hi Our authoring server is running at 100% cpu, with the "sqlserver.exe" process using all available cpu. It has been going on for days - if the server restarts, it sorts the problem temporarily then it gradually ramps up again. We are seeing a number of MCMS and SQL Server errors in the logs, such as:- * CommitChanges() - Warning: Node 102989 not synchronized at start of commit. * An unrecognized request was received by the CMS ISAPI Filter. The request was mapped to the CMS read-only resource cache virtual directory but the URL format did not correspond to a CMS Resource. The CMS ISAPI Filter did not process the request and allowed IIS to handle it instead. The requested URL was '/NR/rdonlyres/E4723A1B-1D06-43FB-9689-839A5E6D3BE4/0/'. * CommitChanges() - Warning: Node d not committed or rolled back at start of commit. It's a 2gb Win2003 server - MCMS is pretty big at approx 10000 postings and 40000 resources. Is there anything I can do to diagnose what is causing the cpu utilization? Regards Andy
Hi Andy, - you can ignore the warning about "rolled back". It is a warning that is handled internally and does not have any negative side effects - beside the fact that it is written into the event log. - the URL listed below is indeed incorrect. It misses the resource gallery item. These type of requests can occur when opening a document in MCMS through Office. Office does a PROPFIND web dav request to the URL it assumes to be the folder. MCMS URLs are not hierarchical in this way and the sent URL is invalid from MCMS perspective and you will get this warning. You can ignore it. Cheers, Stefan "Andy Stephens" <andrew.stephens@cheshire.gov.uk-donotspam> wrote in message news:292DCD8B-ADA2-4801-98F0-F684C9D99FFC@microsoft.com... > Hi > > Our authoring server is running at 100% cpu, with the "sqlserver.exe" > process using all available cpu. It has been going on for days - if the > server restarts, it sorts the problem temporarily then it gradually ramps > up > again. > > We are seeing a number of MCMS and SQL Server errors in the logs, such > as:- > * CommitChanges() - Warning: Node 102989 not synchronized at start of > commit. > * An unrecognized request was received by the CMS ISAPI Filter. The > request > was mapped to the CMS read-only resource cache virtual directory but the > URL > format did not correspond to a CMS Resource. The CMS ISAPI Filter did not > process the request and allowed IIS to handle it instead. The requested > URL > was '/NR/rdonlyres/E4723A1B-1D06-43FB-9689-839A5E6D3BE4/0/'. > * CommitChanges() - Warning: Node d not committed or rolled back at start > of > commit. > > > It's a 2gb Win2003 server - MCMS is pretty big at approx 10000 postings > and > 40000 resources. > > Is there anything I can do to diagnose what is causing the cpu > utilization? > > Regards > > Andy
