From: Adrian Grigorof on 3 Aug 2006 14:02 Please read the comments for these events at www.eventid.net: 1219: http://www.eventid.net/display.asp?eventid=1219&eventno=2848&source=Winlogon&phase=1 1000: http://www.eventid.net/display.asp?eventid=1000&eventno=970&source=Userinit&phase=1 2001: http://www.eventid.net/display.asp?eventid=2001&eventno=730&source=Perfdisk&phase=1 -- Adrian Grigorof www.eventid.net <sguitardude(a)gmail.com> wrote in message news:1154626173.319300.128840(a)i42g2000cwa.googlegroups.com... > Greetings, > I am receiving these errors on multiple servers in Windows 2003 > Terminal Servers farm. It seems that either a network connectivity or > resource issue causes problems with profiles being created properly. > Any ideas? > > If anybody knew what the following line means, it would be helpful: > Not enough resources are available to complete this operation. > > Event Type: Error > Event Source: Winlogon > Event Category: None > Event ID: 1219 > Date: 8/3/2006 > Time: 7:47:45 AM > User: N/A > Computer: <computername> > Description: > Logon rejected for <domain>\<username>. Unable to obtain Terminal > Server User Configuration. Error: Not enough resources are available to > complete this operation. > > Event Type: Error > Event Source: UserInit > Event Category: None > Event ID: 1000 > Date: 8/3/2006 > Time: 7:51:28 AM > User: N/A > Computer: <computername> > Description: > Could not execute the following script logoff.cmd. The system cannot > find the file specified. > . > Event Type: Warning > Event Source: PerfDisk > Event Category: None > Event ID: 2001 > Date: 8/3/2006 > Time: 7:54:12 AM > User: N/A > Computer: <computername> > Description: > Unable to read the disk performance information from the system. Disk > performance counters must be enabled for at least one physical disk or > logical volume in order for these counters to appear. Disk performance > counters can be enabled by using the Hardware Device Manager property > pages. The status code returned is in the first DWORD in the Data > section. >
|
Pages: 1 Prev: the local policy does not permit you to login interactively Next: spooler hang. again |