It will not allow us to create an inventory item (actually will not let us set up any type of item) then shuts down

  • 1
  • Problem
  • Updated 4 years ago
  • Solved
  • (Edited)
It will not allow us to create an inventory item (actually
will not let us set up any type of item)



When I try to create it, the message attached appears and then shuts down quickbooks.

 

Version & Year:                 Quickbooks Premier Edition 2011-2012

Error that appears:           Refer to attachment

Photo of Ron

Ron

  • 142 Points 100 badge 2x thumb

Posted 4 years ago

  • 1
Photo of Andrew

Andrew

  • 22,222 Points 20k badge 2x thumb
Well thats a bit nasty..... Have you checked your data file is valid? A rebuild/verify of the datafile would be my first step to try!

Check out this page for details on how to

https://community.reckon.com/reckon/t...
Photo of Ron

Ron

  • 142 Points 100 badge 2x thumb
We have already done the rebuild/verify of the datafile? Still have the same problem
Photo of Andrew

Andrew

  • 22,222 Points 20k badge 2x thumb
bugger... How many items do you have? not at the ~15k limit for items/lists/customers etc

Open Reckon Accounts aka QuickBooks company file by pressing the F2 key and looking at File Size in the File Information section of the window or List Information section

Otherwise I'm out of ideas and its going to be a Reckon support request.
(Edited)
Photo of Ron

Ron

  • 142 Points 100 badge 2x thumb
we have approx 1000 total accounts, 2600 names, 3876 items.
If we add up all the numbers in the list information box there is approx 12800.
I don't thing we have exceeded the 15k limit
Photo of Ron

Ron

  • 142 Points 100 badge 2x thumb
We also just created a new customer and this works fine
Photo of Andrew

Andrew

  • 22,222 Points 20k badge 2x thumb
Bummer.... I assume you have done the normal things like close everything down and reboot the computer to see if that fixes it?

