Solved

Advertised apps fail to run. Takes forever to show up in advertised programs.

Posted on 2010-11-17
30
5,473 Views
Last Modified: 2013-11-21
I have seen similar questions but not exactly the same as mine so forgive me if there is some redundancy here. We installed SCCM 2007 SP2 last spring and have never been able to use it other than some reporting. I have recently attempted to push out a small app to see if I could make it work in preparation for deploying Office 2010 with SCCM. I have followed all the steps for deploying an app checked and rechecked to make sure I did it right but end up with the same results. That is, the advertised app takes forever to show up but eventually does in the run advertised programs location on my xp pro PC. I can see the program in the default cache location but it fails to run. I know it is trying to do something as I get notified every 5 min that I have a program that is ready to install. The status shows that it failed the last time it tried to run and the details say

" 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 was not the one who installed SCCM and that person is gone. I know that that person burned a ticket with microsoft in the spring to get it working right but apparently there is still something we missed. I really want to use this tool but need some help. If someone can tell me what log to post that would shed light I will happily oblige. I can't help but think that there is a rights issue here or just something we missed in the configuration. And why does it take so stinking long to find out that it fails? The test app i am deploying is so small and simple.
0
Comment
Question by:Benlife
  • 16
  • 14
30 Comments
 
LVL 10

Expert Comment

by:Kezzi
ID: 34156557
Have a look at your Computer Client Agent settings under the Site Setting Client Agent for interval timing.

Also look in the C:\Windows\system32\ccm\logs folder for errors in the log files.  look in execmgr.log first.  that should help point to something.

also what are the properties of your advertisement just to give us some idea of the type of program you are running and how its set to run.
0
 

Author Comment

by:Benlife
ID: 34158465
Changed the policy polling interval from 60 to 10.

Here is a portion of the execmgr.log file

BFG0001D]LOG]!><time="08:07:00.011+420" date="11-12-2010" component="execmgr" context="" type="1" thread="16864" file="execreqmgr.cpp:3440">
<![LOG[A duplicate execution request is found for program Lifepro Display]LOG]!><time="08:07:00.042+420" date="11-12-2010" component="execmgr" context="" type="1" thread="16864" file="execreqmgr.cpp:3609">
<![LOG[Mandatory execution requested for program Lifepro Display and advertisement BFG20022]LOG]!><time="08:09:00.006+420" date="11-12-2010" component="execmgr" context="" type="1" thread="17672" file="execreqmgr.cpp:3317">
<![LOG[Creating mandatory request for advert BFG20022, program Lifepro Display, package BFG0001D]LOG]!><time="08:09:00.006+420" date="11-12-2010" component="execmgr" context="" type="1" thread="17672" file="execreqmgr.cpp:3440">
<![LOG[A duplicate execution request is found for program Lifepro Display]LOG]!><time="08:09:00.053+420" date="11-12-2010" component="execmgr" context="" type="1" thread="17672" file="execreqmgr.cpp:3609">
<![LOG[Mandatory execution requested for program Lifepro Display and advertisement BFG20022]LOG]!><time="08:11:00.016+420" date="11-12-2010" component="execmgr" context="" type="1" thread="20016" file="execreqmgr.cpp:3317">
<![LOG[Creating mandatory request for advert BFG20022, program Lifepro Display, package BFG0001D]LOG]!><time="08:11:00.016+420" date="11-12-2010" component="execmgr" context="" type="1" thread="20016" file="execreqmgr.cpp:3440">
<![LOG[A duplicate execution request is found for program Lifepro Display]LOG]!><time="08:11:00.047+420" date="11-12-2010" component="execmgr" context="" type="1" thread="20016" file="execreqmgr.cpp:3609">
<![LOG[Mandatory execution requested for program Lifepro Display and advertisement BFG20022]LOG]!><time="08:13:00.050+420" date="11-12-2010" component="execmgr" context="" type="1" thread="20288" file="execreqmgr.cpp:3317">

Here are screen shots of the properties page for the advertisement I am trying to deploy.
General.jpg
Schedule.jpg
Distribution-Point.jpg
Interaction.jpg
Security.jpg
0
 
LVL 10

Expert Comment

by:Kezzi
ID: 34158886
is that log from the client or the server?  can you post the whole log from the client which would trap the error it gets when trying to run.
0
 

Author Comment

by:Benlife
ID: 34159108
That was from the client. Ok here is the whole enchilada. So there is another log file with a similar name that I will post as well. Not sure it has anything to do with what we are looking at.
execmgr.log
execmgr-20101111-195500.log
0
 
LVL 10

Expert Comment

