IBM E027SLL-H Troubleshooting Guide - Page 151

KFWITM217E:Request Error,SQL1_CreateRequest Failed, rc=350

Page 151 highlights

v In the list of policies, right-click Log on locally and select Security. v Click Add. The Select Users or Groups window is displayed. v Select sysadmin from the list of user names. v Click Add. v Click OK. v On the Local Security Policy Setting window, verify that the check box in the Effective Policy Setting column is selected for the sysadmin user. v Click OK to save the new setting and exit. Several enterprise workspaces are returning an error, KFWITM217E:Request Error,SQL1_CreateRequest Failed, rc=350 The following workspaces are Link Targets and should not be navigated to directly: v Deploy Status By Product v Deploy Status By Deploy Group v Installation Logs Attempts to navigate to them directly while in *ADMIN MODE* result in the observed error because required context is not available. Also, when navigating to any workspace that is the target of a link, that target workspace does not appear on the "Workspaces" menu. You cannot paste non-ASCII characters in the Situation editor You can type ASCII or non-ASCII characters in the Situation editor. You can paste ASCII characters in the Situation editor. However, you cannot paste non-ASCII characters in the Situation editor. Situation editor cannot display advanced advice help files In double-byte languages, when the font is set to italic, it cannot display the font in italics format. After acknowledging a situation event and selecting the link for that situation, you might receive a message You hover over a navigator item and then right click -> Quick Ack on any situation event. If you then select the link for the same situation , you might receive an error message. If you then wait without clicking OK, the Tivoli Enterprise Portal client exits. If you encounter this problem, use any recent Sun JRE (1.5.0_14 or above). This problem is limited to IBM's 1.5 java. Note: A Sun bug report bug_id=6578895 which describes the issue was fixed in Sun's 1.5.0_14. Chapter 7. Portal client troubleshooting 133

  • 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

v
In the list of policies, right-click
Log on locally
and select
Security
.
v
Click
Add
. The Select Users or Groups window is displayed.
v
Select sysadmin from the list of user names.
v
Click
Add
.
v
Click
OK
.
v
On the Local Security Policy Setting window, verify that the check box in the
Effective Policy Setting column is selected for the sysadmin user.
v
Click
OK
to save the new setting and exit.
Several enterprise workspaces are returning an error,
KFWITM217E:Request Error,SQL1_CreateRequest Failed, rc=350
The following workspaces are Link Targets and should not be navigated to
directly:
v
Deploy Status By Product
v
Deploy Status By Deploy Group
v
Installation Logs
Attempts to navigate to them directly while in *ADMIN MODE* result in the
observed error because required context is not available. Also, when navigating to
any workspace that is the target of a link, that target workspace does not appear
on the "Workspaces" menu.
You cannot paste non-ASCII characters in the Situation editor
You can typeASCII or non-ASCII characters in the Situation editor. You can paste
ASCII characters in the Situation editor. However, you cannot paste non-ASCII
characters in the Situation editor.
Situation editor cannot display advanced advice help files
In double-byte languages, when the font is set to italic, it cannot display the font in
italics format.
After acknowledging a situation event and selecting the link for that
situation, you might receive a message
You hover over a navigator item and then right click -> Quick Ack on any
situation event. If you then select the link for the same situation , you might
receive an error message. If you then wait without clicking
OK
, the Tivoli
Enterprise Portal client exits.
If you encounter this problem, use any recent Sun JRE (1.5.0_14 or above). This
problem is limited to IBM's 1.5 java.
Note:
A Sun bug report bug_id=6578895 which describes the issue was fixed in
Sun's 1.5.0_14.
Chapter 7. Portal client troubleshooting
133