Ошибка odbc sqlstate 42000 номер ошибки 4060

CA WAAE Scheduler and Application server services fail to start with error: CAUAJM_E_18601 SQLSTATE: 42000, Native error: 4,060, Message: [Microsoft][ODBC SQL Server Driver][SQL Server]Cannot open database «AEDB» requested by the login. The login failed.

«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 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

Источник

Sql server error 4060 cannot open database requested login

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?

Источник

SQLServer Error: 4060, Cannot open database

March 13, 2009 at 1:35 pm

[298] SQLServer Error: 4060, Cannot open database «TestDB» requested by the login. The login failed. [SQLSTATE 42000]

[298] SQLServer Error: 18456, Login failed for user ‘DOMAINAdministrator’. [SQLSTATE 28000]

The problem is: I deleted that TestDB a day ago. It does not exist anymore!

What am I missing?

March 13, 2009 at 1:54 pm

Do you have any Jobs, Scheduled tasks or something running that connects to that DB?

March 13, 2009 at 2:07 pm

Thank you, that solved issue. I overlooked that sharepoint installation created job CDW_SHAREPOINT for that database.

March 13, 2009 at 2:10 pm

Glad I could help.. 🙂

January 31, 2022 at 3:25 am

SQL Server Strange behavior:

I have been Getting the following error massages non stop after full backup fails. this massage gets generated for each databases in this Availability Group. The job runs every night, and it call SSIS package. Both the SSIS and Job seems okay and the tricky part is that job fails once in a while like once in 10 days or so.

[298] SQLServer Error: 4060, Cannot open database «testDB» requested by the login. The login failed. [SQLSTATE 42000]

[298] SQLServer Error: 18456, Login failed for user ‘Testtest-user-sql’. [SQLSTATE 28000]

Server; SQL Server 2016 AG with 2 replica synchronized.

More than 10 databases configured in this AG

Backup preference; any replica

Did I miss something here?

January 31, 2022 at 10:00 am

You had better started a new forum post ! Whenever I see new answers to old Questions, I skip it

Johan

Learn to play, play to learn !

Dont drive faster than your guardian angel can fly .
but keeping both feet on the ground wont get you anywhere :w00t:

press F1 for solution, press shift +F1 for urgent solution 😀

Need a bit of Powershell? How about this

Viewing 6 posts — 1 through 5 (of 5 total)

You must be logged in to reply to this topic. Login to reply

Источник

How to fix database SQL server error 4060?

Table of Contents

How do I resolve database error 4060 in SQL Server?

If you use a SQL database, you may encounter SQL Error 4060 following a database migration. This is one of the many SQL Errors that administrators must deal with. SQL Error 4060 occurs on the server. As a result, the client has little control over the situation. You require an immediate solution. We’ll show you how to fix SQL Error 4060 here.

1. sql server error 4060 cannot open database
2. sql state 08004 sql server error 4060 or sql state 08004 error 4060
3. fatal sql error 4060 occurred during company login
4. unable to open the specified server database 4060
5. error number 4060 state 1 class 11 or error number:4060,state:1,class:11
6. server rejected the connection; access to selected database has been denied

Cause for SQL Server Error 4060

After migrating a website or application, users may encounter SQL Error 4060, which reads “Connection Failure: Server Rejected the Connection, Access to Selected Database Denied.” This error appears because:

1. There were insufficient valid credentials to access the database, so access was denied
2. Network Protocol was not enabled
3. Access was blocked by a firewall

Solution for SQL Server 4060 Error

No valid credentials supplied or credentials have no permission

The most serious problem with error 4060 in sql server is that the user did not have permission to view the database objects. They did not face this problem prior to migration because they had the necessary permission. As a result, after migration, you, as an administrator, should grant them permission.

You must use the Transact-SQL or TSQL command to grant the privileges. This command appears to be:

Similarly, you can grant permissions to other users based on their roles.

This should resolve the issue. If not, move on to the next solution.

All connections to the SQL Server Database Engine require a network protocol, which should be enabled. If not, the database will generate the 4060 error.

