Login
Register
Search
Home
Forums
Jobs
LawsonGuru
LawsonGuru Letter
LawsonGuru Blog
Worthwhile Reading
Infor Lawson News Feed
Store
Store FAQs
About
Forums
Supply Chain Management
Lawson S3 Supply Chain
MSCM install - sync errors
Home
Forums
Jobs
LawsonGuru
LawsonGuru Letter
LawsonGuru Blog
Worthwhile Reading
Infor Lawson News Feed
Store
Store FAQs
About
Who's On?
Membership:
Latest:
sakkatan
Past 24 Hours:
1
Prev. 24 Hours:
0
Overall:
5216
People Online:
Visitors:
35
Members:
0
Total:
35
Online Now:
New Topics
Lawson Add-Ins for Microsoft Office
Deleting an Orphan Time Record with MS Add-ins
12/13/2025 7:26 PM
I have discovered an Orphan Time Record when dumpi
Lawson S3 HR/Payroll/Benefits
Secure 2.0
12/8/2025 9:06 PM
Has anyone using S3 V10 for Benefits been able to
Lawson Add-Ins for Microsoft Office
More.... ic81.2
12/5/2025 10:51 PM
We build our PAR's with MS Addins using IC81 a
Lawson Add-Ins for Microsoft Office
Uploads
11/20/2025 3:32 AM
The Next button has stopped functioning on the upl
S3 Systems Administration
Lawson Security Admin (LSA) - Securing Print Manager to self only
10/24/2025 6:27 PM
Looking for someone who would be willing to share
Lawson Add-Ins for Microsoft Office
Lawson Add-in
9/30/2025 6:51 PM
I am looking for a Lawson Add-ins query to add new
Lawson S3 Procurement
Anyone getting PO 0000 not found for company error in PO23?
9/30/2025 2:45 AM
Anyone getting PO 0000 not found for company error
Lawson Add-Ins for Microsoft Office
PO20 - Cancel PO via Add-in
9/25/2025 8:03 PM
Is it possible to cancel PO's using add-ins? I
S3 Systems Administration
S3 Payroll - PayStubs
9/18/2025 6:58 PM
Looking for a reliable solution to streamline the
S3 Systems Administration
Quick Access report
8/25/2025 7:17 PM
Looking for a good way to see who has access Lawso
Top Forum Posters
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
Forums
Filtered Topics
Unanswered
Unresolved
Announcements
Active Topics
Most Liked
Most Replies
Search Forums
Advanced Search
Prev
Next
Forums
Supply Chain Management
Lawson S3 Supply Chain
MSCM install - sync errors
Please
login
to post a reply.
0 Replies
0
Subscribed to this topic
39 Subscribed to this forum
Sort:
Oldest First
Most Recent First
Author
Messages
Roger French
Veteran Member
Posts: 549
New Poster
Congrats on posting!
12/18/2015 5:51 PM
Anyone get MSCM 10.1.6.0 with a Secured LSF Websphere to actually synchronize OK? I've installed MSCM, but the secured LSF WAS piece is apparently causing an issue in the synchronization, as seen as an error in the mscm_error.log. (Server and cluster names removed below). Have already checked and reviewed mscm.filter.properties
12-18-2015 13:40:52,862] WARN [com.lawson.mscm.platform.adapter.ios.data.DMEManagerIOSImpl] Exception occurred during creation of LSF Client Factory. The configuration for this is the following:
Server Type: WEBSPHERE
Context Factory: com.ibm.websphere.naming.WsnInitialContextFactory
Server Name(s):
,
Server IIOP port(s): 2811,2812
Server Namespace: cell/clusters/
com.lawson.ios.client.LSFClientException: Exception occurred during creation of LSF Client Factory. The configuration for this is the following:
Server Type: WEBSPHERE
Context Factory: com.ibm.websphere.naming.WsnInitialContextFactory
Server Name(s):
,
Server IIOP port(s): 2811,2812
Server Namespace: cell/clusters/
at com.lawson.ios.client.LSFClientFactory.processConstructionFailure(LSFClientFactory.java:246)
at com.lawson.ios.client.LSFClientFactory.getInstance(LSFClientFactory.java:197)
at com.lawson.mscm.platform.utilities.LSFClientFactoryUtilityImpl.initLsfClientFactory(LSFClientFactoryUtilityImpl.java:314)
at com.lawson.mscm.platform.utilities.LSFClientFactoryUtilityImpl.createDataService(LSFClientFactoryUtilityImpl.java:120)
at com.lawson.mscm.platform.adapter.ios.data.DMEManagerIOSImpl.runDme(DMEManagerIOSImpl.java:73)
at com.lawson.mscm.platform.adapter.dme.DMEManagerLHCImpl.executeInboundDME(DMEManagerLHCImpl.java:319)
at com.lawson.mscm.platform.adapter.dme.InboundDeltaProcessSchedulable.runDme(InboundDeltaProcessSchedulable.java:300)
at com.lawson.mscm.platform.adapter.dme.InboundDeltaProcessSchedulable.perform(InboundDeltaProcessSchedulable.java:450)
at com.lawson.mscm.platform.adapter.dme.InboundDeltaProcessSchedulable.perform(InboundDeltaProcessSchedulable.java:318)
at com.lawson.mscm.platform.manager.scheduler.BaseInboundDeltaProcessSchedulable.doSchedulerAction(BaseInboundDeltaProcessSchedulable.java:128)
at com.lawson.mscm.platform.manager.schedulertask.InboundDeltaProcessSchedulableTask.perform(InboundDeltaProcessSchedulableTask.java:109)
at com.lawson.mscm.platform.manager.schedulertask.InboundDeltaProcessSchedulableTask.process(InboundDeltaProcessSchedulableTask.java:90)
at com.ibm.websphere.scheduler.EJSRemoteStatelessInboundDeltaProcessSchedulableTa_e32c9fff.process(Unknown Source)
at com.ibm.websphere.scheduler._TaskHandler_Stub.process(_TaskHandler_Stub.java:269)
at com.ibm.ws.scheduler.tasks.BeanTaskInfoWork.doWork(BeanTaskInfoWork.java:126)
at com.ibm.ws.scheduler.AlarmListener.executeTaskWithNotification(AlarmListener.java:807)
at com.ibm.ws.scheduler.AlarmListener.access$700(AlarmListener.java:124)
at com.ibm.ws.scheduler.AlarmListener$TaskWork.doWork(AlarmListener.java:436)
at com.ibm.ws.scheduler.AlarmListener$TaskWork.run(AlarmListener.java:222)
at com.ibm.ws.asynchbeans.J2EEContext.run(J2EEContext.java:811)
at com.ibm.ws.asynchbeans.ExecutionContextImpl.go(ExecutionContextImpl.java:86)
at com.ibm.ws.scheduler.AlarmListener.fireTask(AlarmListener.java:1416)
at com.ibm.ws.scheduler.AlarmListener.fired(AlarmListener.java:1334)
at com.ibm.ws.asynchbeans.AlarmImpl.callListenerMethod(AlarmImpl.java:427)
at com.ibm.ws.asynchbeans.timer.GenericTimer.run(GenericTimer.java:228)
at com.ibm.ws.asynchbeans.J2EEContext.run(J2EEContext.java:1178)
at com.ibm.ws.asynchbeans.AlarmImpl.runListenerAsCJWork(AlarmImpl.java:249)
at com.ibm.ws.asynchbeans.am._Alarm.fireAlarm(_Alarm.java:340)
at com.ibm.ws.asynchbeans.am._Alarm.run(_Alarm.java:237)
at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1881)
Caused by: com.lawson.ios.client.BadConfigurationException: None of the specified servers are accessible or are responding. Please check the servers and the values on the configuration file or the getInstance call parameters.
I've already reviewed and checked the mscm.ios.properties file several times. Reinstalled MSCM, recycled server, and still error exists. Have a case with support open too.
LSF Webshere is secured, and LSF App servers are clustered. I've added the configuration for one of the lsf app servers in the MSCM Websphere security set up. (I can't add both of them since an error message saying "Certificate already exists in key store. May be under a different alias name." Recycled/rebooted MSCM but still the error message in mscm_server.log exists.
MSCM: Windows
LSF: AIX
Thanks for your help.
Please
login
to post a reply.