What is MySQL Error Code 1005?

SQL error 1005, also known as “Can’t create table (errno: 150)”, is a MySQL error that occurs when there is a problem with a foreign key constraint. Foreign key constraints are used to establish relationships between tables in a relational database. They ensure that data integrity is maintained by preventing actions that would create inconsistent or invalid data.

Possible Causes

When you encounter SQL error 1005, MySQL is telling you that there is an issue with a foreign key constraint while trying to create or modify a table. This error can be caused by a variety of reasons, such as:

1. Incorrect syntax: The foreign key constraint might not be defined properly, leading to a syntax error in your SQL statement.
2. Data type mismatch: The data types of the columns involved in the foreign key constraint must match exactly. If there is a mismatch in data types, MySQL will throw error 1005.
3. Missing referenced table: The table referred to in the foreign key constraint might not exist in the database.
4. Incompatible foreign key constraint: The referenced table might have a foreign key constraint with incompatible attributes, such as different collation, character set, or storage engine.
5. Circular reference: A circular reference occurs when two or more tables reference each other with foreign key constraints, creating a loop. MySQL does not allow circular references, and it will result in error 1005.

Fix MySQL Error Code 1005

Now that we have a basic understanding of SQL error 1005 and its possible causes, let’s dive into the solutions to fix this issue.

1. Check for typos or errors in your table definitions: Make sure that you have correctly defined your table columns, data types, and constraints. Double-check for any misspellings, missing or extra commas, and other syntax errors in your table definitions.
2. Ensure that referenced columns and tables exist: If you are defining foreign key constraints, make sure that the referenced columns and tables actually exist in the database. If the referenced table has not been created yet, or if it has been dropped or renamed, you may encounter error code 1005.
3. Check for conflicting constraints: If you have multiple foreign key constraints in your table definitions, ensure that there are no conflicts. For example, if you have two foreign keys that reference the same column in another table, MySQL will raise error code 1005. Make sure that your constraints are properly defined and do not conflict with each other.
4. Verify data types and lengths: Make sure that the data types and lengths of the columns in your foreign key and referencing tables match exactly. Data type mismatches can result in error code 1005.
5. Disable foreign key checks: You can temporarily disable foreign key checks in MySQL by running the following command before creating or modifying tables: SET FOREIGN_KEY_CHECKS = 0;. This can help you identify and fix any issues with foreign key constraints. However, be cautious when using this approach, as it can potentially lead to inconsistent data if not used properly.
6. Check for circular references: If you have circular references in your foreign key constraints, where Table A references Table B and Table B references Table A, you will encounter error code 1005. To fix this issue, you may need to restructure your database schema to remove circular references.
7. Check for storage engine compatibility: If you are using different storage engines for your referencing and referenced tables, you may encounter error code 1005. Make sure that the storage engines are compatible, such as using InnoDB for both tables, as some storage engines do not support foreign key constraints.
8. Review MySQL error logs: Check the MySQL error logs for any additional information on the cause of the error. The error logs may provide more detailed information about the specific issue that is causing error code 1005.

By following these steps, you should be able to identify and fix the issue that is causing MySQL error code 1005. If you are still encountering issues, it may be helpful to consult the MySQL documentation or seek assistance from a knowledgeable database administrator.

Read More articles:

• How to fix SQL Error 1064: You have an error in your SQL syntax
• How to Fix SQL Server Error 207 – Invalid Column Name

The post How to Fix SQL Error 1005: A Comprehensive Guide appeared first on Techyaz.com.

In this article, we will explore what this error means, its possible causes, and provide solutions to fix it.

What is SQL Server Error 207 – Invalid Column Name?

SQL Server error 207 occurs when a column name referenced in a SQL query does not exist in the specified table or view. In other words, SQL Server is unable to find a column with the name mentioned in the query, and as a result, throws the error message “Invalid Column Name.”

Possible Causes

1. Typographical errors: One of the most common causes of error 207 is a typographical error in the SQL query. For example, misspelling a column name, using the wrong case, or forgetting to enclose the column name in square brackets, especially if the column name contains spaces or special characters.
2. Missing or renamed column: Another possible cause of error 207 is that the column may have been deleted or renamed in the table or view, but the query has not been updated accordingly. If a column is dropped or renamed, any queries that reference that column will result in error 207.
3. Scope and visibility of column: The visibility and scope of a column can also cause error 207. If a column is referenced in a query outside of its scope or visibility, SQL Server will not be able to find it, and the error will be thrown.
4. Schema changes: Changes to the schema of a table or view, such as adding, modifying, or deleting columns, can also result in SQL error 207 if the query has not been updated to reflect the changes.
5. Permissions: Another possible cause of SQL error 207 is insufficient permissions. If the user executing the query does not have the necessary permissions to access the column, SQL Server will throw the error.

Fix SQL Error 207

Now that we understand the causes of SQL Server Error 207, let’s explore some solutions to fix this issue:

1. Double-check the column name: The first step in fixing error 207 is to double-check the column name referenced in the SQL query. Make sure it is spelled correctly, using the right case, and enclosed in square brackets if needed. Pay attention to any spaces or special characters in the column name.
2. Verify column existence and visibility: Ensure that the column actually exists in the specified table or view and is visible to the user executing the query. If the column has been deleted or renamed, update the query accordingly.
3. Update the query: If the error is caused by changes to the schema of a table or view, update the query to reflect the changes. For example, if a new column has been added, make sure to include it in the SELECT, INSERT, UPDATE, or DELETE statements as needed.
4. Check permissions: Verify that the user executing the query has the necessary permissions to access the column. Make sure the user has SELECT, INSERT, UPDATE, or DELETE permissions on the table or view that contains the column.
5. Use aliases and table qualifiers: When referencing columns in a query, it is a good practice to use aliases or table qualifiers to avoid ambiguity. For example, instead of just using “SELECT column_name FROM table_name,” use “SELECT t.column_name FROM table_name AS t” or “SELECT table_name.column_name FROM table_name.”
6. Test and debug: After making any changes to the query or schema, always test and debug the query to ensure that the error has been resolved. Use SQL Server tools such as SQL
7. Use Schema Prefix: If you are referencing a table or column that belongs to a specific schema, make sure to include the schema name as a prefix in your SQL query. For example, if you have a table named “Customers” in the “Sales” schema, your query should be something like “SELECT * FROM Sales.Customers” instead of just “SELECT * FROM Customers”.
8. Resolve Ambiguous Column Names: If you encounter an ambiguous column name error, you need to specify which table the column belongs to in your SQL query. You can do this by prefixing the column name with the table name or alias in your query, e.g., “SELECT Orders.OrderID FROM Orders, Customers WHERE Orders.CustomerID = Customers.CustomerID” instead of just “SELECT OrderID FROM Orders, Customers WHERE CustomerID = Customers.CustomerID”.
9. Check Table Existence: Ensure that the table mentioned in your SQL query actually exists in the database. If not, you may need to create the table or correct the table name in your query.
10. Verify Schema Ownership: If you are referencing a table in a different schema, make sure that the schema exists and that you have the necessary permissions to access it. If not, you may need to create the schema or obtain the required permissions.

