IHello,
i get this Message when i start RDM-Free.
I try to reinstall RDMF. Still the same.
I downgrade to Version 2020.3.24.0. Still the Same.
I downgrade to Version 2020.3.23.0. Still the Same.
I downgrade to Version 2020.3.22.0. Still the Same.
I search for other Problems with this File "System.EnterpriseServices.Wrapper.dll" and found topics about .NET Framework.
Which Version of the .NET Framework i must repair?
Hello,
We use .NET 4.72 in RDM. Indeed this seems to be related to your .NET installation.
Regards
David Hervieux
Hello,
Following David's post, this article provides a link to the .Net Framework repair tool.
https://kb.devolutions.net/rdm_corrupted_system_file.html
Best regards,
Érica Poirier
Thanks for your Tips. I run the .Net Framework repair tool, and install the RDMF new, but i get the same Error Message.
Hello,
What Windows version are you using? Could you please send a screen capture of the winver command?
Have you tried the SFC ScanNow from the page I have previously provided?
Best regards,
Érica Poirier
Result of the SFC Scan:
Microsoft Windows [Version 10.0.18363.1316] (c) 2019 Microsoft Corporation. Alle Rechte vorbehalten. C:\WINDOWS\system32>DISM.exe /Online /Cleanup-image /Restorehealth Tool zur Imageverwaltung für die Bereitstellung Version: 10.0.18362.1316 Abbildversion: 10.0.18363.1316 [==========================100.0%==========================] Der Wiederherstellungsvorgang wurde erfolgreich abgeschlossen. Der Vorgang wurde erfolgreich beendet. C:\WINDOWS\system32>sfc /scannow Systemsuche wird gestartet. Dieser Vorgang kann einige Zeit dauern. Überprüfungsphase der Systemsuche wird gestartet. Überprüfung 100 % abgeschlossen. Der Windows-Ressourcenschutz hat keine Integritätsverletzungen gefunden.
Hello,
Thank you for the information and sorry that you still experience this problem.
I have tried to get some answers online and found that a potential solution is to completely uninstall .Net Framework and install it back.
Other people on some online forums mentioned that rebooting the computer helped to solve their problem too.
Let me know if any of these solved your issue.
Best regards,
Érica Poirier
Hello,
While we are currently trying to reproduce this issue on our end, we would like to know if you have any entries in your Event Viewer related to this crash? If so could you please provide it to us via private message?
Best regards,
James Lafleur
Hello,
While we are currently trying to reproduce this issue on our end, we would like to know if you have any entries in your Event Viewer related to this crash? If so could you please provide it to us via private message?
Best regards,
There is no entry in my Event Viewer. I try also to start RDMF as Administrator and there is also no entry in my Event Viewer.
Hello,
Thank you for your quick reply!
I will transfer this information to our engineering department and get back to you once I have an update on this.
Best regards
James Lafleur
Hello,
To gather more information about this issue, we would like you to follow this procedure which makes use of a tool offered by Microsoft's Technet, namely the Sysinternals suite. The tool that we need is procdump. It will monitor the application and create a dump file automatically in case it encounter a crash )-e) or hang (-h) for more than 5 seconds.
This suite can be downloaded using the following link: https://download.sysinternals.com/files/SysinternalsSuite.zip
Once it is installed, please do the following:
1-Create a batch file containing a command such as:
{TOOLS_PATH\procdump.exe -e -h -ma -g -x {DUMP_PATH} "{INSTALL_PATH}\RemoteDesktopManager.exe"
If the application becomes unresponsive, the tool will handle everything.
2-Send the dump file to us using the following secure link: https://api.devolutions.net/redirection/c50a4798-7fd9-44e5-a2a1-79a753a35c36
Also, I would like to know the following:
1- Have you configured an application password on your RDM instance?
2- When you return to your workstation, do you restore RDM from the tray icon?
Best regards,
James Lafleur
Hello,
To gather more information about this issue, we would like you to follow this procedure which makes use of a tool offered by Microsoft's Technet, namely the Sysinternals suite. The tool that we need is procdump. It will monitor the application and create a dump file automatically in case it encounter a crash )-e) or hang (-h) for more than 5 seconds.
This suite can be downloaded using the following link: https://download.sysinternals.com/files/SysinternalsSuite.zip
Once it is installed, please do the following:
1-Create a batch file containing a command such as:
{TOOLS_PATH\procdump.exe -e -h -ma -g -x {DUMP_PATH} "{INSTALL_PATH}\RemoteDesktopManager.exe"
If the application becomes unresponsive, the tool will handle everything.
2-Send the dump file to us using the following secure link: https://api.devolutions.net/redirection/c50a4798-7fd9-44e5-a2a1-79a753a35c36
Also, I would like to know the following:
1- Have you configured an application password on your RDM instance?
2- When you return to your workstation, do you restore RDM from the tray icon?
Best regards,
There is no dump-file created.
"SysinternalsSuite\procdump.exe" -e -h -ma -g -x "C:\Temp\dump" "C:\Program Files (x86)\Devolutions\Remote Desktop Manager Free\RemoteDesktopManagerFree.exe" > c:\temp\dump\log.txt
The log.txt
Process: RemoteDesktopManagerFree.exe (19020)
CPU threshold: n/a
Performance counter: n/a
Commit threshold: n/a
Threshold seconds: 10
Hung window check: Enabled
Log debug strings: Disabled
Exception monitor: Unhandled
Exception filter: [Includes]
*
[Excludes]
Terminate monitor: Disabled
Cloning type: Disabled
Concurrent limit: n/a
Avoid outage: n/a
Number of dumps: 1
Dump folder: C:\Temp\dump\
Dump filename/mask: PROCESSNAME_YYMMDD_HHMMSS
Queue to WER: Disabled
Kill after dump: Disabled
Press Ctrl-C to end monitoring without terminating the process.
[16:47:43] Exception: 04242420
[16:47:43] Exception: E06D7363.PEAVEEFileLoadException@@
[16:47:43] Exception: E06D7363.msc
[16:47:43] Exception: E06D7363.PEAVEEFileLoadException@@
[16:47:45] Exception: E06D7363.PEAVEEFileLoadException@@
[16:47:45] Exception: E06D7363.msc
[16:47:45] Exception: E06D7363.PEAVEEFileLoadException@@
[16:47:45] Exception: E06D7363.msc
[16:47:45] Exception: E06D7363.PEAVEEFileLoadException@@
[16:47:45] Exception: E0434352.CLR
[16:47:46] Exception: E0434352.CLR
[16:47:48] Exception: E0434352.CLR
[16:47:48] Exception: E0434352.CLR
[16:47:48] Exception: E0434352.CLR
[16:47:48] Exception: E0434352.CLR
[16:47:57] Exception: E06D7363.PEAVEEFileLoadException@@
[16:47:57] Exception: E06D7363.msc
[16:47:57] Exception: E06D7363.PEAVEEFileLoadException@@
[16:47:57] Exception: E06D7363.PEAVEEFileLoadException@@
[16:47:57] Exception: E06D7363.msc
[16:47:57] Exception: E06D7363.PEAVEEFileLoadException@@
[16:47:57] Exception: E06D7363.msc
[16:47:57] Exception: E06D7363.PEAVEEFileLoadException@@
[16:47:57] Exception: E0434352.CLR
[16:47:57] Exception: E06D7363.msc
[16:47:57] Exception: E06D7363.PEAVEEFileLoadException@@
[16:47:57] Exception: E0434352.CLR
[16:47:57] Exception: E06D7363.PEAVEETypeLoadException@@
[16:47:57] Exception: E06D7363.msc
[16:47:57] Exception: E06D7363.PEAVEETypeLoadException@@
[16:47:57] Exception: E06D7363.msc
[16:47:57] Exception: E06D7363.PEAVEETypeLoadException@@
[16:47:57] Exception: E06D7363.msc
[16:47:57] Exception: E06D7363.PEAVEETypeLoadException@@
[16:48:00] Exception: E0434352.CLR
[16:48:00] Exception: E0434352.CLR
[16:48:00] Exception: E0434352.CLR
[16:48:00] Exception: E0434352.CLR
[16:48:03] Exception: E0434352.CLR
[16:48:08] Exception: E06D7363.PEAVEEFileLoadException@@
[16:48:08] Exception: E06D7363.msc
[16:48:08] Exception: E06D7363.PEAVEEFileLoadException@@
[16:48:08] Exception: E06D7363.PEAVEEFileLoadException@@
[16:48:08] Exception: E06D7363.msc
[16:48:08] Exception: E06D7363.PEAVEEFileLoadException@@
[16:48:08] Exception: E06D7363.PEAVEEFileLoadException@@
[16:48:08] Exception: E0434352.CLR
[16:48:08] Exception: E0434352.CLR
[16:48:08] Exception: E06D7363.PEAVEEFileLoadException@@
[16:48:08] Exception: E06D7363.msc
[16:48:08] Exception: E06D7363.PEAVEEFileLoadException@@
[16:48:08] Exception: E06D7363.PEAVEEFileLoadException@@
[16:48:08] Exception: E06D7363.msc
[16:48:08] Exception: E06D7363.PEAVEEFileLoadException@@
[16:48:08] Exception: E06D7363.PEAVEEFileLoadException@@
[16:48:08] Exception: E0434352.CLR
[16:48:08] Exception: E0434352.CLR
[16:48:08] Exception: E0434352.CLR
[16:48:08] Exception: E06D7363.PEAVEEFileLoadException@@
[16:48:08] Exception: E06D7363.msc
[16:48:08] Exception: E06D7363.PEAVEEFileLoadException@@
[16:48:08] Exception: E06D7363.PEAVEEFileLoadException@@
[16:48:08] Exception: E06D7363.msc
[16:48:08] Exception: E06D7363.PEAVEEFileLoadException@@
[16:48:08] Exception: E06D7363.PEAVEEFileLoadException@@
[16:48:08] Exception: E0434352.CLR
[16:48:08] Exception: E0434352.CLR
[16:48:08] Exception: E0434352.CLR
[16:48:19] Exception: 0000071A
[16:48:20] The process has exited.
[16:48:20] Dump count not reached.
Hello,
Thank you for your quick reply!
In that case, would it be possible for you to instead create a minidump manually after experiencing the Freeze? To do so, please follow these steps:
1- Download Process Explorer here: https://docs.microsoft.com/en-us/sysinternals/downloads/process-explorer
2- Run RDM
3- Wait for it to freeze
4- Start Process Explorer (procexp.exe)
*If RDM is running with elevated privilege, then you will need to start procexp elevated
5- Find RemoteDesktopManager.exe in the tree
6- Right-click -> Properties -> Threads (tab)
6.1-Sort by CPU descending (should be the default sort)
6.2-Take a screenshot of that UI and send us this image
6.3- Select the top one in the list
6.4- Click Stack
6.5- Copy All and then send us the text
7- OK & OK
8- Right-click > Create Dump > Create Minidump
9- Send us the minidump via ShareFile link: https://api.devolutions.net/redirection/c50a4798-7fd9-44e5-a2a1-79a753a35c36
This will help us diagnose the issue.
Best regards,
James Lafleur
Hello,
Thank you for your files, We have received them. I opened a ticket to centralize all of them.
We will analyze them and get back to you.
Best regards,
Jeff Dagenais
Hello,
Our Engineering Department just informed me that they have made a fix in RDM 2020.3.27.0 that should at the very least reduce the number of freezes in RDM. For this reason, would it be possible for you to try this version and see if you are seeing any improvements?
RDM Free 2020.3.27.0 can be downloaded here:
https://remotedesktopmanager.com/home/thankyou/rdmfreemsi
Best regards,
James Lafleur
Our Engineering Department just informed me that they have made a fix in RDM 2020.3.27.0 that should at the very least reduce the number of freezes in RDM. For this reason, would it be possible for you to try this version and see if you are seeing any improvements?
Thank you for this Information.
I try the new Version but it is still the same problem.
I don´t have a "freeze of RDM". I get only the Messagebox that the "System.Enterprise.Services.Wrapper.dll" could not find.after the Messagebox i can "use" the RDM (i can click on the Menue ... )
I try to repair my .NET installation without any effect.
So i wait for a new SSD and than i reinstall the whole Windows System and any Software on my Notebook.
Hello,
Thank you for your quick reply and for this clarification!
Since this version did not help with this issue, we will wait for the result of your reinstallation on your new SSH.
Best regards,
James Lafleur
Hello,
RDM 2020.3.28.0 has been released yesterday and this version contain enhancements regarding the freeze issue.
Could you give it a try?
You can download this version here
https://remotedesktopmanager.com/home/download
Best regards,
Jeff Dagenais
Hello,
RDM 2020.3.28.0 has been released yesterday and this version contain enhancements regarding the freeze issue.
Could you give it a try?
You can download this version here
https://remotedesktopmanager.com/home/download
Best regards,
No effect. Still the same.
Hello,
Thank you for your quick return! Since this issue persists by updating your RDM instance to the latest version of RDM free, would it be possible for you to try to create a portable version of RDM and see if this issue still occurs?
To do so, you will need to do the following:
1- Download the .zip file below:
https://remotedesktopmanager.com/home/thankyou/rdmfreebin
2- Create a new folder on your Desktop
3- Extract the content of the .zip file into the folder created at #2
4- Go in this folder once the .zip file has been extracted and run remotedesktopmanager64.exe
5- Enter your current serial
Best regards,
James Lafleur
Hello,
According to the information provided by the other users who were experiencing these freezes, updating to RDM 2020.3.28.0 has solved this issue. For this reason, would it be possible for you to update to this version and see if this issue still occurs?
This version can be downloaded here:
https://remotedesktopmanager.com/home/downloadfree
Best regards,
James Lafleur
Hello to all,
one of the last Windows Updates repair my problem.
Thank you for all help.
You are more than welcome! Thank you for your feedback.
James Lafleur