Forums on Intune, SCCM, and Windows 11

Welcome to the forums. Register a free account today to become a member! Once signed in, you'll be able to participate on this site by adding your topics and posts, as well as connect with other members through your own private inbox!

SOLVED ConfigMgr 2303 upgrade to version 2309 failed multiple errors

  • Thread starter Thread starter kchusa
  • Start date Start date
  • Replies Replies 6
  • Views Views 6K
Status
Not open for further replies.

kchusa

Active Member
Messages
25
Solutions
1
Reaction score
0
Points
1
MECM version 2303 upgrade to version 2309, failed multiple errors and multiple warnings, never have had any issues see ConfigMgrPrereq.log attached. Servers the same, OS and SQL server the same, no changes since last version update to 2303. Tried deleting update using cpmupdatereset and letting Precheck run again, but same errors. Current MECM version 2303 is stable and has been since last hotfix KB24719670. Please help and review attached log, Thanks, Kevin
 
Solution
I found the answer here. As soon as I modified the SQL connection properties, the install started and worked like normal.

For those that encounter this, you need changed "Force Encryption" from "On" to "Off". To do this:

1) Log onto the SQL server that hosts your MECM database
2) Open MMC and add the snap-in "SQL Server Configuration Manager"
3) Expand "SQL Server Configuration Manager (Local)"
4) Expand "SQL Server Network Configuration"
5) Right click "Protocols for MSSQLServer" and select "Properties"
6) In the "Flags" tab, change "Force Encryption" to "No"
7) Press "Apply" then "OK"
8) Restart the SQL service (SQL Server (MSSQLSERVER)), either in services.msc or via "SQL Server Services" in SQL Server Configuration Manager

Note...
You need to resolve the SQL DB access error.

*** Failed to connect to the SQL Server, connection type: SMS ACCESS. Configuration Manager Prereq 13-11-2023 07:15:07 532 (0x0214)
ERROR: Failed to connect to SQL Server Configuration Manager Prereq 13-11-2023 07:15:07 532 (0x0214)
 
Thanks Prajwal, not being an SQL guru, have no idea on how to fix and why our current version running on same system instance is working OK. Could our network team have made any changes? Or do you know of any specific tests to check connections and or resolve this error, thanks, Kevin
 
Hello all Techies, does someone have an idea as to why I can not upgrade from MECM 2303 to 2309 on same system, all servers and systems the same as with 2303? attached is the ConfigMgrPreq.log as a zip file. Many Failures and Warnings just doing the upgrade, last upgrade to 2303 was flawless. Thank you.
 

Attachments

I found the answer here. As soon as I modified the SQL connection properties, the install started and worked like normal.

For those that encounter this, you need changed "Force Encryption" from "On" to "Off". To do this:

1) Log onto the SQL server that hosts your MECM database
2) Open MMC and add the snap-in "SQL Server Configuration Manager"
3) Expand "SQL Server Configuration Manager (Local)"
4) Expand "SQL Server Network Configuration"
5) Right click "Protocols for MSSQLServer" and select "Properties"
6) In the "Flags" tab, change "Force Encryption" to "No"
7) Press "Apply" then "OK"
8) Restart the SQL service (SQL Server (MSSQLSERVER)), either in services.msc or via "SQL Server Services" in SQL Server Configuration Manager

Note: I had to keep "Force encryption" set to "No" even after the update completed.
I had set it back to "On" and restarted the SQL service,
but I found that after the admin console updated on the server,
it couldn't connect to the site with the error "Configuration Manager cannot connect to the site <SITE NAME>".
Turning Force Encryption back to off and restarting the SQL service again allowed me to connect the admin console immediately.
 
Solution
Status
Not open for further replies.
Back
Top