Management Reporter 2012 Slow and Event Logs Errors

(0) Share

Report

Posted on by mebenz

3,815

I have upgraded to CU9 so am on the latest version. I can log into MR without any errors. I can run a report without any errors in MR. The report takes a full 3-4 minutes in Queue before it processes it (no one else is processing anything). Once it starts to process, I see 2 entries in the Event Viewer:

System.ServiceModel.Security.SecurityNegotiationException: SOAP security negotiation with 'http://servername:4712/RepositoryService.svc' for target 'http://servername:4712/RepositoryService.svc' failed. See inner exception for more details. ---> System.ComponentModel.Win32Exception: Security Support Provider Interface (SSPI) authentication failed. The server may not be running in an account with identity 'host/wfw-reports'. If the server is running in a service account (Network Service for example), specify the account's ServicePrincipalName as the identity in the EndpointAddress for the server. If the server is running in a user account, specify the account's UserPrincipalName as the identity in the EndpointAddress for the server.

Then

Microsoft.Dynamics.Performance.Reporting.Common.ReportingServerCommunicationException: There was a problem communicating with the server.

at Microsoft.Dynamics.Performance.Reporting.Common.Service.ClientBase.Execute[TExec](Func`1 executor, Action`1 handler)

at Microsoft.Dynamics.Performance.Reporting.Repository.Item.<>c__DisplayClassf`1.<ListItems>b__e()

at Microsoft.Dynamics.Performance.Reporting.Common.ExceptionHandling.<>c__DisplayClass1`2.<MakeHandler>b__0(Func`1 execute)

I've read so many threads about the communicating error but I don't get any errors in MR. There's also articles about a MR application pool that's supposed to exist in IIS but I don't see that in our install.

*This post is locked for comments

All responses (2)

Answers (0)

mebenz 3,815 on at

Like (0)

Report

RE: Management Reporter 2012 Slow and Event Logs Errors

When I run the same report on one of our citrix servers the report is just as slow (full 2-3 minutes before it starts processing the report) and there are no errors in the logs.
Community Member Microsoft Employee on at

Like (0)

Report

RE: Management Reporter 2012 Slow and Event Logs Errors

Hi Mebenz,

The event Error log appears by the below 3 scenarios, please make sure the following things are adopted

1) The computer is not connected to the domain where Management Reporter is installed

for this you can follow the below steps:

Management Reporter will only function while connected to the domain used during the install. Even if all MR server components are on one computer, that computer still needs to be connected to the domain you were using when you installed MR.

Note This means that Management Reporter will not work when demonstration laptops are not physically connected to the domain or not connected using a VPN connection.

2) your computer is having problems communicating or authenticating with the domain

for this you can follow the below steps:

Remove the computer from the domain and then add it back to the domain. Warning A local administrator account will need to be used to logon to the computer one time after it is removed from the domain.
1) Click Start, click Run and type: sysdm.cpl to open System Properties.
2) Click Change and make a note of the Domain name.
3) Click Workgroup, type a name (i.e. workgroup), click OK to accept changes and then restart the computer.
4) After restarting, click Start, click Run and type: sysdm.cpl to open System Properties.
5) Click Change and then click Domain.
6) Enter the domain noted above, click OK to accept changes and then restart the computer.

3) MR Services are being run as a Domain user and WCF Authentication is failing when using the UPN (User Principal Name).

for this you can follow the below steps:

Create an SPN on the computer for the domain account running the MR Service. To create an SPN for this domain account, run the Setspn tool at a command prompt on the MR server with the following commands:

setspn -S HTTP/MRservername domain\customAccountName

setspn -S HTTP/MRservername.fullyqualifieddomainname domain\customAccountName

Note

"MRservername" should be replaced with the MR server name where the MR Application Service is installed.
"MRservername.FullyQualifiedDomainName" should be replaced with the fully qualified domain name of the MR server where the MR Application Service is installed.
"domain\customAccountName" should be replaced with the domain account running the MR Services.