If so, then sorry, out of ideas :( Over to reckon support!
Photo of Reckon FAQs

Reckon FAQs, Employee

  • 10,138 Points 10k badge 2x thumb
Hi Ron,

Sorry to hear your problem is persisting.

The sort of crash you are getting is often associated with a corruption with one of the elements associated with the function your are doing.

Suggest you Rebuild and Verify again and then examine the QBwin.log file that is updated after every rebuild and verify and look for specific errors identified, and address them.  For help with any problem you find, check the Knowledgebase with the keywords in the error entry.

You can get to QBwin.log by clicking Ctrl+1 > Ctrl+2 > Open file >.....

Hope this helps you.


regards,
John
(Edited)
Photo of Ron

Ron

  • 142 Points 100 badge 2x thumb
thank will give it a go
Photo of Ron

Ron

  • 142 Points 100 badge 2x thumb
Hi John,

Thanks for your help. 
I have attempted to use the knowlegebase and have added a few difference errors from the report below and have only had this response - No issues were found for the selected category.
Photo of Ron

Ron

  • 142 Points 100 badge 2x thumb
Hi jJohn,

I have copied the QBwin.log error report, shown below.
Can let me know which parts of the info below I should be using in the Kowledgebase

QBWINDLL.c (255) :  MESSAGE: Fri Aug 14 12:31:35 LVL_ERROR--Returning NULL QBWinInstance HandleQBWINDLL.c (255) :  MESSAGE: Fri Aug 14 12:31:35 LVL_ERROR--Returning NULL QBWinInstance Handle
QBWINDLL.c (115) :  CHECKPOINT: Fri Aug 14 12:31:35 CQBWinApp::InitInstance -- Initializing QBWinInstance Handle
QBWINDLL.c (145) :  CHECKPOINT: Fri Aug 14 12:31:35 CQBWinApp::InitInstance completed
QBW.c (221) :  CHECKPOINT: Fri Aug 14 12:31:35 CQuickBooksApp::InitInstance Initializing Quickbooks (AfxOLE)
QBW.c (225) :  CHECKPOINT: Fri Aug 14 12:31:35 Operations Started
QBW.c (443) :  CHECKPOINT: Fri Aug 14 12:31:35 Calling MauiMain for further initialization
QBW.c (450) :  CHECKPOINT: Fri Aug 14 12:31:36 MauiMain finished successfully
QBW.c (632) :  CHECKPOINT: Fri Aug 14 12:31:36 Initializing Add-Ins
QBW.c (471) :  CHECKPOINT: Fri Aug 14 12:31:36 Initializing COM-dependent components
QBW.c (498) :  CHECKPOINT: Fri Aug 14 12:31:36 CQuickBooksApp::InitInstance exiting
QBW.c (568) :  CHECKPOINT: Fri Aug 14 12:31:36 QuickBooksApp::Run
formwin.c (2520) :  CHECKPOINT: Fri Aug 14 12:31:36 Creating form: formID=6050, itID=0
cwelcomedialog.cpp (450) :  CHECKPOINT: Fri Aug 14 12:31:38 WelcomeDialog: OpenExisting
formwin.c (2520) :  CHECKPOINT: Fri Aug 14 12:31:38 Creating form: formID=101, itID=1
formmgr.c (604) :  CHECKPOINT: Fri Aug 14 12:31:38 Creating a MODAL form: formID=101, itID=0
load.c (1581) :  CHECKPOINT: Fri Aug 14 12:31:39 OpenSystemWithName on \\srfp\DATA\Quickbooks\
load.c (2005) :  CHECKPOINT: Fri Aug 14 12:31:43 InitSystem
load.c (10009) :  CHECKPOINT: Fri Aug 14 12:31:44 Won't be using database server on local machine - no hosting change needed.
load.c (2138) :  CHECKPOINT: Fri Aug 14 12:31:44 InitSystem Check file location and move
load.c (2207) :  CHECKPOINT: Fri Aug 14 12:31:45 InitSystem Open DB Session[4]
formwin.c (2520) :  CHECKPOINT: Fri Aug 14 12:31:48 Creating form: formID=15920, itID=2
formmgr.c (604) :  CHECKPOINT: Fri Aug 14 12:31:48 Creating a MODAL form: formID=15920, itID=1
load.c (8469) :  CHECKPOINT: Fri Aug 14 12:32:00 Max users was set from SKU publisher and the value is = 5
DBManager.cpp (3375) :  CHECKPOINT: Fri Aug 14 12:32:00 Current Database Server version = 9.0.2.3267
FileMgr.cpp (274) :  CHECKPOINT: Fri Aug 14 12:32:00 Company file \\srfp\DATA\Quickbooks\Searay.QBW is open using database server:QB_SRFP_20.
load.c (2214) :  CHECKPOINT: Fri Aug 14 12:32:00 InitSystem Open DB Session[4] Succeeded
QBPRINT.c (2522) :  CHECKPOINT: Fri Aug 14 12:32:00 Detecting if Terminal Service is running.
PermissionManager.cpp (4294) :  CHECKPOINT: Fri Aug 14 12:32:01 A new permission context is added for QuickBooks
load.c (3661) :  CHECKPOINT: Fri Aug 14 12:32:04 InitSystem: Open System
load.c (3669) :  CHECKPOINT: Fri Aug 14 12:32:04 InitSystem: Open System succeeded
load.c (4014) :  CHECKPOINT: Fri Aug 14 12:32:05 InitSystem: successful completion
load.c (1738) :  CHECKPOINT: Fri Aug 14 12:32:05 InitSystem succeeded
GBTErrorLogger.cpp (54) :  MESSAGE: Fri Aug 14 12:32:05 LVL_ERROR--COM Error while pinging GDS:
GBTErrorLogger.cpp (54) :  MESSAGE: Fri Aug 14 12:32:05 LVL_ERROR--COM Error while pinging GDS:
load.c (1768) :  CHECKPOINT: Fri Aug 14 12:32:05 OpenSystemWithName completed. File Opened? NO
oaerror.c (110) :  CHECKPOINT: Fri Aug 14 12:32:05 OAstdMethodRet (80040600)
oaerror.c (110) :  CHECKPOINT: Fri Aug 14 12:32:05 OAstdMethodRet (80040600)
popup.c (430) :  CHECKPOINT: Fri Aug 14 12:32:25 Creating CreatePopUpList: resID=15030, itID=0
popup.c (430) :  CHECKPOINT: Fri Aug 14 12:32:33 Creating CreatePopUpList: resID=15005, itID=1
formwin.c (2520) :  CHECKPOINT: Fri Aug 14 12:32:37 Creating form: formID=900, itID=3
Photo of John G

John G, Information Support Analyst

  • 27,510 Points 20k badge 2x thumb
Thanks Ron,

The entries here are the normal entries recorded in the QBwin.log file at the launch of Quickbooks.  Was this all that was in the file?  These files end up being very long so scroll down to the bottom where you will see entries for Begin Rebuild Log and Begin Verify Log.  Here's the result on my test file:



The red box shows an error found that was found and it was fixed so at the end of the Verify I got the message no errors found.  

Sometimes the Rebuild cannot fix the error found so the Verify will return the message an error was found and suggests you Rebuild.  But another rebuild does not fix it.  Examining the QBwin.log file will give you details of the corrupt transaction and what is wrong with it.  You will need to fix it manually, usually by refreshing the transaction by making a change to the document (as little as adding a full stop into the message box) and saving again.  If that does not fix it you will need to delete it and reinput it.  If the transaction involves an entry to a bank account you may need to redo the reconciliation.

The KB's do have guides for QBwin errors.  I just searched for QBwin and go the following list:




A good guide to manually correcting an error is available in the KB: C=44 error during the upgrade process of my QuickBooks file.  (the QBwin.log file referred to in this guide is an old one - a description of the new one is available at Rebuilding a data file in QuickBooks (also in KB336)).

So in summary what you should do now is:
  1. Backup your company file (don't follow any directions to verify or rebuild yet)
  2. Close and reopen your QuickBooks
  3. Follow the guides to Resort all your Lists
  4. Rebuild (don't overwrite any existing backups) and then Verify
  5. If errors found, examine the QBwin.log file to identify the errors
  6. Search the KBs for guides on your errors, and where indicated refresh or delete and re-enter your corrupt transactions
  7. When done verify your file again and if errors still found repeat these procedures.  

Hope this gets you going again.


regards,
John
(Edited)
Photo of Ron

Ron

  • 142 Points 100 badge 2x thumb
thanks John.  This has fixed our problem. we resaved the last purchase order that we processed and now we can create new items.  Thanks again muchly appreciated.
Photo of Reckon FAQs

Reckon FAQs, Employee

  • 10,138 Points 10k badge 2x thumb
Glad to hear your up and running again, Ron.

regards,
John

This conversation is no longer open for comments or replies.