- This topic has 12 replies, 8 voices, and was last updated 4 years, 7 months ago by
.
-
Posts
-
When I open the WDM mmc console and click on the WyseDeviceManager Node in the tree I get this error.
Application Function: GetEnvInfo: 53 File not found: RptSrvComm.dll
I can click ok, then I get the same error in a different message box titled
WDM Service Log.I can click ok, then I get a different error :
Unable to determine GUI HTTP port. MMC will now terminate. nGUIHTTPPortActual=0
Then the user interface loads and when I click on the “Find Devices” button the mmc snap-in closes out.
The file RptSvcComm.dll is in the Windows/System32 folder and the Program Files/Wyse/WDM folder.
The WDM is running on Windows XP Pro SP2 with IIS-HTTP & FTP, SNMP installed previously.
The SQL Instance appears to be fine.
The HAgent Service, the RptStdSvc and the Rapport4 Service is running
as well as the SQL InstanceAny Clues as to what is going on and/or how to fix it.
Thanks in advance,
ScottyCI have no idea what went wrong. Reinstalled and now it seems to be working great.
I am having this same issue. Running reinstalling will not work as I receive a message saying that “The required libraries are not found” I also tried to run vcredist_x86.exe as posted in another thread and that did not help either. Any ideas?
4.9.1 on Windows Server 2008 R2. It was working fine for some time, then just started throwing this error.
What exact message are you seeing?
I guess that some MS hotfix killed something. Or any other install you did on that server.CG
Also getting the same issue, running on win2003, wdm v4.9.1 – no ms updates nor any other application has been installed…
Server 2003 is no longer supported. Try it on a Windows 2008 server instead.
CG
Pretty crazy digging this thread up, but, I came across this today myself. 2 changes did occur, for one the C drive ran out of disk space. We fixed that by clearing logs. The other change was some MS updates were installed, and since then we got this same error.
I did uninstall the April Cumulative update (KB4493446), but, same result. I’d uninstall all the others if I felt like this was it.
WDM 5.7.2, Windows Server 2012.
Turns out for me, the issue wasn’t caused by Windows Updates, but by the server running out of disk space. We resolved that, then using the Backup directory from within the WDM install folder, we restored the dll file to the needed directories (System 32 and WDM). After that, a reboot fixed it.
LOL. I can’t believe I had this issue as well… Drive space issue here as well…
Used your guide to copy the files over, and I’m back in business. Thank you for helping, as I didn’t want to re-build this old WDM server.
Yes. I know. I should move to WMS…
Hi All,
another reason for this issue could be an update of VMWare Tools…
during the upgrade some C++ libaries are deleted that are required for the correct operation of WDM. The exact version depends of the used WDM version. If you “simply” reinstall the C++ libaries your system will work again..
Regards
Volker
- You must be logged in to reply to this topic.