Josh, Thank you for your response. You are right this has worked fine I was using Report manager URL, i changed it to use Report Server URL. After deployment, i ran the report it says it cannot create a connection to the Data Source. Any thoughts. Regards

Did the data source get deployed, and do you have Windows Authentication selected? Open the data source in Report Manager and try hardcoding a username/password in there that you know works with 'Use as windows credentials' ticked. (This will avoid any Kerberos issues). Also go to the report properties and ensure the correct data source is linked to the report.

Ok, I am using Windows Authentication. Right Clicked Data Source properties --> It says no Credentials since I am using Windows authentication. So are you saying to remove windows authentication and try with a Windows Login? Correct Data Source is linked but how do we check that...TargetDataSourceFolder and it is pointing to the right location.

All, I have made a report Locally on my Machine. Now I am able to connect to the website through my login information successfully through the browser. Now when I go back to my report and entered the URL--> Right Clicked Report and Hit Deploy then again it pops up a Small Login screen (Reporting Services Login) and again i enter the same information i used to login through the browser but it just refreshes (No error what so ever but looks it is denying the same login information) What can be the Error here? Thanks

Is there any other option i do not have a windows login to that server other that Windows authentication. I saw something like Enable Remote Errors in Config table how can we do that?

I am looking into the ReportServer database, I cannot find any table...?

That's right, try using a hardcoded windows login 'use as windows credentials', and save password. If you have a separate reporting and database server you might get the 'double hop' problem where the report server needs to be trusted for delegation. So you want to force it to use a specific active directory username and password, rather than trying to pass on the credentials of the user running the report. Once set up you can test the connection. For the data source of the report, in the properties of the report that is deployed, you'll be able to see which data source it is using, just ensure it is pointing to the correct one.

Do you have the correct information in TargetServerURL? And can you connect through the browser if you use the URL defined in TargetServerURL? Remember the TargetServerURL needs to be the Report Server Web Service URL not the Report Manager URL. eg if the Report Manager URL is http://myreportserver/reports then the webservice URL is often http://myreportserver/reportserver

Thanks Josh for helping me all the way ..appreciate it....I was able to Deploy the reports and view them in the Report Browser. The login was the problem..and it worked the way you suggested

As a first test you want to specifically hard code a windows login and password eg YOURDOMAIN\username - password there rather than having the report server delegate your credentials to the database. Please see the following :- FROM (http://msdn.microsoft.com/en-us/library/ms159736.aspx) To specify stored credentials for a shared data source In Report Manager, navigate to the Contents page. Navigate to the shared data source item. The following icon indicates a shared data source item: Click the item to open it. The General properties page opens. In the Connection Type list, specify the data processing extension that is used to process data from the data source. For Connection String , specify the connection string that the report server uses to connect to the data source. Microsoft recommends that you do not specify credentials in the connection string. The following example illustrates a connection string used to connect to the local SQL Server AdventureWorks2008R2 database: Copy data source=<localservername>; initial catalog=AdventureWorks2008R2 Type a user name and password. If the account is a Windows domain user account, specify it in this format: <domain>\<account>, and then select Use as Windows credentials when connecting to the data source. If the user name and password are database credentials, do not select Use as Windows credentials when connecting to the data source . If the database server supports impersonation or delegation, you can select Impersonate the authenticated user after a connection has been made to the data source . Click Apply .