by:Kezzi
ID: 34162948
Executing program lifepro1.exe in Admin context      execmgr      13/11/2010 23:40:16      7664 (0x1DF0)
Execution Manager timer has been fired.      execmgr      13/11/2010 23:40:16      1056 (0x0420)
Execution Request for package BFG0001D program Lifepro Display state change from Running to NotifyExecution      execmgr      13/11/2010 23:40:16      7664 (0x1DF0)
Checking content location C:\WINDOWS\system32\CCM\Cache\BFG0001D.2461.System for use      execmgr      13/11/2010 23:40:16      7664 (0x1DF0)
Successfully selected content location C:\WINDOWS\system32\CCM\Cache\BFG0001D.2461.System      execmgr      13/11/2010 23:40:16      7664 (0x1DF0)
GetFileVersionInfoSize failed for file C:\WINDOWS\system32\CCM\Cache\BFG0001D.2461.System\lifepro1.exe, error 1813      execmgr      13/11/2010 23:40:16      7664 (0x1DF0)
Executing program as a script      execmgr      13/11/2010 23:40:16      7664 (0x1DF0)
Successfully prepared command line "C:\WINDOWS\system32\CCM\Cache\BFG0001D.2461.System\lifepro1.exe"      execmgr      13/11/2010 23:40:16      7664 (0x1DF0)
Command line = "C:\WINDOWS\system32\CCM\Cache\BFG0001D.2461.System\lifepro1.exe", Working Directory = C:\WINDOWS\system32\CCM\Cache\BFG0001D.2461.System\      execmgr      13/11/2010 23:40:16      7664 (0x1DF0)
Created Process for the passed command line      execmgr      13/11/2010 23:40:16      7664 (0x1DF0)
Raising event:
[SMS_CodePage(437), SMS_LocaleID(1033)]
instance of SoftDistProgramStartedEvent
{
      AdvertisementId = "BFG20024";
      ClientID = "GUID:C42B48EA-23AA-426A-9E44-E410788E6CC7";
      CommandLine = "\"C:\\WINDOWS\\system32\\CCM\\Cache\\BFG0001D.2461.System\\lifepro1.exe\"";
      DateTime = "20101114064016.451000+000";
      MachineName = "S1376D";
      PackageName = "BFG0001D";
      ProcessID = 2748;
      ProgramName = "Lifepro Display";
      SiteCode = "BFG";
      ThreadID = 7664;
      UserContext = "NT AUTHORITY\\SYSTEM";
      WorkingDirectory = "C:\\WINDOWS\\system32\\CCM\\Cache\\BFG0001D.2461.System\\";
};
      execmgr      13/11/2010 23:40:16      7664 (0x1DF0)
Raised Program Started Event for Ad:BFG20024, Package:BFG0001D, Program: Lifepro Display      execmgr      13/11/2010 23:40:16      7664 (0x1DF0)
Execution Manager timer has been fired.      execmgr      13/11/2010 23:42:27      1056 (0x0420)
Policy is updated for Program: Lifepro Display, Package: BFG0001D, Advert: BFG20024      execmgr      14/11/2010 00:32:16      7664 (0x1DF0)
Policy is updated for Program: Lifepro Display, Package: BFG0001D, Advert: BFG20025      execmgr      14/11/2010 00:32:16      11100 (0x2B5C)
Policy is updated for Program: Lifepro Display, Package: BFG0001D, Advert: BFG20025      execmgr      14/11/2010 01:30:18      7664 (0x1DF0)
Policy is updated for Program: Lifepro Display, Package: BFG0001D, Advert: BFG20024      execmgr      14/11/2010 01:32:19      10532 (0x2924)
Program exit code 259      execmgr      14/11/2010 01:40:16      21788 (0x551C)
Looking for MIF file to get program status      execmgr      14/11/2010 01:40:16      21788 (0x551C)
Program ran past its maximum runtime. It will be orphaned      execmgr      14/11/2010 01:40:16      21788 (0x551C)
Raising event:
[SMS_CodePage(437), SMS_LocaleID(1033)]
instance of SoftDistProgramExceededTime
{
      AdvertisementId = "BFG20024";
      ClientID = "GUID:C42B48EA-23AA-426A-9E44-E410788E6CC7";
      DateTime = "20101114084016.175000+000";
      MachineName = "S1376D";
      MaximumTime = "120";
      PackageName = "BFG0001D";
      ProcessID = 2748;
      ProgramName = "Lifepro Display";
      SiteCode = "BFG";
      ThreadID = 21788;
};
      execmgr      14/11/2010 01:40:16      21788 (0x551C)
