Tech News

Investigations with Triaster Server Logs

Home

There are logs associated with much of Triaster functionality, whether it be publishing, approvals or using process library websites. These logs are often our initial focus when dealing with issues. They can offer evidence of something having happened, or suggest something didn't and perhaps why; when something happened; who may have been involved (an e-mail recipient, for example).

Publishing

These are the logs most pertinent to investigating publication issues:


Triaster\TriasterServer2011\
Logs\
Server\
PublicationLog Library Site Date Time.txt|.xml
Services\
PublicationServerLog Date.txt
PublicationTokenLog Date.txt
TaskFileProcessLog Date.txt

Publication Logs

The publication logs in the 'Server' folder are listed on the Administration Publication Tasks page. The Details pages show publication events, which can be filtered by categories 'Info' and 'Warning'. Do note that some errors can be listed as 'Info', so the absence of warnings doesn't necessarily mean an entirely successful publication.

Note:

If searching the Details webpage or the log file directly, some useful search terms:

"warning (include the double-quote if searching the log file directly) exception cannot load

Publication Service Logs

At its simplest, the record of a publication may be something like this:

10:42:35:Processing task process library live (TaskType=PUBLICATION)

10:43:52:SendConfirmationEmail2 Pre-Send: Sender=SenderAddress,Subject= Triaster publish (Library: process library Site:live) has completed successfully. Recipient= Recipient Address(es), SMTP details

10:43:52:Successfully processed task: process library_live (TaskType=PUBLICATION)

This suggests the publication completed (giving the start and end times of the publication), and the notification e-mail was sent.

Cloning

Cloning and deleting libraries and sites are run under the 'Triaster Improvement Workbench Server 2011' service.

This is its log:


Triaster\TriasterServer2011\
Logs\
Services\
ImprovementWorkbenchServerLog Date.txt

A record of a successful clone may be of this form:

11:01:06:before ProcessTask: strTaskType = CLONE_LIBRARY mstrLibrary=Template LibrarymstrStage= mstrOldStage=mstrNewStage= mstrNewLibrary=Process LibrarymstrOldLibrary=Template Library

11:01:19:Sucessfully processed task: CLONE_LIBRARY; Completed: The creation of Triaster library clone Process Library 11:01:20:SendConfirmationEmail Pre-Send: Sender=Sender Address,Subject= The creation of Triaster library clone Process Library has completed successfully Recipient= Recipient Address(es), SMTP details

11:01:20:after ProcessTask: strTaskType = CLONE_LIBRARY mstrLibrary=Template Library mstrStage= mstrOldStage=mstrNewStage= mstrNewLibrary=Process Library mstrOldLibrary=Template Library

Approvals and Alerts

Approval activity is recorded in these logs.


Triaster\TriasterServer2011\
Alerts\
AlertsSent.xml
Logs\
Browser Toolkit\
ApprovalsLog Date.txt
ToolsCommonLog Date.txt
Services\
AlertServerProcessLog Date.txt
PublicationServerLog Date.txt

Approving, Requesting Rework

Approving maps or requesting rework through the Approvals webpage is recorded in the Browser Toolkit Approvals Log.

15:28:47:strUniqueID(Rework Maps)=c:\triaster\triasterserver2011\mapstore\process library\prelive maps\my process map.vdx!{902115d7-55d5-4611-bb0c-64ddd22dd94b}

15:38:54:strUniqueID(Approved Maps)=c:\triaster\triasterserver2011\mapstore\process library\prelive maps\myprocess map.vdx!{902115d7-55d5-4611-bb0c-64ddd22dd94b}

These records reflect a map having been marked for rework, and later, approved.

Approvals Required Alerts

'Approvals Required' alerts are sent following a publication (typically, a Prelive publication), and are recorded in the Publication Server service log.

11:33:50:SendEmail Pre-send: Sender= Sender Address,Subject=Approvals Required (Process Library) Recipient= Recipient Address(es), SMTP details,strBody=e-mail HTML code

Perhaps most significantly, this record would identify the recipients and the maps requiring approval.

These alerts are also recorded in 'AlertsSent.xml', which Triaster Server uses as a reference. Such a record would be of this form:


 <Map Name="/processlibraries 2011/process library/prelive/html/my process map.mappage-1.html">
 <Alert type="ApprovalsRequired" approvertype="contentapprover">
 <Datesent>2016-03-23 </Datesent>
 </Alert>
 </Map>

Approvals Overdue Alerts

'Approvals Overdue' alerts are sent after a certain interval from Prelive for maps that require approval, but haven't yet been approved. They are recorded in the Alert Server service log.

15:09:57:SendEmail Pre-send: Sender=Sender Address,Subject=Reviews Overdue Reminder (Process Library) Recipient= Recipient Address(es), SMTP details,strBody=e-mail HTML code

These alerts are also recorded in 'AlertsSent.xml'. Such a record would be of this form:


 <Map Name="/processlibraries 2011/process library/prelive/html/my process map.mappage-1.html">
 <Alert type="Approval" approvertype="contentapprover">
 <Datesent>2016-03-23 </Datesent>
 </Alert>
 </Map>

Approved Maps, Maps Needing Rework Alerts

'Approved Maps' and 'Maps Needing Rework' alerts are sent when maps are approved or marked for rework through the Approvals webpage. These are recorded in the Tools Common log.

16:52:20:clsToolsCommon SendEmail Pre-send: Sender= SenderAddress,Subject= Approved Maps (process library) Recipient=Recipient Address(es), SMTP details,strBody=e-mail HTML code

15:29:56:clsToolsCommon SendEmail Pre-send: Sender= SenderAddress,Subject= Maps Needing Rework (process library)Recipient= Recipient Address(es), SMTP details,strBody=e-mailHTML code

A map's record in 'AlertsSent.xml' is updated.


 <Map Name="/processlibraries 2011/process library/prelive/html/my process map.mappage-1.html">
 </Map>

What's Changed Alerts

'What's Changed' alerts are sent following a Live publication by convention. These are recorded in the Publication Server service log.

16:10:03:SendEmail Pre-send: Sender=Sender Address,Subject=What's Changed Alert (Process Library) Recipient= Recipient Address(es), SMTP details,strBody=e-mail HTML code

And in 'AlertSent.xml':


 <Map Name="/processlibraries 2011/processlibrary/live/html/my process map.map page-1.html">
 <Alert type="Changed">
 <Text>My changes </Text>
 <ChangeDate>2016-03-23 </ChangeDate>
 </Alert>
 </Map>

Review Due Notice Alerts

'Review Due Notice' alerts are sent a number of days prior to the 'Next Review Date' for maps in Live. These are recorded in the Alert Server service log.

13:04:55:SendEmail Pre-send: Sender= Sender Address,Subject=Review Due Notice (process library) Recipient= Recipient Address(es), SMTP details,strBody=e-mail HTML code

In 'AlertsSent.xml':/


 <Map Name="/processlibraries 2011/process library/live/html/my process map.map page-1.html ">
 <Alert type="Revision">
 <Datesent>2016-03-23 </Datesent>
 </Alert>
 </Map>

Reviews Overdue Reminder Alerts

'Reviews Overdue Reminder' alerts are sent immediately after the 'Next Review Date', and then at intervals a number of days after. These are recorded in the Alert Server service log.

12:11:01:SendEmail Pre-send: Sender= Sender Address,Subject=Reviews Overdue Reminder (process library) Recipient= RecipientAddress(es), SMTP details,strBody=e-mail HTML code

In 'AlertsSent.xml':



 <Map Name="/processlibraries 2011/process library/live/html/my process map.map page-1.html ">
 <Alert type="Revision">
 <Datesent>2016-03-23 </Datesent>
 </Alert>
 </Map>


Browser Toolkit Logs

The Browser Toolkit refers to website functionality such as search, approvals, etc. There are various logs in this location:

Triaster\TriasterServer2011\Logs\Browser Toolkit

Often, an error in a web application will be reported through its webpage in a very generic manner, with no details offered. Reproducing that error when directly logged on to the server can reveal such details, but that option isn't available to most users. The Browser Toolkit logs may help, if, of course, they are accessible.

Summary

Much of Triaster activity is recorded in logs that can help when resolving issues or just confirming expected behaviour. The first step is knowing where to look! Some may be familiar and confident enough with Triaster functionality to investigate for themselves, but as much of this information is recorded in discrete files, it can easily be forwarded to us at Triaster, if required.

Register to receive product release notifications

SIGN UP FOR CONNECTOR

Sign up for Connector
Industry best practice and knowledge in our ‘best of breed’ newsletter.
Published bi-annually.

Signup here