INI at start of Mids - PBX Info :: Your Free PBX, PABX and Telephone Information Resource

TopJimmy · 08-12-2003, 10:04 AM

Can anybody tell me what just happened here:

TIM010 02:00 12/8/2003 CPU 1

DROL000 DAILY ROUTINE BEGIN
NWS LD30 BEGIN 02:00 12/8/2003

INI000 0000002F 02 00 51 00000000 00000000 00000000 00000000 1 1 000000A9
DSET000 DOWN LOAD 0 0 0 0 0 0 0 20878
ACDR ACTIVATED

ERR5417 0000FFFF 00000400

AUD000

CIOD174 Directory /U0x8c63d42 is Corrupted. Please REINSTALL SOFTWARE
after using TOOLS MENU to INITIALIZE Unprotected Partition.

CIOD174 Directory /U0x8c63d42 is Corrupted. Please REINSTALL SOFTWARE
after using TOOLS MENU to INITIALIZE Unprotected Partition.

SRPT731 OS 1: Warm Start
Release: x112508
Created: Monday June 26 14

53 EDT 2000
Last Cold Start: 0/0/00 0:43:07 (from '/flash/flashos')

SRPT751 INI 1: starting INI on side 1 due to System Restart
Previous INI: side 1 at 0/ 0/00 00:45:28
INIs since switch-over (11/ 8/03 02:05:37): 0, 1

SRPT752 INI 1: INI completed in 12 seconds

DTC001

TIM010 02:15 12/8/2003 CPU 1

This occurred on an 81C running Rls 25.08. I was hoping someone can help me decipher these messages and tell me if I got a major problem. The midnight routines never ran for last night. Should I at least run a datadump. Please help. :casstet:

Rachelle · 08-12-2003, 11:31 AM

In my NTP's I can't find the fault code 2f nor can I locate the CIOD174. These codes aren't in the release 25 books that I have access to. Anyone else have any better luck on this one?

rlc

TopJimmy · 08-12-2003, 02:16 PM

Help!!! Can anyone tell me if this needs immediate attention? If I run Mids, will that clear things up? Somebody has have some insight. I can't get any info on the CIOD errors.

ABabbitt · 08-12-2003, 02:45 PM

TJ,
Go ahead and try to run BKO and EDD. I wouldn't run mids in the middle of the workday if you are getting those errors. Call your vendor and have them check it out. Reinstall software doesn't sound like a good thing.

AB

jack · 08-12-2003, 05:02 PM

I've not been able to decipher these either but agree that it would certainly make sense to engage your vendor ASAP.

Jack

dixiedogger · 08-13-2003, 12:56 AM

most likley you need to reinstall the software as the message says I hope you keep periodic backups in case you have to go back a few days before the corruption occured.

TopJimmy · 08-13-2003, 11:08 AM

I contacted my vendor and he suggested running the MID's during an off-peak time and see if the CIOD errors come back. I waited till the end of the day and ran MID's again thru LD135. Sure enough, the errors were there again.
So I call my vendor back up and told him the news. He called ETAS and they suggested a SYSLOAD. "That should clear things up", they said. If not, ETAS said the OS would have to be reloaded.
So I crossed my fingers and did a SYSLOAD! And it worked! According to ETAS the corrupt data was in the UDATA area and the SYSLOAD wrote over it with PDATA.
Bottom line: the switch seems fine. No more error messages. Thanks everyone for your suggestion.

Thread Tools
Show Printable Version Email this Page
Display Modes
Linear Mode Switch to Hybrid Mode Switch to Threaded Mode

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
INI Fault Code question	Rachelle	Meridian Systems	7	06-06-2006 08:41 AM
X UTK Ground start trunks problem	lopeztcom	Meridian Systems	3	06-14-2005 08:32 AM
IP Agent was unable to start the Avaya iClarity IP Audio Pro	ITMANDOTCA	Definity Support	2	12-02-2004 04:03 PM
Ground start trunks causing ports to stay permanently busy	justice	Meridian Systems	7	02-19-2003 12:31 PM
loop or ground start	rex	Meridian Systems	5	01-22-2003 01:37 PM

Currently Active Users Viewing This Thread: 1 (0 members and 1 guests)