Creating Queries and Reports
with the TacServe Log Database
The TacServe Log Database of Call and Event Records
The TacServe MMC user interface includes views of information in the Call and Event logs. These logs are in a database at the default location:
C:\Documents and Settings\All Users\Application Data\TacServe\tacserve.mdb
As a database accessible with ODBC, the TacServe log database can also be viewed, analyzed and reported by various third-party programs. This tech note explains the use of two common tools, MS Query and Crystal Reports.
Querying the database with MS Query
MS Query is an optional component of a Microsoft Office install. It can be used to view and analyze the TacServe database as follows:
- Start the MSQRY32.exe program in the Program Files\Microsoft Office\Office\ folder.
- Choose File | New and under the Databases tab click on TacServe*.
- Choose either the CallLog or EventLog depending on if you want to view just the calls that the TacServe clients have made or all the events that TacServe is reporting.
- Now the TacServe data is loaded into MSQuery. Drag the * from the table you have chosen down to the lower part of the screen and all the columns will be displayed.
- Alternatively, individual columns can see dragged to the viewing area.
- You can now sort columns or search on any criteria.
Creating reports with Crystal Reports
- Open Crystal Reports
- Click File | New -> Blank Report | Create New Connection | ODBC | Expand TacServe
- Select the EventLog or CallLog, and use the arrow to move it to the right side.
- The TacServe database will be shown in the Field Explorer and columns may be moved onto the report.
- You can now use the extensive reporting features of Crystal Reports to create various reports of modem usage for auditing, billing or security uses.
Event and Call Log columns
Columns in the Event Log:
| |
EventTime |
The date and time in YYYY-MM-DD HH:MM:SS format of when each event took place |
| |
ClientAddress |
The IP address of the client that was responsible for the event. This will be blank for internal events such as notices for the stop and start of the TacServe service. |
| |
PortGroup |
The TacServe Port group that was accessed for the call (is blank for internal events) |
| |
ComPort |
The COM port that was used on the TacServer machine (is blank for internal events) |
| |
Event |
The type of event that occurred such as OPEN, CLOSE, DIAL (is blank for internal events) |
| |
User |
The username that used the COM port. This will be blank for internal events or if user authorization is not used |
| |
Duration |
The time that the COM port was in use (is blank for internal events) |
| |
PhoneNumber |
The phone number that was dialed (is blank if a phone number is not dialed) |
| |
Comment |
Detail for an internal event or error condition, blank otherwise |
Columns in the Call Log:
| |
Begin |
Date/time that the call was initiated |
| |
BytesRecieved |
The amount of bytes that were received from the TacServe modem during the call |
| |
BytesSent |
The amount of bytes that were sent to the TacServe modem during the call |
| |
ClientAddress |
The IP address of the client that made the call |
| |
ComPort |
The COM port that was used on the TacServe machine |
| |
Duration |
The time that the COM port was in use |
| |
PhoneNumber |
The phone number that was dialed |
| |
PortGroup |
The TacServe Port Group that was accessed for the call |
| |
ServerAddress |
The IP address of the TacServe machine |
| |
Status |
Shows if the call was successful or not |
| |
Type |
DATA or FAX depending on call type |
| |
User |
The username that used the COM port (is blank if user authorization is not used) |
|
