Sorry for being late, but I was out for a while. Though I am back now. I hope your IBM System Director 6.2 fixed the problem.

Share back with us your experience. Though 6.1.2 has done the trick for me, though I hope 6.2 will even be more stable.

Come on guys at the development team of IBM Director. You have done a great job at the features level, though IBM Director still need a bit more tuning to match the stability expected from IBM Products. Though all I can say it was a great product revamp for now :). Haha, yeah I know we have to be a bit more patient for now as its free product.

Enjoy,
Eiad

I am sorry for the late reply, but man why does your lwi have 25GB!!!. What kind of database are you using?

I don’t see why your database has gone that big if its located in the lwi folder, although normally databases are not located in the lwi folder. the lwi folder usually include many binaries & temp files if I am not mistaken.

Enjoy,
Eiad

I really appreciate your contribution & hope it help other readers.

People like you who share their experiences are the one who help build the community & make it more interesting.

Again thanks for sharing,
Eiad

Thanks for the great article. I am trying to do the upgrade, but do not have enought disk space free. There is about 25gb of data being used in \program files\IBM\Director\lwi folder. I take this is the database; is there a way of compacting it?

I installed an agent on one system. I attempted to create a monitor view to check the existence of a directory/file. This kills the system. I have to delete the monitor view and reboot to get past error.

Systems Director 6.2 has been released and I am downloading it as I am typing. I will again attempt a complete install starting with the OS.

Step 1: Identify if the GroupRead role assignment is lost:

o Run CLI command: smcli lsuser -l
o Look for “AssignedRoles:” in the output
o It should have: “AssignedRoles: {’GroupRead’ applied to }”

Step 2:

o Run the CLI command: smcli chuser -e GroupRead
Where is the Director user ID used to log into the Director console
o To verify that this worked, run the CLI command: smcli lsuser –l
o Verify GroupRead is one of the assigned roles

Hope this is helpful.

I am not sure about your particular situation, but are you using Active Directory to authenticate? If so, make sure your IBM Director is pointing out to the right Domain Controller (preferably the one holding the role masters). Another thing to check is the validity of the user account you are using as well connectivity to your domain controller if you are using AD to authenticate.

I hope this help & good luck resolving your issue,
TSMGURU.

thansk.

I have done a lot of things, but after “normal” and “clean” migration, it simple doesnt start the lwi… therefore director could not work.

I am sorry, I really have not passed with that problem. Most of my upgrades from 5.20 was to 6.1, which was a disaster on their own. Then only had to upgrade them in the past few months again to 6.1.2.

If you find a resolution for this issue, please post it back in here for other people to benefit of it.

Thanks,
TSMGuru