We learn about fixing SQL Server Error 207 which occurs when a SQL query references a column that does not exist in the specified table or view. This error typically results from a misspelled column name or a reference to a non-existent column in a SELECT, UPDATE, or DELETE statement. When the SQL Server query processor encounters an invalid column name, it raises SQL Error 207 and prevents the execution of the query. You can prevent this issue by following the steps given in this article.

Read More articles:

• How to fix SQL Error 1064: You have an error in your SQL syntax
• SQL Server Interview Questions & Answers on Indexes

The post How to Fix SQL Server Error 207 – Invalid Column Name appeared first on Techyaz.com.

What is SQL Error 1045?

Error 1045 is a MySQL error code that indicates a failed connection to the MySQL database server. The error message associated with SQL Error 1045 typically reads “Access denied for user ‘username’@’localhost’ (using password: YES)” or “Access denied for user ‘username’@’hostname’ (using password: YES)“.

This error occurs when a user attempts to connect to a MySQL database but does not have the proper authorization or has entered incorrect login credentials.

Possible Causes

There are several potential causes for SQL Error 1045, including:

1. Incorrect username or password: One of the most common causes of SQL Error 1045 is entering incorrect login credentials, including the username or password. It is essential to double-check and ensure that the correct username and password are entered when connecting to the MySQL database.
2. Missing or improper privileges: Another possible cause of SQL Error 1045 is the absence of the necessary privileges for the user trying to connect to the MySQL database. If the user does not have the proper privileges, they will be denied access, resulting in the error.
3. Hostname or IP address mismatch: MySQL uses hostnames or IP addresses to identify which hosts are allowed to connect to the database. If the hostname or IP address specified during the connection attempt does not match the one defined in the MySQL configuration, SQL Error 1045 may occur.
4. Firewall or security settings: Firewalls or security settings on the server hosting the MySQL database may block incoming connections, resulting in SQL Error 1045. It is essential to check the server’s firewall and security settings to ensure that they are configured correctly to allow MySQL connections.
5. MySQL server configuration issues: Incorrect configuration settings in the MySQL server can also lead to Error 1045. For example, if the MySQL server is not configured to allow remote connections, users may encounter this error when trying to connect from a remote host.

Fix SQL Error 1045

Fixing SQL Error 1045 requires identifying the root cause of the issue and taking appropriate steps to rectify it. Here are some common solutions to fix Error 1045:

Verify Your Credentials

The first step in resolving SQL Error 1045 is to verify that you are using the correct credentials to connect to your database server. Double-check the username and password you are using in your database connection settings or in your SQL command. Ensure that you are using the correct username and password combination that has the necessary privileges to access the database.

Check for Typos

Sometimes, a simple typo in your username or password can result in SQL Error 1045. Make sure that you have spelled your username and password correctly, paying attention to uppercase and lowercase letters. Also, check for any special characters or spaces that may have been mistakenly included in your credentials.

Grant Sufficient Privileges

If you are still unable to connect to the database and receive SQL Error 1045, it could be due to insufficient privileges for the user account you are using. To fix this, you can grant the necessary privileges to the user account. Log in to your database server as a privileged user, such as the root user, and execute the following SQL command:

GRANT ALL PRIVILEGES ON *.* TO 'username'@'localhost'IDENTIFIED BY 'password';

Replace ‘username’ with the actual username you are using to connect to the database and ‘password’ with the actual password for that user.

This command grants all privileges on all databases and tables to the specified user account when connecting from the localhost. If you are connecting from a remote host, you may need to replace ‘localhost’ with the appropriate hostname or IP address.

Check hostname or IP address

Verify that the hostname or IP address specified during the connection attempt matches the one defined in the MySQL configuration. If necessary, update the MySQL configuration to reflect the correct hostname or IP address

Update Your Password

If you recently changed the password for the user account you are using to connect to the database and forgot to update your connection settings, it could result in SQL Error 1045. In this case, you can simply update the password in your connection settings or in your SQL command to match the new password. If you are using a MySQL or MariaDB command-line client, you can update the password using the following SQL command:

ALTER USER 'username'@'localhost'IDENTIFIED BY 'new_password';

Replace ‘username’ with the actual username you are using and ‘new_password’ with the new password you want to set.

Check for Firewall or Network Issues

Firewall or network issues can sometimes block the connection to the database server and result in Error 1045. Make sure that the port used by your database server (default is 3306 for MySQL and MariaDB) is open in your firewall and that there are no network connectivity issues between your client and the database server.

Reinstall or Reconfigure MySQL or MariaDB

If all else fails and you are still unable to fix SQL Error 1045, you may need to reinstall or reconfigure your MySQL or MariaDB server. This should be done with caution, as it may result in data loss or other unintended consequences. Before proceeding with a reinstallation or reconfiguration, make sure to backup your database and configuration files to prevent any potential data loss.

In conclusion, SQL Error 1045 can be a frustrating issue to encounter when trying to connect to your MySQL or MariaDB database server. However, by following above steps you can fix this issue.

Read More articles on SQL errors:

• Fix the Most Common SQL Syntax Error: SQL Error 1064

The post How to Fix SQL Error 1045: Resolving Access Denied Issues appeared first on Techyaz.com.

SQL Server Error 18456, also known as the “Login failed for user” error, is a common authentication error that occurs when a user fails to log in to SQL Server. The error message associated with Error 18456 usually reads:

“Login failed for user ‘<username>’. (Microsoft SQL Server, Error: 18456)”

