How to Deploy Report on Remote Server..

Hi,

I m getting following error while deploying report on remote server...

Error 3 The permissions granted to user 'ZENITH\BalwantPatel' are insufficient for performing this operation. 0 0

The following setting i have on my remote server.

Configure Report Server:

Report Server Virtual Directory: Default

Report Manager Virtual Directory: Default

Windows Service Identity:
Service Name: Report Server
Service Account: Domain\Administrator

Windows Account: Domain\Administrator.

Web Service Identity : ASP.NET Service Account: ServerName\ASPNET

I m creating Report on my local machine as Domain\Balwant Patel. and Trying to deploy on other server on the same domain....

I dont know What settings do need to change on webserver or on my local machine.

Thank you,

Ballu.

hello,

I see u have not configured ur report server. Go to "start" -- "sql server 2005" -- "configuration tools" -- "reporting services configuration". Go thru it step by step and configure it. Once you have done it, you should have "content manager" permission to deploy on the remote server. Needlesss to say, I am assuming you have given the correct target URL for deploment. For "content manager" persmission settings, read http://msdn2.microsoft.com/en-us/library/aa337491.aspx.

I hope it helps...

Regards..

|||

Hi AsianIndian,

Thank you very much for your response....The Link That u give me is very useful...Now I get The Idea How to setup permission on SQL Server Reporting Service...I configured Report Server fine...but I don't know how to setup permission through SQL Server Management Studio...I have one problem when I m trying to connection to my Report Server Through SQL Server Management Studio... Initially when i m trying to connection Report Server on my local machine...i m getting the error that there is not enough permission on C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\Temporary ASP.NET Files this folder to machine\ASP.NET...So I give full permission to ASP.NET user....so I thought the same problem may occure on my deplyoment server...but I get different error...the error was internal server and the error and even the error was not shown correctly...but I found somewhere on the forums that I have to remove <configuration xmlns> attribute from the configuration node from Drive:\Program Files\Microsoft SQL Server\MSSQL.3\Reporting Services\ReportServer\web.config.

Regards,

Balwant Patel.

How to deny information schema views...

Hello, all. I created a login and granted the user access to my sql 2005
database. well when the user creates his odbc dsn to access the database, I
discovered he can also see the INFORMATION_SCHEMA views. What gives? How
can I deny him access to these objects. He should have access to the db I
granted him.
Help!!!!!!!!
RozThe Information Schema views in SQL Server 2005 should only return for the
user information about the objects the user actually has access to. While
this was a prominent information disclosure issue in SQL Server 2000, it's
not as wide open in SQL Server 2005. They are provided for SQL-92 compliance
so that users can query the metadata/schema of the database without having
to query the system tables. Is there a reason you want to block access to
them?
K. Brian Kelley, brian underscore kelley at sqlpass dot org
http://www.truthsolutions.com/

> Hello, all. I created a login and granted the user access to my sql
> 2005 database. well when the user creates his odbc dsn to access the
> database, I discovered he can also see the INFORMATION_SCHEMA views.
> What gives? How can I deny him access to these objects. He should
> have access to the db I granted him.
> Help!!!!!!!!
> Roz|||Hello Roz,
You can't hide the fact the views exist as far as I can tell, but if you
look at what he see, it won't be much if anything. Basically he has to be
able to the see the metadata's metadata, but he shouldn't be able to see
the metadata itself unless you start granting him rights to do so (e.g.,
VIEW DEFINITION).
Thanks!
Kent Tegels
DevelopMentor
http://staff.develop.com/ktegels/|||Thanks for reply. I want to block access because as my users create their
ODBC DSNs, they can open these tables and **change** data. I've tried it an
d
it works. Very scary.
Roz
"K. Brian Kelley" wrote:

> The Information Schema views in SQL Server 2005 should only return for the
> user information about the objects the user actually has access to. While
> this was a prominent information disclosure issue in SQL Server 2000, it's
> not as wide open in SQL Server 2005. They are provided for SQL-92 complian
ce
> so that users can query the metadata/schema of the database without having
> to query the system tables. Is there a reason you want to block access to
> them?
>
> K. Brian Kelley, brian underscore kelley at sqlpass dot org
> http://www.truthsolutions.com/
>
>
>|||Kent,
Simply having the "public" role, gets him access to these tables. He (I)
was even able to open these tables say in Access thru ODBC, and potentially
change the data. Scary.
Roz
"Kent Tegels" wrote:

> Hello Roz,
> You can't hide the fact the views exist as far as I can tell, but if you
> look at what he see, it won't be much if anything. Basically he has to be
> able to the see the metadata's metadata, but he shouldn't be able to see
> the metadata itself unless you start granting him rights to do so (e.g.,
> VIEW DEFINITION).
> Thanks!
> Kent Tegels
> DevelopMentor
> http://staff.develop.com/ktegels/
>
>|||I am wondering if you are seeing something else.
Could you please give us the steps you used to open
information schema views and change the underlying data on
SQL Server 2005? Which views, data in what columns?
As far as I know, what you are saying is not possible.
If it is actually other tables you are referring too, I
think you have a permissions issue with how you have
security set up. I think that's likely the issue anyway.
-Sue
On Tue, 20 Mar 2007 16:51:05 -0700, Roz
<Roz@.discussions.microsoft.com> wrote:
[vbcol=seagreen]
>Thanks for reply. I want to block access because as my users create their
>ODBC DSNs, they can open these tables and **change** data. I've tried it a
nd
>it works. Very scary.
>Roz
>"K. Brian Kelley" wrote:
>