Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

Register Log in
  • Congratulations Mike Lewis on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

No Connection to the Micros Database - Database call failed with fatal error C70700CC

Status
Not open for further replies.
paul4867

paul4867

IS-IT--Management
Dec 19, 2012
18
US
Guys,

Recently I've been having problem with my MIcros POS 3.2 where database hangs or crashes. This may have something to do with nightly Sundays reboot as it mostly happens on Monday mornings. Basically the system says NO Communication with Database Server and the only way to fix it is to reboot the MIcros server again. I've noticed that very often there is Deployment.exe CMD window opened with stars in it but the process seems to be hanged and not deployment package is created. This has been happening for about month or so in my few locations. I can't recall any changes pushed down from our EM nor local. We haven't done any changes to autosequecnes for a few years. I found shown below pos3700 log entry. Does anyone have an idea what's going on and how to troubleshoot it?

Mon Aug 24 04:54:05 2015 | NTSERVER | AutoSeqServ | 8C4 | Autosequence 10243 step 5 of type X has begun. |
Mon Aug 24 04:54:05 2015 | NTSERVER | AutoSeqServ | 8C4 | Run Deployment - c:\MICROS\RES\EM\Bin\Deployment.exe |
Mon Aug 24 04:54:05 2015 | NTSERVER | Autosequence.DL | 8C4 | Failed to find AutoSeqServ registry. Trying to log MICROSSVC user |
Mon Aug 24 04:54:05 2015 | NTSERVER | Autosequence.DL | 8C4 | Unable to load the MICROSSVC user's profile settings. |
Mon Aug 24 04:54:05 2015 | NTSERVER | Autosequence.DL | 8C4 | ***ERROR*** Failed to locate the user profile for the MICROSSVC user. |
Mon Aug 24 04:54:05 2015 | NTSERVER | Autosequence.DL | 8C4 | Have you ever manually logged into the system as the MICROSSVC user? |
Mon Aug 24 04:54:05 2015 | NTSERVER | Autosequence.DL | 8C4 | Logon as the MICROSSVC user failed. |
Mon Aug 24 04:54:05 2015 | NTSERVER | Autosequence.DL | 8C4 | Creating the c:\MICROS\RES\EM\Bin\Deployment.exe process |
Mon Aug 24 04:55:00 2015 | NTSERVER | AutoSeqServ | 8C4 | Signalling automatic reload |
Mon Aug 24 04:56:00 2015 | NTSERVER | AutoSeqServ | 8C4 | Signalling automatic reload |
Mon Aug 24 04:56:12 2015 | NTSERVER | IFS | 7EC | Interface [CPN] No TCP/IP server name specified |
Mon Aug 24 04:57:00 2015 | NTSERVER | AutoSeqServ | 8C4 | Signalling automatic reload |
Mon Aug 24 04:58:00 2015 | NTSERVER | AutoSeqServ | 8C4 | Signalling automatic reload |
Mon Aug 24 04:59:00 2015 | NTSERVER | AutoSeqServ | 8C4 | Signalling automatic reload |
Mon Aug 24 05:00:00 2015 | NTSERVER | AutoSeqServ | 8C4 | Signalling automatic reload |
Mon Aug 24 05:00:00 2015 | NTSERVER | AutoSeqServ | 8C4 | Autosequence #10202 is still running! |
Mon Aug 24 05:01:00 2015 | NTSERVER | AutoSeqServ | 8C4 | Signalling automatic reload |
Mon Aug 24 05:01:12 2015 | NTSERVER | IFS | 7EC | Interface [CPN] No TCP/IP server name specified |
Mon Aug 24 05:02:00 2015 | NTSERVER | AutoSeqServ | 8C4 | Signalling automatic reload |
Mon Aug 24 05:03:00 2015 | NTSERVER | AutoSeqServ | 8C4 | Signalling automatic reload |
Mon Aug 24 05:04:00 2015 | NTSERVER | AutoSeqServ | 8C4 | Signalling automatic reload |
Mon Aug 24 05:05:00 2015 | NTSERVER | AutoSeqServ | 8C4 | Signalling automatic reload |
Mon Aug 24 05:06:00 2015 | NTSERVER | AutoSeqServ | 8C4 | Signalling automatic reload |
Mon Aug 24 05:06:12 2015 | NTSERVER | IFS | 7EC | Interface [CPN] No TCP/IP server name specified |
Mon Aug 24 05:07:00 2015 | NTSERVER | AutoSeqServ | 8C4 | Signalling automatic reload |

Mon Aug 24 08:07:01 2015 | NTSERVER | AutoSeqServ | 8C4 | Signalling automatic reload |
Mon Aug 24 08:08:01 2015 | NTSERVER | AutoSeqServ | 8C4 | Signalling automatic reload |
Mon Aug 24 08:09:01 2015 | NTSERVER | AutoSeqServ | 8C4 | Signalling automatic reload |
Mon Aug 24 08:10:01 2015 | NTSERVER | AutoSeqServ | 8C4 | Signalling automatic reload |
Mon Aug 24 08:11:01 2015 | NTSERVER | AutoSeqServ | 8C4 | Signalling automatic reload |
Mon Aug 24 08:11:12 2015 | NTSERVER | IFS | 7EC | Interface [CPN] No TCP/IP server name specified |
Mon Aug 24 08:12:01 2015 | NTSERVER | AutoSeqServ | 8C4 | Signalling automatic reload |
Mon Aug 24 08:12:10 2015 | PCWS02 | MDSHTTPTransprt | 55C | ** ERROR ** : HttpSendRequest() FAILED : LastErr = 12152 |
Mon Aug 24 08:12:11 2015 | PCWS02 | MDSBroker | 55C | ** ERROR ** : Call to MDSRESDBS->MDS_DbReadTmClkOhd() to Node NTSERVER Failed [ HTTP Send Request Failed ] |
Mon Aug 24 08:12:11 2015 | PCWS02 | OPS | 55C | Database call failed with fatal error C70700CC |
Mon Aug 24 08:13:01 2015 | NTSERVER | AutoSeqServ | 8C4 | Signalling automatic reload |
Mon Aug 24 08:13:32 2015 | PCWS01 | MDSHTTPTransprt | 55C | ** ERROR ** : HttpSendRequest() FAILED : LastErr = 12152 |
Mon Aug 24 08:13:32 2015 | PCWS01 | MDSBroker | 55C | ** ERROR ** : Call to MDSRESDBS->MDS_DbReadTmClkOhd() to Node NTSERVER Failed [ HTTP Send Request Failed ] |
Mon Aug 24 08:13:32 2015 | PCWS01 | OPS | 55C | Database call failed with fatal error C70700CC |
Mon Aug 24 08:14:01 2015 | NTSERVER | AutoSeqServ | 8C4 | Signalling automatic reload |
Mon Aug 24 08:15:01 2015 | NTSERVER | AutoSeqServ | 8C4 | Signalling automatic reload |


Mon Aug 24 09:06:17 2015 | NTSERVER | Autosequence.DL | 8C4 | Failed to create the c:\MICROS\RES\EM\Bin\Deployment.exe process[Process[c:\MICROS\RES\EM\Bin\Deployment.exe] returned error code [-1073741510]] |
Mon Aug 24 09:06:17 2015 | NTSERVER | AutoSeqServ | 8C4 | Autosequence 10243 step 5 of type X has encountered an external program error...Process[c:\MICROS\RES\EM\Bin\Deployment.exe] returned error code [-1073741510] |
Mon

 
Sort by date Sort by votes
Check what's going on with Autosequence #10202 first.
What steps are in the task, etc.
 
Upvote 0 Downvote
Same for what @dll5757 said about checking the Autosequnce number that is showing failed.
When the restarts happen, make sure the EOD isn't running or is finished; don't forget to properly shut the server down, by stopping all services and apps necessary.
 
Upvote 0 Downvote
The Autosequence 10202 is:
10202 Auto Every 1/2 Hour Posting
SP 116 Post Emploee Sales And Tracking
SP 114 Post Cashier Sales And Tracking
SP 133 Post Time Cards and Totals
SP 142 Post Time Period Totals
This was there for ever as well as reboot time. Why would this cause this issue now?
 
Upvote 0 Downvote
Did you recently update or upgrade your server(s)? New Workstations?

Looks like it has an issue with a Workstation, PCWS02.
Mon Aug 24 08:12:10 2015 | PCWS02 | MDSHTTPTransprt | 55C | ** ERROR ** : HttpSendRequest() FAILED : LastErr = 12152 |
Mon Aug 24 08:12:11 2015 | PCWS02 | MDSBroker | 55C | ** ERROR ** : Call to MDSRESDBS->MDS_DbReadTmClkOhd() to Node NTSERVER Failed [ HTTP Send Request Failed ] |
Mon Aug 24 08:12:11 2015 | PCWS02 | OPS | 55C | Database call failed with fatal error C70700CC |
Mon Aug 24 08:13:01 2015 | NTSERVER | AutoSeqServ | 8C4 | Signalling automatic reload |
 
Upvote 0 Downvote
Can you see the PCWS02 workstation? Is it online and communicating with the Server?
 
Upvote 0 Downvote
They are all now but when it happens, no register can communicate. They are pingable as well as we can vnc in. I tried restart some Micros revices but nothing works but full restart.
 
Upvote 0 Downvote
Does the connection drop at the same time during the day or is it at random times?
 
Upvote 0 Downvote
Well, our manager is coming to a location at 8am and the system is already down as they can't clock in or run any reports. There is a message on registers saying that there is no communication with DB and weather they want to enter backup or standalone mode.
 
Upvote 0 Downvote
This is sounding more like a network issue. Check all connections between the server and workstations. Check any Patch Panels, Switches and such. First step can be to replace cables for the server, then workstations.

When you are on the server can you ping your gateway or anything outside your network (Were you able to go online on the server, if not then disregard this)?

open up a command prompt (CTRL+R) and type CMD.
then type: ipconfig

Look for where it shows Default Gateway.
Then in the CMD window, type: ping [insert default gateway address]

If you can ping it, then the server isn't the issue, if you can't ping it then the server is the problem.
 
Upvote 0 Downvote
Yes, everything is pingable. If that was a network issue, it wouldn't occur right after reboot on Sunday and be fixable by restarting the Micros server. The system works just fine during the entire week but than it fails after Sunday's restart.
 
Upvote 0 Downvote
How soon after the restart does it happen?

Have you checked the System Event logs for errors during this time?
 
Upvote 0 Downvote
I did but nothing special there at least I found. It's hard to day how fast after because they restart it and go home. When they come, it is not working. All I could find is the POS log.
 
Upvote 0 Downvote
When they restart it, you said they do shut the system down properly correct, they Stop the services and everything right?

What time does your end of Day run?

Look for the 3700d.log (Res\Pos\Etc\).
You can also check the 3700d.log from the previous Sunday by looking in the archives folder.
[install-location]\MICROS\Res\Pos\archives. Open the one that is stamped with the next day.
Example: Business Date was 8/23/2015, the archive file will be named log_MICROSAPP_20150824.zip.
The site I am at, the End Of Day runs at 3am of the next day.


EDIT: Posted for the Wrong System. Made changes, 9700 to 3700 or Res 3.2.
 
Upvote 0 Downvote
I have 3700 so the logs are in a different directory. They are required to shut down it properly but whether they do it that's a good question. Yes, my EOD runs at 3am as well.
 
Upvote 0 Downvote
Make sure that they are not shutting it down during the EOD, this of course can cause issues. Also, they should stick around and wait for the server to start up and check it before leaving, making sure everything starts back up. Another note too, make sure it isn't coming up after the EOD start time. Some EOD autosequences run after others, so if the first one never kicks off because of the restart you could have issues.

Look through the System Event Viewer log, and look for 6006 (I believe thats the restart code). 1074 should show you Who and what initiated the restart and time. So you can gage the time the system is restarted, to rule out the possible issue above.
 
Upvote 0 Downvote
Is the database faulting out or you just getting the "No Comm" error?

If it's just the No Comm error it could be something with the MDSHTTP service shutting off and hanging as well.
 
Upvote 0 Downvote
Status
Not open for further replies.

Similar threads

R
  • Locked
  • Question
Micros database not starting
Replies
3
Views
432
Ronyad
R
robertosimphony
  • Locked
  • Question
MICROS Simphony Installation Error (Database section)
Replies
10
Views
796
mvelazquez
mvelazquez
M
Database query error in some rna report Simphony
Replies
2
Views
342
Mr.Pitt
M
LeonCL
  • Locked
  • Question
Micros RES 3700 Sample Database 1
Replies
5
Views
288
Andrew Miller
Andrew Miller
alrmd
  • Locked
  • Question
Allow a database to leave the EM client status
Replies
2
Views
346
jimmymcp02
jimmymcp02

Part and Inventory Search

Sponsor

Back
Top