The error occurs when SQL Server is unable to authenticate the user trying to connect to the SQL Server instance. There are several reasons why this error may occur, including incorrect login credentials, disabled user accounts, expired passwords, or issues with SQL Server authentication settings.

How to Fix SQL Server Error 18456?

Fixing SQL Error 18456 requires identifying the root cause of the error and applying the appropriate solution. Here are some common solutions to fix SQL Error 18456:

1. Verify Login Credentials: The most basic step in fixing SQL Server Error 18456 is to verify that the login credentials, including the username and password, are correct. Make sure you are entering the correct login credentials for the SQL Server instance you are trying to connect to.
2. Enable Mixed Mode Authentication: SQL Server supports two types of authentication modes – Windows Authentication mode and Mixed Mode (Windows Authentication and SQL Server Authentication) mode. If you are using SQL Server Authentication, make sure that Mixed Mode Authentication is enabled in SQL Server. You can do this through SQL Server Management Studio (SSMS) by right-clicking on the SQL Server instance, selecting Properties, and then navigating to the Security tab.
3. Check User Account Status: Ensure that the user account you are trying to log in with is not disabled or locked out. If the user account is disabled or locked out, unlock or enable the account using SQL Server Management Studio or SQL Server command-line tools.
4. Reset Password: If you suspect that the password for the SQL Server login is incorrect or has expired, reset the password. You can do this through SQL Server Management Studio or by using the ALTER LOGIN statement in SQL Server.
5. Check SQL Server Error Logs: SQL Server logs detailed information about authentication failures in its error logs. Review the SQL Server error logs to identify any specific error messages related to Error 18456. The error logs may provide additional insights into the root cause of the issue.
6. Verify SQL Server Permissions: Ensure that the user account has the necessary permissions to log in to the SQL Server instance. Check the server-level and database-level permissions for the user account and grant the appropriate permissions if necessary.
7. Check Firewall Settings: If you are connecting to a remote SQL Server instance, verify that the appropriate ports are open in the firewall to allow communication between the client and the server. Check the firewall settings on both the client and server machines to ensure that they are not blocking the required ports.
8. Check SQL Server Version: Error 18456 can also occur if there is a version mismatch between the SQL Server client and server components. Ensure that the SQL Server client version matches the server version to avoid compatibility issues.
9. Apply SQL Server Service Packs and Cumulative Updates: Microsoft regularly releases service packs and cumulative updates for SQL Server that address known issues and provide bug fixes.

You can also read the below articles to fix SQL error 18456:

• Fix SQL Error 18456: failed to open the explicitly specified database
• Fix SQL Server Error 18456: Login failed for user ‘User_Name’.
• Fix Error 18452: Login failed. The login is from an untrusted domain

The post How to Fix SQL Server Error 18456: A Comprehensive Guide appeared first on Techyaz.com.

Login Failed – Error: 18456, Severity: 14, State: 38

Reason: Failed to Open the Explicitly Specified Database

Fix Error “Failed to Open the Explicitly Specified Database”

The error log is saying “Failed to Open the Explicitly Specified Database“, it means either your have specified wrong database in your connection string or your login does not have access to the specified database. You can validate below options to isolate this issue.

• Check whether you have specified correct database in your connection string or not
• If you are using correct database then whether the login you are using to establish database connection has access to this specified database or not.
• Correct if you find something in any of the above two options.
• Check login properties whether it is using correct database as default database configuration or not. If correct database is defined then login has access to that database or not. I will explain about this step in below section as well.
• You should also check whether number of connections to the database is exhausted or not. Review your maximum number of connections setting.
• Ensure your database is not set to AUTO CLOSE setting or not inaccessible. Database should be online and healthy state to accept connections.
• Make sure you have a trust between both machines, database server and the machine from where you are trying to connect. I would suggest you to read below article as well where i have explained various steps to troubleshoot SQL Server connection issues.

Read more articles on SQL error 18456 and connection issues:

• How to Fix SQL Server Error 18456: A Comprehensive Guide
• How to fix SQL Server error 53 – Not able to open database connection
• Fix SQL Server error 18456 – Login failed for user

Let’s learn how to check default database settings for a SQL Server login and a user mapping for any database to the login.

Check Login Properties

The solution to fix this issue can also come by reviewing the properties of this login. Launch its properties window and change the default database to the correct one if this setting is showing wrong database. Sometimes, we drop the databases from the SQL Server instances but never update other objects. If this login is not showing any database and it is showing blank then click at its drop-down to choose your desired database as the default database for this login. Click on Ok button to apply that change. You will stop getting this issue after making this change.

You can open login properties windows by right click at the identified login and then choose properties from dropdown options.

Sometimes, you have chosen the default database as “master” but your login doesn’t have connect permission on master database so ensure you have at least connect permission on the database which you are choosing as the default database for your login. You can click at “User Mapping” tab from left side pane of the login properties window. You will get all databases in top side of right side pane and level of access in bottom side pane. Click at your database from right side pane along with its level of permission which you want to assign. Click at Ok button to apply this change.

Have a look at below screenshot to understand default database of a login and from where you can access User Mapping tab to provide appropriate access to your database. Your login should have access to both databases, the one mentioned as default database for your login and the specified database in connection strings.

You can fix SQL error “Failed to Open the Explicitly Specified Database” by following above steps. Write your feedback if you have fixed this issue by other way. I will update this article accordingly with credits.

The post Fix SQL Error 18456: failed to open the explicitly specified database appeared first on Techyaz.com.

A connection timeout has occurred on a previously established connection to availability replica ‘manvendradbggp03’ with id [availability group id]. Either a networking or a firewall issue exists or the availability replica has transitioned to the resolving role.

You may also receive similar issue under different alwayson error 35201. Below error will generate while attempting to establish the connection to availability group but failed because of connection timeout error 35206. The error text of this SQL error 35201 is given below.

A connection timeout has occurred while attempting to establish a connection to availability replica ‘manvendradbggp03’ with id [availability group id]. Either a networking or firewall issue exists, or the endpoint address provided for the replica is not the database mirroring endpoint of the host server instance.

If you are always getting above issues and unable to establish any connection to its respective availability replica then you should immediately look in to network side whether there is poor network latency, any network packet drop issue or firewall is blocking some connections or not as suggested in error code. But if you are getting this issue on intermittent basis then you should keep reading this article to understand more about alwayson error 35206.

