DM added to DASH will not work

I re-added DM to my DASHBOARD, using the following as a guide. http://wiki.idera.com/display/SQLDM/Register+SQL+Diagnostic+Manager+in+the+IDERA+Dashboard

However, when I try to navigate to the DM via the DASHBOARD, I get the following error...  I have provided system details further below.

HINTS?


---------------------------------------------------------------------------.
Oops, Looks like we are experiencing technical difficulty. Please try again in a few minutes or go back to
Idera CWF Dashboard
Request URL: /sqldm/diagnosticmanager/home
Status Code: 500
Exception Type: class java.lang.NullPointerException
Exception: java.lang.NullPointerException
Exception Type: class java.lang.NullPointerException
Servlet Name:
Stack Trace: java.lang.NullPointerException at org.zkoss.bind.impl.MiscUtil.mergeExceptionInfo(MiscUtil.java:165) at org.zkoss.bind.BindComposer.doBeforeComposeChildren(BindComposer.java:157) at org.zkoss.zk.ui.impl.UiEngineImpl.doBeforeComposeChildren(UiEngineImpl.java:882) at org.zkoss.zk.ui.impl.UiEngineImpl.execCreateChild0(UiEngineImpl.java:821) at org.zkoss.zk.ui.impl.UiEngineImpl.execCreateChild(UiEngineImpl.java:778) at org.zkoss.zk.ui.impl.UiEngineImpl.execCreate0(UiEngineImpl.java:687) at org.zkoss.zk.ui.impl.UiEngineImpl.execCreateChild(UiEngineImpl.java:749) at org.zkoss.zk.ui.impl.UiEngineImpl.execCreate0(UiEngineImpl.java:709) at org.zkoss.zk.ui.impl.UiEngineImpl.execCreate(UiEngineImpl.java:651) at org.zkoss.zk.ui.impl.UiEngineImpl.createComponents(UiEngineImpl.java:1032) at org.zkoss.zk.ui.impl.AbstractExecution.createComponents0(AbstractExecution.java:246) at org.zkoss.zk.ui.impl.AbstractExecution.createComponents(AbstractExecution.java:238) at

---------------------------------------------------------------------------.
IDERA SQL Diagnostic Manager Desktop Client 10.4.0.3432
IDERA SQL Diagnostic Manager Repository 10.4
IDERA SQL Diagnostic Manager Management Service 10.4.0.3432
IDERA SQL Diagnostic Manager Collection Service 10.4.0.3432
Microsoft Data Access Component (MDAC) 6.3.9600.16384
Microsoft .Net Framework 4.0.30319.42000
Microsoft Windows Operating System Microsoft Windows NT 6.2.9200.0
SQLDM Mobile and Newsfeed Version 1.4.15.12

---------------------------------------------------------------------------.
OS Name Microsoft Windows Server 2012 R2 Standard
Version 6.3.9600 Build 9600
Other OS Description  Not Available
OS Manufacturer Microsoft Corporation
System Name SMMNRVWPSMGT02
System Manufacturer VMware, Inc.
System Model VMware Virtual Platform
System Type x64-based PC
System SKU 
Processor Intel(R) Xeon(R) CPU           X5670  @ 2.93GHz, 2926 Mhz, 2 Core(s), 2 Logical Processor(s)
Processor Intel(R) Xeon(R) CPU           X5670  @ 2.93GHz, 2926 Mhz, 2 Core(s), 2 Logical Processor(s)
BIOS Version/Date Phoenix Technologies LTD 6.00, 9/17/2015
SMBIOS Version 2.4
Embedded Controller Version 0.00
BIOS Mode Legacy
BaseBoard Manufacturer Intel Corporation
BaseBoard Model Not Available
BaseBoard Name Base Board
Platform Role Desktop
Secure Boot State Unsupported
PCR7 Configuration Not Available
Windows Directory C:\Windows
System Directory C:\Windows\system32
Boot Device \Device\HarddiskVolume1
Locale United States
Hardware Abstraction Layer Version = "6.3.9600.18969"
User Name Not Available
Time Zone Eastern Daylight Time
Installed Physical Memory (RAM) 8.00 GB
Total Physical Memory 8.00 GB
Available Physical Memory 3.94 GB
Total Virtual Memory 9.25 GB
Available Virtual Memory 4.60 GB
Page File Space 1.25 GB
Page File S:\pagefile.sys
A hypervisor has been detected. Features required for Hyper-V will not be displayed. 
---------------------------------------------------------------------------.

  • The NullPointerException is, unfortunately, very generic and doesn't help pinpoint what the underlying problem might be. However, I do know of one problem that seems to be common. 

    On the machine where SQLDM is installed, can you open Registry Editor and go to HKLM\SOFTWARE\Idera\SQLdm. There should be subkey named Version. If the value for that subkey is 10.4.0.3432, change it to 10.4.0.343 (basically delete the last character) then restart the SQLDM Rest Service. Once restarted, try to access the SQLDM web console again.

    If the Version subkey is already set as 10.4.0.343 or you are running a version different from 10.4.0, then I think contacting support would be your next best step.