Intermec PM4i EasyADC for Microsoft Great Plains User's Manual - Page 67

Using the Systems Manager, Log Transactions, Error Log, Transaction Log

Get Intermec PM4i PDF manuals and user guides View all Intermec PM4i manuals
Add to My Manuals
Save this manual to your list of manuals

Page 67 highlights

Chapter 3 - Using the Data Collection Manager • The Error Log can help you troubleshoot problems. For example, if Great Plains transactions are not being completed while scanning, or if you see generic error messages on the CK30s (such as, "POP(U) Error" or any error message with the module plus parenthesis containing a number or a letter) you should check the error log and send a copy to the technical support staff at Intermec. The error log file is called MDSErr.TXT and is located in the EasyADC program folder. • The Transaction Log is also used primarily for troubleshooting. This log is saved only if you enable the Log Transactions parameter on the Systems Manager Settings screen, as described on page 90. The transaction log file is called MDSTrx.TXT and is located in the EasyADC program folder. To view the error log 1 Start Data Collection Manager, as described on page 28. The DCM main screen appears. 2 Choose View > Error Log. View Menu: Choosing to view the Error Log. To view the transaction log 1 Start Data Collection Manager, as described on page 28. The DCM main screen appears. 2 Choose View > Transaction Log. Using the Systems Manager The Systems Manager controls the CK30s. Without the System Manager running, the CK30s would be lifeless. The Systems Manager starts up immediately whenever the Data Collection Manager is launched, as described on page 28. The Systems Manager does not require user input, but it does display useful information. You should always leave the Systems Manager on. EasyADC System User's Manual 55

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
Chapter 3 — Using the Data Collection Manager
EasyADC System User’s Manual
55
• The Error Log can help you troubleshoot problems. For example, if
Great Plains transactions are not being completed while scanning, or if
you see generic error messages on the CK30s (such as, “POP(U) Error”
or any error message with the module plus parenthesis containing a
number or a letter) you should check the error log and send a copy to
the technical support staff at Intermec.
The error log file is called MDSErr.TXT and is located in the EasyADC
program folder.
• The Transaction Log is also used primarily for troubleshooting. This log
is saved only if you enable the
Log Transactions
parameter on the
Systems Manager Settings screen, as described on page 90.
The transaction log file is called MDSTrx.TXT and is located in the
EasyADC program folder.
To view the error log
1
Start Data Collection Manager, as described on page 28. The DCM
main screen appears.
2
Choose
View
>
Error Log
.
View Menu:
Choosing to view the Error Log.
To view the transaction log
1
Start Data Collection Manager, as described on page 28. The DCM
main screen appears.
2
Choose
View
>
Transaction Log
.
Using the Systems Manager
The Systems Manager controls the CK30s. Without the System Manager
running, the CK30s would be lifeless. The Systems Manager starts up
immediately whenever the Data Collection Manager is launched, as
described on page 28.
The Systems Manager does not require user input, but it does display
useful information. You should always leave the Systems Manager on.