Trouble provisioning a PWA site

I am having a bit of a problem setting up a brand new server with Project Server 2013.  I have tracked it down to the following part of the site -- Enable-SPFeature

When I run it, I get the following

Enable-SPFeature pwasite -Url http://portal.sharepoint.dev/itpwa
Enable-SPFeature : Failed to find Service Application. Either the Service Application does not exist or the Service
Application proxy is misconfigured.
At line:1 char:1+ Enable-SPFeature pwasite -Url http://portal.sharepoint.dev/itpwa+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~+ CategoryInfo          : InvalidData: (Microsoft.Share...etEnableFeature:SPCmdletEnableFeature) [Enable-SPFeature
   ], SPException+ FullyQualifiedErrorId : Microsoft.SharePoint.PowerShell.SPCmdletEnableFeature

I am not sure where to go next outside of completely rebuilding the VM.

Here is what I have done so far

• Validated I am on the last SP and CU (September 2014 is confirmed)
• Removed Service Application and Proxy, removed Database, stopped and restarted service on server
• Tried creating using different credentials
• Tried creating using new application pool
• Tried creating using different database names
• Broke process of settings a PWA up down into individual PowerShell steps. All succeed until the "Enable-SPFeature" call.

Anyone have any suggestions?

Note: I have 4 other VMs that were setup identically (by me) and all are working fine.  This one was working and then stopped working after a reboot. I'd like to figure it out so as to avoid the issue in the future.

Also here is the event log details from creating the PWA instance from inside CA

Failed to provision site ITPWA with error: Microsoft.SharePoint.SPException: Failed to find Service Application. Either the Service Application does not exist or the Service Application proxy is misconfigured.
   at Microsoft.Office.Project.Server.Administration.ProvisionFeatureEventHandler.FeatureActivated(SPFeatureReceiverProperties properties)
   at Microsoft.SharePoint.SPFeature.DoActivationCallout(Boolean fActivate, Boolean fForce)
   at Microsoft.SharePoint.SPFeature.Activate(SPSite siteParent, SPWeb webParent, SPFeaturePropertyCollection props, SPFeatureActivateFlags activateFlags, Boolean fForce)
   at Microsoft.SharePoint.SPFeatureCollection.AddInternal(SPFeatureDefinition featdef, Version version, SPFeaturePropertyCollection properties, SPFeatureActivateFlags activateFlags, Boolean force, Boolean fMarkOnly)
   at Microsoft.SharePoint.SPFeatureCollection.AddInternalWithName(Guid featureId, Int32 compatibilityLevel, String featureName, Version version, SPFeaturePropertyCollection properties, SPFeatureActivateFlags activateFlags, Boolean force, Boolean fMarkOnly, Boolean fIgnoreMissing, SPFeatureDefinitionScope featdefScope)
   at Microsoft.SharePoint.SPFeatureCollection.AddInternal(Guid featureId, Version version, SPFeaturePropertyCollection properties, Boolean force, Boolean fMarkOnly, SPFeatureDefinitionScope featdefScope)
   at Microsoft.SharePoint.SPFeatureCollection.Add(Guid featureId)
   at Microsoft.Office.Project.Server.Administration.PsiServiceApplication.EnsureProvisioningFeature(SPSite site)
   at Microsoft.Office.Project.Server.Administration.PsiServiceApplication.CreateSite(ProjectProvisionSettings provset)

Shawn