closed checks have not been purged problem 3

[VeskoPashpurov]

Hi all, i just found this forum so im kinda new here. Ok to the subject i`m using micros 3700 3.2 sp6 hf1 and recently i have this eror message coming out every time when i want to open a table "warning -- 4728 Closed checks have not been purged" and also i have this single table under micros screen that says: "check detail read failure" tnx in advance everyone and appreciate ur help.

 

[pmegan]

The single check problem is what Micros refers to as a ghost check. Basically it's an open check that's lost the link between the main check table and one of its child detail tables. Just give you Micros support a call and they can dial in or walk you through forcing it closed.

If the ghost check has been hanging around for a while it may be causing your purging problem too.

The "checks not purged" message usually means that your end of night autosequence either isn't running or isn't set up correctly. Here are some things to check:

In the POS Configurator, go to the Reporting tab, Autosequences button. Scroll down until you see your End Of Night procedure and click on it. If you run this manually, make sure that "Hide On Run Screen" is unchecked. If you let it run automatically, make sure the Schedule Class is set. Click on the folder next to the Schedule Class dropdown and make sure the corresponding schedule is correct.

Now go to the Autosequence Steps button. Select your End of Night procedure in the dropdown box. One of the steps with a type of "Stored Procedure" should be "Purge Historical Totals". Make sure that "Skip Step" is false.

If everything looks correct, write down the Autosequence number and close the configurator. Open windows explorer and go to \micros\res\pos\etc. Find 3700d.log and open it with notepad. File rotates with the End of Night, so all entries should be from the current day. If not, you'll know there's a problem.
Search the 3700d.log for the autosequence number you wrote down. Eventually you'll find a step with an error.

Once this is done you should look into running a rebuild on the database. When it can't purge totals it gets to a point where all the disk space it has allocated fills up and it has to start grabbing more. When it finally starts purging again, that space isn't returned to the OS until the db is rebuilt.

 

[VeskoPashpurov]

THANK YOU very much pmegan apreciate your help the purging problem is fixed but still got to figure the ghost table and calling micros is a problem bc they will ask for $$$ of course but ill try anyway thank you once again!

 

[bugeisha3]

I am having the single check issue that is mentioned in this thread. I've tried almost everything and my micros tech support is not helping. Does anyone have some instructions on how to force a check closed? If any one does, I'd appreciate it you'd forward it to me.

 

[jimmymcp02]

you have to find the check seq and then execute the command micros.sp_forcechkclose


To correct this problem do the following:

Open dbisql

type the following sql script

Select * from micros.chk_dtl
where chk_open = 't'
order by chk_seq

this will only display open check from previous business and current dates that are open.
right down the chk_seq # (compare what check are still open)

now run another sql script

call micros.sp_forcechkclose (insert chk_seq # here)

you have reapeat this step for every open check that you wish to force close

 

[monicas21]

can you run this command without dbisql?

 

[jimmymcp02]

not that im aware of...because you need to look for the check seq