I've installed WSUS and have the windows updates information listed in SCCM 2012. I've created a software update group with Windows XP updates only which I then created a deployment package for to deploy to my test collection which contains one Windows XP workstation. The issue I keep encountering over and over again is when the deployment package finishes being created, it finishes with warnings and the vast majority of my updates show with a warning icon and the message (The SMS Provider reported an error). I've looked for some answers, but since a few of them are going through and most of them are throwing this error, I'm not really getting anywhere. Does anyone have any ideas on what this may mean? Thank you.

• Edited by mdh1979 Tuesday, May 21, 2013 9:54 PM

The package source directory you specify must be writable by the computer account of the system hosting the SMS Provider.

Also note that you don't deploy deployment packages (despite their terribly chosen name). Deployment Packages simply make update binaries available to clients when and if they need them.

I checked that and permissions are correct on the directory I assigned during the creation of the deployment package. I looked in the directory itself and I see what appears to be the exe's for all the updates, which is bizarre, because I'm still seeing the "SMS Provider Reported an Error" on all the updates in the final part of the wizard, and it says all of the selected updates cannot be downloaded, but it appears they are there in the directory. I'm sort of confused. 

Is there a better log I should be looking at that may provide more detail? Thank you.

Check the "component status" under the "System Status" in the monitoring console.  Check for errors with the SMS_distribution_manager node.

smsprov.log should provide more detail.

I checked here, and there are no errors what so ever. My package's installation deadline is set in about 20 minutes, it's just a small test package. Is there something I can check client-side to see if the installs process properly?

I looked in this log, but there's so much there I'm having a hard time telling if there's an actual problem, mostly SQL statements from what I see.

Try using the cmtrace.exe tool to view the logs.  It's in the tools folder of the Config Manager program directory on the server.  It highlights the errors, much easier to read. 

Here's the last error in that log, there are a few before it in reference to ADLastLogonTime, but we didn't implement the AD schema extension as it wasn't required and we just want to use this to update clients and endpoint protection, so from what I read, we don't have to do that. Here's the last error I see that didn't reference an AD issue:

Execute SQL =select  all SMS_DeploymentSummary.AssignmentID,SMS_DeploymentSummary.CI_ID,SMS_DeploymentSummary.CollectionID,SMS_DeploymentSummary.CollectionName,SMS_DeploymentSummary.CreationTime,SMS_DeploymentSummary.DeploymentID,SMS_DeploymentSummary.DeploymentIntent,SMS_DeploymentSummary.DeploymentTime,SMS_DeploymentSummary.DesiredConfigType,SMS_DeploymentSummary.EnforcementDeadline,SMS_DeploymentSummary.FeatureType,SMS_DeploymentSummary.ModelName,SMS_DeploymentSummary.ModificationTime,SMS_DeploymentSummary.NumberErrors,SMS_DeploymentSummary.NumberInProgress,SMS_DeploymentSummary.NumberOther,SMS_DeploymentSummary.NumberSuccess,SMS_DeploymentSummary.NumberTargeted,SMS_DeploymentSummary.NumberUnknown,SMS_DeploymentSummary.ObjectTypeID,SMS_DeploymentSummary.PackageID,SMS_DeploymentSummary.PolicyModelID,SMS_DeploymentSummary.ProgramName,SMS_DeploymentSummary.SoftwareName,SMS_DeploymentSummary.SummarizationTime,SMS_DeploymentSummary.SummaryType from fn_DeploymentSummary(1033) AS SMS_DeploymentSummary  where SMS_DeploymentSummary.CollectionID = N'BKS00016'    SMS Provider    5/22/2013 12:50:28 PM    9556 (0x2554)

Yes, I know this is an old post, but Im trying to clean them up. Did you solve this problem, if so what was the solution?

The log snip-it that you posted does not contain an error. You will need to dig deeper to figure out this problem.

The provider error could be a sign of a database lag, write or wmi issue on the server.