Article ID: 271970
Article Last Modified on 11/1/2006
APPLIES TO
- Microsoft Windows NT Services for UNIX Add-On Pack
This article was previously published under Q271970
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:
CAUSE
Cron.exe generates an access violation because of an insufficient error message buffer and resultant data corruption.
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:
282858 Cron Jobs Stop Running
STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.
Keywords: kbhotfixserver kbqfe kbenv kberrmsg kbprb kbqfe KB271970
