Tell me about the issue and I’ll help you find the solution you need.
FIX: "Invalid cursor position" error when you retrieve spatial data by using SQLSetPos in SQL Server 2014 or SQL Server 2012
Content provided by Microsoft
Applies to: Microsoft SQL Server 2014 Service Pack 1Microsoft SQL Server 2014 DeveloperMicrosoft SQL Server 2014 DeveloperMicrosoft SQL Server 2014 EnterpriseMicrosoft SQL Server 2014 EnterpriseMicrosoft SQL Server 2014 StandardMicrosoft SQL Server 2014 StandardMicrosoft SQL Server 2012 Service Pack 3Microsoft SQL Server 2012 DeveloperMicrosoft SQL Server 2012 EnterpriseMicrosoft SQL Server 2012 StandardMicrosoft SQL Server 2012 ExpressMicrosoft SQL Server 2014 DeveloperMicrosoft SQL Server 2014 DeveloperMicrosoft SQL Server 2014 EnterpriseMicrosoft SQL Server 2014 EnterpriseMicrosoft SQL Server 2014 StandardMicrosoft SQL Server 2014 StandardMore
When you use the SQLSetPos function call to run a common table expression (CTE) query to retrieve spatial data, the function call can't set the cursor position, and you receive an "Invalid cursor position" error message. This problem occurs in Microsoft SQL Server 2014 and Microsoft SQL Server 2012.
The issue was first fixed in the following cumulative update of SQL Server:
Each new cumulative update for SQL Server contains all the hotfixes and all the security fixes that were included with the previous cumulative update. We recommend that you download and install the latest cumulative updates for SQL Server:
Microsoft scanned this file for viruses by using the most current virus-detection software that was available on the date that the file was posted. The file is stored on security-enhanced servers that help prevent any unauthorized changes to it.
There are no prerequisites for installing this update.
To install this hotfix, you don't have to make any changes to the registry.
You may have to restart the computer after you install this hotfix.
Hotfix replacement information
This hotfix doesn't replace a previously released hotfix.
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
ERROR: at System.Diagnostics.Process.Kill()
at Microsoft.Support.SEOInfrastructureService.PhantomJS.PhantomJSRunner.WaitForExit(Process process, Int32 waitTime, StringBuilder dataBuilder, Boolean isTotalProcessTimeout)New URL: about:blank