i added the bindingsource control on my winform. here are the details of my connection:
http://img43.imageshack.us/img43/3797/42119312.jpg
when i test the connection, it says "the connection cannot be tested because the specified DB file does not exist"
the DB is located in http://sql0234mjf-2.ordfsweb.com. how should i set up bindingsource?
it looks like you're trying to use a database file instead of a database server, you may need to modify your data source.
You are using the wrong provider. The "Microsoft SQL Server Database File" provider is not the SQL Server provider. Is the provider for user instances attached files (RANU). User instances are a SQL Express edition only feature and they can only be accessed locally.
To connect to a true SQL Server instance you need to use the proper provider, the Data Provider for SQL Server. When you choose this provider you are presented with a different dialog that ahs options to specify the server name and database name.
Related
I have an Access DB that I migrated to SQL server recently. The SQL server is on a Windows server. Now I can work normally with the SQL database but when others log into the same windows server with their credentials they are not able to access the database. As soon as they open Access frontend they get an error saying failed connection. Now I created an ODBC connection string(File DNS) and gave it to the other users in the network but they still are not able to connect to the database. They get an error stating "SQL server connection failed. The server rejected the connection: Access to the selected database has been denied". Can someone please help me to solve this issue so that multiple users can connect to the SQL DB without any issues? Thanks
Hard to know with the limited information. Are you using windows authentication to sql server, or are you using SQL logons? Either should work fine. The other issue to watch out for is what sql driver did you use to link with?
If you link say using the native 17 ODBC driver, then that is not installed on workstations by default - you have to download and install that driver.
Or, maybe you linked using the long time "legacy" sql driver - that is by default installed on all workstations.
So, it not clear if you using SQL logons, or using Windows authentication for the connection to the database????
If your using windows authentication, then all those other users will require permissions to be granted to the database.
If you using a SQL logon, then that logon would have been saved when you link the table(s), and again it should work for all users. Its quite common to create ONE logon on SQL server, link using that logon, and thus all users will be connecting to the database using the one same logon id/password.
And, if you linked using a FILE dsn, then zero configeration should be required, since access converts FILE dsn's into what are called dsn-less connections. (the origonal file is not required anymore once you link - you can even delete that FILE dsn, and it will still work).
So, FILE dsn is the best choice, since that dsn is NOT required to be setup on each workstation.
And if you using sql logon's, then make sure you checked the box to remember the password during linking of the tables. That is this check box:
And note during a re-link the above box does not appear - only on first time linking of table(s).
I have created a local db and I want to connect some tables to Microsoft Access. I'm doing this via Microsoft Access's "Link to the data source by creating a linked table" feature" and in order to do that I need to create a DSN. However I'm getting an error where it says
"Server does not exist or access denied"
At the moment I'm trying to create a new DSN and i'm stuck during the below step which I need to specify my server. I've tried two different server names and they both don't work.
Note: It's definitely not an access denied issue because I've tested the login myself and they all work fine.
Can someone please tell me what I'm doing wrong or is it not possible to link Access to a local db.
Resolution
When choosing a driver for the new data source, use either the ODBC Driver...for SQL Server or the SQL Server Native Client. (note: I am also able to get the "SQL Server" driver to work, but only by specifying the named pipe address of the instance in the next step/image where specifying the SQL Server to connect to.)
The SQL Server to connect to in the "Create a New Data Source to SQL Server" should be "(LocalDB)\instancename"; in this case "(LocalDB)\MSSQLLocalDB"
Caveats
As the LocalDB name itself implies, connections to it can only be
made from the local machine. If you need to access an instance on a
different machine, and need a free solution, you should use SQL
Server Express.
These results were obtained using Access 2016. My
experience with other software indicates it should work with Access
2010 as well, but I did not test that. If you have trouble, try using
the named pipe address for the instance instead of the
"(localdb)\MSSQLLocalDB" moniker in the image above.
Results
Here are the results of testing the connection, then adding links to two tables in the master database
Instead of using a LocalDB I used SQLExpress which worked fine.
When I create a linked server in SQL Server, it causes an error
Cannot create a instance of OLEDB provider SQLNCLI10 for linked server 'linked server name '(microsoft sql server error 7302)
How can I rectify this error?
The OLEDB provider may not properly installed. What you chose is the SQL Server native client. Do you have SSMS installed on server? This should come with sql native client OLE DB.
I would like to share an experience when I faced following error
Cannot create an instance of OLE DB provider "xxx.YYYY" for linked server "test". Error 7302.
I observed this message from a failed SQL Server job. On analysis it is found that Allow Inprocess was not enabled for the provider. When this is enabled, everything worked fine for me.
Server Objects --> Linked Servers --> Providers
Also refer following
"Cannot create an instance of OLE DB provider" error as Windows Authentication user
Linked Server Properties (Provider Options Page)
Configuring OLE DB Providers for Distributed Queries
I developed a school DBMS using ASP.NET and SQL Server, and I tried to transfer to another system then I installed SQL Server 2014. After going on my through my default page inserting my user and pass all that will display is :
Unable to establish connection to database.
Error information:
Microsoft OLE DB Provider for SQL Server (0x80004005)
[DBNETLIB][ConnectionOpen (Connect()).]SQL Server does not exist or access denied.
Other possible cause of this problem:
The database cannot be opened, most likely due to incorrect connection settings or insufficient security set on your database folder or file.
Can you please let know what would be issue.
Had this before, follow this guide
TLDR: Change the provider to SQLOLEDB.1
https://social.msdn.microsoft.com/Forums/sqlserver/en-US/fab0e3bf-4adf-4f17-b9f6-7b7f9db6523c/communication-link-failure-when-connecting-to-remote-database?forum=sqlintegrationservices
SOURCE:http://stackoverflow.com/questions/6946265/ssis-package-creating-hresult-0x80004005-description-login-timeout-expired-e
I need to create a linked server from SQL Server 2012 to a IBM DB2 (9.x) on AIX. It is a mandatory requirement to create the connection with SSL.
I was trying to use "Microsoft® OLEDB Provider for DB2 v4.0 for Microsoft® SQL Server® 2012" but I was not able to connect to DB2 by the Data Access Tool from MS OLEDB.
Later I installed the IBM DB2 client tools and GSKIT and with this I can connect to DB2 via SSL. With the installation also came the connection provider "IBM OLE DB Provider for DB2". The problem is that I can't create the linked server.
I always get the error message
Cannot create an instance of OLEDB Provider "IBMDADB2.DB2COPY1" for linked Sever "mydb2" (Microsoft SQL Server , Error 7302)
In some discussions was mentioned to use a specific provider string, but in this case the field of the provider string is greyed out.
I just have the options for Product name and Data Source. Is the Data Source == the DB Name of the Connection form the IBM BD2 Client tools? What should I use as Data Source?
Okay i could solve the problem and want to share the solution.
The mentioned provider IBMDADB2.DB2COPY1 comes from the installation of the IBM DB2 Client tools.
In Server Objects --> Linked Servers --> right click new server you can choose the provider. Using the "IBM OLE DB Provider for DB2 - DB2COPY1" which has access to the configured connection including the SSL Keys, the field Data Source is greyed out.
The key to successfully create a linked server to a DB2 is not the guy but the script. There you can use also provider string information even it is greyed out in the GUI.
EXEC master.dbo.sp_addlinkedserver #server = N'MyLinkedServer', #srvproduct=N'IBMDADB2',
#provider=N'IBMDADB2', #provstr= N'HOSTNAME=hosturl;Port=12345;
DATABASE=DBinDB2Client;UID=ItsMe;Pwd=secret;Security=SSL;', #datasrc=N'DBinDB2Client'
Et voila, as you can see the linked server will be created successfully and can acceess the DB2 Database. The issue is solved.
__
edit:
the linked server can only! used by it's creator. if other users want to access the server, they'll get this error:
Cannot create an instance of OLE DB provider "MSDADASQL" for linked server "MyDB2"
there is a tutorial how to give the permission to other users:
http://blogs.msdn.com/b/dataaccesstechnologies/archive/2011/09/28/troubleshooting-cannot-create-an-instance-of-ole-db-provider.aspx
after you walk through the tutorial, you also need to reboot.