MICROS Check cannot be created

[themicrosman]

I have a MICROS 3700 system lab in demo mode. I am trying to open a check with a table number. It keeps saying "Check can not be created" after I enter the table number. It is a good table number. Any ideas anyone? It seems to work fine otherwise except I cant open a check to test ring items.

 

[michelle305]

I know because I have had this recently.
The solutions say.....
This is likely a version incompatibility, between database and application software. The database may be at a higher, or more recent version than the application software.
You can do this when looking in Version Info on the site. Then compare the build version of the POS tab and the Database Tab.

Also look in the 3700dlog and see which table is causing the error because it may have reached it's mass Constraint. Then you can search solutions by that table for the next step.

IF the Second >>>>
This does require DBA.
--
Go into Sybase Central, locate table notify_event_temp
Go to Check Constraints tab
Right-click properties on the constraint for notification_seq
Defitions tab
Adjust the upper bound of that constraint to be 2147483647 instead of 9999999
Save, reload db, restart dbupdate

 

[themicrosman]

Thanks Michelle, but that does not seem to be it. The DB and POS seem to be in sync with the same version 4.10.3.3355. and I checked the constraints on the table you referenced, but that appears to be fine also. This is a sample database I grabbed from a live location. I matched all the variables I could think of on my lab. The database starts, you can go in to configurator and work. You can start ops as well. Its just opening a check it does not like. I am running in full demo mode also. I don't have a software key. I just want to run some tests. Its very strange and frustrating.

When I try to Begin Table and enter the Table number, it shows this in 3700d log.

SQLExecDirect: (37000)[Sybase][ODBC Driver][Adaptive Server Anywhere]Wrong number of parameters to function 'sp_InsertChkDtlEx'
Error in call to sp_InsertChkDtlEx statement

 

[pmegan]

Try reloading the MR and any hotfixes with the database in place on the server. Sometimes the system can be flaky if you move a database that doesn't need to be updated.