Re: Linked Servers

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

EvanHennis (EvanHennis@xxxxxxxxxxxxxxxxxxxxxxxxx) writes:
> I created a LinkedServer called "ENT". I gave Windows NT permission to
> someone else I work with. They can get to my SQL Server. But when he
> trys to run "Select * from ENT.db.dbo.table" he gets an errror about
> CoCreate. When he logs in as "SA" and then the sa password he can
> execute the same statement without issues. The SQL Security for each
> user seems to be the same. Any ideas?

Could you post the complete error message he gets?


--
Erland Sommarskog, SQL Server MVP, esquel@xxxxxxxxxxxxx

Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techinfo/productdoc/2000/books.asp
.

Relevant Pages

  • Re: Error re-installing SQL Server 2005
    ... i actually was able to export the reg entries from my ... SQL Server Setup could not connect to the database service for server ... Refer to server error logs and setup logs for ... For details on how to view setup logs, ...
    (microsoft.public.sqlserver.setup)
  • Re: Cluster will not fail over.
    ... Could not recover the master database! ... If you intend to stay on SP3 (for SQL Server), you should at least apply the ... >> From SQL server logs ...
    (microsoft.public.sqlserver.clustering)
  • Re: Error re-installing SQL Server 2005
    ... SQL Server Setup could not connect to the database service for server ... Refer to server error logs and setup logs for more ... For details on how to view setup logs, ... Kevin Struckhoff ...
    (microsoft.public.sqlserver.setup)
  • Re: Error re-installing SQL Server 2005
    ... Kevin Struckhoff ... > decided to try out sql server 2008 rc0. ... Refer to server error logs and setup logs for ... For details on how to view setup logs, ...
    (microsoft.public.sqlserver.setup)
  • Re: host_name
    ... When the user logs in, ... >> of a client from sql server. ... >> For security reasons every user of our database system logs into our ... >> This can't be changed as we are limited to 3 database users. ...
    (comp.databases.ms-sqlserver)