Raised Program Exceeded Time Event for Ad:BFG20024, Package:BFG0001D, Program: Lifepro Display      execmgr      14/11/2010 01:40:16      21788 (0x551C)
Execution is complete for program Lifepro Display. The exit code is 259, the execution status is Unknown Status      execmgr      14/11/2010 01:40:16      9896 (0x26A8)



OK the above lines of code tell me a few things.  
Firstly, the source version for this app is very high.   2461 updates to it?  Do you have the package properties set to update on a schedule?
Secondly, the program timed out as it ran past its execution time limit set on the program.  It seems like a very short time limit.  What do you have it set to on the program?
Lastly, the program exited with status code 259, which is the exit code being passed it from the application.  259 could mean that it spawned a process successfully but it doesnt mean the spawned processes completed successfully.  The fact that it seems to be spawning a process could mean that the program needs user interaction and times out as its waiting for that action.

A good test to make sure there is nothing wrong with SCCM deploying apps in general, is to create a package with a script program that just copies a text file or something on the C:\ drive.   If that works then you know its not SCCM failing, but rather the application not meeting the settings you have put on your program.

Try using this little script as a program to assess deployments.  
Create test.txt and add it to the source along with this .vbs
Command line for the program will be "cscript.exe testcopy.vbs"

testcopy.vbs
0
 

Author Comment

by:Benlife
ID: 34165083
I looked at the package properties but don't see where it is that you set the update interval. Isn't the 2461 number part of the file name in the client cache? The package execution time limit was set to 120 Minutes which seems ample for such a small app. Honestly, the only thing this app does is display a warning that another app (called lifepro) is not available. That is it. Some of the reports show that the client is waiting for content. So I looked in the cache on the PC and the executable file is there. If I click on it it runs.
What you said about the app may be true. I don't know. I have tried other apps with no sucess. I will try the test.txt you suggested and let you know. Thank you so much for your prompt replies. I am motivated to plow through this and get it working.
0
 
LVL 10

Accepted Solution

by:
Kezzi earned 500 total points
ID: 34165297
when you look at the package status, what source version does it show?  On the Data source tab of the package you'll see an update schedule area in the middle of the page.
I'm seeing this constantly in your log which shows the package is sending updates to the cache every few minutes.
Content version for program Lifepro Display package BFG0001D has been changed to 1290
Content version for program Lifepro Display package BFG0001D has been changed to 1363
Content version for program Lifepro Display package BFG0001D has been changed to 1410

I think that is whats causing the content waiting error you're seeing.  Just when its able to grab a handle of the content it gets a request to update it again.

it also appears you had 2 adverts for the same package:

Policy is updated for Program: Lifepro Display, Package: BFG0001D, Advert: BFG20025      execmgr      14/11/2010 14:32:50      12964 (0x32A4)
Policy is updated for Program: Lifepro Display, Package: BFG0001D, Advert: BFG20024      execmgr      14/11/2010 15:32:52      17936 (0x4610)

only at the end of the log do i see the policy for BFG20024 being deleted.  so that also may have been causing an issue.
0
 

Author Comment

by:Benlife
ID: 34165378
It was set to every 2 minutes. That makes sense what you said about the timimg. What is a good interval for updating distribution points? I think we thought that shorter interval would mean we wouldn't have to wait as long to see results. We ( i say we because I have involved a coworker to look at this with me) have been testing this so much that we probably have shot ourselves in the foot a few times trying different things. This may be the reason for multiple advertisments of same package. When testing, is it best to just use the rerun advertisment feature after making changes?
0
 
LVL 10

Assisted Solution

by:Kezzi
Kezzi earned 500 total points
ID: 34165472
I never set my packages to update distribution points.  I distribute them once, and only if there is an issue with them not distributing correctly or I have edited the content of the source, only then, do i right click distribution points node and select to update.   I'd say dont put a shedule on there at all.

for timing, what you want to be looking at is the Client Agent settings for the site.  This will determine the interval at which the client will communicate with the site to see if there are any available advertisements.  Once they download the advertisement they will start running it.    another thing i noticed about your advert schedule is that your available start time for the ad is the same as the schedule.  I prefer to make the available time slightly ahead of the schedule as this gives the client time to download the policy of the advert and import it so that it triggers at the schedule time.

If you want to try and force your clients to pick up adverts quicker, why not try this.

