Intuit QuickBooks Pro 2001 for PC Logo

Question about Intuit QuickBooks Pro 2001 for PC

2 Answers

Error problems, program crashes...

One of my clients has a serious problem. The file and program literally crashes every time we try and enter Make Deposits! And error occurs on the log, one was C=51. Tried rebuild and verify, no luck. This is part of the error code and other data on the log: """V9.0U R1 (M=1115, L=4206, C=51, V=0 (0)) AND CI Lock attempt failed: 33 AND Error: Verify target 39991: Write count 23281 greater than file's write count 21654. ** Corrected **"""" Hope there will be a solution. Thank you

Posted by L.A. Buckle on

Ad

2 Answers

Anonymous

The data might be corrupt

Posted on Oct 16, 2007

Ad

Anonymous

  • Level 2:

    An expert who has achieved level 2 by getting 100 points

    MVP:

    An expert that got 5 achievements.

    Novelist:

    An expert who has written 50 answers of more than 400 characters.

    Champion:

    An expert who has answered 200 questions.

  • Expert
  • 202 Answers

How long has the problem been occuring? Were any updates to programs or new programs installed before the problem started. Is the virus protection software up to date. What operating system is QB 2001 being used? Let me know? Tim

Posted on Jan 29, 2007

Ad

Add Your Answer

×

Uploading: 0%

my-video-file.mp4

Complete. Click "Add" to insert your video. Add

×

Loading...
Loading...

Related Questions:

1helpful
1answer

None of the authentication methods supported by this client

For more information about repairing or configuring your Outlook email account, click the following link: https://www.pstrepairkit.com/
Regards
1helpful
6answers

Are Paul Gill and Masonolivia source of Indian spam? Why are their postings below copied from other spam?

When you register or open QuickBooks, you see one of these error messages:
  • Could not initialize license properties. Error 3371: QuickBooks could not load the license data. This may be caused by missing or damaged files.
  • Could not initialize license properties. [Error 3371, Status Code -11118] QuickBooks could not load the license data. This may be caused by missing or damaged files.
  • Could not initialize license properties. [Error: 3371, Status Code -1] QuickBooks could not load the license data. This may be caused by missing or damaged files.
Important: This issue can occur if your product is hosted by Right Networks and you access QuickBooks with WebConnect and then select to open the file without saving. If you use QuickBooks Enterprise and your product is hosted by Right Networks, you must save the file and then import it.

How to fix it:

Before proceeding, ensure that your copy of Microsoft Windows is up to date.
If the latest Windows updates are not installed, the QuickBooks installation can fail or become damaged. To install the latest updates in Windows, click the Windows Start or Logo button, choose All Programs > Windows Update. Once started be sure to install any updates marked critical.
You may need to re-install your software. Have your license number and product number for your version of QuickBooks ready.

Try these steps in the order shown. If the first one fixes the problem, you do not need to do the other steps.

Re-create damaged EntitlementDataStore.ecml
  1. Close QuickBooks if it's open.
  2. Open the entitlement data folder for your operating system and version of QuickBooks.
    1. On your keyboard, press Windows + R to open the Run window.
    2. Enter (or copy and paste) the following information, and then press Enter
      • QuickBooks 2014 and Enterprise 14.0: C:\ProgramData\Intuit\Entitlement Client\v8
      • QuickBooks 2013 and Enterprise 13.0: C:\ProgramData\Intuit\Entitlement Client\v8
      • QuickBooks 2012 and Enterprise 12.0: C:\ProgramData\Intuit\Entitlement Client\v6.0
      • QuickBooks 2011 and Enterprise 11.0: C:\ProgramData\Intuit\Entitlement Client\v6.0
      • QuickBooks 2010 and Enterprise 10.0 : C:\ProgramData\Intuit\Entitlement Client\v6.0
      • QuickBooks 2009 and Enterprise 9.0: C:\ProgramData\Intuit\Entitlement Client\v5
      • QuickBooks 2008 and Enterprise 8.0: C:\ProgramData\Intuit\Entitlement Client\v5
      • QuickBooks 2007 and Enterprise 7.0: C:\ProgramData\Intuit\Entitlement Client\v3
  3. Right-click the EntitlementDataStore.ecml file and select Delete.
  4. Click Yes to confirm you want to delete the file.
  5. Open QuickBooks, open your company file, and follow the instructions to register the application.


1helpful
1answer

Firefox crase every 15 minuts plz fix 4 us

Mozilla's Firefox Internet browser is one of the most popular browsers in the world, second only to Microsoft's Internet Explorer.

As of April 2011, Firefox held a 21.63 percent share of the worldwide browser market. Unfortunately, problems with plug-ins, websites and general operating system incompatibility occasionally cause Firefox to become unstable and crash.

