VCU - Technology Services
Asynchronous Process Woes
No comments Leave a comment »
Boy did I have a mini meltdown over this one!
One day, publication ceased on one of our projects. I contacted RedDot Support. For 8 days they had me copy the project, export the project, rebuild the publication, publish to a different target, publish target on a different project, remove workflows, rebuild workflows, add project variants, clear XML and page cache, clear out RedDot Temp files, basically an exercise which nearly drove me insane.
And then, on day 8 of no publication, I happened to notice an Asynchronous Process (SmartTree->Administer Project Structure->Project->Show Asynchronous Processes) that had been started one week prior and was "stuck" in the active phase for 8 days. The exact amount of time since the last successful publication.
Normally, with these process you can kill them by clicking on a convient X in the SmartTree.
However, this process was missing the X and there was no way to stop the stalled publication.
I sent a last final email to RedDot Support: "Please send me documentation on how to stop a stalled asynchronous process". And guess what? They had the perfect documentation on how to clear these jobs. The process involved deleting fields from the CMS database and then allowing the back logged publications to run their course. Though I have the documentation, I can not post it due to RedDot copyrights. The documentation is readily available from the Support office.
So, if your project stops publishing and you've cleared out the caches and checked the queues, try looking at the asynchronous processes, because that might be the source of your publication woes.
One day, publication ceased on one of our projects. I contacted RedDot Support. For 8 days they had me copy the project, export the project, rebuild the publication, publish to a different target, publish target on a different project, remove workflows, rebuild workflows, add project variants, clear XML and page cache, clear out RedDot Temp files, basically an exercise which nearly drove me insane.
And then, on day 8 of no publication, I happened to notice an Asynchronous Process (SmartTree->Administer Project Structure->Project->Show Asynchronous Processes) that had been started one week prior and was "stuck" in the active phase for 8 days. The exact amount of time since the last successful publication.
Normally, with these process you can kill them by clicking on a convient X in the SmartTree.
However, this process was missing the X and there was no way to stop the stalled publication.
I sent a last final email to RedDot Support: "Please send me documentation on how to stop a stalled asynchronous process". And guess what? They had the perfect documentation on how to clear these jobs. The process involved deleting fields from the CMS database and then allowing the back logged publications to run their course. Though I have the documentation, I can not post it due to RedDot copyrights. The documentation is readily available from the Support office.
So, if your project stops publishing and you've cleared out the caches and checked the queues, try looking at the asynchronous processes, because that might be the source of your publication woes.
About This Entry
Oct
22
2009
Need Help?
If you need immediate assistance, please contact the Help Desk at (804) 828-2227 or submit a ticket online. You can also submit feedback through our Feedback form above or leave a comment on specific blog entries.
Don't Get Phished
Don't be a phishing victim - VCU and other reputable organizations will never use email to request that you reply with your password, social security number or confidential personal information. Learn more about phishing »
Last updated: Nov 5, 2009
No comments below.
Add your thoughts