Topic
  • 4 replies
  • Latest Post - ‏2010-05-22T17:51:14Z by JGRASETT
SystemAdmin
SystemAdmin
805 Posts

Pinned topic Test Connection fails when installing - Engine error unable to setMaxRetry

‏2009-12-04T17:23:24Z |
I'm trying to install BuildForge on Windows 2003 Server using Install Manager. After filling in the required Database information and clicking on the Test Connection button I get an error
Engine Error::Unable to setMaxRetry
Died at TestDB.pl line 238

I haven't a clue as to what this means or how to correct it.
Any ideas/help would be greatly apprceiated.

Thanks
Updated on 2010-05-22T17:51:14Z at 2010-05-22T17:51:14Z by JGRASETT
  • mralexk
    mralexk
    24 Posts

    Re: Test Connection fails when installing - Engine error unable to setMaxRetry

    ‏2009-12-15T22:11:49Z  
    Which Database; SQL, Oracle, DB2, Other?
  • SystemAdmin
    SystemAdmin
    805 Posts

    Re: Test Connection fails when installing - Engine error unable to setMaxRetry

    ‏2009-12-16T00:38:22Z  
    • mralexk
    • ‏2009-12-15T22:11:49Z
    Which Database; SQL, Oracle, DB2, Other?
    wow...I didn't realize I left that key inforation out. It's DB2 9.5.3
  • sgw
    sgw
    14 Posts

    Re: Test Connection fails when installing - Engine error unable to setMaxRetry

    ‏2009-12-16T15:28:22Z  
    wow...I didn't realize I left that key inforation out. It's DB2 9.5.3
    Should note that DB2 9.5.x is not supported yet in BF.

    -Sean


    ClearQuest : support home » information centers 7.1.0.x | 7.0.1.x | 7.0.0.x » RFE Community : search or submit
  • JGRASETT
    JGRASETT
    6 Posts

    Re: Test Connection fails when installing - Engine error unable to setMaxRetry

    ‏2010-05-22T17:51:14Z  
    • sgw
    • ‏2009-12-16T15:28:22Z
    Should note that DB2 9.5.x is not supported yet in BF.

    -Sean


    ClearQuest : support home » information centers 7.1.0.x | 7.0.1.x | 7.0.0.x » RFE Community : search or submit
    It is supported now, and that error has to do with authorization. Once I granted all to the db2 user for the database specified this error went away.