January 20, 2020 at 4:56 pm
Hello
We have Analysis Server cubes on SQL 2016/Windows 2019 environment.
Using dtexec to process the weekly cubes often fails or if it succeeds then Last Update date is not stamped (Only Last processed date is refreshed)
The Error from dtexec is:
Description: Server: The current operation was cancelled because another operation in the transaction failed.
Source: CubesRefresh
Description: SSIS Warning Code DTS_W_MAXIMUMERRORCOUNTREACHED. The Execution method succeeded, but the number of errors raised (4) reached the maximum allowed (1); resulting in failure. This occurs when the number of errors reaches the number specified in MaximumErrorCount. Change the MaximumErrorCount or fix the errors.
However, the same cubes when processed from SSDT 2017 Visual studio Full Processing is always successful and both dates are stamped correctly - Last Updated and Last processed.
Why is there a difference in both?
I need to schedule this weekly once, hence am using Dtexec via a batch file.
Many thanks in advance
Vinay
January 20, 2020 at 5:00 pm
For scheduled processing of cubes, you might find it simpler to write XMLA scripts & then simply call them from SQL Agent job steps (link).
If you haven't even tried to resolve your issue, please don't expect the hard-working volunteers here to waste their time providing links to answers which you could easily have found yourself.
January 27, 2020 at 5:09 pm
Hi Phil,
This XMLA script seems to have worked for processing the Cubes. Both Last Updated and Last processed date were changed.
Although the process completed, the job history shows the number of errors (count).
How do you collect the errors in cube processing, if I use this method?
Thanks,
Vinay
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply