sharepoint pssnapin lose backend? about autospinstaller

[McAndersDK]

Okey, it just after the run-psconfig step.
Something in that break the already added poweshell snapin. :(

[brianlala]

I'm noticing this too quite frequently. Only with SP2016, and possibly only on Server 2016 as well. Everything works fine in 2013. Even some of my other scripts (AutoSPUpdater) have issues where the "connection" to the PSSnapin gets lost and cmdlets no longer run. Also, frustratingly inconsistent!

Brian

[McAndersDK]

Hmm it seems to somehow connected to a language pack installationen that are not "done" correctly, the Danish language pack are not populating the da-dk in HKLM:\SOFTWARE\Microsoft\Office Server\16.0\InstalledLanguages\

So AutoSPInstaller try to installed it every time, and this will kick psconfig to run again, and break the snapin.

Do this ring a bell on ur side Brian? :)

[brianlala]

Unfortunately it doesn't - but I think the real question is, why does PSConfig break the snapin...?

[McAndersDK]

I have created a support case with microsoft :) lets see what they find out :) All powershell windows that is open while psconfig run will stop working. Only new consoles after it finish will work.

[brianlala]

Excellent, let me know what happens! Brian Sent from Mail for Windows 10 From: McAndersDK Sent: October 20, 2017 9:32 AM To: brianlala/AutoSPInstaller Cc: Brian Lalancette; Comment Subject: Re: [brianlala/AutoSPInstaller] sharepoint pssnapin lose backend?(#11) I have created a support case with microsoft :) lets see what they find out :) All powershell windows that is open while psconfig run will stop working. Only new consoles after it finish will work. MVH Anders Andersson Den 20. okt. 2017 kl. 18.26 skrev Brian Lalancette <[email protected]<mailto:[email protected]>>: Unfortunately it doesn't - but I think the real question is, why does PSConfig break the snapin...? — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub<#11 (comment)>, or mute the thread<https://github.com/notifications/unsubscribe-auth/ANo3EpyMAhwOQE1L7rczvdUcwOBzx9tpks5suMmhgaJpZM4P-5CV>. — You are receiving this because you commented. Reply to this email directly, view it on GitHub, or mute the thread.

[McAndersDK]

They could reproduce the "bug", they wanted an Business Impact, for starting a potential fix for it.
Still pending response on the BI.

Only workaround suggested is to start a new powershell session after PSconfig is done.

[brianlala]

Interesting! Do you have a case number by chance, so I can track it internally? You can email it to me if you prefer.

[McAndersDK]

Sure :) 117102016527014

[brianlala]

Found it, thanks!