QuekBooksPro 2005 I am getting a message "This file was not closed in the previous session. Rolling back to last fully recording transactions." Nothing is happening. Fortunately I backed up on 2/5/09, but I cannot figure out is wrong. We did not close the file other than in the normal manner.

If when you go on the internet using your browser it keeps asking you to restore last session because it shutdown improperly (or something like that). All you have to do is hit the "x" at the top right of your browser before you shutdown your computer.
That should stop you from seeing the restore previous session message.
R

It sounds like data damage. Go into Qb, then go to file, utilities, verify the data. If it fails you may need to rebuild the data.

It's pretty much just like it says:
You either, didn't close out the program right by manually saving the last information you entered.
Or,the system shut down while the program was open, like a power failure or accidental reboot.
Did you have the task manager open, to close out programs,maybe to regain some memory, accidentally closing the program?
Something happen to close out that program before the last entered data was saved

Would probably need the the entire error. The RB simply stands for Rejected Batch when you are trying to settle (I'm guessing with Vital/TSYS). the 00546 is the transaction number. This looks like a rather large batch. The transaction in question is the 544th transaction (the first two records to go over in the batch contain account information and your company information. So always subtract 2 from the number shown).

Without seeing the rest of the error, I can't say exactly what is wrong with the transaction. There should be a 3-4 digit number after the E in your response from the processor.

At any rate, depending on your version of PCCharge,there is a Batch Editor is included. It will be in (C:\Program Files\Active-Charge) for Payment Server or (C:\Program Files\PCCW) for Pro, and is named BatchUtility.exe. This will allow you to quickly view the batches and edit the transactions you need.

If Vital/TSYS is your only merchant account, then your batch will be named Visa1.xxx.Since it is now a rejected batch, it will be called Visa1.PCS (A regular batch should be Visa1.ENC for encrypted. Unless you are on a really old version). You should be able to open the Batch Utility, Open the bad batch by clicking find "Indeterminate" button, find the 544th transaction (if it's corrupt, you'll be able to find it rather quickly), and void it out. Keep in mind that this is not the same as voiding through the inteface, it is merely taking the transaction out of this particular batch, not voiding the transaction authorization. If it's a sale, you're authorization code will still be good (assuming it hasn't been over 30 days since you last settled). If it's a credit or void, there will not be an authorization number to worry about, and you can just dump the transaction altogether.

Make sure to take notes on the transaction so that you can run it as a post-auth (if it is a sale) after your batch is accepted. Once the offender is removed, you should be able to go back into PCC and settle as normal. You will get the message about "all indeterminate batches need to be closed first, blah blah blah", click "ok", check your totals and then attempt to process the settlement.

Good Luck and hope this helps.

Sorry David you'll need to get a replacement remote. Not the answer you probably want but that's the only way you're likely to close the sessions, unless someone has written some software that can do this. I had a problem with my funai with unclosed sessions and I had remote but laser needed adjusting

Do not worry about no Finalize Disk option. You may have it under another guise.
A recording session can be specofied as open ( Default ), or closed. If closed DATA cannot be appended to the disk.
No matter how many sessions have been written, if the last session is closed no more can be written. Your software automatically finalizes each session, in fact must.

That is an "Old QB Software version" installed in to a "Newer Version of Windows" issue.

QB 2002 most likely works best with Win 98 or 2000.

For your best functioning on your PC, I would ONLY do QuickBooks entries when your PC has just been freshly turned on and no other programs have been running first. Also "Pause" or temporarily "Exit" any background running software like Win Defender and/or any Anti-virus programs. Call QuickBooks and ask them how you could go about Up Grading your QB version to a more Windows compatible version without having to purchase EACH version to "UPDATE" your pre-existing database/files so they are not lost or dysfunctional. They once sent me disks to jump 2 versions and they charged me less than 50 bucks but that was a few years back. Good Luck!

this is an issue with firefox 3 try to use firefox 2 when logging in yahoo mail, other yahoo services are ok.

Digidesign website had the answer....go to windows,show workspace and change the settings for your relevant disc from transfer T to R...record in the A..audio column.
Thanks  Bobcat8

This sounds very much like a corrupt database. Blank transactions should not be allowed by a datafile that is fully intact.
You can start by verifying the data. Make sure all of the windows are closed, then go to file, utilities, verify.
If the verify passes, (and it may, even if damage is present), you may want to take the step of rebuilding the data.
Personal preference, I like to copy the company file to the desktop and run the rebuild on the copy, that way if everything goes to heck in a hand basket, the original file is still there.
If the issue continues after a rebuild, you may be faced with a situation where only Intuit can attempt to repair the data. The only problem is, they no longer support this version, and will only work on the file if you are upgrading to the 2008 version!
One way to quickly get an indicator the data is damaged, run a standard balance sheet for all dates on a cash basis. If the two bold numbers on the report are not in balance- you can pretty much bet the company file is damaged. Remeber, this type of issue will only be seen in a single company file, other files on the same computer can be fine.