cancel
Showing results for 
Search instead for 
Did you mean: 
Michael_Bilsbor
Level 6
Accredited
In V7 of Enterprise Vault we introduced a UI to allow you use the tracing component.
When you enable the capability (via Advanced Features in the VAC) when you start the new trace wizard you'll see a list of trace categories. This article is regarding those trace categories.

On the Enterprise Vault server, in Program Files\Scripts for Dtrace

All the .ini files in that directory are what are shown as trace categories in the Dtrace UI. So if there are trace categories that are not applicable to your environement you could just rename the file extension tp stop them appearing if you wish.
If perhaps you don't like the order they are displayed in the UI,make the commonly used ones appear at the top, go ahead and rename the files e.g. 1 - mailbox archiving issues.ini, 2 - retrieval and viewing issues.ini

When you restart the trace wizard after making the above changes you'll see that they have taken affect.

You can also edit the .ini files themselves.

The description that appears in the UI, comes from the .ini file so lets look at editing it.

So in Mailbox Archiving issues (Exchange).ini
The description was
Use this script to trace issues with scheduled, manual and run now MS Exchange Server mailbox archiving.

and I edited it and changed it to
Use this script to trace issues with scheduled, manual and run now MS Exchange Server mailbox archiving.
Components: ArchiveTask,AgentClientBroker,StorageArchive,w3wp

and saved the .ini

Now when you select the trace category it has this new description.

The categories themselves as I say are based upon the files, so there is nothing stopping you copying them and making your own to suit your own needs.

What you have to realise as well is the Commands section is pretty much raw dtrace statements so you can add various dtrace 'smarts' to your script as well.

So for example say you want to dtrace arhiving task but only show get a summary of what it's doing.

An example of archivetask filter.ini   (note you need to create this as a unicode file not ansi)

Description
This is an example of using filter command in dtrace.

Commands
set ArchiveTask v
filter
c i
+ "CArchivingAgent::MainProcessSystem() |Entering routine |"
+ ":CArchivingAgent::MainProcessSystem() |Getting a MAPI session from the session pool |"
+ ":CArchivingAgent::ProcessMailboxesInChunks() |Listing mailbox distinguished names |
+ ":AgentMessageDispenser::ActivateObject() |Called server side object, with arguments: |m_pIBackgroundArchivingAgent->ProcessUserEx(Priority"
+ "CMailboxUsage::SetMailboxInUse - Adding MbxDN to List:"
+ "A storage limit has been found on mailbox "
+ "CMailboxUsage::RemoveUserFromList - Removing MbxDN "
+ "CAA::PUEX() - Mailbox Folder Policy :"
+ "MAPICommon::GetFixed_PR_FOLDER_PATHNAME() - Setting output parameter "
+ "EFP - Folder Policy Settings| Filter Type ="
+ ":CArchivingAgent::ProcessMessages() |Entering routine |"

•":CArchivingAgent::ProcessUser() |Making all selected messages Archive Pending, "
•":CArchivingAgent::WriteWorkItemsToQueue() |Calling MakeItemPendingAndQueueMsg() |"
exit
log ?



Comments
TonySterling
Moderator
Moderator
Partner    VIP    Accredited Certified
Thanks Mike, keep them brain dumps coming!  :)
Simpson_Homer
Level 3
That's Nice...
Version history
Last update:
‎06-05-2009 03:59 AM
Updated by: