Jump to content


mindbox

Console always shows zero targeted Distribution Points

Recommended Posts

Configuration Manager console seems to have developed a strange fault, about a third of all packages are showing as having zero targeted Distribution points. It may have started since we updated to R2 CU3 back in December but it's only recently been noticed. This is a single site setup with a 2 DPs both contain the same data and source data locations haven't changed.

 

So far I have validated the content, redistributed it, removed it, I have even added new packages and they display the same issue.

Checked the logs distmgr, smsdpmon, there are no errors and the distribution point status shows new package source being distributed successfully.

I have run the Content Explorer from the R2 Toolkit and that looks all ok, showing no Invalid or Pending packages.

I have also checked the Admin UI logs for any possible SQL errors but there are no errors in that either.

I have also performed a site reset to restore permissions in case it was that but no change.

 

Any ideas much appreciated as I need to resolve this for a customer.

Share this post


Link to post
Share on other sites

The SMSProv.log is showing:

Error setting property (TransformAnalysisDate) 0x80041002! SMS Provider 09/02/2015 10:07:27 11832 (0x2E38)
Error setting property (TransformReadiness) 0x80041002! SMS Provider 09/02/2015 10:07:27 11832 (0x2E38)

This is appearing every time an item is accessed in the console.

Also I now noticed that the targeted count for any package it not changing, whether I add or remove DP's from the package it makes no difference.

Share this post


Link to post
Share on other sites

Does this apply to new packages too? Or only existing?

If newly created packages are without errors, you could recreate them. I know that's a LOT of work, but there might be some powershell scripts out there that can help.

 

I was also hoping that might be the case but it's happening with old and new ones.

 

The Distribution Point status is showing sucessfully distributed for the zero targeted ones and the existing ones, So it's looking like the SQL table isn't being updated for the content status view. SQL Issue somewhere maybe?

Share this post


Link to post
Share on other sites

All now resolved. Turns out that when the local SQL Express was updated to SQL Standard 2012 it failed to update the triggers for the DP and Content views. Unfortunately it did require a small piece of SQL editing but nothing that detrimentally affects anything else in the console.

 

Within the SQL Console you can run the following the reset the triggers, this then solved the issue of the content status not updating, However as always there is no recommendation to manually edit the SQL Database.

 

sp_configure 'show advanced options' , 1

reconfigure with override

sp_configure 'server trigger recursion' , 1

reconfigure with override

sp_configure 'nested triggers' , 1

reconfigure with override

Once complete, you can redistribute all packages from the Distribution point Content Tab in the Distribution Point properties.

  • Like 1

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...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.