After creating a new advertisement, use one of the best extension tools around (3rd party tool that hooks into SCCM - http://myitforum.com/cs2/blogs/rhouchins/archive/2008/04/09/sccm-right-click-tools.aspx)  to right click your collection and select client actions, then machine policy refresh.   this will force the clients to refresh the policy without waiting for your client agent interval to trigger.
0
 
LVL 10

Expert Comment

by:Kezzi
ID: 34165840
sorry didnt answer your last question.   yes, if you want to rerun the advertisement again, set a new schedule and make sure its set to "rerun if previous failed".  If you select the rerun option, this will add a new schedule with the option set to "always rerun"
0
 
LVL 10

Assisted Solution

by:Kezzi
Kezzi earned 500 total points
ID: 34166236
oh if you use the right click tools, you can select to rerun the advertisement straight on the client without it needing to contact the site to find out its new schedule.  It reruns immediately and the only wait time will be if it needs to download a newer version of the source files from the distribution point.
0
 

Author Comment

by:Benlife
ID: 34168868
That sounds like a good idea. I am changing it to manual from here on out. So as I understand it. Updating the distribution point just pushes changes to the packages or adds new ones you just created or whatever. So once it is done once you shouldn't have to do it again until you have a new package or made a change to an exsisting one. Right?

Again. the timing of the schedule may have been messed up because we set it once and then didn't change it for subsequent trials. I will make the adjsutments you suggested.

I tried installing the third party tool you suggested. Does just add some right click options in the Config manager console? I don't see the "client actions" option you are refering to. I would like to use this if you can help. Sorry to have so many questions.
0
 

Author Comment

by:Benlife
ID: 34169218
I answered my own question. Found the rerun option. I am assuming that it is the third party tool because it has some Dell icon on fire in the upper left of the screen. Showed one succes and one failure. Not sure why. The success was on a windows 7 device the failure on xp. I have rerun it 3 times success 3 failure 3. So using that app fixed the delay.
0
 

Author Comment

by:Benlife
ID: 34175306
So it appears to work fine with my small app but is failing when I try to deploy a big one like Office 2010. I have tried having it run from the distribution point and am currently trying to do it by downloading it to the client and running it locally. I will let you know how it goes but I am pretty sure I have tried this already. Any thoughts? Same PC that I was using to test the small app.
0
 

Author Closing Comment

by:Benlife
ID: 34197324
Kezzi was very prompt to respond to my question and subsequent follow ups. I said that this partially solved my question when really it did fix my original question. It is just that I got selfish and wanted more. I will start a new question for the rest. Thanks Kezzi.
0
Too many email signature updates to deal with?

Do you feel like you are taking up all of your time constantly visiting users’ desks to make changes to email signatures? Wish you could manage all signatures from one central location, easily design them and deploy them quickly to users? Well, there is an easy way!

 
LVL 10

Expert Comment

by:Kezzi
ID: 34211966
Hi Benlife,

Sorry for not replying again, was away for a few days.  Glad you have it sorted out.  I'd be happy to continue helping you with your issues.

You are right about the distribution point updates.  As for the tools, if right clicking the collection, its called Configmgr collection actions.
0
 

Author Comment

by:Benlife
ID: 34231550
YES! I would love some more help. I am just coming back from the holiday weekend. I will get spun up again and reply with a more specific question to see if you can help. Thanks!
0
 

Author Comment

by:Benlife
ID: 34240586
Ok. I found a technet article specific to deploying Office 2010 using sccm. Followed it to a T. And http://technet.microsoft.com/en-us/library/ff404178.aspx
And now I have an advertised software package for 2010 status waiting for content on three machines. They have been in this state for over  a half hour now. I know this is a big install but I have a feeling that it isn't going to ever get past this point. I browse to the client cache c:\windows\system32\ccm\cache\ find the folder and it is still empty. I setup the application to be downloaded from the distribution point and run locally.
I am thinking I don't understand fully how distribution points are supposed to work. When I set this up I pointed it to a UNC on another server for the installation files. The comand line is pointed to setup.exe. The windows installer file is pointed to the ProPlusWW.msi just like the TN article says. And the This server has been used as an application repository and users run installations from there manually all the time. It is a hidden share but has read rights available to the all users group. So how does this work? Should I be coping anything to the shared folder on the sccm server? (SMSPKGD$).  

Please share thoughts and I am eager to respond with any logs or screen shots. Thanks.
0
 

Author Comment

by:Benlife
ID: 34240736
0
 

Author Comment

by:Benlife
ID: 34240796
Just sent a screen cast. That is pretty cool. Never done that before. Thought it might give you some information about our environment. Let me know what you think about the boundaries. Do I need all those subnets identified or should the default-first-site-name type active directory be sufficient?
0
 
LVL 10

Expert Comment

by:Kezzi
ID: 34248025
can you post the execmgr.log and cas.log files from the client please?

Are any of your boundaries configured as slow?  

When you create a package and point it to the source files, SCCM primary server will create a compressed file called a pck to be used for distributing to other SCCM servers.  When you add a distribution point onto the package, sccm unpacks the .pck file and copies the content to the smspkg$ share.  If you have set your advertisment to download, then the client will request the content from that share.  
0
 

Author Comment

by:Benlife
ID: 34249634
None of them are configured as slow. Here are the logs you requested. I have been messing around with different settings so hopfully they shed some light.
CAS-20101118-020229.log
CAS.log
execmgr-20101130-115724.log
execmgr.log
0
 
LVL 10

Expert Comment

by:Kezzi
ID: 34249896
OK well this is definitely showing that it cannot find the content as there are no DP's with the content.

What is your distribution status for the package?
What is the IP address of this machine and does it lie within the boundaries you have set?  Is your site protected by its boundaries?  How many DP's do you have?
0
 

Author Comment

by:Benlife
ID: 34253192
I saw that i couldn't find a DP in the log before I sent it to you and wondered if it was because I was messing around with it.
The distribution status hasn't changed. Still waiting for content. Unless I misunderstand what you mean by distribution status for the package. I have messed with it some by switching it from download and run locally to run from distribution point. Which brings up the question, Do I have to manually copy the installation files to the DP or is it supposed to happen automatically? If manually, where do I put them? And does it have to be a share?

The IP address for this PC is 10.32.32.40 and it is a member of the domain. There is a 10.32.32.0 boundry and domian listed in the boundries. There are no items listed as protected in any of the boundaries.
I am pretty certain that there is only one DP. And that is the one that was createded when SCCM was originally configured. The name of it is ITS-SCCM01. When I go into the Office 2010 package I created and look at the distribution point that is what comes up. Same as the other smaller successful package that I delployed last week.

I was going to try creating a third package that is smaller than Offfice but slightly larger than my my first successful deployment.

Thanks!
0
 
LVL 10

Expert Comment

by:Kezzi
ID: 34256082
OK right click the Package Status option in your package and say show messages - all.   then press skip for time period.  Save the file then upload it here.
0
 

Author Comment

by:Benlife
ID: 34259211
The first Magicdisc package the data source was the D drive of the server. It was successful at pushing the content to the client but never ran the install.

The second one the data  source was a UNC to a share on our network that the everyone group has read access to. It never got past waiting for content.

Neither of these showed up as advertised programs on the client.
Magicdisc.txt
Majicdisc2.txt
0
 
LVL 10

Expert Comment

by:Kezzi
ID: 34259567
ok can you upload your distrmgr.log file from your site server?
0
 
LVL 10

Expert Comment

by:Kezzi
ID: 34259616
also check to see if you have pck files for those 2 packages.
0
 

Author Comment

by:Benlife
ID: 34261437
There are no pck files for either package. The PCK files should only be created if you if you choose download source files to the client and run locally right? For the lifepro display app that works there is a lifepr01.exe file in a folder called BFG0001D that is located on the SMSPKGD$ share on the server. This was created automatically I believe when the package was created and advertised.



I included a screenshot of an error I stumbled accross. Not sure if it means anything.
Critical-error.png
distmgr.log
distmgr1.log
0
 
LVL 10

Expert Comment

by:Kezzi
ID: 34266084
check the permissions on smspkgd$.  make sure you propagate everyone for read access on all files and folders and sub directories and files.  make sure local admin has full access and propagate.

Rebooting the server might fix this as well.  i've seen this issue in another environment were i worked where SCCM would lose access to its own shares. not sure what causes it though...
0

Featured Post

Promote certifications in your email signature

Has your company recently won an award or achieved a certification? They'll no doubt want to show it off. Email signature images used to promote certifications & awards can instantly establish credibility with a recipient and provide you with numerous benefits.

Join & Write a Comment

Every system administrator encounters once in while in a problem where the solution seems to be a needle in haystack.  My needle was an anti-virus version causing problems with my Exchange server. I have an HP DL350 with Windows Server 2008 Stand…
Problem Description: Actually I found the below issue with some customers after migration from SMS 2003 to SCCM 2007 and epically if they change site code, some clients may appear in the console with old site code, plus old sites still appearing …
Illustrator's Shape Builder tool will let you combine shapes visually and interactively. This video shows the Mac version, but the tool works the same way in Windows. To follow along with this video, you can draw your own shapes or download the file…
This demo shows you how to set up the containerized NetScaler CPX with NetScaler Management and Analytics System in a non-routable Mesos/Marathon environment for use with Micro-Services applications.

760 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

20 Experts available now in Live!

Get 1:1 Help Now