SQL Server Error 35206 and Error 35201 in Always on

Both errors come because of connection timeout error between their respective replicas. Microsoft has categorized these errors as product issue and released cumulative updates to fix them. You should also consider these cumulative updates as per your SQL Server version. These issues will be very problematic if you will not address them on time because of below reasons:

• Availability databases will stop synchronizing. This could be a risk of potential data loss.
• Log file will start growing on your primary replica. This could be a potential risk for an outage if we will not address this issue on time.
• Frequent repetitive alerts for your critical systems

You must fix this issue by applying the cumulative update to avoid above problematic scenarios. But if you already have applied these updates and are still facing these issues then i would recommend you to read below section to try out other options.

Fix Always on Connection Timeout SQL Error 35206

Generally, this problem encounters only on high end systems where you have more than 24 cores CPU and SQL Server is highly transactional. One very simple workaround to overcome this issue is to restart SQL Server service on your secondary replica where you are getting this issue. Don’t restart SQL Server on primary replica. Restarting SQL Server on impacted availability replica will surely fix the issue for the time being.

Additionally, you should consider below checks to review and make changes accordingly as per your system design if you are still getting this issue on frequent basis.

Use Default Network Packet Size

Review network packet size configuration in SQL Server. Microsoft suggested to keep network packet size configuration with default value but sometime we make changes as per our need and forgot to revert these changes to their original values so i would recommend to revert this change to its default value. Read below article if you want to learn how to change network packet size configuration in SQL Server.

• How to Change Network Packet Size in SQL Server?

You should also consider evaluating your network bandwidth and firewall settings to make sure and isolate the issue. I would suggest you to work with network engineer on this front to review network or firewall related configurations.

Review Connection Timeout Setting

Another option i would recommend you to evaluate and review the session or connection time out settings. Make sure that session timeout setting for your always on configuration must be more than or equal to 10 seconds. You can consider increasing session time out if you have slow network between your replicas. Although if you are running highly transactional databases on high end box i assume you already have good network bandwidth but nothing wrong in reviewing the settings. Read below article if you want to reconfigure or change session time out in always on availability group.

• How to Change Session Timeout in Always on Availability Group Configuration?

If you are running your always on availability group configuration between multi subnet environment then i would recommend you to read attached Microsoft article to fix connection timeout errors in multi subnet availability groups.

Read More:

• Fix SQL Server Error 976: Cannot connect to Secondary Replica of AlwaysON Availability Group
• SQL Server Alwayson Error 35250: Joining database on Secondary Replica resulted in an error
• Fix SQL Server Error 19471: Listener issue that came during Configuring SQL Server AlwaysOn Availability Group
• SQL Server Alwayson Interview Questions & Answers

The post Fix Always ON Connection Timeout Error 35206 in SQL Server appeared first on Techyaz.com.

A transport-level error has occured when receiving results from the server. (provider: TCP Provider, error: 0 – The semaphore timeout period has expired.) (Microsoft SQL Server, Error:121)

This was an intermittent issue and when we were executing the script from other server it was not throwing any issue. I did some research on this and found out that this error came because of unstable network connectivity.

SQL Server Error 121 The Semaphore Timeout Period Has Expired – Root Cause

There are various parameters that can affect network connectivity like network adaptors, packet drop, configured packet size etc. So i would suggest first you should connect to your network team and ask them to look into this issue. If network team has not found anything then you need to check application level network configurations at your level.

You should ask some questions to your network resource like whether any network packet drop being observed or not, or is there any NIC card issue etc. Let’s assume you have already reached out to network team and they haven’t found anything. I would suggest you to look into below options at your level to make sure everything is in place and not misconfigured.

• Check TCP\IP settings
• Ensure you have appropriate network packet size configured in SQL Server
• Make sure you have properly configured TCP Chimney Offload
• Validate you don’t have Network Interface Card (NIC) driver issue, you can get it checked with your network team

Solution

I have already described high level areas where you need to look in in above section. Let’s discuss them further here.

Check TCP\IP settings

You should open SQL Server configuration manager and check whether TCP configuration is properly done or not. Make sure to review all settings in SQL Server Network configuration settings. You should also read below article about this settings which causes a network error.

• Fix: SQL Network Interfaces Error 28 – Server doesn’t support requested protocol

Review Network Packet Size

You should also review network packet size configuration in SQL Server. This could be one of the possible reason for this issue. Ideally we should not change the default value of this setting and keep it as it is until you have a specific requirement to change network packet size. Read below article to understand and learn network packet size in SQL Server and also step by step process about how to change the network packet size to your desired value.

• How to Change Network Packet Size Configuration in SQL Server

TCP Chimney Offload

This settings is very important if we have network related connectivity issue. TCP Chimney Offload is a networking technology that helps transfer the workload from the CPU to a network adapter during network data transfer. It can be enabled or disabled in the following two locations:

• The operating system
• The advanced properties page of the network adapter

TCP Chimney Offload will work only if it is enabled in both locations. By default, TCP Chimney Offload is disabled in both these locations. However, OEM installations may enable TCP Chimney Offload in the operating system, in the network adapter, or in both the operating system and the network adapter.

Validate Network related Driver Issues

You should speak to your network resource and Windows OS platform resource and validate all drivers at OS layer and network layer should be up to date and they should not have any issue. Make sure to update the drivers if you found any issue any of these layer.

I hope you can fix your issue by following above steps mentioned in this article. Comment us how you have fixed this issue, the semaphore timeout period has expired.) (Microsoft SQL Server, Error:121)

Related Articles

• SQL Server Error 40: A network-related or instance-specific error occurred while establishing a connection to SQL Server.
• Fix Error 1418: The server network address cannot be reached or does not exist.
• Fix: SQL Network Interfaces Error 28 – Server doesn’t support requested protocol
• SQL Server Native Client Error 50000: A network error occurred while attempting to read from the file

The post Fix SQL Server Error 121 – The Semaphore Timeout Period Has Expired appeared first on Techyaz.com.

SQL Server Native Client Error 50000

Before explaining about SQL native client error 50000, i would like to describe about what is SQL Server native client. As per MSDN “SQL Server Native Client, is a term that has been used interchangeably to refer to ODBC and OLE DB drivers for SQL Server.” 

