Management Reporter Errors ("No endpoint listening" and "You don't have permission")

Question Status

Laurie Sweeney asked a question on 2 Aug 2012 6:14 PM

This is an FYI.   I was receiving the following messages when trying to install Management Reporter 2012 for Dynamics SL 2011.     My problem was that I was trying to do the install logged in as Administrator.   You have to be logged in with the Domain Account that you created to take on the Administrator role for Management Reporter.   I'm posting this because I spent a ton of time on other resolutions around these errors below, when I was simply not logged in as the correct user.


From the Deployment Log:
System.ServiceModel.EndpointNotFoundException: There was no endpoint listening at http://wccs1:4712/CompanyService.svc that could accept the message. This is often caused by an incorrect address or SOAP action. See InnerException, if present, for more details. ---> System.Net.WebException: Unable to connect to the remote server ---> System.Net.Sockets.SocketException: No connection could be made because the target machine actively refused it
I do have a displayname for the user I created.
If I just install the application and process services, it will install successfully. When I add the Dynamics SL piece, then I get this error message:
Microsoft.Dynamics.Performance.Reporting.Common.ReportingPermissionException: You don't have permission to perform this operation.
at Microsoft.Dynamics.Performance.Reporting.Security.Service.SecureServiceBase.SecureExecuteInternal[TResult](Func`1 hasPermission, Func`1 executor)
at Microsoft.Dynamics.Performance.Reporting.Common.Service.ServiceBase.BaseExecute[TResult](Func`1 executor)
8/1/2012 2:42:46 AM - System.ServiceModel.Security.SecurityAccessDeniedException: Access is denied.
Cory Severson responded on 20 Aug 2012 10:16 AM

Hello Laurie,

Thanks for adding this.  Sounds like you found you had to be logged onto the machine as an MR Admin to run the provider install.  Nice catch.  I belive the install guide does have this information.  That guide can be found here.

Brian Meagher responded on 17 Jun 2013 1:19 PM

As an update to this: first - Microsoft should NOT require that a particular user be logged in to deploy an application (assuming the logged in user has sufficient privileges). Or, if that is a requirement, the User Interface should show the logged in user's name in the dialog box, clearly indicating that the user will be used for the Service Account.

The update: The message about "no endpoint" seems to be something of a red herring. It seems like the installer is testing to make sure TCP port 4712 is available. Farther down in the log (in my case) was a message "an error occured during decryption". In my case, the cause was an invalid "Master Key" in the instance of SQL Server I was installing to. Looking up error "Msg 15466" in google lead me to the answer: forcefully reset the Master Key for the instance of SQL Server. Look for articles referencing ALTER SERVICE MASTER KEY to learn more.

Very specifically in this case, I believe that the instance of SQL Server was originall built, and then the master database was restored from a different instance to retain security and other configuration data.

Bottom line: Microsoft needs to work on the MR installation/configuration tool to provide MUCH better error reporting for things that seem to be pretty common in the field.