Error while publishing through Macro

[amitbehere2002]

I am getting a error while publishing from Macro

2009-07-21T22:06:51.042+00:00

Machine details: ADS0\COGBI

User details: ADS0\cognos3

Process ID / Thread ID: 4288 / 4528

Unable to execute macro step 'Publish - View Layout - Advanced PNL'.

Unable to execute macro 'pad/pad_live/macro/Admin_Links_for_Final_P_L'

Unable to execute 'Publish - View Layout - Advanced PNL'

The 'PUBLISH' Job is at state 'CANCELLED'.

2009-07-21T22:06:37.316+00:00

Machine details: ADS0\COGNOSWEBBI

User details: ADS0\cognos2

Process ID / Thread ID: 5732 / 380

Source: <SupplementalInfo><Source>LockHelper_73.LockHelper.Release</Source><StackInfo><ErrorGuid>{EA4F4FC4-57CC-48D8-A576-096B5AC892B6}</ErrorGuid><StackPosition>7</StackPosition><PreviousUserDomain>ADS0</PreviousUserDomain><PreviousUserName>cognos2</PreviousUserName><PreviousComputerDomain>ADS0</PreviousComputerDomain><PreviousComputerName>COGNOSWEBBI</PreviousComputerName></StackInfo></SupplementalInfo>
Error Number: -2147219891
Line Number: 230
Description: Unable to get Job Item

The Job management step failed.  An attempt has been made to mark the 'PUBLISH' Job as CANCELLED.  Please rectify the problem and re-create a similar Job.

The call to 'JobEnd' on 'Publish_%v.Implementation' was not successful.

The lock of 2 minutes had expired before we finished releasing it after 2 minutes, 2.39 seconds
See the log file for further details.

for this cognos gives a recomendation that please re create the publish container and its not possible as all the ETL activities are depending upon that

[rbuhrt]

First step would be to re-create the publish container.
Second step is to have both of your cognos services set to logon as an administrative user for the machine.
- Do the second step as best practice across all of your cognos servers

[amitbehere2002]

As I cannot recreate the Publish container as in above mentioned all the ETL activities are depending upon this

Kindly suggest the another solution

[rbuhrt]

Are you using SQL, Oracle, or DB2?

Either way if you completely delete your existing container and create a new one with the same name, you would be able to still use your ETL processing

[praveennb]

ETL should take care of the publish databases, even if it is dropped and recreated.

With each release of planning new columns or tables will get added to the publish database.