300
Database configuration: The password could not be validated against the password policy.
The same password worked in UAT/TEST/DEV for those service accounts. The only difference in PROD is the DB Server is NOT local on the Management Reporter server where teh services will be installed. Could this be a Kerberos issue.
*This post is locked for comments
In my case it was due to installation file. I change the installation file by downloading the latest setup namely "ManagementReporter2012-CU15-en-us" and issue is resolved.
This "back connection" was exactly my problem. I have a development VM that I do work in and I often clone my base VM for various reasons. I have etc\host entries for SQL Server, web sites, and the like so everything loops back and I don't have to reconfigure stuff.
You saved me a lot of time!
Regards,
Stuart
Just in case anyone comes across this old string looking for an answer like I did this morning... I got this same error with MR 2012 RU5 today. I hadn't seen it before. I was installing MR right on the SQL Server itself. We were using a DNS alias here, which I haven't tried before, so I thought it might be related. The DNS was working fine, but I added a host file entry anyway. However I believe the actual fix was adding the BackConnectionHostNames reg entry. This is how to do it (from an MS article):
Create the Local Security Authority host names that can be referenced in an NTLM authentication request
To do this, follow these steps for all the nodes on the client computer:
1.Click Start, click Run, type regedit, and then click OK.
2.Locate and then click the following registry subkey: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa\MSV1_0
3.Right-click MSV1_0, point to New, and then click Multi-String Value.
4.In the Name column, type BackConnectionHostNames, and then press ENTER.
5.Right-click BackConnectionHostNames, and then click Modify.
6.In the Value data box, type the CNAME or the DNS alias, that is used for the local shares on the computer, and then click OK.
Note Type each host name on a separate line.
There is an article on this specific issue on partnersource:
mbs2.microsoft.com/.../kbdisplay.aspx
Basically:
The password validate function that is used during the Management Report installation tries to connect to the RPC Endpoint Mapper service on the SQL server (port 135).
If that is successful, the RPC Endpoint Manager will provide the Management Reporter installer with a port number from the range of dynamics ports on the SQL server. The installer will
then try to connect to the SQL server using that port. If either of these connection attempts fail, you will receive the password validation error.
So you may need to open port 135 to RPC and start the RPC locator service.
#1
André Arnaud de Cal...
292,516
Super User 2025 Season 1
#2
Martin Dráb
231,317
Most Valuable Professional
#3
nmaenpaa
101,156
Share
Report
All responses (
Answers (
