Who's On?

	Membership:
	Latest: cat andrews
	Past 24 Hours: 0
	Prev. 24 Hours: 0
	Overall: 5215

	People Online:
	Visitors: 0
	Members: 0
	Total: 0

Name	Points
Greg Moeller	4184
David Williams	3349
Kat V	2984
Woozy	1973
Jimmy Chiu	1883
Kwane McNeal	1437
Ragu Raghavan	1377
Roger French	1315
mark.cook	1244
Chesca	1042

userenv.exe smoke test fails

3 Replies

0 Subscribed to this topic

28 Subscribed to this forum

Sort:

Author

Messages

wildT

Basic Member

Posts: 5

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

Posts: 3364

New Poster

Engaged Reader

Avid Reader

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?=

wildT

Basic Member

Posts: 5

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

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.