Explore information related to sql error


PostgreSQL Error code 23505 - Fix it Now ?


This article covers methods to fix PostgreSQL Error code 23505 for our customers. This issue happens when you are trying to insert a value in a column that already exists there. If you have a sequencer on the field (like with a serial column type), it is likely out of sync with the table because you have done an insert and supplied a value (rather than letting the "default" mechanism handle it by getting the nextval from the sequencer). If this is the case, reset the sequencer with a setval statement to the max value of the field.

Read More



PostgreSQL Error code 42703 - Fix it Now ?


This article covers steps to resolve PostgreSQL Error code 42703 for our customers. PostgreSQL database 42703 error triggers an error message "column does not exist" which indicates either that the requested column does not it exist, or that the query is not correct.

There are many possible reasons for this issue.

To get started, check your query for any mistakes. Often, the error is caused by a lack of quotes.

If this is the case, add double quotes to the column name, then try again. 

Read More



AWS RDS MySQL Error 1227 - Fix it Now ?


This article covers how to fix AWS RDS MySQL Error 1227 for our customers. In order to fix this issue, you’ll need to leverage DB parameter groups. To modify parameter values in a customer-created DB parameter group, you can’t change the parameter values in a default DB parameter group. Changes to parameters in a customer-created DB parameter group are applied to all DB instances that are associated with the DB parameter group.

To modify a DB parameter group, use the AWS CLI modify-db-parameter-group command with the following required parameters:

--db-parameter-group-name
--parameters

Read More



AWS ERROR 2003 (HY000): Can't connect to MySQL server - Fix it Now ?


This article covers methods to tackle AWS "ERROR 2003 (HY000): Can't connect to MySQL server" for our customers.

You can easily fix this issue by adding the public ip address of my EC2 server to the DB security group default policy.

You can create a new security group with the corresponding IP range/subnet of your EC2 instances(s). You can use the exact IP(s), or use your VPC's subnet(s) as the range.

Once created, you can right click your RDS instance in the management console and select 'Modify'. From there, you can change the associated security groups.

Read More



mysqldump error 1194 table is marked as crashed - Best Fixes ?


This article covers methods to resolve the mysqldump error 1194 for our customers. Generally database administrators use MySQL tables to store some important files along with their professional data or records. Though users store their important data but they are unaware of the situation that they can also lose their important data some day when the database gets corrupt or damaged. 

When MySQL database gets corrupted then it displays several error messages, one such error is "ERROR 1194 (HY000): Table 'table_name' is marked as crashed and should be repaired". And this error is very annoying so its very important to fix MySQL error 1194 as soon as you can.


Main causes of MySQL Error 1194:

  • Due to sudden system shutdown.
  • Virus/malware infection.
  • File system corruption after the newly installed program like hardware or software.

Read More



MySQL dump error 'illegal mix of collations' - Fix it Now ?


This article covers methods to resolve MySQL dump error 'illegal mix of collations'. 

You should set both your table encoding and connection encoding to UTF-8:

ALTER TABLE keywords CHARACTER SET UTF8; -- run once

and

SET NAMES 'UTF8';
SET CHARACTER SET 'UTF8';

You can try to run SHOW CREATE TABLE my_table; and see which column was not converted or just fix incorrect character set on problematic column with query below (change varchar length and CHARSET and COLLATE according to your needs):

ALTER TABLE `my_table` CHANGE `my_column` `my_column` VARCHAR(10) CHARSET utf8 
COLLATE utf8_general_ci NULL;

Read More



AWS MySQL error 10060 – Can't connect to MySQL server ?


This article covers methods to resolve AWS MySQL error 10060. This error is a result of the inbound connection rule set on your DB instance.

For each RDS database instance we create, there are Inbound & Outbound connection-security groups.

In AWS RDS console, under 'Databases', click on the 'DB Identifier' of your RDS instance. Then in the 'Security group rules' section, click on 'Inbound' type security group and edit the inbound rule to allow appropriate inbound connections.

You get 3 options here, under 'source' column:

  • Custom.
  • Anywhere (Allows connections from any IP. Not recommended for production.).
  • My IP (Automatically detects your machine's IP).

Read More



pgAdmin "connection to the server has been lost" - Fix it Now ?


This article covers methods to resolve pgAdmin "connection to the server has been lost" error for our customers. When connecting to a PostgreSQL server, you may get this error message. From the error message you will be able to resolve the problem. 


If pgAdmin displays this message, there are two possible reasons for this:

  • the database server isn't running - simply start it.
  • the server isn't configured to accept TCP/IP requests on the address shown.


For security reasons, a PostgreSQL server "out of the box" doesn't listen on TCP/IP ports. Instead, it must be enabled to listen for TCP/IP requests. This can be done by adding listen_addresses=’*’; this will make the server accept connections on any IP interface.

Read More



"FATAL: no pg_hba.conf entry" – How to fix the PostgreSQL error ?


This article covers methods to resolve "FATAL: no pg_hba.conf entry" error. Basically, the "no pg_hba.conf entry" can happen due to missing entries in the configuration file. 


A quick way to fix this PostgreSQL server error is to do the following steps:

1. Add or edit the following line in your postgresql.conf :

listen_addresses = '*'

2. Add the following line as the first line of pg_hba.conf. It allows access to all databases for all users with an encrypted password:

# TYPE DATABASE USER CIDR-ADDRESS  METHOD
host  all  all 0.0.0.0/0 md5

3. Restart Postgresql after adding this with service postgresql restart or the equivalent command for your setup.

Read More



"psql :could not connect to server: no route to host" - Fix it Now ?


This article covers how to fix the "could not connect to server: No route to host" PostgreSQL error. Basically, the "could not connect to server: No route to host" triggers while connecting to PostgreSQL due to a number of reasons.

Make the Iptables rules different in Master and Slave.

iptables -L INPUT
iptables -P INPUT ACCEPT
iptables -P OUTPUT ACCEPT
iptables -P FORWARD ACCEPT
iptables -F INPUT 
iptables -F OUTPUT
iptables  -F FORWARD

Read More



mysqldump error "can't create/write to file" - Fix it Now ?


This article covers to fix mysqldump error "can't create/write to file" for our customers. This error can be as a result of lack of space in your /tmp keeping the file from being created. It may also be the result of a permissions error or configuration error.


We recommend restarting the service to clear any excessive temporary files:

$ /etc/init.d/mysqld restart

If that doesn't improve the situation, we recommend reviewing your configuration file and permissions, particularly if you are using SE Linux:

$ cat /etc/my.cnf | grep tmpdir
$ ls /var/tmp

Read More



"403 forbidden" error in phppgadmin - Fix it Now ?


This article covers methods to tackle "403 forbidden" error messages in phpPgAdmin. Basically, the "Forbidden" error happens while accessing phpPgAdmin when permissions in the phpPgAdmin configuration file are not intact. 


To resolve 403 forbidden error, In the Apache configuration, simply replace:

<Directory /usr/share/phppgadmin>
    DirectoryIndex index.php
    Order deny,allow
    Allow from all
</Directory>

With:

<Directory /usr/share/phppgadmin>
   Require all granted
</Directory>

Read More



"Login disallowed for security reasons" phppgadmin error – Fix it Now ?


This article covers how to resolve "Login disallowed for security reasons" phppgadmin error. Basically, the "Login disallowed for security reasons" error can happen when extra login security is enabled in the phpPgAdmin configuration file.


To fix this issue, You will need to edit the phppgadmin config file from following directory /etc/phppgadmin/config.inc.php.

Finally modify the line $conf['extra_login_security'] = true; to $conf['extra_login_security'] = false;

Read More



MySQLdump: got error :1049 :unknown database - Fix it Now ?


This article covers the best method to fix the MySQL database error, "MySQLdump: got error :1049 :unknown database".

Generally, this error happens while performing cPanel backups and it simply indicates that the database does not exist in MySQL.


How to fix mysqldump unknown database when selecting the database?

In cases where this error occurs when you specify the password on the command line with -p flag and there is a space between -p and password.

For example, if you want to dump the database named wpdb using the user "root" and password "your-password".

Fix this error, by specifying the password with no space after -p switch as shown below:

mysqldump -u root -pyour-password wpdb > wpdb_backup.sql

Read More



Can't connect to mysql error 111 - Fix this error now ?


This article covers methods to fix mysql error, 'Can't connect to mysql error 111' on Linux machine for our customers.
This can happen when there was a host IP change. 

This issue can prevent connection to the database.
As it turned out if you do come accross this look in /etc/my.cnf, there is a line:

bind-address = ip.add.ress

This may be the old address for the server and this will stop connections, change this to your new address and restart MySQL/MariaDB and you should be good again.

Read More



SQL Server divide by zero error encountered - Fix it Now ?


This article covers methods to resolve resolve error 'SQL Server divide by zero error encountered'. This error is caused by performing a division operation wherein the denominator or the divisor is 0. This error is not encountered when the denominator or divisor is NULL because this will result to a NULL value.


Many client applications or drivers provide a default value of ARITHABORT is OFF.
The different values might force SQL Server to produces a different execution plan, and it might create performance issues.
You should also match the setting similar to a client application while troubleshooting the performance issues.

Read More



SQL Server Error 9002 - Fix it now


This article covers methods to resolve SQL Server Error 9002 for our customers. SQL Server Error 9002 happens when the SQL Transaction Log file becomes full or indicated the database is running out of space. A transaction log file increases until the log file utilizes all the available space in disk. A quick fix is to create more space for log file.


To Fix SQL Server Error 9002:


1. Backup Transaction Log File

Incase, SQL database that you are using is full or out of space, you should free the space. For this purpose, it is needed to create a backup of transaction log file immediately. Once the backup is created, the transaction log is truncated. If you do not take back up of log files, you can also use full or Bulk-Logged Recovery model to simple recovery model.


2. Free Disk Space

Generally, the transaction Log file is saved on the disk drive. So, you can free the disk space which contains Log file by deleting or moving other files on order to create some new space in the drive. The free space on disk will allow users to perform other task and resolve SQL Error Log 9002 The Transaction Log for Database is Full.


3. Move Log File to a Different Disk

If you are not able to free the space on a disk drive, then another option is to transfer the log file into a different disk. Make sure another disk in which you are going to transfer your log file, has enough space.

i. Execute sp_detach_db command to detach the database.

ii. Transfer the transaction log files to another disk.

iii. Now, attach the SQL database by running sp_attach_db command.


4. Enlarge Log File

If the sufficient space is available on the disk then you should increase the size of your log file. Because, the maximum size for a log file is considered as 2 TB per .ldf file.


To enlarge log file, there is an Autogrow option but if it is disabled, then you need to manually increase the log file size.

i. To increase log file size, you need to use the MODIFY FILE clause in ALTER DATABASE statement. Then define the particular SIZE and MAXSIZE.

ii. You can also add the log file to the specific SQL database. For this, use ADD FILE clause in ALTER DATABASE statement.

Then, add an additional .ldf file which allows to increase the log file.

Read More



SQL Error 17051 – Server Evaluation Edition to Enterprise Edition


This article covers method to resolve SQL Error 17051.

This SQL error  sometimes happens when the SQL Server Evaluation period has expired.

To fix Microsoft SQL Server Management Studio error:
1. Now as per the error message you open the Event Viewer and see that the Event with ID 17051, which shows SQL Server Evaluation period has expired under Details section.
2. Now, you recall that the Instance that you had installed was under Evaluation of 180 days, because you didn’t applied any Product Key. So, now how can you make it live again? All you need is a Product key of SQL Server and some clicks.
3. Open the SQL Server Installation Center and click on Maintenance link, and then click on Edition Upgrade.
4. Now on the Upgrade window Click Next and you will reach the Product Key page, apply the Key and click Next.
5. On the Select Instance page, select the SQL Instance that you want to fix and Click next. It will take some time and finally you will see a final window and click Upgrade.
6. Finally you will see the successful window, click on Close button.

Also, you can use following command line installation option to skip this specific rule to allow the upgrade process to complete successfully:
a) Open Command Prompt (CMD)
b) Go to the folder where SQL Server Setup, setup.exe file is located (like C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\SQLServer2012\)
c) Apply following command:

