Windows scheduled task last result 0x80
Join our site today to ask your question. This site is completely free -- paid for by advertisers and donations. If you're not already familiar with forums, watch our Welcome Guide to get started.
Join over , other people just like you! Forums New posts Search forums. What's new New posts Unanswered threads Latest activity.
Members Current visitors. Log in Sign up. Search titles only. Search Advanced search…. New posts. Search forums. Log in. Sign up. Computer problem? Tech Support Guy is completely free -- paid for by advertisers and donations.
Click here to join today! JavaScript is disabled. But if that user is logged out, the task will get the 0x80 error. My scheduled task was running with a specific system user account.
Please start a New Thread if you're having a similar issue. View our Welcome Guide to learn how to use this site. The Human Interface Device Access service is disabled. Please no email replies - reply in newsgroup. When we restart the server everthing is fine. Are you looking for the solution to your computer problem? This of course broke the macro. Stack Overflow for Teams — Collaborate and share knowledge with a private group.
Create a free Team What is Teams? Collectives on Stack Overflow. Learn more. Asked 8 years, 10 months ago. Active 8 years ago. Viewed 2k times. EXE Note this database file lives on a network drive. Why is this task failing? Jason Strimpel Jason Strimpel XP Scheduler returns "Last Result" 0x Forums Software Windows Legacy. JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding. Previous Next. Guest Guest. Archived from groups: microsoft.
I am trying to schedule an Event, using the XP Scheduler. I want this scheduled event to run, even when i am logged off, something that does not happen in one specific PC. We have many pc's in the company, one of them is a DB Server. The Last Result column has a value of 0x80 some kind of error code , instead of 0x0 which appears on all other PC's after a successfull run.
Has anybody seen this problem before? Is it a hardware or BIOS problem? Is there a workaround for this? I searched a lot online, but no luck so far Regards, John. If that is a Win 32 error code it means There are no child processes to wait for. However it is the program that is returning the code. EG Norton chosse 42 to mean OK though the whole world apart from norton uses 0.
It may not signify an error either.
0コメント