RE: Assert Failed on NT system

Posted in 2000

Murray Wood — Wed, 5 Jan 2000 14:38:59 +1300 — source: , line -1, thread 9, proc id 276, No Exception Handler.@@NL@@14:33:31 PANIC: Attempting to bring system down@@NL@@@@NL@@Then from the above af. file:@@NL@@@@NL@@C:\\Informix\\bin\\onstat -g dis:@@NL@@@@NL@@Informix Dynamic Server Version 7.31.TC2 -- On-Line -- Up 03:24:52 --@@NL@@10944 Kbytes@@NL@@There are 2 servers found@@NL@@Server : CurrentVersion@@NL@@Server Number : -1@@NL@@Server Type : Unknown@@NL@@Server Status : Down@@NL@@Server Version: <Unknown>@@NL@@Shared Memory : 0xffffffff@@NL@@INFORMIXDIR : <Unknown>@@NL@@ONCONFIG : <Unknown>@@NL@@SQLHOSTS : <Unknown>@@NL@@Host : <Unknown>@@NL@@@@NL@@Server : foley_map@@NL@@Server Number : 0@@NL@@Server Type : IDS@@NL@@Server Status : Up@@NL@@Server Version: Informix Dynamic Server Version 7.31.TC2@@NL@@Shared Memory : 0xc000000@@NL@@INFORMIXDIR : C:\\Informix@@NL@@ONCONFIG : C:\\Informix/etc/ONCONFIG@@NL@@SQLHOSTS : \\\\NTSERV@@NL@@Host : ntserv@@NL@@@@NL@@There are two problems here -@@NL@@ 1) I cannot find the command - C:\\Informix\\bin\\onstat -g dis: in the books@@NL@@but it works.@@NL@@ 2) There is only one server on this system@@NL@@@@NL@@I think if I could remove the first server the problem may go away.@@NL@@Comments?@@NL@@@@NL@@Thanks@@NL@@Dave

There are more details at the Techinfo center. http://www.informix.com/informix/services/ilink/alerts/123099_117981.htm The case notes say that this only happens when a "DNS/router problems which result in unreliable domain name resolution." is used. WORKAROUND A potential workaround for this problem is to ensure TCP host name resolution from client connections is handled by DNS and returns the fully qualified domain name for each client machine that connects to the server. The problem can still occur in the event of a DNS/router problem which causes name resolution to omit the domain name. Configure the server machine to use DNS for TCP name resolution. This step assumes a suitable DNS server is available on the network. Edit the Windows NT hosts file on the server machine: %windir%\\system32\\drivers\\etc\\hosts Remove all entries from this file except the following: 127.0.0.1 localhost Murray Wood -----Original Message----- From: owner-informix-list@iiug.org [mailto:owner-informix-list@iiug.org]On Behalf Of Dave Osmon Sent: Wednesday, January 05, 2000 11:29 AM To: informix-list@iiug.org Subject: Assert Failed on NT system Normally I just lurk and learn and I have opened an Informix case on this. So far Informix has said : Bug #117981 Description: Customers have reported cases of listener thread and msc vp thread crashes. The actual function that causes the access violation is in NT's system dll's. Fixed in version 7.31.TC5 - but it will take some time to get the software. What bothers me is in the af file. We are on NT 4.0 SP5 running 7.31.TC2 - here is the failure: 14:32:42 Assert Failed: No Exception Handler 14:32:42 Informix Dynamic Server Version 7.31.TC2 14:32:42 Who: Session(8398, informix@, 0, 0) Thread(9, soctcplst, 0, 1) Exception at Addr: 0x69b4f2, TOS: 0xc4eb848, FP:0xc4eb84c, Exc: c0000005 14:32:42 Results: Exception Caught. Type: MT_EX_OS, Context: mem 14:32:42 Action: Please notify Informix Technical Support. 14:33:10 See Also: af.3f1f95a, shmem.3f1f95a.0 14:33:29 \