Submit a ticketCall us

WebinarDatabase Roundtable – Expert Database Professionals Feel Your Pain

In this video broadcast, Head Geek™ Tom LaRock is joined by Karen Lopez, Tim Chapman, and David Klee. They’ve known each other for many years, so this discussion was like four friends getting together to talk data and databases. They discussed diagnostic data collection, common performance root causes, reactive tuning versus proactive, and more. Join us for an engaging discussion on these topics! Plus, Tom LaRock will be available to answer your questions live.

Register now.

Home > Success Center > Kiwi CatTools > Kiwi CatTools Documentation > Kiwi CatTools 3.11 Administrator Guide > Troubleshooting > Reporting problems

Reporting problems

Table of contents
No headers
Created by Caroline Juszczak, last modified by Caroline Juszczak on Jun 28, 2016

Views: 184 Votes: 0 Revisions: 1


When reporting a problem with CatTools, please ensure you provide as many details as possible.


If, for instance, you are getting an error logging on to a device, tell us what the actual error is that you are getting. An error message should be present in the infolog that describes the error.


It is very helpful to know what type of device the problem is happening to. CatTools supports a number of different devices that can exhibit very different problem behaviours.


If you are sending us your infolog.txt file it is very helpful to tell us the approximate time the problem occurred. It is easy for us to miss something when we are scanning a 50MB text file for an error message.


Please do not send us raw screen shots of messages or setup issues unless there is no other way of getting the information across. Mail servers often block this data, and they produce very big emails. Use the CatTools facilities on the File menu to provide us with the text information.


If sending data present in the infolog, please send the file itself as an attachment, zipped if it is large. Trying to copy and paste entries from the infolog into an email can produce some pretty garbled emails. We often need to see more of the infolog than is copied to the email as well to provide us with context.


Doing this allows us to answer your queries in the quickest time.


Last modified