Access issue due to sa account

Question

Access issue due to sa account

Jonathan 360

Hi,

To issue

Microsoft OLE DB Provider for SQL Server Cannot open database "hMailserver" requested by the login.

I can logon on SSMS using the same sa account. I am using Sql server 14.0.1000. Any reason?

0 comments

Answer accepted by question author

Erland Sommarskog 137.1K MVP Volunteer Moderator

The most likely reason would be that the database hMailserver does not exist.

When you log in through SSMS, you will connect to your default database, unless you explicitly select a database. The default database for sa is typically master, which always exists.

When you connect through an application, it's common that the connection string specifies a database explicitly. If you connect and specify non-existing database, connection will fail. Even if you are sa.

By the way, you are running the release version of SQL 2017. You should download and install the last Cumulative Update, CU31 for SQL 2017 to get access to many bug fixes and enhancements.

Jonathan 360 Reputation points

2026-08-21T14:53:32.4666667+00:00

Thanks a lot to all.

Erland,

I used the expressed version and that download is also fine to apply?
Erland Sommarskog 137.1K Reputation points MVP Volunteer Moderator

2026-08-21T15:35:47.3166667+00:00

Yes, the CU applies to all editions.
Jonathan 360 Reputation points

2026-08-24T02:47:27.75+00:00

I tried to set up

SQLServer2017-KB5050533-x64

but got "File is corrupt". Any help?
Erland Sommarskog 137.1K Reputation points MVP Volunteer Moderator

2026-08-24T06:30:22.0933333+00:00

At which point did you get this? I was able to download the file and start the installer. I did not try to install, as I am on CU31 already.

I would suggest that you try to download again, if possible over another network path.
Jonathan 360 Reputation points

2026-08-25T03:53:07.5366667+00:00

I finished the setup of that and rebooted the server but I still got

Code: HM5028, Source: ADOConnection::Connect, Description: Error when connecting to database. Microsoft OLE DB Provider for SQL Server Login failed for user 'sa'.
Erland Sommarskog 137.1K Reputation points MVP Volunteer Moderator

2026-08-25T12:36:59.2466667+00:00

I'm sorry, if it was not clear, but installation of the CU has nothing to do with your login problem. This is something I always point out when I see it, because there is zero reason you should be running with an unpatched version.

The answer for the login failure is something we have already covered in the thread. The database is missing, or not accessible. If you connect through SSMS and say USE hMailserver, what happens?
Jonathan 360 Reputation points

2026-08-28T09:07:32.9+00:00

Good day Erland,

Is it possible to uninstall all of the recent SQL server update below (per the previous download you mentioned) "thoroughly"?
Erland Sommarskog 137.1K Reputation points MVP Volunteer Moderator

2026-08-28T12:45:46.32+00:00

I'm confused. I got the impression that you were able to install CU31, but these are fixes for SQL 2017 RTM. So you did not install CU31 after all? Furthermore, I find that KB5050533 is the Azure Connect Pack, something I would expect only gets installed if you explicitly do so. Is this what you did?

And in any case, this has little to do with your original problem. I pointed out that you were an old version, because this is something I do as a matter of routine. Sometimes installing the recent fixes resolves problem, but since this problem is due to that the the database is inaccessible or non-existing, the CU will not matter.
Jonathan 360 Reputation points

2026-08-31T02:24:54.6933333+00:00

Yes, I set up CU31 (used your suggested download) and any way to uninstall that?
Erland Sommarskog 137.1K Reputation points MVP Volunteer Moderator

2026-08-31T06:46:36.9+00:00

I'm sorry, but I don't understand what you want to do, and more importantly I don't understand why.

Since this has no relation to original problem, I suggest that you ask a new Question and include all details of what you want to do and why. Include the output of "SELECT @@version" in the question.

2 additional answers

Your answer

Jonathan 360 Reputation points

2026-08-21T14:53:32.4666667+00:00

Thanks a lot to all.

Erland,

I used the expressed version and that download is also fine to apply?
Erland Sommarskog 137.1K Reputation points MVP Volunteer Moderator

2026-08-21T15:35:47.3166667+00:00

Yes, the CU applies to all editions.
Jonathan 360 Reputation points

2026-08-24T02:47:27.75+00:00

I tried to set up

SQLServer2017-KB5050533-x64

but got "File is corrupt". Any help?
Erland Sommarskog 137.1K Reputation points MVP Volunteer Moderator

2026-08-24T06:30:22.0933333+00:00

At which point did you get this? I was able to download the file and start the installer. I did not try to install, as I am on CU31 already.

I would suggest that you try to download again, if possible over another network path.
Jonathan 360 Reputation points

2026-08-25T03:53:07.5366667+00:00

I finished the setup of that and rebooted the server but I still got

Code: HM5028, Source: ADOConnection::Connect, Description: Error when connecting to database. Microsoft OLE DB Provider for SQL Server Login failed for user 'sa'.
Erland Sommarskog 137.1K Reputation points MVP Volunteer Moderator

2026-08-25T12:36:59.2466667+00:00

I'm sorry, if it was not clear, but installation of the CU has nothing to do with your login problem. This is something I always point out when I see it, because there is zero reason you should be running with an unpatched version.

The answer for the login failure is something we have already covered in the thread. The database is missing, or not accessible. If you connect through SSMS and say USE hMailserver, what happens?
Jonathan 360 Reputation points

2026-08-28T09:07:32.9+00:00

Good day Erland,

Is it possible to uninstall all of the recent SQL server update below (per the previous download you mentioned) "thoroughly"?
Erland Sommarskog 137.1K Reputation points MVP Volunteer Moderator

2026-08-28T12:45:46.32+00:00

I'm confused. I got the impression that you were able to install CU31, but these are fixes for SQL 2017 RTM. So you did not install CU31 after all? Furthermore, I find that KB5050533 is the Azure Connect Pack, something I would expect only gets installed if you explicitly do so. Is this what you did?

And in any case, this has little to do with your original problem. I pointed out that you were an old version, because this is something I do as a matter of routine. Sometimes installing the recent fixes resolves problem, but since this problem is due to that the the database is inaccessible or non-existing, the CU will not matter.
Jonathan 360 Reputation points

2026-08-31T02:24:54.6933333+00:00

Yes, I set up CU31 (used your suggested download) and any way to uninstall that?
Erland Sommarskog 137.1K Reputation points MVP Volunteer Moderator

2026-08-31T06:46:36.9+00:00

I'm sorry, but I don't understand what you want to do, and more importantly I don't understand why.

Since this has no relation to original problem, I suggest that you ask a new Question and include all details of what you want to do and why. Include the output of "SELECT @@version" in the question.

Answer 1

Deepesh Dhake 1,165

The login is fine. This error means the database couldn't be opened, not that authentication failed. SSMS connects to master by default, so a successful SSMS login doesn't confirm hMailserver itself is accessible.

Please run:

SELECT name, state_desc FROM sys.databases;

Then check whether hMailserver is listed, spelled/cased exactly right, and shows ONLINE. If it's missing, offline, or named differently, that's your cause.

Jonathan 360 Reputation points

2026-09-01T06:39:05.8366667+00:00

OK. I will raise the other issue if needed. Thanks.

Answer 2

If sa can connect in SSMS but the OLE DB connection fails with Cannot open database "hMailserver" requested by the login, the most likely cause is not the sa password itself, but the database being requested at login time.

Check these items:

Verify the database name in the OLE DB connection string
- Confirm that hMailserver exists on the target SQL Server instance.
- Confirm the connection is going to the correct server and instance.
- If a named instance is used, include the instance name.
Check whether hMailserver is available
- If the login’s default database or the database specified in the connection string is offline or unavailable, login can fail even when the same login works elsewhere.
- In SSMS, try connecting and then explicitly selecting an available database in Connection Properties.
Compare SSMS and application connection targets
- A common cause is that SSMS is connecting to the correct server, but the OLE DB provider is pointing to a different server or instance.
- Validate the server name in the connection string carefully.
Test the exact OLE DB connection outside the application
- Use a UDL file and select the same OLE DB provider.
- On the Connection tab, enter the server as FQDN and port, for example: tcp:SQLProd01.contoso.com,1433
- Then select Test Connection.
- This helps confirm whether the issue is the provider settings or the application configuration.
Review the connection string syntax
- Make sure it includes the correct server name, database name, user name, and password.
- If the database name is wrong, or the server is wrong, SQL Server can return the database-open/login failure.
Check SQL Server error details
- SQL Server Errorlog can show whether the failure is due to:
  - wrong server/instance
  - wrong database name
  - failed to open the database specified in login properties
  - incorrect password

Since sa works in SSMS, the strongest candidates are:

the OLE DB connection string points to a different server or instance
hMailserver is specified in the OLE DB connection but is offline, unavailable, or incorrect
the application is using different connection properties than SSMS