For example if you encounter below error

SQLDriverConnect: RETCODE=-1, State=37000, Native
Error=4060 [Microsoft][ODBC SQL Server Driver][SQL Server]Cannot open
database required.

Resolving the SQL 4060 above is to set database to “Single User” or permissions issue. To resolve these errors:

1. SQL 4060 above can occur when database is in “Single User” access, so set it back to Multi user access. To remove single user mode in sql server is achieved with the ALTER DATABASE statement as follows:

   ALTER DATABASE [Database_Name] SET MULTI_USER

2. Make sure no server roles are enabled for the application login in Server Roles but only database permissions list by application provider correctly like read, write, execute etc…

2. To resolve Network protocol error for sql server 4060, follow these steps:

• Go to the programme’s list by clicking on “Start”
• From the list, select “SQL Server Configuration Manager”
• Then navigate into SQL Server Network Configuration and Protocols for machine instance>.
• Double click on “Named Pipes”. This will open the Named Pipes Properties tab
• Select “Yes” for the Enabled option and then OK to confirm.

Also like the above, you also need to enabled TCP/IP.

• Go to the list of programs by click on Start and select “TCP/IP”.
• From the properties screen, select “Yes” on the Enabled parameter.
• Now go to the IP Addresses tab and select “Yes” for the IP address.
• Also check for the correctness of TCP Port.
• Finally click “OK”

3.Firewall Blocking issue

If neither of the preceding solutions resolves the problem, it is more likely that a firewall is preventing access to the database. To fix this, simply instruct the firewall to grant the user access. Navigate to the firewalls that have been installed and look for permissions. If it hasn’t already been granted to the user, do so.

SQL Error 4060 can also be caused by other problems. A corresponding database, for example, may not have been properly copied into a new environment. There are also issues with rows and objects. Although these are uncommon, we recommend that you investigate them if the SQL 4060 error persists.

Источник

Microsoft SQL Server

	Я
pavlik 04.10.12 — 21:07	Incorrect syntax near the keyword ‘order’ Возникает при попытке чтения данных с SQL Server 2008 (пользую внешние источники данных). Подключение происходит, поля таблицы вижу, данных нет. Где руки поправить?
pavlik 1 — 04.10.12 — 21:30	на сервере вот такой для БД collation «SQL_Latin1_General_CP1_CI_AS»
МихаилМ 2 — 04.10.12 — 21:56	текст запроса в студию.
pavlik 3 — 04.10.12 — 21:59	да нет никакого запроса. Создал элемент метаданных «Внешний источник данных». На форму вывалил несколько полей. Подключение происходит, поля отображаются верно (как на сервере). Однако ж талбица на форме пуста, при попытке сортирнуть данные — имеем ашипко. Как-то так.
МихаилМ 4 — 04.10.12 — 22:07	насколько я помню, внешние источники работают через odbc. попробуйте воспользоваться odbc трассировщиком. или трассировщиком субд ms sql (sql profiler) коли collation «SQL_Latin1_General_CP1_CI_AS»
pavlik 5 — 04.10.12 — 22:39	пилять, вообще ничего не понимаю. Изначально от ODBC требовал все поля таблицы (>дохера). Если существенно ограничить количество полей — взлетает, сука. Нешто ограничение 8-ка имеет на такой случай?
Живой Ископаемый 6 — 04.10.12 — 22:41	нет, 8-ка не имеет потому что сообщение от ОДБС.
shuhard 7 — 04.10.12 — 22:54	(5) 42000 Syntax error or access violation может тупо прав на поля нет или идёт попытка чтения Блоб-а
pavlik 8 — 04.10.12 — 23:05	(7) блобов нету, читаю от sa
shuhard 9 — 04.10.12 — 23:07	(8) прицепись через ADODB поверх ODBC и протестируй, получишь ответ где ODBC ломается
pavlik 10 — 04.10.12 — 23:18	(9) ниасилит 8ка ADODB. Или я крепко ошибаюсь? PS Читать данные нужно из конфиги. Хотелось бы еще и писать, еще лучше — выполнять хранимки на сервере. Может что-то дельное почтенная публика присоветует?
shuhard 11 — 04.10.12 — 23:32	(10)[ ниасилит 8ка ADODB. Или я крепко ошибаюсь? ] угу кардинально нет с ADODB и ADOX у 1С ни каких проблем

Программист всегда исправляет последнюю ошибку.

How do I resolve database error 4060 in SQL Server?

If you use a SQL database, you may encounter SQL Error 4060 following a database migration. This is one of the many SQL Errors that administrators must deal with. SQL Error 4060 occurs on the server. As a result, the client has little control over the situation. You require an immediate solution. We’ll show you how to fix SQL Error 4060 here.

Errors include

1. sql server error 4060 cannot open database
2. sql state 08004 sql server error 4060 or sql state 08004 error 4060
3. fatal sql error 4060 occurred during company login
4. unable to open the specified server database 4060
5. error number 4060 state 1 class 11 or error number:4060,state:1,class:11
6. server rejected the connection; access to selected database has been denied

After migrating a website or application, users may encounter SQL Error 4060, which reads “Connection Failure: Server Rejected the Connection, Access to Selected Database Denied.” This error appears because:

1. There were insufficient valid credentials to access the database, so access was denied
2. Network Protocol was not enabled
3. Access was blocked by a firewall

Solution for SQL Server 4060 Error

1. No valid credentials supplied or credentials have no permission

The most serious problem with error 4060 in sql server is that the user did not have permission to view the database objects. They did not face this problem prior to migration because they had the necessary permission. As a result, after migration, you, as an administrator, should grant them permission.

You must use the Transact-SQL or TSQL command to grant the privileges. This command appears to be:

GRANT <permission> [] TO <database_principal> [] [ WITH GRANT OPTION] [AS <database_principal>  As you can see, the first line of code grants the required permission, and the second line to a specific user.

Similarly, you can grant permissions to other users based on their roles.

This should resolve the issue. If not, move on to the next solution.

All connections to the SQL Server Database Engine require a network protocol, which should be enabled. If not, the database will generate the 4060 error.

For example if you encounter below error

SQLDriverConnect: RETCODE=-1, State=37000, Native
Error=4060 [Microsoft][ODBC SQL Server Driver][SQL Server]Cannot open
database required.

Resolving the SQL 4060 above is to set database to “Single User” or permissions issue. To resolve these errors:

1. SQL 4060 above can occur when database is in “Single User” access, so set it back to Multi user access. To remove single user mode in sql server is achieved with the ALTER DATABASE statement as follows:
   
ALTER DATABASE [Database_Name] SET MULTI_USER
2.  Make sure no server roles are enabled for the application login in Server Roles but only database permissions list by application provider correctly like read, write, execute etc…

2. To resolve Network protocol error for sql server 4060, follow these steps:

• Go to the programme’s list by clicking on “Start”
• From the list, select “SQL Server Configuration Manager”
• Then navigate into SQL Server Network Configuration and Protocols for machine instance>.
• Double click on “Named Pipes”. This will open the Named Pipes Properties tab
• Select “Yes” for the Enabled option and then OK to confirm.

Also like the above, you also need to enabled TCP/IP.

• Go to the list of programs by click on Start and select “TCP/IP”.
• From the properties screen, select “Yes” on the Enabled parameter.
• Now go to the IP Addresses tab and select “Yes” for the IP address.
• Also check for the correctness of TCP Port.
• Finally click “OK”

3.Firewall Blocking issue

If neither of the preceding solutions resolves the problem, it is more likely that a firewall is preventing access to the database. To fix this, simply instruct the firewall to grant the user access. Navigate to the firewalls that have been installed and look for permissions. If it hasn’t already been granted to the user, do so.

SQL Error 4060 can also be caused by other problems. A corresponding database, for example, may not have been properly copied into a new environment. There are also issues with rows and objects. Although these are uncommon, we recommend that you investigate them if the SQL 4060 error persists.