You will want to start by reviewing the security_provisioning.log(s) in your LAWDIR/system directory.
All transactions completed in ISS related to user maintenance, federation, and synchronization, are logged in the LAWDIR/system/security_provisioning.log(s).
Please note, the log may take a few minutes to complete after the sync completes in the browser. Once the logs have completed, best practice is to copy the log(s) to a new directory so that they are not overwritten while you are researching the sync errors.
Open the most recent provisioning log and go to the bottom of the log. If nothing has been done in ISS since the sync completed you should see a message similar to the one below followed by a list of records that failed:
Thu Apr 26 16:56:01.282 CDT 2018 – default-457261151: Sync Analysis for object type IDENTITY completed with status=true
Thu Apr 26 16:56:01.282 CDT 2018 – default-457261151: Sync Analysis successfully completed for object type IDENTITY
Thu Apr 26 16:58:52.073 CDT 2018 – 1360326122: Sync Execution successfully completed for Task ID[4,963] with failed transactions for Sync Records:
The list of records that failed is limited to one section of the sync. You will see a list of either roles, actors, services, domains, endpoints endpoint groups or identities, depending on which section of the sync had failed records. This is because once the sync completes the analysis or execution of the section with the failed records the sync process will not continue. You must address the failed records to continue the sync.
Alternately you can search the log for the word “completed” to find the most recent section of the sync process that completed. There will be a completed message for each section of the sync.
Examples of completed messages without failed records:
Thu Jan 28 10:50:29.536 GMT-06:00 2021 – default-1845137754 – L(4) : Sync Execution task for [ROLE] with Task ID [1207] started.
Thu Jan 28 10:50:29.536 GMT-06:00 2021 – default-1504145202 – L(4) : Setting progress percentage [-1]
Thu Jan 28 10:50:29.537 GMT-06:00 2021 – default-1504145202 – L(4) : Success updating task [1207]
Thu Jan 28 10:50:29.537 GMT-06:00 2021 – default-1504145202 – L(4) : Starting Sync Execution using pagesize [500] and Nthread [5]
Thu Jan 28 10:50:29.551 GMT-06:00 2021 – default-1504145202 – L(4) : Retrieved 0 ROLE for execution
Thu Jan 28 10:50:29.551 GMT-06:00 2021 – default-1504145202 – L(4) : Sync Execution Successful for ROLE
Thu Jan 28 10:50:29.551 GMT-06:00 2021 – default-1504145202 – L(4) : SyncExecution execution time for [ROLE] took [0] seconds to complete
Thu Jan 28 10:55:33.485 GMT-06:00 2021 – default-863748063 – L(4) : Sync Execution task for [DOMAIN] with Task ID [1219] started.
Thu Jan 28 10:55:33.500 GMT-06:00 2021 – default-1293059945 – L(4) : Setting progress percentage [-1]
Thu Jan 28 10:55:33.500 GMT-06:00 2021 – default-1293059945 – L(4) : Success updating task [1219]
Thu Jan 28 10:55:33.502 GMT-06:00 2021 – default-1293059945 – L(4) : Starting Sync Execution using pagesize [500] and Nthread [5]
Thu Jan 28 10:55:33.506 GMT-06:00 2021 – default-1293059945 – L(4) : Retrieved 0 DOMAIN for execution
Thu Jan 28 10:55:33.506 GMT-06:00 2021 – default-1293059945 – L(4) : Sync Execution Successful for DOMAIN
Thu Jan 28 10:55:33.506 GMT-06:00 2021 – default-1293059945 – L(4) : SyncExecution execution time for [DOMAIN] took [0] seconds to complete
Examples of completed messages with failed records:
Thu Jan 4 07:19:55.755 EST 2018 – default- 2123289590: SyncAnalysis for ACTOR have 2 error records
Thu Jan 4 07:19:55.755 EST 2018 – default- 2123289590: Sync Analysis for object type ACTOR completed with status=true
Thu Jan 4 07:19:55.842 EST 2018 – 2123289590: Sync Analysis completed for object type ACTOR with failed Sync Records:
ACTOR=user1;
ACTOR=user2;
Tue Apr 19 10:18:33.128 CDT 2018 – default-1441714547: SyncAnalysis for ENDPOINT have 7 error records
Tue Apr 19 10:18:33.128 CDT 2018 – default-1441714547: Sync Analysis for object type ENDPOINT completed with status=true
Tue Apr 19 10:18:33.130 CDT 2018 – 1441714547: Sync Analysis completed for object type ENDPOINT with failed Sync Records:
HTTPPORT=82,SSODOMAIN=CSEMSS_EXTERNAL,FQDN=WFHPROD-LSF01.COM,HTTPSPORT=1448;
HTTPPORT=81,SSODOMAIN=CS_INTERNAL,FQDN=WFHPROD-LSF01.COM,HTTPSPORT=443;
HTTPPORT=81,SSODOMAIN=CS_INTERNAL,FQDN=WFHPROD-LM01.COM,HTTPSPORT=1443;
HTTPPORT=85,SSODOMAIN=TC_LDAP_BIN_EXT,FQDN=WFHPROD-LSF01.COM,HTTPSPORT=1447;
HTTPPORT=85,SSODOMAIN=TC_LDAP_BIN_EXT,FQDN=WFHPROD-LM01.COM,HTTPSPORT=1447;
HTTPPORT=9080,SSODOMAIN=CS_INTERNAL,FQDN=WFHPROD-MSCM01.COM,HTTPSPORT=8443;
HTTPPORT=21442,SSODOMAIN=CS_INTERNAL,FQDN=WFHPROD-IES01.COM,HTTPSPORT=9443;
Tue Apr 3 10:51:21.774 EDT 2018 – default-471380075: SyncAnalysis for IDENTITY have 4 error records
Tue Apr 3 10:51:21.774 EDT 2018 – default-471380075: Sync Analysis for object type IDENTITY completed with status=true
Tue Apr 3 10:51:21.774 EDT 2018 – 471380075: Sync Analysis completed for object type IDENTITY with failed Sync Records:
IDENTITY=USER:DOMAIN\user1,SERVICE=SSOP,ID=user1;
IDENTITY=USER:DOMAIN\user2,SERVICE=SSOP,ID=user2;
IDENTITY=USER:user1@domain.com,SERVICE=THICKCLIENTLDAPLS,ID=user1;
IDENTITY=USER:user2@domain.com,SERVICE=THICKCLIENTLDAPLS,ID=user2;
To find the exceptions for the failed records you will need to search within the log(s) each failed record. For each failed record you will search for the value from the list without the semicolon at the end of the line:
For failed record ACTOR=user1; you will would search for “ACTOR=user1”
For failed record HTTPPORT=82,SSODOMAIN=CSEMSS_EXTERNAL,FQDN=WFHPROD-LSF01.COM,HTTPSPORT=1448; you would search for “HTTPPORT=82,SSODOMAIN=CSEMSS_EXTERNAL,FQDN=WFHPROD-LSF01.COM,HTTPSPORT=1448”
For failed record IDENTITY=USER:DOMAIN\user1,SERVICE=SSOP,ID=user1; you would search for “IDENTITY=USER:DOMAIN\user1,SERVICE=SSOP,ID=user1”
Weekly Patch Notification: July 8, 2023
Articles, Frontpage Article, PatchesISS: How to review logs after running an Infor Security Services (ISS) sync
Articles, Frontpage Article, NewsYou will want to start by reviewing the security_provisioning.log(s) in your LAWDIR/system directory.
All transactions completed in ISS related to user maintenance, federation, and synchronization, are logged in the LAWDIR/system/security_provisioning.log(s).
Please note, the log may take a few minutes to complete after the sync completes in the browser. Once the logs have completed, best practice is to copy the log(s) to a new directory so that they are not overwritten while you are researching the sync errors.
Open the most recent provisioning log and go to the bottom of the log. If nothing has been done in ISS since the sync completed you should see a message similar to the one below followed by a list of records that failed:
Thu Apr 26 16:56:01.282 CDT 2018 – default-457261151: Sync Analysis for object type IDENTITY completed with status=true
Thu Apr 26 16:56:01.282 CDT 2018 – default-457261151: Sync Analysis successfully completed for object type IDENTITY
Thu Apr 26 16:58:52.073 CDT 2018 – 1360326122: Sync Execution successfully completed for Task ID[4,963] with failed transactions for Sync Records:
The list of records that failed is limited to one section of the sync. You will see a list of either roles, actors, services, domains, endpoints endpoint groups or identities, depending on which section of the sync had failed records. This is because once the sync completes the analysis or execution of the section with the failed records the sync process will not continue. You must address the failed records to continue the sync.
Alternately you can search the log for the word “completed” to find the most recent section of the sync process that completed. There will be a completed message for each section of the sync.
Examples of completed messages without failed records:
Thu Jan 28 10:50:29.536 GMT-06:00 2021 – default-1845137754 – L(4) : Sync Execution task for [ROLE] with Task ID [1207] started.
Thu Jan 28 10:50:29.536 GMT-06:00 2021 – default-1504145202 – L(4) : Setting progress percentage [-1]
Thu Jan 28 10:50:29.537 GMT-06:00 2021 – default-1504145202 – L(4) : Success updating task [1207]
Thu Jan 28 10:50:29.537 GMT-06:00 2021 – default-1504145202 – L(4) : Starting Sync Execution using pagesize [500] and Nthread [5]
Thu Jan 28 10:50:29.551 GMT-06:00 2021 – default-1504145202 – L(4) : Retrieved 0 ROLE for execution
Thu Jan 28 10:50:29.551 GMT-06:00 2021 – default-1504145202 – L(4) : Sync Execution Successful for ROLE
Thu Jan 28 10:50:29.551 GMT-06:00 2021 – default-1504145202 – L(4) : SyncExecution execution time for [ROLE] took [0] seconds to complete
Thu Jan 28 10:55:33.485 GMT-06:00 2021 – default-863748063 – L(4) : Sync Execution task for [DOMAIN] with Task ID [1219] started.
Thu Jan 28 10:55:33.500 GMT-06:00 2021 – default-1293059945 – L(4) : Setting progress percentage [-1]
Thu Jan 28 10:55:33.500 GMT-06:00 2021 – default-1293059945 – L(4) : Success updating task [1219]
Thu Jan 28 10:55:33.502 GMT-06:00 2021 – default-1293059945 – L(4) : Starting Sync Execution using pagesize [500] and Nthread [5]
Thu Jan 28 10:55:33.506 GMT-06:00 2021 – default-1293059945 – L(4) : Retrieved 0 DOMAIN for execution
Thu Jan 28 10:55:33.506 GMT-06:00 2021 – default-1293059945 – L(4) : Sync Execution Successful for DOMAIN
Thu Jan 28 10:55:33.506 GMT-06:00 2021 – default-1293059945 – L(4) : SyncExecution execution time for [DOMAIN] took [0] seconds to complete
Examples of completed messages with failed records:
Thu Jan 4 07:19:55.755 EST 2018 – default- 2123289590: SyncAnalysis for ACTOR have 2 error records
Thu Jan 4 07:19:55.755 EST 2018 – default- 2123289590: Sync Analysis for object type ACTOR completed with status=true
Thu Jan 4 07:19:55.842 EST 2018 – 2123289590: Sync Analysis completed for object type ACTOR with failed Sync Records:
ACTOR=user1;
ACTOR=user2;
Tue Apr 19 10:18:33.128 CDT 2018 – default-1441714547: SyncAnalysis for ENDPOINT have 7 error records
Tue Apr 19 10:18:33.128 CDT 2018 – default-1441714547: Sync Analysis for object type ENDPOINT completed with status=true
Tue Apr 19 10:18:33.130 CDT 2018 – 1441714547: Sync Analysis completed for object type ENDPOINT with failed Sync Records:
HTTPPORT=82,SSODOMAIN=CSEMSS_EXTERNAL,FQDN=WFHPROD-LSF01.COM,HTTPSPORT=1448;
HTTPPORT=81,SSODOMAIN=CS_INTERNAL,FQDN=WFHPROD-LSF01.COM,HTTPSPORT=443;
HTTPPORT=81,SSODOMAIN=CS_INTERNAL,FQDN=WFHPROD-LM01.COM,HTTPSPORT=1443;
HTTPPORT=85,SSODOMAIN=TC_LDAP_BIN_EXT,FQDN=WFHPROD-LSF01.COM,HTTPSPORT=1447;
HTTPPORT=85,SSODOMAIN=TC_LDAP_BIN_EXT,FQDN=WFHPROD-LM01.COM,HTTPSPORT=1447;
HTTPPORT=9080,SSODOMAIN=CS_INTERNAL,FQDN=WFHPROD-MSCM01.COM,HTTPSPORT=8443;
HTTPPORT=21442,SSODOMAIN=CS_INTERNAL,FQDN=WFHPROD-IES01.COM,HTTPSPORT=9443;
Tue Apr 3 10:51:21.774 EDT 2018 – default-471380075: SyncAnalysis for IDENTITY have 4 error records
Tue Apr 3 10:51:21.774 EDT 2018 – default-471380075: Sync Analysis for object type IDENTITY completed with status=true
Tue Apr 3 10:51:21.774 EDT 2018 – 471380075: Sync Analysis completed for object type IDENTITY with failed Sync Records:
IDENTITY=USER:DOMAIN\user1,SERVICE=SSOP,ID=user1;
IDENTITY=USER:DOMAIN\user2,SERVICE=SSOP,ID=user2;
IDENTITY=USER:user1@domain.com,SERVICE=THICKCLIENTLDAPLS,ID=user1;
IDENTITY=USER:user2@domain.com,SERVICE=THICKCLIENTLDAPLS,ID=user2;
To find the exceptions for the failed records you will need to search within the log(s) each failed record. For each failed record you will search for the value from the list without the semicolon at the end of the line:
For failed record ACTOR=user1; you will would search for “ACTOR=user1”
For failed record HTTPPORT=82,SSODOMAIN=CSEMSS_EXTERNAL,FQDN=WFHPROD-LSF01.COM,HTTPSPORT=1448; you would search for “HTTPPORT=82,SSODOMAIN=CSEMSS_EXTERNAL,FQDN=WFHPROD-LSF01.COM,HTTPSPORT=1448”
For failed record IDENTITY=USER:DOMAIN\user1,SERVICE=SSOP,ID=user1; you would search for “IDENTITY=USER:DOMAIN\user1,SERVICE=SSOP,ID=user1”
The Future of Retail: Top 6 Retail Technology Trends for 2023
NewsEven before the start of the pandemic, the retail space has been integrating some technological tools here and there. Since then, we’ve seen this new normal of tech-infused shopping experiences. With the hottest technology trends being integrated in almost every industry, what will the future of retail look like? Rajendra Roul, Content Promotion Specialist at G2, along with retail experts around the globe, share 6 retail technology trends for 2023 and beyond
For Full Article, Click Here
XM ER Not Showing – Expense Report
Articles, Frontpage Article, NewsRecently a user submitted an error that could be useful for anyone else who encounters it.
Problem
The user is reporting they are not seeing Expense Reports in Lawson XM. They are receiving emails.
Solution
While this could be an alerting problem, we have a quick fix for user error.
The user needs to log into Mingle. Once logged in and in XM, simply click on the filter option at the top right of the screen. Here, you must make sure you clear your filters as shown below:
Log back in and you should not have the missing error again.
Delta Plus Modernizes its Information System with Infor
NewsInfor recently announced that Delta Plus, a manufacturer and distributor of a complete range of personal protective equipment (PPE) , has chosen Infor CloudSuite enterprise resource planning (ERP) solution to optimize its management processes. Additionally, Delta Plus will also deploy the following Infor products: Infor Factory TrackTM warehouse mobility functions, Infor CPQ configure price quote tool, and Infor IDM optical recognition software dedicated to the dematerialization of supplier invoices. These Infor-based tools will provide the group with a modern, more scalable and interoperable IS, all secured in a high availability cloud environment hosted at AWS (Amazon Web Services). Per the press release, the choice of Infor’s ERP solution was made following the decisive commitment of Delta Plus’s CIO, who supported Infor’s Value Engineering approach and involved the group’s general management, as well as all stakeholders in the project. Further, the project is scheduled to start this summer. An initial 1,000 users will benefit from Infor’s new solutions, mainly in the functional areas of sales, inventory and supply chain management, financial and analytical management, and budget consolidation. This number is expected to grow as the group deploys and acquires new solutions on a regular basis.
For Full Article, Click Here
Mute Selects Infor to Transform its Technology and Strengthen Overseas Expansion
NewsIn recent news Mute, a leading manufacturer of acoustic solutions for office spaces, has chosen Infor M3 CloudSuite™ ERP (enterprise resource planning) system to support the intensive development of the company, including its international expansion. Per the press release, eighty users in Mute will gain access to the Infor OS cloud platform and the Infor Birst data analytics system. The solutions will be delivered in a multi-tenant cloud powered by Amazon Web Services (AWS). Infor Poland partner iPCC will be responsible for the implementation. Mute employees will also gain access to Infor Birst, a cloud-native business intelligence (BI) and analytics platform. This platform allows personalization of reports and sharing data across the organization as well as information analysis supported by artificial intelligence and complete insight into business processes. The implementation started in April and is expected to be live in January 2024.
For Full Article, Click Here
Weekly Patch Notification: July 1, 2023
Articles, Frontpage Article, PatchesMigrating Lawson On-Premise to Infor Cloudsuite
Articles, Frontpage Article, NewsAs businesses grow and technology advances, it’s not uncommon for companies to outgrow their current enterprise resource planning (ERP) software. In some cases, this may mean moving from an on-premise solution, such as Lawson, to a cloud-based platform like Infor Cloudsuite. If you’re considering making the switch, here are some steps to keep in mind.
In conclusion, moving from Lawson on-premise to Infor Cloudsuite can be a complex process, but by following these steps and working closely with your IT team and vendor, you can ensure a successful transition. By choosing a cloud-based ERP solution like Infor Cloudsuite, you can benefit from improved functionality, scalability, and cost-effectiveness, supporting your organization’s growth and success in the years to come.
E&A Scheer Selects Infor to Optimize Processes
NewsE&A Scheer recently had a successful go-live of the Infor CloudSuite Food & Beverage solution. The rum company will use the solution to optimize internal processes. The future-proof solution offers the Dutch rum company improvements for distribution and recipe management in combination with greater insight into the supply chain. Per the press release, E&A Scheer was looking for a partner with standardized cloud solutions for sector-specific challenges. After a thorough evaluation, Infor was selected because of its extensive food & beverage functionalities, such as planning & scheduling, recipe management and inventory management. In addition, the cloud expertise and team composition from Infor played an important role in the decision.
For Full Article, Click Here
10 Small Business Tech Trends Defining 2023
NewsEvery day more and more technology is introduced or revamped, continuously shaping the way we run our businesses. Small businesses especially see the competitive edge when using digital tools such as customer relationship management (CRM) software, unique marking platforms, and integrated accounting and financial programs. Sales expert David Appel shares an article on BuiltIn.com of the latest small business tech trends that can help small businesses stay ahead of their competition.
Technology is important for all businesses big and small to stay competitive. Future-proofing a small business, Appel notes, starts with looking at your existing processes and the potential benefits of these technologies, as well as making sure your tech stack is compatible with them so you can easily integrate them in the future
For Full Article, Click Here