SOLVED
Home

In-Place upgrade - Status Waiting for another program

%3CLINGO-SUB%20id%3D%22lingo-sub-1076672%22%20slang%3D%22en-US%22%3EIn-Place%20upgrade%20-%20Status%20Waiting%20for%20another%20program%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1076672%22%20slang%3D%22en-US%22%3E%3CP%3EHi%2C%3C%2FP%3E%3CP%3EIn-Place%20upgrade%20from%20Windows%207%20SP1%20to%20Windows%2010%201803%20was%20working%20fine%20and%20after%20upgrade%20to%20SCCM%2FMECM%201910%20I%20faced%20the%20below%20issues%3A%3C%2FP%3E%3CP%3E1-%26nbsp%3BWindows%2010%20In-Place%20upgrade%20TS%20hang%20and%20never%20start%20-%20showing%20%22%3CSTRONG%3EWaiting%20for%20another%20program%3C%2FSTRONG%3E%22%3C%2FP%3E%3CP%3EClient%20-%20execmgr.log%3C%2FP%3E%3CP%3EChecking%20Account%20subkeys%20returned%20status%200x80070002%2C%20returning%20false.%20-%20warning%3C%2FP%3E%3CP%3EGetMergedSWDistPolicy%20-%20Could%20not%20find%20the%20policy%20in%20WMI%20for%20package%20%3CSTRONG%3EPackage%3C%2FSTRONG%3E%20Program%20*%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E2-%26nbsp%3BIn%26nbsp%3B%3CSTRONG%3ESMS_STATE_SYSTEM%3C%2FSTRONG%3E%3CSPAN%3E%26nbsp%3B%3C%2FSPAN%3EI%20received%20the%20following%20error%20every%205%20minutes%3A%3C%2FP%3E%3CP%3EMicrosoft%20SQL%20Server%20reported%20SQL%20message%208672%2C%20severity%2016%3A%20%5B42000%5D%5B8672%5D%5BMicrosoft%5D%5BSQL%20Server%20Native%20Client%2011.0%5D%5BSQL%20Server%5DThe%20MERGE%20statement%20attempted%20to%20UPDATE%20or%20DELETE%20the%20same%20row%20more%20than%20once.%20This%20happens%20when%20a%20target%20row%20matches%20more%20than%20one%20source%20row.%20A%20MERGE%20statement%20cannot%20UPDATE%2FDELETE%20the%26nbsp%3B%3CBR%20%2F%3E%3CBR%20%2F%3EPlease%20refer%20to%20your%20Configuration%20Manager%20documentation%2C%20SQL%20Server%20documentation%2C%20or%20the%20Microsoft%20Knowledge%20Base%20for%20further%20troubleshooting%20information.%3C%2FP%3E%3CP%3EAnyone%20face%20the%20above%20issues%20after%20upgrade%20%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ETroubleshooting%3A%3C%2FP%3E%3CP%3E1-%20Reset%20Site%20Settings%3C%2FP%3E%3CP%3E2-%20Uninstall%20and%20re-install%20CCM%20agent%26nbsp%3B%3C%2FP%3E%3CP%3E3-%20Verify%20DPs%3C%2FP%3E%3CP%3E4-%20Create%20a%20new%20task%20sequence%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ENote%3A%20Software%20Update%20is%20working%20fine%20and%20PXE%20boot%20is%20also%20working%20fine.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-1076672%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EOperating%20System%20Deployment%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1090855%22%20slang%3D%22en-US%22%3ERe%3A%20In-Place%20upgrade%20-%20Status%20Waiting%20for%20another%20program%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1090855%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F212447%22%20target%3D%22_blank%22%3E%40Abdul%20Jalil%20Abou%20Alzahab%3C%2FA%3EI%20found%20this%20link%2C%20maybe%20this%20can%20help%20you.%3C%2FP%3E%3CP%3ELast%20time%20I%20upgraded%20from%201902%20to%201906%20my%20third%20party%20updates%20stopped%20publishing.%20Only%20after%20installing%20the%20KB%20for%201906%20it%20was%20fixed%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1098927%22%20slang%3D%22en-US%22%3ERe%3A%20In-Place%20upgrade%20-%20Status%20Waiting%20for%20another%20program%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1098927%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F255442%22%20target%3D%22_blank%22%3E%40RahamimL%3C%2FA%3E%26nbsp%3BThanks%20for%20your%20response.%3C%2FP%3E%3CP%3EYou%20are%20right%2C%20In-Place%20upgrade%20back%20to%20normal%20after%20installing%20SCCM%201910%20Hotfix%3A%3C%2FP%3E%3CH1%20id%3D%22toc-hId-358505206%22%20id%3D%22toc-hId-358505206%22%20id%3D%22toc-hId-358505206%22%3EClient%20update%20available%20for%20Configuration%20Manager%20current%20branch%2C%20version%201910%20early%20update%20ring%3C%2FH1%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fsupport.microsoft.com%2Fen-us%2Fhelp%2F4535384%2Fclient-update-available-for-configuration-manager-current-branch-versi%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fsupport.microsoft.com%2Fen-us%2Fhelp%2F4535384%2Fclient-update-available-for-configuration-manager-current-branch-versi%3C%2FA%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1098928%22%20slang%3D%22en-US%22%3ERe%3A%20In-Place%20upgrade%20-%20Status%20Waiting%20for%20another%20program%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1098928%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F212447%22%20target%3D%22_blank%22%3E%40Abdul%20Jalil%20Abou%20Alzahab%3C%2FA%3Eglad%20to%20hear.%3C%2FP%3E%3C%2FLINGO-BODY%3E
Highlighted
Occasional Contributor

Hi,

In-Place upgrade from Windows 7 SP1 to Windows 10 1803 was working fine and after upgrade to SCCM/MECM 1910 I faced the below issues:

1- Windows 10 In-Place upgrade TS hang and never start - showing "Waiting for another program"

Client - execmgr.log

Checking Account subkeys returned status 0x80070002, returning false. - warning

GetMergedSWDistPolicy - Could not find the policy in WMI for package Package Program *

 

2- In SMS_STATE_SYSTEM I received the following error every 5 minutes:

Microsoft SQL Server reported SQL message 8672, severity 16: [42000][8672][Microsoft][SQL Server Native Client 11.0][SQL Server]The MERGE statement attempted to UPDATE or DELETE the same row more than once. This happens when a target row matches more than one source row. A MERGE statement cannot UPDATE/DELETE the 

Please refer to your Configuration Manager documentation, SQL Server documentation, or the Microsoft Knowledge Base for further troubleshooting information.

Anyone face the above issues after upgrade ?

 

Troubleshooting:

1- Reset Site Settings

2- Uninstall and re-install CCM agent 

3- Verify DPs

4- Create a new task sequence

 

Note: Software Update is working fine and PXE boot is also working fine.

3 Replies
Highlighted
Solution

@Abdul Jalil Abou AlzahabI found this link, maybe this can help you.

Last time I upgraded from 1902 to 1906 my third party updates stopped publishing. Only after installing the KB for 1906 it was fixed

Highlighted

@RahamimL Thanks for your response.

You are right, In-Place upgrade back to normal after installing SCCM 1910 Hotfix:

Client update available for Configuration Manager current branch, version 1910 early update ring

https://support.microsoft.com/en-us/help/4535384/client-update-available-for-configuration-manager-c...

 

Highlighted