New installation with fatal error (Unable to load SQLite.Interop.dll)

New installation with fatal error (Unable to load SQLite.Interop.dll)

avatar

Hello there,

I'm new here so pardon me if this has being brought up countless times.

I've recently installed RDM (v10.1.9.0) into a fresh Win Server 2008 R2 OS but encountered fatal error when I try to run it (image as attached).

Thinking that it's something to do with the OS not being installed properly, I deployed a new Win Server 2008 R2 OS & this time, I installed RDM v10.5.4.0 but still had the same issue.

May I know if there's some workaround to get RDM running on my machine? Prior to the RDM installation, I've installed:
- Microsoft .NET Framework 4.5.2
- Microsoft Visual C++ 2010 x86 Redistributable - 10.0.40219
- Microsoft Visual C++ 2010 x64 Redistributable - 10.0.40219

The RDM log from %appdata% folder is attached along as well.

Many thanks in advance for the kind help.
edited by talexeh@hotmail.com on 5/26/2015

rdm_fatal_error.png

RemoteDesktopManager.log.db

All Comments (20)

avatar

Hello,

Under RDM's installation folder, you should see a x86 and a x64 folder. Each of them contain the SQLite.interop.dll for that platform.

Can you double check that they are in there, and that they aren't locked (right-click, properties)

Best regards,

Maurice

avatar

Did you use the installer or the zip file?

David Hervieux

avatar














Yes, both x86 & x64 folders have SQLite.Interop.dll in them.

I checked their Properties windows but don't see any specific "locked" description or label.

avatar





I used the installer files.

avatar

Hi,

Have you tried to install RDM 10.5.4.0 or 10.9.0.0?
http://remotedesktopmanager.com/Home/Download#beta

On a Windows 7 or Windows 8.1 computer, are you able to install RDM without any issue?

Best regards,

Jeff Dagenais

avatar

I'm having the same problem.
I installed RDM Version 2.0.5.0 (11.24.15) on my Windows 8.1 laptop.
The installation went OK without error, but when I start RDM I get the same error as Eng Hong Tan.
These are the details from the messagebox:

System.DllNotFoundException: Unable to load DLL 'SQLite.Interop.dll': Kan opgegeven module niet vinden. (Exception from HRESULT: 0x8007007E)
at System.Data.SQLite.UnsafeNativeMethods.sqlite3_config_none(SQLiteConfigOpsEnum op)
at System.Data.SQLite.SQLite3.StaticIsInitialized()
at System.Data.SQLite.SQLiteLog.Initialize()
at System.Data.SQLite.SQLiteConnection..ctor(String connectionString, Boolean parseViaFramework)
at System.Data.SQLite.SQLiteConnection..ctor(String connectionString)
at Devolutions.RemoteDesktopManager.Business.DataSources.SQLiteConnectionDataSource.CreateDbConnection(String connectionString)
at Devolutions.RemoteDesktopManager.Business.DataSources.DatabaseConnectionDataSource.CreateDbConnection(Int32 connectTimeout)
at Devolutions.RemoteDesktopManager.Business.DataSources.SQLiteConnectionDataSource.c573285c43e8ad00398cc41d47807b7e0()
at Devolutions.RemoteDesktopManager.Business.DataSources.SQLiteConnectionDataSource.get_Version()
at Devolutions.RemoteDesktopManager.Business.DataSources.DatabaseConnectionDataSource.get_IsUpgradeRequired()
at Devolutions.RemoteDesktopManager.Managers.ConnectionManager.get_c051434e45afa78ddb6fe64501cb1cb6d()
at Devolutions.RemoteDesktopManager.Managers.ConnectionManager.Upgrade()
at Devolutions.RemoteDesktopManager.Managers.ConnectionManager.ca4799bebd8b706f34eea94a778843b55(BaseConnectionDataSource c01af917dca3518ff73ed69848f95f91a)

avatar

Hello,
Usually just a simple reboot fixes the problem. Could you try?

David Hervieux

avatar

Hi, thanks for your answer.

Tried the reboot. A well known Windows problem solver. ;)
This time however the problem wasn't solved.

