MS SQL remote server procedure not found on Win 2K8 R2

[Former Member]

Current installation of SQL Anywhere 9.0.2.3951 on Win 2k3 with a remote server on a MSSQL with no problems. We moved the SQL Anywhere DB a new server, Win 2k8R2. Now, when acessing the MSSQL remote server proxy tables are working, but when executing remote procedure, MSSQL return 'procedure x not found'. I deleted and recreated the remote server and remote login. When creating the proxy for the remote procedure (with Sybase Central) I see the list of stored proc on the MSSQL DB. How can I see a list of remote procs, but when executing the proxy the I get an error with the remote proc not found.

Any help appreciated.

[VolkerBarth]

May you have run in a similar problem as in that [FAQ](http://sqlanywhere-forum.sap.com/questions/9865)?

Sorry, dumb suggestion, I thought you were using MS SQL to access SA procedures, but now I see you are trying the opposite...

[VolkerBarth]

Is the SA database user listing the remote proc in Sybase Central the same user trying to execute the remote proc?

If not, are they mapped to the same extern login (aka MS logins)? Or may they be mapped to different MS logins having different permissions and/or MS default databases?

Yes, I know, no answers, just more questions:)

[Former Member]

I use the same user, DBA, for the listing and to execute the remote proc.

[VolkerBarth]

Could you please show the code for your external procedure and how you call it?

[VolkerBarth · Accepted solution]

Besides my comments on your question, I would try to use Remote Data Access debugging (i.e. using CIS_OPTION = 7), cf. this v12.0.1 doc page...

[Former Member · Accepted solution]

With the CIS_OPTION and trace, the only thing that was different between the two setup was the version of sqlsrv32.dll. Everything worked once I used the same driver version.

[VolkerBarth · Accepted solution]

Glad you got it working! BTW, what version of MS SQL Server are you using?

[Former Member · Accepted solution]

I believe it's 2005, but I'm not sure, that is/was part of the problem. It's from another software vendor of one of our client and they are not really helpful about their product.