SYMPTOMS
The Cron service may stop unexpectedly after some jobs have been started.
When this occurs, the Cron service reports
CreateNamedPipe error 2 or 231. Typically, the Event log records an entry similar to the following message:
Event Type: Error
Event Source: CronService
Event Category: None
Event ID: 1001
Date: 8/5/2000
Time: 8:57:49 AM
User: N/A
Computer: LC2-LFD10
Description: Cron Service Win32 API CreateNamedPipe failed with the error 2
RESOLUTION
A supported hotfix is now available from Microsoft, but it is only intended to correct the problem that this article describes. Apply it only to systems that are experiencing this specific problem.
To resolve this problem, contact Microsoft Product Support Services to obtain the hotfix. For a complete list of Microsoft Product Support Services telephone numbers and information about support costs, visit the following Microsoft Web site:
Note In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question.
The English version of this fix should have the following file attributes or later:
Date Time Version Size File name Platform
--------------------------------------------------------------
12/11/2000 05:08p 5.1999.922.2 176,640 Cron.exe Intel
For additional information, click the article number below
to view the article in the Microsoft Knowledge Base: