Failed to open the explicitly specified database ошибка

Since a little while I’m having the same problem. MY connection string specifically states a user and password to use for logging in. However on one of my application pages I’m getting the same error, all others are working perfectly fine.

It worked perfectly fine on my test server previously so I thought it might be due to a received update? So I started de-installing some recent .NET updates and found this:
Initial error:
Login failed for user ‘NT AUTHORITYANONYMOUS LOGON’.

Then after de-installing KB2901126 & KB2898869 the error changes to:
Login failed for user ‘DOMAINCOMPUTERNAME$’.

Note that both of those updates are security patches which prevent users of getting elevated rights:

From KB2901126

This update resolves vulnerabilities that could allow elevation of privilege if a user visits a specially crafted website or a website that contains specially crafted web content.

So I then wanted to re-install both updates again but I get this message:
Windows update error message

Notice the error, 80244022. The error occurs because of a connection interruption between my server and the update server. Bit weird since the other updates successfully manages to download and install itself.

MS might have removed the updates? I’m not sure what’s happening but I’m fairly sure this is happening because of a MS update. No way my «working» app went from working to 1 broken page within 2 weeks without me even updating code from that specific page (or references behind it).

I’m going to try to see whether the same update on my DEV machines could have broken my build.

As a workaround I created a domain account and granted it access to the database, then I switched the app pool to this domain account. Without DB rights, and without editing the connecting string, the error on the specific page changed to «DOMAINnew account» is unable to access the db. This confirms that for some reason that specific page, and the code behind, disregards the UID & PW in the connection string and uses integrated security.

• Hi,

  We have sql server 2008 x64 instance with SP1. When ever SQL Serve instance got restarted, I’m seeing the below error in log:

  Error: 18456, Severity: 14, State: 38.

  2011-07-04 17:38:57.95 Logon Login failed for user ‘abcmssqlsrv’. Reason: Failed to open the explicitly specified database. [CLIENT: <local machine>]

  Could you please advice

  Thanks

• Welsh Corgi

  SSC Guru

  Points: 116520

  What did you do before you restarted the Server?

  Check the default database for the User.

  Is it offline or in suspect mode, etc?

  Did you restore the database and have orphan users.

  If you change the default database can the user log on?

• gary1

  SSC-Insane

  Points: 21152

  What did you do before you restarted the Server?

  Nothing Just a restart of the sql service

  Check the default database for the User.

  Master database

  Is it offline or in suspect mode, etc?

  No

  Did you restore the database and have orphan users.

  No

  If you change the default database can the user log on?

  It’s a service account. The default database is Master and I did not try changing it

  Thanks

• Welsh Corgi

  SSC Guru

  Points: 116520

  Why did you restart the service?

  It is an account for what service?

  Is this user account the only that you are having problems with?

  What else is in the log? Did the master database start before the login attempt?

• Leo.Miller

  SSChampion

  Points: 13035

  There’s a good change this is some proces that is using the ‘abcmssqlsrv’ account to connect to a database that has not yet been brought on line.

  One hint is the fact that it says «the explicitly specified database». This implies the connection sting requests an initial catalog and isn’t relying on the default. Since it’s comming from the local machine you need to check what all on the server is running uner this account. If it’s a service you may need toput in some sort of control to prevent it from starting so quickly, or just ignore the error if it isn’t fatle for the app.

  On Windows 2003 servers it’s a real pain getting services to start after a delay. You typlically have to put them in manual mode, then use a scheduled task to start them, and have a special batch process to delay the start. This is a lot easier in Windows 2008, you still need to use a scheduled task, but the scheduler has a delay option.

  Cheers

  Leo

  Leo
  Nothing in life is ever so complicated that with a little work it can’t be made more complicated.

• Ignacio A. Salom Rangel

  SSC-Insane

  Points: 20443

  Did you find out what was causing the problem?

• stephen.lappe

  SSChasing Mays

  Points: 608

  My organization has just started to transition to 2008 R2 and I have seen this error on a couple of our legacy databases.

  I have tried the following to no avail:

  Change default database to the user database.

  Given the account explicit connect rights to Master

  Synch’d the user with the sp_change_users_login.

  So, for now those databases are going to stay on the legacy 2005 instance until we can resolve the issue. MS and googling for 18456 state 38 does not provide much in the way of useful information.

• Ignacio A. Salom Rangel

  SSC-Insane

  Points: 20443

  stephen.lappe (7/28/2011)

  ---

  My organization has just started to transition to 2008 R2 and I have seen this error on a couple of our legacy databases.

  I have tried the following to no avail:

  Change default database to the user database.

  Given the account explicit connect rights to Master

  Synch’d the user with the sp_change_users_login.

  So, for now those databases are going to stay on the legacy 2005 instance until we can resolve the issue. MS and googling for 18456 state 38 does not provide much in the way of useful information.

  Have you tried connecting to the SQL Server using that domain account?

• stephen.lappe

  SSChasing Mays

  Points: 608

  account connects just fine through SSMS(domain account), but when credentials (domain account) are presented through an application connection string we get the state 38 error

