This is a short tip to solve the error event 34215, this event appears when client-side is trying to write an extra configuration into a IIS shared configuration and you don´t have enough permissions.
First thing, is understand how client-side monitoring is deployed. By default, client-side monitoring, tries to create the CSMCollector virtual directory and the OperationsManagerCsmCollector v.4.0 application pool when you execute the client-side wizard in the SCOM console.
The solution is easy, just give the computer permissions (web server) over the shared directory of IIS config.
After that you will get an event 34243 that means "The new client-side monitoring configuration has been successfully applied. No conflicts were detected."
Showing posts with label apm. Show all posts
Showing posts with label apm. Show all posts
Tuesday, March 18, 2014
Saturday, December 7, 2013
A fast way to find a LAMP memory leak
This summary is not available. Please
click here to view the post.
Tuesday, November 26, 2013
Scom APM 2012 SP1
In System Center 2012 – Operations Manager, you can monitor web applications and web services from server- and client-side perspectives to get details about application availability and performance that can help you pinpoint problems. (For System Center 2012 SP1 only: You can also monitor Windows Services.) When you specify settings, the types of events to collect, the performance goals to measure, and which servers to monitor, Operations Manager .NET Application Monitoring provides insights into how web-based applications are running. You can see how frequently a problem is occurring, how a server was performing when a problem occurred, and the chain of events related to the slow request or a method that is unreliable. You have to have this information to partner with software developers and database administrators to help ensure that applications are available and perform at optimal levels.
Subscribe to:
Posts (Atom)