October 20, 2008 at 4:25 am
Ever since we migrated our servers to a new production cluster 2 weeks ago (and from SP1 to SP2), we've been getting a weird, intermittant error on our jobs. The jobs will work fine for a couple of days, then one of them (at random) will throw the following error:
Could not load package "MyPkg" because of error 0x80040E37. Description: Table/view either does not exist or contains errors.
The odd things about this are:
A) We can either run the job manually with no problem or add a "One Time" schedule to the job and it'll run fine this next time.
B) The job in question will start running again that night without issue.
C) It's different jobs that have this problem. Kind of like a random shuffle on your iPod.
D) Our job failure notifications aren't working when this happens, so we have to manually go into Job Activity to see which jobs might have failed the night before because we're not getting our proper notifications via email.
Any thoughts? I can't find much about this problem via google, unless I'm searching on the wrong phrases.
Thanks in advance,
October 20, 2008 at 5:00 am
I assume the packages are stored in MSDB on your server - have you run a checkdb on MSDB? The error looks like it is indicating a problem getting the package definition.
Also, after the sp2 upgrade, did you open and re-save your packages with an sp2 version of BIDS? Some components changed - packages that have not been re-saved usually fail consistently with some weird com errors, but it is a step people forget to do.
October 20, 2008 at 7:47 am
I assume the packages are stored in MSDB on your server - have you run a checkdb on MSDB? The error looks like it is indicating a problem getting the package definition.
Yes, the packages are saved there, but why would it be able to access the package one day, not be able to access it the next, then be able to access it the next time we run the job? These are nightly scheduled jobs, same time every day, so that part doesn't make sense.
But I'll still run a check on MSDB just for kicks, giggles and CMA. After all, couldn't hurt, could it? @=)
Also, after the sp2 upgrade, did you open and re-save your packages with an sp2 version of BIDS? Some components changed - packages that have not been re-saved usually fail consistently with some weird com errors, but it is a step people forget to do.
I was unaware package components actually changed in SP2. Huh. And actually, it's not so much that we forgot to do it as we can't quite yet. Our Dev/Test/QC servers were built to old corporate specs and don't have enough space on the drive which houses the program files for us to upgrade to SP2. So now that our Prod Servers are rebuilt, we're working on the Dev/Test/QC stuff.
Yes, I know doing production first is a little backwards, but we had mission critical stuff that needed more HD space, so they decided to Prod first and the others later.
Thanks for the advice, Michael. I'll check into these possibilities.
Viewing 3 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply