While deploying reports I am getting login prompt asking for the User Name and password. I have tried providing all possible id and passwords but no use. I can access both the Report manager url and ReportServer url but if I start deploying reports through SQL Server Business Intelligence development studio I am getting the above mentioned prompt. Please let me know how to avoid this.
Make sure that the server on which you are trying to deploy the Reports, you must be under the group which has the following Role assigned.
Browser, ContentManager and Publisher.
goto Start menu ->Microsoft SQL Server 2008->Configuration tools ->select Reporting services configuration manager ->Connect Report server ->Select Database from the left side options -> Current Report server Database -> Click Change Database ->Choose Existing server Database ->Test the connection ->Next -> Select Report Server as Report server Database.
And goto Select Database from the left side options -> "Current Report server Database Credentials" ->select Authentication type as integrated security and Test connection -> select Authentication type as Service credentials.
I hope it will resolve the problems
Best verification is to make sure you are deploying the new reports to your report server link. And not to the link which corresponds to the report manager. I was running across the process of deploying reports after ages, and I observed this problem when the report server target link is not correct.
I use VM for SSRS development.. and it's not a member of the domain where the SSRS Service lives.
I was able to easily eliminate prompts when deploying reports.. by setting up a LOCAL user account on the SSRS server that used the same username / password as what I was using in my VM.
I had the same issue, but this worked for me: When deploying from SQL Server Business Intelligence Development Studio, you must be running it as Administrator. ie. Right-Click and select 'Run as Administrator'.
This is possibly because if you are not running it with elevated privileges, then it can't do the Impersonation to login to the server.
Using web services URL in TargetServerURL instead of Report Manager URL.
Goto Reporting services configuration manager, connect SSRS server then go to "Web service URL" in right hand side you will find a link like as http://server//reportingServer. Copy the url.
Now open Business Intelligence Development Studio. open SSRS project.
Goto Project menu and click on properties, in property page Paste copied URL in TargetServerURL. Now Rebuild the project and Deploy. Credential will not appear and Deploy succeeded.
When moving (deploying or copying) an RDL file from one location (development) to another (production) the report may loose track of it's shared data source, at which point the data set will replace the original node with a new node that instructs SSRS to demand credentials.
In the report that is persistently demanding credentials if you right-click in solution explorer and select 'view code' the .rdl will open in an xml reader window. If your mark up contains a reference that looks like:
<DataSources>
<DataSource Name="YourDataSourceName">
<ConnectionProperties>
<DataProvider>SQL</DataProvider>
<ConnectString>Data Source=<i>your-server</i>;Initial Catalog=<i>your-db-name</i> </ConnectString>
<Prompt><b>Enter a user name and password to access the data source:</b></Prompt>
</ConnectionProperties>
<rd:SecurityType>DataBase</rd:SecurityType>
<rd:DataSourceID>e2f9f97c-GUID-GOES-HERE-395c383c1da2</rd:DataSourceID>
</DataSource>
</DataSources>
If this is what you find in the xml/rdl this is likely your problem.
Make sure you have a Shared Data Source that works as expected, you may have to build a new report based off of this that does not prompt for credentials.
In a report that does NOT ask for credentials, open the RDL using 'view code' option.
Select the relevant xml node (under ) and copy the node, it should look something like:
<DataSource Name="YourDataSourceName">
<DataSourceReference>YourDataSourceName</DataSourceReference>
<rd:SecurityType>None</rd:SecurityType>
<rd:DataSourceID>19f0a78a-<b>GUID-GOES-HERE</b>-0e277b3b153f</rd:DataSourceID>
</DataSource>
In your target report replace the node with the one you copied.
(worth noting that when you change the 'rd:SecurityType' from 'Database' to 'None' you are NOT removing security, you are merely passing responsiblity for authentication from the report's dataset on to the shared datasource. (Security is born by the connection rather than the query)
I had the same problem, it was due to the wrong spelling of the TargetServerUrl in report project properties, make sure that it meet the same name in the Report Server Configuration Manager:
Related
When I am trying to process dimensions after creating a data source view I get the error:
The project could not be deployed to the server because of the following connectivity problems : A connection cannot be made. Ensure that the server is running. To verify or update the name of the target server, right-click on the project in Solution Explorer, select Project Properties,click on the Deployment tab, and then enter the name of the server.
I have checked in task manager & SQLBrowser is running. Why am I getting this error?
I was able to get the SQL Server instances on my computer this way:
Start Menu
Microsoft SQL Server 2008 or your version
Server Installation Center
Admin login
Select "Tools" from left menu
Select "Installed SQL Server features discovery report"
You then get a nice HTML web page. You want to look for Database Services. You should see an instance name. Mine is called "SQLEXPRESS." So the combination of server name and instance would be MYCOMPUTER\SQLEXPRESS given that my computer name is MYCOMPUTER.
BTW, the default instance name is MSSQLSERVER.
Alternatively, you can get it from your registry. Just run regedit and look for this key: Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\Instance Names\SQL
Check that the SQL Server service itself (or MSSQLSERVER) is running. Also check the connection string.
If you want to deploy the project to a named instance of Analysis Services on the local computer, or to an instance on a remote server, change the Server property to the appropriate instance name, such as <InstanceName>.
https://learn.microsoft.com/en-us/analysis-services/multidimensional-tutorial/lesson-2-5-deploying-an-analysis-services-project?view=asallproducts-allversions
You need the server name and the instance name.
Open port 2382,2383 to server solve this issue for me.
How to configure rebuild and reorganization in maintenance plan? Please tell me step by step, for SQL Server 2008 R2
I think you need to set up a default profile for your database mail profile. Under Management -> Database mail profile, right click and select Database Mail configuration. A wizard will pop up. Select Manage profile security. As shown below, atleast one of your mail profiles should have been set as Default Profile ('Yes')
When trying to configure the TFS 2010 backup using the TFS Power Tools I kept running into teh following error message:
Account TFS\tfsadmin failed to create backups using path \\tfs-xxxxxxx.local\TFSBackups
The strange thin is that TFS\TFSAdmin has full permissions on both share and file system and that the share path doesn't contain any spaces (thanks for MSDN forums for pointing that out).
I tried backing up through the SQL Server Management Studio, and sure, there the backups fail too.
It turns out that while the backup job is started using the account specified in the Create Backup Wizard of the TFS Power Tools, SQL Server will try to write the files to the share using its own service account.
So in addition to whomever needs access to the share, you need to add the service account running SQL Server to that share as well. In this case it was running under NETWORK SERVICE, so adding MACHINENAME$ to the share's list of permitted users did wonders.
My 2 server both use SQL Server 2008 R2
I have my local SQL server and also an Amazon machine running an instance of SQL-Server there.
I'm able to connect from my local machine to that Amazon SQL using the standard 10.10.10.10, 1433 connection from my local Management Studio.
What i need to do now is to run a query that says ..tells me what records I have locally that are not on the Amazon server right now.
Something like:
SELECT *
FROM [LOCAL].dbo.Table1
WHERE Field1 NOT IN
(SELECT Field1 FROM [AMAZON].Database1.dbo.Table1)
================================
Question:
I don't know how to write the "AMAZON" location on the Query window itself, since it's running on a different server.
Any help is truly appreciated !!!
You have to configure AMAZON Server as LINKED Server on your local machine. If you name it "AMAZON" - you query will work exactly as you wrote.
In SSMS, \Server Objects\Linked Servers. Right click, 'new linked server'. Name your server, and choose 'SQL server' radio button. Because I was authorized user on both machines with windows credentials, I selected 'Be made using the login's current security context' radio button under the security tab, and did not even have to fool with the local/remote user mappings.
In order to be able to run queries across multiples servers, a link (linked Server) must be established between the 2 Servers. To create a linked server,
Navigate to the Linked Server Sub-folder under the Server Object folders
Right Click on the Linked Server Folder
Click on New Linked Server
Supply the Connection Strings for the Server
Name your Linked Server.
You can now use the full object qualification (LinkedServer.Database.tableOwner.Table) to access the objects.
Good Luck !
You should open your registered server window and create a group for your servers. then you right click the group name and select new query (Or select several servers in that group). if you execute the query it will rung against the servers selected.
We deployed a VB.Net application on a customer's computer that contains SSRS reports.
The application connects to the SQL Server database in the app without any problems. We installed SQL Server Data Tools so we could deploy the reports (rdl) and data source (rdl) files up to the report server. These deploy without any problems.
In SQL Server Data Tools we can "Preview" the reports without any problems as well.
We do run into a problem when attempting to view the report from Internet Explorer (run as an administrator).
We get the following error:
Cannot create a connection to data source 'DataSourceReports'
(this is the name we used for the TargetDataSourceFolder)
error:40 - Could not open a connection to SQL Server
We also get the same error when the app we deployed runs the reports.
Please let us know what is not set up correctly on the SQL Server side.
A likely possibility is that you are experiencing a double hop authentication problem. It's not clear from your explanation, but is the SQL Server database on a separate server from the report server? If so, then your credentials allow you to connect to the report server but Windows integrated security does not pass those credentials on to the SQL Server database if you are using NTLM on the report server. The report server tries to use Kerberos on your network to authenticate by way of ticketing to the SQL Server database, but you must have this configured correctly on your network. See this article if you want to use Kerberos: http://technet.microsoft.com/en-us/library/ff679930(v=sql.100).aspx.
Another (easier) solution is to open the data source on the report server and change the authentication to use stored credentials. Make sure the credentials you use have read permission on the SQL Server database. The downside of this approach is that you cannot use row-level security in your report by user unless you design your report to capture user information and set up the query or a filter on the dataset to restrict data by user. If that's not a concern, the stored credentials are easy to set up and maintain - and you're going to have to do this anyway if you want to use caching, snapshots, or subscriptions. For more information on stored credentials, see http://msdn.microsoft.com/en-us/library/ms159736.aspx.