[Last Call] Learn how to a build a cloud-first strategyRegister Now

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 3542
  • Last Modified:

Unable to run advertised programs from SCCM 2007

I am unable to run advertised programs from SCCM 2007.  I create a package and advertise it to a collection.  The client receives the advertised package.  When I attempt to run the package, I receive the following error:

The requested software cannot be located.  The system might be in the process of transferring these files.  Try again later, or if this operation continues to fail after several attempts, please contact your administrator or helpdesk operator.

I have one SCCM server that holds all the roles including Distribution Point.  On the client, I can manually navigate to \\servername\smspkgd$\HQ10008 and run the application.  

The files are located on the D:\ drive of the server.  I have set the Location of Stored Packages to D:\ in Site Setting --> Component Configuration.  I have also created a Boundary based on my Active Directory Site the the client is in.  

Any Ideas?

Here is my CAS.log
<![LOG[Requesting content HQ100008.1, size(KB) 12885, under context S-1-5-21-35927030-1161448165-1566916341-42942 with priority Low]LOG]!><time="08:42:37.046+420" date="04-22-2009" component="ContentAccess" context="" type="1" thread="192" file="contentaccessservice.cpp:573">
<![LOG[Created and Sent Location Request '{5E46F3BA-33D9-4AAB-A25F-B6D53D659034}' for package HQ100008]LOG]!><time="08:42:37.218+420" date="04-22-2009" component="ContentAccess" context="" type="1" thread="192" file="ccmpkglocation.cpp:69">
<![LOG[LS job {5E46F3BA-33D9-4AAB-A25F-B6D53D659034} submitted to get DP locations for content HQ100008.1]LOG]!><time="08:42:37.218+420" date="04-22-2009" component="ContentAccess" context="" type="1" thread="192" file="locationcontentrequest.cpp:509">
<![LOG[Successfully created location request {7DB8164D-09C0-4FB6-B32A-0703B46F470E} for content HQ100008.1]LOG]!><time="08:42:37.234+420" date="04-22-2009" component="ContentAccess" context="" type="1" thread="192" file="locationcontentrequest.cpp:527">
<![LOG[Releasing content request {7DB8164D-09C0-4FB6-B32A-0703B46F470E}]LOG]!><time="08:44:37.578+420" date="04-22-2009" component="ContentAccess" context="" type="1" thread="192" file="contentaccessservice.cpp:1197">
<![LOG[Canceling LS Job {5E46F3BA-33D9-4AAB-A25F-B6D53D659034} for content HQ100008.1]LOG]!><time="08:44:37.578+420" date="04-22-2009" component="ContentAccess" context="" type="1" thread="192" file="locationcontentrequest.cpp:544">

0
cybersean
Asked:
cybersean
1 Solution
 
cyberseanAuthor Commented:
We previously had SMS 2003 installed in our environment.  We didn't upgrade to SCCM 2007.  We just removed SMS 2003 and installed SCCM 2007 on a new machine.  This led to the Management Point (configured in ADUC --> System --> Systems Management) pointing to the old SMS 2003 server.  Once we removed those items and only had the correct setting in AD, it worked fine.
0

Featured Post

Get quick recovery of individual SharePoint items

Free tool – Veeam Explorer for Microsoft SharePoint, enables fast, easy restores of SharePoint sites, documents, libraries and lists — all with no agents to manage and no additional licenses to buy.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now