SCCM 2012 R2 SP1 - Ribbon - Wunderbar - Not loading for deployments on collections

Issue is bizarre. We have a CAS setup with 3 primaries attached. (To get this out of the way: Yes we have a CAS, yes there are disadvantages).

In the SCCM Console, whenever you select a Device Collection and view the Deployments Tab. The Ribbon/Wunderbar in the console should populate with the Delete/Properties buttons, if you right click on a listed deployment those same options should appear.

Instead we have a continuously scrolling grey bar under the ribbon, and all icons are greyed out. In turning on advanced console logging, we see the follow entries displayed continuously: 

[19, PID:7524][06/22/2015 07:16:01] :Tasks not in cache for node 'msscnav://root/Windows/Wunderbar/ConsoleDisplay/AssetManagementNode/AssetManagementNodeOverview/DevicesNode/2e1945a8-627b-42ea-bcf1-d17bad4bf91f/901d377d-6dbe-495f-8a4a-1941462113ae/81e2cb84-f782-4d5a-80b0-ab52452265fc', calculating, ID='911480eb-a11d-40ee-87e6-751c9bf4821e-DefaultOpenTask'.

At this point, the remaining areas of the console remain usable; and everything works normally. All deployment properties are inaccessible.

June 22nd, 2015 9:26am

Side comment: the ribbon bar is not the wunderbar. The wunderbar is the control in the bottom left that allows you to change between the workspaces like "Administration" and "Assets and Compliance".

Does this happen for the console on the site server or remotely connected consoles (or both)?

Do you have any third-party extensions installed?

What version of ConfigMgr are you running?

Free Windows Admin Tool Kit Click here and download it now
June 22nd, 2015 9:46am

This issue happens on any site regardless of where the console is connected, and happens to all users. We have SCCM right click tools installed. But the issue persists for fresh installations of the console.

This is SCCM 2012 R2 SP1, on the latest update. This issue started after we performed the upgrade to the latest patch, although there is nothing else to suggest the episodes are linked.

June 22nd, 2015 10:10am

By "patch" I assume you mean "service pack"?

I've seen one weird issue with the console since the upgrade although that issue is only sporadic.

What happens when you go to the actual deployment tab for the package or application?

Free Windows Admin Tool Kit Click here and download it now
June 22nd, 2015 1:13pm

There isnt any difference whether the deployment is viewed from the collection or the application. So the ribbon just keeps scrolling and does not display and buttons.
June 22nd, 2015 2:35pm

And this happens on consoles installed on your workstation also?
Free Windows Admin Tool Kit Click here and download it now
June 22nd, 2015 7:16pm

Yes, theres no difference between where the console is installed. Sometimes, infrequently you can access the deployment options from the Deployments tab of an Application, on collections it cosistently fails.
June 29th, 2015 11:52am

Time to open a case with Microsoft Customer Support Services then. I can't say I've had any problems remotely similar to this so it'll probably take some actual hands-on troubleshooting and possibly even in-depth knowledge of the console code.
Free Windows Admin Tool Kit Click here and download it now
June 29th, 2015 1:24pm

Hi,

We have encountered the same issue in our environment, also SCCM 2012 R2 SP1. Here are the observations I have recorded so far:

  • Issue starts when user clicks deployment tab on a collection AND there is a software update group deployment on the collection AND the software update group deployment is selected - either by default or by a user clicking it. The issue does NOT start happening unless these three conditions are met, exactly.
  • After the issue starts happening - all subsequently viewed collection deployment tabs on all other collections, regardless of type of deployment exhibit the issue until console restart.
  • After the issue starts happening - viewing the deployments from the Application/SUG objects (i.e. the '\Software Library\Overview\Application Management\Applications' and '\Software Library\Overview\Application Management\Packages' nodes) themselves also exhibit the issue and are non-functional.
  • Before and after the issue - editing deployments via the [\Monitoring\Overview\Deployments] path is unaffected and is always accessible.
  • Before the issue starts happening, - viewing/editing the deployments through the Software Library nodes works normally, no issues for any deployment type.
  • Issue persists until console is restarted - then issue no longer occurs until a collection's deployments tab is clicked that has a SUG deployment active.

Originally we thought it was an issue with any random deployment but that turned out to be just because once the issue starts, it affects all deployment editing nodes (except the monitoring tab ones). The start of the issue for us is always very specifically the highlighting/selection of a software update group (SUG) deployment on the collection -> deployments tab. After the issue starts, it persists on all collection -> deployment tabs and all software library object -> deployments tabs.

Can anyone else seeing this issue confirm these specifics are the same in their environment?