setup.exe /q /ACTION=editionupgrade /InstanceName=MSSQLSERVER /PID=<appropriatePid> /SkipRules= Engine_SqlEngineHealthCheck

The <appropriatePid> should be the 25 digit Key.
The above command line runs SQL Server setup in silent mode.
Now Restart the SQL Server Service for this Instance, and you will see it running fine.
Finally, go back to SSMS and now you can connect to the SQL Instance.

Read More



Attributes do not match - Fix this SQL Server Installation Error


This article covers how to resolve the error, SQL Attributes do not match. Basically, the error, Attributes do not match occurs during SQL Server installation or during SQL Server patching activity.
Once you get this issue, you can check all drives available on your database server whether they are compressed or not. If any drive is compressed and SQL Server is using that drive during installation then that might be the reason for getting issue Attributes do not match.
You need to uncompress all such drives and then start the installation.

To uncompress the drive we need to launch property window of that drive:
1. We just need to right click on the identified drive and choose Properties to see the status of compression.
2. You can see compress this drive to save disk space option is ticked.
3. Uncheck this option and click on OK button to apply the change.
4. Once you validated all drives that none of the drives are compressed then you can start SQL Server installation and this time SQL Server installation will be successful.

When installing SQL server and running into an error "Attributes do not match.
Present attributes (Directory, Compressed) , included attributes (0), excluded attributes (Compressed, Encrypted)".
This is because you are trying to install SQL into a folder that is compressed which is not supported.
To fix this;
1. Navigate to C:\Program Files\Microsoft SQL server folder
2. Right click on properties on SQL Server folder.  
3. Under advanced option in general tab, look for compress contents to save disk space, uncheck it.
4. Also, uncheck "encrypt contents to secure data"
5. Re-run the SQL install

Read More



SQL Error 50000 - Best method to fix


This article covers method to fix SQL Error 50000.

This SQL error happens in the process of installing SQL Server Management Studio on one of the client machines.
If you receive SQL Server 50000 error on a SQL Agent Job, you need to Quit the job reporting failure.

To fix this SQL error, you can try the following queries:
1. Enable the SQL Broker on the Site database:

USE master; 
GO 
ALTER DATABASE CM_PR1 SET ENABLE_BROKER 
GO

2. SET the Site Database as trustworthy:
USE master;

GO 
ALTER DATABASE CM_PR1 SET TRUSTWORTHY ON 
GO

3. SET the Database to honor the HONOR_BROKER_PRIORITY:

USE master; 
GO 
ALTER DATABASE CM_PR1 SET HONOR_BROKER_PRIORITY ON; 
GO

Read More



SQL Server Error 5009 – Different scenarios and fixes


This article covers how to fix SQL Server Error 5009 error which occurs while adding or removing a database file or extending the database file size.
 
To fix Microsoft SQL Server Error 5009 While Adding Database File:
1. Set the Operating system permission on the mentioned .ldf file to full permission for your login account and SQL Server service account.
2. Change the location to the path where you have enough permission to create or add database files.

Read More



SQL error 300 - Fix it Now


This article covers tips to resolve SQL error 300. The reason of the error is related with user permission on VIEW SERVER STATE. You can upgrade SQL Server Management studio with the same version like SQL Instance or higher. 


Also, To mitigate this error, give the following GRANT and the error message will disappear:

USE master
GO
GRANT VIEW SERVER STATE TO "LoginName"

Read More



Configure PostgreSQL on Linux in Vesta control panel - How to do it


This article covers how to install and setup PostgreSQL on Vesta Control panel running RHEL, CentOS, Debian, or Ubuntu server. PostgreSQL is an advanced version of SQL which provides support to different functions of SQL like foreign keys, subqueries, triggers, and different user-defined types and functions.


To set up PostgreSQL on a RHEL or CentOS:

1. Install PostgreSQL packages

yum install postgresql postgresql-server postgresql-contrib phpPgAdmin

* If you have remi installed then don't forget to explicitly enable it.

yum install --enablerepo=remi postgresql postgresql-server postgresql-contrib phpPgAdmin


2. Initialize database cluster

service postgresql initdb


3. Download hba configuration

wget http://c.vestacp.com/0.9.8/rhel/pg_hba.conf -O /var/lib/pgsql/data/pg_hba.conf


4.  Start the server

service postgresql start


5. Set oracle user password

su - postgres

psql -c "ALTER USER postgres WITH PASSWORD 'pgp4sw0rd'"

exit


6. Enable pgsql databases support in vesta.

open /usr/local/vesta/conf/vesta.conf and set DB_SYSTEM to 'mysql,pgsql'


7. Register pg instance in control panel

v-add-database-host pgsql localhost postgres pgp4sw0rd


8. Download phpPgAdmin configuration

wget http://c.vestacp.com/0.9.8/rhel/pga.conf -O /etc/phpPgAdmin/config.inc.php

wget http://c.vestacp.com/0.9.8/rhel/httpd-pga.conf -O /etc/httpd/conf.d/phpPgAdmin.conf


9. Restart web server

service httpd restart


To set up PostgreSQL on a Debian or Ubuntu:

1. Install PostgreSQL packages

apt-get install postgresql postgresql-contrib phppgadmin


2. Download hba configuration

wget http://c.vestacp.com/0.9.8/debian/pg_hba.conf -O /etc/postgresql/*/main/pg_hba.conf


3. Restart the server

service postgresql restart


4. Set oracle user password

su - postgres

psql -c "ALTER USER postgres WITH PASSWORD 'pgp4sw0rd'"

exit


5. Enable pgsql databases support in vesta.

open /usr/local/vesta/conf/vesta.conf and set DB_SYSTEM to 'mysql,pgsql'


6. Register pg instance in control panel

v-add-database-host pgsql localhost postgres pgp4sw0rd


7. Download phpPgAdmin configuration

wget http://c.vestacp.com/0.9.8/debian/pga.conf -O /etc/phppgadmin/config.inc.php

wget http://c.vestacp.com/0.9.8/debian/apache2-pga.conf -O /etc/apache2/conf.d/phppgadmin


8. Restart web server

service apache2 restart

Read More



Add MySQL Service on WebsitePanel - Do it now


This article covers how to add MySQL service in websitepanel. 

WebsitePanel began as DotNetPanel, which its creators made only for the Windows web technology platform as a Windows hosting panel.


To add MySQL Service on WebsitePanel, follow the steps provided below:

1. Download the installation file from here. Choose to skip registration and start the download.

2. Run the .msi file to start the installation. Click “Next” when prompted.

3. Select the product to upgrade, then click “Next“.

4. Click “Execute” to apply the update.

5. Click “Next” to configure the product.

6. If you already have a database within your server, the installer will check and update your database. Type in the correct password and then press “Check“, then press “Next” when the connection is successful.

7. Click “Execute” to apply the configuration, then “Next” to finish this part of the installation.

8. Click “Next” to proceed.

9. The installation is completed, click “Finish” to continue.

10. This shows the product you have installed, you can close the installer here or click “Add…” to install additional products such as MySQL Server ver 5.7

11. Select the “CONFIGURATION” tab and click “Servers” from the drop-down list.

12. Next, click on “My Server“, scroll down and search for “MySQL 5” tab (since we have installed MySQL 5.5 by default).

13. Click on the small “Add” besides the “MySQL 5” tab to add MySQL service to WebsitePanel.

14. From the drop-down list, choose the version of MySQL that had been installed (MySQL Server 5.5 in our case), then click "Add Service".

15. You will see a message saying that installation of  MySQL Connector/Net is required, follow the instructions and download the installer.

16. Run the downloaded installer but DO NOT choose “Typical Installation“, choose “Custom Installation” instead and remove the entire “Web Providers” section from your installation as it will give a nasty error after installation. Proceed with the installation by clicking “Next” and then “Install“.

17. Return to the MySQL Service Properties page, fill in the password with the password used to login to MySQL root account and then click “Update” at the bottom of the page. If the password entered is correct, the MySQL service will be successfully added to the list of server services.

Read More



SQL error 1071 - Fix it Now


This article covers methods to resolve SQL error 1071 which generally happens if the combined key is too long, and adjusting the varchar value must resolve this error.

MySQL always reserves the max amount for a UTF8 field which is 4 bytes so with 255  + 255 with your DEFAULT CHARACTER SET utf8mb4 COLLATE utf8mb4_unicode_ci; 

you are over the 767 max key length limit.

You can only reduce the single varchar length or don't use a composite key.


To fix SQL error 1071:

You can also add these lines to a new conifg file in /etc/my.conf.d directory named umb4-support.cnf:

[mysqld]
innodb_large_prefix=true
innodb_file_format=barracuda
innodb_file_per_table=true

Then restart the maria db service.

Read More



MySQL error 1819 HY000


This article will guide you on how to resolve MySQL error 1819 (HY000) which happens when creating a MySQL user with a relatively weak password.  

Because of validate_password_policy we applied on database, we are not able to change and assign simple or weak passwords it don't allow to to change password and came up with error.

To resolve this error, We can check validate_password_policy applied on machine. Also you can change your password under Low policy.


Solution to MySQL Error Your Password does not satisfy the Current Policy Requirements:

1. Set the Password_policy value to low, next is setting the same Password_Policy value in my.cnf file and the last is uninstalling the plugin that is used for validating password.

