Solved

Reporting Services reports failing - connection could not be made

Posted on 2009-05-20
18
1,041 Views
Last Modified: 2012-05-07
Hi All,

Have a Windows Server 2003, Standard edition R2 running:
SQL Server 2005 and SharePoint 3.0 Central Admin - integrated mode

Configured Report Server and have tried to run reports in SharePoint through Visual Studio 2005.  When try to build a report, I get the error 'A connection could not be made to the report server http://sqlserv:8080/ReportingServ'  

I have gone through numerous articles but unfortunately pulling my hair out.  I get various authentication issues so no doubt this is IIS or central admin related.  Have had to change IIS to basic authentication to be able to browse the URL.

When I browse to the URL http://sqlserv:8080/ReportingServ, this works fine.

Any help would be greatly appreciated
0
Comment
Question by:buddles
  • 9
  • 5
  • 2
18 Comments
 
LVL 11

Expert Comment

by:indianguru2
ID: 24431054
What permissions did you give to the ReportServer in the IIS?
0
 

Author Comment

by:buddles
ID: 24431182
The reportServer in IIS now has Integrated Windows authentication.  Should reporting services only be affected by permissioning to the ReportServer tree or does the default server also play a role?

Thanks
0
 
LVL 11

Assisted Solution

by:indianguru2
indianguru2 earned 250 total points
ID: 24431244
If you give the permission to the Default WEb Site... it will update the permission to all the WEb Shares below it... If you have custom permission set on any web share it will ask before updating that share.
What access have you given to Users on Reporting Services?

0
 

Author Comment

by:buddles
ID: 24431279
Sorry to sound naive but can you elaborate?
0
 

Author Comment

by:buddles
ID: 24434341
Ok.  Have reinstalled Reporting Services.  Things I have found:
When IIS is set to Integrated Windows Authentication, I can browse to http://sqlserv:8080/reportingserv.
However I cannot browse from the SQL Server to my Intranet site http://intranet which is our main SharePoint site.  I can however from a normal desktop.
When IIS for Intranet site and ReportServer are set to Basic Authentication I can browse to http://intranet locally from the SQL Server.  How can I get over this problem?  Any idea?

I followed the install document for integrated mode and configure SP Central Admin.  When I configure Reporting Services Integration it says to set the Autherntication mode to Trusted Acoount.  I then set Grant database to username domain\sqladmin (which is an admin account).
When i then try to set server defaults I get the error detailed below.  However, the error points to the domain\administrator account not the sqladmin account!  How and why?

If I set the Authentication Mode in Reporting Services Integration as before but this time to Windows Authentication, it works fine!

Please help :)  Clearly permissions are not configured correctly but am lost where to now look.
An unexpected error occurred while connecting to the report server. Verify that the report server is available and configured for SharePoint integrated mode. --> System.Web.Services.Protocols.SoapException: The permissions granted to user 'domain\administrator' are insufficient for performing this operation. ---> Microsoft.ReportingServices.Diagnostics.Utilities.AccessDeniedException: The permissions granted to user 'domain\administrator' are insufficient for performing this operation.

   at Microsoft.ReportingServices.SharePoint.Server.SharePointTrustedUserVerification.VerifyTrustedUserAccessToWssContent(String processAccountName, String userName, String item)

   at Microsoft.ReportingServices.SharePoint.Server.SharePointTrustedUserVerification.VerifyTrustedUserAccess(String processAccountName, String userName, String item)

   at Microsoft.ReportingServices.Library.TrustedAccountVerification.VerifyTrustedAccountAccess(String userName, String item)

   at Microsoft.ReportingServices.WebServer.WebServiceHelper.ExtractWebUserInfo(TrustedUserHeader userHeader, String item)

   at Microsoft.ReportingServices.WebServer.ReportingService2006.Initialize(TrustedUserHeader userHeader, String item)

   --- End of inner exception stack trace ---

   at Microsoft.ReportingServices.WebServer.ReportingService2006.Initialize(TrustedUserHeader userHeader, String item)

   at Microsoft.ReportingServices.WebServer.ReportingService2006.ListSecureMethods() 

Troubleshoot issues with Windows SharePoint Services. 

Open in new window

0
 
LVL 11

Expert Comment

by:indianguru2
ID: 24438743
Go to  http://sqlserv:8080/reports or the Report Manager URL.
On the Top Right Corner of the Page you will see "Site Settings". Open that Link.
In the Site Settings Page, at the bottom you will see
Security --> Configure site-wide security... Open that.
Before that it is advisable to create Group in your Domain who should have access to Reports.
Say, you create a User Group SQLReports in Your Domain. The idea of creating this is to minimize the effort of giving access to another user next time. All you need to add the new user to the group and you can skip the process below.
Now Click on the New Role Assignment on the toolbar in the Configure site-wide security.
Enter the Group Name like DOMAIN\SQLReports.
Select the roles both that you would like to give.. in your case you can select both,
Click on OK.
Also do this..
Open Start Menu\Programs\Microsoft SQL Server 2005\Configuration Tools-->SQL Server Surface Area Configuration
In that you will see a Link called "Add a New Administrator"
Enter the domain\sqladmin in the User to Provision box on top and select all "Member of the SQL Server SysAdmin role on SERVERNAME and move it on the other side using >.
Click OK and restart SQL Server.
Try doing your test now and let me know ...

 

 
0
 

