| Author |
Messages |
|
SuperUser
 
Posts:26
 |
| 07/23/2003 5:21 PM |
|
When attempting to access Workload functions via a Windows Terminal Server Client, the following error message is displayed:
Facility #287, Severity Level 'FATAL', Message #801, cannot open the data (followed by current date/time stamp)
The Admin account that installed the Unicenter software IS ABLE to execute all workload functions properly but all other users get this message. Any help appreciated...
|
|
|
|
SuperUser
Posts:26
|
| 07/24/2003 1:45 PM |
|
I think I found the root cause...
Win 2000 Service Pack 4 had been applied to this server. I have uninstalled Service pack 4 and users are now able to access workload functions.
So it appears that Service Pack 4 changed security / access settings that have prevented users from accessing these functions. Be very careful apply this service pack to your clients or Unicenter servers. |
|
|
|
SuperUser
Posts:26
|
| 08/26/2003 8:39 AM |
|
W2k SP4 introduces two new security policies:
Impersonate a client after authentication and Create global objects.
To solve the problem, add the terminal client user to the "Create global objects" policy:
1. Click Start, point to Programs, point to Administrative Tools, and then click Local Security Policy.
2. Expand Local Policies, and then click User Rights Assignment.
3. In the right pane, double-click Create global objects.
4. In the Local Security Policy Setting dialog box, click Add.
5. In the Select Users or Group dialog box, click the user account that you want to add, click Add, and then click OK.
This should solve Workload Security issues on Win2000 SP4. |
|
|
|
SuperUser
Posts:26
|
| 10/24/2003 10:22 AM |
|
If workload fails to start after a "unicycle all" on a solaris server and a "unistart sche" gives the following error:
# unistart sche
One or more workload processes terminated abnormally.
Please enter the following at the command line:
ipcrm -M 0xca7
Once the above commands have been executed, please re-issue 'unistart sche'
Running the command yields the following:
# ipcrm -M 0xca7
ipcrm: shmkey(0xca7): not found
usage: ipcrm [-q msqid -m shmid -s semid -Q msgkey -M shmkey -S semkey] ...
To resolve this issue do the following:
Shutdown all Unicenter Processes:
unishutdown all
Then list all running CA Processes:
ps -ef | grep $CAIGLBL0000
Kill any processes that show up.
kill -9 (pid)
then issue the following IPCS command:
ipcs -a |grep ca
The list should show any processes that have used shared memory started by users assigned to CA. If you have a typical load of Unicenter installed you may find users such as CADB and CA7MNGR. The display should look something like this:
m 4937 0 --rw-rw-rw- ca7mngr sys ca7mngr sys 0 516 26794 26794 11:56:25 11:56:25 11:56:25
m 4938 0 --rw-rw-rw- ca7mngr sys ca7mngr sys 0 575 26794 26794 11:56:25 11:56:25 11:56:25
m 4939 0 --rw-rw-rw- ca7mngr sys ca7mngr sys 0 571 26794 26794 11:56:25 11:56:25 11:56:25
m 4940 0 --rw-rw-rw- ca7mngr sys ca7mngr sys 0 517 26794 26794 11:56:25 11:56:25 11:56:25
m 4941 0 --rw-rw-rw- ca7mngr sys ca7mngr sys 0 567 26794 26794 11:56:25 11:56:25 11:56:25
These must now be removed by issuing another IPC command:
ipcrm [-q msqid -m shmid -s semid -Q msgkey -M shmkey -S semkey]
You should refer to the display you received to determine exactly how to format the command.
m 4937 0 --rw-rw-rw- ca7mngr sys ca7mngr sys 0 516 26794 26794 11:56:25 11:56:25 11:56:25
The first entry (the m) is the type and first parameter to use and the pid (4937) is the second parameter. so the command should look like:
ipcrm -m 4937
You will need to run this command for each listed pid from your "ipcs -a |grep ca" command. |
|
|
|
|