To prevent these crashes from occurring again, the cause of the crash needs to be identified so an effective fix can be implemented.

Take note of the action or circumstance that lead to the crash.
Pay particular attention to the timing of the crash and whether it occurred while launching Firefox, when trying to view a specific website, when attempting to download a file or at a seemingly random time.


Repeat the action that caused the crash to see whether it causes Firefox to crash again. Some crashes are caused by memory problems or other external factors and may be a one-time occurrence.

Repeating the action determines whether the crash was caused by errors within Firefox or if there were other factors involved.

Hold the "Shift" key down on your keyboard and relaunch Firefox.
This will launch the application in "Safe Mode," disabling all plug-ins and themes.

Repeat the action that caused the crash; if the problem was caused by a plug-in or theme then the crash will not occur this time.

Open a new Firefox tab and type "about:crashes" without the quotation marks into the navigation bar.
Press "Enter" to load the Firefox crash log listing.

Select the most recent entry and scroll through it to find the name of the plug-in, theme or other component that caused the crash.

Disable or update the component to remove the cause of the crash.
This information should be contained in the "Details>Signature" or "Details>Crash Reason" sections.

Open the Tools menu in Firefox and select "Add-ons" if you cannot resolve the crash problem by disabling or updating a plug in.
Scroll through the list of installed browser add ons, disabling add ons one at a time in an attempt to correct the error.

If the crash occurs when trying to view certain types of content, such as streaming video or other media files, focus in disabling add-ons that are related to that type of content.

Open the Help menu and select the "Troubleshooting Information" option if crashes occur only when attempting to download files.

Locate the "Application Basics" entry, then click the "Open Containing Folder" link to open the folder containing your Firefox profile.

Exit Firefox, then select the "downloads.sqlite" file in your profile folder and delete it.
This removes your download history, eliminating any problems with the file and allowing Firefox to create a new file when it launches again.

Update Firefox.
Some crashes are caused by problems within the Firefox program itself, such as problems with specific operating systems or crashes that occur only in new Firefox releases.

Updates may contain fixes to these Firefox crashes, eliminating the crash problem once the browser update is installed.
2helpful
5answers

Google chrome keeps crashing not sure why

You need to check out all these:
1. Check for Conflicting Software:
- Some third-party software can cause Google Chrome to crash. When this happens, you'll see the message "Whoa! Google Chrome has crashed. It's possible that you have malware that can cause Google Chrome to crash.
- Google Chrome has a hidden page that will tell you if any software on your system is known to conflict with Google Chrome. To access it, type chrome://conflicts into Chrome's address bar and press Enter.
- You can try to fix these crashes by updating, disabling, or uninstalling any conflicting third-party software listed in "about:conflicts" on your computer. Also, take a look at Google Chrome's known issues for specific solutions to resolve crashes caused by some software.
2. Scan for Malware
- This includes malware and network-related software that interferes with Google Chrome. Malware can also interfere with Google Chrome and cause it to crash.
- You can try using Malwarebytes, or other anti-virus software to scan for and remove malware or you can also try searching the web for information related to any conflicting modules listed on the chrome://conflicts page (Windows only), to see if there are other steps you can take to remove malware.
- Many crashes are caused by malware. If you're experiencing frequent crashes, try scanning your computer with antivirus software.
3. Solve Flash Crashes
- We have found that the Flash plugin Chrome includes can cause it to crash in some cases. If you are seeing regular Shockwave Flash crashes, you may want to try disabling the internal Flash plugin and using the standard Flash plugin in Google Chrome.
4. Switch to a New Profile
- Chrome crashes may be caused by a corrupted profile. You can test this by creating a new profile from Chrome's Settings screen. Open the Settings page from Chrome's menu and click Add new user under Users.
- Change to the new profile after creating it and see if the crashes continue to occur. You can sign into Chrome with your Google account to sync the data from your old profile. However, Google recommends you don't copy any files from the old profile folder by hand - they may be corrupted and causing the problem.
5. Fix System File Problems

- Google recommends running the SFC.EXE /SCANNOW program to check for - and fix - problems with protected system files on your Windows system if you are encountering crashes. To do this, locate the Command Prompt in your Start menu (press the Windows key and type Command Prompt), right-click it, and select Run as Administrator.
- Type the following command in the Command Prompt window and press Enter:
SFC.EXE /SCANNOW
- Windows will scan your computer for problems with system files and fix any problems it finds.
6. Hardware issues
- It can also cause Chrome crashes. You may want to test your computer's RAM and ensure it isn't faulty.

