Can't publish pages.

 

iMIS 2017

We cannot publish pages. @/<XYZ>/ClinicalPracticeForum

Sample screen capture:

Capture2.jpg

 

Case Scenario:

When observing publishing pending status as shown above, and even if you republish the content item, and they are still getting stuck in publishing pending, that indicates there is a problem with publishing.

 

Some Validation Check Points: 

  • Do you have more than one iMIS App server connecting to a share iMIS Database?
  • If it is only one iMIS App server connected to a single iMIS Database, we will suggest fixing the publishing issue. Please, ensure to make a back up copy of your database as a best practice prior making SQL changes.

Be sure to back up your database prior making any changes:


-- Clear out any publish requests except for ones that are requesting a delete from index
delete from TaskQueuePublishDetail where ItemAction != 2
-- Clear out any parent rows for these delete publish requests
delete from TaskQueue where TaskQueueTypeId = 1 and TaskQueueId not in (select TaskQueueId from TaskQueuePublishDetail)
--Clear completed publishing logs
delete from PublishMessageLog where PublishRequestDetailKey not in (Select PublishRequestDetailKey from PublishRequestDetail where PublishedDateTime is not null)
delete from PublishRequestDetail where PublishedDateTime is not null
delete from PublishRequest where PublishRequestKey not in (Select PublishRequestKey from PublishRequestDetail)
 
-- *Proceed with caution here* - it's possible that resetting these back to "not started" will result in double processing of the tasks
-- if it got stuck after the task fired. There's no way to tell without manual inspection - check the task log and scheduler log around the time of the StatusUpdatedOn time in these rows.
-- There is a chance people could get duplicate emails, a stored procedure could be run twice, etc. But if you delete it, it's possible an important task won't be fired
-- *******************
-- Update any "processing" trigger details back to "requested" if they have been stuck for over 12 hours
Update TaskQueueTriggerDetail set TaskQueueStatusId = 1 where TaskQueueStatusId = 2 and StatusUpdatedOn < DATEADD(hour, -12, GETDATE())

 

After running the above delete SQL statements, follow these other steps:


Second, rebuild the SQLQueryNotifications in SQL Server Management Studio (SSMS). To do that:
- Stop the AsiSchedulerPool app pool on their iMIS app/web server
- Expand the iMIS database
- Expand Service Broker > Services > right click the iMISPublishServer and delete it
- Right click the SQLQueryNotificationService and delete it.
- Expand Queues and do the same there.
- Run DB Maintenance "prepare iMIS database" to recreate the SQL Server Broker services and queues
- Start the AsiSchedulerPool app pool and browse the scheduler application in a web browser on the iMIS app/web server.
- Publish a new content, and test publishing again.

I hope the above helps.

 

Prior running the Delete Statement, you are welcome to review these tables as follows:

 

-- Clear out any publish requests except for ones that are requesting a delete from index
SELECT * FROM TaskQueuePublishDetail where ItemAction !=2
-- Clear out any parent rows for these delete publish requests
SELECT * from TaskQueue where TaskQueueTypeId = 1 and TaskQueueId not in (select TaskQueueId from TaskQueuePublishDetail)

--Clear completed publishing logs
SELECT * from PublishMessageLog where PublishRequestDetailKey not in (Select PublishRequestDetailKey from PublishRequestDetail where PublishedDateTime is not null)
SELECT * from PublishRequestDetail where PublishedDateTime is not null
SELECT * from PublishRequest where PublishRequestKey not in (Select PublishRequestKey from PublishRequestDetail)

-- *Proceed with caution here* - it's possible that resetting these back to "not started" will result in double processing of the tasks
-- if it got stuck after the task fired. There's no way to tell without manual inspection - check the task log and scheduler log around the time of the StatusUpdatedOn time in these rows.
-- There is a chance people could get duplicate emails, a stored procedure could be run twice, etc. But if you delete it, it's possible an important task won't be fired
-- *******************
-- Update any "processing" trigger details back to "requested" if they have been stuck for over 12 hours

SELECT * FROM TaskQueueTriggerDetail where TaskQueueStatusId = 2 and StatusUpdatedOn < DATEADD(hour, -12, GETDATE())

 

The above recommended steps helped getting this type of concern resolved for other customers.

If the above did not help, please reference to the other public kb article: 

https://support.imis.com/hc/en-us/articles/360041014991-After-publishing-root-publishing-task-appears-stuck

Ref zd119296, zd130985

0 Comments

Article is closed for comments.
Powered by Zendesk