SSRS works inside GP2010 but not with separate Browser

(0) Share

Report

Posted on by Accounting Department

1,540

I am able to view some SQL Reports in GP2010 Metrics and open them in a Browser from the Homepage. However if I just open a browser, and select a report, the reports all come up blank with no data.

It works on the SQL Server (2008 R2) while I am logged in with my Admin account, but not from my workstation while I am logged in with my domain account. I have given my domain user poweruser access to all the reports in SQL Mgmt Studio and access to all the folders and reports in SSRS.

Any ideas? I am connecting to a test server.

*This post is locked for comments

All responses (3)

Answers (0)

Jason Larson 45 on at

Like (0)

Report

Re: SSRS works inside GP2010 but not with separate Browser

You may need to use integrated security = false and a service account in the data connections if you are not using Kerberos.

If you decide that you want to use Kerberos here is a blog:

blogs.msdn.com/.../microsoft-dynamics-gp-and-kerberos-do-you-need-it.aspx
Rob Bernhardt on at

Like (0)

Report

Re: SSRS works inside GP2010 but not with separate Browser

barmeh,

As Mike mentioned, I'm guessing that this is a security issue. If you're unable to see the actual error, you can open SQL Management Studio, choose the SRS instance, and set EnableRemoteErrors = true. This will allow you to see the error details and debug the issue.

Thanks

Rob
Mike Smith 6,840 on at

Like (0)

Report

Re: SSRS works inside GP2010 but not with separate Browser

Are the reports coming up blank or are they producing an error?

An error will denote an actual issue with the report or security (in this case security since the reports should not be the culprit). A blank report can be tied to incorrect parameters.

To verify the security settings, you could go into one of the Data Sources used on the report and hard-code a user and password that you know has the proper SQL permissions and re-run the report. If the report then runs, there is something not right with the SQL security.