During a recent IFS install we encountered an install failure and the error message/return code was blank. The setup_log.log file said “Error: IFS -DoInstall failed with a return code of”. We noticed that the setup_log.log claimed that it had created the new database successfully, but the database was not there. After much troubleshooting, we finally realized that we needed some inbound/outbound firewall rules for our IFS database instance. The interesting thing is that the install wizard made it past the database connection screen, but once we added those firewall rules, we were good to go.
You may run into this error at some point in GL40.1:
Fortunately, there’s an easy fix to this. First login to Lawson portal and search GLMONITOR:
In GLMONITOR, type “GL190” and select Inquire. If you get results and notice the run time, the process is in fact still running and causing the issue with GL40:
Go to job scheduler by opening LID and typing in jobschd >> F7 + A to select all users >> Then W to go to waiting screen.
Look for any GL190 jobs running and verify the User Name is the same one in GLMONITOR when inquiring on GL190 program. Check the error and if its safe to recover, recover it and let the job complete.
Go back to GLMonitor and inquire on GL190 to verify the job is no longer running:
Go to GL40.1 and release your Journal Entries. This should solve the error. Good luck!
Database errors and security breaches have increased significantly in recent years. With data migration, vulnerability to error and hacking is a great risk. “We have seen a large number of breaches and failures due to human error,” says Robert Reeves, Co-founder and CTO of Datical. Often times, humans underestimate and rely too much on “technology” to believe there will be room for error, but you can still make mistakes. Reeves emphasizes the need to automate security and system standards to eliminate (or significantly decrease) human error. Below are five recommendations on how to ensure that new technologies and systems are properly automated and secured:
- Mandate corporate security standards are applied to any new technology before deployment.
- Secure C-level and board support for universal application of security standards
- Automate security process whenever possible
- Continuously improve security as threats change
- Link IT security management with the organization’s overall risk management assessments
By automating security with technology, we can significantly lower the potential risk for human error.
Opening the log reveals a java.lang.StackOverflowError:
This error was fixed by going to (C:\IPDesigner\ADTALEMPRD\workspace\.metadata\.plugins\org.eclipse.ui.workbench)
And removing workbench.xml. We opted to rename it to workbench_old.xml and when we restarted IPDesigner, it generated a new workbench.xml and started working correctly.
When updating a WebSphere fix pack, the following error can be seen from the IBM Installation Manager.
The update in this example is from WebSphere 22.214.171.124 to Fix Pack 10 – 126.96.36.199.
Looking at the error details shows that a dll file was unable to be deleted –
D:\IBM\WebSphere\AppServer\bin\WASServiceMsg.dll. This file can be locked by the Cell Manager when the server is started.
To resolve the issue, stop the WebSphere service in Computer Management and set it to manual start (not to start automatically).
Then find the file that was locked (WASServiceMsg.dll) and rename it to something like WASServiceMsg8550orig.dll.
Permissions may need to be added to the IBM directory to ensure Full Control is Allowed for your user id. Then restart the server and run the IBM Installation Manager again to apply the update.
Afterwards, you can see an updated version of the dll is available along with the original file that was renamed.
Be sure to change the service back to start automatically after the update is complete.