Even after reading that a few times, I'm not sure what a Get Command is doing that could remedy this problem, I have edited my answer to include the output. Thank you for showing me Get-SPProduct

Can you run a psconfig? Running this command allows your SharePoint to detect required software that would otherwise be blocking the sync in the farm.

You are very close to an accepted answer. We ran the powershell command and psconfig wizard on both servers. I decided to start/stop with central admin on the WFE the Excel Calculation Services. And it worked! However on the APP server I was able to STOP excel Calculation services, but now it's stuck on starting.

Do you have a healthy Excel Services Service Application? I'd check the settings on that. Also have you tried restarting?

It looks like it just took an extremely long time. Which I didn't think I've ever seen it take nearly 30 minutes to unprovision. I love you.

haha glad i could help! Thanks!

It's not working again, we have to run the command for solutions still.

Are all servers and db server on the same timezone?

Same Time zone and same daylight savings!

Check the timer jobs and delete the one-time jobs, and restart the sptimer service, before you try to deploy again. You may need to reset the sp config cache, read here: blogs.msdn.com/b/jamesway/archive/2011/05/23/…

Should APP and Web both be running SPTimer? Our Central Admin is on the WFE. Should SPAdminv4 only be running on the WFE then? Let me Delete ALL one time jobs, some of them looked important

SPTimerv4 is a crucial service that syncs the server with the rest of the farm's servers. It should always be running on every SharePoint server. If One-Time jobs are in the definitions, they aren't running correctly. One-time timer jobs are created by SharePoint and the definitions are deleted after they run successfully.

So what about spadminv4?

Yes, this needs to be started as well.

Okay, so I stopped sptimerv4 and spadminv4 on all servers. I deleted every timerjob that was .Schedule.Description = One-Time with powershell. I am starting up the services now

Stopped the services, and did a cleared the cache. Restarted services

This "Upgrade Job" is showing failed in the timer job.

make sure you are running the psconfig as an administrator or as the account you installed sharepoint with.

I was sure we did

under spadmin

Okay, No Timer Job status reported failure this time!

Somehow through that NintexWorkflows got deployed to only Central Admin

We redeployed them to the web apps

and now the sites still on 2010 can't manage/create workflows

but that's a separate issue now

THANK YOU

You are welcome! Please star the chat message that helped you the most