HQ Client Sync Error on 250/260 Sheet

We are creating a rather large worksheet 250/260(> 33,000 items). It works fine on one of our stores (running SQL 2000 SP4 same location as HQ) without any issues. When we run the worksheets for the other store (SQL 2005 Express), it runs for an indetminiate time (about an hour) and fails. The worksheets run if we break the number down to less than 5000 items. We adjusted the time on the HQ Client in the registry as recommended. We are now recieving a new error message related to this syncronization.

Here's the error message in the HQ Client Log: Download Items-Stag

4/20/2007 12:06:40 PM Ref. No.: 52743 4/20/2007 12:07:02 PM Updated 3 record(s) in table 'QuantityDiscount'. 4/20/2007 12:07:03 PM Updated 3 record(s) in table 'ItemClass'. 4/20/2007 12:17:31 PM Error -2147467259: [DBNETLIB][ConnectionRead (recv()).]General network error. Check your network documentation. SELECT #Temp.* INTO #TempInsert FROM #Temp LEFT JOIN Item ON (#Temp.HQID = Item.HQID) OR (Item.HQID=0

4/20/2007 12:17:34 PM Error -2147467259: Connection failure SELECT * FROM [#TempInsert]

4/20/2007 12:17:34 PM An error occurred while attempting to Update Inventory Structure. 4/20/2007 12:17:34 PM An error occurred while attempting to Update Inventory Structure. 4/20/2007 12:17:34 PM Not completed due to errors encountered during processing.

After clicking OK on the error message the client gets into a loop with the following error repeating itself:

4/20/2007 12:17:36 PM Error 3246: Connection object cannot be explicitly closed while in a transaction. (Unhandled Error, state = '9') 4/20/2007 12:17:36 PM An error was detected, connection will be aborted.
Reply to
Floppy Cow
Loading thread data ...

Anyone have anything more to share. We are seeming to have network issues:

"Fl> We are creating a rather large worksheet 250/260(> 33,000 items). It works

Reply to
John M

Anyone have anything more to share. We are seeming to have network issues:

"Floppy Cow" wrote:

Reply to
CptSoft

BeanSmart website is not affiliated with any of the manufacturers or service providers discussed here. All logos and trade names are the property of their respective owners.