Transaction Log Format

Each record in the transaction log includes at least two fields in addition to the timestamp and device name:

Message Type Code – Identifies the type of event that has occurred. This is a number that corresponds to the description immediately following. If this log is being read by a software program, a number is very easy to use for comparison when looking for specific message types.
Message Type Description – Text that describes the message type code.

The following table is a list of the different messages that can appear in the transaction log, some of the optional parameters and what the message means. Where appropriate, a suggested response to the message is provided.

Transaction Log Messages
Code	Message Text	Message Parameters	Message Meaning	User Response to Message
1	Network device added	Device Name	A new device was added to the network map.
2	Network branch deleted	Device Name	A branch of the network map was deleted (this may consist of a single device)
3	Network branch moved	Device Name	A branch of the network map was moved from one parent device to another (not supported in LoggerNet 1.1)
5	Network logon succeeded	Logon Name
6	Network logon failed	Logon Name	A client application failed to attach to the server	If unsuccessful logon messages occur frequently, use a network monitor to determine who is trying to connect. If security is enabled this message will appear for someone trying to connect with the wrong user name or password.
7	Security session opened		The security configuration utility has attached to the server.
8			When the server started up it could not read the security settings file.	This is a normal message on server startup if security has not been set up. If security should be set the file needs to be removed and security re-configured.
9	Modem default database read failed		When the server started up it could not read the default modem file wmodem.ini.	This file should exist in the working directory on the server computer (c:\campbellsci \loggernet\sys\bin). May indicate a permissions or configuration problem on the computer.
10	Modem custom database read failed		When the server started up it could not read the user customized modem settings file wmodem.cust.	If the user has not set up custom modem configurations, this file will not exist.
11	Clock check started		A clock check has been initiated. This clock check is not sent out to the station until the transaction is sent.
12	Clock set	Device time before set; Server time;	The device clock has been set.
13		Datalogger time	The datalogger clock has been checked.
14	Clock check failed	Reason code: 3. Communication failure 4. Invalid datalogger security clearance 5. Invalid transaction number specified (already in use) 6. Communications are disabled for this device 7. The transaction was aborted by client request 8. The device is busy with another transaction	The clock check/set failed for the reason specified in the reason code.	Check the connections of the communication path to the datalogger, make sure the datalogger is connected and has power, check the security setting in the datalogger and in Setup, check that communications are enabled in Setup for all the devices in the path.
15	Starting BMP data advise transaction		A start data advise operation has been initiated. Data advise is not in place until the datalogger responds.
16	Stopping BMP data advise transaction		A stop data advise operation has been initiated.
17	BMP data advise transaction started		The message from the datalogger confirming the start of data advise has been received.
18	BMP data advise transaction stopped		The message from the datalogger confirming the suspension of data advise has been received.
19	BMP data advise transaction failed		The attempt to start or stop a data advise with the datalogger has failed or the operation has timed out waiting for a response.	Check communications with the datalogger by trying to check the clock. If that fails follow the steps for message 14.
20	Hole detected	Table name; Beginning record number; Ending record number	A hole or missed records has been detected in the data coming from the	The server will automatically try to collect the data if hole collection is enabled.
21	Hole collected	Table name; Beginning record number; Ending record number	The missing records specified have been collected from the datalogger.
22	Hole lost	Table name; Beginning record number; Ending record number	The missing records have been overwritten in the datalogger.
23	Hole collect start	Table name; Beginning record number; Ending record number	The hole collect request has been started. This message won’t go to the datalogger until the BMP1 message is sent. (see message 104)
24	Hole collect response received		The datalogger has returned the response to the hole collect request. This will contain either the data or state that the hole is lost.
25	Hole collect failed		The hole collection request either timed out or a communication failure occurred.	Check communications with the datalogger by trying to check the clock. If that fails follow the steps for message 14.
26	Data polling started		Data collection by polling started.
27	Data polling complete		Data collection by polling completed
28	Data polling failed		Data collection by polling failed due to communication failure or a timeout.	Check communications with the datalogger by trying to check the clock. If that fails, follow the steps for message 14.
29	Directed data query start		A user initiated query has been started.
30	Directed data query continue		The requested data in the directed query could not fit in one block and the next part is being requested.
31	Directed data query complete		The user requested data has been received by the server.
32	Directed data query failed		The directed query request failed.
33	Getting logger table definitions		The server is getting the table definitions from the datalogger.	Getting the datalogger table definitions will erase any data in the data cache.
34	Received logger table definitions		The server has received the datalogger table definitions.
35	Failed to get logger table definitions		The request to get table definitions has failed.
36	Logger table definitions have changed		The server has detected a change in the table definitions in the datalogger.	A change in table definitions indicates that the datalogger program may have changed. Before updating table definitions make sure the needed data in the data cache has been saved to a file if desired.
37	Updating BMP1 network description		The network description in the RF base is being updated to reflect changes in collection schedule or stations to collect.
38	BMP1 network description update complete		The RF base has acknowledged the network description update.
39	BMP1 network description update failed		The network description update to the RF base has either timed out or communication has failed.	Check the connections from the PC to the RF base.
40	Datalogger message	Severity (S for Status, W for Warning, F for Fault); Message text.	This is a message that has been generated by the datalogger (or in some cases the RF base on behalf of the datalogger).	Datalogger warning and fault messages should be investigated using the datalogger operators manual or contacting an applications engineer at Campbell Scientific.
41	Records received	Table name; Beginning record number; Ending record number	Datalogger records have been received and stored in the data cache.
42	A datalogger transaction has timed out	Time out period in milliseconds	The server has waited longer than the allotted time for the expected response to a transaction.	Determine the reason for the timeout. This is usually due to a problem with the communications path between the PC and the datalogger.
43	Terminal emulation transaction started		Terminal emulation message has been sent to the datalogger.
	Terminal emulation transaction complete		Terminal emulation response message has been received from the datalogger.
