Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
Home
Discussion Groups
DB Engine
SQL ServerMSDESQL Server CE
Services
Analysis (Data Mining)Analysis (OLAP)DTSIntegration ServicesNotification ServicesReporting Services
Programming
CLRConnectivitySQLXML
Other Technologies
ClusteringEnglish QueryFull-Text SearchReplicationService Broker
General
Data WarehousingPerformanceSecuritySetupSQL Server ToolsOther SQL Server Topics
DirectoryUser Groups
Related Topics
MS AccessOther DB ProductsMS Server Products.NET DevelopmentVB DevelopmentJava DevelopmentMore Topics ...

SQL Server Forum / General / Security / January 2007

Tip: Looking for answers? Try searching our database.

Trouble with linked servers

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
gurbao - 24 Jan 2007 11:33 GMT
Hi,

I have SQL Server 2005 SP1 installed on win2003 SP1 with two instances
(default and \instance2).
The server is set up with mixed mode authentication.
SA is setup with the same password on both. The domain user
"sqlservice" is running both instances (and are a local admin).
Linked server setup between the instances with

I have a proc that is calling sp_makewebtask to generate a html-files.
Calling this proc to run a local query runs fine, but passing a query
issueing a remote query (using the linked server) returns an error:
Msg 18456, Level 11, State 1, Line 0
[Microsoft][SQL Native Client][SQL Server]Login failed for user 'sa'.
Msg 16805, Level 11, State 1, Procedure sp_makewebtask, Line 131
SQL Web Assistant: Could not execute the SQL statement.

Line 131 in sp_makewebtask is
       SET @procname = 'xp_makewebtask'
and have hardly anything to do with the error.

A few lines above I find
  EXECUTE @retval = sys.xp_makewebtask  @outputfile, @query,
@username, @procname, @dbname,
       @fixedfont, @bold, @italic, @colheaders, @lastupdated,
@HTMLheader,
       @templatefile, @webpagetitle, @resultstitle, @URL, @reftext,
       @table_urls, @url_query, @whentype, @targetdate, @targettime,
       @dayflags, @numunits, @unittype, @rowcnt, @maketask, @tabborder,
       @singlerow, @blobfmt, @nrowsperpage, @datachg, @charset, @codepage

which I guess is failing. But why?

Running the query directly in SSMS works fine.

I newly migrated this from a sql server 2000 environment where this
worked flawlessly. As far as I can see, the two environments are setup
identically when it comes to users running the services and logins on
the server.

I have struggeled with this for a while and would like to know if
anyone has a tip on what could be wrong.

Regards,
Uri Dimant - 24 Jan 2007 11:42 GMT
Have you enabled on SS2005  remote and local connection checkbox in Surface
Area Configuration?

> Hi,
>
[quoted text clipped - 40 lines]
>
> Regards,
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2009 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.