Unrecoverable Error

I haven't had that problem (or any problems) so far. If you would supply more info, maybe someone could help. What operating system are you using? (Hopefully it's not Vista.) Does your system do this only when running ProSeries, or is it doing it with other programs too? Are you running it on a network or standalone? Is it Windows that's reporting the unrecoverable error, or is it ProSeries? Does the little rectangle pop-up asking you whether you want to report the error to Microsoft? If so, you can find information about what's causing the problem from clicking on the box that shows you the details of the computer operation that produced the error. This will contain alot of computer jargon that's meaningless to me, but it will usually be clear enough for you to figure out which specific program or specific operation caused the error. Also, in re-reading your post, am I correct that you can't get back into ProSeries at all? If so, I would try reinstalling by doing a manual download of the program and then updating. You shouldn't lose any of your data by doing so. Also, try last year's program to see if you can access it. I know it looks as though I'm just using a shotgun approach here, but more specifics about the problem would help. One final question: at any point does your entire screen go blue, display alot of words, then go blank before you have a chance to read it?

I don't mind the shotgun approach. I am running it on a network, using Microsoft XP. This problem only happens when running Proseries. The little box asks me to send the report to Proseries. Proseries will load up and re-index my homebase, which is confusing me because it seems to be looking at my 2006 files because I only transfer clients into my homebase as I prepare their current year returns yet the tab says it is indexing 1,286 files. Which is the amount of returns I prepared last year. Once it loads up I can open a client but the minute I begin working on it the error appears. I am on my way into the office this morning I will try your suggestion in the re-install and hopefully I can get hold of someone at proseries tech support this morning. In answering your final question, no we don't have the blue screen issue.

Thanks for your help. I will keep my progress posted.

