Jump to content


  • 0
blmclaws

Advertised Apps fail to run

Question

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.

post-7714-1290003774583_thumb.png

post-7714-12900038026671_thumb.jpg

Share this post


Link to post
Share on other sites

1 answer to this question

Recommended Posts

  • 0

Look at cas.log(c:\windows\system32\ccm\logs) check the version of package requested.

 

There might be the cases where,package version mismatch occurs.Compare the packge version from your console and version from CAS.log package version.

 

At your client, to resolve the mismatch, if interactively logged into your client, in the Configuration Manager applet, the Actions tab, run the "Machine Policy Retrieval & Evaluation Cycle". Wait 2 minutes. Then re-run "Machine Policy Retrieval & Evaluation Cycle".Then try your install again.

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Answer this question...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...


×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.