Take the 2-minute tour ×
Server Fault is a question and answer site for professional system and network administrators. It's 100% free, no registration required.

I have a user that needs to be logged in for nightly automation to work correctly. The setup is as follows:

Scheduled task launches an RDP session @ 7:00 pm every night just to ensure an interactive desktop is open for the automation Automation processes start @ 8:00 pm and finish @ 11:00 pm After all is done, our invoices are mailed/faxed out

Now here's the strange part

when this started failing, I started getting these security audit failures telling me that the "closeforday" user isn't a user, and the RDP session fails to start, causing our interactive session to fail.

If I go and run the RDP session manually (saved in an .rdp file), the connection starts up OK - no credential issues

If I start the task manually (i.e. right-click and run from task scheduler) it fails

If the task is triggered, it fails

If I use a different username to launch the task, manually or triggered, it starts OK

I have deleted and re-created the tasks to ensure that the saved passwords weren't being corrupted, and when I create the task it accepts my username/password for the close account

So my question is: Why would I be getting these errors? Everything appears to be set up correctly, and no changes were made when this started failing. This is seriously causing my organization problems, and both myself and my software vendor are stumped. Any ideas would be greatly appreciated!

An account failed to log on. Subject: Security ID: SYSTEM Account Name: DR-VTS2$ Account Domain: DIAMOND Logon ID: 0x3e7 Logon Type: 2 Account For Which Logon Failed: Security ID: NULL SID Account Name: closeforday Account Domain: DR-VTS2 Failure Information: Failure Reason: Unknown user name or bad password. Status: 0xc000006d Sub Status: 0xc0000064 Process Information: Caller Process ID: 0x218 Caller Process Name: C:\Windows\System32\winlogon.exe Network Information: Workstation Name: DR-VTS2 Source Network Address: 127.0.0.1 Source Port: 0 Detailed Authentication Information: Logon Process: User32 Authentication Package: Negotiate Transited Services: - Package Name (NTLM only): - Key Length: 0

share|improve this question

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Browse other questions tagged or ask your own question.