Author Comment

by:buddles
ID: 24439571
Thank you again for your response.

When I go to  http://sqlserv:8080/reportingserv in IE7, I do not see any Site settings options?  Am I looking in the right place?
0
 
LVL 11

Expert Comment

by:indianguru2
ID: 24441357
Then You yourself don't have rights ...
Do the second part and add your username first as administrator :)
Open Start Menu\Programs\Microsoft SQL Server 2005\Configuration Tools-->SQL Server Surface Area Configuration
In that you will see a Link called "Add a New Administrator"
Enter the domain\sqladmin in the User to Provision box on top and select all "Member of the SQL Server SysAdmin role on SERVERNAME and move it on the other side using >.
Click OK and restart SQL Server.
 
0
How to improve team productivity

Quip adds documents, spreadsheets, and tasklists to your Slack experience
- Elevate ideas to Quip docs
- Share Quip docs in Slack
- Get notified of changes to your docs
- Available on iOS/Android/Desktop/Web
- Online/Offline

 
LVL 11

Expert Comment

by:indianguru2
ID: 24441368
Hey ...
Not Reportserver ... go to  http://sqlserv:8080/reports ... this is the Manager wesite ...
0
 

Author Comment

by:buddles
ID: 24442502
Am I correct in saying that report Manager is only available in Standard mode only, not SharePoint Integrated mode?
0
 

Author Comment

by:buddles
ID: 24451637
Can confirm that Report Manager is not configured in Integrated mode.  Can anyone offer any assistance?
0
 

Author Comment

by:buddles
ID: 24473100
Can anybody help please?
0
 

Author Comment

by:buddles
ID: 24502798
Can anybody help with the question please?  

I have moved a step closer and now have report services working (somehow!) but have issues with deploying reports (model) via Visual Studio 2005.  I can deploy a report if using Basic authentication in IIS but when using Integrated Windows  authentication, it prompts for logon credentials and nothing works...  If I set Basic authentication then users get prompted for password details which is not ideal...
0
 
LVL 22

Assisted Solution

by:cj_1969
cj_1969 earned 250 total points
ID: 24518111
If you remove WIA and it is not working.
AND you MUST enable basic under authentication to get it working  ...
THEN
This tells me that you are not using the client credentials.
This being the case then the credentials are going to be provided by IIS which means either the anonymous user account or the application pool logon account.  

Based on this, we need to determine why basic authentication is needed.  This implies that something is not communicating using the default MS protocols or that there are 3 stages of communication so that Kerberos authentication is not working.  

Check your connection strings ... do you have any server names entered using a FQDN that is not part of the LAN?  If you do then this will prevent the applications from sending the passwords in encrypted format as MS apps will not pass encrypted credentials over the Internet (this is determined by a comparison of the destination URL or machine with the one it is on).  This would explain why BASIC is working and WIA is not ... WIA will not work (unless in conjunction with BASIC) as the credentials are encrypted by default.
0
 

Accepted Solution

by:
buddles earned 0 total points
ID: 24526673
Not sure how to go on this one.  Reporting Services started working today after a server reboot.  Authentication is working fine it seems although nothing has been changed...

Thanks to those who responded.
0
 
LVL 22

Expert Comment

by:cj_1969
ID: 24526739
Funny how a reboot does that some times.
Sometimes cached information can mess things up and a reboot clears it so that things start working.
0

Featured Post

How your wiki can always stay up-to-date

Quip doubles as a “living” wiki and a project management tool that evolves with your organization. As you finish projects in Quip, the work remains, easily accessible to all team members, new and old.
- Increase transparency
- Onboard new hires faster
- Access from mobile/offline

Join & Write a Comment

In this article I will describe the Copy Database Wizard method as one possible migration process and I will add the extra tasks needed for an upgrade when and where is applied so it will cover all.
International Data Corporation (IDC) prognosticates that before the current the year gets over disbursing on IT framework products to be sent in cloud environs will be $37.1B.
Familiarize people with the process of retrieving data from SQL Server using an Access pass-thru query. Microsoft Access is a very powerful client/server development tool. One of the ways that you can retrieve data from a SQL Server is by using a pa…
Via a live example, show how to extract information from SQL Server on Database, Connection and Server properties

757 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

21 Experts available now in Live!

Get 1:1 Help Now