Program Crashed

I don't know for sure if it is my computer that is causing the problem. Apparently no one else has had the problem or at least I am not aware of any other posting. I am getting paranoid. It seems to be related to Schedule C.

I've had one instance of what you've described. Yesterday, the program simply stopped, and I got that little window asking me to report the glitch to Microsoft (you know the little window I'm referring to). Same thing, no autorecovery file to be found. I had lost about 15 minutes worth of work, but of course I had to review the entire return because I wasn't sure which entries had survived the crash. I've been using ProSeries for 14 years, and that's the first and only time I can remember the program simply stopping right in the middle of everything. So I guess I had been living on borrowed time.

We have had the same experiences with 2006 program crashes on various workstations. Only way found to continue was force all proseries programs to quit and restart(reboot) all workstations and PC operating as server. Of course with some data loss in some cases. An unusual day is when there are no crashes.

There are several kinds of stops (crashes): 1 send some thing back to intuit: 2 hangs when saving file (all other workstations hang too); 3 Memory error; 4 cannot find common file; 5 no path to server.

Twice today it crashed again. We are using a network with dedicated server. I have the thing set for doing backups every 5 minutes, but it has not ever recovered anything that had been entered. Is there another place other than the timer under options? I would call the help desk, but they are not help. I ordered a scanner a week ago. Called support, talked to somone in the Phillipines, who could not find my order, after talking to her supervisor for awhile she said that the order had been recieved and that it would be shipped by DHL sometime, but did not know when. Isn't life great!!

Count us in MFAbreu's list of errors:

They seem to be ramping up too and occurring more frequently and at seemingly random times and we are trying to isolate the issues.

Networked workstations are getting the "MEMORY ERROR"... something I suspect to do with Homebase. I've told couple preparers to enter into a client file using the "partnership view" of homebase (a lot less clients in the database vs. indiv. which has 5,000). So far so good at least until later today when I'm sure it will break. Tip: DON'T click the "OK" button immediately. I was able to just move the window and actually keep working in Proseries and save it too!?! Of course after that's done, then you can blow up PS by clicking OK, but all the stuff saved well.

Crashes are happening on our stand alone workstations (all are XP Pro with min. 1gig RAM) with the "Send Error report to intuit" window. It's not like windows xp is brand new to these folks who program this software.
... oh well, another year, another set of ProSeries issues.

I experienced crashing, last year, when I deleted a line in a table in input mode. This year, I've crashed twice, with the advice that I tell Bill Gates about it. In each case I had deleted a line from a table in input mode a few minutes earlier. I, too, lost all date even though the program was supposed to do automatic saves.

My solution? to TTPro crashes --
I turn off autosave-I do not trust it re prior experience NG
I ctrl-s every few minutes (I have worn out ctrl-s keys)
I use send-to command from Explorer to backup file-my insurance that I have a fairly current backup file
Comments?

What I have learned to fix some of these problems. If you have a firewall running shut it down. You will have a lot fewer problems.

Well, you may have less problems with proseries. Let us know how things go with the FBI.

If you have a firewall, run it. If you don't have one, get one, now.

I too had been working 1/2 hr on a return when PS Pro crashed. Autosave enabled, but no file saved. Call to PS support and was told that autosave only starts functioning after the first manual save. So open file, save, and proceed.
Still no explanation as to the cause of the crash.
I think it's attributable to technology
Jim Kelly

Jim Kelly: was this a new client, or one transferred from prior year?

I can't remember, It wasn't a question the tech person asked, nor did she qualify their explanation. but I believe it was a transfer from prior year.

I suppose that is a crash message, I can't get into the program to do returns, and I have them piled on my desk. It's late Sunday afternoon and I thought that I would get some work done, but not so. This has never occured before and tech support is not available until Monday morning... I am livid. But such is life... Has anyone else had this problem.... I didn't see it in the forum anywhere.

Thanks.

Did you try to reinstall the program?

Check out some of these messages:

http://forums.turbotax.com/int...

Here I am again. I am begining to detect a trend. I have been having major storms of crashes the last couple of days. It seems to be happening in only large files with maybe a couple of hundred of entries. It also seems to be in either schedule C or F returns. Not nessessarly working in those schedules, but with those being accessed. Someone suggested a driver conflict, but my IT guy said the only drivers ps usses are printers, and it doesn't seem to have a problem there. I would very much appreciate Proseries program management personal to monitor this forum and address the issues brought forward. If anyone is calling the 'help desk' which I have found to be no help at all, if they would each time as for monitering of this forum, that might help. I have tried rebooting, shutting down other programs, and nothing seems to help when a file gets to big. I am going to try accessing the file on another station to determine if the problem is in the software or the station. If I find I get the problem in another station also, it will be an indication that the problem is software related, which I think it is. Just thought about a denial of service attack on intuit something similiar to what they have given us...don't know how we would get it done, but at least we would get their attention.

I was talking about symantec client firewall which was causing many problems with proseries. I still have a hardware firewall to protect my network. Overall the symantec client firewall is to much work to manage as well as zone alarm which I tried also. I do not need to be a full time tech support person I need to get taxes done.

Looking at your dossier I suspected that was the case, but your advice basically said "turn off your firewall" and I was afraid someone would read it and do just that. I'm sure you can recognize just how much of a disaster that could be. Please, when you're giving advice, word it carefully; remember that not everyone that hears it will interpret it the way you meant. And yes, Symantec is a pain. You could try Comodo on one of your machines, perhaps between seasons - it seems to be a little less intrusive than the others while doing an apparently fine job. A tax office could be a pretty nice target, consider the type of information you have on people and, at least in some cases, the quantity. And there are some very bad and very smart people out there.

Same situation is happening in our office.
Technical support has been not helpful at all. (ie. no answers)

Greetings!

The update that addresses the memory error issue was released on 3/6. If you have not updated, I urge you to do so, if you have, please verify your engine version by going to the Help menu, selecting About ProSeries, then holding the control key down and clicking OK. This will open a dialog that will tell you the version of the engine that you currently have. The version should read wPro.2006.08.00.25. If your version matches this, you should no longer see the memory error.

Kevin W.
ProSeries Technical Support