LSF V10.0.9 install issue (Windows)

Sort:
You are not authorized to post a reply.
Author
Messages
Roger French
Veteran Member
Posts: 545
Veteran Member

    New LSF V10.0.9 environment, windows 2012R2, SQL 2014, on a server where the same exact environment version was previously installed on. But with SQL 2012.

    All prerequisites were installed (java 1.7, COBOL, perl, etc.). Rights, permissions, OK. Using domain lawson account for installation. New SQL GEN and LOGAN created OK, with user/login perms. Environment variable set OK, reviewed, etc. New LDAP created.

    Installation fails because it can't create GEN using dbcreate. Here's a part of the log: I've installed many environments but have never seen this type of error before.during initial installation. Have not seen any valid references on support, and support is currently reviewing it too.

    ....

    ....

    Updating XFERREQ
    run E:\LSF10\gen\bin\dbcreate gen
    ATFMID     not created ** Bad file handle (15) **.
    BCACCPATH  not created ** Bad file handle (15) **.
    BCASSOC    not created ** Bad file handle (15) **.
    BCATTRIB   not created ** Bad file handle (15) **.
    BCDEF      not created ** Bad file handle (15) **.
    BCINTERFAC not created ** Bad file handle (15) **.
    BCMETHOD   not created ** Bad file handle (15) **.
    BTMETH     not created ** Bad file handle (15) **.
    CALENDAR   not created ** Bad file handle (15) **.
    CALYEAR    not created ** Bad file handle (15) **.
    CFKEYNBR   not created ** Bad file handle (15) **.
    CNDFLD     not created ** Bad file handle (15) **.
    CNDFLDELM  not created ** Bad file handle (15) **.
    COBFILE    not created ** Bad file handle (15) **.
    COBFLD     not created ** Bad file handle (15) **.
    COBPATH    not created ** Bad file handle (15) **.
    CRTERRMAP  not created ** Bad file handle (15) **.

    ....

    ....

    Kwane McNeal
    Veteran Member
    Posts: 479
    Veteran Member
      What does ladb.log contain?
      Roger French
      Veteran Member
      Posts: 545
      Veteran Member

        And from the ladb,.log

        ...

        ...

        ladb:  database server 10.0.9.0.1174 2015-12-14 22:00:00 started, pid = 1268.
        Tue Feb 21 12:14:51 2017: ladb (main): database server ready
        Tue Feb 21 12:14:55 2017: [dbcreate] GetDbAuthInfo() Could not get a security context
        Tue Feb 21 12:14:55 2017: [dbcreate] GetDbAuthInfo() Could not get a security context
        Tue Feb 21 12:14:55 2017: [dbcreate] GetDbAuthInfo() Could not get a security context
        Tue Feb 21 12:14:55 2017: [dbcreate] GetDbAuthInfo() Could not get a security context
        Tue Feb 21 12:14:55 2017: [dbcreate] GetDbAuthInfo() Could not get a security context
        Tue Feb 21 12:14:55 2017: [dbcreate] GetDbAuthInfo() Could not get a security context
        Tue Feb 21 12:14:55 2017: [dbcreate] GetDbAuthInfo() Could not get a security context
        Tue Feb 21 12:14:55 2017: [dbcreate] GetDbAuthInfo() Could not get a security context
        Tue Feb 21 12:14:55 2017: [dbcreate] GetDbAuthInfo() Could not get a security context
        Tue Feb 21 12:14:55 2017: [dbcreate] GetDbAuthInfo() Could not get a security context
        Tue Feb 21 12:14:55 2017: [dbcreate] GetDbAuthInfo() Could not get a security context
        Tue Feb 21 12:14:55 2017: [dbcreate] GetDbAuthInfo() Could not get a security context

        ...

        ...


        Kwane McNeal
        Veteran Member
        Posts: 479
        Veteran Member
          You have something wrong with lase, ldap, the license file, or a running/zombie/orphan process
          Roger French
          Veteran Member
          Posts: 545
          Veteran Member

            Issues were resolved and install completed.

            Discovered that the logins/users for the GEN and LOGAN databases had been changed when servers were renamed. Corrected them. (sql lawson account is both the login and user for both GEN and LOGAN. Note though your requirements may be different.)

            Also for LDAP the Schema could not connect to the domain or the Schema Operations Master (using the Change Active Directory Controller... option in ADSI Edit). The app server (virtual) was then unjoined and rejoined back to the domain, the Schema was then properly connected and configured.

            Once I did that I recreated GEN and LOGAN and LDAP (and restarted LDAP), the install went along fine as usual.

             

             

             

            You are not authorized to post a reply.