SSRS report dies with error

Hi Chris,

Good day.

I think you can use SSRS URL format first. make sure reporting service report is working, then you can setup the proxy.

For SSRS URL, you only need to config T_DEFAULTS: SSRS_URL field.

Is your report working in IE?

have fun.

Ben

Unknown said:

I think you can use SSRS URL format first. make sure reporting service report is working, then you can setup the proxy.

For SSRS URL, you only need to config T_DEFAULTS: SSRS_URL field.

Is your report working in IE?

Yes, the SSRS_URL variable is set to "http://actedata/Reports", which, if I open in IE, opens Report Manager. I can click through the folder structure and open my new report, and it generates fine.

Today I seem to be getting closer. When I try to run the report from Tessitura, I get this error:

Next, I see this in event viewer:

"It is not possible to run two different versions of ASP.NET in the same IIS process. Please use the IIS Administration Tool to reconfigure your server to run the application in a separate process."

In IIS, TessituraSSRSProxy is running under ASP.NET 1.1.4322, which is grayed out and can't be changed. Is your Proxy running under that version? Any other suggestions?

Thanks!

Unknown said:

The URL in SSRS_URL (T_DEFAULTS) needs to be the Report Server (http://server/ReportServer), not the Report Manager (http://server/Reports).

Thanks for your reply. I've made that update to t_defaults, logged my client in/out, and am still getting the "Server application unavailable" message pictured above.

If I just try to load the SSRS_URL in a browser, I get this. Is this what I should see?

Unknown said:

That might mean that the ReportServer is not configured on the web server (IIS) as an application, or the permissions aren’t set appropriately on the web server or the virtual directory to be able to execute scripts.

 

In IIS, I see that ReportServer appears under Application Pools and Web Sites -> Default Web Site. Under the latter, I see entries for both Reports and Report Server. Both seem to be set up as Applications. Reports had already been set up to allow execution of Scripts & Executables, though Report Server had not. I added that setting to ReportServer, clicked Apply, and tried running the report again. Same result. Does the reporting services service (or something else) need to be restarted?

Thanks.

Hi Chris,

Good day.

To make reporting service work,

1, normally start from sql server 2005-->configuration tools-->reporting service configuration (this should be done from sql reporting service instance machine<actedata>, you need the admin login to do this)

2,after you setup this admin account, you need to go back IE, type in http://localhost/reports (I assume you use the default website), in the report manger, choose the "Site Settings", add some new users, especially yourself, then you do not need admin account any more. You can add yourself as "System All".  (this part still need to be done at instance machine)

3,then you can go to the report folder to setup individaul report security. add persons and groups with permissions.(this part can be done at domain machines)

you can play with all those steps, it will take a bit time then you will know the whole thing.

For the reporting service, there are two parts.

1, part 1 is report manager, this part controls the security configuration. the link is something like http://reportingServiceMachine/reports

2, part 2 is for report usage, this part have an interface like FTP, when you try to consume the reports, you have to go through this part. http://reportingServiceMachine/reportserver

after you make all things working, you can take a look of this, it is about dropdown list selection:

http://www.tessituranetwork.com/COMMUNITY/forums/p/315/1707.aspx#1707

have fun

Ben

Unknown said:

1, normally start from sql server 2005-->configuration tools-->reporting service configuration (this should be done from sql reporting service instance machine<actedata>, you need the admin login to do this)

Thanks for the screenshots. We had done a lot of SSRS setup (possibly not all correctly!) last fall when we went live with Tessitura, but we haven't used SSRS yet, so as we are just getting started, we had missed the Execution account along the way. I assume I will need that for scheduled reports.

Unknown said:

2,after you setup this admin account, you need to go back IE, type in http://localhost/reports (I assume you use the default website), in the report manger, choose the "Site Settings", add some new users, especially yourself, then you do not need admin account any more. You can add yourself as "System All".  (this part still need to be done at instance machine)

This part is unfamiliar to me. Will I need to set up all my report users again in SSRS? Won't permissions be inherited from AD?

Unknown said:

1, part 1 is report manager, this part controls the security configuration. the link is something like http://reportingServiceMachine/reports

This is working for us. I can access this URL and run reports individually. Launching a report from teh Tessitura report menu is what is not working now.

Unknown said:

2, part 2 is for report usage, this part have an interface like FTP, when you try to consume the reports, you have to go through this part. http://reportingServiceMachine/reportserver

This is sort of a plain text interface. If I wanted to access a report from IE via an URL I sent to a non-Tessitura Executive, for example, would that be the path to use (substituting servername for localhost of course)?

Unknown said:

after you make all things working, you can take a look of this, it is about dropdown list selection:

Thanks for that link! And the rest of your post. Very informative.

Unknown said:

1, normally start from sql server 2005-->configuration tools-->reporting service configuration (this should be done from sql reporting service instance machine<actedata>, you need the admin login to do this)

Thanks for the screenshots. We had done a lot of SSRS setup (possibly not all correctly!) last fall when we went live with Tessitura, but we haven't used SSRS yet, so as we are just getting started, we had missed the Execution account along the way. I assume I will need that for scheduled reports.

Unknown said:

2,after you setup this admin account, you need to go back IE, type in http://localhost/reports (I assume you use the default website), in the report manger, choose the "Site Settings", add some new users, especially yourself, then you do not need admin account any more. You can add yourself as "System All".  (this part still need to be done at instance machine)

This part is unfamiliar to me. Will I need to set up all my report users again in SSRS? Won't permissions be inherited from AD?

Unknown said:

1, part 1 is report manager, this part controls the security configuration. the link is something like http://reportingServiceMachine/reports

This is working for us. I can access this URL and run reports individually. Launching a report from teh Tessitura report menu is what is not working now.

Unknown said:

2, part 2 is for report usage, this part have an interface like FTP, when you try to consume the reports, you have to go through this part. http://reportingServiceMachine/reportserver

This is sort of a plain text interface. If I wanted to access a report from IE via an URL I sent to a non-Tessitura Executive, for example, would that be the path to use (substituting servername for localhost of course)?

Unknown said:

after you make all things working, you can take a look of this, it is about dropdown list selection:

Thanks for that link! And the rest of your post. Very informative.

Hi Chris,

Good day.

You are welcome.

Let me explain a bit about webBrowser in application. In Visual Studio if you create a windows form application, you can drag and drop a WebBrowser on the form, it will work like IE. Same thing is happening with Tessitura SSRS custom report. Whatever types you are using POST or URL, they are still same thing: webpages in an application. So it will always have the registry problem.

 So actually Tessitura hasn't setup any security to the reporting service reports at all.

At security point, the difference between URL and POST, is URL format showing you the real link , and POST format displaying the proxy web page link only, when you right click the mouse.

So do you think we should setup SSRS security? The answer is Yes.

Unknown said:

This part is unfamiliar to me. Will I need to set up all my report users again in SSRS? Won't permissions be inherited from AD?

So you need to setup permissions and roles. SSRS can talk to AD, and all users can come from AD, but you have to tell SSRS who is going to do what.

You have to play with report manager, it needs a bit time to figure out what you should do, as this is a custom part.

Black Belt Administration: Reporting Services Configuration Manager

http://www.databasejournal.com/features/mssql/article.php/3683406/Black-Belt-Administration--Reporting-Services-Configuration-Manager.htm

Unknown said:

This is sort of a plain text interface. If I wanted to access a report from IE via an URL I sent to a non-Tessitura Executive, for example, would that be the path to use (substituting servername for localhost of course)?

Yes.

have fun.

Ben

Ryan describes a different security method in his webinar, I think, but he quickly covered a lot of ground re: security. It's big topic.

Thanks for all the replies!