45	Terminal emulation transaction failed		The expected terminal emulation response from the datalogger was not received.
46	Set variable started		The message to set an input location, flag or port has been sent to the datalogger.
47	Set variable complete		The datalogger has acknowledged the set of an input location, flag or port.
48	Set variable failed		The datalogger failed to acknowledge the set variable message.
49	Table resized		The size of the table storage area in the data cache has been changed.	If the table is made smaller the oldest data will be lost.
50	Program file send start		The server is sending a program to the datalogger. The actual program segments will appear as BMP1 message type 4.
51	Program file send status		The datalogger has received the program segment.
52	Program file send complete		The datalogger has compiled the program.
53	Program file send failed		The datalogger did not acknowledge the receipt of the program, the program did not compile, or communications failed with the datalogger.	If the program did not compile check the error messages. Otherwise, check communications with the datalogger by trying to check the clock. If that fails, follow the steps for message 14.
54	Program file receive start		The server is requesting the datalogger program. The actual program segments will appears as BMP1 message type 5.
55	Program file receive status		A program segment has been received.
56	Program file receive complete		The datalogger program has been received from the datalogger.
57	Program file receive failed		The datalogger failed to send the program or communications with the datalogger failed.	Check communications with the datalogger by trying to check the clock. If that fails, follow the steps for message 14.
58	Collection schedule: normal		This is an advisory message that the normal data collection schedule is active.
59	Collection schedule: primary retry		A normal data collection has failed and data collection will be attempted at the primary retry interval.	Determine the reason for communication failure. Temporary communication problems may cause the collection state to change between normal and primary.
60	Collection schedule: secondary retry		The number of primary retries specified has passed and data collection will be attempted at the secondary retry interval.
61	Collection schedule suspended		The scheduled data collection has been turned off or suspended because communication is disabled or table definitions have changed.
62	Primary retry collection attempt failed		Data collection on the primary data collection interval failed.	Check communications with the datalogger by trying to check the clock. If that fails, follow the steps for message 14.
63	Secondary retry collection attempt failed		Data collection on the secondary data collection interval failed.	Check communications with the datalogger by trying to check the clock. If that fails, follow the steps for message 14.
64	Device restore from file succeeded		On server startup a device previously entered in the network map has been restored.
65	Device restore from file failed		On server startup a device in the network map could not be restored.	This is an indication that the configuration file has been corrupted. Check the network map and the computer file system.
66	Device save to file succeeded		The update to the device configuration file was successful.
67	Device save to file failed		The update to the device configuration file failed.	This may be due to a problem with directory permissions or a corrupted directory.
68	Packet delivery failed	Fault code: 1. Incompatible BMP1 device or malformed packet 2. Routing failure {unrecognized station number} 3. Temporarily out of resources 4. Link failure	This is a message from the RF base indicating that a BMP1 message didn’t make it to the data logger.	Codes 1 and 3 are rare. If ever seen contact an technical support engineer at Campbell Scientific. Code 2 indicates that the RF base has lost the network map and doesn’t know how to route the message. The server automatically resends the network map. Code 4 is an indication that the RF base was not able to communicate with the RF modem attached to the datalogger. These will happen occasionally as part of normal operations. Frequent occurrences indicate that the radio, antenna, connectors and RF link be reviewed.
69	Unexpected change in datalogger table definitions		As part of data collection the server has detected a change in the datalogger’s table definitions.	A change in table definitions indicates that the datalogger program may have changed. This will suspend data collection and warnings will be shown in the Status Monitor. Data Collection can only be restored by updating table definitions. Before updating table definitions make sure the needed data in the data cache has been saved to a file if desired.
70	A device setting value has changed	Setting Identifier; Client’s logon name; New value of the setting	A client has changed one of the device configuration settings.
71	A LgrNet setting value has changed	Setting Identifier; Client’s logon name;	A client has changed one of the server configuration settings.
72	Client defined message	Client defined message	These messages are placed in the transaction log by client applications. The message should indicate which client entered the message.
73	Socket listen failed		Indicates an error in the computer system that prevents the server from listening for client connections on a socket.	This is a rare error and results in a problem with the computer operating system. If rebooting the computer does not clear the error, contact an application engineer
74	Device renamed		The name of a device in the network was changed.
75	Logger locked		This message indicates the start of a transaction such as terminal emulation that will tie up the datalogger preventing other operations.
76	Logger unlocked		The transaction blocking datalogger access has completed.
77	Null program sent		The server has sent a null program to get an older datalogger (CR7X or 21X) out of keyboard emulation mode.
78	Server started	The server version	The server has been started.
79	Server shut down		The server is being shut down	If a new “server started” message is seen without the shut down message before it, this is an indication that the server or the PC crashed without exiting properly.
80	Collect area initialized	Collect area name	A data cache collect area has been created.
82	Collect area removed		A data cache collect area has been removed
83	LgrNet restore failed		On server startup the network description file, csilgrnet.dnd, could not be read.	The network setup and configuration will have to be restored from a backup or re-entered. Try to determine what corrupted or removed the network description file.
84	Security manager restore failed		On server startup the security manager database could not be restored.	There is a problem with the computer or operating system. If rebooting the machine does not get it working get help from someone who can troubleshoot computer problems.
85	Data restore failed		On server startup the data broker data storage area could not be created.	This is a computer problem. The files are either not present or are corrupted. See notes for message 83.
86	Manual poll transaction started	Client logon name	The listed client is starting a manual poll operation according to the scheduled collection settings. A manual poll is initiated from the Collect Now button on the Connect Screen.
87	Manual poll transaction complete		The manual poll operation has received the data from the datalogger.
88	Manual poll aborted		The manual poll operation was stopped or failed to complete due to communications failure or a timeout.	Check communications with the datalogger by trying to check the clock. If that fails, follow the steps for message 14.
89	Selective manual poll begun	Collect area name	A user specified poll has been started for one of the datalogger collect areas.
90	Selective manual poll complete	Collect area name	The user specified manual poll has completed.
91	Selective manual poll aborted	Collect area name	The user specified manual poll failed.	Check communications with the datalogger by trying to check the clock. If that fails, follow the steps for message 14.
92	Polling started on collect area	Collect area name	Data has been requested for the specified collect area. This message is always associated with another message indicating whether this is scheduled, manual or selective manual polling.	Collect areas can be table for table mode dataloggers, final storage areas, ports and flags, or input locations.
93	Collect area poll data	Collect area name	Data has been received from an array based datalogger for the specified collect area.
94	Collect area polling complete	Collect area name	Data collection for the specified collect area has successfully completed.
95	Collect area polling failed	Collect area name	Data collection for the specified collect area failed.	Check communications with the datalogger by trying to check the clock. If that fails, follow the steps for message 14.
96	Scheduled polling begun		Scheduled data collection has started.
97	Scheduled polling succeeded		Scheduled data collection has completed.
98	Scheduled polling failed		Scheduled data collection failed.	Check communications with the datalogger by trying to check the clock. If that fails, follow the steps for message 14.
99	Collect area first poll		This message is posted either the first time data is collected for a collect area, or holes were lost for the datalogger.	If this is not the first poll for the collect area, this message indicates that data that had been stored in the datalogger was lost before it could be collected.
100	Table mount failed	Table name; Operating system information regarding the failure	The server was not able to create a data collection area from the stored table configuration file or new table definitions. This could be the result of trying to create table files that are too large for the computer system.	Check the computer operating system integrity. Verify that the LoggerNet system configuration files exist and the directory has not been corrupted.
101	Add record failed	Table name; Beginning record number; End record number; A reason for the failure	The server was not able to write data records to the data storage area.	This indicates a problem writing to files on the computer hard disk. Verify write permissions are set and that there is sufficient space left on the disk.
102	Collect area skipped warning	Collect area name	The specified collect area was skipped because the associated table has not been initialized by the server yet.	During system startup this is a normal message. If it occurs at other times contact an application engineer.
103	Collect area skipped error	Collect area name	The specified collect area was skipped because the server could not initialize the associated table.	See message 100
104	BMP1 packet sent	The packet message type code: 0 Packet Delivery Fault Notification 1 Status/Warning/Fault Notification 2 Network Description Transaction 3 Clock Check/Set Transaction 4 Program Down-load Transaction 5 Program Up-load Transaction 7 Data Advise Command Transaction 8 Data Advise Notification Packet 9 Hole Collection Command Transaction 10 Control Command (Set Variable) Transaction 11 User I/O Transaction (Terminal Mode) 12 Memory Image Down-load Transaction 13 Memory Image Up-load Transaction 14 Get Table Definitions Transaction 15 RF Test Transaction 16 Communication Status Notification	The specified BMP1 packet was sent to the serial communication interface. The number specifies the type of message that was sent.
105	BMP1 packet received	The packet message type code: 0 Packet Delivery Fault Notification 1 Status/Warning/Fault Notification 2 Network Description Transaction 3 Clock Check/Set Transaction 4 Program Down-load Transaction 5 Program Up-load Transaction 7 Data Advise Command Transaction 8 Data Advise Notification Packet 9 Hole Collection Command Transaction 10 Control Command (Set Variable) Transaction 11 User I/O Transaction (Terminal Mode) 12 Memory Image Down-load Transaction 13 Memory Image Up-load Transaction 14 Get Table Definitions Transaction 15 RF Test Transaction 16 Communication Status Notification	The specified BMP1 packet was received over the serial communications link. The number indicates the type of message received.The specified BMP1 packet was received over the serial communications link. The number indicates the type of message received.
106	Data file output failed		Data collected from a datalogger could not be written to the data output file.	Check that there is space available on the hard disk and that write permissions allow the server to write the data output files.
107	Max time on-line exceeded	The amount of time the device was connected, in milliseconds	A client kept the communication link on-line longer than the specified max time on-line.
108	Table reset	The name of the table that was reset; The account name of the logged in client	The name of a table was changed at the request of a client. On CR5000 and CR9000 loggers this is a reset for the table in the datalogger and on the PC.
109	Collect schedule reset	The account name of the logged in client	The collection schedule was reset by the indicated client.
110	Collect area setting changed	The name of the collection area; The setting identifier for the setting that was changed; The new value of the setting; The account name of the logged in client.	One of the settings for the specified collect area was changed. The identifiers for the setting can be found in CoraScript help.
111	PakBus route added		A new PakBus route has been added to the routing table.
112	PakBus route lost		A PakBus route has been lost and will be removed from the routing table.
113	PakBus station added		A new PakBus station was added to the network.
114	Call-back begin		A device has called in to the server starting the call-back response.
116	Call-back stopped		A datalogger that called in to the server with call-back is hanging up.
117	Client logged off	The login name of the client; The reason the session was closed.	A client application has closed or lost the connection to the server.
118	Table size reduced during creation	The size of the table in the data cache was reduced because there was not enough computer disk space to create it, or the file would have exceeded the 2 Gbyte size limit.	Reduce the size of the tables in the datalogger program or get more hard disk storage space for the computer.
119	Security enabled	Account name used to enable security.	Security has been enabled on the LoggerNet server.	Usernames and passwords will now be required for communication with the LoggerNet server.
120	Security disabled	Account name used to disable security.	Security has been disabled on the LoggerNet server.
121	Security account added	Account name used to add new account; Name of the account that was added.	A new security account has been added.
122	Security account changed	Account name used to change account; Name of the account that was changed.	A change has been made to the attributes of a security account.
123	Security account deleted	Account name used to delete account; Name of the account that was deleted.	A security account has been deleted.
124	Security interface locked	Account name used by the client that started the transaction that locked the interface.	The security interface is locked because an account is currently making changes to the interface.
125	Security interface unlocked	Account name used by the client that started the transaction that unlocked the interface.	The security interface is unlocked because pending changes were applied or canceled.
126	Network lock started	Account name used by the client that started the transaction that locked the network; Client that started the transaction that locked the network.	The network is locked because a client is currently making changes to the interface.	Some functionality will be disabled until the network lock is stopped. To unlock, determine why the client transaction locked the network. For instance, there may be unapplied changes in the Setup Screen. Apply or cancel the changes to unlock the network.
127	Network lock stopped		The network is unlocked because pending changes were applied or canceled.
128	Set value command received	Name of the table specified; Name of the field specified.	A device has requested to set a value in one of its tables.
129	Column renamed	Name of the table; Original column name; New column name; Reason why column was renamed.	The name of a column has been changed due to an incompatibility with a previous field in the table that had the same name.
130	Last primary retry failed	Number of retries that were made.	The last primary retry attempt failed.	Check the connections of the communication path to the datalogger, make sure the datalogger is connected and has power, check the security setting in the datalogger and in Setup, check that communications are enabled in Setup for all the devices in the path.
131	Working directory snapshot	Name of the file that was created.	The server created a backup.
132	Working directory snapshot restored	Name of the file from which the network was restored.	The network was restored from a backup file.
133	File receive started	Name of the file being received.	The server has begun a file retrieval from the datalogger.
134	File receive completed	Name of the file received.	The server completed a file retrieval from the datalogger.
135	File receive failed	Name of the file received; Reason for the failure.	The server failed to retrieval a file.	Check the connections of the communication path to the datalogger, make sure the datalogger is connected and has power, check the security setting in the datalogger and in Setup, check that communications are enabled in Setup for all the devices in the path.
136	File send started	Name of the file being sent.	The server has begun to send a file to the datalogger.
137	File send completed	Name of the file sent.	The server has completed a file send to the datalogger.
138	File send failed	Name of the file sent; Reason for the failure.	The server failed to send a file to the datalogger.	Check the connections of the communication path to the datalogger, make sure the datalogger is connected and has power, check the security setting in the datalogger and in Setup, check that communications are enabled in Setup for all the devices in the path.
139	Collect area poll stopped due to table interval		Polling on a collect area was aborted because the table interval has not expired.
140	Device setting override	Setting identifier; Name of the user’s account overriding the setting; Value of the setting.	One of the device settings has been overridden.
141	Device setting override stopped		The device setting override has been stopped.
142	Collect area setting overridden	Name of the collect area; Setting identifier; Name of the user overriding the setting; Value of the setting.	One of the device collect area settings has been overridden.
143	Device collect area setting override stopped		The device collect area setting override has been stopped.
144	Data file opened	Collect area name; File name.	Collect area data file has been opened by the server.
145	Data file closed	Collect area name; File name.	Collect area data file has been closed by the server.
146	Datalogger query started	Table name; Query Mode; Client Logon Name	A datalogger query has been started by a client.
147	Datalogger query temp table created	Table name; Temporary table name.	A temporary cache table has been created for a datalogger query.
148	Datalogger query records received	Table name; Begin record number; End record number.	Records have been received from the datalogger for a datalogger query transaction.
149	Datalogger query complete	Table name.	All of the data for a datalogger query transaction has been collected from datalogger.
150	Datalogger query closed	Table name.	Client has closed a datalogger query transaction.
151	Existing data file renamed	Collect area name; File Name; Reason for renaming.	Server has renamed an existing data file as a result of attempting to append data in an incompatible format.	Existing data file will be renamed with a .backup extension. New data will be stored to the specified file name.
153	Program/TDF file associate start	User account name.	Client has begun a program file association transaction.
154	Program/TDF file associate complete		Program file associate transaction has successfully concluded.
155	Program/TDF file associate failed	Reason for the failure.	Program file associate transaction has failed.
156	File control started	File control command; First argument (optional); Second Argument (optional); User name (optional).	A file control operation has begun with a PakBus datalogger.
157	File control complete	File control command; First argument (optional); Second Argument (optional); User name (optional).	A file control operation with a PakBus datalogger has successfully completed.
158	File control failed	File control command; First argument (optional); Second Argument (optional); User name (optional).	A file control operation with a PakBus datalogger has failed.	Check the connections of the communication path to the datalogger, make sure the datalogger is connected and has power, check the security setting in the datalogger and in Setup, check that communications are enabled in Setup for all the devices in the path.