· If still problem not solve, maybe you should try these simple steps:
1. Try restarting your computer first. It could be that the computer has just encountered a slight glitch on your system, which is causing things to not work properly.
2. Remove and Re-install the Google Chrome application. Doing this will allow your computer to read the files a lot better and faster, and also repair any damaged or corrupt files that have been causing the issue. To remove the Google Chrome application, first insure that you have another browser, such as IE or Firefox, click "Start, Control Panel, Add / Remove Programs," locate "Google Chrome" click UNINSTALL next to it. When the application loads, select "REMOVE" (not repair). Follow the uninstall process, and restart your PC. Problems uninstalling or re-installing Chrome indicate mal- or spy-ware, which must be dealt with.
3. Remove any extensions that you have on Google Chrome. Although they are a great way to personalize your Internet browsing experience, they are not so good for speed and functionality, as many can cause the application to crash. To remove any extensions follow these steps: Open up Google Chrome. In the address bar type chrome: //extensions. Click Uninstall, or Click Disable if you think you may use the add-on in the future. Restart your browser.
4. Disable plug-ins. Chrome can get bogged down with plugins that you aren't using, also. Type about: plugins into Chrome; it will redirect to chrome://plugins. Disable any that you aren't currently using.
Hopefully your Google Chrome crash problems are gone. Hope it works. Sharing is always caring.
2helpful
1answer

How do i fix windows delayed write failed. failed to save all the components for the file \System32\00007e87. The file is corrupted or unreadable.

Description:
Application popup: Windows - Delayed Write Failed : Windows was unable to save all the data for the file [name_of_the_file_you_want_to_save].
The data has been lost. This error may be caused by a failure of your computer hardware or network connection. Please try to save this file elsewhere.
Cause:
This problem occurs when the data redirector of a System flushes the contents of the file, and writes to a file handle with read-only access instead of to a file handle with write access.
When the redirector received an opportunistic lock break to none, it purged the cache for the file, but did not uninitialize the cache for the file.
More Information:
The redirector also needed to purge and uninitialize when the set end of file occurs because the opportunistic lock break is asynchronous. Because it did not uninitialize the cache for the file, it wrote to the incorrect file handle.
Remediation:
Warning: Serious problems might occur if you configure the registry incorrectly by using the Registry Editor. Microsoft recommends that you create a backup of your current registry before making changes.
1. Click Start, and then click Run.
2. In the Open box, type regedit, and then press ENTER.
3. In Registry Editor, locate the following subkey in the registry:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet \Services\LanmanServer\Parameters
4. In the right pane, click EnableOplocks, and then press ENTER.
5. In the Value data box, type 0, and then press ENTER.
6. Quit Registry Editor.

This problem occurs when the redirector flushes the contents of the file, and writes to a file handle with read-only access instead of to a file handle with write access. When the redirector received an opportunistic lock break to none, it purged the cache for the file, but did not uninitialize the cache for the file. The redirector also needed to purge and uninitialize when the set end of file occurs because the opportunistic lock break is asynchronous. Because it did not uninitialize the cache for the file, it wrote to the incorrect file handle.Back to the top RESOLUTION Service pack information
To resolve this problem, obtain the latest service pack for Microsoft Windows XP. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
322389 How to obtain the latest Windows XP service pack Back to the top Hotfix information
A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site:http://support.microsoft.com/contactus/?ws=support
Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language. The English version of this fix has the file attributes (or later) that are listed in the following table. The dates and times for these files are listed in coordinated universal time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.Windows XP SP1, Windows XP Tablet PC Edition

Date Time Version Size File name
--------------------------------------------------------------
30-Jan-2003 21:41 5.1.2600.1164 400,896 Mrxsmb.sys
30-Jan-2003 21:41 5.1.2600.1164 154,880 Rdbss.sys

Windows XP 64-Bit Edition

Date Time Version Size File name
-------------------------------------------------------------
30-Jan-2003 21:41 5.1.2600.1164 1,259,392 Mrxsmb.sys
30-Jan-2003 21:41 5.1.2600.1164 489,216 Rdbss.sys


Back to the top
WORKAROUND
Important This section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, click the following article number to view the article in the Microsoft Knowledge Base:
322756 How to back up and restore the registry in Windows
To work around this problem, disable opportunistic locking on the file server:

Click Start, and then click Run.
In the Open box, type regedit, and then press ENTER.
In Registry Editor, locate the following subkey in the registry:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet \Services\LanmanServer\Parameters
In the right pane, click EnableOplocks, and then press ENTER.
In the Value data box, type 0, and then press ENTER.
Quit Registry Editor.

Back to the top
STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article. This problem was first corrected in Microsoft Windows XP Service Pack 2.
Back to the top
MORE INFORMATION
For additional information about opportunistic locking, click the following article number to view the article in the Microsoft Knowledge Base:
296264 Configuring Opportunistic Locking in Windows 2000
A trace of this problem shows that the file is opened at least two times, and shows the system improperly writing to the read-only file handle. A trace that shows this problem is similar to the following:

