This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(3.2, 69%, 10%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EO%3C/text%3E%3C/svg%3E)
Every once in awhile our ETL jobs in SSIS fail. The error message looks like this:
Login failed for user 'TEAMASP\SQLAdmin'. Reason: Failed to open the explicitly specified database '$Project::BICfg_Svr'
As you can see, I have a parm at the project level. But SSIS is not pulling in the parm value, and instead is literally trying to connect to a database named what my parm name is?
A Microsoft platform for building enterprise-level data integration and data transformations solutions.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(96, 26%, 19%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EYK%3C/text%3E%3C/svg%3E)
What is your SQL Server/SSIS run-time environment version?
Please issue the following statement, and share its result:
SELECT @@VERSION;
Microsoft SQL Server 2017 (RTM-CU18) (KB4527377) - 14.0.3257.3 (X64)
Nov 16 2019 01:14:50
Copyright (C) 2017 Microsoft Corporation
Enterprise Edition (64-bit) on Windows Server 2012 R2 Standard 6.3 <X64> (Build 9600: ) (Hypervisor)
I should have mentioned that this only happens intermittently so there's got to be a correlation to something else -- high cpu, slow network, etc?
Answer accepted by question author
The consensus is that our SQL Server that produced this error has not been patched since 2019. The suggestion is to patch it to current, and then test the behavior to see if the issue still exists in the latest CU, and then if so, raise the issue.
Hi @OmaCoder ,
This bug was already fixed by Microsoft.
As @CarrinWu-MSFT mentioned, it is documented here: kb4486936-fix-login-failed-for-user-error-occurs-when-you-run-maintenance-plan-with-sql-login-account-in-sql-server
Your current CU18 is dated back to 2019.
Please update your SQL Server/SSIS run-time environment with the latest CU, which is CU24.
You can see it here: Microsoft SQL Server Versions List
That KB is unrelated to this issue. Different error messages, and we're not using a sql login account.
Still, you instance was last patched in 2019.
It is a good idea to install the latest CU.
Thanks for the input @Yitzhak Khabinsky
Running a production farm with 90 servers makes it a bit hard to ask infrastructure to install the latest CU because it seems like a good idea.
If this was fixed in a patch then there should be a KB.
There is no justification to run SQL Server with two year old patches.
"...Since January 27, 2016: Microsoft recommends ongoing, proactive installation of SQL Server CUs as they become available. SQL Server CUs are certified to the same levels as Service Packs, and should be installed with the same level of confidence..."
Service Packs are discontinued starting from SQL Server 2017. Only Cumulative Updates (CUs) will be provided.
It is a message directly from Microsoft.
Thank you for that information! That will be helpful in my request to infrastructure for an update. Wish me luck!
Hi @OmaCoder ,
Welcome to Microsoft Q&A!
Have you check the SQL Server error log before? And find some error like below. If yes, this error had been fixed by KB4486936.
DateTime Logon Error: 18456, Severity: 14, State: 8.
DateTime Logon Login failed for user 'UserName'. Reason: Password did not match that for the login provided. [CLIENT: <LocalMachine>]
Best regards,
Carrin
If the answer is helpful, please click "Accept Answer" and upvote it.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.
Yes, I checked the SQL Server error log. The error from the log is what I pasted when I opened this Q&A.
The error you pasted is a different error that we are not receiving.
Hi @OmaCoder , I read the discussion about you and YitzhakKhabinsky-0887. Good to know that you are going to update the SQL Server. Could you please do "Accept Answer" for this thread? By doing so, it will benefit for community members who have this similar issue. Your contribution is highly appreciated. Thank you!
The only two answers refer to KB4486936, which is not the correct answer and is completely unrelated to my question. Marking this as answered will mislead other community members with the same issue as mine.