Local Database
This page is relevant for MetaDefender Managed File Transfer™ versions prior to 3.9.2
Insufficient RAM for LocalDB Creation
An error such as "Failed to create a tenant" in the log file may indicate insufficient RAM for creating a LocalDB.
Resolution
To resolve this issue:
- Examine the installed log file for entries indicating "Failed to create a tenant."
- Identify and terminate non-essential processes consuming system memory.
- Attempt to create the LocalDB instance again after freeing up sufficient memory.
Conflict in LocalDB Preventing Creation of a New Instance
Conflicts in LocalDB that prevent the creation of a new instance can arise due to several factors, such as database corruption, ongoing processes, or other environmental issues. These conflicts can hinder the successful creation of a new LocalDB instance. Following the steps below will help resolve the conflict by stopping and deleting the conflicting LocalDB instance, allowing for the creation of a new one without disruptions.
Resolution
To resolve this issue:
- Open the "PSTool" folder using an Administrator command prompt.
- Run the following command to initiate SQL PSExec:
PSExec -i -s -d cmd
- Display SQL LocalDB information using the command:
sqllocaldb i
- Stop the conflicting LocalDB instance with:
sqllocaldb stop <instance-name>
- Delete the conflicting LocalDB instance using:
sqllocaldb delete <instance-name>
After completing this step, try to install LocalDB again.
Was this page helpful?