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.

Network Packet Size Server Configuration

Network Packets are the fixed-size chunks of data that transfer requests and results between clients and servers. The default value of network packet size is 4096 bytes which is 4KB. Microsoft suggests to not change this value until it is required or it will improve any performance because SQL Server performs best with default network packet size. There is a limitation for encrypted connection that the network packet size can not be more than 16,383 bytes.

Change Existing Network Packet Size using T-SQL

Let’s check the current value of this option on SQL Server Instance. Run below command to see the details. If you are getting Error 15123: This Configuration Option does not exist then you should first read attached article to fix this issue and then proceed with the solution given in this article.

EXEC sp_configure 'show advanced options', 1;
GO
RECONFIGURE ;
GO
EXEC sp_configure 'network packet size'

You can see the current config value is set to 4096 that means SQL Server will use network packet size of 4KB to send out data over the network. We can set minimum value to 512 byte and maximum value to 32767 byte.

If you want to change this value from 4KB to 8KB or any other user value, you can do that by running below T-SQL statement. Microsoft suggest to not change the default value although if you are facing any network related performance issue you can change this value as per your requirement. Make sure to do proper testing in lower life cycle before applying this change in to productions.

EXEC sp_configure 'show advanced options', 1;
GO
RECONFIGURE ;
GO
EXEC sp_configure 'network packet size', 8192 ;
GO
RECONFIGURE;
GO

See the below screenshot in which we have changed the value from 4KB to 8KB.

Changing Network Packet Size using GUI

We can check or change network packet size value using GUI as well. Let’s make this change using GUI so that you will be aware of both methods. I have already discussed T-SQL method in above section.

Connect to SQL Server Instance in SQL Server Management Studio (SSMS). Right click on SQL Server Instance in SSMS and choose properties. Server Properties window will appear to make server level changes. Click on “Advanced” tab from left side pane. You can see the value for network packet size is 8192 which we set in above steps.

Now revert this value to 4096 to its default value. Enter the value and hit the ok button to apply this change. This change will be in immediate effect and does not required any reboot or restart.

You can validate the changes by running sp_configure command or by using GUI method.

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

Read More:

• Fix Error 15123: This Configuration option does not exist
• How to Set or Limit number of User Connections in SQL Server?
• Assign SQL Server MIN and MAX Memory at Server Level
• Fix SQL Server Error 14258: Cannot Perform this Operation while SQL Server Agent is Starting.

The post How to Change Network Packet Size in SQL Server? appeared first on Techyaz.com.

User Connections Server Configuration

This option user connections is a dynamic (self-configuring) option, SQL Server adjusts the maximum number of user connections automatically as needed, up to the maximum value allowable. SQL Server allows a maximum of 32767 user connections. The default value of this option is 0 that means SQL Server can use maximum number of allowed connections which is 32767.

Best way to use this option to avoid the overloading the server with too many concurrent connections. Ideally we should not set this value too high because each connection will put some load to the server whether it will be using or not. If all defined number of connections are in use or connected, you receive SQL Server error 233 and will not be able to connect until another connection becomes available. Here is the description of above error.

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).

If you will look into SQL Server error log, you will find below error message for the same issue.

Could not connect because the maximum number of 'XX' user connections has already been reached.
The system administrator can use sp_configure to increase the maximum value. The connection has been closed. [CLIENT: XX.XX.XX.XX]

I will explain about how to fix SQL Server error 233 in below section of this article.

Set User Connections Server Configuration using T-SQL

Let’s check the current value of this option on SQL Server Instance. Run below command to see the details.

EXEC sp_configure 'show advanced options', 1;
GO
RECONFIGURE ;
GO
EXEC sp_configure 'user connections'

You can see the current config value is set to 0 that means this instance is set for maximum allowed connections. Also we can see the maximum allowed connections are shown 32767.

Now you can set the value as per your need. I have set the value of user connection to 1000 to limit its number of concurrent connections. Run below command to get this done.

EXEC sp_configure 'show advanced options', 1;
GO
RECONFIGURE ;
GO
EXEC sp_configure 'user connections', 1000 ;
GO
RECONFIGURE;
GO

See the below screenshot which has changed the value from 0 to 1000.

Check the value again by running same command which we have executed in first screenshot to validate this change. You can see config value is now showing as 1000.

Note: You must restart the SQL Server machine to apply this change to take effect.

Fix SQL Server Error 233 No process is on the other end of the pipe

If all configured number of connections are in use or connected, you will receive below error message and will not be able to connect until another connection becomes available.

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).

If you will look into SQL Server error log, you will find below error message for the same issue.

Could not connect because the maximum number of 'XX' user connections has already been reached.
The system administrator can use sp_configure to increase the maximum value. The connection has been closed. [CLIENT: XX.XX.XX.XX]

We can fix SQL Server Error 233 using below three options.

• Set the user connections option to 0 to enable maximum number of allowed connection.
• Increase the value of user connections so that SQL Server can accept the new connections.
• You can also close your existing connections so that new connections can be accepted by SQL Server. But this is not a permanent solution.

This time let’s make this change using GUI so that you will be aware of both methods. I have already discussed T-SQL method in above section.

Connect to SQL Server Instance in SQL Server Management Studio (SSMS). Right click on SQL Server Instance in SSMS and choose properties. Server Properties window will appear to make server level changes. Click on “Connections” tab from left side pane. You can see below screen. You can see the value is 1000 in right side pane which we set in above steps.

Now revert this value to 0 to accept maximum number of allowed connection. We can also fix error 233 which you might get if maximum number of connections will be exceeded.

Now again you can validate the changes by running same command. You will see value of user connections will be showing as 0 now, that means you will not face any issue related to error 233 anymore. Restart the server to apply this change into effect.

If you are still facing SQL Server error 233 then I would recommend you to read below article. I have described another aspect for Error 233 in below article.

• Fix Error 233: No process in on the other end of the pipe

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

Read More:

• SQL Server Error 15123: The Configuration Option does not exist
• How to change Network Packet size in SQL Server?
• Change Database Default Locations in SQL Server
• SQL Server DBA Interview Questions & Answers

The post SQL Server Error 233: User Connections Server Configuration option in SQL Server appeared first on Techyaz.com.