Ошибка sql сервер 4060

SQL error 4060 “Server rejected the connection; Access to the selected database has been denied” is a common error usually seen after website migration in Windows servers.

The reasons for this error include permission issues, firewall restrictions, etc.

As a part of our Server  Management Services, we help our customers to fix SQL related errors regularly.

Let’s today discuss the possible causes and fixes for this error.

What causes SQL error 4060?

Often after a migration, some users notice SQL error 4060 while applications or websites. This error states that the “Server rejected the connection; Access to the selected database has been denied“. As the error message states, access to the database was denied as the server rejected the connection.

To list out, the common reasons for this error include:

• No permission to access the database using the credentials
• Protocol not enabled
• Firewall blocking access

Lets us now look into each of these reasons in detail and the possible fix for them.

Lack of Permission

The most common reason for the error 4060 is the lack of permission for the user to access the database. After migration, it is important to ensure that all the users in the previous environment are set up in the new environment as well with the required privileges. However, this is often a frequently missed point.

Correct permissions can be granted to the users with a proper TSQL command. A general format of the command is

GRANT  [ ,...n ]
TO  [ ,...n ] [ WITH GRANT OPTION ]
[ AS  ]

For instance, to grant SHOWPLAN permission on the Example database to application role Moderator, TSQL command to be used is:

USE Example;
GRANT SHOWPLAN TO Moderator;
GO.

Similarly, we could grant the required privileges to the user after comparison with that of the permission in the old environment.

Protocol not enabled

To connect to SQL Server Database Engine you must have a network protocol enabled. If those are not enabled, it may trigger the error 4060.

The steps to enable them are:

• First, select Start, and in your list of programs, select SQL Server Configuration Manager.

• Next, navigate to SQL Server Configuration Manager > SQL Server Network Configuration > Protocols for .

  

• Then, double-click Named Pipes. The Named Pipes Properties screen appears.

• From Enabled, select Yes. Then click OK.

  

• Similarly to enable TCP/IP, we can select TCP/IP as in step 2. The TCP/IP Properties screen appears.

• Next, on the Protocol tab, ensure Yes is selected for Enabled. On the IP Addresses tab, ensure that Yes is selected for the appropriate IP Address. Also, ensure that the appropriate TCP Port is indicated. Then click ok.

• Finally, from SQL Server Management Studio, restart the server instance.

  

Firewall blocking Access

Firewall restrictions can also trigger the error 4060. To fix it, we need to allow access in firewall. Generally, a closed port is the most common restriction that Firewall places. To fix it, we need to open the port in the firewall for the client.

Apart from the common reasons mentioned above, some other reasons can also trigger this error. In a rare case scenario, this error could also indicate that the corresponding database is not copied over to the new environment. Thus it is not a bad idea to cross-check if the database is actually copied over before we go for any other complex fixes.

[Need help to fix SQL errors? We are available 24×7]

Conclusion

In short, lack of permission for users to access database, firewall restriction etc trigger the error 4060. Today, we discussed how our Support Engineers fix the error “Server rejected the connection; Access to the selected database has been denied”.

var google_conversion_label = «owonCMyG5nEQ0aD71QM»;

Symptoms

In Microsoft Dynamics SL 2011, you try to log on to a new, Windows authenticated, Microsoft Dynamics SL application database. However, when you try to log on, you receive the following error message:

Fatal SQL Error 4060 Occurred during Company login

Cause

This problem occurs when the user ID that you use to log on to Microsoft Dynamics SL is not mapped to the new application database in Microsoft SQL Server.

Resolution

Hotfix information for Microsoft Dynamics SL

A supported hotfix is now available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next Microsoft Dynamics SL Service Pack that contains this hotfix as specified in the «Status» section in this article.

To resolve this problem, click the «View and request hotfix downloads» link at the top of this article to obtain the hotfix.

Note If additional issues occur or any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. To create a separate service request, visit the following Microsoft website:

http://support.microsoft.com/contactus/?ws=support

File information

The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.

Microsoft Dynamics SL 2011

Changed Files	Date	File Version
SWIMAPI.DLL	29-Sept 2011	8.0.20929.00
SOLOMON.KERNEL.DLL	29-Sept 2011	8.0.20929.00
Microsoft.dynamics.SL.Reporting.dll	29-Sept 2011	8.0.20929.00
QQVIEW00.exe	29-Sept 2011	8.0.20929.00
9829000.exe	29-Sept 2011	8.0.20929.00
Soldb.dll	29-Sept 2011	8.0.20929.00
lli.dll	29-Sept 2011	8.0.20929.00
SAFMenuStrip.dll	29-Sept 2011	8.0.20929.00
Toolbarenu.dll	29-Sept 2011

Installation information

Install this hotfix by following the installation instructions that are included in the hotfix download.

Prerequisites

For information about the prerequisites for this hotfix, see the installation instructions that are included in the hotfix download.

Restart requirement

If you are prompted, restart the computer after you install the hotfix.

Removal information

You cannot remove this hotfix.

Status

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the «Applies to» section.

This problem was reported as issue number 23832.

More Information

For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:

824684 Description of the standard terminology that is used to describe Microsoft software updates

«Fatal SQL Error 4060» occurs when you try to log on to a new application database in Microsoft Dynamics SL

Symptoms

In Microsoft Dynamics SL 2011, you try to log on to a new, Windows authenticated, Microsoft Dynamics SL application database. However, when you try to log on, you receive the following error message:

Fatal SQL Error 4060 Occurred during Company login

Cause

This problem occurs when the user ID that you use to log on to Microsoft Dynamics SL is not mapped to the new application database in Microsoft SQL Server.

Resolution

Hotfix information for Microsoft Dynamics SL

A supported hotfix is now available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next Microsoft Dynamics SL Service Pack that contains this hotfix as specified in the «Status» section in this article.

To resolve this problem, click the «View and request hotfix downloads» link at the top of this article to obtain the hotfix.

Note If additional issues occur or any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. To create a separate service request, visit the following Microsoft website:

File information

The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.

Источник

Microsoft sql server error 4060

This forum has migrated to Microsoft Q&A. Visit Microsoft Q&A to post new questions.

Asked by:

Question

Problem: see JPEG image attached regarding the error message I get when I try to insert a single row in a table. SQL Error 4060.
I can access this database, CutSysDB, in Sql Server Management Studio, SSMS, and insert values in each of the five tables that comprise
the database which runs under Windows 7, Visual Studio 2008 Standard SP1, SQL Server Express 2008 R2 SP1.

When I try to add the first row in the empty table with my VS2008/Visual Basic 2008 project under Debug, I get the 4060 sql error.
Before you expend to much effort on this, you should first look at the following thread that Cathy is suggesting may be due to a
VS2008 SP1 install problem: Terry01 Thread — Studio Setup and Installation/Visual Studio 2008/devenv.exe

Login to SQL Server using Management studio and go to Security. Select ‘Terry-HPTerry’ login, in newly opened screen of Login Properties you will have User Mapping section. In that window give permission to databases in which this user required permission. On the lower screen, click the role db_owner. Click OK.

Please remember to mark the replies as answers if they help and unmark them if they provide no help. This can be beneficial to other community members reading the thread.

I believe I followed your instructions, but to no avail. My Login Properties screen is included as a JPEG for your review. Where do I go from here?

By the way, when I try to create a new login I get the above screen but the master, model, msdb, tempdb and db owner check boxes are unchecked. Where do i go from there? I’ve tried a number of different combinations and none of them seem to work. I get an error message quite a bit about dbo object creating an error and login update fails.

The following is the screen I see when I try a new login as you suggested. Nothing I’ve tried will work. I can’t get a database to show in «Map Database listbox.

