micros 3700 database fault.

[mdiaczyk]

Once or twice a week I get a fault on the micros control panel under database. What causes this? Is this something I can troubleshoot? What causes this? In the log it says rbdbms fault.

 

[DrZogg]

Hi,

not enough information. What is the problem? What is the fault? You could read the logs, but even then you need to know what u r looking for. You should also include RES version and service pack details, and if there is an error message, what that message is and what u are doing when the error happens.

Cheers

 

[mdiaczyk]

Okay I looked at the log. This is what I found.
Sat Aug 28 16:47:15 2010 | MICROS4 | 3700d | 3f8 | Op step changed from [39] to [1] after [runDBMS] [FAULT] |
3700d | 48c | current working directory for process [runDBMS] [D:\MICROS\Common\Bin\RunDBMS.exe ] will be [D:\MICROS\Res\Pos\etc] |
Sat Aug 28 16:48:05 2010 | MICROS4 | 3700d | 48c | calling CreateProcess() for process [runDBMS] [D:\MICROS\Common\Bin\RunDBMS.exe ], dwCreateFlags 0x0000000C, startupInfo.dwFlags 0x00000001, startupInfo.wShowWindow 0x00000007 |
Sat Aug 28 16:48:05 2010 | MICROS4 | 3700d | 48c | current working directory for process [runDBMS] [D:\MICROS\Common\Bin\RunDBMS.exe ] will be [D:\MICROS\Res\Pos\etc] |
Sat Aug 28 16:48:05 2010 | MICROS4 | 3700d | 48c | calling CreateProcess() for process [runDBMS] [D:\MICROS\Common\Bin\RunDBMS.exe ], dwCreateFlags 0x0000000C, startupInfo.dwFlags 0x0000
Sat Aug 28 16:48:15 2010 | MICROS4 | 3700d | 48c | Timeout: Detected process fault for process [runDBMS] [0x00000614] |
Sat Aug 28 16:48:15 2010 | MICROS4 | 3700d | 48c | Op step changed from [0] to [1] after [runDBMS] [FAULT] |
Sat Aug 28 16:48:15 2010 | MICROS4 | 3700d | 48c | Timeout: Trying to automatically restart process [runDBMS], retry count 4 |
Sat Aug 28 16:48:15 2010 | MICROS4 | 3700d | 48c | Freeing old environment block [0x0015CA78] for process [runDBMS] |
Sat Aug 28 16:48:15 2010 | MICROS4 | 3700d | 48c | current working directory for process [runDBMS] [D:\MICROS\Common\Bin\RunDBMS.exe ] will be [D:\MICROS\Res\Pos\etc] |
Sat Aug 28 16:48:15 2010 | MICROS4 | 3700d | 48c | calling CreateProcess() for process [runDBMS]
I think this is what is going on.

 

[DrZogg]

Hi.
I will make some notes on what is happening here. The rundbms.exe uses rundbmsdll.dll, dbsecurity.dll, dblib9.dll, and dbtool9.dll plus a few other ole32 dlls.

This is the line where the server state is lost
Sat Aug 28 16:47:15 2010 | MICROS4 | 3700d | 3f8 | Op step changed from [39] to [1] after [runDBMS] [FAULT] |

The 3700d server states are:
0=OFF
12=DATABASE
28=BACK OF HOUSE
39= FOH

So you can see in the above log that the database state is going from Operations to some state barely above off.

IT is common for RUNDBMS.dll to lose connection with the DB, but it would normally reconnect with a function call (below) where we are getting a connection fault.

Sat Aug 28 16:48:15 2010 | MICROS4 | 3700d | 48c | Op step changed from [0] to [1] after [runDBMS] [FAULT]

===========================================================
Next time this happens could you please (on the server) type: START>RUN>services.msc
(run the services manager) and check the services running. The Micros Databases services which should all be running are:
MICROS 3700d Server
MICROS Database Service
MICROS DB Update Service
sqlMICROS4

A guess at this point is that either an antivirus is stopping a Micros service, or that a SQL connection to the DB is set to Stop the DB when closing the connection.

There is no documentation on this problem. If you could also provide details on which version RES4.xx would be good.

Cheers

 

[mdiaczyk]

Okay I figured half of this out. Downtown Sarasota is fixing the street lights and pulling wire. Our ups is not big enough to put up with a ten hour power outage. The other issue is Comcast has been going up and down. Where the lines cable tv lines down to the ground could have been nicked. I need to look at what services have been going up and down. Figure out why. Mcafee?

 

[DrZogg]

Hi,
something appears to be taking the database from front of house to off, so the next time this happens check the server system services to make sure the 4 database specific services above are on.
Cheers