I'm attempting to use SSDT to publish to a SQL Server database in Azure. When I do so, I am seeing the following error:
Unable to connect to master or target server 'DATABASE_NAME'. You must have a user with the same password in master or target server 'DATABASE_NAME'.
Ignoring the fact that it's listing a database name as the server name in the error, I'm not sure how to resolve it. When I specify the target database, I can successfully Test Connection. I can also connect using the same creds to the database through SSMS.
After researching the error, it seems like it is often that the firewall for the database in Azure does not include the IP address of the machine you're publishing from. It not only contains my IP, but I added another firewall rule to allow every IP (0.0.0.0-255.255.255.255) to eliminate the firewall as a potential cause of the problem.
Any ideas?
This is a known issue. This happens due to the new compatibility level 140 for newly created SQL Azure databases. The issue has been documented here and updating SSDT from here to the latest version may solve the issue.
Alternatively, you can change the compatibility level of your database to 130.
ALTER DATABASE database_name
SET COMPATIBILITY_LEVEL = 130;
Hope this helps.
Initializing deployment (Start)
Initializing deployment (Failed)
*** Could not deploy package.
Unable to connect to master or target server 'DbName'. You must have a user with the same password in master or target server 'DbName'.
Issue occurred while deploying build through VisualStudio-2015 and it support to publish database on the database servers whose version up to only 2016.
Solution: For SQL server 2017 we need to Publish Database with Visual Studia 2017 only. Need to upgrade SSDT.
Faced same issue when trying to deploy a DB from local SQL Server to Azure SQL DB via SSMS.
Tried to alter source DB's compatibility level to 130, still got same error.
Tried to add same user logins to master DB, no help.
Eventually, started looking for other approaches. Succeeded by using Data Migration Assistant, as instructed in https://learn.microsoft.com/en-us/azure/sql-database/sql-database-cloud-migrate.
My situation was slightly different in that I had exported an Azure database (with compat level 140) from SQL Azure and then tried to import it into a local SQL Server 2017 installation - using the latest SSMS 2017 that I just installed yesterday - and still got this message.
Turned out that although I did have latest SSMS installed, I was actually opening SSMS 2016 by mistake! So be sure to select and pin the correct version to avoid it happening again. Just typing 'SSMS' into the Windows Start menu may not show both.
So if you use SSMS to import you only need the latest version, and no separate tools.
Footnote: Even after opening the correct SSMS version I got another error - something about contained databases.
An Azure database is a 'contained' database (or at least mine was) - meaning that its user logins are embedded in the database. This isn't enabled by default apparently in standard SQL Server 2017.
After running this in the local SQL in master I was able to import it successfully.
sp_configure 'contained database authentication', 1;
GO
RECONFIGURE;
GO
When this happened to me it was due to the version of tools I was using. I thought it strange that the most recent SqlPackage.exe I found in C:\Program Files (x86)\Microsoft SQL Server didn't work and publishing from visual studio did, so I found the most recent
under the visual studio directories:
C:\Program Files (x86)\Microsoft Visual Studio\2017\Professional\Common7\IDE\Extensions\Microsoft\SQLDB\DAC\150\SqlPackage.exe
* to publish to a SQL Server database in Azure*, you can use "Data Migration Assistant" (DMA).
I just tried it and it works smoothly without any issues (firewall and compatibility level)
please refer to this link SQL Server database migration to Azure SQL Database
for step by step: 10. How to migrate the SQL database to Azure with the Azure Database Migration Service
I got the same error while trying to update a local SQL Server database from Visual Studio database project (i.e. not i Azure). Turns out the problem was I was running SSDT for Visual Studio 2017 while using Visual Studio 2015. Visual Studio discovered an updated version of SSDT (just happened to see it in notifications!), pointing to the right Visual Studio version. Now it works!
My setup: BizTalk Server 2016 forces me to use Visual Studio 2015. My local database is on SQL Server 2017. Using SSDT for Visual Studio 2015 works for updating databases in SQL Server 2017. Just so you know. ;)
Most of the sources recommend to set COMPATIBILITY_LEVEL = 130; and, usually, it solves the issue. Unfortunately, this did not help me.
In my case, I had to downgrade SQL Server 2017 on my machine to SQL Server 2016 Developer Edition.
I ended up having to install DacFramework.msi on the SQL server that my azure runner agent was installed to get past this error. My server is a VM running in our network. not running in azure...
the description on the msi says:
'This installer database contains the logic and data required to install Microsoft SQL Server Data-Tier Application Framework (x64).'
Try to connect to the SQL Azure database using Sql Server Management Studio and the ip getting listed in the management studio is the right ip address. Try to add to the SQL Azure firewall rules. The ip address listed in the firewall page of Sql Azure portal is not accurate.
I have a client application that will be deployed using ClickOnce. The client application will connect to a local sql database on their machine. They will need sql server 2008 express installed upon installed and the .mdf file attached.
I set Prerequisites to include sql server 2012 express.
So I would like the application when installing to check if sql server already installed with the database. If not then install and attach database. How can i achieve this properly using click once. I have a vb.net project using visual studio 2013. any references would help thanks.
You just have to change your connection string
to somthing like this
Server=.\SQLExpress;AttachDbFilename=C:\MyFolder\MyDataFile.mdf;Database=dbname;
Trusted_Connection=Yes
now your sql is linked to a specific database file
check this link https://www.connectionstrings.com/sqlconnection/attach-a-database-file-on-connect-to-a-local-sql-server-express-instance/
Perhaps this was asked before but I can't find a whole lot on this, so I would appreciate some help.
Our architecture is as follows: Win 7 desktop on a domain with VS 2010. MS Sql server R2 on Win Server 2008 R2 Ent; SharePoint 2007 on Win 2003; SharePoint 2010 on Win 2008 R2 Ent; Visual Sourcesafe on yet another separate Win Server 2008 R2 Ent server. On this server I have just installed TFS and was running Advanced Config Wizard.
As I'm new to TFS all my selected options are based on intuition and perhaps common sense but Reporting Services and SharePoint aren't working. With reporting services after I add my sql server name (and I've tried IP address and dns name) neither the Report Server URL nor Report Manager URL is populated. (Note: What do I need reporting services for anyway?)
So I've opted not to use reporting services, which as I said, I don't know what is the benefit of it.
Next, in the SharePoint configuration, I wanted to use the existing SharePoint farm which is installed on a separate servers. Testing the Site and Administration URLs would throw an error: "The following site could not be accessed. ... Either ... not installed the Team Foundation Server Extensions, or Firewall... "
I suspect it is not the firewall so then the TFS Extensions. Having search that topic as well seems to point back to the TFS's configuration, so I'm a completely at a loss.
Any ideas?
Thanks,
Risho
/posted from a smartphone since employer blocks this site/
Edited: I was looking at this article http://msdn.microsoft.com/library/dd631915.aspx but I don't have the options listed in the step-by-step solution. TFS Admin Console has this: Top tear - server name, below is Application Tear then Proxy Server, build Configuration and Logs. Expanding Application Tear shows Team Project Collections, SharePoint Web Applications, Reporting, and Lab Management.
You have to configure the SharePoint extensions on each SharePoint machine you wish to connect to TFS. Install TFS on whichever SharePoint machine (or both, if you plan to use both). In the configuration wizard, you should have the option to configure SharePoint Extensions. Once done, you should be able to re-run the readiness checks in the Advanced Wizard on your Application Tier machine.
I have a sharepoint Server that I uninstalled. (I just did it through add-remove programs and uninstall)
Then when I tried to re-install Sharepoint foundations 2010 (the same version I uninstalled) it would seem to work correclty, but it would not give me an option for Stand Alone. Only giving me an option for Existing Web Farm or New Web Farm.
I have tried to delete the instances of SQL Server (Sharepoint) but still getting this problem.
I have Windows 2010 Server (same as Windows 2008 R2)
There is no "Stand Alone" option. I just installed a fresh SharePoint 2010 and only had the options for "Existing Server Farm" or "New Server Farm". As explained in the same dialog: Go for "New Server Farm" when you are installing it on a single server (stand alone).
I have installed SQL Server 2005 three times now on the same box. I cleaned up registry settings, files, you name it.
All along I have been trying to install SQL Server 2005 Database and Reporting Services (x64) on a Windows 2008 Server. I have also applied the SP3 patch. Installing and Restarting the Server at every point. Verified that the installation was 64bit. ASP.NET and IIS7 are both running under 64bit.
Also, I have installed multiple instances (SQLDEV64, SQLQA64, SQLSTAGE64) of the Database and Reporting Services.
I started to go through the Reporting Services Configuration manager, installing the Reporting Database along with setting up IIS. When I go test the website I get the following error and there lies my question. How can I get around this error?
http://localhost/reportserver
Reporting Services Error
--------------------------------------------------------------------------------
An internal error occurred on the report server. See the error log for more details. (rsInternalError)
Method not found: 'Void Microsoft.ReportingServices.Diagnostics.UserUtil.CleanCurrentUserName()'.
--------------------------------------------------------------------------------
SQL Server Reporting Services
Any help would be greatly appreciated.
I found the solution to my issue by pure chance. It looks like the SP3 upgrade only upgraded the last reporting services instance that was installed. So I had to manually copy the files under:
C:\Program Files\Microsoft SQL Server\MSSQL.9\Reporting Services\ReportServer
to the other instances. This seemed to fix the missing reference issue. I work with Microsoft products and defend them every day, but some of their developer tool install files are just wonky and ill packaged.