IBM E027SLL-H Troubleshooting Guide - Page 36
Diagnosing that portal server logon fails, The portal client does not respond, Diagnosing that
![]() |
View all IBM E027SLL-H manuals
Add to My Manuals
Save this manual to your list of manuals |
Page 36 highlights
Procedure 1. Check the status of the instance in theDB2 Control Panel. 2. Recycle the portal server and resolve any issues reported. 3. Ensure that the user ID and password are correct. Diagnosing that portal server logon fails Logging on to the Tivoli Enterprise Portal Server fails when a user ID is locked, disabled, or an internal error occurs during logon. Examine the portal server or portal client logs for more information. The logon failure might cause one or more of the following messages to display: v KFWITM392E: Internal error occurred during logon. v KFWITM009I: The Tivoli Enterprise Portal Server is still being initialized and is not ready for communications. v KFWITM010I: Tivoli Enterprise Portal Server not ready. v KFWITM395E: User ID has been locked or disabled. v KFWITM396E: User ID has been locked or disabled by Tivoli Enterprise Portal Server. About this task To diagnose that the portal server logon Tivoli Enterprise Portal Logon fails, perform the following steps: Procedure Preliminary diagnostics 1. For a guide to the messages and operator responses, refer to IBM Tivoli Monitoring: Messages (http://publib.boulder.ibm.com/infocenter/tivihelp/ v15r1/topic/com.ibm.itm.doc_6.2.3fp1/itm623_messages.htm). 2. Look in the portal server or portal client logs for more information concerning the message. The portal client does not respond You can encounter a problem that the Tivoli Enterprise Portal does not respond or stops running. Diagnosing that the portal client does not respond You can diagnose that the Tivoli Enterprise Portal does not respond by verifying that a Tivoli Enterprise Monitoring Server is started or the selected workspace is returning data. About this task To diagnose that the Tivoli Enterprise Portal does not respond, perform the following steps: Procedure Preliminary diagnostics 1. Verify that the monitoring server is started. 18 IBM Tivoli Monitoring: Troubleshooting Guide
-
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
-
250
-
251
-
252
-
253
-
254
-
255
-
256
-
257
-
258
-
259
-
260
-
261
-
262
-
263
-
264
-
265
-
266
-
267
-
268
-
269
-
270
-
271
-
272
-
273
-
274
-
275
-
276
-
277
-
278
-
279
-
280
-
281
-
282
-
283
-
284
-
285
-
286
-
287
-
288
-
289
-
290
-
291
-
292
-
293
-
294
-
295
-
296
-
297
-
298
-
299
-
300
-
301
-
302
-
303
-
304
-
305
-
306
-
307
-
308
-
309
-
310
![]() |
![]() |
![](/manual_guide/products/ibm-e027sllh-troubleshooting-guide-7c8d102/36.png)