Error Writing to Disk............

User-to-User general discussions regarding POS Pizza
Veteran Member
User avatar
Posts: 154
Joined: Fri Oct 12, 2007 4:41 pm
Location: Illinois

Error Writing to Disk............

Postby joshwho » Tue Apr 08, 2008 7:37 pm

I keep seeing this message every now in then, even when no one is even logged in. Usually when I see this message, it happens when some one is taking a order. They will start taking the order and some times customers will have a hard time deciding on what food to get so the order taking field gets left open for longer then a couple of minutes. When they go to cash out the order it will say Error Writing to Disk. It still prints the Kitchen ticket but it never gets added to the data base. This is a big problem because this makes orders look like they have already been processed so the food gets handed out the food for free. I dont know why Its doing this It use to do it all the time but I have made so many improvements to the whole network. We are now running 200mbps Network speeds now we have no firewall restrictions for POS Pizza. Every thing including hardware and software was done a 100% correctly and I still get this error message every now or then. Is there going to be a update soon that will fix these problems ? I know its not a hardware or windows issue. Thanx.....

Site Admin
User avatar
Posts: 2083
Joined: Wed Apr 16, 2003 4:35 pm
Location: Western PA

Postby Scott » Wed Apr 09, 2008 7:55 am

Check the integrity of your database files. POS Pizza doesn't give a message exactly like the one you said. It would give you back an error number which will help better determine the problem.

This is not a problem that others seem to be experiencing so it is not in the software itself. My suspicion is that you have a corrupted record in one of your data files. That would explain it being intermittent, since the bad record may not be accessed regularly.

Scott

Support Team
Posts: 93
Joined: Wed Apr 16, 2003 5:51 pm

Re: Error Writing to Disk............

Postby Mike » Wed Apr 09, 2008 8:24 am

joshwho wrote:I keep seeing this message every now in then, even when no one is even logged in.


If you are seeing any error messages while POS Pizza is idle, then it is *not* from the software. POS Pizza does not do any writes while the system is idle or while no one is logged in.

It is from another process or Windows, but definitely not POS Pizza if it is while things are just sitting.

What Scott said is true if you get the message when you click a button, or take some action at that moment, otherwise the message belongs to another process.

-Mike

Veteran Member
User avatar
Posts: 154
Joined: Fri Oct 12, 2007 4:41 pm
Location: Illinois

Postby joshwho » Wed Apr 09, 2008 12:48 pm

I guarantee that its not windows. I have tested this on multiple systems. I have used different OS.'s and I even had a software team test it out they had the same problems. I don't see y u keep telling me this is a windows issue. No other pos software does this.

Veteran Member
User avatar
Posts: 154
Joined: Fri Oct 12, 2007 4:41 pm
Location: Illinois

Re: Error Writing to Disk............

Postby joshwho » Wed Apr 09, 2008 12:55 pm

Mike wrote:
joshwho wrote:I keep seeing this message every now in then, even when no one is even logged in.


If you are seeing any error messages while POS Pizza is idle, then it is *not* from the software. POS Pizza does not do any writes while the system is idle or while no one is logged in.

It is from another process or Windows, but definitely not POS Pizza if it is while things are just sitting.

What Scott said is true if you get the message when you click a button, or take some action at that moment, otherwise the message belongs to another process.

-Mike



If that was the case then how does the Deliv Stat Mod. update. The time date udp time server all run while no one is logged in.

Veteran Member
Posts: 177
Joined: Fri Apr 18, 2003 11:50 am
Location: New Jersey

Postby H-Man » Wed Apr 09, 2008 5:42 pm

joshwho wrote:I guarantee that its not windows. I have tested this on multiple systems. I have used different OS.'s and I even had a software team test it out they had the same problems. I don't see y u keep telling me this is a windows issue. No other pos software does this.


You make it sound like the POS system does this everywhere. I personally am only a lowly user, but have been running pos pizza for 4+ years now and have never encountered a problem like you describe. Did you check the files like the support staff asked you to?

Also if you tell them the numeric error code that the system is giving you, they might be a bit more helpful. Just saying that you are getting a disk write error ever time you wait during the order process isn't very specific. It may sound specific to you but I'm sure that the software is doing many things at this point.

