ERROR: { SQL6031N Error in the db2nodes.cfg file at line number "1". Reason code "10" }

I have created an MSI Package for the DB2 8.2 version.

But while launching the app. config assistant link the above error appears.

Can any one advise what is the issue here & the solution to resolve???

In db2nodes.cfg file, the machine name of the packaging machine has been captured.

 

Does any script is needed for capturing the package with the user machine name???

0 Comments   [ + ] Show Comments

Comments

Please log in to comment

Answers

1

Just install this package on your packaging machine where you have captured this setup and try to lauch the shortcut, if the application is working fine without any error in packaging build whereas the same package is not working on your client build then there might be some machine specific entries are captured in you msi.

Also cross check once whether you have installed the necessary pre-requisites before capturing this application on packaging machine.. Also ensure that the same pre-req is installed on your client build before installing this package..

 

 

 

Answered 06/15/2012 by: jagadeish
Red Belt

  • Hi Jagad,
    Thanks for the info..
    Ya.. The package is fine in Packaging Machine. Machine specific entries has been captured... Pre-Requiste is also installed...

    Still getting that prob..
  • Ok. Please use ProcessMon at the time of launching shortcut.. Try to figure out the problem using FileMon and RegMon (Both are available in ProcessMon)

    http://technet.microsoft.com/en-us/sysinternals/bb896645.aspx
Please log in to comment
1

Sounds like you'll need to write a CA to replace/re-write the line in the cfg file using the [ComputerName] property that is available in the MSI

Just make sure you schedule it somewhere after InstallFiles in deferred context, so the cfg file is in place (if you place it using the Files table... you could of course also generate it completely from scratch in the CA)

Answered 06/11/2012 by: pjgeutjens
Red Belt

  • Ya.. That is gud idea.. But checked the same in End User Machine by changing {computer name} manually.. But still is poses error...
Please log in to comment
0

 

I have tried a different solution:

Testing is still in progress.. :-P

Placing the executable files & all supporting files  in users pc and running an silent installation command using a response file created while installing -> which may avoid that error..

 

Answered 06/16/2012 by: silvang87
White Belt

Please log in to comment
Answer this question or Comment on this question for clarity