Login
Register
Search
Home
Forums
Jobs
LawsonGuru
LawsonGuru Letter
LawsonGuru Blog
Worthwhile Reading
Infor Lawson News Feed
Store
Store FAQs
About
Forums
Infor / Lawson Platforms
S3 Systems Administration
Problem with Failover / Cluster mgmt
Home
Forums
Jobs
LawsonGuru
LawsonGuru Letter
LawsonGuru Blog
Worthwhile Reading
Infor Lawson News Feed
Store
Store FAQs
About
Who's On?
Membership:
Latest:
Jessica
Past 24 Hours:
2
Prev. 24 Hours:
0
Overall:
5164
People Online:
Visitors:
244
Members:
0
Total:
244
Online Now:
New Topics
Top Forum Posters
Name
Points
Greg Moeller
4184
David Williams
3349
JonA
3288
Kat V
2984
Woozy
1973
Jimmy Chiu
1883
Kwane McNeal
1437
Ragu Raghavan
1348
Roger French
1311
mark.cook
1244
Forums
Unanswered
Active Topics
Most Liked
Most Replies
Search Forums
Search
Advanced Search
Topics
Posts
Prev
Next
Forums
S3 Systems Administration
Problem with Failover / Cluster mgmt
Sort:
Oldest First
Most Recent First
You are not authorized to post a reply.
Author
Messages
This_Guy
Veteran Member
Posts: 93
1/11/2013 8:47 PM
LSF 9019 / Apps 9015
Windows OS
SQL 2008 DB
We have our Lawson installed on Windows 64bit 2008 OS. We are clustered with all Lawson services: Dmgr, NodeAgent, Server1, LAENV, LDAP. The problem we cannot seem to figure out - everytime I fialover to the inactive node, all services startup EXCEPT the environment. I do notice that WAS comes up pretty quickly, and then the laenv fails to start. I try to manually start this with no luck. The only way I can seem to get the environment to start backup is to leave the inactive node offline, reboot the active node (where services are listed with laenv down) and when it comes online all of Lawson starts fine.
Has anyone seen this? Know of anything I can look at? I've ck'd server logs, event viewer, lawson logs, IBM logs and nothing is telling me why this failover does not work.
Roger French
Veteran Member
Posts: 545
1/12/2013 4:11 AM
I'll start simply:
what does ladb.log show?
what does lase.log show?
Is your ad lds service starting OK?
Do you have any dependencies on your services?
This_Guy
Veteran Member
Posts: 93
1/14/2013 4:18 PM
Hi Robert - logs dont tell me anything. I've scanned thru them pretty closely... coming up with nothing useful. ADLDS starts up fine. The dependencies are set for boot up order: LAENV > WAS Dmgr > NodeAgent > WAS Server1
Its just odd. I dont get it...
This_Guy
Veteran Member
Posts: 93
1/14/2013 4:19 PM
I am seeing this in the Event Viewer for the server that Lawson wont start on
Log Name: Application
Source: LAWSON
ROD (LAWSON INSIGHT Environment)
Date: 1/14/2013 9:01:56 AM
Event ID: 32783
Task Category: (9)
Level: Error
Keywords: Classic
User: N/A
Computer: SHLAWPRD201.phhservices.org
Description:
The description for Event ID 32783 from source LAWSON
ROD (LAWSON INSIGHT Environment) cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.
If the event originated on another computer, the display information had to be saved with the event.
The following information was included with the event:
laserv.c
1499
UNKNOWN
laserv.exe
Lawson Service (lase) unable to start
the message resource is present but the message is not found in the string/message table
Event Xml:
ROD (LAWSON INSIGHT Environment)" />
32783
2
9
0x80000000000000
86639
Application
SHLAWPRD201.phhservices.org
laserv.c
1499
UNKNOWN
laserv.exe
Lawson Service (lase) unable to start
You are not authorized to post a reply.