deployment not working

I have a freshly installed reporting server/sql server and I have an older
visual studio reporting project.
Now I wanted to change the deployment url to the new server, but whenever I
try to deploy I get the message: "The permissions granted to user 'user' are
insufficient for performing this operation."
What permissions and where do I need to change to get this right?Give the user 'user' the Content Manager role on the folder to which you
want to deploy.
-Lukasz
This posting is provided "AS IS" with no warranties, and confers no rights.
"Servé La" <blabla@.bestaatniet.nl> wrote in message
news:O0%23tvvk$EHA.2580@.TK2MSFTNGP15.phx.gbl...
>I have a freshly installed reporting server/sql server and I have an older
> visual studio reporting project.
> Now I wanted to change the deployment url to the new server, but whenever
> I
> try to deploy I get the message: "The permissions granted to user 'user'
> are
> insufficient for performing this operation."
> What permissions and where do I need to change to get this right?
>

Deploying Reports with WSS 3.0 integrated mode

Hi ,

I am trying to deploy reports through visual studio. In the Target server URL, specified the url of the report server as http://<localhost>:<portnumber>/reportserver/Shared Documents/. But
When i deploy it asks for username and password. when i provide them, again login screen appears. Finally deployment fails when i press cancel.

Did anybody face this kind of problem ?

Thanks & Regards,
Kiran Kumar

For deploying reports to a Report Server in SharePoint Integrated mode use the updated Report Designer that ships with SQL 2005 SP2 CTP3. Additionally, it is reco'd to deploy to the SharePoint Document Library with settings as follows:
TargetDataSourceFolder: http://<MyServer>/<mySharePointsite>/Shared Documents/
TargetReportFolder: http://<MyServer>/<mySharePointsite>/Shared Documents/
TargetServerURL: http://<MyServer>/<mySharePointsite>/

Hope this helps.

thanx,
Prash

|||

Can you also check for the following in the web.config file of the SharePoint web site:

- Do you see multiple entries looking like (?):

<location path="_vti_bin/ReportServer/ReportServiceAuthentication.asmx">
<system.web>
<authorization>
<allow users="*" />
</authorization>
</system.web>
</location>

There should be only one such entry for the ReportServiceAuthentication.asmx in the web.config. Please ensure there is only one such entry and retry deploying.

This is a bug that we are working on fixing for RTM.

Deploying Report Server behind web servers

We'd like to deploy our report servers behind our web tier in the app tier
in order to prevent our clients from being able to use url access directly.
My main concern has to do with a chance that a client may attempt to alter
the content of report parameters or otherwise probe around.
Our web code is able to forward requests to the report server and render
reports correctly, but toolbar functionality seems to be broken. The web
developer tells me that the toolbar functionality is too stateful, so
paging (as an example) won't work.
Is what we're trying to do (request forwarding) unsupported? Are my fears
regarding exposing the report server in our DMZ unwarranted? If so, I must
be missing something.What about building your own interfaace or getting the Report Stream from
Reporting Webservice to Qrite the Stream to the browser ? There you could
lock down your reporting server and connect to the RS with special lockedup
credentials.
HTH, Jens Suessmeyer.
--
http://www.sqlserver2005.de
--
"JoeA" <joea@.nospam.net> schrieb im Newsbeitrag
news:Xns963D69BAFC14Emailmailcom@.207.46.248.16...
> We'd like to deploy our report servers behind our web tier in the app tier
> in order to prevent our clients from being able to use url access
> directly.
> My main concern has to do with a chance that a client may attempt to alter
> the content of report parameters or otherwise probe around.
> Our web code is able to forward requests to the report server and render
> reports correctly, but toolbar functionality seems to be broken. The web
> developer tells me that the toolbar functionality is too stateful, so
> paging (as an example) won't work.
> Is what we're trying to do (request forwarding) unsupported? Are my fears
> regarding exposing the report server in our DMZ unwarranted? If so, I
> must
> be missing something.|||Thanks for the reply. We have considered that - however we didn't want to
have to recreate all of the goodies in the toolbar.
"Jens Süßmeyer" <Jens@.Remove_this_For_Contacting.sqlserver2005.de> wrote
in news:#1t7uEQRFHA.2136@.TK2MSFTNGP14.phx.gbl:
> What about building your own interfaace or getting the Report Stream
> from Reporting Webservice to Qrite the Stream to the browser ? There
> you could lock down your reporting server and connect to the RS with
> special lockedup credentials.
> HTH, Jens Suessmeyer.
> --
> http://www.sqlserver2005.de
> --
>