Date parsed: 07/05/2008 07:56:59
Date: Wed, 07 May 2008 07:56:59 GMT
Hi Steve,
After discussing with other SQL Engineers, they think that the problem is
likely due to the SSRS integration with SPS has something not configured
correctly. They'll suggest you try go through the steps for configuring
reporting service with MOSS/WSS, here I pasted the suggested steps from
them:
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
STEP 1:
Installing Reporting Services:
========================
We can install SQL 2005 Server with all the features or install just the
Reporting
Services. In order to get the integration feature in Reporting Services we
need to
install SP2 for Reporting Services.
Installing MOSS / WSS3.0 on Reporting Services SERVER1
==============================================
Install MOSS / WSS3.0 on SERVER1.
Installing SharePointRS Add-in:
=========================
Download the Add-in
<http://www.microsoft.com/downloads/details.aspx?familyid=1E53F882-0C16-4847
-B331-132274AE8C84&displaylang=en>
We need to install the Add-in on SERVER1
STEP2:
Create New Web App on the MOSS / WSS3.0 server:
==========================================
We need to create Web App before we could configure any thing Further.
Configuring Reporting Services for SharePoint Integration:
==============================================
- Open ?onfigure Report Server?from the SERVER1.
- From ?eport Server Virtual Directory?Create a new Web Site for Report
Server with a Different Port.
- We can Skip the ?eport Manager Virtual Directory?
- From ?indows Service Identity?Use the SharePoint Services account to
configure the ?indows Service Identity?
- From ?eb Service Identity?created a new AppPool for the Report Server web
site. Make sure you use the SharePoint Services account.
- Next step is to create a Reports Database on the Database Server. While
creating a New Reports Database make sure you create it with ?harePoint
Integrated?Mode.
- Once all these steps are complete the ?harePoint Integration?shows up
with tick next to saying that the integration is configured with SharePoint.
Now to confirm the configuration browse to the reports server web site
which you created Ex : <http://SERVER1:8080/ReportsServer>
You now should be able to browse to the report server and it should display
the web app which we created earlier.
Configure SharePoint Central Administrator Site for Reporting Services:
========================================================
- From the Application management -> Reporting Services -> Click on ?anage
Integration Settings?
- Type in the report server URL and Select Windows Authentication. Click
OK- Now select the ?rant Database Access?and then type in the Reporting
Services Server name and then click OK. Then it would prompt for User name
and password. Specify the user account. This account I used to retrieve the
Reporting services from the SERVER1. I would use the SharePoint Services
account since I have using a sigle account for integrating.
- Click on the ?et Server Defaults?you should see the defaults value for
the Reporting Services.
Configure the SQL Reporting Services Web Part on the Portal:
=================================================
Now we can add the SQL Reporting Services Web and you should be able to get
it working fine.
<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<
Sincerely,
Steven Cheng
Microsoft MSDN Online Support Lead
Delighting our customers is our #1 priority. We welcome your comments and
suggestions about how we can improve the support we provide to you. Please
feel free to let my manager know what you think of the level of service
provided. You can send feedback directly to my manager at:
msdnmg@microsoft.com.
==================================================
Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif
ications.
==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
>From:
stcheng@online.microsoft.com (Steven Cheng [MSFT])
>Organization: Microsoft
>Date: Mon, 05 May 2008 08:48:11 GMT
>Subject: RE: Unable to add Web Reference in Visual Studio 2008 on Win 2003
>
>Thanks for your reply Steve,
>
>Well, from the webbrowser behavior, that means the wsdl page doesn't
>display. Also, the further information about MOSS integrated is very
>important. I think the problem is likely due to the MOSS integrated
>envirionment. I'll do some further research on this and let you know if I
>get any new information.
>
>Sincerely,
>
>Steven Cheng
>
>Microsoft MSDN Online Support Lead
>
>
>Delighting our customers is our #1 priority. We welcome your comments and
>suggestions about how we can improve the support we provide to you. Please
>feel free to let my manager know what you think of the level of service
>provided. You can send feedback directly to my manager at:
>msdnmg@microsoft.com.
>
>==================================================
>Get notification to my posts through email? Please refer to
>http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#noti
f
>ications.
>
>==================================================
>This posting is provided "AS IS" with no warranties, and confers no rights.
>
>--------------------
>>Thread-Topic: Unable to add Web Reference in Visual Studio 2008 on Win
2003
>>thread-index: AcisMezRccDUJO4hSL+fGFjK0L0g+Q==
>>X-WBNR-Posting-Host: 207.46.19.197
>>From: =?Utf-8?B?ZXplZ2V0LmNvbQ==?= <ezeget.com2007@community.nospam>
>>References: <4F559407-B7E9-415E-B2D1-61F7044BC299@microsoft.com>
><ZfFq67$qIHA.1784@TK2MSFTNGHUB02.phx.gbl>
>>Subject: RE: Unable to add Web Reference in Visual Studio 2008 on Win 2003
>>Date: Fri, 2 May 2008 01:53:00 -0700
>
>>Steven,
>>
>>In fact if you read the title of the thread it said
>>UNABLE TO ADD WEB REFERENCE IN VISUAL STUDIO 2008
>>
>>That means I am trying to add a web reference and Visual Studio itself is
>>throwing the error about
>>
>>> >C:\Program Files\Microsoft Visual Studio 9.0\VC>wsdl.exe
>>> >http://localhost/_vti_b
>>> >in/ReportServer/ReportService2006.asmx?WSDL
>>> >Microsoft (R) Web Services Description Language Utility
>>> >[Microsoft (R) .NET Framework, Version 2.0.50727.1432]
>>> >Copyright (C) Microsoft Corporation. All rights reserved.
>>> >Error: There was an error processing
>>> >'http://localhost/_vti_bin/ReportServer/Rep
>>> >ortService2006.asmx?WSDL'.
>>> > - The document at the url
>>> >http://localhost/_vti_bin/ReportServer/ReportService
>>> >2006.asmx?WSDL was not recognized as a known document type.
>>> >The error message from each known type may help you fix the problem:
>>> >- Report from 'DISCO Document' is 'Root element is missing.'.
>>> >- Report from 'WSDL Document' is 'There is an error in XML document
(0,
>>> 0).'.
>>> > - Root element is missing.
>>> >- Report from 'XML Schema' is 'Root element is missing.'.
>>> >
>>
>>Hope that makes it clear.
>>
>>In response to your test to
>>browse to the page in browser
>>
>>if I go to
>>http://localhost/_vti_bin/ReportServer/ReportService2006.asmx
>>
>>I get the supported operations, but if I add ?WSDL
>>
>>I just get a blank screen. If it is an error on the server side do you
>have
>>any suggestions how to fix it please. It is a MOSS Site that I am using
>Deep
>>Integration with SSRS.
>>
>>--
>>Steve G
>>
>>>> ><add verb="*" path="*.vsdisco"
>>> >type="System.Web.Services.Discovery.DiscoveryRequestHandler,
>>> >System.Web.Services, Version=1.0.3300.0, Culture=neutral,
>>> >PublicKeyToken=b03f5f7f11d50a3a" validate="false"/>
>>> >
>>> >in there?!!!!
>>> >
>>> >--
>>> >Steve G
>>> >
>>>
>>>
>>
>
>