2. Set the Password_Policy to low:

Default Password level of plugin can be changed at runtime or using config file. 

To do this, default authentication plugin has to be checked:

SHOW VARIABLES LIKE 'default authentication plugin';

3. For checking the current variables for validating the password you should run the following command:

SHOW VARIABLES LIKE 'validate_password%';

4. Validate_password is a variable that is used to inform the server about the validate_password plugin. 

This plugin tests the passwords and improve security. 

Following output will be displayed, if you run the above command:

mysql> SHOW VARIABLES LIKE 'validate_password%';

Read More



MySQL error log cPanel


This article will guide you on more information about MySQL error logs and methods to resolve its errors. 

You will learn how to fix MySQL errors, crashes and other unexpected behavior from #MySQL. 

To view mysql error logs:

1. edit /etc/my.cnf [mysqld] log=/tmp/mysql.log.

2. restart the computer or the mysqld service service mysqld restart.

3. open phpmyadmin/any application that uses mysql/mysql console and run a query.

4. cat /tmp/mysql.log ( you should see the query ).

To Clear cPanel Error Log:

1. Login to your server using an #SSH client.

2. To clear the #Apache #errors, type the following and press Enter. cat /dev/null> /usr/local/apache/logs/error_log.

3. To delete PHP error_log files, type the following and press Enter. find /home -type f -name error_log -delete.

Read More



MySQL is not running


This article will guide you on methods to resolve MySQL #error 'MySQL is not running'. Basically, this MySQL error occurs due to many reasons that include stopping MySQL improperly, tables crashing and so on. 

Both MySQL and #Microsoft SQL Server (MSSQL) are widely used enterprise database systems. MySQL is an open-source relational #database management system (RDBMS), while MSSQL Server is a Microsoft-developed RDBMS. 

Enterprises can choose between multiple #MSSQL Server editions to suit their individual needs and budgets.

Why #MySQL is not opening?

1. You can also check the MySQL service is running in background or not. 

2. To do that open Task manager ( Press CTRL + SHIFT + ESC simultaneously ) and look for mysqld service in background process section. 

3. If it isn't listed there then the service is stopped or disabled.

Read More



cPanel MySQL error query PHP


This article will guide you on methods to fix cPanel MySQL #error query #PHP. Generally, the MySQL error query PHP is mainly related to the PHP file. This can be either caused due to incorrect database details in the PHP file or incorrect permissions or incorrect ownership in files. 

To fix this issue:

1. Update to the latest version of #MySQL to resolve the issue. 

For some, this may require removing yum version locks on the MariaDB packages.

If packages are locked for #MariaDB clear the lock with the below command:

yum versionlock clear

Otherwise, proceed with the updates for MariaDB:

yum upgrade MariaDB-*

Read More



SQL error 825 How to fix it


This article will guide you on methods to resolve SQL error 825 which indicates a major disk problem and not a SQL server problem. 

The connection to #SQL server cannot be established or is no longer usable. There can be various causes of this #error. The most common causes are that Microsoft Dynamics NAV Server has stopped or the connection to SQL #Server is not configured correctly.

To find SQL errors:

i. In SQL Server Management Studio, select Object Explorer.

ii. In Object Explorer, connect to an instance of SQL Server, and then expand that instance.

iii. Find and expand the Management section (assuming you have permissions to see it).

iv. Right-click SQL Server Logs, select View, and then choose SQL Server Log.


Every SQL Server #database has a transaction log that records all transactions and the database modifications made by each transaction. The transaction log is a critical component of the database. If there is a system failure, you will need that log to bring your database back to a consistent state.

To get SQL query history in SQL Server:

1. In Object Explorer, connect to an instance of the SQL Server Database Engine, and then expand that instance.

2. Expand SQL Server Agent, and then expand Jobs.

3. Right-click a job, and then click View History.

4. In the Log File Viewer, view the job history.

5. To update the job history, click Refresh.

Read More



Could not allocate space for object sql server error


This article will guide you on how to fix #SQl #error "Could not allocate space for object" which occurs due to insufficient space in the database. 

SQL SERVER – Msg 1105 – Could Not Allocate Space for #Object Name in Database ‘DB’ Because the ‘PRIMARY’ Filegroup is Full.

Whenever you get such error check below:

1. Check if auto growth is restricted.

2. Check if auto growth is set to a high value which would cause disk space to become full.

3. Check if disk space is low.

4. Check SQL edition because SQL #Express has a database file size limit.

Here is the command to set the growth to UNLIMITED:

[sq]USE [master] GO

ALTER DATABASE


[SQLAuthDB] MODIFY FILE (NAME = N’SQLAuthDB’, MAXSIZE = UNLIMITED)

GO[/sql]

Read More



SQL server error 1326 Steps to fix it


This article will guide you on methods to resolve SQL server error 1326 which occurs due to the IIS Service not having any rights to use the named pipe.

If the SQL server resides on a separate server from IIS, then the IUSR_machinename account needs to be validated on the Windows NT server that SQL resides on.

#SQL #SERVER – Fix : Error : 1326 Cannot connect to #Database Server Error: 40 – Could not open a connection to SQL Server.

Now if SQL Server can be connected perfectly from #local system, but cannot be connected from a remote system, in that case firewall on the server where SQL Server is installed can be issued.

Follow instructions below to fix the issue:

1. Go to control panel >> #Firewall Settings >> Add SQL Server’s Port to Exception List.

2. Now try to connect to SQL Server again. It will allow you to connect to the server successfully.

Read More



Microsoft SQL server error 18470 How to fix it


This article will guide you on the different factors that causes SQL server error: 18470 and also how to fix this #error.