Has anyone had luck contacting Microsoft support about the issue or have any case numbers or bug IDs to share?

Thanks!

- Joel

July 2nd, 2015 3:52pm

The above is great info and detail but honestly more or less useless here in the forum. You need to open a case with Microsoft to get any sort of attention on this as it does appear to be a bug.
Free Windows Admin Tool Kit Click here and download it now
July 2nd, 2015 4:45pm

Hi,

We have encountered the same issue in our environment, also SCCM 2012 R2 SP1. Here are the observations I have recorded so far:

  • Issue starts when user clicks deployment tab on a collection AND there is a software update group deployment on the collection AND the software update group deployment is selected - either by default or by a user clicking it. The issue does NOT start happening unless these three conditions are met, exactly.
  • After the issue starts happening - all subsequently viewed collection deployment tabs on all other collections, regardless of type of deployment exhibit the issue until console restart.
  • After the issue starts happening - viewing the deployments from the Application/SUG objects (i.e. the '\Software Library\Overview\Application Management\Applications' and '\Software Library\Overview\Application Management\Packages' nodes) themselves also exhibit the issue and are non-functional.
  • Before and after the issue - editing deployments via the [\Monitoring\Overview\Deployments] path is unaffected and is always accessible.
  • Before the issue starts happening, - viewing/editing the deployments through the Software Library nodes works normally, no issues for any deployment type.
  • Issue persists until console is restarted - then issue no longer occurs until a collection's deployments tab is clicked that has a SUG deployment active.

Originally we thought it was an issue with any random deployment but that turned out to be just because once the issue starts, it affects all deployment editing nodes (except the monitoring tab ones). The start of the issue for us is always very specifically the highlighting/selection of a software update group (SUG) deployment on the collection -> deployments tab. After the issue starts, it persists on all collection -> deployment tabs and all software library object -> deployments tabs.

Can anyone else seeing this issue confirm these specifics are the same in their environment?

Has anyone had luck contacting Microsoft support about the issue or have any case numbers or bug IDs to share?

Thanks!

- Joel

  • Proposed as answer by nolajp 4 hours 39 minutes ago
  • Unproposed as answer by nolajp 4 hours 39 minutes ago
July 2nd, 2015 7:50pm

Hi,

We have encountered the same issue in our environment, also SCCM 2012 R2 SP1. Here are the observations I have recorded so far:

  • Issue starts when user clicks deployment tab on a collection AND there is a software update group deployment on the collection AND the software update group deployment is selected - either by default or by a user clicking it. The issue does NOT start happening unless these three conditions are met, exactly.
  • After the issue starts happening - all subsequently viewed collection deployment tabs on all other collections, regardless of type of deployment exhibit the issue until console restart.
  • After the issue starts happening - viewing the deployments from the Application/SUG objects (i.e. the '\Software Library\Overview\Application Management\Applications' and '\Software Library\Overview\Application Management\Packages' nodes) themselves also exhibit the issue and are non-functional.
  • Before and after the issue - editing deployments via the [\Monitoring\Overview\Deployments] path is unaffected and is always accessible.
  • Before the issue starts happening, - viewing/editing the deployments through the Software Library nodes works normally, no issues for any deployment type.
  • Issue persists until console is restarted - then issue no longer occurs until a collection's deployments tab is clicked that has a SUG deployment active.

Originally we thought it was an issue with any random deployment but that turned out to be just because once the issue starts, it affects all deployment editing nodes (except the monitoring tab ones). The start of the issue for us is always very specifically the highlighting/selection of a software update group (SUG) deployment on the collection -> deployments tab. After the issue starts, it persists on all collection -> deployment tabs and all software library object -> deployments tabs.

Can anyone else seeing this issue confirm these specifics are the same in their environment?

Has anyone had luck contacting Microsoft support about the issue or have any case numbers or bug IDs to share?

Thanks!

- Joel

  • Proposed as answer by nolajp Tuesday, July 28, 2015 3:12 AM
  • Unproposed as answer by nolajp Tuesday, July 28, 2015 3:12 AM
Free Windows Admin Tool Kit Click here and download it now
July 2nd, 2015 7:50pm

Hi,