I could not see that the user ‘Terry-HPTerry’ is mapping with database CutSysDB. Is C:VISUAL STUDIO the database CutSysDB?

Please remember to mark the replies as answers if they help and unmark them if they provide no help. This can be beneficial to other community members reading the thread.

Maggie, that is my question. How do I get the database into the new login? And, if I do, with your answer, what do I use as the user id, the same as the current one ‘Terry-HPTerry’?

Here is another try at trying to change my login. This happens no matter what I chose, only the object changes.

A valid user account within a database is required to access that database. User accounts are specific to a database. All permissions and ownership of objects in the database are controlled by the user account. SQL Server logins are associated with these user accounts. A login can have associated users in different databases, but only one user per database.

Please remember to mark the replies as answers if they help and unmark them if they provide no help. This can be beneficial to other community members reading the thread.

Maggie, you are not reading or interpreting my replies to you. I ask a question and I get some info to read. I don’t mind the reading, but I expect a direct answer to my question. If you need more infor to answer it, ask.

Maggie, I’m getting more than frustrated, because nothing you’ve suggest works or makes sense to me!
I have two SSMS login ids, and none of them work. I’ve read most articles available on this subject,
including the ones you suggested. None appear to help me.
My two Login IDs are:Terry-HPTerry which is computerme as administrator and only user of this pc, and
TERRYAdministrator.

You aren’t helping me, only delaying the resolution. I believe I’ve done everything you’ve suggested,
and nothing works. What do I need to give you to get this issue resolved?

Источник

При попытке войти в новую базу данных приложения в Microsoft Dynamics SL появляется сообщение «Неустранимая ошибка SQL 4060»

Проблемы

В Microsoft Dynamics SL 2011 вы пытаетесь войти в новую базу данных приложения Microsoft Dynamics SL с проверкой подлинности Windows. Однако при попытке входа в систему появляется следующее сообщение об ошибке:

Произошла неустранимая ошибка SQL 4060 при входе в компанию

Причина

Эта проблема возникает в том случае, если идентификатор пользователя, который вы используете для входа в Microsoft Dynamics SL, не сопоставлен с новой базой данных приложения в Microsoft SQL Server.

Решение

Сведения об исправлении для Microsoft Dynamics SL

Поддерживается исправление, выпущенное корпорацией Майкрософт. Однако это исправление предназначено для устранения только проблемы, описанной в этой статье. Применяйте это исправление только для систем, в которых наблюдаются указанные выше проблемы. Это исправление может получать дополнительное тестирование. По этой причине корпорация Майкрософт рекомендует во всех случаях, когда проблема не представляет особой важности, дождаться следующего пакета обновления для Microsoft Dynamics SL, содержащего это исправление, как указано в разделе «состояние» этой статьи. Чтобы устранить эту проблему, щелкните ссылку «просмотреть и запросить исправления» в верхней части этой статьи, чтобы получить исправление. Примечание Если возникнут дополнительные проблемы или необходимо устранить неполадки, возможно, потребуется создать отдельный запрос на обслуживание. Для дополнительных вопросов и проблем, которые не могут быть неполными для данного исправления, действуют стандартные затраты на поддержку. Чтобы создать отдельный запрос на обслуживание, посетите веб-сайт Майкрософт по следующему адресу:

Сведения о файлах

Английская версия данного исправления содержит атрибуты файлов (или более поздние версии), указанные в приведенной ниже таблице. Дата и время для этих файлов указаны в формате всемирного координированного времени (UTC). При просмотре сведений о файле они преобразуются в местное время. Чтобы узнать разницу между временем по ГРИНВИЧу и местным временем, используйте вкладку Часовой пояс в элементе » Дата и время » на панели управления. Microsoft Dynamics SL 2011

Источник

Microsoft sql server error 4060

This forum has migrated to Microsoft Q&A. Visit Microsoft Q&A to post new questions.

Asked by:

Question

