Conectare
 
Pagina de pornireBibliotecăInformațiiFişiere de descărcatSuportComunitateForumuri
Resurse pentru profesionişti IT >
> 
> 
Logon failure on SQL Reporting Server

Locked Logon failure on SQL Reporting Server

  • 17 aprilie 2007 20:18
     
     
    Sign in pentru a vota
    0

    When I want to view a report on SQL Reporting Server using FCS, the page finishs with the following error:

     

    Logon failed (rsLogonFailed)

              Logon failure: unknown user name or bad password (Exception from HRESULT: 0x8007052E)

     

    I installed FCS with administrator account, and I have been using it. But recently I can not view anything.

     

    Comments?

     

    Thank you.

       

    Toate mesajele

    • 18 aprilie 2007 15:15
       
       
      Sign in pentru a vota
      0
      I am assuming that you have been able to access the reporting server before with the same username and password. But from the log, the username or password is incorrect. I would check that SQL, MOM and FCS are using the same database and are accessing with the same username and password
         
      • 18 aprilie 2007 20:53
         
         
        Sign in pentru a vota
        0
        SQL Reporting Services permissions are modified from the web interface http://server/reports and then the properties tab. From there you can allocate users/groups and their appropriate permissions
           
        • 18 aprilie 2007 21:18
           
           
          Sign in pentru a vota
          0

          I created two or three user accounts for using FCS. Each one is for SQL, MOM, and MOM DTS. In the installation (and the document) refers that. If I need to use one account for all services, please me notify me.

          However, the first days it works with out problems. Only the report area (14-day) is not working yet (since the installation).

           

          Thank you for your support.

             
          • 21 iunie 2010 17:04
             
              Are cod
            Sign in pentru a vota
            0

            http://www.eggheadcafe.com/aspnet_answers/SQLServerreportingsvcs/May2006/post26747332.asp

             

            BINGO! 
 
Removing the unattended execution account has fixed all of my reports.

             

            I decided to follow that advice and bingo! it worked!