• Leo.Miller

  SSChampion

  Points: 13035

  Ignacio A. Salom Rangel (7/28/2011)

  ---

  stephen.lappe (7/28/2011)

  ---

  My organization has just started to transition to 2008 R2 and I have seen this error on a couple of our legacy databases.

  I have tried the following to no avail:

  Change default database to the user database.

  Given the account explicit connect rights to Master

  Synch’d the user with the sp_change_users_login.

  So, for now those databases are going to stay on the legacy 2005 instance until we can resolve the issue. MS and googling for 18456 state 38 does not provide much in the way of useful information.

  Have you tried connecting to the SQL Server using that domain account?

  Have you checked the order of events in the event log? Did you try confirm that some of the databases are still not available when this error occures? This is what it looks like, and if the connection string is using an initial-cataloge, then none of the changes you have tried above will help because you would need to chane the applications connection request.

  I’ve seen this a number of times, if you can identify the application and if it comes on line once the database is available, then the error is normaly nothing more than an iritation. There are a lot of apps out there that should be stopped when their underlying SQL server is stopped. If you don’t they sit trying to connect until the server comes back.

  Cheers

  Leo

  Leo
  Nothing in life is ever so complicated that with a little work it can’t be made more complicated.

• stephen.lappe

  SSChasing Mays

  Points: 608

  Negative. Databases are up. Application connection strings coded properly. When the app tries to connect we get a 18456 state 38 error. Application has no problem connecting to the orginal 2005 instance. We have no problem logging into the databserver using the application service account through SSMS on the new 2008 instance. Other applications that are coded with the same .NET framework and connect to the DB without a problem.

• Ignacio A. Salom Rangel

  SSC-Insane

  Points: 20443

  stephen.lappe (8/1/2011)

  ---

  Negative. Databases are up. Application connection strings coded properly. When the app tries to connect we get a 18456 state 38 error. Application has no problem connecting to the orginal 2005 instance. We have no problem logging into the databserver using the application service account through SSMS on the new 2008 instance. Other applications that are coded with the same .NET framework and connect to the DB without a problem.

  Maybe it is time to get your system administrators (AD administrators & network administrators) involved!

• webtomte

  Ten Centuries

  Points: 1125

  We have SQL 2008 R2 (x64) on MS Server 2008 R2 with all the SP including SP2 for SQL Server 10.50.4000.

  This is a new server and we started using it yesterday.

  The service account starting the services giving «Error: 18456, Severity: 14, State: 38» numerous times during last day.

  Service account is sysadmin, Local admin and have all the rights it needs, still error.

  Tried restart service, restart server still reporting error in the log.

  Microsoft said this would be solved by SP1 for SQL server but parently not.

  Any one out there who can come up with a solution for this.

  I have an exactly the same configuration on another SQL Server only using SP1 so far. There I do not have this problem.

  So what is causing this.

• Ignacio A. Salom Rangel

  SSC-Insane

  Points: 20443

  webtomte (9/6/2012)

  ---

  We have SQL 2008 R2 (x64) on MS Server 2008 R2 with all the SP including SP2 for SQL Server 10.50.4000.

  This is a new server and we started using it yesterday.

  The service account starting the services giving «Error: 18456, Severity: 14, State: 38» numerous times during last day.

  Service account is sysadmin, Local admin and have all the rights it needs, still error.

  Tried restart service, restart server still reporting error in the log.

  Microsoft said this would be solved by SP1 for SQL server but parently not.

  Any one out there who can come up with a solution for this.

  I have an exactly the same configuration on another SQL Server only using SP1 so far. There I do not have this problem.

  So what is causing this.

  Which service are you starting with the service account?

• webtomte

  Ten Centuries

  Points: 1125

  All services used in SQL is using the same service account

1. I can login using SSMS with the port given. I see these database: CustomerManagement, Invoicing, Notification, VehicleManagement, WorkshopManagement.

2. Error persist.

3. I installed Docker Desktop, with Kitematic. I can see a list of containers at left, and when I go for Settings, Advanced, I didn’t see anything to adjust the CPU/Memory.
   
   