Hello, i got the error message below when trying to create the todo item table in mobile app service. I’m pretty sure have configure the connection string correctly. please advice as soon as you can.

There was an error while initializing App Service app for ‘testappsg’. ‘Error connecting to SQL server (SQL error code 4060)’

Error code 4060 is «Server rejected the connection». This indicates either the host named in the connection string is wrong, the server has a firewall (perhaps you didn’t allow azure services to connect to it?) or there was a problem with the SQL service.

What does the Connection String look like in the Azure App Service Application Settings? (Feel free to obfuscate the password — it isn’t important).

Adrian, here is the connectionstring. I’ve checked the DB server and the allow azure services is turned on. please let me know if you meant different. Thanks.

The Step 1 in the quickstart — connection to DB is green check marked as well so i assumed the there is a connection the the DB.

Источник

How to fix SQL error 4060

by Arya MA | Jun 25, 2020

SQL error 4060 “Server rejected the connection; Access to the selected database has been denied” is a common error usually seen after website migration in Windows servers.

The reasons for this error include permission issues, firewall restrictions, etc.

As a part of our Server Management Services, we help our customers to fix SQL related errors regularly.

Let’s today discuss the possible causes and fixes for this error.

What causes SQL error 4060?

Often after a migration, some users notice SQL error 4060 while applications or websites. This error states that the “Server rejected the connection; Access to the selected database has been denied“. As the error message states, access to the database was denied as the server rejected the connection.

To list out, the common reasons for this error include:

• No permission to access the database using the credentials
• Protocol not enabled
• Firewall blocking access

Lets us now look into each of these reasons in detail and the possible fix for them.

Lack of Permission

The most common reason for the error 4060 is the lack of permission for the user to access the database. After migration, it is important to ensure that all the users in the previous environment are set up in the new environment as well with the required privileges. However, this is often a frequently missed point.

Correct permissions can be granted to the users with a proper TSQL command. A general format of the command is

For instance, to grant SHOWPLAN permission on the Example database to application role Moderator, TSQL command to be used is:

Similarly, we could grant the required privileges to the user after comparison with that of the permission in the old environment.

Protocol not enabled

To connect to SQL Server Database Engine you must have a network protocol enabled. If those are not enabled, it may trigger the error 4060.

The steps to enable them are:

First, select Start , and in your list of programs, select SQL Server Configuration Manager .

Next, navigate to SQL Server Configuration Manager > SQL Server Network Configuration > Protocols for .

Then, double-click Named Pipes . The Named Pipes Properties screen appears.

From Enabled , select Yes . Then click OK .

Similarly to enable TCP/IP, we can select TCP/IP as in step 2. The TCP/IP Properties screen appears.

Next, on the Protocol tab , ensure Yes is selected for Enabled . On the IP Addresses tab , ensure that Yes is selected for the appropriate IP Address. Also, ensure that the appropriate TCP Port is indicated. Then click ok.

Finally, from SQL Server Management Studio , restart the server instance.

Firewall blocking Access

Firewall restrictions can also trigger the error 4060. To fix it, we need to allow access in firewall. Generally, a closed port is the most common restriction that Firewall places. To fix it, we need to open the port in the firewall for the client.

Apart from the common reasons mentioned above, some other reasons can also trigger this error. In a rare case scenario, this error could also indicate that the corresponding database is not copied over to the new environment. Thus it is not a bad idea to cross-check if the database is actually copied over before we go for any other complex fixes.

[Need help to fix SQL errors? We are available 24×7]

Conclusion

In short, lack of permission for users to access database, firewall restriction etc trigger the error 4060. Today, we discussed how our Support Engineers fix the error “Server rejected the connection; Access to the selected database has been denied”.

PREVENT YOUR SERVER FROM CRASHING!

Never again lose customers to poor server speed! Let us help you.

Our server experts will monitor & maintain your server 24/7 so that it remains lightning fast and secure.

Источник