TN - 1497 Resolving the following error: From Microsoft OLE DB Driver for SQL Server. Cannot open database "****" requested by the login
Last updated: December 18th, 2025Description
- Author: Glenn Yancey
- Published: December 18th, 2025
Details:
The following technote from InSource shows to resolve the following issue:
ISSUE:
When migrating a Galaxy from one node to another new node with (2023 R2 SP1 P2), one could receive these error messages when restoring your galaxy through the IDE (BackupGalaxies).
This doesn't affect creating a new galaxy from other backup templates from different sources. The user that I logged into my VM image with is also the aaAdminUser with full Admin rights in both SQL server (SysAdmin) and in the OS.
ERRORS:
- Microsoft.Data.SqlClient.SqlError: Cannot open backup device 'C:\ProgramData\tmprestore\Database\database.backup'. Operating system error 3(The system cannot find the path specified.).
- From Microsoft OLE DB Driver for SQL Server. Cannot open database "****" requested by the login. The login failed.. Unspecified error (80004005) caught at line 12016 in Cdi.cpp (in D:\ADO\Work\69\s\src\WWCdi\).
- Application is unable to connect to the SQL Server database. Please ensure that SQL Server is configured to allow proper access to the ArchestrA Network User using aaConfig SQL utility and retry the operation.

The issue is NOT related to the aaConfigSQL program needing to be set to Legacy mode. However it is caused on the backup side. Somehow, the backup is rendered useless as it does not contain a folder called Database. The example below show what the CAB file is supposed to look like inside.
HINT: You can look at the files and folder inside of the backup file (.CAB) by changing the file extension from .CAB to .ZIP. Then you can open it up like a zipped folder.

RESOLUTION:
To resolve, you must be on the machine where the backup is performed, and then create the CAB file again. If the logger shows the exception with the Microsoft.Identity.Client, the solution is the following:
Copy the 'Microsoft.Identity.Client.dll' from
"<installpath>\ArchestrA\Framework\Bin\SMOSupport" and paste it to "<installpath>\ArchestrA\Framework\Bin\". REBOOT and try creating the CAB file again.
NOTE: <installpath> could be C:\Program Files (x86)\ or D:\Program Files (x86)\, which depends on the drive where the software was installed.
Recommended articles
[ISS Support Case] PLC Communication Failure
Client reached because after user migrated the Galaxy none of the tags are communicating.
Read More[ISS Support Case] Batch 2023 R2 license acquisition failure
Batch is failing to acquire a license from client's consignment license.
Read More[ISS Support Case] SQL scripts stopped executing Post 2020 Upgrade
InTouch and SQL script we had an existing application and SQL database upgraded to 2020 about a year a go. Brought from 2014 -> 2020 Updated to 64 - bit Scripts are no longer sending Not sending in the logs not familiar with SQL (profiler logs etc) Analog tags 15 periodically run a report for the day super light weight. Built new database new tables in an effort to eliminate any permission issue. Standalone application. Time based trigger and assigned to button action script
Read More