Prev
Next
Forums S3 Systems Administration

userenv.exe smoke test fails

Sort:
You are not authorized to post a reply.
Author
Messages
wildT
Basic Member
Posts: 5
Basic Member
5/26/2010 8:03 PM
    I'm getting this error when running the smoke test for userenv.exe on a new install of 9.0.0.5: You should verify that the ladb process is running.

    The ladb process is running but this message is logged in LADB.log when attempting the smoke test: tsConnectInit (0) Unable to attach the ladb shared memory segment


    ios.log is logging these messages:
    Unable to retrieve SSO Identity. service: logan_EMPLOYEE attribute: EMPLOYEE user: lawson.
    Unable to retrieve SSO Identity. service: logan_EMPLOYEE attribute: COMPANY user: lawson.
    Unable to retrieve SSO Identity. service: logan_CUSTOMER attribute: CUSTOMER user: lawson.
    Unable to retrieve SSO Identity. service: logan_CUSTOMER attribute: CUST_GROUP user: lawson.
    Unable to retrieve SSO Identity. service: logan_VENDOR attribute: VENDOR user: lawson.
    Unable to retrieve SSO Identity. service: logan_VENDOR attribute: VENDOR_GROUP user: lawson.
    Unable to retrieve SSO Identity. service: logan_REQUESTER attribute: REQUESTER user: lawson.

    I also get "Operation timed out" for LAUA

    Does anyone have any idea what I need to do to fix this? I searched the lawson KB and haven't had any luck. Thanks



    John Henley
    Senior Member
    Posts: 3348
    Senior Member
    5/26/2010 9:01 PM
      It sounds like websphere con fig issue, i.e. Env vars. Or bouncy castle isn't working. Did you run the regression tests?=
      Thanks for using the LawsonGuru.com forums!
      John
      wildT
      Basic Member
      Posts: 5
      Basic Member
      5/26/2010 9:45 PM
        The regression tests worked. I've looked through the websphere configuration and I found that I missed the os400.file.create.auth and os400.dir.create.auth under custom properties. It still fails after adding those entries and restarting the app server
        MattD
        Veteran Member
        Posts: 94
        Veteran Member
        5/27/2010 12:21 PM
          Is it possible your user has a default product line of LOGAN? Is your employee service named LOGAN_EMPLOYEE? Have you checked security to make sure the lawson user is setup correctly? If it is using that user to run the test that could be causing the issue.
          You are not authorized to post a reply.