Transaction Log Example

"2009-04-15 16:41:05.367","CR1000","11","Clock check started"
"2009-04-15 16:41:05.429","CR1000","13","Clock checked","2009-04-15 16:41:33.44","2009-04-15 16:41:05.421","-28"
"2009-04-15 16:41:06.367","CR1000","86","Manual poll started","admin"
"2009-04-15 16:41:06.367","CR1000","92","Collect area poll started","TestFast"
"2009-04-15 16:41:06.382","CR1000","41","Records received","TestFast","21007","21007","polling"
"2009-04-15 16:41:06.382","CR1000","20","Hole detected","TestFast","20769","21006"
"2009-04-15 16:41:06.429","CR1000","11","Clock check started"
"2009-04-15 16:41:06.492","CR1000","41","Records received","TestFast","20769","20799","polling"
"2009-04-15 16:41:06.507","CR1000","144","data file opened","TestFast","C:\Campbellsci\LoggerNet\CR1000_TestFast.dat"
"2009-04-15 16:41:06.507","CR1000","21","Hole collected","TestFast","20769","20799"
"2009-04-15 16:41:06.507","CR1000","41","Records received","TestFast","20800","20864","polling"
"2009-04-15 16:41:06.507","CR1000","21","Hole collected","TestFast","20800","20864"
"2009-04-15 16:41:06.523","CR1000","13","Clock checked","2009-04-15 16:41:34.55","2009-04-15 16:41:06.516","-28"
"2009-04-15 16:41:06.601","CR1000","41","Records received","TestFast","20865","20899","polling"
"2009-04-15 16:41:06.601","CR1000","21","Hole collected","TestFast","20865","20899"
"2009-04-15 16:41:06.601","CR1000","41","Records received","TestFast","20900","20960","polling"
"2009-04-15 16:41:06.601","CR1000","21","Hole collected","TestFast","20900","20960"
"2009-04-15 16:41:06.648","CR1000","41","Records received","TestFast","20961","20999","polling"
"2009-04-15 16:41:06.648","CR1000","21","Hole collected","TestFast","20961","20999"
"2009-04-15 16:41:06.648","CR1000","41","Records received","TestFast","21000","21006","polling"
"2009-04-15 16:41:06.648","CR1000","21","Hole collected","TestFast","21000","21006"
"2009-04-15 16:41:06.679","CR1000","145","data file closed","TestFast","C:\Campbellsci\LoggerNet\CR1000_TestFast.dat"
"2009-04-15 16:41:06.679","CR1000","94","Collect area poll complete","TestFast","956","956"
"2009-04-15 16:41:06.695","CR1000","87","Manual poll complete"
"2009-04-15 16:41:07.429","CR1000","11","Clock check started"
"2009-04-15 16:41:07.445","CR1000","13","Clock checked","2009-04-15 16:41:35.46","2009-04-15 16:41:07.438","-28"
"2009-04-15 16:41:08.429","CR1000","11","Clock check started"