Software Deployment Error SCCM 2012

I am getting the following error when I attempt to install an advertised package from within software center. Has anyone else had this error or simular? If so what is the root cause? I did check and reconfigure my boundary group to include the subnet that this PC is in. is is there anything else that I can check.

Screen Capture of the error
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Michael PfisterCommented:
Have a look at the AppEnforce.log and Execmgr.log on the affected client (C:\WIndows\CCM\Logs). If you want attch them here
cyberchrisrockAuthor Commented:
Here are the files that you suggested. I apologize that it took this long to post them, I had some difficulty.

Michael PfisterCommented:
right in the first line of AppEnforce.log:

... Starting Install enforcement for App DT "Lync 2013"

I believe this is your problem (line 2):

The content path is not specified for DeploymentType ScopeId_656B0575-4C8A-4940-9546-619EEDE229B4/DeploymentType_841fd280-2273-463a-a61c-e424535db491.  Content is assumed to be locally available.

Then line  16

Invalid executable file setup.exe

Check your "Lync 2013" package settings.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Newly released Acronis True Image 2019

In announcing the release of the 15th Anniversary Edition of Acronis True Image 2019, the company revealed that its artificial intelligence-based anti-ransomware technology – stopped more than 200,000 ransomware attacks on 150,000 customers last year.

cyberchrisrockAuthor Commented:
Can you recommend a tool that will repackage ".exe" installation files to ".msi"?
Michael PfisterCommented:
I'm not sure if this will help.

It seems the SCCM client is not able to locate the installation source and this is usually due to a misconfiguration in the package definition or it wasn't copied to the DP.

If you search for "repackage msi" you'll find many tools, some free some not. But repackaging setups often end in a disaster when the machine you're building your msi and the targets aren't 100% identical. I normally use this as the last resort.
cyberchrisrockAuthor Commented:
So what do you do instead?
Michael PfisterCommented:
Check the package definition?
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows Server 2008

From novice to tech pro — start learning today.