November 12, 2008 at 12:42 pm
I am recieving a unique error when trying to process a cube through a job step. The SQLAGENT.OUT File reports an error:
Step 1 of job 'CFMS Star - Analysis Cube' (0x82D61E33ECFE7B41A37830A738785DB6) has caused an exception in the ANALYSISCOMMAND subsystem and has been terminated. Then Acutal Error from the job is : An exception (0xe0434f4d) occurred in the ANALYSISCOMMAND subsystem. The step failed.
Has anyone encountered this error while trying to schedule a job to process a cube, if so what was the resolution.
Regards,
Anthony Malone
Anthony Malone
November 13, 2008 at 7:16 pm
It might be helpful if you post the actual command that you are running so that we can evaluate it. Also, which version of SQL Server are you running? If 2005, have you run a trace with Profiler against the server to evaluate what activity is going on and the actual error message that is generated? If this is 2005 are you running this with a proxy that has the necessary credentials and permissions to perform the processing?
----------------------------------------------------------------------------------------
Dan English - http://denglishbi.wordpress.com
November 14, 2008 at 8:17 am
The Version is Sql Server 2005 With sp2 installed. It is a clustered environment. The XML code used to process the cube works find when executed manually from the ssms. However we scripted the xml command and placed it in a job step to execute automatically. This is where the errors are being thrown. The Analysiscommand subsystem is a sql server agent process which processes xml command and code. The error is a general error, and I do not know if one of the subsystems were not loaded. However we followed the directions given by microsoft support attached below and still we seeing errors when we execute the job to process the cube.
http://support.microsoft.com/kb/914171/en-us
http://support.microsoft.com/kb/903205
Anthony Malone
June 30, 2011 at 6:00 pm
Add me to the list. I'm on SQLserver 2008 (not R2 and recentlly upgraded from 2005) and my SQA jobs calling SSAS ran fine up until one fine day earlier this week. I'm on a cluster and I've re-hosted my instances during the week to apply Windows updates (but not to all servers and I've re-hosted the SSAS instance to servers that haven't been updated yet and it still fails); other than that no changes in the environment, yet this code now throws the exception error we're all dealing with. The ClearCache test works in my environment as does the cube processing directly from SSAS.
This code comes directly from the SSAS cube Process, Script option and thence into the SQA job:
<Batch xmlns="http://schemas.microsoft.com/analysisservices/2003/engine">
<Parallel>
<Process xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:ddl2="http://schemas.microsoft.com/analysisservices/2003/engine/2" xmlns:ddl2_2="http://schemas.microsoft.com/analysisservices/2003/engine/2/2" xmlns:ddl100_100="http://schemas.microsoft.com/analysisservices/2008/engine/100/100">
<Object>
<DatabaseID>ContactLog</DatabaseID>
</Object>
<Type>ProcessFull</Type>
<WriteBackTableCreation>UseExisting</WriteBackTableCreation>
</Process>
</Parallel>
</Batch>
TIA,
Al
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply