can we deploy RDL files into report server without using web services through .Net

how can we deploy the reports into report server with out using web services from .Net. Is it possible.

Hi vidya
It is possible, after the initial deployment and folders were created. You could do the following:
Browse to your reportserver. Normally [server]/reports
Browse to the report and click on it. Select the report's 'Properities' Tab. Under the heading 'Report Definition' are 2 options 'Edit' and 'Update'. Use the 'Update' to upload the new rdl file. This will deploy a new version.
Hope this helps
,l0n3i200n

Can not Subscribe a Report

Hi,

I just create a report using Whidbey and deploy it to the Project reportserver. And I can access that report correctly, but I can not subscribe that report, what's going on? Additional, I create that report using Shared Data Source (connected to Analysis Service of my TFS DT) which I created in Whidbey. The exception info is below:

The current action cannot be completed because the user data source credentials that are required to execute this report are not stored in the report server database. (rsInvalidDataSourceCredentialSetting)

Thanks.

The report is set up for Integrated Security. This doesn't work with subscriptions as you are not around to authenticate to the Analysis Server. You would need to store some Windows credentials for this to work.|||

Hi Brian.

I'm having problem regarding connecting to OLAP Database when I use the Credential stored in the Report Server. but when I used the Credential stored in the Report Server connecting to OLTP database, It work fine.

Below is the error I'm Geting connecting to OLAP Database.

An error has occurred during report processing. (rsProcessingAborted)|||

May be you are using windows authentication or Prompted credentials for your datasource. you can't create a subscription for a report unless it uses stored credentials. Please change the credetials authentications.

it will work- no problem

|||I have tried this several times now. I'm updating the stored credentials from the report Manager once the data source is deployed. No matter what credentials I give I am unable to see the report. If I have no stored credentials and use Windows Auth, I obviously can't set the subscription.

Does anyone have any ideas?|||I finally found it. SQL Server 2005 does not allow credentials when connecting to analysis services.

So I can view the report, but I cannot create subscriptions due to not being able to give credentials.

Why, why, why?|||

Did you find why since?

I'm wondering why credentials should differ for a subscription.

I've not found it yet reported as one bug but it might be.

On my environnement I'm using integrated security in reporting services, datasource linked to the cube, and analysis services

|||I understand why credentials are needed for subscriptions in Reporting Services. Basically

you can't use Windows Authentication because the subscriptions run on

their own, and who would be logging in to run the subscriptions?

I'm fine with that, and I once I figured that out I set about to set

credentials for my data source which connects to Analysis Services

(cubes/OLAP). But in sql server 2005, they have removed the ability

to connect to AS with stored Credentials. You must use windows auth to

connect to AS. This results in not being able to run subscriptions on

reports that connect to AS.

Here is the link I found saying that this will break in sql server 2005, which means that this changed from sql server 2000.
http://msdn2.microsoft.com/en-us/library/ms143380.aspx

Microsoft, why did this change? How are people supposed to set up reports connecting to OLAP which is highly regarded, if subscriptions can't be sent out.

Can not Subscribe a Report

Hi,

I just create a report using Whidbey and deploy it to the Project reportserver. And I can access that report correctly, but I can not subscribe that report, what's going on? Additional, I create that report using Shared Data Source (connected to Analysis Service of my TFS DT) which I created in Whidbey. The exception info is below:

The current action cannot be completed because the user data source credentials that are required to execute this report are not stored in the report server database. (rsInvalidDataSourceCredentialSetting)

Thanks.

The report is set up for Integrated Security. This doesn't work with subscriptions as you are not around to authenticate to the Analysis Server. You would need to store some Windows credentials for this to work.|||

Hi Brian.

I'm having problem regarding connecting to OLAP Database when I use the Credential stored in the Report Server. but when I used the Credential stored in the Report Server connecting to OLTP database, It work fine.

Below is the error I'm Geting connecting to OLAP Database.

An error has occurred during report processing. (rsProcessingAborted)|||

May be you are using windows authentication or Prompted credentials for your datasource. you can't create a subscription for a report unless it uses stored credentials. Please change the credetials authentications.

it will work- no problem

|||I have tried this several times now. I'm updating the stored credentials from the report Manager once the data source is deployed. No matter what credentials I give I am unable to see the report. If I have no stored credentials and use Windows Auth, I obviously can't set the subscription.

Does anyone have any ideas?
|||I finally found it. SQL Server 2005 does not allow credentials when connecting to analysis services.

So I can view the report, but I cannot create subscriptions due to not being able to give credentials.

Why, why, why?
|||

Did you find why since?

I'm wondering why credentials should differ for a subscription.

I've not found it yet reported as one bug but it might be.

On my environnement I'm using integrated security in reporting services, datasource linked to the cube, and analysis services

|||I understand why credentials are needed for subscriptions in Reporting Services. Basically you can't use Windows Authentication because the subscriptions run on their own, and who would be logging in to run the subscriptions?
I'm fine with that, and I once I figured that out I set about to set credentials for my data source which connects to Analysis Services (cubes/OLAP). But in sql server 2005, they have removed the ability to connect to AS with stored Credentials. You must use windows auth to connect to AS. This results in not being able to run subscriptions on reports that connect to AS.

Here is the link I found saying that this will break in sql server 2005, which means that this changed from sql server 2000.
http://msdn2.microsoft.com/en-us/library/ms143380.aspx

Microsoft, why did this change? How are people supposed to set up reports connecting to OLAP which is highly regarded, if subscriptions can't be sent out.

Can not Subscribe a Report

Hi,

I just create a report using Whidbey and deploy it to the Project reportserver. And I can access that report correctly, but I can not subscribe that report, what's going on? Additional, I create that report using Shared Data Source (connected to Analysis Service of my TFS DT) which I created in Whidbey. The exception info is below:

The current action cannot be completed because the user data source credentials that are required to execute this report are not stored in the report server database. (rsInvalidDataSourceCredentialSetting)

Thanks.

The report is set up for Integrated Security. This doesn't work with subscriptions as you are not around to authenticate to the Analysis Server. You would need to store some Windows credentials for this to work.|||

Hi Brian.

I'm having problem regarding connecting to OLAP Database when I use the Credential stored in the Report Server. but when I used the Credential stored in the Report Server connecting to OLTP database, It work fine.

Below is the error I'm Geting connecting to OLAP Database.

An error has occurred during report processing. (rsProcessingAborted)|||

May be you are using windows authentication or Prompted credentials for your datasource. you can't create a subscription for a report unless it uses stored credentials. Please change the credetials authentications.

it will work- no problem

|||I have tried this several times now. I'm updating the stored credentials from the report Manager once the data source is deployed. No matter what credentials I give I am unable to see the report. If I have no stored credentials and use Windows Auth, I obviously can't set the subscription.

Does anyone have any ideas?
|||I finally found it. SQL Server 2005 does not allow credentials when connecting to analysis services.

So I can view the report, but I cannot create subscriptions due to not being able to give credentials.

Why, why, why?
|||

Did you find why since?

I'm wondering why credentials should differ for a subscription.

I've not found it yet reported as one bug but it might be.

On my environnement I'm using integrated security in reporting services, datasource linked to the cube, and analysis services

|||I understand why credentials are needed for subscriptions in Reporting Services. Basically you can't use Windows Authentication because the subscriptions run on their own, and who would be logging in to run the subscriptions?
I'm fine with that, and I once I figured that out I set about to set credentials for my data source which connects to Analysis Services (cubes/OLAP). But in sql server 2005, they have removed the ability to connect to AS with stored Credentials. You must use windows auth to connect to AS. This results in not being able to run subscriptions on reports that connect to AS.

Here is the link I found saying that this will break in sql server 2005, which means that this changed from sql server 2000.
http://msdn2.microsoft.com/en-us/library/ms143380.aspx

Microsoft, why did this change? How are people supposed to set up reports connecting to OLAP which is highly regarded, if subscriptions can't be sent out.

can not login my database when published to IIS

hi,

i am tring to use the 'xcopy' way to deploy my web site, this is the connection string i am using:

"Data Source=.\SQLEXPRESS;INITIAL CATALOG=;AttachDbFilename='|DataDirectory|\HotStage.mdf';Integrated Security=True;User Instance=True"

it works when in debug mode, but after i depoly it to my XP's IIS, it can not login the database, the error message is :

Cannot Login to the default user database. Login Failed. Login Failed for user xxx\ASPNET

'xxx' is my computer.

i think this problem is cause of improper setting of security, but i really do not know how to set it in this situation, because the database is attached to the db system dynamically.

plz someone help, thx

when you use userinstance in sql server express, once the applicaiton is connected to the database you can not connect to the database using SSMO Express. If you donot want to use userinstance change the connection string . "AttachDbFilename='|DataDirectory|\HotStage.mdf' " this is the part where u are attaching the db in connection string. change it if not needed

refer :

http://blogs.msdn.com/sqlexpress/archive/2006/11/22/connecting-to-sql-express-user-instances-in-management-studio.aspx

Madhu

|||

hi,

yes, after i remove the 'User Instanct' clause, and did some permission adjustment, i do connected to my database.

but now i have another strange problem... it says my database is read-only

i have set that folder to hava 'write' permission in IIS.

any idea about this?

can not login my database when published to IIS

hi,

i am tring to use the 'xcopy' way to deploy my web site, this is the connection string i am using:

"Data Source=.\SQLEXPRESS;INITIAL CATALOG=;AttachDbFilename='|DataDirectory|\HotStage.mdf';Integrated Security=True;User Instance=True"

it works when in debug mode, but after i depoly it to my XP's IIS, it can not login the database, the error message is :

Cannot Login to the default user database. Login Failed. Login Failed for user xxx\ASPNET

'xxx' is my computer.

i think this problem is cause of improper setting of security, but i really do not know how to set it in this situation, because the database is attached to the db system dynamically.

plz someone help, thx

when you use userinstance in sql server express, once the applicaiton is connected to the database you can not connect to the database using SSMO Express. If you donot want to use userinstance change the connection string . "AttachDbFilename='|DataDirectory|\HotStage.mdf' " this is the part where u are attaching the db in connection string. change it if not needed

refer :

http://blogs.msdn.com/sqlexpress/archive/2006/11/22/connecting-to-sql-express-user-instances-in-management-studio.aspx

Madhu

|||

hi,

yes, after i remove the 'User Instanct' clause, and did some permission adjustment, i do connected to my database.

but now i have another strange problem... it says my database is read-only

i have set that folder to hava 'write' permission in IIS.

any idea about this?