Did you ever get this resolved? I’m experiencing the same thing. Thankfully, this is in my lab environment though. But when I ran spdiagdrs my SiteStatus is INACTIVE and DrsQueueStatus are both ENABLED with IncomingMessageInQueue and Outgoing both at 0.
CMUpdate.log is still waiting for the cmupdate.box to be updated. Again, thankfully, this is in my lab but hoping I won’t run into this in production. From: listsadmin@lists.myitforum.com [mailto:listsadmin@lists.myitforum.com] On Behalf Of Sherry Kissinger Sent: Tuesday, April 05, 2016 2:00 PM To: ms...@lists.myitforum.com Subject: Re: [mssms] 1602 upgrade stuck I suggest opening a call w/MS. There are lots of moving parts with having a CAS and primaries, and without guidance you could easily make it worse. On Tue, Apr 5, 2016 at 10:49 AM, Mead, Renae (DTMB) <mea...@michigan.gov<mailto:mea...@michigan.gov>> wrote: Thank for you the info. On both the primaries I verified the sites are Active, DrsQueueStatus status is enabled and 0 files in IncomingMessagesInQueue. On the CAS we have 48,069 (which isn’t huge for us) IncomingMessagesInQueue messages and the site status is MAINTENANCE_MODE. The IncomingMessagesInQueue hasn’t changed in over an hour. It appears the CAS flipped to maintenance mode around the time the primaries started updating and hasn’t flipped back. Renae Mead mea...@michigan.gov<mailto:mea...@michigan.gov> From: listsadmin@lists.myitforum.com<mailto:listsadmin@lists.myitforum.com> [mailto:listsadmin@lists.myitforum.com<mailto:listsadmin@lists.myitforum.com>] On Behalf Of Sherry Kissinger Sent: Tuesday, April 5, 2016 10:35 AM To: ms...@lists.myitforum.com<mailto:ms...@lists.myitforum.com> Subject: Re: [mssms] 1602 upgrade stuck on the primary sites, using sql mgmt. studio, run exec spdiagdrs that won't tell you much or help you 'fix' anything, but what I look at is whether it's 'Active' under "SiteStatus" I noticed when we upgraded to 1602 SiteStatus was in a different state as the primary site upgraded. I also noticed that DrsQueueStatus wasn't "Enabled" while the site components were still being reinstalled. Once that flipped to "Enabled", then it was a matter of the primaries getting through the backlog of "IncomingMessageInQueue", and then the CAS server also getting through the "IncomingMessagesInQueue" that the primaries then sent up to the CAS. If DrsQueueStatus is still not enabled, I would look at sitecomp.log on the primary sites, and see if they are choking on reinstalling any particular site component, and work that. If DrsQueueStatus is Enabled, is there a huge huge backlog of "IncomingMessageInQueue" ? it'll depend upon your hardware of course, but anything up to 100,000 for us "isn't that big of a deal"--but we have ridiculous hardware and a lot of clients. Once we get more than that, occasionally we'll get replication warnings until it clears (hasn't happened lately, last time was a particularly ridiculous Software Update release of a zillion updates, or so it felt like ). if DrsQueueStatus is Enabled, and as you re-run the exec spdiagdrs "incomingmessagesinqueue" slowly goes down... then it's literally just "please wait". It simply has to get through all the messages before it gets to the one about "all is well". But... If sitecomp.log doesn't give you any hints, and cmupgrade.log on the primary sites doesn't give you any hints... you may need to open a call. On Tue, Apr 5, 2016 at 8:52 AM, Mead, Renae (DTMB) <mea...@michigan.gov<mailto:mea...@michigan.gov>> wrote: Good morning, Yesterday around 4:30pm updated our production environment to 1602 and this morning at 9am our primary servers are still not reporting installed. Under monitoring it shows “waiting for Configuration manager Update service” and has been in this state all night. We have tried restarting sms_executive service and rebooted the servers without change. We have a CAS and two primary sites. In the CMUpdate.log on the CAS and both primaries it shows “INFO: Successfully dropped update pack installed notification to HMan CFD box.” And then the next line is “Waiting for changes to the "D:\ConfigMgr\inboxes\cmupdate.box" directories, updates will be polled in 600 seconds...: it has been waiting for changes to the cmupdate.box for about 14 hours now. Now we are running into replication failures between all our sites. Maybe because the upgrade is stuck… The Replication link Analyzer says SQL Service Broker login in missing for sites. I had the analyzer recreate SQL service Broker login, but not seeing any change. Has anyone ran into this issue? Thanks, Renae Mead DTMB IS OA Enterprise Services mea...@michigan.gov<mailto:mea...@michigan.gov> (517) 636-0761<tel:%28517%29%20636-0761> Office (517) 388-2737<tel:%28517%29%20388-2737> Mobile -- Thank you, Sherry Kissinger My Parameters: Standardize. Simplify. Automate Blogs: http://www.mofmaster.com, http://mnscug.org/blogs/sherry-kissinger, http://www.smguru.org -- Thank you, Sherry Kissinger My Parameters: Standardize. Simplify. Automate Blogs: http://www.mofmaster.com, http://mnscug.org/blogs/sherry-kissinger, http://www.smguru.org ________________________________ Confidentiality Notice: This e-mail is intended only for the addressee named above. It contains information that is privileged, confidential or otherwise protected from use and disclosure. If you are not the intended recipient, you are hereby notified that any review, disclosure, copying, or dissemination of this transmission, or taking of any action in reliance on its contents, or other use is strictly prohibited. If you have received this transmission in error, please reply to the sender listed above immediately and permanently delete this message from your inbox. Thank you for your cooperation.