In SQL Server Configuration Manager, in the left pane, click SQL Server Services. In the results pane, right-click SQL Server (#MSSQLServer) or a named instance, and then click Start, Stop, Pause, Resume, or Restart.

User gets the #Microsoft SQL Server Error: 18470. This may happen if the SA (System Administrator) user account is disabled in #SQL Server. It can be verified by trying to log in to SQL Server Management Studio (#SSMS) using the SA account. In the Login Properties screen, select Status on the left side.

To Microsoft SQL Server Error 18456:

1. Log In with Remote Desktop.

2. Run Microsoft SQL Server Management.

3. Checking the Server Authentication Mode.

4. Restart the SQL Service.

5. Checking SQL User Permissions.

6. Mapping the User to the #Database.

Read More



SQLSTATE42000 syntax error or access violation


This article will guide you on methods to resolve 'sqlstate42000 #syntax error or access violation' which occurs due to wrong syntax entry or extra space or no space in the user's #SQL #query. 

The #1064 error displays any time you have an issue with your SQL syntax, and is often due to using reserved words, missing data in the database, or mistyped/obsolete commands.

As you can see there is more than one cause for the 1064 error within MySQL code. Now, you know how to correct the issues with your SQL Syntax, so your query can run successfully. This list will be updated as more specific instances are reported.

Read More



SQL server Error 1053


This article will guide you on different methods of fixing error #1053 SQL server which occurs when attempting to pause or stop the SQL Server service in the #Windows Services Console. 

The most common cause of this error is when one of the files needed by sql server was not on a shared resource, and Sql Server, once failed to the other node, couldn't access it.

The #SQL #Server Agent error log may include a path or a file name that is not correct.

In this case, verify that the path and file name for SQLAgent.out is valid:

1. In SQL Server Enterprise Manager, expand the Management folder.

2. Right-click SQL Server Agent, and then click Properties.

3. Under Error Log, make sure that the path that is specified next to File Name is valid.

4. Make sure that the file name is SQLAGENT.out.

Read More



Restrict anonymous login and ban IP address of attacker Windows


This article will guide you on the steps to Restrict anonymous login and ban #IP address of attacker by using Local Group Policy Editor in #Windows which allows us to prevent anonymous login and #IPBan helps to ban IP of #attacker. 

Read More



SQL server error 17 Steps to fix it


This article will guide you on the steps to fix 'SQL Server does not exist or access denied' error which occurs when the computer running #Microsoft #SQL Server is not reachable.

Read More



Microsoft SQL Server Error 701


This article will guide you on the steps to resolve #SQL Server #Memory pressure or insufficient #memory issue which can happen due to huge data load or other memory-intensive #operations that lead to a 701 #error in the SQL server.

Read More



SQL Server error 14265 How to fix


This article will guide you on the steps to fix SQL Server #error 14265 which occurs when the #SQL Server #Agent service auto restarts the SQL #Server.

Read More



SQL server error 1101


This article will guide on the steps to resolve #SQL SERVER ERROR "1101 : Could not allocate a new page for database because of insufficient #disk space in filegroup".

You can make sure there is enough Hard Disk space where #database files are stored on #server and Turn on AUTOGROW for file #groups.

Read More



SQL error 15123


This article will guide you on the steps to troubleshoot and fix #SQL server #error #15123 which occurs in the process of changing or viewing the values of any advanced server configuration option.

Read More



Using Ansible to copy MySQL databases


This article will guide us on how to perform database migration using Ansible as the controller which can help to copy a MySQL database from one remote server to another.

Read More



Xampp MySQL shutdown unexpectedly error


This tutorial will help to fix MySQL shutdown unexpectedly which occurs as a result of server-side errors such as missing configuration, corrupted file, port changes, and improper shutdown.

Read More



Page Splits in SQL Server


This article will guide you on how to prevent page splits which can cause performance issues.

Read More



Steps to fix SQL Error 1069 the service did not start due to a logon failure


This article will guide you on how to fix SQL error 1069 arises when SQL Server service fails to start while restarting Microsoft SQL Server or SQL Server Agent.

Read More



SQL error Msg 5144 SQL error Msg 5145


This article will guide you on how to solve SQL error Msg 5144, SQL error Msg 5145 which happens in the process of extending the data or transaction log files or during autogrowth operation for data or log files.

Read More



SQL error 17058


This article will help you to solve SQL error 17058 which occurs due to various reasons that include insufficient privileges, corrupted log files, the issue with network policies, and permission issues.

Read More



SQL error Msg 4341


This guide will help you to fix SQL error Msg 4341 which can occurs during a database recovering process to a point in time. 

Read More



An error occurred for a dependency of the feature causing the setup process for the feature to fail


This article will guide you on what to do to solve the error "An error occurred for a dependency of the feature causing the setup process for the feature to fail." in the process of installing the SQL server 2019 from a mounted ISO file.

Read More



SQL error Msg 3266


This article will help you to solve SQL error Msg 3266 which occurs when database backups job fails when the filemark in the backup device cannot be read. 

Read More



How to fix Microsoft SSMS activity monitor paused state error


SSMS activity monitor paused state error occurs when trying to access Activity Monitor in SQL Server Management Studio.

Read More



How to fix SQL Error 823


SQL Server error 823 results when there are hardware related issues with the SQL server such as disk errors power failures, or system problems.

Read More



How to fix SQL Server Error 824


SQL Server Error 824  is a logical Input/Output (I/O) error which affects database and makes it to be damaged or corrupted.

Read More



Solve microsoft SQL server error 15173


Microsoft SQL Server Error 15173 occurs when a login fails to drop from a SQL server instance.

Read More



Solve SQL Server error 15170


Method to fix SQL Server error 15170 via T-SQL command or SSMS.

Read More



Solve SQL error Msg 11730


Best way to fix SQL Msg 11730 error.

Read More



Solve SQL Server event id 833


Best method to fix SQL server error 833 and optimizing database performance.

Read More



Solve SQL Error 3101


Steps taken to solve SQL Error 3101.

Read More



Solve SQL server error 7416


Most sql users discover that the logins which they used before suddenly develops server error 7416.

Read More



Fix Microsoft SQL Server Error 14258


SQL Server error 14258 triggers when a job is trying to run in the affected SQL instance.

Read More



Fix MySQL error code 1054


MySQL error code 1054 occurs when you forget to add single quotes while inserting a varchar value or due to any missing column.

Errors in the database of a website can be very frustrating especially if you have got a high traffic website and it leads to loss of customers and money as your they will turn away from your site since this type of errors affects the whole website in general.

Read More



Easy fix to SQL error 5023


From time to time, we do receive SQL related server bugs queries of which one of it was "SQL error 5023".

This SQL error is very catastrophic and it tends to disrupt the SQL server when it is trying to start up.


To fix SQL Server Error 1225:

1. Click WindowsKey + R and enter services. msc.

2. Once Services opens scroll down and locate service SQL Server.

3. Highlight the service and click START.

4. Wait for the service to start and retry to connect to your MSSQL instance.

Read More




For Linux Tutorials

We create Linux HowTos and Tutorials for Sys Admins. Visit us on LinuxAPT.com

Also for Tech related tips, Visit forum.outsourcepath.com or General Technical tips on www.outsourcepath.com






Focus on your business, not your servers.

Click Here to Learn More