Wrox Programmer Forums

Need to download code?

View our list of code downloads.

Go Back   Wrox Programmer Forums > SQL Server > SQL Server 2000 > SQL Server 2000
Password Reminder
Register
| FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read
SQL Server 2000 General discussion of Microsoft SQL Server -- for topics that don't fit in one of the more specific SQL Server forums. version 2000 only. There's a new forum for SQL Server 2005.
Welcome to the p2p.wrox.com Forums.

You are currently viewing the SQL Server 2000 section of the Wrox Programmer to Programmer discussions. This is a community of tens of thousands of software programmers and website developers including Wrox book authors and readers. As a guest, you can read any forum posting. By joining today you can post your own programming questions, respond to other developers’ questions, and eliminate the ads that are displayed to guests. Registration is fast, simple and absolutely free .
DRM-free e-books 300x50
Reply
 
Thread Tools Search this Thread Display Modes
  #1 (permalink)  
Old March 8th, 2007, 10:03 AM
Friend of Wrox
 
Join Date: Jun 2003
Location: Bangalore, KA, India.
Posts: 2,480
Thanks: 0
Thanked 1 Time in 1 Post
Default Job Fails - trying to insert into remote machine

Hi,

I am trying to capture some data from each of the sql servers and store them into a centralised table. When I do a addlinked server and test the stored procedure at different servers it works perfect. But when I try to schedule it as a job on each sql server, it fails with the following error.

Executed as user: Domain\UserName. Login failed for user '(null)'. Reason: Not associated with a trusted SQL Server connection. [SQLSTATE 28000] (Error 18452). The step failed.

I knew adding the same account in the remote machine will solve this. But I am not sure what domain users are existing in the production environment, since I dont have access, I was told that those are not in a domain. More over there will be no technical person involved in doing this at production, so I need to give the scripts that work perfectly and independently.

I also tried setting an sql user name and password for sql server agent to run as, so that sql server agent runs with the sql userid provided, and the same done on source sql server and destination sql server solves the purpose. But this process needs an sql server agent restart. Since all the servers are participating in replication, I am not sure about the impact of this process on Replication. At any cause replication should not break.

Is there any way I can have this sorted out? There could be different ways of doing it, I wanted the best shortest way to achieve this, as it needs to go into production and needs to be tested well locally.

Any help is much appreciated.
Cheers

_________________________
- Vijay G
Strive for Perfection
__________________
- Vijay G
Reply With Quote
Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off
Trackbacks are Off
Pingbacks are On
Refbacks are Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
Retore Db from a remote machine to a local machine srkvellanki BOOK: Beginning SQL 0 October 3rd, 2008 05:17 PM
Chapter 2 - Using copies of virtual machine fails Jvillalobos BOOK: Professional SharePoint 2007 Development ISBN: 978-0-470-11756-9 1 July 8th, 2008 05:10 PM
Creating Job with VBScript in it Fails happygv SQL Server 2000 1 April 27th, 2007 02:56 AM
Job fails & need to use domain\user acct to run kiwikencox SQL Server 2000 1 October 17th, 2005 09:30 PM
DB backup Job fails within a second or two happygv SQL Server 2000 6 October 16th, 2004 01:21 PM



All times are GMT -4. The time now is 07:52 PM.


Powered by vBulletin®
Copyright ©2000 - 2019, Jelsoft Enterprises Ltd.
© 2013 John Wiley & Sons, Inc.