Posts Tagged ‘SQL Error’

SQL Python Error – ‘sp_execute_external_script’ is disabled on this instance of SQL Server. Use sp_configure ‘external scripts enabled’ to enable it.

August 29, 2018 Leave a comment

You are running a Python script by using sp_execute_external_script SP but its throwing this error:

Msg 39023, Level 16, State 1, Procedure sp_execute_external_script, Line 1 [Batch Start Line 27]
‘sp_execute_external_script’ is disabled on this instance of SQL Server. Use sp_configure ‘external scripts enabled’ to enable it.


You can refer to my blog post on setting up ML with Python with SQL Server, link:

This fix will also work with R support with SQL Server.



SQL Error – SHOWPLAN permission denied in database

August 10, 2016 Leave a comment


So, you are working on a SQL Query Performance issue in your Production environment, but you just have read access and can just execute SELECT statements to check the data.

But when you try to check what execution plan that query is creating/using you are getting blocked as you don’t have sufficient privileges for the same, and getting this error:

Msg 262, Level 14, State 4, Line 283
SHOWPLAN permission denied in database ‘AdventureWorks2014’.


For checking Execution plans you don’t need to have admin privileges, just granting access on SHOWPLAN setting will work for you.

So, you can your DBA to grant you access by using below query:

USE AdventureWorks2014

GRANT SHOWPLAN TO user_name -- replace user_name here

Categories: SQL Errors Tags: , ,

SQL Error – Unable to generate a temporary class (result=1), error CVT1108, error CS1583

August 14, 2015 1 comment

Few days back I got an email from one of this blog reader mentioning that he was facing issues while Installing SQL Server, and was getting following error:

SQL Server Setup has encountered the following error:

Unable to generate a temporary class (result=1).
error CVT1108: cannot open C:\Users\DELL\AppData\Local\Temp\RESAC3F.tmp for writing
error CS1583: ‘c:\Users\DELL\AppData\Local\Temp\CSCAC2F.tmp’ is not a valid Win32 resource file´╗┐


By the above error its evident that the user does not have sufficient rights to the Temporary location mentioned above “C:\Users\DELL\AppData\Local\Temp”.

As the SQL Server installer EXE is trying to extract the compressed files to this Temp location before actually installing SQL Server on your machine. But it looks like due to some reason the use account does not have access to this location, thus throwing error mentioned above.

–> Now the resolution for this is to, either:

1. Re-extract the contents to an another drive where you have full permission.

– or –

2. To set proper rights for the User on the Temp location. Go to the above Temp location and Right-click on the Temp folder, and select Properties, go to Securities tab. Under the “Groups or user names:” section just check if your user name is there. Select the user name and make sure it should have “Full Control” selected under the “Permissions for Administrators”. If it’s not then click on the Edit button and provide Full rights to the user account.

SQL Error – Index (zero based) must be greater than or equal to zero and less than the size of argument list

January 11, 2015 Leave a comment

SQL Server version is “SQL Server 2012(SP2-CU15-GDR)(KB3194725) – 11.0.5676.0(X64)”.
An error occurred when you applied SQL Server 2012 Service Pack 3 to the current server(see attached image)

–> Summary Log

Overall summary:
Final result: The patch installer has failed to update the shared features. To determine the reason for failure, review the log files.
Exit code (Decimal): -2068774911
Exit facility code: 1201
Exit error code: 1
Exit message: Index (zero based) must be greater than or equal to zero and less than the size of the argument list.
Start time: 2018-02-22 10:40:52
End time: 2018-02-22 10:41:22
Requested action: Patch



There can be various reasons you might be getting this issue, like a failure of a previous installation of SQL server may corrupt the registry, and this registry corruption may initiate this issue.

There seems to be no direct fix to this, so try:

– Uninstalling all the patches, and re-install them in sequence.

– Or, uninstall the whole SQL Server completely and install fresh again.

Categories: SQL Errors, SQL Server 2012 Tags: