SMS "Waiting for content" 10035

Status Message ID 10035, or "Waiting for content" is a common error which can drive you up the wall when testing a package deployment.

Have you checked your site boundaries? Often a client is located in a IP Subnet which hasn't been configured within Site or Roaming Boundaries.

Has the software been deployed to the clients local DPs? Check the reports and console, make sure the package has been deployed and is available to the clients.

Is the advertisement configured for download and execute? Check the DP, make sure BITS is enabled, and the web site is functioning properly.

Have you checked the logs? Start with the cas.log and execmgr.log on the client computer.

Related Articles

Comments

danovich said…
Also check your site boundaries - by default advertisements won't run on slow boundaries. Either change it to fast or change the option in advertisements from "Do not run program" for slow or unreliable network boundary to download content and run locally.

http://blog.danovich.com.au
March 30, 2010 at 9:50 PM
Post a Comment

Popular posts from this blog

SMS "Program failed (run time exceeded)" 10070

When a program fails due to error 10070, it does so because the Run Time was Exceeded. SMS Allows a program to run for 12 hours, afterwhich it will issue the failed status message if the program hasn't completed successfully. Note: The Maximum allowed run time within program properties is generally a guide for users running the program themselves, and is not enforced.
Read more

SMS "Waiting for User Condition" 10036

Status Message ID 10036, or "Waiting for User Condition" can occasionally grind advertisements to a halt. Make sure the environment and user condition settings for a particular program have been configured appropriately and are not excluding a large portion of your intended audience. Related Articles SMS WQL for All Clients where Last Status is Waiting for User Condition SMS Status Message ID's
Read more