SQL reporting service fails on Sharepoint extranet Website
- Hi,
I was be able to configure the SQL reporting services 2005 to work and integrate them in intranet sharepoint site 2007 in my company.So, we decided to put them on internet facing sharepoint site using Form Authentication. However, the report service doesnt work. The error message we got is something like this :" Either Sharepoint Integrated mode is disabled or Report Server is using Trusted Account".
I dont know what's exactly going on here. I've been researching and found no solution. I would like an advice.
Thank you- Moved byMike Walsh MVPMVP, ModeratorWednesday, July 29, 2009 7:20 AMssrs (From:SharePoint - Setup, Upgrade, Administration and Operation)
All Replies
- SSRS questions in connection with SP go to SharePoint - Business Intelligence Moving this.
WSS FAQ sites: http://wssv2faq.mindsharp.com and http://wssv3faq.mindsharp.com
Total list of WSS 3.0 / MOSS 2007 Books (including foreign language) http://wssv3faq.mindsharp.com/Lists/v3%20WSS%20FAQ/V%20Books.aspx - Manh Le -
There are quite a few considerations to take in when deploying SSRS to an extranet type environment, particularly around security -- you can have issues authenticating to data sources and the report server db, particularly if you have two different domains, or even zones on the same domain (think DMZ).
Here is a good starting doc on MSDN: http://msdn.microsoft.com/en-us/library/ms159272.aspx. Take a look and post back with any questions.
Please click the Mark as Answer button if a post solves your problem! Hi,
Thank you for your reply
I read the article you gave above and get the the part of implementing security extension. I wonder should I implement that so my extranet users can have authenticated Ticket to the report server? I look through the examples, it seemed to me that it has nothing to do with my sharepoin authentication formPlease advice, thank you
BTW,
I found an error when I click directly on the report file on extranet site
The specified path refers to a SharePoint zone that is not supported. The default zone path must be used
Searching on the internet I found this
http://social.msdn.microsoft.com/Forums/en-US/sqlreportingservices/thread/029a2f68-098e-4a57-a8a8-5db099beca0e
I wonder if the post is true ? If so then we have no solution for Viewing the report on Extranet Sharepoint Site...
If the URL for the report server is not in the default zone (same zone as the SharePoint site you are using), then you will get this error.
Go to Central Admin > Operations > Global Configuration > Alternate Access Mappings and configure the URL you are using for report server access to be in the same zone
Reference:
http://msdn.microsoft.com/en-us/library/bb969101(SQL.90).aspx
Please click the Mark as Answer button if a post solves your problem!Hi,
Do you mean, that I have to get to that Alternate Access Mapping and Configure the public URL from Internet to Default? Im not very clear about this.
I just tried it and It said Public URL cant not be deleted. I wonder how outside people can hit my website if i change that to default instead of internet... or maybe Im misunderstading...
But let me clarify the way I setup the url of the report server
In the Configure report Server dialog box I set Report Virtual Directory to a site has port 50 http://myservername:50
In Sharepoint Admin Website, category :Reporting Service Integration ,I set Report Server web service URL the same as above http://myservername:50
The SQL Server, Web Server , Report Server are on the same machine. The machine hosts Public SP site also the other Sharepoint sites that we use inside our company
I tested the report webpart on every SP site that use inside our company, they worked fine. However, the webpart doesnt work Public Sharepoint Site and gives all the errors as I posted above. Am I still missing something?
Thank youDirect from the article I posted above, use the directions below and add the http://myservername:50 to the Alternate Access Mappings list and set the zone to Default. This should resolve the issue given the error message you are seeing. Post back if it resolves your issue or if you get another error message that we can use to get this working for you:
<From the MSDN article>:
Report Server Only Supports SharePoint Default ZoneSymptom: When you access a Reporting Services item via a URL that belongs to a SharePoint zone that is not the Default zone, the following error is encountered:
The specified path refers to a SharePoint zone that is not supported. The default zone path must be used.
Solution: In the Alternate Access Mappings section of the Operations tab in the SharePoint Central Administration Web site, configure the URL you are using for accessing Reporting Services items to be in the Default zone.
Please click the Mark as Answer button if a post solves your problem!- Hi,
I checked the Alternate Access Mapping and http://myservername:50 was already in there and in Default Zone.
when I accessed http://myservername:50 ,everything worked fine
However, still I have the problem with Internet Sharepoint Site when I access the file rdl, the message is the same: "The specified path refers to a SharePoint zone that is not supported. The default zone path must be used."
I think the problem is the URL of my Internet Sharepoint Site is not in Default Zone but Internet Zone. I could not configure the Internet Sharepint URL to be in Default Zone , It should be in Internet Zone since it is supposed to face the public.
Is there a work around for this?
Thank you - Did you find a workaround for this?
- use a webpartpage and deploy the report(use default zone rpt file address) in report viewer webpart on this page. and try to access this page using your public ip address.
- Reporting services only supports access via the default zone in AAM. You will get an error along the lines "The specified path refers to a SharePoint zone that is not supported" if you try to access a report from a non-efault zone. You can consider a workaround wherein multiple “Internal URLs” (Internet, intranet, etc.) for the same web application use a single “Public URL for Zone” all in the AAM default zone. Full AAM support is being considered for the next version post-SSRS 2008.
-Ivan
Ivan Sanders http://www.linkedin.com/in/iasanders http://dimension-si.com/blog
