My integration was running fine, but then I had to delete our TEST SQL database – TWO00. After doing so, my map fails with the error:
Parameter set value event.
Cannot open database ‘TWO00’ requested by the login. The Login failed.
Login failed for user ‘sa’.
If you’d like to watch a video explaining why your integration fails after removing a SQL database, see below or click here.
Fixing the Error Caused by Removing a SQL Database
I know the credentials being used for the ‘sa’ login are good, and since the destination company is not the TWO00 database per the screenshot, the login error is puzzling.
Typically, SQL Login Errors would be due to user/password issues, but SQL gives a specific message about that with an indication of “user/password is not correct”
The message clearly suggests that it is a login issue, so it doesn’t seem like it is a SQL Permissions type of error due to the ‘sa’ user being sysadmin, which would have the correct permissions for anything.
From the message, the only reason to get this type of error would be that the database no longer exists. I have confirmed that the database has been deleted, and that the database that is failing to log in is the same database that gives us the database failure error. But it does not give you the “why” since it does not seem like that database is being accessed anywhere.
The clue in the error message is what SmartConnect was trying to do: set the Primary Address ID.
If this was regular source field, we wouldn’t see a “SQL” error. This suggests that either the field is being set by an MS SQL Lookup or a Calculation that is making a SQL Connection, and that is what is failing to connect. But again, why, since we aren’t connecting to that database for this integration?
The reason is both the Calculation and the MS SQL Lookup are using are both using the same MS SQL Connection.
The default Database in the connection is set to the non-existent TWO00 database.
When the MS SQL Lookup tried to connect using that same initial connection, it tried to connect to that same default database. Since it doesn’t exist, the connection fails with the login error we see. If it had tried to re-connect using the actual target database, that should have been successful, but the code never gets that far and fails at the first exception.
The simple solution to this problem is to switch the Database Default to another database that does exist. We would suggest the “master” database since that will always exist and so that initial connection would never fail.
After switching that connection to be “master” and resaving the SQL Server Connection, the map once again runs successfully.
If you have more questions on how to fix the error caused by removing a SQL database, contact our team at support@eonesolutions.com.