96 CLIENT SMB: C NT create & X, File = \newshare.xls
SMB: Desired Access = 0x00020089
(Read Data,Read EA,Read Attributes)
97 SERVER SMB: R NT create & X, FID = 0x5
SMB: Oplock Level = Batch

<content removed that displays the client program reading and locking the file, but the file is not closed>

450 CLIENT SMB: C NT create &amp; X, File = \newshare.xls
SMB: Desired Access = 0x0002019F
(Read/Write Data, Read/Write EA, Read/Write Attributes)

451 SERVER SMB: R NT create &amp; X, FID = 0xc007
SMB: Oplock Level = NONE

<content removed that displays the client program reading, locking, writing and flushing data on this file handle>

585 CLIENT SMB: C write &amp; X, FID = 0x5, Write 0xc00 at 0x00005000
PID = 0xFEFF TID = 0x1002 MID = 0x4400 UID = 0x0801
586 SERVER SMB: R write &amp; X - NT error, System, Error, Code = (34) STATUS_ACCESS_DENIED

Note The process identifier (PID) of 0xFEFF in frame 585 represents the client system process that is using the read-only file handle. It does not show the client program writing the data to disk.
Back to the top
0helpful
2answers

Corrupt MYOB data file

Our MYOB 14 .dat file is crashing. We suspect a corrupt entry in the database. The file will open but as soon as we trying to do anything the program closes and produces the following error: MYOB must terminate. Termination Code 1284 Important Details: Error -3000 in DMGTEKey (5037:7000:69) Seems to be the same error every time. We have tried running MYOB's Verify and Optimise tools with no luck. Each time either tool is run the program crashes and displays the error: An error occurred while attempting to compact the database. DM Error = (-3000-5049-7000-158) Restoring from a backup is not an option as last backup was 3 months ago. So looking for solutions to fix the current file please. Will not be satisfied if the solution is to take it to MYOB. Need someone who can actually dig around inside the file and correct the errors??
4helpful
1answer

APPCRASH error please help

When program files or files within your computer's registry have become corrupted, this can cause the programs to unexpectedly crash. When a program crashes, you will likely get an Appcrash error. The error message will say "Windows Media Player (or whichever program has crashed) has stopped working" and then list rows of technical information regarding the cause of the crash. Unless you are a computer programmer, you may never fully understand what caused your program crash, but that doesn't mean that you can't fix it.
Delete any new programs that you have downloaded. Often, the cause of corruption in a computer system are bad downloads that bring harmful files onto your computer. If you started to get the Appcrash error on your system after downloading a new program or software from the Internet, it's highly likely you have downloaded a bad product. Use the "Add/Remove Programs" feature in your "Control Panel" to get rid of the program immediately.
Uninstall the program that is crashing. It is possible to fix the program's corrupted files while the program is still installed, but to make sure that you clear the program files completely, it is safest to completely uninstall it from the system.
Run a full scan of your computer. Your computer should already have antivirus software installed that can scan for corrupted files and either fix them or delete them from your system. If you do not have antivirus software on your computer, that could be a big part of the problem. Purchase and install antivirus software as soon as possible. These are designed tor from outside threats. Once you have the antivirus program installed, open it and click "Scan Computer." The antivirus scan will isolate bad files and you will be given the option to remove them from your system.
  1. Reinstall the program that was crashing. Now that the corrupted files have all been removed, your program should run smoothly after reinstallation.
  2. Check for program incompatibility. If, after a thorough scan and cleaning of your computer and reinstallation of your program, the Appcrash errors continue, the program you are trying to use may not be compatible with your program. For instance, there are some DVD softwares, such as Media Now, that do not work correctly with Windows Vista. These lists can be easily found online. If this is the case, you will have to purchase a software program that is compatible with your OS
You should download a program such as RegCure and run it from time to time. If you are unable to download a copy let me know and I will give you a link on my web where you can download it.


0helpful
1answer

Cisco VPN Client for 32 bit vista

Download the latest version of the Cisco VPN Client. My version is 5.0.03.0530.

You can also try using the Microsoft "MSIZap" utility to ensure a clean uninstall. It is a command-line utility. You will need the original MSI install file from the Cisco VPN client to use MSIZap.

You can download it here: http://msdn.microsoft.com/en-us/library/aa370523.aspx
0helpful
2answers

Loading Excel and Word

I would try uninstalling Excel and Word and reinstalling. Something seems corrupted.
Not finding what you are looking for?

209 views

Ask a Question

Usually answered in minutes!

Top Intuit Computers & Internet Experts

Ekse

Level 3 Expert

13435 Answers

Mandeep  Singh
Mandeep Singh

Level 3 Expert

1184 Answers

Mike

Level 3 Expert

4382 Answers

Are you an Intuit Computer and Internet Expert? Answer questions, earn points and help others

Answer questions

Manuals & User Guides

Loading...