Steps to take if PS script test yields no results in either view

What troubleshooting steps can be taken in the event testing the PS script yields no results in either view?

I am in that situation and the solution in a similar thread does not work. I'm running SQL 2012 as a CMS using EPM 4.1 and trying to evaluate servers from 2012 to 2005 both named and default instances.

Thanks for the prompt feedback. I re-registered my test servers and ran policy evaluation from the CMS. I got some records in the second view but, with a discouraging message in each records evaluation results column. It read:

You're very welcome. At first glance and I'm not sure how this would be, but it looks like the policy doesn't have a name (or maybe condition your using) or at least its not parsing name correctly.
Do you have oddly named policies or conditions?

Object reference not set to an instance of an object. (Microsoft.SqlServer.Dmf)

OK

I experienced this as well on my first tries at the PowerShell script. tl;dr: try commenting out the line for 'LoadAssemblies' in the PowerShell script if your host machine has SQL Server 2012 client tools.

After adding write-host and traps to figure out the error, the exception occurred on the line:

In my environment - a tools server - Windows Server 2008 + SQL Server 2012, the 2014 tools aren't yet installed. As an experiment, I commented out the loading of custom assemblies since EPM 3.0 had been working fine and doesn't include such a step. This did
the trick:

(line 110 as of Release 4.1.1)
#LoadAssemblies

The environment is an inplace upgrade from Server 2008R2 to Server 2012, which I would typically avoid in favor of a clean install. That or some combination of the Server 2008 r2 patch level might be why this is uncommon.

Not sure the ramifications of not loading assemblies for other environments, but in this case, all the required funcationality appears to be present because of the load of the 'sqlps' module (?)