SQL Server Native Client is a technology that we can use to access data in a SQL Server database. There are several factors you should consider while deciding whether to use SQL Server Native client or some other data access technology. You can read attached article about when to use SQL Server Native Client.

Generally, we get SQL Server native client error 50000 while installing or updating native client software or a software component that uses SQL Server Native Client and your target machine already have this installed previously using some msi file.

You can also get this issue if SQL Server native client file sqlncli.msi has been renamed after its installation and later today when you are trying to update it, you will end up with this SQL error 50000 . If somehow native client installation file has been renamed on your machine, setup will not find its file to update SQL Server native client and through below error.

A network error occurred while attempting to read from the file <Filename>.”

Solution

To fix this error, you should uninstall installed version of SQL Server native client from add/remove program and then you can try to install SQL Server or its component again. This time you will not get any error and your software or native client will be installed. To avoid further issue, you can reboot the machine post uninstalling the native client tool.

If you are installing only SQL Server native client and not SQL Server then you can download it from Microsoft website and then reinstall it again.

You can also prevent this error to not generate in future by not installing it using its msi file sqlncli.msi. If you had installed it using this file, make sure to never rename it as well.

Here, I have shown you how to fix SQL Server Native Client Error 50000, “A network error occurred while attempting to read from the file <Filename>.”  I hope you like this article. Please follow our Facebook page and Twitter handle to get latest updates.

Read More:

• Fix SQL Server Error 5009: One or more files listed in the statement could not be found or could not be initialized
• Fix SQL Server Installation Error: Attributes do not match
• How to Fix SQL Server Installation Error 1639?
• SQL Server DBA Interview Questions & Answers

The post SQL Server Native Client Error 50000: A network error occurred while attempting to read from the file appeared first on Techyaz.com.

Microsoft SQL Server Error 5009 While Adding Database File

I was working on a migration project where we had to load huge data in a SQL Server database on the target server. To optimize data load performance, we had decided to create database with the final size on the destination server. The final size of database post data import was around 800 GB. We made some configurational changes to reduce data import time. Extending database files size was one of the step to reduce data load time. If you want to learn how to speed up data import then I would suggest reading attached article.

We decided to add one more log file on separate drive considering extensive log growth during data load. While adding the log file, we got error 5009. Full error details are given below.

One or more files listed in the statement could not be found or could not be initialized. CREATE FILE encountered operating system error 5(Access is denied.) while attempting to open or create the physical file ‘T:\Techyaz_log3.ldf’.(Microsoft SQL Server, Error: 5009)

As error suggests, I don’t had enough permission to create this file on given location where i was trying to create the log file. There are two solutions to fix this issue. First solution is to set the Operating system permission on the mentioned .ldf file to full permission for your login account and SQL Server service account. While second solution is to change the location to the path where you have enough permission to create or add database files. Any of these two solutions will fix your problem. Let’s go to another version of Microsoft SQL Server Error 5009 while extending the log file.

Microsoft SQL Server Error 5009 While Extending the Size of Log File

When i changed the location to create this ldf file to a directory T:\Data\Techyaz_log3.ldf this time log file was created but we get same issue again while extending the size of this log file. Next, I was assigning bigger value to each data and log files. We had successfully increased data files size in few minutes because we had already enabled Instant File Initialization to skip zeros process on storage but we faced Microsoft SQL Server error 5009 again while increasing the size of log files. i was extending  log file with bigger values. As we know Instant File Initialization does not work for transaction log files so extending the size of log files was taking lot of time. This time access denied issue was disappeared but error 5009 issue was there only. Error description for this error is given below.

Msg 5009, Level 16, State 9, Line 1
One or more files listed in the statement could not be found or could not be initialized.

To fix this error, we had passed small value to extend the file size. Earlier we were trying to increase the log file in a slot of 40 GB in single go. It was taking time to finish but most of time log file size got extended with 40GB but sometimes we had received above Microsoft SQL Server error 5009. When we got this error, we extend the size of log file to 10Gb in place of 40GB that we were doing previously. Reducing the value while extending the log file has fixed this issue and log files had been extended to its future size successfully.

Microsoft SQL Server Error 5009 While Removing Database File

Some of the blogs have suggested that they got SQL Server error 5009 while removing a logical file in SQL Server but surprisingly I got this error while creating or increasing the size of log file. So if you are getting this error while removing any database file then you can keep reading this article to solve this issue.

Whenever we add any database file then its entry got captured in system catalog files, if you are trying to delete any database file then there might be possibility that logical name of the file that you try to remove is not unique in the system catalog tables. For example, this issue occurs if the file existed in the database earlier, and then the file was removed. When you remove the file, it will try to drop earlier file that has been removed but its metadata is not cleaned and appear like ghost file.

You should follow below steps to fix this issue.

• Create a new logical file with different name and the same data type. For example, If your file;s logical name is Techyaz_Logical_Name then create this new file with “Techyaz_Logical_Name_New”. Run below command to create this file.

ALTER DATABASE [Techyaz] 
ADD FILE ( NAME = N'Techyaz_Logical_Name_New', FILENAME = N'T:\DATA\Techyaz_file4.ndf', SIZE = 10MB, MAXSIZE = 100MB)

• Now we will remove the logical file that we have created in step 1, as in the following example:

ALTER DATABASE [Techyaz] REMOVE FILE [Techyaz_Logical_Name_New]

• Run a transaction log backup of the database.
• Now go ahead and remove the logical file that were trying to remove earlier and your received Microsoft SQL Server Error 5009.

Here, I have described multiple possibilities and fixes for Microsoft SQL Server Error 5009. I hope you like this article. Please follow us on our facebook page and on Twitter handle to get latest updates.

Read More:

• Manage Transaction Log File during Data Load
• How to get total no of virtual log files in a transaction log file
• Fix Error 3023: Shrink failed for Log file
• Understanding SQL Server Transaction Log Architecture
• Fix SQL Server Error 1105: Could Not Allocate Space for Object in Database because the Filegroup is Full
• Fix SQl Server Error 5144 and 5145 for long and failed Autogrow of data and log file

The post SQL Server Error 5009: One or more files listed in the statement could not be found or could not be initialized appeared first on Techyaz.com.

Error 1105, Severity 17, State 2
Could not allocate space for object ‘Object_Name’ in database ‘DB_Name’ because the ‘Primary’ filegroup is full. Create disk space by deleting unneeded files, dropping objects in the filegroup, adding additional files to the filegroup, or setting autogrowth on for existing files in the filegroup.

Error 1105 – Root Cause

As error suggests, this issue was generated because database was not able to allocate space anymore. Whenever you get such space issue, all transactions will be stopped until you make some room in the database. All transactions will be stopped because of non availability of space because none of the transaction will get any space to proceed their transactions. There are many reasons you can get space issues. Some of them are:

• Data or Log drive is full.
• Database file/s has restricted file growth
• Database File Autogrowth is not enabled.
• Some tables are growing faster than our prediction.
• Some long running transaction is eating all space.

We generally get error 1105 when any database including tempdb or any transaction log file get full and runs out of space. File growth restriction is also a possible reason you can get error 1105. Make sure to check all database files associated with your database to make sure there is no file growth restriction is set that is causing to generate this error. Sometimes when you restrict the file growth and the file size reached its limit, you may get this error message when trying insert / updates on database. I have explained multiple solutions to overcome this issue. Have a look at below section to get the solution of such space issues.

Solution

To fix this error we need to make space in the database so that all running transactions can execute and log their operations. We have multiple solutions to fix such issue based on the nature of the issues. Some of the solutions are given below:

• First you should check if any unwanted file is not there in data or log drive. Sometimes we placed backup files in data or log drive and forgot to delete it. Make sure to remove or move such unwanted files to make space for your database.
• If any of the database files have restricted file growth then you should immediately turn on autogrow feature of the data or log file. You can read below article to understand what should be the perfect value for autogrowth of a data or log file.

How to Enable Autogrowth and What should be the Best value for File Autogrowth?

• If size of your database file is limited to some value then make sure to extend the size of that file or I would suggest going with unrestricted growth. Read above attached article to get more about this.
• If your data or log drive is running out of space then you should add more files to the file group on different drive where you have enough space. You can use below command to add any data or log file to your desired drive. Make sure to change the drive path as per your correct path.

ALTER DATABASE Techyaz
ADD FILE (
NAME = techyaz_Data3,
FILENAME = 'F:\MSSQL\DATA\techyaz_DataFile3.ndf')

• We can also free disk space by dropping index or tables that are no longer needed. You can also consider data purging for unwanted tables or indexes.
• You can also consider moving some of the database files to different drive to make some space for your database.

I hope you like this article. Please follow our Facebook page and Twitter handle to get latest updates.

Read More:

• Fix Error 1101: Could not allocate a new page for database
• Why should we Avoid Database Shrink Operation?
• Why should we always Disable Autoshrink property?

The post Fix Error 1105: Could not allocate space for object in database because the filegroup is full. appeared first on Techyaz.com.

Msg 15123, Level 16, State 1, Procedure sp_configure, Line 51
The configuration option ‘xp_cmdshell’ does not exist, or it may be an advanced option.

The screenshot of the error is given in below image.

You might get this error while changing or viewing values of any advanced server configuration option. Here I will show you how to fix this error and make such changes successfully.

Error 15123 – Root Cause

As we know, there are lot of server level configurations that we can see or change using command sp_configure. Some of the server level configuration options categorized as advanced options and that cannot be viewed or changed if the value of “show advanced options” is set to 0 or disabled.

We can view “show advanced options” value by running sp_configure command. If the run value of this command is set to 0 it means this option is disabled and you cannot see any advanced server configurations.

To see or change the advance server level configurations we need to enable “show advanced options” by setting its value to 1 using sp_configure. Run below command to check the current run value for “show advanced options”. You can also simply type sp_configure command and execute it to get its details along with all other server configuration options.

exec sp_configure ‘show advanced options’

We can see run value of parameter “show advanced option” is set as zero it means we cannot view or change any advanced server configurations using command sp_configure.

This is the main reason behind getting error 15123 and we can get this error while changing any advance server level parameters. Read below section to enable “show advanced options” and change the values of advanced server configurations.

Solution

Generally, we get error 15123 because “show advanced options” is disabled and set to zero and it’s not allow to do anything with advanced server options. As we have seen “show advanced options” is set to zero in above screenshot. Here, we will enable it and then run again same command that we have ran in first screenshot to enable xp_cmdshell extended procedure.

Let’s enable “show advanced options” option to view or change the advance server level configurations by running below command.

exec sp_configure ‘show advanced options’, 1
 RECONFIGURE WITH OVERRIDE

Above command has been executed successfully. You can see this in below screenshot.

Now we can go ahead and view any advanced options by running simply sp_configure command. If you need to make any changes on existing values of advanced server options then also you can do it using sp_configure command now. Let’s go ahead and run same command that we had ran in first image to enable xp_cmdshell.

exec sp_configure 'xp_cmdshell', 1
 reconfigure with override

We can see this command has been executed successfully this time without any error.

Whenever you get error 15123 while viewing or changing values of any advanced option you should first enable or set the value for option “show advanced options” then you can make your desired changes accordingly.

I hope you like this article. Please follow our Facebook page and Twitter handle to get latest updates.

Read More:

• How to change Network Packet size in SQL Server
• Fix Error 233: How to Set the User Connections Server Configuration option in SQL Server
• Understanding SQL Server Memory Allocation
• SQL Server DBA Interview Questions & Answer

The post Fix Error 15123: The configuration option does not exist. appeared first on Techyaz.com.

The server network address “TCP://ServerName.abc.local:5022″ cannot be reached or does not exist. Check the network address name and that the ports for the local and remote endpoints are operational. (Microsoft SQL Server, Error: 1418)

Reason behind Error 1418

Main reason behind database mirroring error 1418 is because the specified server network address cannot be reached or does not exist. The server network address cannot be reached because of multiple reasons. Some of them are given below.

• Principal, Mirror and Witness servers are not talking to each other.
• Wrong network address name, mirror server instance name or port number.
• Mirror database is not ready for mirroring.
• Principal or mirror server instance is behind a firewall.
• You are using local system account to run SQL Server services and not using certificates for authentication.
• SQL Server services are running with different domain accounts on Principal and Mirror server and service accounts don’t have enough permission on endpoints.
• Different endpoint encryption value set on Principal, Mirror and Witness server.
• Endpoints are not started on the partner servers.
• Principal server instance is not listening on the port assigned to its database mirroring endpoint.

