Micros 3700 serving period issue

[Leagarow]

Hello,

could use any help available about serving periods that we have setup in pos configurator, the issue we are having is that the serving periods are not switching over as the time come for breakfast or lunch and so on and we have been doing it manually were as before it was automatic. We have checked all our setting for serving periods and periods and nothing has changed, we checked our services and all are running that should be, we just did a server reboot and still having issues any ideas???

Thanks

 

[Moregelen]

As far as I remember, changing serving periods has never been automatic in Micros... if you were changing automatically I'm guessing you had some sort of autosequence set to run.

Have any changes (any files deleted, auto sequences changed, database passwords changed, etc) been made recently?

 

[pmegan]

Are you talking about actual Micros serving periods, or the autolevels that change menu item availability, prices, etc...
Serving periods aren't usually used unless there's an interface that requires them, a hotel PMS for instance.

A quick way to check is to open the POS Configurator and go to System / Serving Periods and see if you have anything set up in there. You can also go to System / Periods and see if any of your periods have the "Serving Period" box checked.

Whatever you do, don't make any changes in these forms. They're a base part of the system and incorrect setting could really mess things up.

 

[Leagarow]

there has been no major changes but i narrowed it down to the batch file, i noticed it while i was working on it and a console open and started running the batch this is what it got:

C:\scripts>Dnrsrvprds.bat

C:\scripts>dbisql -c "uid=custom;pwd=custom;dbf=D:\MICROS\Database\Data\micros.d
b" -q D:\MICROS\Res\Pos\scripts\SP Scripts\dnrsrvprds.sql
Could not connect to the database.
Request to start/stop database denied
SQLCODE=-75, ODBC 3 State="42000"
You are not connected to a database.

now i think that there might be something wrong with this script or the database but as far as i know the database is still working cause its being used as we speak.

 

[Moregelen]

change 'dbf=...' to 'dns=micros'

And see if that helps

 

[pmegan]

'dsn=micros' not dns

I think you've been working with domains too much moregelen

 

[Moregelen]

D'oh. Nice catch Data Source Name != DNS

And yeah.. I spent most of yesterday chasing a crazy bug that ended up being caused by having a DNS that rarely updates... of all things... switched them to the google DNS and working perfectly -.-

 

[Leagarow]

tried this dbf to dsn still the same issue as last post

 

[pmegan]

Did you change it to "dsn=micros" or "dsn=D:\MICROS\Database\Data\micros.db"?

The old school "bdf=" is giving SQL the location of the database file (dbf)
Using "dsn=" is telling SQL to look at a datasource name (dsn), in this case the ODBC connection that Micros sets up during installation.

If you have "dsn=micros" and it still doesn't work, try opening up and logging into SQL:
Start | Run
Type in dbisql and hit enter
Username = custom
Password = custom

See if it connects or gives you an error. The message is a connection error, so the script is probably fine. The most likely causes are the connection string, or possibly a password change for the custom user.

 

[Leagarow]

dsn=D:\MICROS\Database\Data\micros.db" that i tried then "dsn=micros" and it seems to be working ill update you at a later time when its suppose to actually kick in at the right time rather then forcing running the batch

Thanks for the help pmegan!

 

[pmegan]

Good deal, hope it starts working.
Weird that it just started causing problems out of the blue. The dbf/dsn issue usually doesn't show up until you upgrade to Res 5. The only time I've ever seen it with Res 4.x is when you're connected to the Micros server through remote desktop.

 

[Leagarow]

ya i know what you mean its been a solid system for years but we will be upgrading soon to the newest, which will be nice cause we can have the server on one of the xen instead of it on its own server and upgrade 15 pos.

CHEERS

 

[Leagarow]

worked like a charm issue solved thanks for all the help pmegan gets thumbs up for this one