4. The output of the file:
   [
   {
   «Id»: «sha256:314918ddaedfedc0345d3191546d800bd7f28bae180541c9b8b45776d322c8c2»,
   «RepoTags»: [
   «microsoft/mssql-server-linux:latest»
   ],
   «RepoDigests»: [
   «microsoft/mssql-server-linux@sha256:9b700672670bb3db4b212e8aef841ca79eb2fce7d5975a5ce35b7129a9b90ec0»
   ],
   «Parent»: «»,
   «Comment»: «»,
   «Created»: «2018-12-17T19:37:22.052136555Z»,
   «Container»: «ad4994d21cb3a364fcac4e419fd5827e1723c86e767a321876c49f8f75c7d132»,
   «ContainerConfig»: {
   «Hostname»: «4dcf0239b565»,
   «Domainname»: «»,
   «User»: «»,
   «AttachStdin»: false,
   «AttachStdout»: false,
   «AttachStderr»: false,
   «ExposedPorts»: {
   «1433/tcp»: {}
   },
   «Tty»: false,
   «OpenStdin»: false,
   «StdinOnce»: false,
   «Env»: [
   «PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin»
   ],
   «Cmd»: [
   «/bin/sh»,
   «-c»,
   «#(nop) «,
   «CMD [«/opt/mssql/bin/sqlservr»]»
   ],
   «ArgsEscaped»: true,
   «Image»: «sha256:becb2cc726794b29b88a3a2a82cf524080b551b81b67f143fefc2970310fb6c8»,
   «Volumes»: null,
   «WorkingDir»: «»,
   «Entrypoint»: null,
   «OnBuild»: [],
   «Labels»: {
   «com.microsoft.product»: «Microsoft SQL Server»,
   «com.microsoft.version»: «14.0.3048.4»,
   «vendor»: «Microsoft»
   }
   },
   «DockerVersion»: «1.13.0»,
   «Author»: «dpgswdist@microsoft.com»,
   «Config»: {
   «Hostname»: «4dcf0239b565»,
   «Domainname»: «»,
   «User»: «»,
   «AttachStdin»: false,
   «AttachStdout»: false,
   «AttachStderr»: false,
   «ExposedPorts»: {
   «1433/tcp»: {}
   },
   «Tty»: false,
   «OpenStdin»: false,
   «StdinOnce»: false,
   «Env»: [
   «PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin»
   ],
   «Cmd»: [
   «/opt/mssql/bin/sqlservr»
   ],
   «ArgsEscaped»: true,
   «Image»: «sha256:becb2cc726794b29b88a3a2a82cf524080b551b81b67f143fefc2970310fb6c8»,
   «Volumes»: null,
   «WorkingDir»: «»,
   «Entrypoint»: null,
   «OnBuild»: [],
   «Labels»: {
   «com.microsoft.product»: «Microsoft SQL Server»,
   «com.microsoft.version»: «14.0.3048.4»,
   «vendor»: «Microsoft»
   }
   },
   «Architecture»: «amd64»,
   «Os»: «linux»,
   «Size»: 1353110161,
   «VirtualSize»: 1353110161,
   «GraphDriver»: {
   «Data»: {
   «LowerDir»: «/var/lib/docker/overlay2/08196c17518227a63394f8edbfba8772e50e38f1212327d71a4ba880d031b261/diff:/var/lib/docker/overlay2/cac1716072ca4175d6f117b13c08d3106b3b3502ec1c741e2af6cb100ff2c992/diff:/var/lib/docker/overlay2/3360cfdce7995cd50bf3f0245cef1c6ac3bd915b5f14abb9bed9112e23d5fafc/diff:/var/lib/docker/overlay2/c60606cc74efc4ee86a77b7e218a14c1d7ae4d6fbb90ea2be5d416d9246a108c/diff:/var/lib/docker/overlay2/e0b6b3716b86d38f72bde18537f611cab9b6105bf06be59fb879a93ad377486a/diff:/var/lib/docker/overlay2/13edd7fb69258dc38599901040727c1ee0fc8139613179422c11fd02f7d518b3/diff:/var/lib/docker/overlay2/73abb0ed3e4393f13982a4159a4fe458a695e6fede891a079f0f9162f4b2e6ab/diff:/var/lib/docker/overlay2/9933000f6efd6cbf4a8458c5fe7b235a435d4c5a7777c242322d3fac76d24065/diff»,
   «MergedDir»: «/var/lib/docker/overlay2/478e285b250a718ee8ecd31027c99abfe85aece8de68035dee35c4175797e24a/merged»,
   «UpperDir»: «/var/lib/docker/overlay2/478e285b250a718ee8ecd31027c99abfe85aece8de68035dee35c4175797e24a/diff»,
   «WorkDir»: «/var/lib/docker/overlay2/478e285b250a718ee8ecd31027c99abfe85aece8de68035dee35c4175797e24a/work»
   },
   «Name»: «overlay2»
   },
   «RootFS»: {
   «Type»: «layers»,
   «Layers»: [
   «sha256:644879075e24394efef8a7dddefbc133aad42002df6223cacf98bd1e3d5ddde2»,
   «sha256:d7ff1dc646ba52a02312b535446d6c9b72cd09fda0480524e4828554efb2f748»,
   «sha256:686245e78935e73b737c9a82111c3c7df35f5529d06ce8c2f9a7cd32ec90b456»,
   «sha256:d73dd9e652956dccbbef716de4b172cc15fff644cc92fc69d221cc3a1cb89a39»,
   «sha256:2de391e51d731ba02b708038a7f98b7103061b916727bcd165e9ee6402f4cdde»,
   «sha256:d33a8ef9dea5016c8647174b5580425f021385b9ab87453cd7508587c030305c»,
   «sha256:911ad08015cfe167b552e1c330220f90e4ff82f572bfb309f7e3afab619d71fc»,
   «sha256:be08dc7c21612388e812298a006b9fd65095b985de77c71d62f20008945997a6»,
   «sha256:79b07b78f674ac90913b63152a2cf7060d363552b6174cc966bd841569b7fb95»
   ]
   },
   «Metadata»: {
   «LastTagTime»: «0001-01-01T00:00:00Z»
   }
   }
   ]