April 26, 2015 at 8:58 pm
Hi all,
I'm in a pickle. I have 2 SQL server installs for 2008 R2 configured as multi instances.
I have a product called Esri ArcMap 10.3 that can be used to generate a database.
When I run the wizard against one installation, the wizard successfully creates the database. When I then run the same against the other installation it fails with the following error
[Microsoft][SQL Server Native Client 10.0]Invalid cursor state
I've attempted to look at the configuration of each using
select *
from master.sys.configurations
From this I found several differences
Successful Mulit instance
Optimize for Ad hoc Workloads – False
Max Degree of Parallelism - 0
UnSuccessful Multi instance
Optimize for Ad hoc Workloads – True
Max Degree of Parallelism - 4
I attempted to co-ordinate the differences running the wizard for each iteration but it always failed with the same error above. The error always seems to occur when a particular store procedure is run. There are quite a number of scripts run prior to this and are technically under the covers and only discovered via tracing, in this case using SQL Profiler. I don't have access to individual scripts that I can run incrementally to replicate the issue. I have to rely only on the Esri Wizard.
Reviewing the error against several forums suggests that this is an ODBC error but the trace I ran using SQL Profiler finds that the driver used is Native.
My question then is
"What are the conditions that would cause this error above (Invalid Cursor)?"
"Is there other configuration settings that are not captured via the SQL identified above?"
"Could this be caused by mapped drives for data, Logs and Temp?"
Any help would be greatly appreciated in diagnosing this particular error.
Cheers
Peter
April 27, 2015 at 3:17 am
It's most likely a data problem within the cursor itself. I'd focus on what that cursor is doing specifically within the code in order to understand where the problem might be coming from. I'm pretty sure it's not related, directly, to the disk or server settings. It might be related to them indirectly if the code within the cursor is assuming some state of the server that's not true.
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
April 27, 2015 at 7:52 pm
Hi Grant
Thanks for the feedback.
Will speak to Esri about the code being executed to get a better understanding of what's happening.
Cheers
Peter
Viewing 3 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply