How to fix Windows ODBC Drivers Error 80040e14

ODBC Drivers Error 80040e14 occurs when user wants to connect the existing MS access or existing database with ODBC (Open Database Connectivity) driver. The machine displays messages : [Microsoft][ODBC SQL Server Driver][SQL Server]Cursor open failed because the size of the keyset row exceeded maximum allowed row size. /storename/manager/product_edit.asp, line 27     OR

Microsoft OLE DB Provider for ODBC Drivers error ‘80040e14’
[Microsoft][ODBC SQL Server Driver][SQL Server]Cursor open failed because the size of the keyset row exceeded maximum allowed row size.
/storename/xt_orderform_additem.asp, line 39

The error causes size (length of different fields) problem. User should fix and solve ODBC Drivers Error 80040e14 with “Advanced System Repair tool” to spurn system crash.


{Compatible with Windows 8, 7, XP, ME, Vista, 98, 2000 (32/64)
File Size: 4.9MB Download Time: <(dsl, 2sec, dialup 2min)>}

Abrupt shut down or current window crash may occur with the error causes one of the impairment reasons – drivers support, bad registry, version problem having size limit, internet connection, firmware, malware, fated RAM installation. ODBC Drivers Error 80040e14 should be resolved with either automatic tool or manual solution.

Manual Solution:

Perform these steps to delete all records from the existing store tables:

  1. Edit the Schema.sql script in the %storeroot%\Config\SQL\SQLSvr directory. Schema.sql is a text file and can be edited in Notepad.
  2. Locate the section that looks similar to the following:

 

CREATE TABLE yourstorename_product(

sku VARCHAR(100) NOT NULL,

name VARCHAR(255) NULL,

description VARCHAR(255) NULL,

list_price INT NULL,

image_file VARCHAR(255) NULL,

image_width INT NULL,

image_height INT NULL,

sale_price INT NULL,

sale_start DATETIME NULL,

sale_end DATETIME NULL,

customattribute1 VARCHAR(255) NULL,

customattribute2 VARCHAR(255) NULL,

customattribute3 VARCHAR(255) NULL,

customattribute4 VARCHAR(255) NULL,

customattribute5 VARCHAR(255) NULL,

customattributeN VARCHAR(255) NULL,

PRIMARY KEY (sku)

) GO

  1. Specify the maximum row size for your version of SQL Server which shouldn’t be exceeded having 28 attributes, given below for (upto 7.0 enhancements):

CREATE TABLE yourstorename_product(

sku VARCHAR(100) NOT NULL,

name VARCHAR(255) NULL,

description VARCHAR(255) NULL,

list_price INT NULL,

image_file VARCHAR(255) NULL,

image_width INT NULL,

image_height INT NULL,

sale_price INT NULL,

sale_start DATETIME NULL,

sale_end DATETIME NULL,

customattribute1 VARCHAR(10) NULL,

customattribute2 VARCHAR(20) NULL,

customattribute3 VARCHAR(30) NULL,

customattribute4 VARCHAR(30) NULL,

customattribute5 VARCHAR(50) NULL,

customattributeN VARCHAR(100) NULL,

PRIMARY KEY (sku)

) GO

  1. Open ISQL_W and select the Commerce database that contains the yourstore_product table.
  2. Click File , and then select Open from the menu bar.
  3. Browse to the %storeroot%\Config\SQL\SQLSvr directory and open Schema.sql.
  4. Select Query , and then select Execute from the menu bar.
  5. When the Schema.sql script completes, the store will be configured properly.


{Compatible with Windows 8, 7, XP, ME, Vista, 98, 2000 (32/64)
File Size: 4.9MB Download Time: <(dsl, 2sec, dialup 2min)>}

Conclusive Decision:

If user is unable to reach on optimal solution point with the said manuals, a third party “Advanced System Repair tool” can fix and solve ODBC Drivers Error 80040e14. It overlaps the limitations of manual solution while providing – cache speed, defragmentation, free tech support for downloads and updates, repair of HDD bad sectors, firmware incompatibility removal, virus threats and spyware safety removal.


Leave a Reply