|
I am trying to create a linked server in sql server 2005 to a clarion table. In a test box with sql server installed it works fine. When I move it to a live sql server it gives the following message when I run a openquery against it. the linked-server connection tests fine "[SoftVelocity Inc.][TopSpeed ODBC Driver][ISAM]ISAM Table Not Found" everything matches (well obviously something doesn't). Could there be a setting in sql server that might cause this?
(comments are locked)
|
|
is there any difference in the network - domain / workgroup - between the test and the production boxes? Are you logged on as the same user? can you create a ODBC DSN on the server via Windows that is successful? Quick tip - create a file on the desktop of your prod SQL Server called "clarion.udl" and then double click it. This will open a dialog that allows you to enter the connection details and then test it is successful. This works regardless of installed software so can be used to diagnose issues from ANY hardware... thanks for the response. I created a udl file and the test connection button returns test connection succeeded. Same user in all cases. same network. same domain, same sub domain. I remember somewhere reading about a sql setting to allow adhoc queries or connections or something. I'm leaning towards this being some setting in sql. The prod server probably has more recent security patches.
Mar 19 '10 at 10:11 AM
mhj96813
Also, I am using select * from openquery(Linked-server-name, 'Select * from tablename') to test
Mar 19 '10 at 10:52 AM
mhj96813
It may be worth reviewing the setting in the SQL Server Surface Area Configuration Manager to make sure that's not affecting this but the error saying "Table Not Found" suggests to me it's permissions within SQL rather than connectivity to the server/database.
Mar 20 '10 at 07:39 AM
Fatherjack ♦♦
(comments are locked)
|