Let me put this a bit in a time line:


















I tried both the msi and exe installation. Nice try, no banana...

What might be the cause and how can I solve it?
Any ideas?

avatar

Hi Leo,

- What happens if you run the 64-bit version of RDM? RemoteDesktopManager64.exe
- Are the following files in the install folder?
- System.Data.SQLite.dll
- x86\SQLite.Interop.dll
- x64\SQLite.Interop.dll
- Any of the above files locked?
- [img]https://forum-api.devolutions.net/api/messages/87875/images/11713[/img]

Stéfane Lavergne

11-25-2015 8-51-54 AM.png

avatar

Hi Stefane,

I can't find RemoteDesktopManager64.exe
I'm running the free version.
All files you refer to are present, none of them is locked.

Regards,
Leo Ooms

avatar

Could you try to unzip it in a new folder not located in program files? For example C:\RDM

David Hervieux

avatar

When I copy the folder from Program Files (x86) to my PortableApps folder and run it from there, everything seems to be ok.
When I try running RDM from Program Files (x86) I get the error again.
I tried to give users change rights to the folder Devolutions in Program Fi... but to no avail. The error keeps showing up.

Anyway, I can run RDM from my PortableApps folder, so I can give it a go now.
I'll look into the problem of the file location at some later time.
If I find something I'll keep you posted.

avatar

Hi,
I gave it another go.
First removed the Devolutions folder from Program Files (x86).
Then I copied the Devolutions folder from the PortableApps folder back to Program Files (x86).
When running RDM as Administrator I encountered no problems.
So I changed the security settings of the Remote Desktop Manager Free folder so that standard users can write to the folder.
Ran RDM as standard user and BINGO! No more error.
Looks like it has everything to do with user rights on the installation folder.
Isn't Windows fun? :)

Regards,
Leo Ooms

avatar

:)

David Hervieux

avatar

Looks like it isn't only about user rights on the installation folder.
After my changes to the security info of the folder I noticed the following:
When I run RDM from the Windows Explorer, so I doubleclick on the exe file directly, it runs ok.
When I run RDM from the Menu Start (shortcut), it produces the error...
The shortcut looks ok to me. But one never knows.
So I created another shortcut on the desktop, doubleclick it... and RDM runs without a problem.
Has Windows gone crazy? :\:

avatar

Could it be related to the Windows program files virtualization?

http://www.symantec.com/connect/articles/folder-virtualization-concepts-windows-vista

David Hervieux

avatar

Leo, thanks for resurrecting this thread of mine. As awkward as it can be, I'm kinda of relieved that I'm not the only to have encountered this issue. :D

Anyway, I have a question. Is your laptop connected to the Internet during the RDM installation?

In my scenario, my machine (which was a VM) is a darksite system therefore I actually had to install the pre-requiresite files manually & I believe those were the culprit.

I had RDM installed in my Windows 8.1 laptop without any issue though.

avatar

I did some more trying.
Looks like it has to do with the location of the shortcut.
When I run the shortcut (as a standard user) from the start menu, the error shows up.
When I copy the shortcut from the start menu to the desktop and run it from the desktop, it runs without a hickup.
If I logon or run RDM as an administrator user, the program runs fine from the start menu too.

To be honest, it's the first time I encounter a problem like this one.
It's weird, to say the least.
Windows sure has some quirks that will surprise us every now and then.

avatar

Perhaps it's related to the working directory of the shortcut. Could you verify if it configured with the application installation path?

David Hervieux

avatar

The shortcut is placed in the standard location for all users:
C:\programdata\microsoft\windows\start menu\programs\Remote Desktop Manager Free
It points to the correct installation location of RDM.

If I copy that shortcut to my desktop or some free accessible folder on my disk, it works flawlessly, from the standard location in the start menu it gets flunked.
Even if I copy the shortcut to the Menu Start in my own userfolder it fails with the dll error.

Short:
- RDM works fine if called from the desktop or a free accessible folder.
- RDM fails if called from the Menu Start.

I will try again this evening on another PC to see what happens there.
That way I can pinpoint if the problem only occurs on my laptop or not.
CU later.

Ends in 12 days