none
Verify that SQL Server Reporting Services is installed properly and that it is running. RRS feed

  • Question

  • I am trying to install DPM 2010 on Windows 2008 R2.  Running through installation and the server that I'm installing DPM to will also host the SQL instance and Reporting instance.  Pretty much choosing all the defaults.

    Installation gets to reporting portion and fails.  It says that I need to verify that Reporting Services is running.   The exact error is:

    Data Protection Manager installation has failed. To return the server to its original state, you must uninstall Data Protection Manager by using Add or Remove Programs in Control Panel. This will remove all files and components copied during installation.  For details, click the Error tab.

    DPM Setup has not configured Reporting Services to use Secure Sockets Layer. For more information on how to configure the Report Server for Secure Sockets Layer (SSL) connections, see Configuring Report Server for Secure Sockets Layer (http://go.microsoft.com/fwlink/?LinkId=178289)

    Report configuration failed.

    Verify that SQL Server Reporting Services is installed properly and that it is running.

    ID: 812

    It is running and working, I can go to the URL and see Reports installed.   It grabbed a server certificate which is valid and binds that to 443.  I have tried this as well with the certificate removed.

    Here is the relative portion of the DPM 2010 log:

    [6/25/2010 10:30:01 AM] * Exception :  => System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> Microsoft.Internal.EnterpriseStorage.Dls.UI.Library.Reporting.ReportingException: Exception of type 'Microsoft.Internal.EnterpriseStorage.Dls.UI.Library.Reporting.ReportingException' was thrown.
       at Microsoft.Internal.EnterpriseStorage.Dls.UI.Library.Reporting.ReportingException.UnableToConfigureAccount(ErrorCode errorCode)
       at Microsoft.Internal.EnterpriseStorage.Dls.UI.Library.Reporting.Reporter.CreateUserAccount(String server, String password, Boolean create)
       at Microsoft.Internal.EnterpriseStorage.Dls.UI.Library.Reporting.Reporter.SetReportingPassword(String password, String server, String instanceName, String dbConnectionString)
    *** Mojito error was: PasswordTooShort; 0; None
       --- End of inner exception stack trace ---
       at System.RuntimeMethodHandle._InvokeMethodFast(Object target, Object[] arguments, SignatureStruct& sig, MethodAttributes methodAttributes, RuntimeTypeHandle typeOwner)
       at System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture, Boolean skipVisibilityChecks)
       at System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture)
       at System.RuntimeType.InvokeMember(String name, BindingFlags bindingFlags, Binder binder, Object target, Object[] providedArgs, ParameterModifier[] modifiers, CultureInfo culture, String[] namedParams)
       at System.Type.InvokeMember(String name, BindingFlags invokeAttr, Binder binder, Object target, Object[] args)
       at Microsoft.Internal.EnterpriseStorage.Dls.Setup.Wizard.ReportingConfiguration.ConfigureReporting(Boolean isRemoteDb, String rsMachineName, String rsInstanceName, String installerPath)
    [6/25/2010 10:30:01 AM] * Exception :  => Report configuration failed.Verify that SQL Server Reporting Services is installed properly and that it is running.Microsoft.Internal.EnterpriseStorage.Dls.Setup.Exceptions.BackEndErrorException: exception ---> Microsoft.Internal.EnterpriseStorage.Dls.Setup.Exceptions.ReportDeploymentException: exception ---> System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> Microsoft.Internal.EnterpriseStorage.Dls.UI.Library.Reporting.ReportingException: Exception of type 'Microsoft.Internal.EnterpriseStorage.Dls.UI.Library.Reporting.ReportingException' was thrown.
       at Microsoft.Internal.EnterpriseStorage.Dls.UI.Library.Reporting.ReportingException.UnableToConfigureAccount(ErrorCode errorCode)
       at Microsoft.Internal.EnterpriseStorage.Dls.UI.Library.Reporting.Reporter.CreateUserAccount(String server, String password, Boolean create)
       at Microsoft.Internal.EnterpriseStorage.Dls.UI.Library.Reporting.Reporter.SetReportingPassword(String password, String server, String instanceName, String dbConnectionString)
    *** Mojito error was: PasswordTooShort; 0; None
       --- End of inner exception stack trace ---
       at System.RuntimeMethodHandle._InvokeMethodFast(Object target, Object[] arguments, SignatureStruct& sig, MethodAttributes methodAttributes, RuntimeTypeHandle typeOwner)
       at System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture, Boolean skipVisibilityChecks)
       at System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture)
       at System.RuntimeType.InvokeMember(String name, BindingFlags bindingFlags, Binder binder, Object target, Object[] providedArgs, ParameterModifier[] modifiers, CultureInfo culture, String[] namedParams)
       at System.Type.InvokeMember(String name, BindingFlags invokeAttr, Binder binder, Object target, Object[] args)
       at Microsoft.Internal.EnterpriseStorage.Dls.Setup.Wizard.ReportingConfiguration.ConfigureReporting(Boolean isRemoteDb, String rsMachineName, String rsInstanceName, String installerPath)
       --- End of inner exception stack trace ---
       at Microsoft.Internal.EnterpriseStorage.Dls.Setup.Wizard.ReportingConfiguration.ConfigureReporting(Boolean isRemoteDb, String rsMachineName, String rsInstanceName, String installerPath)
       at Microsoft.Internal.EnterpriseStorage.Dls.Setup.Wizard.BackEnd.ConfigureReporting(String reportserverConfigFilePath, Boolean existingDB, Boolean isOemSetup, Boolean isRemoteDb, String sqlServerMachineName, String instanceName)
    *** Mojito error was: ReportDeploymentFailed; 0; None
       --- End of inner exception stack trace ---
       at Microsoft.Internal.EnterpriseStorage.Dls.Setup.Wizard.BackEnd.ConfigureReporting(String reportserverConfigFilePath, Boolean existingDB, Boolean isOemSetup, Boolean isRemoteDb, String sqlServerMachineName, String instanceName)
       at Microsoft.Internal.EnterpriseStorage.Dls.Setup.Wizard.DpmInstaller.ConfigureReporting(Boolean isRemoteDb)
       at Microsoft.Internal.EnterpriseStorage.Dls.Setup.Wizard.ProgressPage.InstallerThreadEntry()
    *** Mojito error was: ReportDeploymentFailed; 0; None
    [6/25/2010 10:30:07 AM] *** Error : Report configuration failed.

    Verify that SQL Server Reporting Services is installed properly and that it is running.

    ID: 812
    [6/25/2010 10:30:07 AM] Information : Data Protection Manager installation has failed. To return the server to its original state, you must uninstall Data Protection Manager by using Add or Remove Programs in Control Panel. This will remove all files and components copied during installation.
    For details, click the Error tab.

    DPM Setup has not configured Reporting Services to use Secure Sockets Layer. For more information on how to configure the Report Server for Secure Sockets Layer (SSL) connections, see Configuring Report Server for Secure Sockets Layer (http://go.microsoft.com/fwlink/?LinkId=178289)

    Friday, June 25, 2010 3:21 PM

Answers

  • Hello,

     

    The real problem is the error UnableToConfigureAccount and *** Mojito error was: PasswordTooShort; 0; None

     

    The reason is due to the new password complexity on Windows 2008 which states the following:

    -----------------------------------------------------------------------------
    Password must meet complexity requirements

    This security setting determines whether passwords must meet complexity requirements.

    If this policy is enabled, passwords must meet the following minimum requirements:

    Not contain the user's account name or parts of the user's full name that exceed two consecutive characters
    Be at least six characters in length Contain characters from three of the following four categories:
    English uppercase characters (A through Z)
    English lowercase characters (a through z)
    Base 10 digits (0 through 9)
    Non-alphabetic characters (for example, !, $, #, %)
    Complexity requirements are enforced when passwords are changed or created.

    Default:

    Enabled on domain controllers.
    Disabled on stand-alone servers.

    Note: By default, member computers follow the configuration of their domain controllers.

    Please use a more secure password adhering to the above criteria and DPM should install fine.


    Regards, Mike J [MSFT] This posting is provided "AS IS" with no warranties, and confers no rights.
    Friday, June 25, 2010 5:50 PM
    Moderator
  • What happens when you try to make the account from command line:  net user DPMR$DPMmachinename PASSWORD /ADD

     

    Example:  net user DPMR$dpm2010 Windows#2008R2 /ADD

    If you get an error, you need to troubleshoot your password policy.


    Regards, Mike J [MSFT] This posting is provided "AS IS" with no warranties, and confers no rights.
    • Marked as answer by Alvin____CHEN Tuesday, June 29, 2010 3:54 PM
    Friday, June 25, 2010 11:40 PM
    Moderator

All replies

  • Hello,

     

    The real problem is the error UnableToConfigureAccount and *** Mojito error was: PasswordTooShort; 0; None

     

    The reason is due to the new password complexity on Windows 2008 which states the following:

    -----------------------------------------------------------------------------
    Password must meet complexity requirements

    This security setting determines whether passwords must meet complexity requirements.

    If this policy is enabled, passwords must meet the following minimum requirements:

    Not contain the user's account name or parts of the user's full name that exceed two consecutive characters
    Be at least six characters in length Contain characters from three of the following four categories:
    English uppercase characters (A through Z)
    English lowercase characters (a through z)
    Base 10 digits (0 through 9)
    Non-alphabetic characters (for example, !, $, #, %)
    Complexity requirements are enforced when passwords are changed or created.

    Default:

    Enabled on domain controllers.
    Disabled on stand-alone servers.

    Note: By default, member computers follow the configuration of their domain controllers.

    Please use a more secure password adhering to the above criteria and DPM should install fine.


    Regards, Mike J [MSFT] This posting is provided "AS IS" with no warranties, and confers no rights.
    Friday, June 25, 2010 5:50 PM
    Moderator
  • Hmmm.  I have tried twice again, each time with a password that meets and exceeds all these complexity requirements, and again I get the same error during installation. 
    Friday, June 25, 2010 9:59 PM
  • What happens when you try to make the account from command line:  net user DPMR$DPMmachinename PASSWORD /ADD

     

    Example:  net user DPMR$dpm2010 Windows#2008R2 /ADD

    If you get an error, you need to troubleshoot your password policy.


    Regards, Mike J [MSFT] This posting is provided "AS IS" with no warranties, and confers no rights.
    • Marked as answer by Alvin____CHEN Tuesday, June 29, 2010 3:54 PM
    Friday, June 25, 2010 11:40 PM
    Moderator
  • That fixed it!  Thanks so much!
    Tuesday, June 29, 2010 3:54 PM
  • What fixed it Alvin____Chen?

    What did you do to fix it.

     

    Wednesday, August 11, 2010 8:08 PM
  • i got my problem fixed by setting more complex password.

    but one thing i need to ask one thing from MS that why the error is not self explanatory ?

    i was searching for more then 4 days for SQL reporting and the error was just password complexity....

     


    Ali Salman Naqvi.
    Thursday, October 14, 2010 6:38 AM
  • I have the same problem installing DPM 2010 eval on a new install of Server 2008 R2.

     

    I can create a new user with the same password, and it does meet the complexities.

     

    Someone mentioned pulling the network cable out at this stage, i tried it and it did pass, however the install failed after that.

     

    Any ideas?

    Wednesday, February 23, 2011 1:19 PM
  • Hi,

    Please try adding the user manually from a command prompt:

        net user DPMR$%computername% Windows#2008R2 /ADD

    Then use that same password during installation of DPM.


    Regards, Mike J. [MSFT] This posting is provided "AS IS" with no warranties, and confers no rights.
    Wednesday, February 23, 2011 6:44 PM
    Moderator
  • Mike,

     

    I have done this and it created the user but still gave the same error when i entered it in the install.

    It takes that passwordduring the install if i unplug the network cable or disable the NIC, but then the install fails later.

    IS this a known fault?


    Jonny Nabb
    Thursday, February 24, 2011 2:37 PM
  • Hi,

    This is not a DPM issue, check to see if you have any 3rd party products installed like PassFilt

    Check under HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa
    Check for passfilt.dll or CSPWFILT.DLL in the windows\system32 directory. 

    You can try plugging in the NIC after you get past the password screen.

     


    Regards, Mike J. [MSFT] This posting is provided "AS IS" with no warranties, and confers no rights.
    Thursday, February 24, 2011 4:36 PM
    Moderator
  • Mike,

    Thanks for your attention on this, however it is most definitely a DPM issue.

    This is a brand new install of 2008 R2. Nothing else is installed. This issue arrises when i try and install DPM.

     

    How is that not a DPM issue?

     

    Jonny


    Jonny Nabb
    Thursday, February 24, 2011 7:39 PM
  • Hi,

    What I mean is there is nothing in DPM code that can be configured or fixed to overcome that problem.  DPM setup is just a victim of an external problem.  Perhaps there is something in your domain group policy that is effecting us or a generic communication issue trying to communicate with your DC when it comes time to verify password requirements. The only issues we have seen that can cause this have already been discussed, so let us know if you find a different cause.


    Regards, Mike J. [MSFT] This posting is provided "AS IS" with no warranties, and confers no rights.
    Thursday, February 24, 2011 8:07 PM
    Moderator
  • Mike,

    I strongly disagree. This is very much a DPM problem - and responsibility.

    DPM does prerequisite checking and DPM should be checking ALL prerequisites and reporting accurately on ANY environmental issues that prevent it from being installed.

    Further, DPM documentation should include full, accurate checklists for preparation, including hot fixes and what order they should be applied in, and that list should be updated and kept in one place that we can all find easily. If SQL has reporting and documentation deficiencies (and it surely does), then get that department to help out.

    All this time wasting is because of bad management and incomplete programming. I've seen similar threads going back to DPM2006.

    Microsoft staff already know what things to check, and definitely the programmers are in a position to provide better diagnostics.

    By the way, it's eight hours now, and I still can't re-install.

    Bob.

    Friday, April 29, 2011 9:38 AM
  • Hi I encountered the same issue and could not get DPM to install either domain or newly created account.

    The newley created local account, prereq checks reported that the service account should be a domain account or a local account.  It was using a local account.

    I set all SQL services to use a local account and encountered the same error id 812..

    On closing the installation i receive an error id 4387 before prompting to end task on the app...

    Clean install from scratch, new VM and a fresh installed of SQL i think...

    Tuesday, January 21, 2014 2:36 PM
  • I was having the same problem (error 812) with DPM 2012 which I managed to fix.
    I performed the following actions to make it work:-

    Make sure that the account that you are using to install with, has explictitly been added to the local administrators group.
    As even if it has domain admin rights it won't work!

    If you changed the accounts that the SQL Server services run under, then...
    Start the 'Reporting Services Configuration Manager', connect to the reporting instance.
    Be warned you do the next step at your own risk, so make sure that you perform the backup step first if there is anything in the Reporting Services instance! Which there shouldn't be, as if like me you can't install DPM to use it.
    Select the 'Encryption Keys' on the left hand side, 'Backup' (so you can recover if needs be), then 'Delete' Encrypted Content, then on 'Change' (replace encryption keys), then'Backup' again using a different file name.

    Start the installation process again, and this fixed it for me!

    Monday, September 21, 2015 11:59 AM