Distribution Manager failed to process package triggers an update of the packages

Hi all,
we have randomly following issue:
SCCM 2012 Sp1 CAS, takes a snapshot of a Windows update package in the morning (not sure how the frequency of this check is done). If for any reason it fails, SCCM automatically redistributes the package to all sites. This happened this morning again for 5
Windows updates packages. You understand that this means GB sent to all Secondary sites (66) with an useles amount of data sent out.
From the Status messages I see
Information Milestone RC0 06.11.2014 07:12:11 SCHVSGGSC600.rccad.net SMS_DISTRIBUTION_MANAGER 2300 Distribution Manager is beginning to process package "SUP-2014.09" (package ID = RC00017B).
Then lot of updates lists with comment taking a snapshot and finally
Error Milestone RC0 06.11.2014 07:12:29 SCHVSGGSC600.rccad.net SMS_DISTRIBUTION_MANAGER 2302 Distribution Manager failed to process package "SUP-2014.09" (package ID = RC00017B). Possible cause: Distribution manager does not have access to either the package source directory or the distribution point. Solution: Verify that distribution manager can access the package source directory/distribution point. Possible cause: The package source directory contains files with long file names and the total length of the path exceeds the maximum length supported by the operating system. Solution: Reduce the number of folders defined for the package, shorten the filename, or consider bundling the files using a compression utility. Possible cause: There is not enough disk space available on the site server computer or the distribution point. Solution: Verify that there is enough free disk space available on the site server computer and on the distribution point. Possible cause: The package source directory contains files that might be in use by an active process. Solution: Close any processes that maybe using files in the source directory. If this failure persists, create an alternate copy of the source directory and update the package source to point to it.
This triggers immediately an update of all DPs
Information Milestone RC0 06.11.2014 07:43:52 SCHVSGGSC600.rccad.net SMS_DISTRIBUTION_MANAGER 2304 Distribution Manager is retrying to distribute package "RC00017B". Wait to see if the package is successfully distributed on the retry.
Any idea
How this can be avoided, since nobody changed the package and we suppose it was a temp connection issue between the CAS and the package repository server
If this check can be set up to once a week for instance or even less?
Thanks,
Marco

Hi Daniel,
thanks for the prompt answer. Actually I saw it yesterday at least for 1 package (the last one). The error is generate by SQL killing a task
Adding these contents to the package RC00010D version 347.
SMS_DISTRIBUTION_MANAGER 06.11.2014 07:12:23
7796 (0x1E74)
Sleep 30 minutes... SMS_DISTRIBUTION_MANAGER
06.11.2014 07:12:23 3652 (0x0E44)
*** [40001][1205][Microsoft][SQL Server Native Client 11.0][SQL Server]Transaction (Process ID 152) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. Rerun the transaction.
SMS_DISTRIBUTION_MANAGER 06.11.2014 07:12:25
5460 (0x1554)
STATMSG: ID=2302 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=SCHVSGGSC600.rccad.net SITE=RC0 PID=2144 TID=5460 GMTDATE=jeu. nov. 06 06:12:25.422 2014 ISTR0="SUP-2012.Q4" ISTR1="RC000068" ISTR2=""
ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=1 AID0=400 AVAL0="RC000068"
SMS_DISTRIBUTION_MANAGER 06.11.2014 07:12:25
5460 (0x1554)
Failed to process package RC000068 after 0 retries, will retry 100 more times
SMS_DISTRIBUTION_MANAGER 06.11.2014 07:12:25
5460 (0x1554)
Exiting package processing thread. SMS_DISTRIBUTION_MANAGER
06.11.2014 07:12:25 5460 (0x1554)
Used 4 out of 5 allowed processing threads.
SMS_DISTRIBUTION_MANAGER 06.11.2014 07:12:26
3300 (0x0CE4)
Starting package processing thread, thread ID = 0x894 (2196)
SMS_DISTRIBUTION_MANAGER 06.11.2014 07:12:27
3300 (0x0CE4)
Used all 5 allowed processing threads, won't process any more packages.
SMS_DISTRIBUTION_MANAGER 06.11.2014 07:12:27
3300 (0x0CE4)
Sleep 1828 seconds... SMS_DISTRIBUTION_MANAGER
06.11.2014 07:12:27 3300 (0x0CE4)
STATMSG: ID=2300 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=SCHVSGGSC600.rccad.net SITE=RC0 PID=2144 TID=2196 GMTDATE=jeu. nov. 06 06:12:27.716 2014 ISTR0="SUP-2014.M05" ISTR1="RC00011D" ISTR2=""
ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=1 AID0=400 AVAL0="RC00011D"
SMS_DISTRIBUTION_MANAGER 06.11.2014 07:12:27
2196 (0x0894)
Start updating the package RC00011D... SMS_DISTRIBUTION_MANAGER
06.11.2014 07:12:27 2196 (0x0894)
CDistributionSrcSQL::UpdateAvailableVersion PackageID=RC00011D, Version=14, Status=2300
SMS_DISTRIBUTION_MANAGER 06.11.2014 07:12:27
2196 (0x0894)
*** [40001][1205][Microsoft][SQL Server Native Client 11.0][SQL Server]Transaction (Process ID 154) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. Rerun the transaction.
SMS_DISTRIBUTION_MANAGER 06.11.2014 07:12:27
1424 (0x0590)
Taking package snapshot for package RC00011D
SMS_DISTRIBUTION_MANAGER 06.11.2014 07:12:27
2196 (0x0894)
Now as I mentioned it was probably an SQL (more likely) or networ issue, however the question was more about how to avoid that. Finally the packages were not changed and if possible I would avoid any automatic SCCM action on packages unless an operator manually
triggers them.
I didn't see any error today, so it should not be a configuration issue.
Is this possible?

Similar Messages

Distribution manager failed to process package - the source directory does not exist

Hi,
I have the following behaviour:
A Software Update Deployment Package is not distributing because of the following error:
I have found the following query (http://blogs.technet.com/b/ken_brumfield/archive/2013/01/10/troubleshooting-sccm-software-update-deployment-package-distribution-due-to-missing-directories.aspx) to
determine which update is missing.
It is about update KB978601. If we search this update in the console, we see this:
The update is not required, not downloaded, not deployed and superseeded.
If we look into the members of the Update deployment package, we can't find this update.
When I was digging into the database, I found this:
SELECT
distinct cp.Content_ID,
cp.ContentSubFolder,cp.PkgID,
con.ContentProvisioned
FROM
[dbo].[vCI_ContentPackages] cp
INNER
JOIN [dbo].[CI_ConfigurationItemContents]cic
ON cp.Content_ID
= cic.Content_ID
inner
join dbo.v_CIContents_All
con on con.Content_ID
= cp.Content_ID
where cp.PkgID
=
'XXX002BA'
and cp.ContentSubFolder
=
'39b46f0a-7244-48a6-b795-119ac74009f9'
which resulted in:
Content_ID ContentSubFolder PkgID ContentProvisioned
16828355 39b46f0a-7244-48a6-b795-119ac74009f9 BP1002BA 1
I found the "ContentProvisioned = 1 " a little bit strange.
So, my question is:
Why SCCM is thinking of distributing the content although it is not downloaded or deployed and how can we fix this?
Has it something todo with the "ContentProvisioned" or is it something else?
Thanks,
Sem

I can tell you why CM wants to distribute it, but the easiest way would be downloading that patch thus adding it to the package (so that it can be distributed) and remove it afterwards.
Torsten Meringer | http://www.mssccmfaq.de

Distribution manager failed to create the defined share or folder on distribution point and failed to connect to remote distribution point

We have recently upgraded remote distribution point to SCCM 2012 R2 CU4. when i try to distribute the package getting the error on the distribution point configuration status "Distribution manager failed to create the defined share or folder on distribution
point and failed to connect to remote distribution point"
Errors on the package transfer log file.
CWmi::Connect() could not connect to \\XXXXXXXX.COM\root\SCCMDP. error = The operation completed successfully.. Will try FQDN
CWmi::Connect() failed to connect to \\XXXXXXX.COM\root\SCCMDP. error = The RPC server is unavailable.
Failed to connect to the DP WMI namespace on the remote DP

Thanks Sandys for your suggestions.
i have tried wbemtest from site server(Secondary site) and remote DP server. Receiving the "The RPC
server is unavailable" from both ends.
error:0x800706ba - The RPC server is unavailable

Distribution Manager Failed To Access The Source Directory

Hello All,
I have this issue distributing content to my Distribution Points for months now. I keep running into this error below:
Distribution Manager Failed to Access the source directory (\\share\folder\file.wim)
Possible Cause: Distribution Manager does not have sufficient rights to the source directory.
Solution: Verify that the site server computer account has at least Read access to the directory you specify as the source directory.
Possible Cause: There is not enough disk space available on the site server.
Solution: Verify that there is enough free disk space available on the site server.
I checked the distmgr.log file and received these messages:
GetTempFileNameA failed; 0x80004005   SMS_DISTRIBUTION_MANAGER   3/24/2015 2:15:38 PM   13952 (0x3680)
CFileLibrary::AddFile failed; 0x80004005   SMS_DISTRIBUTION_MANAGER   3/24/2015 2:15:38 PM   13952 (0x3680)
CContentDefinition::AddFile failed; 0x80004005   SMS_DISTRIBUTION_MANAGER   3/24/2015 2:15:38 PM   13952 (0x3680)
Failed to add the file. Please check if this file exists.   SMS_DISTRIBUTION_MANAGER   3/24/2015 2:15:38 PM   13952 (0x3680)
SnapshotPackage() failed. Error = 0x80004005   SMS_DISTRIBUTION_MANAGER   3/24/2015 2:15:38 PM   13952 (0x3680)
Failed to take snapshot of package CSU0006A   SMS_DISTRIBUTION_MANAGER   3/24/2015 2:15:38 PM   13952 (0x3680)
There is enough space on the site server and the site server has full control over the source directory. I wish I can give you more information but I'm hoping this is enough info to get some assistance. If more information is needed please let me know!

We usually give the DP's computer account and the site server computer account read access to these shares in our environment.
... which is not enough for drivers and updates (as there will also files be added).
Torsten Meringer | http://www.mssccmfaq.de
... And for capture Image too if your capture destination points on that share

SCCM 2012 SP1 Distribution Manager Failed

I am getting the error below when I send the package to the Distribution point:
" Distribution Manager failed to find or create the defined share or volume on distribution point"

Hi,
Please check Distmgr.log to find the problem.
The blog that Paul provided seems to be helpful.
Best Regards,
Joyce Li
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

SMS_DISCOVERY_DATA_MANAGER Message ID 2636 and 620. Discovery Data Manager failed to process the discovery data record (DDR)

Hi
I'm seeing this critical error on my primary.
SMS_DISCOVERY_DATA_MANAGER Message ID 2636 and 620.
Discovery data manager failed to process the discovery data record (DDR)"D:\Prog.....\inboxes\auth\ddm.box\userddrsonly\adu650dh.DDR", because it cannot update the data source.
Where these ddr's are actually under ddm.box\userddrsonly\BAD_DDRS folder
I see a ton of DDR files in that folder. Not sure if I can delete them, so I moved them to a temp folder. AD User discovery keeps generating them.
Any help ?
Thanks
UK

Check the ddm.log file for more information.
My Blog: http://www.petervanderwoude.nl/
Follow me on twitter: pvanderwoude

Distribution manager failed to connect to the distribution point

After upgrading my distribution point to windows server 2012 standard I can't distribute content to my distribution point.
I see the following error.
source: SMS Server
Component: SMS_DISTRIBUTION_MANAGER
message id 2391
Distribution Manager failed to connect to the distribution point Check your network and firewall settings.
The firewall is not enabled.
wbemtest is able to connect to the remote server that has the distribution point role installed.
The network access account is working.
How do I fix this?

but why does it most of the time work? I did inplace upgrade at least 6 times from 2008 R2 to 2012 R2 and every DP except one works fine.
I'm not completely sure, but I think, my faulty one, that I'm trying to get working, was working correctly after the inplace upgrade. But as I said, that is only a theory, I'm just curious if that's possible.
I have the same issue as described above.
The IT guys from LukOIL

SCCM Distribution Manager Failed to access source directory...

Hi guys....
Im in a desperate position at the moment. I joined a small company a short while ago as an infrastructure engineer but have never had hands on experience with sccm 2012. The guy I was working with left
at short notice and never had time to show me the system.
I am now trying to image some new systems but for some reason I keep getting the above error message. I have checked share and NTFS permissions and ensured that all the SMS accounts have a minimum of modify
if not full rights including the local administrator account. The drives also have sufficient disk space. I am finding it impossible to update the distribution point (even though the wizards says successful).
Each time i try to run the task from the client I get Failed to run Task sequence, "This task sequence cannot be run because the program files for DI100005 cannot be located on a distribution point."
I have also ensured that Site system installation account is set to
Use the site server's computer account to install the site system
Please can someone point me in the right direction and help me to resolve this issue.
Many Thanks

Hi Torsten,
I have checked the log but not really sure what i am looking for. It tells me that a task has filed but not sure why? Is SMS_Distribution _Manager a generic name used for whatever account its supposed to be using?
Here is a snippet of the log from this morning. If you could please decypher it for me I would be very grateful.
---------Log Start ----------
Found package properties updated notification for package 'DI100005' $$<SMS_DISTRIBUTION_MANAGER><08-26-2014 09:18:01.967-60><thread=7128 (0x1BD8)>
Found notification for package 'DI100005' $$<SMS_DISTRIBUTION_MANAGER><08-26-2014 09:18:06.969-60><thread=7128 (0x1BD8)>
~Used 0 out of 3 allowed processing threads. $$<SMS_DISTRIBUTION_MANAGER><08-26-2014 09:18:07.032-60><thread=7128 (0x1BD8)>
~Starting package processing thread, thread ID = 0xCC0 (3264) $$<SMS_DISTRIBUTION_MANAGER><08-26-2014 09:18:07.550-60><thread=7128 (0x1BD8)>
~Sleep 3600 seconds... $$<SMS_DISTRIBUTION_MANAGER><08-26-2014 09:18:07.552-60><thread=7128 (0x1BD8)>
STATMSG: ID=2300 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=DI-WSUS-SRV.di.local SITE=DI1 PID=916 TID=3264 GMTDATE=Tue Aug 26 08:18:07.720 2014 ISTR0="Boot image (x64)" ISTR1="DI100005" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7=""
ISTR8="" ISTR9="" NUMATTRS=1 AID0=400 AVAL0="DI100005" $$<SMS_DISTRIBUTION_MANAGER><08-26-2014 09:18:07.720-60><thread=3264 (0xCC0)>
Start updating the package DI100005... $$<SMS_DISTRIBUTION_MANAGER><08-26-2014 09:18:07.721-60><thread=3264 (0xCC0)>
~CDistributionSrcSQL::UpdateAvailableVersion PackageID=DI100005, Version=14, Status=2300 $$<SMS_DISTRIBUTION_MANAGER><08-26-2014 09:18:07.728-60><thread=3264 (0xCC0)>
Taking package snapshot for package DI100005 from source \\DI-WSUS-SRV.di.local\SMS_DI1\OSD\boot\x64\boot.DI100005.wim $$<SMS_DISTRIBUTION_MANAGER><08-26-2014 09:18:08.115-60><thread=3264 (0xCC0)>
~Share folder \\DI-WSUS-SRV.di.local\D$\SCCMContentLib does not exist or is not accessible. Error code = 67 $$<SMS_DISTRIBUTION_MANAGER><08-26-2014 09:18:08.120-60><thread=3264 (0xCC0)>
~Cannot create \\DI-WSUS-SRV.di.local\D$\SCCMContentLib, [error code: 67, error message: The network name cannot be found.]. $$<SMS_DISTRIBUTION_MANAGER><08-26-2014 09:18:08.189-60><thread=3264 (0xCC0)>
~Cannot create the content library storage directory \\DI-WSUS-SRV.di.local\D$\SCCMContentLib, use the default directory. $$<SMS_DISTRIBUTION_MANAGER><08-26-2014 09:18:08.190-60><thread=3264 (0xCC0)>
~Share folder \\DI-WSUS-SRV.di.local\D$\SCCMContentLib does not exist or is not accessible. Error code = 67 $$<SMS_DISTRIBUTION_MANAGER><08-26-2014 09:18:08.191-60><thread=3264 (0xCC0)>
Failed to get the content library path. $$<SMS_DISTRIBUTION_MANAGER><08-26-2014 09:18:08.200-60><thread=3264 (0xCC0)>
SnapshotPackage() failed. Error = 0x80004005 $$<SMS_DISTRIBUTION_MANAGER><08-26-2014 09:18:08.200-60><thread=3264 (0xCC0)>
STATMSG: ID=2361 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=DI-WSUS-SRV.di.local SITE=DI1 PID=916 TID=3264 GMTDATE=Tue Aug 26 08:18:08.201 2014 ISTR0="\\DI-WSUS-SRV.di.local\SMS_DI1\OSD\boot\x64\boot.DI100005.wim" ISTR1="Boot image
(x64)" ISTR2="DI100005" ISTR3="30" ISTR4="100" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=1 AID0=400 AVAL0="DI100005" $$<SMS_DISTRIBUTION_MANAGER><08-26-2014 09:18:08.201-60><thread=3264 (0xCC0)>
~CDistributionSrcSQL::UpdateAvailableVersion PackageID=DI100005, Version=13, Status=2302 $$<SMS_DISTRIBUTION_MANAGER><08-26-2014 09:18:08.201-60><thread=3264 (0xCC0)>
STATMSG: ID=2302 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=DI-WSUS-SRV.di.local SITE=DI1 PID=916 TID=3264 GMTDATE=Tue Aug 26 08:18:08.363 2014 ISTR0="Boot image (x64)" ISTR1="DI100005" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7=""
ISTR8="" ISTR9="" NUMATTRS=1 AID0=400 AVAL0="DI100005" $$<SMS_DISTRIBUTION_MANAGER><08-26-2014 09:18:08.363-60><thread=3264 (0xCC0)>
~Failed to process package DI100005 after 0 retries, will retry 100 more times $$<SMS_DISTRIBUTION_MANAGER><08-26-2014 09:18:08.364-60><thread=3264 (0xCC0)>
~Exiting package processing thread. $$<SMS_DISTRIBUTION_MANAGER><08-26-2014 09:18:08.381-60><thread=3264 (0xCC0)>
Sleep 30 minutes... $$<SMS_DISTRIBUTION_MANAGER><08-26-2014 09:18:12.018-60><thread=8392 (0x20C8)>
~Used 0 out of 3 allowed processing threads. $$<SMS_DISTRIBUTION_MANAGER><08-26-2014 09:18:12.566-60><thread=7128 (0x1BD8)>
~Sleep 1826 seconds... $$<SMS_DISTRIBUTION_MANAGER><08-26-2014 09:18:12.591-60><thread=7128 (0x1BD8)>
~Used 0 out of 3 allowed processing threads. $$<SMS_DISTRIBUTION_MANAGER><08-26-2014 09:18:17.611-60><thread=7128 (0x1BD8)>
~Sleep 1821 seconds... $$<SMS_DISTRIBUTION_MANAGER><08-26-2014 09:18:17.621-60><thread=7128 (0x1BD8)>
Sleep 30 minutes... $$<SMS_DISTRIBUTION_MANAGER><08-26-2014 09:38:42.490-60><thread=8392 (0x20C8)>
Found package properties updated notification for package 'DI100004' $$<SMS_DISTRIBUTION_MANAGER><08-26-2014 09:38:47.491-60><thread=7128 (0x1BD8)>
Found notification for package 'DI100004' $$<SMS_DISTRIBUTION_MANAGER><08-26-2014 09:38:53.425-60><thread=7128 (0x1BD8)>
~Used 0 out of 3 allowed processing threads. $$<SMS_DISTRIBUTION_MANAGER><08-26-2014 09:38:53.450-60><thread=7128 (0x1BD8)>
~Starting package processing thread, thread ID = 0xE0C (3596) $$<SMS_DISTRIBUTION_MANAGER><08-26-2014 09:38:53.950-60><thread=7128 (0x1BD8)>
~Sleep 585 seconds... $$<SMS_DISTRIBUTION_MANAGER><08-26-2014 09:38:53.952-60><thread=7128 (0x1BD8)>
STATMSG: ID=2300 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=DI-WSUS-SRV.di.local SITE=DI1 PID=916 TID=3596 GMTDATE=Tue Aug 26 08:38:54.072 2014 ISTR0="Boot image (x86)" ISTR1="DI100004" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7=""
ISTR8="" ISTR9="" NUMATTRS=1 AID0=400 AVAL0="DI100004" $$<SMS_DISTRIBUTION_MANAGER><08-26-2014 09:38:54.072-60><thread=3596 (0xE0C)>
Start updating the package DI100004... $$<SMS_DISTRIBUTION_MANAGER><08-26-2014 09:38:54.073-60><thread=3596 (0xE0C)>
~CDistributionSrcSQL::UpdateAvailableVersion PackageID=DI100004, Version=5, Status=2300 $$<SMS_DISTRIBUTION_MANAGER><08-26-2014 09:38:54.074-60><thread=3596 (0xE0C)>
Taking package snapshot for package DI100004 from source \\DI-WSUS-SRV.di.local\SMS_DI1\osd\boot\i386\boot.DI100004.wim $$<SMS_DISTRIBUTION_MANAGER><08-26-2014 09:38:54.104-60><thread=3596 (0xE0C)>
~Share folder \\DI-WSUS-SRV.di.local\D$\SCCMContentLib does not exist or is not accessible. Error code = 67 $$<SMS_DISTRIBUTION_MANAGER><08-26-2014 09:38:54.108-60><thread=3596 (0xE0C)>
~Cannot create \\DI-WSUS-SRV.di.local\D$\SCCMContentLib, [error code: 67, error message: The network name cannot be found.]. $$<SMS_DISTRIBUTION_MANAGER><08-26-2014 09:38:54.120-60><thread=3596 (0xE0C)>
~Cannot create the content library storage directory \\DI-WSUS-SRV.di.local\D$\SCCMContentLib, use the default directory. $$<SMS_DISTRIBUTION_MANAGER><08-26-2014 09:38:54.120-60><thread=3596 (0xE0C)>
~Share folder \\DI-WSUS-SRV.di.local\D$\SCCMContentLib does not exist or is not accessible. Error code = 67 $$<SMS_DISTRIBUTION_MANAGER><08-26-2014 09:38:54.122-60><thread=3596 (0xE0C)>
Failed to get the content library path. $$<SMS_DISTRIBUTION_MANAGER><08-26-2014 09:38:54.131-60><thread=3596 (0xE0C)>
SnapshotPackage() failed. Error = 0x80004005 $$<SMS_DISTRIBUTION_MANAGER><08-26-2014 09:38:54.131-60><thread=3596 (0xE0C)>
STATMSG: ID=2361 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=DI-WSUS-SRV.di.local SITE=DI1 PID=916 TID=3596 GMTDATE=Tue Aug 26 08:38:54.131 2014 ISTR0="\\DI-WSUS-SRV.di.local\SMS_DI1\osd\boot\i386\boot.DI100004.wim" ISTR1="Boot image
(x86)" ISTR2="DI100004" ISTR3="30" ISTR4="100" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=1 AID0=400 AVAL0="DI100004" $$<SMS_DISTRIBUTION_MANAGER><08-26-2014 09:38:54.131-60><thread=3596 (0xE0C)>
~CDistributionSrcSQL::UpdateAvailableVersion PackageID=DI100004, Version=4, Status=2302 $$<SMS_DISTRIBUTION_MANAGER><08-26-2014 09:38:54.132-60><thread=3596 (0xE0C)>
STATMSG: ID=2302 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=DI-WSUS-SRV.di.local SITE=DI1 PID=916 TID=3596 GMTDATE=Tue Aug 26 08:38:54.221 2014 ISTR0="Boot image (x86)" ISTR1="DI100004" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7=""
ISTR8="" ISTR9="" NUMATTRS=1 AID0=400 AVAL0="DI100004" $$<SMS_DISTRIBUTION_MANAGER><08-26-2014 09:38:54.221-60><thread=3596 (0xE0C)>
~Failed to process package DI100004 after 0 retries, will retry 100 more times $$<SMS_DISTRIBUTION_MANAGER><08-26-2014 09:38:54.222-60><thread=3596 (0xE0C)>
~Exiting package processing thread. $$<SMS_DISTRIBUTION_MANAGER><08-26-2014 09:38:54.222-60><thread=3596 (0xE0C)>
Sleep 30 minutes... $$<SMS_DISTRIBUTION_MANAGER><08-26-2014 09:38:58.439-60><thread=8392 (0x20C8)>
~Used 0 out of 3 allowed processing threads. $$<SMS_DISTRIBUTION_MANAGER><08-26-2014 09:38:58.965-60><thread=7128 (0x1BD8)>
~Sleep 580 seconds... $$<SMS_DISTRIBUTION_MANAGER><08-26-2014 09:38:58.966-60><thread=7128 (0x1BD8)>
~Used 0 out of 3 allowed processing threads. $$<SMS_DISTRIBUTION_MANAGER><08-26-2014 09:39:03.979-60><thread=7128 (0x1BD8)>
~Sleep 575 seconds... $$<SMS_DISTRIBUTION_MANAGER><08-26-2014 09:39:03.980-60><thread=7128 (0x1BD8)>
Sleeping for 60 minutes before content cleanup task starts.~ $$<SMS_DISTRIBUTION_MANAGER><08-26-2014 09:42:35.263-60><thread=3480 (0xD98)>
---------Log Finish ----------
Cheers,
Aaron

SSIS package fails when Configuration value has value saved into the package

when a package is migrated from dev to QA and to PROD sometimes it fails since the variables have values in them saved into the package.
what we do is clear these values manually and restart the job.
Is there a way we can clear the variables when saving the package or at least programmatically?
eddy.a

Hello Arthur
Thank you for your response. I should start by apologizing by not making myself clear. We do use indirect configuration that work cross environments however this is the issue that we have:
when the package is first created say you create a DB Variable called A and you enter value A in the variable to test the package. After the package development is tested, you change the configuration values to fetch data whether from an excel file or from
an XML.
when you run on environment A the package runs fine however when you move over to environment B it seems that first it validates against A then overwrites B - if environment A is not there anymore the package sometimes fails.
we are changing these manually for now but I was wondering if there's a way to prevent it.
thanks
eddy.a

Prestage package status not updating on the server

I have been successful in extracting other prestage packages on DP but for 2 packages, it extract them fine as per the logs and sends the status to the MP as well but the server doesnt reflect the updated status.
prestagecontent.log shows the following
Management Point: 'http://<MP Name>'
Site Code: '<Sitecode>' PrestageContent
DP server: '<DP server name>'
NAL Path: ["Display=\\<DP server name>\"]MSWNET:["SMS_SITE=<sitecode>"]\\<DP server name>\'                PrestageContent
Set authenticator in transport    PrestageContent
Sent <packageID> package state message to site
End ====
What could be the reason, i have tried to recopy the packages from the original source and tried extracting 2-3 times
using the extraction switch "/f" as well but didnt reflect the status.
Prestage option is already checked.

Distmgr.log has the below entries although they were not in red
Will reject STA for DP ["Display=\\DP server name\"]MSWNET:["SMS_SITE=SITE CODE"]\\DP server name\ as it does not exist in the PkgServers table       SMS_DISTRIBUTION_MANAGER
7/4/2014 10:07:50 AM    6180 (0x1824)
Will not process this invalid package status file from remote DP ["Display=\\DP server name\"]MSWNET:["SMS_SITE=SITE CODE"]\\DP server name\, delete C:\Program Files\Microsoft Configuration Manager\inboxes\distmgr.box\INCOMING\EAKYPGEC.STA
SMS_DISTRIBUTION_MANAGER              7/4/2014 10:07:50 AM         6180 (0x1824)
STATMSG: ID=2354 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=Primary server name SITE=SITE CODE PID=7420 TID=6180 GMTDATE=Fri Jul 04 04:37:50.055 2014 ISTR0="C:\Program Files\Microsoft Configuration Manager\inboxes\distmgr.box\INCOMING\EAKYPGEC.STA"
ISTR1="["Display=\\DP server name\"]MSWNET:["SMS_SITE=SITE CODE"]\\DP server name\" ISTR2="SITE CODE001C5" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=2 AID0=400 AVAL0="SITE CODE001C5" AID1=404 AVAL1="["Display=\\DP server name\"]MSWNET:["SMS_SITE=SITE
CODE"]\\DP server name\" SMS_DISTRIBUTION_MANAGER              7/4/2014 10:07:50 AM       6180 (0x1824)
Successfully delete package status file C:\Program Files\Microsoft Configuration Manager\inboxes\distmgr.box\INCOMING\EAKYPGEC.STA        SMS_DISTRIBUTION_MANAGER
7/4/2014 10:07:50 AM         6180 (0x1824)
There are no entries in pkgxfermgr.log

How to deploy SSIS packages and jobs that run the package?

I am fairly new to deploying SSIS packages. We are migrating servers and I need to deploy the packages to the new dev and prod servers. Can you please walk me through this? Also is there a configuration through which we can specify connection strings so
that it is not dependent on a particular environment?
Anonymous

Hi Devcoder,
As Visakh16 suggested above, we can use deployment utility to deploy SSIS packages to production server. Here are some good articles regarding this topi for your reference, please see:
Deploying SSIS Packages on to Production Server:
http://sqlbiblog.blogspot.com/2011/02/deploying-ssis-packages-on-to.html
Package Deployment (SSIS):
http://msdn.microsoft.com/en-us/library/ms137592.aspx
If you have any feedback on our support, please click
here.
Elvis Long
TechNet Community Support

Download Manager fails to close after Flash Player update

I recently updated my Flash Player to 10.1. The Adobe Download Manager screen indicates 100% installation, but the screen doesn't close. When I go to close the Download Manager screen, it indicates that an installation is still in progress. I have validated that Flash Player has successfully installed on the Adobe site and it appears to work fine with links in emails that require Flash Player, but I think that my computer has not fully acknowledged a successful and complete installation because my HP wireless printer Solution Center program is not accessible on my computer. I had this program disappear several months ago and it was due to my needing to update Flash Player to the previous updated version. I suspect I'm experiencing the same problem again.
I have an IBM ThinkPad tablet PC, running Windows XP 32 bit. I typically use IE 8 (although I also have FireFox on my machine). I have tried uninstalling Flash Player and Adobe Download Manager through my Control Panel and that doesn't seem to fix the situation. Any ideas? (I would really like to get my Solution Center software back up and working so I can go back to using my scanner.)

The Adobe download manager seems to cause all sorts of problems, so I never use it. I usually download executable installers from http://www.adobe.com/products/flashplayer/fp_distribution3.html
There have been other topics in this forum regarding HP solution center recently; try a forum search on HP +solution +center

How to compile package which contain class outside the package

I am writing a JDBC driver.
I have the following package structure in the folder:
MyDriver
    |_manager.jar
    |_com
           |_ jdbc
                   |_ HXDriver
                   |_ HXConnection
                   |_ HXResultSet
                   |_ HXStatementIn manager.jar, there is a remote object Interaface(Manager.java) which I need to use inside HXConnection.
My question is how to compile(or/and how to set the classpath)so that I can compile the 4 classes inside jdbc package.
I tried this:
C:\MyDriver>javac -cp .;manager.jar com/hx/jdbc/*.java
However, this does not work, compiler says it cannot find Manager
Please help me.
Cheers

D:\380 Project\Driver>javac -cp .;manager.jar com\hx\jdbc\*.java
com\hx\jdbc\HXConnection.java:21: cannot find symbol
symbol : class Manager
location: class com.hx.jdbc.HXConnection
        private Manager manager;
                ^
com\hx\jdbc\HXStatement.java:18: cannot find symbol
symbol : class Manager
location: class com.hx.jdbc.HXStatement
        private Manager manager;
                ^
com\hx\jdbc\HXStatement.java:20: cannot find symbol
symbol : class Manager
location: class com.hx.jdbc.HXStatement
        public HXStatement(Manager manager){
                           ^
com\hx\jdbc\HXConnection.java:41: cannot find symbol
symbol : class Manager
location: class com.hx.jdbc.HXConnection
                        manager = (Manager)reg.lookup("manager");
                                   ^

How to schedule Process Chain with Full Update for the past closed month

Hello,
I have an HR-BN benefits transactional data extractor - http://help.sap.com/saphelp_nw70/helpdata/en/08/b01d3cf8aa101ce10000000a11405a/frameset.htm
One of the selection fields for that extractor is calendar year/month 0CALMONTH and it is a full update extractor.
SAP recommends running this extractor once a month after the month has been closed.
If I were to include this update/extract into my process chain, would it be possible to automate the process in a way where the process chain is scheduled to execute once a month (I know how to do that), but that also only pulls values for the past/closed CALMONTH (as if it had a variable value of which would be automatically set to the last closed month when pchain is run)? As I mentioned 0CALMONTH is one of the selection criterias in the infopackage for that extractor.
let me know how I might be able to do that.
P.S. we are on BI 7.0/2004s
Thank you

For Calmonth selection in infopackage you can use the SAP-Exit OLAP Variable 0CMLMON (Last Month)
select Type "7" ("OLAP Variable")
and in Details of Type screen, Select OLAP Variable "0CMLMON" Which is SAP-Exit variable for Calmonth, that returns the last month from the current system-date.
If variable 0CMLMON is not active, you need to activate it from Business content.
Assign pts if helpful.

How to Access a class outside a package which is friendly to the package

Hi All,
i hav a class which has friendly scope in package X. how do i access it from a class in package Y without declaring it as public.
Rgds,

Hmm. If it is friendly in X, you can access it only from X. There is no way you can access it from Y.

Distribution Manager failed to process package triggers an update of the packages

Similar Messages

Maybe you are looking for