Different app! It has just moved along to the next app in the deployment list!Ĭan this be SCCM? I'm not sure how it could be? 1618 is a client-side error, right?

Looking through the logs, it's the exact same error/exit code, but. Fast forward to today, and the failure rate is back again. All machines completed successfully (and the 'problem' app was installed in most cases). As I mentioned, nothing has changed here, and the previous app is not spawning any other processes that we know of.Īs a test, I enabled the 'Continue on error' checkbox on the affected app, and we ran testing again. However, the previous app appears to have exited with a clean success code. Google tells me that 1618 means that another instance of msiexec is already running/another install is in progress. We traced back through the logs, and found that, in the AppEnforce.log, it was always failing on a specific app, giving the 0x80070652 error and informing us that the app was exiting with code 1618. For the record, nothing has changed on the SCCM servers, the OSD Task Sequence, or any of the software which it is deploying.

However, over the last 2 days, around 50% of machines have begun failing to complete the OSD Task Sequence.

Our deployment department images/re-images around 130 machines in any given day.

Error code 1618 msi