Ricoh MP C6502 Manuals - Page 228

When the WSD scanner function cannot be used, Set Scan Profile. For details about how

Page 228 highlights

10. Troubleshooting When the WSD scanner function cannot be used Message Causes Solutions "Cannot communicate with PC. Contact the administrator." WSD (Device) protocol or WSD (Scanner) protocol is disabled. For details about how to enable or disable the WSD protocol, see Security Guide . "Cannot start scanning Scan Profile is not set on the because communication was client computer. failed." Set Scan Profile. For details about how to do this, see "Creating a New Scan Profile", Scan . "Cannot start scanning because communication was failed." The [Take no action] setting has been selected on the client computer, forcing the client computer to remain inactive when it receives scan data. Open scanner properties, click the [Events] tab, and then select [Start this program] as the computer's response on receipt of scan data. For details, see your operating system's Help. "Cannot start scanning. Check the setting(s) on the PC." The Scan Profile might be incorrectly configured. Check the Scan Profile configuration. "Could not send the data because the PC timed out before it was sent." A time out occurred when using WSD Scanner. Time outs occur when too much time passes between scanning an original and sending its data. The followings are likely causes of time outs: • Too many originals per set. • Misfed originals. • Transmission of other jobs. • Reduce the number of originals, and then scan again. • Remove any misfed original, and then scan again. • Use Scanner Journal to check there are no jobs awaiting transmission, and then scan again. 218

  • 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
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160
  • 161
  • 162
  • 163
  • 164
  • 165
  • 166
  • 167
  • 168
  • 169
  • 170
  • 171
  • 172
  • 173
  • 174
  • 175
  • 176
  • 177
  • 178
  • 179
  • 180
  • 181
  • 182
  • 183
  • 184
  • 185
  • 186
  • 187
  • 188
  • 189
  • 190
  • 191
  • 192
  • 193
  • 194
  • 195
  • 196
  • 197
  • 198
  • 199
  • 200
  • 201
  • 202
  • 203
  • 204
  • 205
  • 206
  • 207
  • 208
  • 209
  • 210
  • 211
  • 212
  • 213
  • 214
  • 215
  • 216
  • 217
  • 218
  • 219
  • 220
  • 221
  • 222
  • 223
  • 224
  • 225
  • 226
  • 227
  • 228
  • 229
  • 230
  • 231
  • 232
  • 233
  • 234
  • 235
  • 236
  • 237
  • 238
  • 239
  • 240
  • 241
  • 242
  • 243
  • 244
  • 245
  • 246
  • 247
  • 248

When the WSD scanner function cannot be used
Message
Causes
Solutions
"Cannot communicate with
PC. Contact the
administrator."
WSD (Device) protocol or
WSD (Scanner) protocol is
disabled.
For details about how to enable or
disable the WSD protocol, see Security
Guide
.
"Cannot start scanning
because communication was
failed."
Scan Profile is not set on the
client computer.
Set Scan Profile. For details about how
to do this, see "Creating a New Scan
Profile", Scan
.
"Cannot start scanning
because communication was
failed."
The [Take no action] setting
has been selected on the
client computer, forcing the
client computer to remain
inactive when it receives
scan data.
Open scanner properties, click the
[Events] tab, and then select [Start this
program] as the computer's response
on receipt of scan data. For details, see
your operating system's Help.
"Cannot start scanning.
Check the setting(s) on the
PC."
The Scan Profile might be
incorrectly configured.
Check the Scan Profile configuration.
"Could not send the data
because the PC timed out
before it was sent."
A time out occurred when
using WSD Scanner. Time
outs occur when too much
time passes between
scanning an original and
sending its data. The
followings are likely causes
of time outs:
Too many originals per
set.
Misfed originals.
Transmission of other
jobs.
Reduce the number of originals,
and then scan again.
Remove any misfed original, and
then scan again.
Use Scanner Journal to check
there are no jobs awaiting
transmission, and then scan
again.
10. Troubleshooting
218