I don't have an answer because I don't use the network version. My guess is that it will ultimately turn out to be an easy fix since we're not seeing similar posts on here. Plus the fact that you say it has been working fine leads me to believe it's going to be a minor problem in the long run (although that's not much consolation at this point, I know).

As I say, I don't use the network version so I'm guessing whether this would work, but until you get this resolved, you might consider installing the software as a standalone. Right now it sounds as though you're effectively completely shut out of ProSeries due to the network glitch. If you reinstalled as standalone, that would at least allow you to get work done until you figure out a permanent fix or are able to reach Tech Support. Good luck!

Ok....spill the beans. What's wrong with the vista and proseries combo? My first year with Vista. No problems yet, except the usually little ones.

We seem to be having the same problem with two of our systems. The others seem to operate fine. It may be the BIOS of the operating system. Try running a system restore on your Computer and then try and see if it continues.

Good Luck!

We're running 7 workstations on the network version and have been having these type of crashes all week. Our workstations have fairly beefy specs (Core 2 Duo, 2 GB RAM, Gigabit Ethernet, etc.) so it's certainly not the computers. All other programs including prior ProSeries year programs work as expected.

Something is definitely wrong with the network version. We're having HomeBase problems, as well, as we've been sending returns electronically these last two days. Clients disappearing from the HomeBase, Client Status not showing the correct status, etc.

I can't say I'm completely surprised since we've been dealing with these types of problems for years now. I just hope Intuit recognizes these bugs quickly and informs Tech Support on the front lines, because every time I call, they've never heard of anyone else having the same problems.

You might poke around in the TY06 archives. It seems that these network problems with ProSeries are an annual ritual, but you might find something in last year's archives to point you in the right direction. The only thing I know about the network version of ProSeries is to stay away from it. Luckily, I have that option. I know most users don't.

Tech support said that the unrecoverable error was unique to our installation. Saturday morning I spoke with them and they said they would get right on it. Monday morning and the wait time on phone is over an hour. Chat is not available. Clients are expecting checks tomorrow.

We uninstalled and downloaded network version. Reinstall doesn't work. Trying to work with the stand alone version but we're having issues such as duplicate DCN's......

If anyone finds a solution PLEASE let us know!

After two hours waiting for phone support we decided to try work around with stand alone. What a hassle. We are able to function at 1/4 speed and four times the work. Program has to be set up on each computer and all the files need to be double checked on destination drive. Hope there is resolution soon. Anyone find an easier solution? After twenty years with TurboTax/ProSeries this is first time I feel that they've totally abandoned us.

I'm running a stand alone and have received this same error a couple of times. Mine is an Acer laptop running XP with a gig of ram. A couple of times I got an out of memory error. Never happened last year.

I also can't get Easyacct to run the IRS (Information Return System) to run on my computer. It runs in Safe Mode, but won't print. All of my other software runs fine.

It makes me wonder how these products can be released and have these problems. What kind of testing is performed? Very, very disappointed.

Ok I'm with Babs_13 what is wrong with Vista?
I've got 3 new machines all with Vista, because Proseries said it will work just fine this year. Also I have 2 machines with windows 2000 and 1 with XP. Server with windows 2000.

I'm having the errors everyone else seems to be having, but they don't have Vista. Unstable homebase, unreliable status for returns. Individual clients in homebase go blank. Open return save and they're are back.

Messages when efile that says returns was not sent due to... something about No value in EF Center. Open return, return is there save return try to send again. Rejects, intuit already has a return with this dcn. Blah Balh Balh...

I go to efile - check acks. And low and behold there it is... Now status says received by intuit.

Got another same thing with federal but State(Indiana) won't go "no value in ef center". No pre-submission.. something or the other. Sorry can't remember all now have all the printouts and notes at work.

Screen, any screen, goes total light gray and at top by Proseries 2007 says (NOT RESPONDING). Throws you out of program. It might do this 1 time or 6 times then seems to run fine. All this has been on my Vista machines. Today we are only going to work on the non vista machines and see what happens.

I've been waiting since Frday 1-11 for a call back from Tier II support because Teir I couldn't help. I call back and they don't want to talk just wait for your call from Teir II, your on the list. They'll call you when they get to you on the list

I do know when I call Proseries,they do not know much of anything about Vista and they have to go "find" a computer with vista on it.

To avoid future problems would we be better in the long run to strip vista off and load 2000 or XP? It's now or we won't have time until May.

I used the Express program since it came out without any serious problems and had to switch back to professional this year when Proseries dumped Express. For the additional $2300 I get this mess.

I don't think Vista is the problem. Are you running network or standalone? We've got a working solution using standalone with XP.

For the efile problems may be simpler to open the Homebase View "EF Center". Select "Efile" from top line menu. Select "Electronic Filing" from the drop down. Select "Update Acknowledgment Status of Selected Returns" from the next drop down. Select one client at a time. We've found this to fix status on files sent.

Still no word from Tech Support on our problem.....

We do have the same problem and the other major printing problem too. Beside the Unrecoverable Error, we also receive error code #202 when printing the complete return and create PDF file.

It's not just with Vista, debrigdon. We have the same problems on an all XP workstation network.

Every year they promise better network reliability, but I swear it gets worse. I would love to know how they test their software.

A couple of times already this year a like problem, but tonite the schedule F wouldn't allow me to enter any info, altho I could enter on any other form. Finally just bam, gone, client and program. Just as tho I hit the close button, didn't ask for status, didn't ask to save, just gone.
Started program again and it was fine. It was almost like it was computing in the background and couldn't get the job done.
Happened a couple of times last year on big farm returns and the automatic save didn't seem to catch it in time and I had to re-enter the info.
Already happened 3 times this year, always on Sched F.
Now I F-10 after each major entry. Like when the income is complete and when the expenses are complete, etc. Then at least I can recover the return.
Tech support doesn't seem to have a clue.
Win XP-Pro, 1 gig mem and so on.
might be a scary season.

I encountered the same result when I checked the boxes on the Information Worksheet to answer the Yes/No questions for "Credit for Qualified Retirement Savings Contribution (Form 8880)." Same thing--the program just shut down. I wasn't sure what I had done to cause the shut down, so I restarted, brought the same return back up, clicked the Form 8880 Yes box again, and boom! ProSeries shut down again. I repeated this same thing with the same result one more time. Then I tried it a 4th time, and it worked fine. Same computer, same return, same sequence of mouseclicks, but it took 4 tries for it to work. Other than that, and a few minor annoyances, the program seems to be working ok (knock on wood). I just keep hitting that F10 key though.

I have the same problems with no word on how to fix it, or when a fix is coming. I have clients waiting for checks and getting desperate....

This is just terrible.

What a waste of time.

Yes - I have seen it again and again.

Usually to remedy the error, you need to sync your homebase with your server.if you are setup in that environment.

Have you been doing your maintenance?

James

Not a direct reply to James, but we've been doing every type of maintenance possible to no avail.

We still get a great deal of Unrecoverable Errors, not to mention Homebase corruption and general instability.

We've been using ProSeries for over a decade, so problems with the program are not new to us, especially on the network version that we use.

This year has been extraordinarily bad, though. Tech support has been extremely unhelpful. You know it's going to be bad when they won't even acknowledge the problems. They try to blame your hardware or setup, but since I'm the admin, well...you know.

Your right! As this is my 9th year with PS, but have seen enough errors with PS that I should be supporting Windows ME for MS! :-)

Have you removed the local file on your workstations for the homebase? That is the file that is supposedly sync'd from the server? I learned that trick in 05 and have used it consistantly to get results.

Are you have errors on your HomeB server? Does everything work there?

As you know, but others may not, you need to make sure that you are consistanly backing up your 0x_Data (07 this year). While I have restored once this year for one of my clients that wanted a Citrix MetaFrame impementation and it was a disaster!

Email with q's - James

JHulscher@HHHTechnology.com