Unsolved
This post is more than 5 years old
3 Posts
0
3130
WDM 5.7 - Discovery and imaging OFFLINE
Hi,
Since yesterday our wdm environment (WDM 5.7 Workstation) says in the web interface that discovery and imaging is offline?
In the welcome window / server status it says system down.
The server itself is online and working. I already rebooted the server but no difference.
What does this exactly mean, and what can i do about it to fix this?
In the diagnostic report i made everything passes except this:
| PASS | C:\Program Files (x86)\Wyse\WDM\Utilities\RptDiag.exe | 5.7.0.1277 | 5.7.0.1277 |
| FAIL | C:\Program Files (x86)\Wyse\WDM\Utilities\Database\DatabaseCredentialManager.exe | 5.7.0.1277 | File doesn't exist |
| FAIL | C:\Program Files (x86)\Wyse\WDM\Utilities\Database\HAConfigureUtility.exe | 5.7.0.1277 | File doesn't exist |
| FAIL | C:\Program Files (x86)\Wyse\WDM\Utilities\GUIExtractor\MgmtConsoleExtract.exe | 5.7.0.1277 | File doesn't exist |
| PASS | C:\Program Files (x86)\Wyse\WDM\WDMServerComm.dll | 5.7.0.1277 | 5.7.0.1277 |
| PASS | C:\Windows\system32\mssnapr.dll | 5.0.2150.1 | 5.0.2150.1 |
| PASS | C:\Program Files (x86)\Wyse\WDM\Rapport.msc | NA | File Exists |
| PASS | C:\Program Files (x86)\Wyse\WDM\RegFilter40.tpl | NA | File Exists |
| PASS | C:\Windows\system32\WBCustomizer.dll | 1.0.0.3 | 1.0.0.3 |
| PASS | C:\Program Files (x86)\Wyse\WDM\RptBundle32\bundle32.exe | NA | File Exists |
| PASS | C:\Program Files (x86)\Wyse\WDM\RptBundle32\k | NA | File Exists |
| FAIL | C:\Program Files (x86)\Wyse\WDM\TftpRoot\rapport.0 | NA | File doesn't exist |
| FAIL | C:\Program Files (x86)\Wyse\WDM\TftpRoot\bzImage | NA | File doesn't exist |
| FAIL | C:\Program Files (x86)\Wyse\WDM\TftpRoot\rapport.conf | NA | File doesn't exist |
The standard service passes, and in the web portal says discovery and imaging is using this port (8008). But when i do a netstat -a nog service is listening on this port.
benso37
2 Posts
0
December 9th, 2016 11:00
Did you ever find a solution to this issue? I have the same error on my dashboard.
rrosing
3 Posts
0
December 16th, 2016 02:00
Because i installed a second instance of sql server this problem accured.
2 sql instances one 1 server is not an option.
After you install the second instance this problem is solved.