IBM Systems Director 6.1 becomes unusable with ATKCOR031E An unknown error has occurred

After using IBM Systems Director 6.1 for a month or so, customers seems to always hit a funny error “ATKCOR031E An unknown error has occurred”. This error tear up IBM Systems Director 6.1 unusable. This error seems to come up when discovering many items usually 500 or more, which cause IBM Director to stuck & force you to reboot the machine. After the reboot you start IBM Director web console & get hammered with the error on the web console.

The only work around I have been able to find on the net so far was to do an smreset to IBM Director. The problem with this its a destructive procedure and will get you to lose your configuration & the data in your IBM Director Database. Below is a solution I have came up with that will eliminate the need for SMreset.

As a start this issue has been resolved in IBM Director 6.1.2, though what many other posters has missed even IBMers that you can update IBM Director 6.1 to 6.1.2 even without the IBM Director Web Console being functional using command line & with zero data loss. Below are the step by step procedure.

1- Of course the first step is to take a backup of your current IBM Director 6.1. Hopefully you will note need to use it but its always a good idea. You take a backup of your IBM Director using the following command: smsave

Note: SMSave is usually found in the IBM Director install_root\bin directory

2- Download The IBM Director 6.1.2 Installation & Update CD. The download package name is “SysDir6_1_2_Server_Inst_Upd_Windows_a.zip” & it can be downloaded by visiting:  http://www-03.ibm.com/systems/software/director/downloads/mgmtservers.html

Then hit “Select a platform and download IBM Systems Director Server 6.1.2″, then login with your account, agree to the license agreement then download

(1.45 GB)”

Note: Make sure you download the full installation & update package not just the update package  as the stand alone update package which found at: http://www-933.ibm.com/support/fixcentral/ can’t be applied from the command line.

3- Extract the SysDir6_1_2_Server_Inst_Upd_Windows_a.zip package to a folder on your machine ex:  c:\sysdirupdate

4- Under the directory you extracted the system director 6.1.2 update go to the bin directory and run installds.bat -u  (ex: c:\sysdirupdate\bin\installds.bat -u)

Please note step four can take up to 60 minutes, so be patient & don’t stop it even if it look not doing anything for a while.

After the update is completed, you can enjoy the new stable version of IBM Director 6.1.2 without losing your data. I hope that help & please leave your result & suggestion in the comment area below.

Note: 6.1.2 seems not to resolve the above issue for everyone, as some people have still reported the same problem after the upgrade. As IBM Systems Directory 6.2 has been announced few week backs & seems to resolve the above problem & more stable than previous releases, you shall consider upgrading to IBM Systems Director 6.2.




13 Responses to 'IBM Systems Director 6.1 becomes unusable with ATKCOR031E An unknown error has occurred'

  1. skulker - February 19th, 2010 at 3:04 pm

    I’ve updated Systems Director to 6.1.2.1. I still get this error when I attempt to run System Status and Health=>Monitors=>when clicking on any of the monitors I get the ATKCOR031E unknown error. I’m running on AIX 6.1 on a POWER 5.

  2. admin - March 6th, 2010 at 8:41 am

    Hi Skulker,

    I am sorry, but I have not tried IBM Systems Director 6 on AIX yet.

    I hope some one else can post any feed back on here.

    Regards,
    TSMGuru

  3. Hector E. rios - March 16th, 2010 at 11:01 am

    Hi maybe you know about this, im little bit desesperated, im migrating ibm director 5.20 into 6.1.2. usind the migration tool kit, everything ran smoothly at the export and the import, but at the end the database is not coming up, therefore the director.
    I dont have any errors on that migration, just DB is not working at the end.

  4. admin - March 17th, 2010 at 12:19 pm

    Hi Hector,

    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

  5. Hector E. rios - March 17th, 2010 at 3:17 pm

    Sure i will do, but to be honest i will smreset again everything, and will begin to discover my systems i normally have on the 5.20, and after successfuly discover, i will get away from 5.20

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

  6. Hector Rios - March 25th, 2010 at 1:26 pm

    Hi Guys new issue, finally im doing the things manually (discovery), all my servers i already discovered have Director Agant level 2 5.20, well all of them are discovered fine but with the NO ACCESS on the IBM director 6.12 console.well i right click on them access type valid account and password name on my domain, and it change from No access to OK… but as soon as i left that screen the status comes again as no access… then something is not working fine. have you have any knowledge about this?

    thansk.

  7. admin - March 26th, 2010 at 3:38 am

    Hi Hector,

    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.

  8. Jesse Hu - May 12th, 2010 at 1:32 am

    Hi all, I also encounted into the ATKCOR031E error when using Active Energy Manager 4.2 and Director 6.1. I found the solution on http://www-01.ibm.com/support/docview.wss?uid=nas766b713ecfe7c930086257540006a3c14:

    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.

  9. Tim - June 3rd, 2010 at 7:41 am

    Like Skulker, I have had the same issue. I have installed Systems Director 6.1.2.1 on an IBM x3650 running W2K8 64 bit (external SQL DB). Same type error(s). I then started over with same hardware and installed W2K3 32 bit (internal Apache Derby – default).

    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.

  10. Nicholas - June 4th, 2010 at 8:38 am

    Hi,

    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?

  11. admin - July 6th, 2010 at 11:36 am

    Hi Jesse,

    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

  12. admin - July 6th, 2010 at 11:46 am

    Hi Nicholas,

    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

  13. admin - July 6th, 2010 at 11:51 am

    Hi Tim,

    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


Leave a Reply