Symantec 10744983 Administration Guide - Page 153

Error in log file due to running out of disk space, Users receive notification messages

Page 153 highlights

Working with Spam Quarantine 153 Configuring Spam Quarantine 4 Specify additional filters as needed. 5 Click Display Filtered. Error in log file due to running out of disk space If you check log file as described in Checking the Control Center error log and see lines similar to those listed below, make sure that you haven't run out of disk space where Spam Quarantine is installed. 9 Jan 2004 00:00:22 (ERROR:5396:6396):[2032] Error connecting to 192.168.1.4:41025: Unknown Error; Out of range. 9 Jan 2004 00:00:22 (ERROR:5396:6396):[4042] smtp_direct: failed to connect to SMTP server. If that isn't the problem, follow the steps below. To correct this problem 1 Delete the following directory: .../Tomcat/jakarta-tomcat-version/work 2 Reboot the computer where Spam Quarantine is installed. Users receive notification messages, but can't access messages If some users at your company can successfully log into Spam Quarantine and read their spam messages but others get a message saying that there are no messages to display after logging in to Spam Quarantine, there may be a problem with the Active Directory (LDAP) configuration. If the users who can't access their messages are in a different Active Directory domain from the users who can access their messages, configure LDAP in the Control Center to use a Global Catalog, port 3268, and verify that the nCName attribute is replicated to the Global Catalog as described below. Configure access to a global catalog To configure access to an Active Directory Global Catalog, specify the port for the Global Catalog, usually 3268, in your LDAP server settings page in the Control Center. In addition, on the Active Directory server, verify that the nCName attribute is replicated to the Global Catalog. To replicate the nCName attribute to the Global Catalog using the Active Directory Schema snap-in 1 Click Start > Run, type regsvr32 schmmgmt.dll and click OK. 2 Click Start > Run, type mmc and click OK.

  • 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

4
Specify additional filters as needed.
5
Click
Display Filtered
.
Error in log file due to running out of disk space
If you check log file as described in
Checking the Control Center error log
and see
lines similar to those listed below, make sure that you haven't run out of disk
space where Spam Quarantine is installed.
9 Jan 2004 00:00:22 (ERROR:5396:6396):[2032]
Error connecting to 192.168.1.4:41025: Unknown Error; Out of range.
9 Jan 2004 00:00:22 (ERROR:5396:6396):[4042]
smtp_direct: failed to connect to SMTP server.
If that isn't the problem, follow the steps below.
To correct this problem
1
Delete the following directory:
.../Tomcat/jakarta-tomcat-
version
/work
2
Reboot the computer where Spam Quarantine is installed.
Users receive notification messages, but can't access messages
If some users at your company can successfully log into Spam Quarantine and
read their spam messages but others get a message saying that there are no
messages to display after logging in to Spam Quarantine, there may be a problem
with the Active Directory (LDAP) configuration. If the users who can't access their
messages are in a different Active Directory domain from the users who can access
their messages, configure LDAP in the Control Center to use a Global Catalog,
port 3268, and verify that the nCName attribute is replicated to the Global Catalog
as described below.
Configure access to a global catalog
To configure access to an Active Directory Global Catalog, specify the port for the
Global Catalog, usually 3268, in your LDAP server settings page in the Control
Center. In addition, on the Active Directory server, verify that the nCName
attribute is replicated to the Global Catalog.
To replicate the nCName attribute to the Global Catalog using the Active Directory
Schema snap-in
1
Click
Start > Run
, type
regsvr32 schmmgmt.dll
and click
OK
.
2
Click
Start > Run
, type
mmc
and click
OK
.
153
Working with Spam Quarantine
Configuring Spam Quarantine