April 2, 2008 at 2:48 pm
Hi All,
I'm having intermittent failure on a production package where table meta data cannot be seen and logging to sysdtslog90 does not occur. Log rows do exist for successful runs (between failures)!? Below is the job history message with business names replaced with [replacement].
Another aspect of this is that the table referred to does not exist in production: it only exists on a separate development server. I have opened both versions of the package and confirmed that the new table is only referenced in the development version of the package (the one that does not run in a scheduled job yet). Twilight Zone time?
Has anyone come across anything like this?
TIA
Executed as user: [agent login] for 32-bit Copyright (C) Microsoft Corp 1984-2005. All rights reserved.
Started: 7:00:00 AM
Error: 2008-04-02 07:00:04.25
Code: 0xC0204026
Source: [data flow task name] [table_name] [1151]
Description: The metadata for "[i][table_name][/i]" cannot be retrieved. Make sure the object name is correct and the object exists.
End Error
Error: 2008-04-02 07:00:04.25
Code: 0xC004706B
Source: [data flow task name] DTS.Pipeline
Description: "component "[table_name]" (1151)" failed validation and returned validation status "VS_ISBROKEN".
End Error
April 2, 2008 at 3:00 pm
And, I figured it out shortly after posting!
The problem is that the job deployed to production was pointing to the package on the development server. It's intermittent because those days where the backout script was tested (and left overnight), the package would again be pointing to the correct production tables. How clever.
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply