I don't understand the error I'm getting. I have a virtual machine with Windows Server 2012 and Win 10. I installed SQL Server 2008 Enterprise on it.
Now, when I set distributed database, I set publication with my win 10. After I set publication success and I set subscription in publication, set success but when I watch virtual machine not result. And error not connect with virtual machine.
Here is error
Please help me !
Related
In Visual Studio 2019 menu: Tools -> Connect To Database I see "MySQL Database" data provider, but an attempt to connect to my aurora database finishes with weird error:
"Microsoft Visual Studio / Unable to connect to any of the specified MySQL hosts. Sequence contains more than one matching element"
I have Aurora DB based on MySQL 5.6.10. I can connect to it using the latest MySQL Workbench 8.0.18. I have the latest "MySQL for Visual Studio 1.2.9" and Connector/NET 8.0.18. I work with .NET Framework 4.7.2. I can also connect to other (normal) MySQL instances from the Visual Studio, but not to Aurora DB.
My final target is to create ADO.NET Entity Data Model from the amazon db, but this fails on the same error message.
Is there any guide how to connect MySQL Aurora DB with .NET Framework (not .NET Core)? A guide to extremely simple application which can download single value from any table would mean a significant step forward for me.
OK. I found it's a Bug #97448 introduced in MySql.Data 8.0.18. Workaround is to define server name by IP address instead of xxx.rds.amazonaws.com address.
It's a know bug.
FYI the previous version of mysql.data (v6.10.9) is also affected.
As a workaround you could resolve the DNS value to an IP address manually.
In the code example below I check if the server value is an IP then I resolve the DNS name when the value is not an IP address.
if (IPAddress.TryParse(server, out var ipAddress))
{
// The server value is an IP address, it can be used directly
}
else
{
server = Dns.GetHostEntry(server).AddressList.FirstOrDefault()?.MapToIPv4().ToString();
}
return new MySqlConnectionStringBuilder
{
Server = server
// ...
};
I have a Linux SUSE server with Microstrategy 10.3 installed, metadata stored on MySQL database on the same server and I am trying to connect to data stored on Teradata database. The problem is when I create any report or cube and run it; I get the error:
Error: Server 'SERVER_NAME' has temporarily become unavailable.
and the service stops. I attached the DSSErrors log for further information.
SUSE Linux Enterprise Server 11 SP4
Security Guide
Linux server technical data
I'm currently trying something I've never done before - I'm trying to access MySQL data in an SQL Server environment. Where I am, we have two servers (the MySQL and MSSQL servers), and each stores different types of data. Recently I've found a need to write queries that include data for both servers. One of the ways I read to do this is adding a "Linked Server" in SQL Server. But try as I might I cannot seem to get a Linked Server added.
I am working on a Windows 7 system, our SQL Server instance is 2005, and the MySQL version is 5.5.31.
What I've done so far is this:
Downloaded and installed the MySQL ODBC drivers
Created a System DSN using that driver for the MySQL database, called "Production". (I also tested the connection from the Data Sources application and it connects just fine).
Checked for the Provider in SQL Server (MSDASQL) to configure options such as "allow nested queries" and "allow 'LIKE' operator"
right click on Linked Servers in Server Objects in SQL Server > "New Linked Server"
From here, I fill out the linked server info like this:
Checked "Other data source" (not SQL Server)
Chose Provider "Microsoft OLE DB Provider for ODBC Drivers"
Product Name: "Production"
Data Source: (the name of the System DSN) Production
Then in the security tab, I chose the "Connections will be made using this security context" and provided my username and login for the MySQL server.
Then this is where I run into an error every time. I always get the following error message:
The linked server has been created but failed a connection test. Do you want to keep the linked server?
ADDITIONAL INFORMATION:
An exception occurred while executing a Transact-SQL statement or batch. (Microsoft.SqlServer.Express.ConnectionInfo)
Cannot initialize the data source object of OLE DB provider "MSDASQL" for linked server "FLUX".
OLE DB provider "MSDASQL" for linked server "FLUX" returned message "[Microsoft][ODBC Driver Manager] Data source name not found and no default driver specified". (Microsoft SQL Server, Error: 7303)
For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=09.00.5000&EvtSrc=MSSQLServer&EvtID=7303&LinkId=20476
If you click that link for help, by the way, nothing shows up.
I saw other people suggested trying an older MySQL ODBC driver, adding a System Data Source for the 32bit driver as well as the 64bit driver, and restarting my machine (not the DB server) -- none of these fixed my error.
What I do not understand is why my System DSN seems to work and connect fine, but SQL Server cannot see the Data Source. Does anyone see what I'm missing, or what I might be configuring incorrectly?
EDIT
Clarified that I restarted my local machine, but not the DB server since trying to add the Linked Server.
From everything you've said, you probably have a mismatch between bitnesses of SQL Server 2005 components and the installed ODBC Driver for MySQL.
System DSNs are definitely the way to go.
You probably will need to install both the 32-bit and 64-bit ODBC driver, and configure an identical (same name and everything!) System DSN with each.
I would say you may also want/need to install this patch it was useful for getting XP and 2003 to work properly for ODBC type connections for me.
http://www.microsoft.com/downloads/details.aspx?FamilyID=000364db-5e8b-44a8-b9be-ca44d18b059b&displaylang=en
Is your Database server on the same machine on which you have Sql Server Management Studio Installed? If the SQL Server is on a remote machine then you need to install the ODBC driver on remote Machine and create the DSN there as per link
I was having the same issue but the above link solved my problem.
I'm trying to set up replication between a SQL Server 2008 R2 database and SQL Server CE 3.5. I have set up IIS 7 accordingly and get a nice "Microsoft SQL Server Compact Server Agent" when checking the publication URL (http://winserver2008/SQLReplication/sqlcesa35.dll).
However when I try http://winserver2008/SQLReplication/sqlcesa35.dll?diag I get the following:
When I try to connect to the publisher via a C# app I'm writing I get "Initializing SQL Server Reconciler has failed. Try again". i assume that means I need that 9.0 database reconciler? If so how do I install it?
On a side note this only happens when I try to connect via Integrated Windows Authentication. If I try via SQL Server authentication instead I just get an error about SQL Server missing or having an incorrect login/password.
Finally figured it out. After locating the actual error message in SQL Server Profiler it became obvious there was an issue with the access privileges of the publication. As it turns out I had to add the database user to the PAL instead of the corresponding windows account.
The IIS web site and web application utilized by SQL CE 3.5 has to be set to allow "directory browsing". Once I turned that on, the ReadWriteDeleteMessageFile status went to SUCCESS.
OK maybe I'm being stupid somehow, and my googleing has not found a clear step by step user case for beginners.
I have just installed into my Win 7 Pro 64-bit SP1 machine SQL Server 2008 R2 Express Database with Advanced Services [downloaded from here http://www.microsoft.com/express/Database/InstallOptions.aspx]. (Actually I have removed and installed it 3 times now to check I'm not missing anything config wise). I have left basically all settings as default, with the exception of calling the Instance SQLEXPRESS (all caps vs default SQLexpress) my last installation I have left set as 'windows authentication mode' with only the same user as I am running now selected (only one user on this machine anyway).
After completion I have restarted the machine, I can see the services
SQL Server (SQLEXPRESS) -> Started -> Automatic
SQL Server Agent (SQLEXPRESS) -> -> Manual
SQL Server Browser -> -> Manual
SQL Server Reporting Service (SQLEXPRESS) -> Started -> Automatic
SQL Server VSS Writer -> Started -> Automatic
.. So it seems to be up OK.
As part of the installation process it also installed SQL Server Management Studio 2008 R2 and when I try and connect I am choosing:
Server: Database Engine
Servername : \SQLEXPRESS
Authentication: Windows Authentication
User name: (selected for me and not alterable) machinename\username
Password: (also blank greyed out)
I hit connect and get the following message.
Cannot connect to \SQLEXPRESS.
A network-related or instance-specific
error occurred while establishing a
connection to SQL Server. The server
was not found or was not accessible.
Verify that the instance name is
correct and that SQL Server is
configured to allow remote
connections. (provider: SQL Network
Interfaces, error: 25 - Connection
string is not valid) (.Net SqlClient
Data Provider)
Error Number: 87
Severity: 20
State: 0
OK, so given I am not entering a username or password, and I'm certain of the server instance name - and that it is running ... what am I doing wrong?
Here are a few troubleshooting tips for connecting to SQL Server via SSMS:
Ensure you're connecting to .\sqlexpress or localhost\sqlexpress, or (local)\sqlexpress. It's not case sensitive. It appears you're missing the hostname in the server name field in the connection dialog.
You're using Windows/AD authentication, so you don't have to enter any credentials. It appears you're all set there.