If you are unable to create a new account, please email support@bspsoftware.com

 

News:

MetaManager - Administrative Tools for IBM Cognos
Pricing starting at $2,100
Download Now    Learn More

Main Menu

CAC Macro - stopping execution

Started by shananigins, 11 Sep 2008 06:42:48 PM

Previous topic - Next topic

shananigins

Hi all,

I was wondering if anyone has run into an issue where they are running a Macro in the CAC (8.3) and the macro gets hung up.  I've been trying to stop the macro, fixed the error that caused the stall, have deleted all the macro steps, restarted services, restarted the server and it's still hanging onto the Macro.

Any ideas of what to try next?

Thanks!

sascha

Hi shananigins

do you mean that it is still hanging or it hangs up again when trying to run it again?

shananigins

Still hanging...been going for 20 hours now.

sascha

Try removing the app from the Content Store, restart server and reattach it (link to existing app).

Does the macro state prevent you from rerunning the macro or is it only displayed as a kind of log?

shananigins

Thanks all!  I sorted out this issue.

My biggest concern was just deleting the macro as I wasn't sure if it would continue to run in the back ground (as many Cognos processes tend to do).  After logging a ticket with Cognos, I found out that deleting a macro clears it out all together.

Problem solved.

adityashah27

Just to share one more option,
you can also kill processes from planning/job server's task manager.

sascha

Quote from: adityashah27 on 16 Sep 2008 08:22:45 PM
Just to share one more option,
you can also kill processes from planning/job server's task manager.


Is there a separate process that is started to process macro jobs?

adityashah27

i think above question is for me,

no its the same process. just like any other program, you would see process ids in the task manager when its using CPU of that server.

GEPlebe

I know this is a dead topic - but recently had same problem and eventual solution (perhaps easier than deleting the macro) was to simply restart the Cognos service....