Jump to content


BzowK

Help! - BIG Issue with Primary DP After Updating to SP1

Recommended Posts

Good Morning -

 

Last night, I updated our production SCCM 2012 to SP1. I was very careful to check all I could before doing so. The install seemed to go fine and a few tests passed when I was on the primary server.

 

This morning, I tried to open the Admin COnsole isntalled on my workstation and found it wouldn't connect to the site. After running the console installation again, it worked. Easy, right? Just deploy the console to a collection to all who have it installed? I tried to do so, but it never deployed.

 

Here's why - My primary DP (only local one) isn't updating content. My other 3 remote ones are. I checked the logs and here's what I found:

 

Console / Monitoring

  • Distribution Manager failed to find or create the defined share or volume on distribution
  • Distribution Manager failed to process package "SCCM Console SP1"

distmgr.log

  • Failed to set share security on share \\ABCSCCM02.domain.com\SMSSIG$. Error = 5
  • Failed to set access security on share SMSSIG$ on server ABCSCCM02.domain.com
  • DPConnection::Disconnect: Revert to self
  • Cannot find or create the signature share.
  • STATMSG: ID=2324 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=ABCSCCM02.domain.com SITE=ABC PID=2340 TID=6220 GMTDATE=Tue Jan 08 15:16:35.474 2013 ISTR0="["Display=\\BNASCCM02.bassberry.com\"]MSWNET:["SMS_SITE=BBS"]\\ABCSCCM02.domainy.com\" ISTR1="ABC001A1" ISTR2="SMSSIG$" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=2 AID0=400 AVAL0="ABC001A1" AID1=404 AVAL1="["Display=\\ABCSCCM02.domain.com\"]MSWNET:["SMS_SITE=ABC"]\\ABCSCCM02.domain.com\"
  • Error occurred. Performing error cleanup prior to returning.

So far, I opened the SMSSIG$ & SMSPKGE$ shares on the server and compared NTFS & Share permissions to other DPs which looked good. I also added the hostmane of the primary site server as well as the sccm service account with full rights to them, but it didn't help any.

 

All post I've found so far about this say to uninstall/reinstall the DP. I'm sure that would work, but I have tonsof content which would take forever to redistribute.

 

Any suggestions? I'm continuing to search, but wanted to go ahead and post. If uninstall / reinstall of DP is only option, suggested procedures for doing so would be helpful.

 

I've attached my distmgr.log just in case.

 

Any suggestions? Thanks!

 

 

UPDATE 1

After more research, I took screenshots of SMSSIG$'s share and NTFS permissions, then Stopped sharing it. As the post I read said, SCCM did reshare it automatically - but - it still didn't fix the issue.

 

UPDATE 2

Correction - the stopping sharing fixed it - somwhat... If I stop sharing SMSSIG$ then Update my DPs, I here's what happens:

 

1. Stop Sharing SMSSIG$

2. Update DPs on package failing

3. SMSSIG$ is automatically re-shared with correct (supposedly) permissions

4. The package is added to SMSSIG$ (opened folder and verified new sig files are created) + console reports it successfully deployed to DP

5. No other packages can be added - they get the same error.

 

Basically, every time I need to add a package to the DP, I must Stop the SMSSIG$ share once per package. Wierd.

 

Any Ideas? Thanks

distmgr.log

Share this post


Link to post
Share on other sites


Per your other thread, I am curious to see if re-installing the DP role requires you to remove it from each package as well...please post whether or not you end up trying that.

Share this post


Link to post
Share on other sites

hi Ben

sorry for the delay in responding, was this server running the RTM release of Configuration Manager 2012 prior to the upgrade, did it have any of the Cumulative Updates (cu1, cu2) installed ?

 

can you (briefly) describe your upgrade process on that site server ?

Share this post


Link to post
Share on other sites

stopping the sharing is working for me too. But i am seriously thinking about rebuilding my sccm with server 2012 . its too messed up. :(

Share this post


Link to post
Share on other sites

Hey Niall -

 

Thanks for the reply. I know you are busy!

 

Previous to SP1, I was running the release of SCCM 2012. I guess that would be RTM, but def not a Beta! I didn't have any CU's installed, either. To upgrade it, I performed the following steps:

 

1. Verified I had good backups

2. Ran PreReq checker via command line

3. Verified SQL Memory and AD permissions. Had to install something small, but don't remember what it was

4. Installed ADK for Win 8 (Had WAIK previously of course)

5. Disabled the site maintenance task “Delete Aged Client Operations

6. Downloaded all update files needed to folder

7. Ran Pre-Req checker again - all good except SQL RAM & AD Permissions warnings which I'd already verified

8. Restarted dedicated SQL Server (2008) & SCCM Primary server

9. Ran splash.htm and proceeded with upgrade

 

Currently, I'm considering removing the DP and re-installing it. What worries me is that it's on the primary site server. If I proceed, my plan is as follows:

 

1. Try to make backup if possible (again)

2. Cancel advertisements which may use the DP (don't know if needed for packages advertised only during time of this fix being applied or not)

3. Run script here: http://blogs.msdn.com/b/rslaten/archive/2006/03/01/removing-a-retired-dp-from-all-your-packages.aspx

4. Remove DP role from primary site server

5. Monitor DP log and wait for it to catch up

6. Reinstall DP role

 

What say you? Thanks!

Share this post


Link to post
Share on other sites

hi Ben

did you use media from the VLMS site or from Technet/MSDN ?

did you uninstall the WAIK prior to installing the ADK ?

did you reboot your server(s) prior to running setup ?

did you review this ?

Share this post


Link to post
Share on other sites

Good Morning (here in TN) Niall -

 

No, I didn't uninstall WAIK before the ADK install, either. Back on my Technet thread, someone posted a possible workaround which I'm trying now, but there's some controversy behind it. What's your take?

 

Thanks!

Share this post


Link to post
Share on other sites

OK -

Just got off the phone with Microsoft and think we found the issue... I'm now working!

I had my Site System Installation Account set to my service account (DA) which I use for most everything. We changed that back to "Use the site server's computer account to install the site system."

After doing that, I restarted the SMS_Executive services, updated my packages, and they worked!

Microsoft has now marked it as a "Known Bug"

Please try it out and let me know if this resolves your issues, too -

Thanks -

  • Like 1

Share this post


Link to post
Share on other sites

Thanks for the update, Ben...just as a side note to other users who might not know where this setting is at right away: you can find it under the Administration > Servers and Site System Roles> [site] > Site System Roles: Site System

post-7827-0-69434500-1357842776_thumb.jpg

Share this post


Link to post
Share on other sites

hi Ben

did you use media from the VLMS site or from Technet/MSDN ?

did you uninstall the WAIK prior to installing the ADK ?

did you reboot your server(s) prior to running setup ?

did you review this ?

 

That technet article never mentions uninstalling WAIK before installing ADK. Was I supposed to do that?

 

My server behaves very strangley after upgrading to SP1 also, it's very sluggish. I get all kinds of errors in the Site Status and Component Status nodes. Last night I rebooted the server so it could install Windows updates, and when I logged in again the Component Status node contained only a few components, like 4-5. I got errors like these

 

y0Fpm.png

 

I think basically every component or site system role has been in Warning or Critical status a few times since upgrading.

 

Installing applications during OSD sometimes fails also, with different error messages. Apps can sometimes not even be downloaded. I know I'm not being very specific or providing log files, but I can just _feel_ that something's wrong with the server.

 

Was I supposed to create a new ConfigMgr client package and distribute to the DP when I upgraded to SP1? Or was it enough to just update the package on the DP?

 

I should add that everything, apart from WSUS, looks totally fine on server right now. I did a site reset last night. OSD is still kind of shaky though.

Share this post


Link to post
Share on other sites

Good Morning -

 

I finally found the issue after much research.

 

 

I had my Site System Installation Account set to my service account (DA) which I use for most everything. We changed that back to "Use the site server's computer account to install the site system."

 

post-1-0-99645000-1359380535_thumb.jpg

 

After doing that, I restarted the SMS_Executive services, updated my packages, and they worked!

Microsoft has now marked it as a "Known Bug"

Please try it out and let me know if this resolves your issues, too -

 

Thanks -

Share this post


Link to post
Share on other sites

Good Morning -

 

I finally found the issue after much research.

 

 

I had my Site System Installation Account set to my service account (DA) which I use for most everything. We changed that back to "Use the site server's computer account to install the site system."

 

attachicon.gifss1.jpg

 

After doing that, I restarted the SMS_Executive services, updated my packages, and they worked!

Microsoft has now marked it as a "Known Bug"

Please try it out and let me know if this resolves your issues, too -

 

Thanks -

 

also when you change WMI service account to Domain\administrator user. you can solve this problem.

Share this post


Link to post
Share on other sites

Logged in to say thank you, this worked for me too!

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...

×
×
  • Create New...