SOLVED After Upgrade Primary to 1802 unable to push new seconday server

[mvdburg]

Hello,

Im facing a serious problem with my SCCM environment. We have a Primary site and several secondary Sites. After upgrading to 1802 I tried to upgrade a secondary site, this failed and that sec site lost his Database connection. I thought, Im removing the secondary and reinstall the windows from base and push the secondary from scratch and let it sync wih my Primary

Until now no luck, I made e rapport call with Microsoft, and we are working on in currently, but after 24 hours they couldn't trigger the issue and come up with a solution yet, so I thought lets throw it in the forum with the really experienced guys.

The Seconday has all prerequisits and the install info looks good:



The ConfigMgrSetop.log shows the following:



The C root of the Secondary shows no SCCM activity:


Manually connect with WMI service looks fine (All kinds of checks are done by MS support)

Is there anybody familiar with this issue and can give me a guiding?

Much appreciated! Regards, Michael

 

[mvdburg]

I thought I would get some feedback on this from the forum, but unfortunately nobody responded or had any suggestions.

after a lot of hours with Microsoft on the phone, I managed to resolve the problem, by cheking all security, logs and diskspace.

The scope log from Microsoft:

Scope:

The case can be archived when we provide assistance in troubleshooting the following issue
Secondary site installation on server xxxx fails with : ERROR: Failed to connect to WMI namespace root\cimv2 on xxxxx.inet-local.com
CWmi::Connect(): ConnectServer(Namespace) failed. - 0x80070005
, or we determine that the issue is caused by hardware, 3rd party software, or identified design behavior.
The case can be reopened if the same issue on the same machine reappears. Any other issue will require a new case to be opened and handled by the appropriate team.
Note:
*Microsoft Professional Support is a break-fix team and does not perform Root Cause Analysis on the issue. Root Cause Analysis is available on Premier Support level: https://premier.microsoft.com
*Data recovery is not supported on any level
*According to Microsoft Policy, each support incident can only address one problem
*More information and Frequently Asked Questions for Professional Support:
https://support.microsoft.com/en-us/gp/support-options-for-business
Current Status:
Resolved. Customer resolved
Analysis / Action Plan:
Increased the size of drive “ D” holding the SQL and SCCM package data
More Information:
part of the sender.log form the Primary server :

Trying the No. 1 address (out of 1) SMS_LAN_SENDER 5/30/2018 2:44:33 PM 8772 (0x2244)
There is no existing connection, Win32 error = 67 SMS_LAN_SENDER 5/30/2018 2:44:33 PM 8772 (0x2244)
There is no existing connection, Win32 error = 67 SMS_LAN_SENDER 5/30/2018 2:44:33 PM 8772 (0x2244)
Error during connection to \\xxxxx\SMS_SITE (67). SMS_LAN_SENDER 5/30/2018 2:44:33 PM 8772 (0x2244)
Error is considered fatal. SMS_LAN_SENDER 5/30/2018 2:44:33 PM 8772 (0x2244)
Cannot connect to server SL-SR-RTM-DP-03.inet-local.com at remote site xxx, won't try send requests going to site RTM for an hour or until there are no active send requests. SMS_LAN_SENDER 5/30/2018 2:44:33 PM 8772 (0x2244)
Could not establish connection. SMS_LAN_SENDER 5/30/2018 2:44:33 PM 8772 (0x2244)
Attempt to connect failed. SMS_LAN_SENDER 5/30/2018 2:44:33 PM 8772 (0x2244)


Error 67 = The network name cannot be found.

Looks like a name resolution issue. We guess the bootstrap did not get coped over as the connection was logs by that time. Make sure that both the primary and secondary can ping each other by name or monitor your network for blips.

 

[Harshit Pandey]

Wow the solution is very different.

 

[Lukas Rottach]

Hi Michael

Thanks a lot for your very detailed posts.

One of our customers is having a very similar issue.
He upgraded his primary site successfully to build 1802.
In the next step he tried to upgrade his three secondary sites.
Since 20 days the secondary sites are stuck in the "Upgrade" state. We noticed, that the database replication to all three sites is no longer working. It is impossible to distribute content to the child sites.

At this point some facts of our analysis:
- No ConfigMgrSetup.log was createt in the C:\ root on the secondary sites
- Same errors like you posted above in the ConfigMgrSetup.log on the primary site

ERROR: Connection strings not initialized
CSql Error: Cannot find data for connection type: , cannot get a connection.
CSql Error: Cannot find data for connection type: SMS Master, cannot get a connection.
CWmi::Connect(): ConnectServer(Namespace) failed. - 0x8004100e



At first look, it looks like a connection issue, but if I test all of the connections manually everything is working.
I am able to connect to the SQL, WMI, UNC and so on without any problems.
We have opened a Microsoft case a few days ago and checked everything like port settings, connection settings and Windows and SQL permissions.

The customer tried to install an additional secondary site a few months ago. That was only possible after copying the sources manually to the target server. The primary site was not able to copy the necessary files by itself.
Maybe there is a connection between that past and the current issue of upgrading the secondary sites.

Maybe you have some ideas.
If you need futher informations, please let me know.
Thanks in advance.

Greetings from Switzerland
Lukas

 

[rsgurunath]

Hi Michael

Thanks a lot for your very detailed posts.

One of our customers is having a very similar issue.
He upgraded his primary site successfully to build 1802.
In the next step he tried to upgrade his three secondary sites.
Since 20 days the secondary sites are stuck in the "Upgrade" state. We noticed, that the database replication to all three sites is no longer working. It is impossible to distribute content to the child sites.

At this point some facts of our analysis:
- No ConfigMgrSetup.log was createt in the C:\ root on the secondary sites
- Same errors like you posted above in the ConfigMgrSetup.log on the primary site

ERROR: Connection strings not initialized
CSql Error: Cannot find data for connection type: , cannot get a connection.
CSql Error: Cannot find data for connection type: SMS Master, cannot get a connection.
CWmi::Connect(): ConnectServer(Namespace) failed. - 0x8004100e

View attachment 1396

At first look, it looks like a connection issue, but if I test all of the connections manually everything is working.
I am able to connect to the SQL, WMI, UNC and so on without any problems.
We have opened a Microsoft case a few days ago and checked everything like port settings, connection settings and Windows and SQL permissions.

The customer tried to install an additional secondary site a few months ago. That was only possible after copying the sources manually to the target server. The primary site was not able to copy the necessary files by itself.
Maybe there is a connection between that past and the current issue of upgrading the secondary sites.

Maybe you have some ideas.
If you need futher informations, please let me know.
Thanks in advance.

Greetings from Switzerland
Lukas

HI ,

Can you elaborate which are the source files that were copied manually and how the secondary site was installed in that way ?