on 2013 Oct 30 10:40 AM
Hello: I'm trying setup a link server from sqlserver 2012 (64 Bits installed in a winserver 2012) With a Sybase Database (my database is C:DBasesCONVIAL2009.DB). I have ASA 9.0, with Sybase 32 and 64 bits installed in the same server. Someone could help me with the correct parameters?
MS request this data:
exec sp_addlinkedserver @server = 'TESTING' ,
@srvproduct = 'Sybase',
@provider = 'ASAProv.90',
@datasrc = 'Sybase System DSN' I'm typing "EAS Demo DB V9 IM"
Sp_addlinkedsrvlogin @useself='false ', @rmtsrvname = 'TESTING', @rmtuser = 'User Name', I'm typing (dba) @rmtpassword = 'Strong Password' I'm typing (sql)
I changed the RPC parameters to TRUE.
There is another parameter @provider_String = What to write in it?
The error received is "cannot initializate the data source of OLE DB provider "ASAPRov.90" for linked server"
Thanks a lot.
Request clarification before answering.
You need to ensure that the OLE DB provider is registered with the system first. The bitness of the OLE DB provider needs to match the bitness of your running application - in this case, the bitness of Microsoft SQL Server (so, x64).
There should be two DLL files in your SQL Anywhere 9.0.2 x64 directory: %ASANY9%\\x64\\dboledb9.dll
and %ASANY9%\\x64\\dboledba9.dll
which need to be registered at the Command Line:
regsvr32 dboledb9.dll regsvr32 dboledba9.dll
Ensure that %ASANY9%\\x64\\dblgen9.dll
and %ASANY9%\\x64\\dblcon9.dll
are also present in the same deployment directory.
Regarding the error: Cannot initializate the data source of OLE DB provider "ASAPRov.90" for linked server
, it sounds as if you have not specified a valid DSN to connect to SQL Anywhere. How is: "EAS Demo DB V9 IM" specified for this server?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Jeff Thanks for your answer.
I registered the two dboledb libraries, also, verified the file dblgen9. In the next link, you can see the ODBC in the server. Please see it and give me your recomendations. link text
Your screenshot is indicating that you have created a 32-bit ODBC DSN for this entry - you need to create a 64-bit ODBC DSN in order for the 64-bit Microsoft SQL Server to access the DSN definition.
In order to create the 64-bit DSN, be sure to launch the 64-bit ODBC administrator from C:\\WINDOWS\\System32\\odbcad32.exe
(as is currently shown in the screenshot). In order to remove the existing 32-bit DSN entry, you'll need to launch the 32-bit ODBC Administrator from C:\\Windows\\SysWOW64\\odbcad32.exe
, and remove it from there.
As the screenshot shows that jhenaoc is already using the 64-bit ODBC administrator, he would only have to "Add..." a 64-bit DSN straight from that dialog.
Aside: Whereas User DSNs are shared between 32-bit and 64-bit, System DSNs are not, as is explained here.
@jhenaoc: If you have setup the correct DSN, make sure to set the required properties for the linked server, particularly the "AllowInProcess" option - cf. my older FAQ...
User | Count |
---|---|
75 | |
30 | |
9 | |
8 | |
7 | |
6 | |
6 | |
5 | |
5 | |
5 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.