We need to verify each option mentioned above carefully to fix this error.

Solution

The solution of this issue may vary case to case depending on the nature of issue. To fix this issue we need to find out the main root cause behind error 1418. The root cause may be anything that is given in above section. Here I will describe each probable reason given above and its solution to fix this issue. Make sure to go through with each point given in this article.

Principal, Mirror and Witness Servers Should be Accessible

Make sure that SQL Server Instances installed on Principal, Mirror & Witness servers are accessible to each other. If remote login for any SQL Server instance is not enabled then you might get this issue. You can enable remote connectivity by enabling TCP/IP and Named Pipes protocols in SQL Server Configuration Manager. Each system must access the ports of the other SQL Server instances over TCP. You can try telnet the SQL Server ports of other partners.

Verify Correct System Details 

Sometimes we entered wrong details that end up with throwing errors. Make sure to verify the network address name, mirror server instance name and its port numbers are correct. You can recheck all the details whether you have entered them correctly or not.

Mirror Database Preparation

Verify that the mirror database is ready for database mirroring. We should prepare mirror database before configuring or during configuring database mirroring. It is suggested to keep identical drive path for mirror database files. Below are the steps you should take care for preparing your mirroring database.

• Run full backup and subsequent transactional log backup of the Principal database and copy it to the Mirror server.
• Restore database with same name in norecovery state on Mirror server with the copied backup files from above step. You must ensure that restored database on mirror server should be in restoring mode before starting database mirroring configuration.

Firewall/Ports

One of the probable reason to get error 1418 is partner servers are behind firewall. Make sure that the principal server instance and destination mirror server instance is not behind a firewall and they should talk to each other. Principal server, Mirror server and witness server should be accessible to each other.

Verify that SQL Server port and endpoint ports are enabled and accessible via telnet. If not or you are not able to telnet any of the partner instance from any server participating in mirroring then you should ask your network admins to open these ports to establish the connectivity over given port.

Endpoints

Make sure that endpoint has been created on principal, mirror and witness servers. Verify that the endpoints are started on each partner server instances. You can check endpoint status by running below T-SQL query on each instance.

SELECT state_desc FROM sys.database_mirroring_endpoints

If either endpoint is not started, execute below ALTER ENDPOINT statement to start it.

#Change the name of your endpoints. Here endpoint name is Mirroring
ALTER ENDPOINT Mirroring
STATE = STARTED
AS TCP (LISTENER_PORT = <port_number>)
FOR database_mirroring (ROLE = ALL);
GO

Recheck that the principal server instance is listening on the port assigned to its database mirroring endpoint and the mirror server instance is listening on its port. If a partner is not listening on its assigned port, modify the database mirroring endpoint to listen on a different port.

Sometimes this issue got fixed by dropping the existing endpoint and recreate it again on partner servers.

Service Accounts

Do not use local system account to run SQL Server services. If you don’t have any choice and want to use local system then ensure to use certificates for authentications.

Make sure that service accounts that you are using to run SQL Server services must have CONNECT permission to mirroring endpoints. Also, if you are configuring database mirroring between two domains then the login of one account must be created in master database on the other computer, and that login must be granted CONNECT permissions on the endpoint.

It’s always advisable to use same service accounts to run SQL Server services on all three Instances on Principal, Mirror and Witness server.

You can comment us your experience about fixing this issue. We will update this article with your solution that you have used to fix this issue.

I hope you like this article. Please follow us on our Facebook page and Twitter handle to get latest updates.

Read More:

• Fix Error 15141: The server principal owns one or more endpoints and cannot be dropped
• Fix AOAG Error 35250: Joining database on Secondary Replica resulted in an error
• How to Upgrade or Patch Availability Group Instances?
• SQL Server Always On Interview Questions and Answers

The post Fix Error 1418: The server network address cannot be reached or does not exist. appeared first on Techyaz.com.

A connection was successfully established with the server, but then an error occurred during the login process. (provider: Shared Memory Provider, error: 0 – No process is on the other end of the pipe) (Microsoft SQL Server, Error: 233)

You can see the screenshot of this error that I had received while making a database connection.

SQL Server Error 233 No process is on the other end of the pipe – Root Cause

Above SQL error 233 suggests the provider name as Shared Memory Provider. We know Shared Memory is a protocol used in SQL Server along with TCP/IP and Named pipe. We decided to check the settings and values for all protocols in SQL Server Configuration Manager.

I launched SQL Server Configuration manager and expanded SQL Server Network Protocols from left side pane. Here, you can see an option “Protocols for MSSQLSERVER”.  MSSQLSERVER is the name of SQL Server Instance as default instance has been installed there. If you have named instance installed on your machine then you might get “Protocols for <INSTANCENAME>.

Now click on this option “Protocols for MSSQLSERVER”, you can see all three protocols used in SQL Server in right side pane as shown in below image.

Here we can see Shared Memory protocol is set as Enabled but Named Pipes is set as Disabled that should be enabled to make successful database connection. This was the main reason for getting this error. Keep reading this article to fix this issue in next section.

I have also written another aspect of SQL Server Error 233 in below article. You might get this error if your SQL Server Instance has exceeded the total number of user connections set in server configurations. Have a look at this article as well.

• Fix SQL Server Error 233: User Connections Server Configuration option in SQL Server

Solution

We get error 233 ( SQL Server no process is on the other end of the pipe )because SQL Server client cannot connect to the server. This error could occur because the server is not configured to accept remote connections. To fix this issue, we will use the SQL Server Configuration Manager tool to allow SQL Server to accept remote connections. Here, in our case one of the protocol Named Pipe was disabled that’s why we were getting error. We will go ahead and fix this issue by enable the Named Pipe protocol. You might get this issue due to any protocol being disabled.

Make sure to enable Shared Memory, TCP/IP and Named Pipe protocols. Launch SQL Server Configuration Manager. Expand SQL Server Network Configuration from left side pane and click on Protocols for MSSQLSERVER. MSSQLSERVER is SQL Server Instance name. Now you will see all protocols in to right side pane. Right click on given protocols that is disabled and select Enable button to enable that protocols.

