| Event Id | 7000 |
| Source | Win NT 4.0 |
| Description | GNCFD service failed to start, system cannot find the file specified. |
| Event Information | This information from some newsgroups may help you: ------------------------------------------------------------------------------ This technote discusses the various Service Specific Error codes that can result when unsuccessfully starting the Dialogic services. The errors will appear in the NT Event Viewer. Following are the Service Specific Error Codes and what there most likely causes are. 1. initialization failed. 2. genload failed, typically caused by a memory address conflict A memory conflict can occur when a) the memory address board settings do match the settings in the dialogic.cfg file or the Dialogic Configuration Manager (DCM) b) another device in the system is using the same address c) the BIOS is not configured correctly. 3. copying user supplied VOXCFG and DTICFG failed (Win NT SR4.1 Release only). 4. genstart failed (failed to start generic driver), typically caused by an IRQ conflict. An IRQ conflict can occur when a) the IRQ settings do match the settings in the dialogic.cfg file or the Dialogic Configuration Manager (DCM) b) the BIOS is not configured correctly c) Dialogic service is dependent on devices GLOADDRV and GNCFD to be started prior to it being started. 5. dtistart failed 6. stadtifw failed 6. Error executing assignment program Dlgcdev\dialogic\bin\ sctsdtdx.exe (the sc bus timeslot mapping utility has failed) 7. nfascfg failed. |
| Reference Links |
Catch threats immediately
We work side-by-side with you to rapidly detect cyberthreats
and thwart attacks before they cause damage.