Post reply

Reporting Services Login Screen to report Manager

  • June 26, 2017 at 2:53 am

    #338403

    Hi

    I have an issue with Reporting Services in that I get a login screen when I try to access Report Manager. I am using the Network Service account for the report server. I have User Access Control switched off. I have an administrator account I use for logging on to the server. If I enter that into the login screen the screen just goes blank. I cannot access the report manager at all.

     I cannot deploy any reports from Visual Studio Data tools although I can run the reports (so I can get a connection to the databases) from there.

    I get the login screen when I run a deployed report too. I have installed a new instance of reporting services but I get the same issue.

    Any Ideas would be gratefully received.

    Regards

    PJC

  • June 26, 2017 at 10:33 am

    #1948190

    Are you right clicking on IE and selecting Run As Administrator?
    When you created the new instance, did you add yourself to the administrators for SSRS? Did you try the same thing as I mentioned above with IE?

    Sue

  • June 26, 2017 at 11:17 am

    #1948211

    Hi Sue
    I have tried run as administrator but still does not work. 
    It was all working fine upto a couple of weeks ago. The network guys say nothing has changed. I couldn't access report manager when I created a new instance. These credentials all worked fine upto recently. Pjc

  • June 26, 2017 at 5:09 pm

    #1948288

    p_cormack - Monday, June 26, 2017 11:17 AM

    Hi Sue
    I have tried run as administrator but still does not work. 
    It was all working fine upto a couple of weeks ago. The network guys say nothing has changed. I couldn't access report manager when I created a new instance. These credentials all worked fine upto recently. Pjc

    Check the reporting services logs then - you have some type of permissions errors going on which should be in the log. If it used to work then most likely something has changed. Are you doing any of this from being logged onto the server itself or are you doing this from your PC?
    And you need to make sure you right click IE and select Run As Administrator...it's different than logging on as Administrator and running IE or being in the local admins group and opening IE.

    Sue

  • June 27, 2017 at 1:58 am

    #1948307

    Sue_H - Monday, June 26, 2017 5:09 PM

    p_cormack - Monday, June 26, 2017 11:17 AM

    Hi Sue
    I have tried run as administrator but still does not work. 
    It was all working fine upto a couple of weeks ago. The network guys say nothing has changed. I couldn't access report manager when I created a new instance. These credentials all worked fine upto recently. Pjc

    Check the reporting services logs then - you have some type of permissions errors going on which should be in the log. If it used to work then most likely something has changed. Are you doing any of this from being logged onto the server itself or are you doing this from your PC?
    And you need to make sure you right click IE and select Run As Administrator...it's different than logging on as Administrator and running IE or being in the local admins group and opening IE.

    Sue

    Hi Sue

    Thanks for replying.
    Which log should I be looking in. I have a trace log from which I cannot make out an error but might be because I don't understand the contents wholly. I understand there should be a http log, which I don't seem to have. Should I be looking in there or will the trace log provide the information around permissions ? Do you know how to set up the http log?

    I am logging on as Administrator, and have tried Run as Administrator on IE, but to no avail.

    Many thanks

    Paul

  • June 27, 2017 at 6:59 am

    #1948350

    p_cormack - Tuesday, June 27, 2017 1:58 AM

    Hi Sue

    Thanks for replying.
    Which log should I be looking in. I have a trace log from which I cannot make out an error but might be because I don't understand the contents wholly. I understand there should be a http log, which I don't seem to have. Should I be looking in there or will the trace log provide the information around permissions ? Do you know how to set up the http log?

    I am logging on as Administrator, and have tried Run as Administrator on IE, but to no avail.

    Many thanks

    Paul

    The reporting services log - the path on the server would be \Microsoft SQL Server\<instance name>\Reporting Services\LogFiles
    It's named ReportServerService_<timstamp>.log. That is the log you should check. You'll need to start going over it and you will eventually see it makes sense and does follow whatever activities are taking place on the report server.  
    If you don't have these files, it means you changed the DefaultTraceSwitch to 0 in the ReportingServicesService.exe.config file in the bin directory or through SSMS. But I am guessing the logs are there, you just need to search more for them.
    You setup an http log by modifying the ReportingServicesService.exe.config. I don't think it will do you any good at this point to set one up.

    Sue

  • June 27, 2017 at 7:06 am

    #1948352

    Sue_H - Tuesday, June 27, 2017 6:59 AM

    p_cormack - Tuesday, June 27, 2017 1:58 AM

    Hi Sue

    Thanks for replying.
    Which log should I be looking in. I have a trace log from which I cannot make out an error but might be because I don't understand the contents wholly. I understand there should be a http log, which I don't seem to have. Should I be looking in there or will the trace log provide the information around permissions ? Do you know how to set up the http log?

    I am logging on as Administrator, and have tried Run as Administrator on IE, but to no avail.

    Many thanks

    Paul

    The reporting services log - the path on the server would be \Microsoft SQL Server\<instance name>\Reporting Services\LogFiles
    It's named ReportServerService_<timstamp>.log. That is the log you should check. You'll need to start going over it and you will eventually see it makes sense and does follow whatever activities are taking place on the report server.  
    If you don't have these files, it means you changed the DefaultTraceSwitch to 0 in the ReportingServicesService.exe.config file in the bin directory or through SSMS. But I am guessing the logs are there, you just need to search more for them.
    You setup an http log by modifying the ReportingServicesService.exe.config. I don't think it will do you any good at this point to set one up.

    Sue

    Thanks Sue. I will investigate further with the logs this evening.

    Paul

  • June 28, 2017 at 2:00 am

    #1948508

    p_cormack - Tuesday, June 27, 2017 7:06 AM

    Sue_H - Tuesday, June 27, 2017 6:59 AM

    p_cormack - Tuesday, June 27, 2017 1:58 AM

    Hi Sue

    Thanks for replying.
    Which log should I be looking in. I have a trace log from which I cannot make out an error but might be because I don't understand the contents wholly. I understand there should be a http log, which I don't seem to have. Should I be looking in there or will the trace log provide the information around permissions ? Do you know how to set up the http log?

    I am logging on as Administrator, and have tried Run as Administrator on IE, but to no avail.

    Many thanks

    Paul

    The reporting services log - the path on the server would be \Microsoft SQL Server\<instance name>\Reporting Services\LogFiles
    It's named ReportServerService_<timstamp>.log. That is the log you should check. You'll need to start going over it and you will eventually see it makes sense and does follow whatever activities are taking place on the report server.  
    If you don't have these files, it means you changed the DefaultTraceSwitch to 0 in the ReportingServicesService.exe.config file in the bin directory or through SSMS. But I am guessing the logs are there, you just need to search more for them.
    You setup an http log by modifying the ReportingServicesService.exe.config. I don't think it will do you any good at this point to set one up.

    Sue

    Thanks Sue. I will investigate further with the logs this evening.

    Paul

  • June 28, 2017 at 2:07 am

    #1948509

    p_cormack - Wednesday, June 28, 2017 2:00 AM

    p_cormack - Tuesday, June 27, 2017 7:06 AM

    Sue_H - Tuesday, June 27, 2017 6:59 AM

    p_cormack - Tuesday, June 27, 2017 1:58 AM

    Hi Sue

    Thanks for replying.
    Which log should I be looking in. I have a trace log from which I cannot make out an error but might be because I don't understand the contents wholly. I understand there should be a http log, which I don't seem to have. Should I be looking in there or will the trace log provide the information around permissions ? Do you know how to set up the http log?

    I am logging on as Administrator, and have tried Run as Administrator on IE, but to no avail.

    Many thanks

    Paul

    The reporting services log - the path on the server would be \Microsoft SQL Server\<instance name>\Reporting Services\LogFiles
    It's named ReportServerService_<timstamp>.log. That is the log you should check. You'll need to start going over it and you will eventually see it makes sense and does follow whatever activities are taking place on the report server.  
    If you don't have these files, it means you changed the DefaultTraceSwitch to 0 in the ReportingServicesService.exe.config file in the bin directory or through SSMS. But I am guessing the logs are there, you just need to search more for them.
    You setup an http log by modifying the ReportingServicesService.exe.config. I don't think it will do you any good at this point to set one up.

    Sue

    Thanks Sue. I will investigate further with the logs this evening.

    Paul

    I checked the logs but really couldn't find anything there. I entered my administrator account into the login screen again when it appeared and this time it went through to report manager (maybe I had been entering the wrong password previously or something else has changed). I got an error on the screen then saying I was unable to run scripts. I checked restricted sites (internet options) and saw the server name on there. I took it off and added it to trusted sites. I was able to access report manager fully ( with or without entering run as administrator).
    I will check later whether I can deploy reports and have asked Users whether that has fixed their issues (Reports are linked to asp .net application) or whether I need to investigate issues further.
    I think either an IE windows update or someone had moved the server name to restricted sites was the issue. I will investigate further.

    Thanks for your help Sue

  • June 30, 2017 at 8:23 am

    #1948944

    p_cormack - Wednesday, June 28, 2017 2:07 AM

    p_cormack - Wednesday, June 28, 2017 2:00 AM

    p_cormack - Tuesday, June 27, 2017 7:06 AM

    Sue_H - Tuesday, June 27, 2017 6:59 AM

    p_cormack - Tuesday, June 27, 2017 1:58 AM

    Hi Sue

    Thanks for replying.
    Which log should I be looking in. I have a trace log from which I cannot make out an error but might be because I don't understand the contents wholly. I understand there should be a http log, which I don't seem to have. Should I be looking in there or will the trace log provide the information around permissions ? Do you know how to set up the http log?

    I am logging on as Administrator, and have tried Run as Administrator on IE, but to no avail.

    Many thanks

    Paul

    The reporting services log - the path on the server would be \Microsoft SQL Server\<instance name>\Reporting Services\LogFiles
    It's named ReportServerService_<timstamp>.log. That is the log you should check. You'll need to start going over it and you will eventually see it makes sense and does follow whatever activities are taking place on the report server.  
    If you don't have these files, it means you changed the DefaultTraceSwitch to 0 in the ReportingServicesService.exe.config file in the bin directory or through SSMS. But I am guessing the logs are there, you just need to search more for them.
    You setup an http log by modifying the ReportingServicesService.exe.config. I don't think it will do you any good at this point to set one up.

    Sue

    Thanks Sue. I will investigate further with the logs this evening.

    Paul

    I checked the logs but really couldn't find anything there. I entered my administrator account into the login screen again when it appeared and this time it went through to report manager (maybe I had been entering the wrong password previously or something else has changed). I got an error on the screen then saying I was unable to run scripts. I checked restricted sites (internet options) and saw the server name on there. I took it off and added it to trusted sites. I was able to access report manager fully ( with or without entering run as administrator).
    I will check later whether I can deploy reports and have asked Users whether that has fixed their issues (Reports are linked to asp .net application) or whether I need to investigate issues further.
    I think either an IE windows update or someone had moved the server name to restricted sites was the issue. I will investigate further.

    Thanks for your help Sue

    This fixed all my issues. the Users and deployment all working now.

  • June 30, 2017 at 8:41 am

    #1948951

    Thanks for posting back. Sometimes when told nothing has changed, you need to take it with a grain of salt.

    Sue

  • June 30, 2017 at 9:59 am

    #1948967

    Sue_H - Friday, June 30, 2017 8:41 AM

    Thanks for posting back. Sometimes when told nothing has changed, you need to take it with a grain of salt.

    Sue

    Thanks Sue for taking the time to help me out.

Viewing 12 posts - 1 through 12 (of 12 total)

You must be logged in to reply to this topic. Login to reply