I understand that you may be frustrated due to things happening during your rush times, but just coming on here and saying my Windows is perfect and that you know that's not the problem, and claiming the software is full of bugs is not a very good way to handle this. I am sure that if this were happening on a wide scale, then it would be a bug, and it would have been long ago addressed. I am not saying that this isn't happening to you, but a little calmer approach and maybe some useful information such as the exact verbiage of the error message (including the error code) would be very helpful in getting your problem resolved.

Just my .02

Member
Posts: 29
Joined: Wed Aug 06, 2003 1:42 pm
Location: Chicago, Illinois

Postby edembek » Wed Apr 09, 2008 6:03 pm

+1 for what h-man said. I manage several installations in my area, and none of them have had this problem.

Most data problems have happened because someone rebooted the server without logging the clients out first.

There has to be more to it? If you can replicate it over and over, then what steps are you taking? It sounds exactly like what the others told you. Data corruption. Fix your data files and it will probably subside. If left go, I know these problems tend to worsen.
Ed Dembek

Site Admin
User avatar
Posts: 2083
Joined: Wed Apr 16, 2003 4:35 pm
Location: Western PA

Postby Scott » Wed Apr 09, 2008 7:30 pm

Update: I spoke with Josh on the phone today and arrived at the conclusion that it was a timeout error (error code 99). The default timeout on the database engine is roughly 2 seconds. I sent Josh a test version with the timeout bumped up to the max value on the order saving process for a test run. We will wait and see if this helps solve the problem that he is experiencing.

Scott

Veteran Member
Posts: 177
Joined: Fri Apr 18, 2003 11:50 am
Location: New Jersey

Postby H-Man » Fri Apr 11, 2008 8:11 am

AND??

It has been a couple days now, did you get the problem solved?

Site Admin
User avatar
Posts: 2083
Joined: Wed Apr 16, 2003 4:35 pm
Location: Western PA

Postby Scott » Fri Apr 11, 2008 10:26 am

I will let you know as soon as I hear anything.

Scott

Site Admin
User avatar
Posts: 2083
Joined: Wed Apr 16, 2003 4:35 pm
Location: Western PA

Postby Scott » Mon Apr 14, 2008 7:56 am

Boosting the Databases Timeout value seems to have solved the problems that Josh was experiencing. This was easy to figure out once I had the numeric error code returned by the software. Normally for 99% of the systems out there the 2 second timeout is great, but here it needed a little more.

We are planning on making this value changeable in future versions. This will probably be done via the INI files since this is a setting that most people will never need to mess with. Along with this we may bump our default to be 5 seconds instead of the using the standard default of 2 seconds used by the database. 5 seconds is still a reasonable amount, but could be the difference in some cases between getting an error code back or having the transaction accepted. This is due to the fact that a POS system puts a much heavier load on a database system than most other types of applications do.

Scott

Veteran Member
Posts: 177
Joined: Fri Apr 18, 2003 11:50 am
Location: New Jersey

Postby H-Man » Mon Apr 14, 2008 5:52 pm

So since most of us are not having any such issue, I guess that this does not pertain to us.

Site Admin
User avatar
Posts: 2083
Joined: Wed Apr 16, 2003 4:35 pm
Location: Western PA

Postby Scott » Tue Apr 15, 2008 7:58 am

H-Man wrote:So since most of us are not having any such issue, I guess that this does not pertain to us.


You are correct.

Scott

Veteran Member
Posts: 177
Joined: Fri Apr 18, 2003 11:50 am
Location: New Jersey

Postby H-Man » Sun Apr 27, 2008 8:43 am

Scott wrote:Update: I spoke with Josh on the phone today and arrived at the conclusion that it was a timeout error (error code 99). The default timeout on the database engine is roughly 2 seconds. I sent Josh a test version with the timeout bumped up to the max value on the order saving process for a test run. We will wait and see if this helps solve the problem that he is experiencing.

Scott


Wow you would think that 2 seconds is more than enough time. In fact that is an eternity in computer terms. I guess it was something wrong with Windows after all because things should never take more than 2 seconds internally. What type of processors is this guy running? Probably needs a serious upgrade.

Site Admin
User avatar
Posts: 2083
Joined: Wed Apr 16, 2003 4:35 pm
Location: Western PA

Postby Scott » Mon Apr 28, 2008 6:55 am

This issue has been resolved.


-Scott

Return to General Information about v5

Who is online

Users browsing this forum: No registered users and 1 guest