I've linked to a table in an sql server 2012 database using an odbc connection. This was straightforward and worked fine using my log in. When I attempted to open the linked table on another users computer I got an error saying I could not connect. I tried to set up the connection on their PC but couldn't see the database on the server. I logged on to sql server and gave that user a log on to the sql and access to the database using windows log in.
I still could not gain access to the database through access. Any idea what I'm doing wrong.
One Idea, you shall create all linked tables with a privileged user account of the SQL Server.
For example, if you enabled Trusted_Connection in the SQL Server, you can use the administrator's account of Windows, for example, johndoe2 for connection. If your SQL Server is installed on the LAN host masterserver, a linked table can be created as this:
ODBC;DRIVER=SQL Server;SERVER=masterserver\SQLEXPRESS;Database=[MyDatabase];UID=johndoe2;Trusted_Connection=Yes;TABLE=dbo.[MyTable]
In our case we can access MyTable throuhg Access 2007 on the host biomas that is on the same LAN as the masterserver.
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 a virtual desktop which is hosting a SQL Server 2014 32 bit intance named "MyRemoteServer". The server has been set up with a linked server named "mscribe" using VFPOLEDB which is the OLEDB for FOXPro.
When I am logged directly into the virtual desktop I am able to query the linked server in SSMS by connecting with either Windows Authentication or a SQL Account. However when I access the server using SSMS from my laptop, the SQL Account is able to query the linked server without a problem, but when using Windows Authentication the same query returns an error. I have also tried formatting this as an openquery however I get the same error. What confuses me further about this is that I have another linked server (this one is a remote SQL Server) setup on MyRemoteServer and when I connect from my laptop using Windows Authentication I have no problems querying it.
Query:
Select o.ordernr from mscribe...[order] o where o.ordernr = 'O12345'
Error:
Msg 7303, Level 16, State 1, Line 1 Cannot initialize the data source object of OLE DB provider "VFPOLEDB" for linked server "mscribe".
With this error and the fact that I can query the other linked server my first assumption would be that the issue is with the setup of the linked server, however since the same query works when executed using the SQL Account I must assume that this is not the issue. My next assumption would be a permissions issue, however the Windows Authentication works when I am logged directly into the Server so I am not sure that this is the issue either.
Any help or suggestions are very much appreciated.
Thank You
I have a windows 7 run SQL server (I don't know what is kind of SQL) of my colleague.
My colleague is stopped work.
I don't know password windows, password sql,and sql file,...
I tried crack pass windows using hirent boot but failed, and I can't load partition to remove syskey password.
His machine is sql server.
I can't connection to his machine.
I have a question:
How to get database on his machine without login windows?
Thank all
If the service of SQL server stopped, you can copy database file and copy in other location, and can attach this file to another SQL server database engine. also you can know version of your SQL server by using SQL Server connection management, and also SQL server query (select ##Version ) if you can execute query.
I have set up an instance of SQL Server Express 2012 on a computer. On this computer I use MS Access as the client to access the data stored on the SQL Server Express. When I open MS Access and click on an object it then prompts me for the SQL Server username and password (I set up a SQL Server Native 11.0 Driver). This works fine. The goal is to put the file on others computers so they can access the data on our SQL Server. I also have enabled the TCP/IP protocols to allow remote connections as well as the Firewall settings that are necessary. However, when I place the file on another computer, it returns SQL Server Error 53.The strange thing is that I have another computer that I tested this on and it works perfectly fine.
My assumption is that I am missing software on the client computer. What software must be present on the client computers so it will be able to access my SQL Server Express on the "server computer"?
Please let me know if you have any questions, at this point I am stumped.
If you're using ODBC, then on the 2nd computer you need to
Start->Control Panel->Data Sources (ODBC)
Select System DSN tab
Click Add...
Select SQL Server Native Client
Give it the same name as the name on the working computer
Select the server to connect to etc.
and you should be OK
I am a developer-having-to-play-admin and wish to connect to a remote sql server from my development machine using a sql server user ("op_web").
When I try to connect from vs2008 Server Explorer, I can connect to the server, but no databases are listed. If I connect using the server admin user, all databases are listed as expected.
The server is a relatively fresh install made by me.
I have
allowed for remote connections in sql server.
created the login op_web at server level
created a user at database level and assigned to login with same name
assigned roles to the user to allow for reading and writing - I have assigned no schemas and default schema for the user is dbo.
If I log on (locally at server) using sqlserver management studio/sqlserver authentication and the created login, I can display and alter table data as I would expect.
Remote access gives me no choice of databases.
Any pointers to what I might have missed?
You have to give your users rights on the database.