We have encountered the same issue in our environment, also SCCM 2012 R2 SP1. Here are the observations I have recorded so far:

  • Issue starts when user clicks deployment tab on a collection AND there is a software update group deployment on the collection AND the software update group deployment is selected - either by default or by a user clicking it. The issue does NOT start happening unless these three conditions are met, exactly.
  • After the issue starts happening - all subsequently viewed collection deployment tabs on all other collections, regardless of type of deployment exhibit the issue until console restart.
  • After the issue starts happening - viewing the deployments from the Application/SUG objects (i.e. the '\Software Library\Overview\Application Management\Applications' and '\Software Library\Overview\Application Management\Packages' nodes) themselves also exhibit the issue and are non-functional.
  • Before and after the issue - editing deployments via the [\Monitoring\Overview\Deployments] path is unaffected and is always accessible.
  • Before the issue starts happening, - viewing/editing the deployments through the Software Library nodes works normally, no issues for any deployment type.
  • Issue persists until console is restarted - then issue no longer occurs until a collection's deployments tab is clicked that has a SUG deployment active.

Originally we thought it was an issue with any random deployment but that turned out to be just because once the issue starts, it affects all deployment editing nodes (except the monitoring tab ones). The start of the issue for us is always very specifically the highlighting/selection of a software update group (SUG) deployment on the collection -> deployments tab. After the issue starts, it persists on all collection -> deployment tabs and all software library object -> deployments tabs.

Can anyone else seeing this issue confirm these specifics are the same in their environment?

Has anyone had luck contacting Microsoft support about the issue or have any case numbers or bug IDs to share?

Thanks!

- Joel

  • Proposed as answer by nolajp Tuesday, July 28, 2015 3:12 AM
  • Unproposed as answer by nolajp Tuesday, July 28, 2015 3:12 AM
July 2nd, 2015 7:50pm

Hi Serg Danshin and nolajp,

have you got an answer from Microsoft already?

We have the same problem in our environment after updating to SCCM 2012 R2 SP1.

Sincerely yours, Christian


Free Windows Admin Tool Kit Click here and download it now
July 6th, 2015 4:59am

Hi Serg Danshin and nolajp,

have you got an answer from Microsoft already?

We have the same problem in our environment after updating to SCCM 2012 R2 SP1.

Sincerely yours, Christian


July 6th, 2015 8:55am

Hi Serg Danshin and nolajp,

have you got an answer from Microsoft already?

We have the same problem in our environment after updating to SCCM 2012 R2 SP1.

Sincerely yours, Christian


Free Windows Admin Tool Kit Click here and download it now
July 6th, 2015 8:55am

Hi Serg Danshin and nolajp,

have you got an answer from Microsoft already?

We have the same problem in our environment after updating to SCCM 2012 R2 SP1.

Sincerely yours, Christian


July 6th, 2015 8:55am

Hi Christian,

No, we are building our case to submit to Microsoft, although as usual that will take several days to be processed and any results to come back. I will make sure to update this post if I get details that I can share.

FWIW - You can workaround the issue by relaunching your console (if its already happening) and using the "Monitoring -> Deployments" or Software Library views, instead of viewing deployments via the collection. This has allowed us to treat the issue as an annoying bug but not a 'show-stopping' bug, while we work to get a fix from Microsoft.

Free Windows Admin Tool Kit Click here and download it now
July 6th, 2015 11:00am

Hi Christian,

No, we are building our case to submit to Microsoft, although as usual that will take several days to be processed and any results to come back. I will make sure to update this post if I get details that I can share.

FWIW - You can workaround the issue by relaunching your console (if its already happening) and using the "Monitoring -> Deployments" or Software Library views, instead of viewing deployments via the collection. This has allowed us to treat the issue as an annoying bug but not a 'show-stopping' bug, while we work to get a fix from Microsoft.


  • Proposed as answer by nolajp 4 hours 39 minutes ago
  • Edited by nolajp 4 hours 38 minutes ago Emphasize workaround
July 6th, 2015 2:56pm

Hi Christian,

No, we are building our case to submit to Microsoft, although as usual that will take several days to be processed and any results to come back. I will make sure to update this post if I get details that I can share.

FWIW - You can workaround the issue by relaunching your console (if its already happening) and using the "Monitoring -> Deployments" or Software Library views, instead of viewing deployments via the collection. This has allowed us to treat the issue as an annoying bug but not a 'show-stopping' bug, while we work to get a fix from Microsoft.


  • Proposed as answer by nolajp Tuesday, July 28, 2015 3:12 AM
  • Edited by nolajp Tuesday, July 28, 2015 3:12 AM Emphasize workaround
Free Windows Admin Tool Kit Click here and download it now
July 6th, 2015 2:56pm

Hi Christian,

No, we are building our case to submit to Microsoft, although as usual that will take several days to be processed and any results to come back. I will make sure to update this post if I get details that I can share.