Named Pipe protocol was disabled in my case so I have launched Properties window of this protocol and selected Enabled option as Yes from dropdown as shown in below screenshot. Now click on Apply and Ok button to apply this change on SQL Server. It will ask you to restart the SQL Server service to apply these changes in to effect. Restart SQL Server services from SQL Server Configuration manager. Once services will come online, try to connect to your SQL Server instance, this time you will not face error 233 and you will be able to make successful database connection.

If you are still facing same issue ( no process is on the other end of the pipe )then you can also check “Allow Remote Connections” settings for this SQL Server instance. This setting must be enabled to connect to databases remotely. Connect to SQL Server Instance in SSMS locally on database server. Right click on SQL Server instance name in SSMS and choose Properties. You will get Server properties window. Click on Connections from left side pane and tick the check box on Allow remote connections to this server option from right side pane.

I hope you like this article. Please follow our Facebook page and Twitter handle to get latest updates.

Read More Articles on SQL Server Connection Issues:

• Fix SQL Server Network Interfaces Error 28: Server doesn’t support requested protocol
• Error 40: A network-related or instance-specific error occurred while establishing a connection to SQL Server
• Fix Error 53: Could not open a connection on SQL Server
• Fix Error 4064: Cannot open user default database
• Error 233: How to set the user connections server configuration option in SQL Server

The post Fix SQL Server Error 233: No process is on the other end of the pipe appeared first on Techyaz.com.

Product: Microsoft SQL Server Browser – Update Service Pack 1 for Microsoft SQL Server Browser (KB-NUMBER)’ could not be installed. Error code 1639.

Root Cause

I was not able to find any reason behind this error because I had followed all prerequisites before starting this installation. I went to some forums to get a root cause of this error 1639 or solution to fix it and what i found is described in this article.

This issue (Error 1639) comes when there is a blank space between your SQL Server setup folder directories. As I found my setup files were placed under a directory named “SQL Server 2012”. You can see there are two blank space between this directory name. This was the main reason or cause behind getting this SQL Server installation error. Read next section to fix this issue and install SQL Server successfully on your database server.

Resolution

To fix this issue, we have decided to first uninstall SQL Server instance that was failed to install. I have uninstalled it from “Add and Remove Programs” and deleted all SQL Server folders that was created during the installation. Once failed installation of SQL Server was uninstalled from database server, we have rebooted the machine to proceed with fresh installation.

As I mentioned above, issue was due to blank space between the parent directory of SQL Server setup files. You can see the name of directory in below screenshot.

Now I have removed the blank space between the words of this folder name and changed it to “SQLServer2012”. You can see the below screenshot of this change.

That’s all to fix this issue. Now go ahead and start the installation again for your work.

Once this directory was renamed, I have started the SQL Server installation process. I had launched setup file and proceed for installation. You can also right click on setup file and choose “Run as Administrator” to start the installation. Follow all windows and processes of installation process as you did last time to install it. This time your SQL Server instance will be installed without any issue.

The key takeaway from this issue is to never keep any bank space between files or folders otherwise you will be end up with similar issues.

I hope you like this article. Please Like, Share, Comment & Subscribe to this website to get all new articles directly to your index. You can also follow our Facebook page and Twitter handle to get latest updates.

Read More:

• SQL Server Interview Questions & Answers on Architecture
• SQL Server Interview Questions & Answers on Indexes
• Microsoft SQL Server DBA Interview Questions & Answers
• SQL Server Interview Questions & Answers on Backup & Recovery

The post How to Fix SQL Server Installation Error 1639? appeared first on Techyaz.com.

Msg 5144
Autogrow of file ‘Data or Log file name’ in database ‘Database’ was cancelled by user or timed out after <n> milliseconds. Use ALTER DATABASE to set a smaller FILEGROWTH value for this file or to explicitly set a new file size.

Or you will get below message if autogrow operation or data/log file size increase operation will run for longer duration than expected.

Msg 5145
Autogrow of file ‘Data or Log file name’ in database ‘Database’ took <n> milliseconds. Consider using ALTER DATABASE to set a smaller FILEGROWTH for this file.

Whenever data or log file growth operation is taking lot of time then a wait type PREEMPTIVE_OS_WRITEFILEGATHER will be shown in to SQL Server. If you want to read more about this wait type then click at the attached link. 

Root Cause

Data and log file initialization takes lot of time if you have to create large database files or large data or log file growth will be performed. Whenever we allocate or extend space to data or log file, it first fills with zeros. Zeroing operation takes lot of time for bigger size autogrowth operations that causes for longer run to complete. We generally see these messages (5144 or 5145) during either extending the data or transaction log files or during autogrowth operation for data or log files.

Microsoft has given a solution named Instant File Initialization to fix the time consuming file size allocation for data files. Once Instant File Initialization will be enabled, your data files size allocation will be done in faster way but unfortunately Instant File Initialization does not work on transaction log files.  Instant file initialization reclaims used disk space without filling that space with zeros. Instead, disk content is overwritten as new data is written to the files. Read below section to overcome these error messages.

Solution

To avoid these messages 5144 or 5145 to be logged, we should plan file size growth carefully. We should set maximum size of the database so that it could not perform frequent autogrowth operation. We can enable Instant File Initialization feature to speed up the data file size allocation. It is not recommended to rely on autogrowth of files as standard operation for obtaining more space in a file. Rather, you should plan out the maximum size of your database and/or transaction log file and allow autogrowth to occur only in unplanned situations for space. Follow below points to avoid this error.

• Enable Instant File Initialization to speed up data file size allocation. Read attached article to enable IFI (Instant File Initialization) on your database server.
• As IFI (Instant File Initialization) does not work on log files so we need to set log files in smaller chunks to avoid any time out error or longer runs.
• Set database size to the maximum size it could be and allow autogrowth settings to occur only in unplanned situations for space.Read attached article to understand Autogrowth setting and its perfect value for database files.

I hope you like this article. Please follow our Facebook page and Twitter handle to get latest updates.

Related Articles:

• Manage Transaction Log File during Data Load
• How to Improve Bulk Data Load Performance?
• How to Reduce SQL Server Wait type PREEMPTIVE_OS_WRITEFILEGATHER?
• Why Should You Always Turn Off Database Auto Shrink Property?
• Fix Error 3023: Shrink failed for Log file

The post Fix SQL Server Msg 5144 and 5145 for long or failed autogrow of data and log files appeared first on Techyaz.com.