Invalid Cursor State

girish.joshi
Member Posts: 407
Has anyone seen this error before :
The following ODBC error occrued:
Error: [Microsoft][ODBC SQL Server Driver]Invalid Cursor State State ID:24000
This error occured when trying to import objects on NAV 4.03 Update 6 running on SQL2K5
Thank you
The following ODBC error occrued:
Error: [Microsoft][ODBC SQL Server Driver]Invalid Cursor State State ID:24000
This error occured when trying to import objects on NAV 4.03 Update 6 running on SQL2K5
Thank you
0
Answers
-
I got this from msdn (State ID 2400 just means that its an invalid cursor state error)
* In SQL Server Enterprise Manager, you may receive the "Invalid cursor state" error message when Microsoft® SQL Server™ runs out of resources while attempting to save selected tables or a database diagram. This error is returned because of insufficient space in your database or transaction log to complete the save process. To correct this problem, check to see if whether the database or the transaction log is full. If so, increase the size of the database to accommodate the change. Check other system resources or contact your system administrator.0 -
So now you know what the error means, what did you do to solve the issue? Were the two problems you were having yesterday related to the same issue?0
-
[Topic moved from Navision forum to SQL General forum]Regards,Alain Krikilion
No PM,please use the forum. || May the <SOLVED>-attribute be in your title!0 -
it was related to replication.
the table was setup to be replicated.
Removed the replication, and it solved the problem0 -
we have the same problem.
but our customer don´t use replication.
SQL-Server 2005 64-Bit
32 GB Ram
MSSQL Version
MSSQL 2005 9.00.4035.00
Data Access Components 2000.086.3959.00
(SRV_SP2_RTM.070216-1-1710)
Navision Version
4.0.3.26954 (4.0 SP3 with Hotfix KB 954672)
thank you for every / any hints
BTW: the servers are clustered!0 -
any suggestion?
same problem on big batch job, (3'000'000 records to generate, hangs after 168'000) something with the size/full log could be correct but the SQL 2008 Database is in SIMPLE mode and with auto-increase size... Mybe the RAM? it runs on my computer- Dev environment (Win7 64 bits / SQL 2008R2 64 Bits / 4GB RAM).
Should I put some COMMIT (every 1000 records?) but if it hangs, where should I begin again ](*,) ?
Any idea is welcome!
Regards
Chris#### Only one can survive ######0 -
:shock: it's complicated... it looks like the IF INSERT THEN; condition to avoid the raising of primary key violation error has no good effects with the INIT command, so I had to put a IF NOT GET(myPK) THEN "do the code"
Old code:
table.init
table.PK := value1;
table.Field1 := value2;
if table.insert then;
New code:
if NOT table2.get(value1) then begin
table.init
table.PK := value1;
table.Field1 := value2;
if table.insert then;
end;
it works, my 3471530 records were imported! \:D/
thank you MS-support!#### Only one can survive ######0
Categories
- All Categories
- 73 General
- 73 Announcements
- 66.6K Microsoft Dynamics NAV
- 18.7K NAV Three Tier
- 38.4K NAV/Navision Classic Client
- 3.6K Navision Attain
- 2.4K Navision Financials
- 116 Navision DOS
- 851 Navision e-Commerce
- 1K NAV Tips & Tricks
- 772 NAV Dutch speaking only
- 617 NAV Courses, Exams & Certification
- 2K Microsoft Dynamics-Other
- 1.5K Dynamics AX
- 320 Dynamics CRM
- 111 Dynamics GP
- 10 Dynamics SL
- 1.5K Other
- 990 SQL General
- 383 SQL Performance
- 34 SQL Tips & Tricks
- 35 Design Patterns (General & Best Practices)
- 1 Architectural Patterns
- 10 Design Patterns
- 5 Implementation Patterns
- 53 3rd Party Products, Services & Events
- 1.6K General
- 1.1K General Chat
- 1.6K Website
- 83 Testing
- 1.2K Download section
- 23 How Tos section
- 252 Feedback
- 12 NAV TechDays 2013 Sessions
- 13 NAV TechDays 2012 Sessions