1802 upgrade stuck at replication

[amit paul]

ried to open SQL Server Configuration Manager however its not allowing me to open, so I was not able to check the SQL name Pipes. screen shot already shared.

[anyweb]

and if it's stuck on the upgrade then once again, share the logs (cmupdate.log)...

[amit paul]

CMUpdate.log file attached. You might get some error related to SQL as I have restarted SQL service many a times.

CMUpdate (2).txt

[anyweb]

you still have these issues, and until they are fixed there's no point trying to upgrade

CONFIGURATION_MANAGER_UPDATE service is starting...  $$<CONFIGURATION_MANAGER_UPDATE><08-21-2018 15:29:46.024+240><thread=2868 (0xB34)>
Microsoft System Center Configuration Manager v5.00 (Build 8540)  $$<CONFIGURATION_MANAGER_UPDATE><08-21-2018 15:29:46.024+240><thread=2868 (0xB34)>
Process ID: 2844  $$<CONFIGURATION_MANAGER_UPDATE><08-21-2018 15:29:46.024+240><thread=2868 (0xB34)>
Worker thread ID: 2868  $$<CONFIGURATION_MANAGER_UPDATE><08-21-2018 15:29:46.024+240><thread=2868 (0xB34)>
Inbox source is local on abc.com  $$<CONFIGURATION_MANAGER_UPDATE><08-21-2018 15:29:46.024+240><thread=2868 (0xB34)>
Set inbox to C:\Program Files\Microsoft Configuration Manager\inboxes\cmupdate.box  $$<CONFIGURATION_MANAGER_UPDATE><08-21-2018 15:29:46.024+240><thread=2868 (0xB34)>
This running on active site server abc.com.  $$<CONFIGURATION_MANAGER_UPDATE><08-21-2018 15:29:46.024+240><thread=2868 (0xB34)>
Inbox source is local on abc.com  $$<CONFIGURATION_MANAGER_UPDATE><08-21-2018 15:29:46.040+240><thread=2868 (0xB34)>
*** [28000][18456][Microsoft][SQL Server Native Client 11.0][SQL Server]Login failed for user 'NT AUTHORITY\SYSTEM'.  $$<CONFIGURATION_MANAGER_UPDATE><08-21-2018 15:29:46.165+240><thread=2868 (0xB34)>
*** [42000][4060][Microsoft][SQL Server Native Client 11.0][SQL Server]Cannot open database "CM_MDC" requested by the login. The login failed.  $$<CONFIGURATION_MANAGER_UPDATE><08-21-2018 15:29:46.165+240><thread=2868 (0xB34)>
*** [28000][18456][Microsoft][SQL Server Native Client 11.0][SQL Server]Login failed for user 'NT AUTHORITY\SYSTEM'.  $$<CONFIGURATION_MANAGER_UPDATE><08-21-2018 15:29:46.181+240><thread=2868 (0xB34)>
*** [42000][4060][Microsoft][SQL Server Native Client 11.0][SQL Server]Cannot open database "CM_MDC" requested by the login. The login failed.  $$<CONFIGURATION_MANAGER_UPDATE><08-21-2018 15:29:46.181+240><thread=2868 (0xB34)>
*** Failed to connect to the SQL Server, connection type: SMS ACCESS.  $$<CONFIGURATION_MANAGER_UPDATE><08-21-2018 15:29:46.181+240><thread=2868 (0xB34)>
ExecuteSqlCMUpdateInitScripts: Can't get SQL connection  $$<CONFIGURATION_MANAGER_UPDATE><08-21-2018 15:29:46.181+240><thread=2868 (0xB34)>
*** [28000][18456][Microsoft][SQL Server Native Client 11.0][SQL Server]Login failed for user 'NT AUTHORITY\SYSTEM'.  $$<CONFIGURATION_MANAGER_UPDATE><08-21-2018 15:29:46.196+240><thread=2868 (0xB34)>
*** [42000][4060][Microsoft][SQL Server Native Client 11.0][SQL Server]Cannot open database "CM_MDC" requested by the login. The login failed.  $$<CONFIGURATION_MANAGER_UPDATE><08-21-2018 15:29:46.196+240><thread=2868 (0xB34)>
*** [28000][18456][Microsoft][SQL Server Native Client 11.0][SQL Server]Login failed for user 'NT AUTHORITY\SYSTEM'.  $$<CONFIGURATION_MANAGER_UPDATE><08-21-2018 15:29:46.196+240><thread=2868 (0xB34)>
*** [42000][4060][Microsoft][SQL Server Native Client 11.0][SQL Server]Cannot open database "CM_MDC" requested by the login. The login failed.  $$<CONFIGURATION_MANAGER_UPDATE><08-21-2018 15:29:46.196+240><thread=2868 (0xB34)>
*** Failed to connect to the SQL Server, connection type: SMS ACCESS.  $$<CONFIGURATION_MANAGER_UPDATE><08-21-2018 15:29:46.196+240><thread=2868 (0xB34)>
ERROR: Can not get InstallationType from SetupInfo  $$<CONFIGURATION_MANAGER_UPDATE><08-21-2018 15:29:46.196+240><thread=2868 (0xB34)>
Failed to initialize. 

 

[amit paul]

Hi Garth, SQL Name pipes are disabled. Do I need to enable it.

[GarthMJ]

I always enabled Names Pipes. However, if you have an open ticket with MS, I strongly recommend that you don't continue with troubleshooting in the forums. Items I guess might conflict with item CSS suggest. This will increase the time it takes to solve the problem and may cause new problems. 

[amit paul]

issue got resolved after solving SQL server configuration manager issues.

 

Open a command prompt as administrator

Navigate to your SQL version’s shared directory (cd <version path>):

SQL 2008:  C:\Program Files (x86)\Microsoft SQL Server\90\Shared\
SQL 2008 R2:  C:\Program Files (x86)\Microsoft SQL Server\100\Shared\
SQL 2012:  C:\Program Files (x86)\Microsoft SQL Server\110\Shared\
SQL 2014:  C:\Program Files (x86)\Microsoft SQL Server\120\Shared\

Then run the following command:

mofcomp sqlmgmproviderxpsp2up.mof

1802 Upgrade successfully completed.

[anyweb]

thanks for posting the solution, your SQL server configuration was well messed up though.

[amit paul]

Yes niall, thanks a lot for all your support

Thank you Garth for your support.

[anyweb]

did Microsoft CSS explain why they thought your SQL was in such a bad state ?