FWIW - You can workaround the issue by relaunching your console (if its already happening) and using the "Monitoring -> Deployments" or Software Library views, instead of viewing deployments via the collection. This has allowed us to treat the issue as an annoying bug but not a 'show-stopping' bug, while we work to get a fix from Microsoft.


  • Proposed as answer by nolajp Tuesday, July 28, 2015 3:12 AM
  • Edited by nolajp Tuesday, July 28, 2015 3:12 AM Emphasize workaround
July 6th, 2015 2:56pm

Exactly same problem here. Can't wait for Microsoft's reply to you 8)
Free Windows Admin Tool Kit Click here and download it now
July 8th, 2015 5:50am

Yes, I have exactly the same problem but I have no clue of how it can be solves. I am hoping that Microsoft soon comes up with hotfixes. It is very irritating problem.
July 10th, 2015 7:40am

I have the same problem.
Free Windows Admin Tool Kit Click here and download it now
July 13th, 2015 9:00am

This was confirmed as a bug by support. They indicated it would be resolved in CU1 for SP2/R2SP1. For now, I recommend using the workaround I described above to avoid the issue, or use PowerShell! :-)
July 15th, 2015 12:39pm

The workaround is good for viewing deployments but what about stopping/deleting the deployments?  Any workaround for that?
Free Windows Admin Tool Kit Click here and download it now
July 24th, 2015 10:45am

3 different environments, all recently upgraded to latest Service Pack.  2 were 2012 R2 to 2012 R2 SP1. 1 was 2012 SP1 to 2012 SP2, then enabling R2 features. So the same build for all 3 now.

I see the same issue.  Also seeing the Root of collections show me every collection even if they are in other folders.  In a glitch sort of way in the deployment wizard.

Let us know if MS resolves for you.

-LvilleSystemsJockey 

July 27th, 2015 11:03pm

Hi FOTWN,

You should be able to delete / edit deployments by using the 'Deployments' tab on a specific object (Software Update Group / Application / Package / etc.) on the 'Software Library' main section. Do not use any collection level deployment list view in 'Assets and Compliance', at least not those with Software Update Group deployments configured - and you should be able to avoid this issue. Sorry for the late reply, let me know if you have any questions. 

Free Windows Admin Tool Kit Click here and download it now
July 27th, 2015 11:12pm

3 different environments, all recently upgraded to latest Service Pack.  2 were 2012 R2 to 2012 R2 SP1. 1 was 2012 SP1 to 2012 SP2, then enabling R2 features. So the same build for all 3 now.

I see the same issue.  Also seeing the Root of collections show me every collection even if they are in other folders.  In a glitch sort of way in the deployment wizard.

Let us know if MS resolves for you.

-LvilleSystemsJockey 

 Hey LvilleSystemsJockey,

  I will make sure to come back to this thread if I hear anything else, but at this point our incident is resolved and we do not expect anything more from Microsoft until they release the fix in CU1. Timeframe is unclear for CU1 - it may be affected by support volume, that I am not sure about.

July 27th, 2015 11:14pm

Hi FOTWN,

You should be able to delete / edit deployments by using the 'Deployments' tab on a specific object (Software Update Group / Application / Package / etc.) on the 'Software Library' main section. Do not use any collection level deployment list view in 'Assets and Compliance', at least not those with Software Update Group deployments configured - and you should be able to avoid this issue. Sorry for the late reply, let me know if you have any questions. 

FOTWN,

The only way I have found to avoid so far is to never look at the deployment through the collection node. NOLAJP eluded to this in his post.  If you do look at deployments through collection views, it seems to start exhibiting the behavior described in this post. 

If you have a need to stop a deployment, the fast way to make that happen (even without the bug) is to disable the Program / Task Sequence that is deployed.  This will take hold much faster than deleting an deployment.  This behavior described in post will not prevent you from doing that unless it is a Software Update Deployment.  In which case, the only option is to avoid Collection views and get straight to the Software Update Group itself from the start (again, indicated by NOLAJP).

-LvilleSystemsJockey


Free Windows Admin Tool Kit Click here and download it now
July 28th, 2015 10:31pm

Same problem here. I can't change any deployments from Deployments Tab.
July 30th, 2015 4:02pm

You can still see the deployments from the PROPERTIES of the collection.  Then you would at least be able to view all deployments without locking the console up.  However, it would be necessary to go find the object that is being deployed at it's source in another area of the console to be able to take action on it.

Hope this helps someone.

-Lville

Free Windows Admin Tool Kit Click here and download it now
July 31st, 2015 3:56pm

https://support.microsoft.com/en-us/kb/3074857

CU1 addresses this.  Thanks Microsoft!!

August 4th, 2015 4:24pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics