Ошибка 4064 sql server

SQL server error 4064 triggers while connecting to Microsoft SQL Server. This generally happens when the default database is not available to complete the connection requests.

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

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

What is SQL server error 4064?

Each user has a default database. It by default uses this database for login if no other database is explicitly specified. But, what happens if the default database is unavailable at the time of the connection?

This normally triggers the 4064 error message with the message below:

SQL server error 4064

What are the causes of SQL server error 4064?

Microsoft SQL Error 4064 occurs when the default database for a user is dropped. Thus when the user tries to log in, this error shows up. This error will occur whenever the user’s default database is offline as well.

In general, the error 4064 triggers when the user default database is unavailable at the time of connection. It may happen when the database:

1. Is in suspect mode.
2. No longer exists.
3. Is in single-user mode and the only available connection is already being used by someone or something else.
4. Has been detached.
5. Has been set to the RESTRICTED_USER state.
6. Is offline.
7. Is set to emergency status.
8. Does not have the login account mapped to a user, or the user has been denied access.
9. Is part of a database mirror.

Additionally, this may also happen when the login account is a member of multiple groups, and the default database for one of those groups is unavailable at the time of connection.

How to fix SQL server error 4064?

To resolve this error message, we need to specify a valid, available database in the connection string. To prevent the error when the user’s default database is unavailable, log on as a user who can modify logins. Then, change the user’s default database to a database that’s currently available for a connection.

We can use the sqlcmd utility to change the default database. To do this, follow these steps:

  1. Click Start, click Run, type cmd, and then press ENTER.
  2. Use one of the following methods, depending on the kind of authentication that the SQL Server login uses:
    * If the SQL Server login uses Microsoft Windows authentication to connect to the instance, type the following at the command prompt, and then press ENTER:sqlcmd E -S InstanceName d master

    * If the SQL Server login uses SQL Server authentication to connect to the instance, type the following at the command prompt, and then press ENTER:

    sqlcmd -S InstanceName -d master -U SQLLogin -P Password

    Replace the InstanceName in the command above with the name of the SQL Server instance to which you are connecting. Likewise, replace SQLLogin with the SQL Server login whose default database has been dropped and Password with the  SQL Server login password.

  3. At the sqlcmd prompt, type the following, and then press ENTER:ALTER LOGIN SQLLogin WITH DEFAULT_DATABASE = AvailDBName

    Replace AvailDBName with the name of the existing database that can be accessed by the SQL Server login in the instance.

  4. At the sqlcmd prompt, type GO, and then press ENTER.
Using SQL Server Management Studio

We can perform this same task via SQL Server Management Studio as well. The steps to perform it include:

  1. Launch SSMS and click on connect to database engine. Enter server name and login details for which you are facing issue.
  2. Now click on Options tab.
  3. You can see Connect to Database option is set to default database.
  4. Now we need to change this default to any accessible database. You need to enter or type the database name.
  5. Now click on connect button to establish the database connection. This time you can connect to your SQL Server instance.
  6. You can bring your database online first or can change the default database for the login. If the database is dropped you need to change the default database of your login.
Change default database of Login Name

Once we have found the database, next step would be to change the default database set for the login. There are two options to change the default database set to any login. One is by using T-SQL code and another is by using GUI. Let’s start with GUI method.

1. Expand Security Folder followed by Logins folder. Now double click on your login name or right click on login and choose properties tab.

2. You can see default database is showing as blank. This was the main issue because your database has dropped from the instance. Now change it to master database and click on OK button to proceed.

3. Now change the connect to database to any existing database on your server like master or msdb

We can use the Alter command to set the default database for the login using the T-SQL method.

ALTER LOGIN [loginname] WITH DEFAULT_DATABASE = master

Replace loginname with your login name.

[Need any further assistance in fixing SQL errors? – We’re available 24*7]

Conclusion

In short, the SQL server error 4064 triggers while connecting to Microsoft SQL Server. This generally happens when the default database is not available to complete the connection requests.  Today, we saw how our Support Engineers fix this error.

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.

GET STARTED

var google_conversion_label = «owonCMyG5nEQ0aD71QM»;

Источник
title description author ms.author ms.reviewer ms.date ms.service ms.subservice ms.topic helpviewer_keywords

MSSQLSERVER_4064

MSSQLSERVER_4064

MashaMSFT

mathoma

sureshka, randolphwest

03/01/2023

sql

supportability

reference

4064 (Database Engine error)

MSSQLSERVER_4064

[!INCLUDE SQL Server]

Details

Attribute Value
Product Name SQL Server
Event ID 4064
Event Source MSSQLSERVER
Component SQLEngine
Symbolic Name DB_UFAIL_FATAL
Message Text Cannot open user default database. Login failed.

Explanation

The SQL Server login was unable to connect to SQL Server, either due to permission issues with a database user associated with the login in the default database, or a problem with its default database.

Permission issues can be one or more of the following:

  • The login doesn’t have a corresponding mapped user in its default database.
  • You assigned a default database to the login but didn’t create a user mapping in the specified database.
  • The mapped user for the login has been denied access. (For example, this can happen if the user is inadvertently added to a db_denydatareader fixed database role.)

The default database may be unavailable at the time of connection for the following reasons:

  • The default database is in suspect mode.
  • The default database no longer exists.
  • The default database is in single-user mode, and the only available connection is already used by someone or something else.
  • The default database has been detached.
  • The default database is set to a RESTRICTED_USER state.
  • The default database is offline.
  • The default database is set to an EMERGENCY state.
  • The default database is part of a database mirror.

Additionally, the login account may be a member of multiple groups, and the default database for one of those groups is unavailable at the time of connection.

For more information about database users in SQL Server, see Create a Database User.

User action

You can take one of the following actions:

Work around the issue

If you don’t need to access the currently configured default database and you just need to connect to the SQL Server instance for other operations using SQL Server Management Studio (SSMS), follow these steps:

  1. Open SQL Server Management Studio (SSMS).

  2. On Object Explorer, select Connect > Database Engine.

  3. Fill out the Connect to Server dialog.

  4. Select Options.

  5. Under Connection Properties, modify the Connect to database value using one of the following options:

    • If the login is a member of the sysadmin role, enter master, and select Connect to establish a connection to SQL Server. Once you’re successfully connected to SQL Server, you can change your default database to a different one that’s currently available in the General page of login’s properties in SSMS. For more information, see Create a Login.

    • If the login isn’t a member of the sysadmin role, enter a database name on the server that you know you have access to. Alternatively, you can try entering a system database name like master and then select Connect. This step may not work if your system administrator has explicitly denied permissions to a guest user in the master database. In that scenario, you need to work with your system administrator to resolve the issue.

Fix the issue

A system administrator can check what the current default database of the user is, using the following query:

SELECT name, default_database_name
FROM sys.server_principals
WHERE type = 'S' AND name = '<sql-login>';

Use the following table to determine the appropriate action for fixing the issue for associated causes:

Cause Resolution
No user mapping exists in the login’s default database or the user has been denied access. These database users are also referred to as orphaned users. This problem typically occurs when databases are moved between two server instances, and is one of the common causes of the 4064 error. To detect orphaned users and resolve the problem, see Troubleshoot orphaned users (SQL Server).
No database user exists for the login Create a database user and assign relevant permissions to access the database.
Database user account denied permissions to access the database Navigate to the user properties in the database (Expand database node > Security > Users) and check if the user is part of db_denydatareader role in the Membership page. You can also check effective permissions of a user using sys.fn_my_permissions.
The default database is in suspect mode. A database can become suspect for several reasons. Possible causes include denial of access to a database resource by the operating system and the unavailability or corruption of one or more database files. You can check the state of the database using this query: SELECT DATABASEPROPERTYEX (N'<dbname>', N'STATUS') AS N'Database Status';. In SSMS, the status of suspect databases shows as (Recovery Pending). You may have to recover the database from its backup to resolve this situation.
The default database no longer exists. If you’ve intentionally removed the database from the server, change the default database for the login to another existing database on the server using SSMS or an ALTER LOGIN (Transact-SQL) statement. Optionally, you may want to check if there are other logins on the server whose default database is set to this non-existing database by using this query: SELECT name AS Login_Name FROM sys.server_principals where default_database_name = '<removed-dbname>';.
The default database is in a single-user mode, and the only connection is being used by the administrator or someone else. If the database is set to single-user mode for maintenance purposes, you should set it back to multi-user mode after the completion of maintenance activity, using this query: ALTER DATABASE <dbname> SET MULTI_USER;.
For more information, see Set a database to single-user mode.
Note: To check if a database is in single-user mode, you can use this query: SELECT name, user_access_desc FROM sys.databases WHERE name = '<dbname>';.
If you still need to restrict access to the database but want to enable connectivity for the affected logins, change their default database to a different database on the server.
The default database has been detached. Detaching a database removes it from the instance of SQL Server and is no longer accessible. To make it available for logins, attach the database using SSMS or an sp_attach_db stored procedure. For more information, see Database Detach and Attach (SQL Server).
The default database has been set to a RESTRICTED_USER state. When a database is set to a RESTRICTED_USER state, only members of the db_owner fixed database role and dbcreator and sysadmin fixed server roles can connect to the database. If you no longer need to restrict access to the corresponding database, set the database to multi-user mode using this query: ALTER DATABASE <dbname> SET MULTI_USER;.
Note: To check if a database is in a restricted-user state, you can use this query: SELECT name, user_access_desc FROM sys.databases WHERE name = '<dbname>';.
If you still need to restrict access to the database but want to enable connectivity for the affected logins, change their default database to a different database on the server.
The default database is offline. A database that is in the offline state can’t be modified. You can bring your database online using this query: ALTER database <dnname> SET ONLINE;.
You can check if a database is OFFLINE either using SSMS, or using this query: SELECT DATABASEPROPERTYEX (N'<dbname>', N'STATUS') AS N'Database Status';.
For more information, see Database States and ALTER DATABASE SET Options (Transact-SQL) — SQL Server.
If you still need to keep the database in an offline state but want to enable connectivity for the affected logins, change their default database to a different database on the server.
The default database is set to an EMERGENCY state. A database may have been put into an EMERGENCY state for troubleshooting by a system administrator. Only users of the sysadmin role can access databases set to an EMERGENCY state. You can bring your database online using this query: ALTER database <dnname> SET ONLINE;.
You can check if a database is in an EMERGENCY state either using SSMS, or this query: SELECT DATABASEPROPERTYEX (N'<dbname>', N'STATUS') AS N'Database Status';.
For more information, see Database States and ALTER DATABASE SET Options (Transact-SQL).
If you still need to keep the database in an EMERGENCY state, but want to enable connectivity for the affected logins, change their default database to a different database on the server.
The default database is part of the database mirror. You can’t connect to a mirror database on the mirror server, and this behavior is by design. To check if the database is currently in mirror role, use this query SELECT DB_NAME(database_id) as database_name, mirroring_role_desc FROM sys.database_mirroring WHERE DB_NAME(database_id) = '<dbname>';. For more information about database mirroring, see Database Mirroring (SQL Server).
The login account may be a member of multiple groups, and the default database for one of the groups is unavailable at the time of connection. To enumerate the groups that have a specified user using PowerShell, see Get-ADPrincipalGroupMembership (ActiveDirectory).

Change the default database for a given user

To make changes to a user’s default database, you need to have ALTER ANY LOGIN permission. If the login being changed is a member of the sysadmin fixed server role or a grantee of CONTROL SERVER permission, it also requires CONTROL SERVER permission when making the following changes. Members of the sysadmin role have these permissions enabled by default. For more information, see ALTER LOGIN (Transact-SQL).

SQL Server Management Studio

Change the default database using SSMS

  1. Connect to your SQL Server instance using SQL Server Management Studio (SSMS).

  2. Select Security > Logins to locate the user and change user’s default database to a different one that’s currently available in the General page of login’s properties in SSMS. For more information, see Create a Login.

  3. After connecting to the SQL Server instance, you can execute an ALTER LOGIN statement, like the following examples:

    ALTER LOGIN <LoginName> WITH DEFAULT_DATABASE = <AvailableDatabaseName>;

    <AvailableDatabaseName> is a placeholder for the name of the existing database that can be accessed by the SQL Server login in the instance. <LoginName> is a placeholder for the SQL Server login with necessary ALTER LOGIN permissions.

    For example:

    ALTER LOGIN [SQLLogin] WITH DEFAULT_DATABASE = master;
ALTER LOGIN [ConstosoWindowslogin] WITH DEFAULT_DATABASE = [AdventureWorks];

sqlcmd utility

Change the default database using the sqlcmd utility

You can use the following procedure to change the default database using the sqlcmd utility:

  1. On the computer running SQL Server, select Start, then select Run, enter cmd, and then press Enter.

  2. Connect to SQL Server using the sqlcmd utility and one of the following options:

    • If you want to use Windows authentication to connect to the instance using the Windows user account currently logged on, enter the following command in the Command Prompt window, and then press Enter:

      sqlcmd -E -S <InstanceName> -d master

      For example:

      sqlcmd -S "contososql22" -E -d master

    • If you want to use SQL Server authentication to connect to the instance, enter the following command in the Command Prompt window, and then press Enter:

      sqlcmd -S <InstanceName> -d master -U <SQLAdminAccount> -P <Password>

      <InstanceName> is a placeholder for the name of the SQL Server instance to which you are connecting. <Password> is a placeholder for the SQL Server login password.

      For example:

      sqlcmd -S contososql -U sqladmin -P <Strong password>

  3. To change the default database of a login, at the sqlcmd prompt, use the following example, and then press Enter:

    ALTER LOGIN <LoginName> WITH DEFAULT_DATABASE = <AvailableDatabaseName>;

    <AvailableDatabaseName> is a placeholder for the name of the existing database that can be accessed by the SQL Server login in the instance. <LoginName> is a placeholder for the SQL Server login with necessary ALTER LOGIN permissions.

    For example:

    ALTER LOGIN [SQLLogin] WITH DEFAULT_DATABASE = master;
ALTER LOGIN [ConstosoWindowslogin] WITH DEFAULT_DATABASE = [AdventureWorks];

  4. At the sqlcmd prompt, enter GO, and then press Enter.

    For more information about the sqlcmd utility, see sqlcmd — Use the utility.

PowerShell

Change the default database using PowerShell

You can use the following PowerShell script to update the default database for a specified login.

# Define the variables for the SQL Server instance name and login name

$instanceName = "YOUR_SQL_SERVER_INSTANCE_NAME"
$loginName = "YOUR_SQL_SERVER_LOGIN_NAME"
$newDefaultDB = "YOUR_NEW_DEFAULT_DATABASE"

# Connect to the SQL Server instance

$connectionString = "Server=$instanceName;Integrated Security=True"
$connection = New-Object System.Data.SqlClient.SqlConnection($connectionString)
$connection.Open()

# Execute a T-SQL command to change the default database for the specified login

$tsql = "ALTER LOGIN $loginName WITH DEFAULT_DATABASE = $newDefaultDB"
$command = New-Object System.Data.SqlClient.SqlCommand($tsql, $connection)
$command.ExecuteNonQuery()

# Print a message indicating the update was successful
 
Write-Host "The default database for the login '$loginName' has been successfully updated to '$newDefaultDB'"
 
# Close the SQL Server connection

$connection.Close()

Error 18456 is displayed along with error 4064

When using applications like SSMS that get error 4064 displayed to the user, the following message is logged in the SQL Server error log. This behavior is by design. Fixing the default database for the failed login, using the procedures documented in this article, automatically addresses the 18456 error.

2023-02-06 18:17:02.56 Logon       Error: 18456, Severity: 14, State: 40.
2023-02-06 18:17:02.56 Logon       Login failed for user '<user name>. Reason: Failed to open the database '<db_name>' specified in the login properties. [CLIENT: <hostname >]
Источник

When I want to connect to SQL Server 2008, I get this message:

Cannot connect to server.
Additional Information: Cannot open user default database. Login failed. Login fail for user ‘sa’. (Microsoft SQL Server. Error:4064)

How do I resolve this error?

Peter Mortensen's user avatar

asked Apr 4, 2012 at 11:21

Tavousi's user avatar

0

This error (Microsoft SQL Server.Error:4064) occurs when the database which is dropped is default for some database user.

When the user tries to login and their default database is dropped the error shows up.

Cannot open user default database. Login failed. Login failed for user
‘UserName’. (Microsoft SQL Server, Error: 4064)

The way to resolve this is given here, summarized below.

The solution to log on is:

  1. From the Connect to Server dialog, click Options
  2. Change value of Connect to database: to any valid database on the server

The permanent solution to fix the server is to run SQL like:

ALTER LOGIN [test] WITH DEFAULT_DATABASE = master
GO

Abacus's user avatar

Abacus

2,0211 gold badge18 silver badges23 bronze badges

answered Apr 4, 2012 at 11:52

painotpi's user avatar

painotpipainotpi

6,8521 gold badge37 silver badges69 bronze badges

3

In my case this was due to a user being a member of multiple groups, each group having its own login. All groups’ logins need to have their default database set to a database accessible to the user.

Other possible problems are listed at https://support.microsoft.com/en-us/kb/307864.

You can set each login with an invalid default database to have a default database of master (accessible to all logins):

alter login [loginname] with DEFAULT_DATABASE = master

answered Jun 23, 2015 at 7:21

Simon D's user avatar

Simon DSimon D

4,1305 gold badges39 silver badges47 bronze badges

The user default database is unavailable at the time of connection so that this error message will popup .SO check which server you tagged to that particular user to access whether it is online or offline mode.

answered Aug 23, 2016 at 4:58

Bhanu's user avatar

BhanuBhanu

31 silver badge

Источник

Summary:- >Many users encounter SQL Server Error 4064 while using the MS SQL database. This mistake occurs when you connect to a system that’s running Microsoft SQL Server, and you do not specify a login database, then the default database is used. So, this article suggests the best methods to solve this error related to the MSSQL database.

What is SQL Server Error 4064?

This error happens when the user database is set to the default database. When the user attempts to log in and find that the default database is dropped, then this error is shown as if the user “abcd” tries to log in to the database but fails as the database is set as default.

SQL Server Error 4064

Lets us know the causes behind this type of error.

Valid Reasons for SQL Server error-

If the database is in suspect mode or the database is no longer exists. Then this blunder can take place. It is also possible that the SQL database has been set to the RESTRICTED_USER state. The database could be offline as well. If a user does not have the login account mapped, or the user has been denied access, then this error can also take place.

How to Get Rid of SQL Server Error 4064?

To get rid of the “Cannot open default user database login failed” error, different techniques need to be used depending on the server setting. There are manual methods explained below to solve database error. Then manual methods are only applicable for SQL Server 2005 and its later version. So, those users who are using the SQL server 2005 and its later version should follow the below methods.

There are two manual methods that quickly resolve this error:

  1. Use SQLCMD to Modify Default Database
  2. Use the GUI to Change Default Database
  3. Rectify Issues with Sysinfotools SQL Recovery

Method 1: Use SQLCMD to Modify Default Database

SQLCMD utility is used to modify the default database in SQL Server. So, to do this, follow the steps that are shown below:

  • The first step is to click on Start and type Run in the search field.
  • Then in the Run dialog box type cmd, and hit Enter.
  • Deploy any of the techniques in the command prompt according to the sort of SQL Server login authentication you prefer:
  • For Microsoft Windows authentication, Type this command “sqlcmd E -S InstanceName d master”
  • For SQL Server authentication, Type this following command “Sqlcmd -S InstanceName -d master -U SQLLogin -P Password”

Then type the below-mentioned command in sqlcmd prompt and then hit the Enter key:

ALTER LOGIN SQLLogin WITH DEFAULT_DATABASE= AvailDBName

Where AvailDBName shows the database name that already exists. This database can further be used by the login of SQL Server while synchronizing with SQL database.

Method 2: Use the GUI to Change Default Database

  1. First, open the SQL Server 2005 login page and then click on Options.
  2. Next, modify the Connect to database status with the help of existing databases such as Master.
  3. At last, click on connect.

Method 3: Solve Error with SQL Database Recovery

You can follow the above important methods one by one to solve the database error. If you are facing some issues with manual methods there is another best way to get rid of this issue is SQL Database Recovery.

This software recovers quickly helps in removing the SQL server error. Let us discuss some important features of SQL Data recovery:

  • Recovers file objects including tables, stored procedures, views,  programmability, triggers, default, and functions.
  • Corrupt MDF and NDF files of SQL Server database can be repaired by this.
  • It can save recovered data either in SQL Server database format.
  • The preview option is there to review the data before saving.

Last words

Manual and a direct method has been explained above to move out from the SQL Server error 4064. Users can use any of the above methods but if someone wants to resolve the issue quickly can opt for the direct method. As you don’t need to identify the corruption of SQL data manually, this tool will automatically solve your issue and you can easily recover corrupted MySQL Database.

Источник

I am using an SQL database where I have seen the database connection lost when connecting to the server many times. This query is most common when connecting to the database server. So, here in this tech guide, we will explain all about Microsoft SQL server error 4064 Cannot open user default database and also how it can be resolved. This guide comprises of reasons behind the database error 4064, solutions for this error and at last a third-party solution.

Every user has a default account-related database in SQL Server. Each time the user attempts to sign in without specifying a password, the default database remains active. But if the default database is not available, or the SQL Server does not locate the server, the issue will be shown with an error message.

Error:

“Cannot open user default database. Login failed.

Login failed for user “username” (Microsoft SQL Server, Error: 4064)

SQL Server Error 4064”

When you double-click the user (Expand Security-> Logins) you will end up seeing that Default User is not allocated a user as shown below.

Reasons for the occurrence of Server Error 4064:-

There are many more explanations for the error such as the unavailability at the time of communication of the user default server. It may be that the database is in suspicious mode or offline. There is also the possibility that it was set to or left disconnected from RESTRICTED USER. The number of causes could be the following:

  1. RESTRICTED USER: Limiting access to databases by general users is important when performing certain maintenance tasks, particularly in recovery situations. Limited access mode can be used in such circumstances to restrict connections to high-level users only.
  2. There is no longer any database: When there is no database present then it may result in server error 4064.
  3. The database is set to the stage of an emergency situation: When a database is placed in the state of emergency, three major changes are made to the database configuration:
    • Makes the database READ ONLY
    • Restricts access to representatives of the set server feature only
    • Logging is disabled (as the database is READ ONLY)
  4. It operates in single-user mode: It shows that only one user can connect to the server.

Because of the above-mentioned reasons, Microsoft SQL server error 4064 occurs. So, to solve this blunder “cannot open default user database” we are going to explain various methods in detail.

Solution 1: Connect to Server

Specify the name of the server as TempDB for Connect to Server in the Connection Properties and press the Connect option to connect to the SQL Server.

Upon connection with the SQL Server Instance, execute the TSQL below to add a new default server to the account.

Use master

GO

ALTER LOGIN [MonitorDB] WITH DEFAULT_DATABASE = TempDB

GO

Solution 2: Connect to Different Database

You can log in to your account if you are the Database Administrator and switch the default server to the master server. Follow the steps below:

  1. Begin the Studio for SQL Server Management. When the wizard ‘ Connect to Server ‘ opens, enter the name, username, and password of the database. Tap on the Options tab here.
  2. Look “Connect to database” option which is connected to the user account’s default server. After this, you can type any database name that is accessible or write the master database name as well.

    NOTE: Do not pick any other server by using the drop-down as it may send the error.

  3. Tap the Connect key to sign in successfully this time.

Solution 3: Change the Default Database

You can also use the login properties to change the default database to any other database. Follow the steps below:

  1. Go to Security Folder and expand it after connecting to your SQL Server case. Select the folder and go to your login name. Tap the name of the account right click on Property.
  2. You can see the ‘ default database ‘ option in the bottom part. If it is empty, this means that the account has not associated with your default folder. Type the name of the database that is accessible and then click on the OK button.

You can also execute the T-SQL command to alter your SQL account’s default server. Follow the instructions:

“ALTER LOGIN [username] WITH DEFAULT_DATABASE = master”

Methods mentioned above can be said to fixing Microsoft SQL server error 4064. But the problem arises when a database is accessible by the user. Then a third party utility comes named SQL Recovery that is capable to recover inaccessible files of any server. Also, it can easily recover damaged databases quickly.

Download Now

Conclusion

This guide has been discussed all the effective measures for solving the server error 4064 in the SQL database. With manually and alternatively both the solutions have been described above. So, users can use any one of the options whether working step by step manually or directly go with SQL Recovery utility.

Источник

Возможно, вам также будет интересно:

  • Ошибка 406 при оплате картой
  • Ошибка 406 крайслер пацифика
  • Ошибка 406 not acceptable что это
  • Ошибка 406 not acceptable см вывод консоли для отладочной информации
  • Ошибка 406 iis 1c

    • Понравилась статья? Поделить с друзьями:
    0 0 голоса
    Рейтинг статьи
    Подписаться
    Уведомить о
    guest

    0 комментариев
    Старые
    Новые Популярные
    Межтекстовые Отзывы
    Посмотреть все комментарии