Server ‘SERVERNAME’ is not configured for RPC

Setting 'RPC out' to true worked! Thank you very much!

I hope you come back here sometimes. You inadvertently stumbled into a topic that not one other blog, forum post, article, or screech has talked about. Note your screen shot above: ONLY the "rpc out" option is actually necessary. The "rpc" option (without the "out" part) isn't. Maybe you were doing the screenshot in-transit. But my point is, I've found it to be a myth that BOTH options need to be enabled to call a remote stored procedure. At least, for a remote SQL Server. "rpc out" definitely must be enabled to call a stored procedure on the remote server. But what specifically does "rpc" do? If "rpc out" is enabled, and "rpc" is disabled... you can still call a stored procedure on the remote server. If you don't believe me, try it yourself - disable the "rpc" option, but keep "rpc out" enabled, and call a remote procedure. I can only surmise two possibilities: 1. A provider, since it is essentially an external "driver", requires *something* be specified for both options, even if the source system - SQL Server in this case - doesn't support a bi-directional link, e.g. a remote server calling a local procedure (the reverse of what you were trying to do above). In this scenario, I'm not immediately referring to what the options are, only that both have to be explicitly specified, as if the provider won't supply a default for either one if SQL Server doesn't set the value. Kind of like saying, if you insert into a table with a column that can't be null and doesn't have a default, you HAVE to specify a value for that column. Same idea for the provider - it requires both options, it cannot use a default value if one isn't specified, so both HAVE to be specified, even if one of them means nothing. Like inserting an empty string into that column - the value means nothing, but at least it's not NULL. 2. Some providers - not SQL Server's, but maybe e.g. DB2 or Firebird - actually DO require both options be enabled, to call a remote stored procedure. I haven't encountered this with Oracle databases, but I've never worked with a linked server to other true data stores like DB2 et al. I have used linked servers to flat files (e.g. Excel) but those don't have stored procedures, so the "rpc" and "rpc out" options are moot. But, the fact that both options are available EVEN for a linked server to a flat file suggests the first guess - that some providers require it be specified even if it is ultimately meaningless for other providers. Thoughts?

Wow... sorry about that, first comment here ever. Didn't know it ignores "new paragraph" apparently. :( And, I can't edit it. Yuck.