Author Topic: Failure to launch 'event 203' & failure to run 'event 103' task scheduler Win 7  (Read 22954 times)

0 Members and 1 Guest are viewing this topic.

Offline aztony

  • PcWinTech Jr. Member
  • Join Date: Apr 2013
  • Posts: 2
  • Karma: 0
Hi,
I am having an issue which I discovered last nite whereby CleanMem is unable to run at its 15 minutes interval. I get this error, "handle is invalid 0x80070006 . Here are the details from task scheduler's history:

   System-Provider

   [ Name]  Microsoft-Windows-TaskScheduler
   [ Guid]  {DE7B24EA-73C8-4A09-985D-5BDADCFA9017}
 
   EventID 203
 
   Version 0
 
   Level 2
 
   Task 203
 
   Opcode 101
 
   Keywords 0x8000000000000000
 
  - TimeCreated

   [ SystemTime]  2013-04-11T20:35:20.866700000Z
 
   EventRecordID 22898
 
  - Correlation

   [ ActivityID]  {A45E81B8-BC45-40EE-8732-64367E897456}
 
  - Execution

   [ ProcessID]  5224
   [ ThreadID]  1700
 
   Channel Microsoft-Windows-TaskScheduler/Operational
 
   Computer Custodian
 
  - Security

   [ UserID]  S-1-5-18
 

- EventData

  TaskName \Clean System Memory
  TaskInstanceId {A45E81B8-BC45-40EE-8732-64367E897456}
  ActionName C:\Windows\system32\CleanMem.exe
  ResultCode 2147942406

-------------------------------------------------------------------------------
 System-Provider

   [ Name]  Microsoft-Windows-TaskScheduler
   [ Guid]  {DE7B24EA-73C8-4A09-985D-5BDADCFA9017}
 
   EventID 103
 
   Version 0
 
   Level 2
 
   Task 103
 
   Opcode 102
 
   Keywords 0x8000000000000001
 
  - TimeCreated

   [ SystemTime]  2013-04-11T20:35:20.866700000Z
 
   EventRecordID 22899
 
  - Correlation

   [ ActivityID]  {A45E81B8-BC45-40EE-8732-64367E897456}
 
  - Execution

   [ ProcessID]  5224
   [ ThreadID]  1700
 
   Channel Microsoft-Windows-TaskScheduler/Operational
 
   Computer Custodian
 
  - Security

   [ UserID]  S-1-5-18
 

- EventData

  TaskName \Clean System Memory
  InstanceId {A45E81B8-BC45-40EE-8732-64367E897456}
  UserContext TONY'S\CUSTODIAN$
  ResultCode 2147942406

Also see attached screenshot. Would appreciate any help, as everything I have tried to resolve has not worked. My system is 32bit
« Last Edit: April 11, 2013, 02:16:51 PM by aztony »

PcWinTech.com Forums


Offline Shane

  • Top Geek, err uh Dog.
  • PcWinTech Administrator
  • PcWinTech Guru
  • *******
  • Join Date: Jul 2008
  • Posts: 16,846
  • Location: USA
  • Karma: 523
  • "Knowledge should be shared not hidden."
(My weekends belong to my wife and kids, I will try my best to answer all posts daily during the work week)

(About Shane)
Site Owner, Top Admin, Lead Programmer, Wife & 5 kids, Needs a lot more coffee.

When people ask "Why fix what isn't broken?" I reply "To make it better."
"Only a life lived for others is a life worthwhile"
Honor & Respect is all that matters.

Owner & Programmer of: www.pcwintech.com & www.tweaking.com

Offline aztony

  • PcWinTech Jr. Member
  • Join Date: Apr 2013
  • Posts: 2
  • Karma: 0
Quote
See if this helps :wink:

Thanks for the reply. Following the instructions provided with the link did not work for me. Moreover, the issue as pointed out there had to do with password(s) being changed, thereby causing the problem. There has been no password changes on my systems. I've been using CleanMem for a couple years on an XP desktop without issue. It's my Win 7 desktop which has been running CleanMem for about 3 wks that is the problem. After a couple of wasted hours trying to resolve I am now giving MZ Ram a test drive. 

Offline Shane

  • Top Geek, err uh Dog.
  • PcWinTech Administrator
  • PcWinTech Guru
  • *******
  • Join Date: Jul 2008
  • Posts: 16,846
  • Location: USA
  • Karma: 523
  • "Knowledge should be shared not hidden."
The problem isn't with cleanmem, it is something with the task scheduler. Did you try deleting the schedule and remaking it?

Cleanmem runs on over 1 million machines, from every version of Windows from xp to 8 and all servers. The error is coming from the task scheduler not cleanmem. A lot of times when ever I have trouble with a task scheduler I just need to delete the task. On some other machines there was a security issues with it and I found a fix for that and that got task scheduler working. But that error kept every task in the task scheduler from working :wink:

Also on a side note, alot of the other memory cleaners out there simply copied what cleanmem does with the API. But they dont do something else that I do, you will see Cleanmem can clean out of more processes then they can :-)

Anyways, need anything else let me know.

Shane
(My weekends belong to my wife and kids, I will try my best to answer all posts daily during the work week)

(About Shane)
Site Owner, Top Admin, Lead Programmer, Wife & 5 kids, Needs a lot more coffee.

When people ask "Why fix what isn't broken?" I reply "To make it better."
"Only a life lived for others is a life worthwhile"
Honor & Respect is all that matters.

Owner & Programmer of: www.pcwintech.com & www.tweaking.com

Offline Willy2

  • PcWinTech Full Member
  • **
  • Join Date: Jul 2010
  • Posts: 278
  • Karma: 7
One more confirmation that the Win 7 Task Scheduler is (more than) a bit "buggy". As long as one doesn't fiddle with it, all is OK. But once the user starts to meddle with Win 7, problems & errors (can) surface.

E.g. One task is reported in Piriform's CCleaner but it doesn't show up in Task Scheduler. Weird.

PcWinTech.com Forums


 

email