Symantec 10744983 Administration Guide - Page 151

Message The operation could not be performed is displayed

Page 151 highlights

Working with Spam Quarantine 151 Configuring Spam Quarantine Message "The operation could not be performed" is displayed Rarely, you or users at your organization may see the following message displayed at the top of the Spam Quarantine page while viewing email messages in Spam Quarantine: The operation could not be performed. See "Checking the Control Center error log" on page 210. Can't log in due to conflicting LDAP and Control Center accounts If there is an account in your LDAP directory with the user name of admin, you won't be able to log in to Spam Quarantine as admin, but you will still be able to log into the Control Center as admin. This is because your LDAP administrator account name conflicts with the default Control Center administrator account name. To address this problem, you can change the user name in LDAP. You cannot change the "admin" user name in the Control Center. Error in log file due to very large spam messages If you check the log file as described in Checking the Control Center error log and see lines similar to those listed below, the messages forwarded from the Scanner to Spam Quarantine are larger than the standard packet size used by MySQL (1 MB). com.mysql.jdbc.PacketTooBigException: Packet for query is too large (3595207 > 1048576) at com.mysql.jdbc.MysqlIO.send(MysqlIO.java:1554) at com.mysql.jdbc.MysqlIO.send(MysqlIO.java:1540) at com.mysql.jdbc.MysqlIO.sendCommand(MysqlIO.java:1005) at com.mysql.jdbc.MysqlIO.sqlQueryDirect(MysqlIO.java:1109) at com.mysql.jdbc.Connection.execSQL(Connection.java:2030) at com.mysql.jdbc.PreparedStatement.executeUpdate (PreparedStatement.java:1750) at com.mysql.jdbc.PreparedStatement.executeUpdate (PreparedStatement.java:1596) at org.apache.commons.dbcp.DelegatingPreparedStatement.executeUpdate (DelegatingPreparedStatement.java:207) at com.brightmail.dl.jdbc.impl.DatabaseSQLManager.handleUpdate (Unknown Source) at com.brightmail.dl.jdbc.impl.DatabaseSQLManager.handleUpdate

  • 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
  • 249

Message "The operation could not be performed" is displayed
Rarely, you or users at your organization may see the following message displayed
at the top of the Spam Quarantine page while viewing email messages in Spam
Quarantine:
The operation could not be performed.
See
“Checking the Control Center error log”
on page 210.
Can't log in due to conflicting LDAP and Control Center
accounts
If there is an account in your LDAP directory with the user name of
admin
, you
won't be able to log in to Spam Quarantine as
admin,
but you will still be able to
log into the Control Center as
admin
. This is because your LDAP administrator
account name conflicts with the default Control Center administrator account
name.
To address this problem, you can change the user name in LDAP. You cannot
change the "admin" user name in the Control Center.
Error in log file due to very large spam messages
If you check the log file as described in
Checking the Control Center error log
and
see lines similar to those listed below, the messages forwarded from the Scanner
to Spam Quarantine are larger than the standard packet size used by MySQL (1
MB).
com.mysql.jdbc.PacketTooBigException:
Packet for query is too large (3595207 > 1048576)
at com.mysql.jdbc.MysqlIO.send(MysqlIO.java:1554)
at com.mysql.jdbc.MysqlIO.send(MysqlIO.java:1540)
at com.mysql.jdbc.MysqlIO.sendCommand(MysqlIO.java:1005)
at com.mysql.jdbc.MysqlIO.sqlQueryDirect(MysqlIO.java:1109)
at com.mysql.jdbc.Connection.execSQL(Connection.java:2030)
at com.mysql.jdbc.PreparedStatement.executeUpdate
(PreparedStatement.java:1750)
at com.mysql.jdbc.PreparedStatement.executeUpdate
(PreparedStatement.java:1596)
at org.apache.commons.dbcp.DelegatingPreparedStatement.executeUpdate
(DelegatingPreparedStatement.java:207)
at com.brightmail.dl.jdbc.impl.DatabaseSQLManager.handleUpdate
(Unknown Source)
at com.brightmail.dl.jdbc.impl.DatabaseSQLManager.handleUpdate
151
Working with Spam Quarantine
Configuring Spam Quarantine