RDM Enterprise Crashing on 2022.2.14 on only 1 database
I have an odd problem.
I have 7 SQL databases to segment different companies and such. I can open 6 of 7 data sources without issues. When I open the 7th one, RDM hangs and then closes/crashes. This is recorded in the Application log on Event Viewer.
Faulting application name: RemoteDesktopManager64.exe, version: 2022.2.14.0, time stamp: 0xf9c131ad
Faulting module name: clr.dll, version: 4.8.4515.0, time stamp: 0x624ce98e
Exception code: 0xc00000fd
Fault offset: 0x00000000001f01b9
Faulting process id: 0x44d4
Faulting application start time: 0x01d88717689f5df7
Faulting application path: C:\Program Files (x86)\Devolutions\Remote Desktop Manager\RemoteDesktopManager64.exe
Faulting module path: C:\Windows\Microsoft.NET\Framework64\v4.0.30319\clr.dll
Report Id: 928399b1-0e79-44ae-8847-96cdf2b240bd
Faulting package full name:
Faulting package-relative application ID:
Now, I didn't need to connect to this database until today, but I know it worked prior to the 2022.2.12.0 released this week.
All of the other databases prompted for an upgrade prior to connecting, with the exception of number 7. So...I launched RDM on one of the working data sources and performed a manual upgrade on the data source. I checked connections and database connections. All reported successful. Yet....when try to connect to DB #7, it crashes and generates the same error in the application log.
So...I assumed a database error. I restored the database from backups from both last week and last month. Performed the same manual upgrade tasks, but the application continues to crash. Next, I created a new database and restored the latest backup to the new database. Performed the same manual upgrade tasks but still continues to implode.
Ugh.
Ideas?
All Comments (6)
Hello,
Thank you for contacting us on that matter!
Could you email us the schema of the affect SQL data source? Under File > Data Sources, select the problematic SQL, go to Upgrade, and click on the last button:
Also, while using an older version of RDM, are you able to connect to it? You can use a portable version of RDM to test it out.
1- Download the .zip for RDM 2022.1.27: https://cdn.devolutions.net/download/Devolutions.RemoteDesktopManager.Bin.2022.1.27.0.zip
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
6- Add your SQL data source
Best regards,
Richard Boisvert
Unfortunately, I've been poking and prodding. I deleted the data source and recreated it. Now, I suspect the new data source is now set as the default, so it opens and crashes now. I deleted cfg file and relauched. I added license information and then it crashed again. The same scenario as before. How do I change the default data source without RDM?
Hello,
First, make sure RDM is closed. Then, go to %localappdata%\Devolutions\RemoteDesktopManager\RemoteDesktopManager.cfg (default path for the configuration file).
Do a search for <PromptDataSourceOnStartUp> and changed the value to true, meaning it would look like this:
<PromptDataSourceOnStartUp>true</PromptDataSourceOnStartUp>
If you cannot find it, add it just before the </Option> at the end. Re-open RDM and you should get a prompt with all your data sources:
Best regards,
Richard Boisvert
Hello,
I was just notified that you can simply hold the ctrl key while RDM is loading and you will get the data source prompt, no need to modify your .cfg file.
Best regards,
Richard Boisvert
Thanks for the replies.
Unfortunately, this odd error message was foreshadowing a larger hardware issue. I started getting BSODs, which devolved into simply freezing just attempting to boot into Windows. While a base Windows reinstall stabilized the system, the system crashes when attempting to load any drivers. RAM and storage tests didn't show problems.
Hello,
I hope you can get your issues resolved quickly! Once stabilized, let us know if you have still have any issues with your SQL data source.
Best regards,
Richard Boisvert