March 23, 2007 at 10:10 am
I have a simple SSIS package that processes a cube every morning at 8:05am. It's been running fine for a couple of months until this week it's been failing with this error from the job history.
Message
Executed as user: MyDomain\AppAdmin. ... 9.00.3042.00 for 32-bit Copyright (C) Microsoft Corp 1984-2005. All rights reserved. Started: 8:05:54 AM Progress: 2007-03-23 08:06:02.08 Source: Process cube Started building processing schedule.: 0% complete End Progress Progress: 2007-03-23 08:06:02.08 Source: Process cube Finished building processing schedule.: 100% complete End Progress Progress: 2007-03-23 08:06:02.09 Source: Process cube Processing of the 'Affiliates Cube' cube has started..: 0% complete End Progress Progress: 2007-03-23 08:06:02.09 Source: Process cube Processing of the 'Fact Affiliates' measure group has started.: 0% complete End Progress Progress: 2007-03-23 08:06:02.09 Source: Process cube Processing of the 'Fact Affiliates' partition has started.: 0% complete End Progress Progress: 2007-03-23 08:06:02.09 Source: Process cube Starting to write data of the 'Fact Affiliates... The package execution fa... The step failed.
There doesn't appear to be any other error in the sql error logs. When I go to process the cube manually it always succeeds. Any idea what could be causing the problem?
-Phil
March 23, 2007 at 10:37 am
Hello Phil,
Has the password for the user with which it is getting executed changed? Try to refresh the data sources on the SSIS package.
Hope this helps.
Thanks
Lucky
March 27, 2007 at 8:06 am
No, the password hasn't changed.
Is there a way to get a more detailed error message?
March 28, 2007 at 9:11 pm
Here is what I think happened Microsoft maybe trying to automatically create the proxy account for the Agent when you run SSIS packages as Jobs so you need to make sure xp_cmdshell is enabled and create a proxy account for the Agent make sure the you account you clone is of admin level. Try the links below for details, post again if you still need help. Hope this helps.
http://www.mssqltips.com/tip.asp?tip=1020
http://support.microsoft.com/kb/890775
Kind regards,
Gift Peddie
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply