Job failed to execute

  • Hi,

    I have created simple Job in maintenance plan having simple Sql query to insert data in another server's database table (lets say B server).

    when i copy paste this query in A server (my main server), it runs perfectly fine.

    (Job is created in A server & I fire query in A server only)

    Query is look like :

    insert into [192.168.x.x].[database].dbo.table select a,b,c,d from xxxx

    i have saved B server's login details in A server's Job, from 'Manage Connections.....'.

    Job starts daily as per schedule but ends with error.

    Error description is as under :

    Description: Executing the query "delete from [192.168.x.x].[db].dbo.table..." failed with the following error: "Invalid object name 'xxxx'.". Possible failure reasons: Problems with the query<c/> "ResultSet" property not set correctly<c/> parameters not set correctly<c/> or connection not established correctly. End Error DTExec: The package execution returned DTSER_FAILURE (1). Started: 2:52:05 PM Finished: 2:52:09 PM Elapsed: 4.212 seconds. The package execution failed. The step failed.,00:00:05,0,0,,,,0

    Guide pls.

  • Why are you using a maintenance plan for this? Maintenance plans are what their name suggests - for backups, updating statistics, consistency checks and so on.

    The query in your job clearly isn't as simple as you say, since the error message begins with "delete from". Do you have a linked server on your source server pointing at the destination server? You need that for the four-part object naming to work.

    John

  • Yes, Source server and destination servers are linked.

    And i give full path in query eg. delete from [192.168.x.x].database.dbo.table.

    Is there any other way to execute such query at specific schedule time ?

    thanks

  • In that case, there's absolutely no reason I can see to use a maintenance plan for this. Please try changing the job step to T-SQL and see whether that works.

    John

Viewing 4 posts - 1 through 3 (of 3 total)

You must be logged in to reply to this topic. Login to reply