FYI for anyone having issues installing the Sage 2024.0.1 update
Never did have an issue such as this on any other previous updates.
Today, I installed the Sage 50 2024.0.1 Update for a client.
Starting with the server i attempted to install the update.
I received the message: Sage 50 Update could not be completed and needs to be run again.
The steps below resolved the issue and I was able to process the update.
No issue installing the update on the workstations.
Hope this helps anyone having this issue.
Hopefully Sage 50 Support will take a look at this as it does seem that the update process is not stopping the Actian Zen Workgroup database service and apparently it should.
Lonnie
References:
- https://us-kb.sage.com/portal/app/portlets/results/viewsolution.jsp?solutionid=230928152750307&hypermediatext=null
- https://us-kb.sage.com/portal/app/portlets/results/viewsolution.jsp?solutionid=220924250010183&page=1&position=1&q=sage%2050%20update%20could%20not%20be%20completed
- https://superuser.com/questions/117902/find-out-which-process-is-locking-a-file-or-folder-in-windows
- Update did not apply on first attempt.
- Restarted Server
- All attempts would get the message:
Sage 50 Update could not be completed and needs to be run again. - Reviewed: C:\ProgramData\Sage\Peachtree\PeachWLog.XML
- Found line on each installation attempt that stated that during the BackupPatchFileData process, C:\Shared\Data\Sage 50 Data\Company\Attrib.ddf, copying the back files failed.
- Attempted to rename the Attrib.ddf file and could not because some process had it locked.
- Used steps in the above references to find the process which I determined to be the zenengnsvc32.exe process.
- This is the Actian Zen Workgroup Engine Service
- Ending that process freed the lock on the file.
- Note, I did not rename the Attrib.ddf file. Now knowing that the file was no longer locked, I proceeded with the update
- Was able to then complete the update successfully.
- After the update was complete, attempted to start Sage 50 but could not as the Actian Zen Workgroup Engine service was not restarted.
- Restarting this service,Sage would then now open normally.
- Restarted Server just as a best practice.
- Moving on to updating the workstations.
Screenshots:
