Issue is owstimer.exe is consuming 100% CPU. After using process explorer and filemon tools i can understand following things.1. In OWSTIMER.exe process one module "ADVAPI32.dll!LookupPrivilegeValueW" is consuming max CPU. See attached imagehttp://4.bp.blogspot.com/_-m7rJPvQsSE/SWwt3Xt49YI/AAAAAAAAEG4/P0-2c-f8nAE/s1600/owstimer_CPU.PNG2.In filemon OWSTIMER.EXE is trying to load one dll i.e. DBmsLPCn.dll but unable to load. See imagehttp://2.bp.blogspot.com/_-m7rJPvQsSE/SWwt3X3ObYI/AAAAAAAAEGw/PC3IMyv8A7U/s1600/owstimer.PNGIf i suspend "ADVAPI32.dll!LookupPrivilegeValueW" using process explorer, then filemon doesn't show up any error.More info on Envt:-#An VPC Image downloaded from Microsoft site http://www.microsoft.com/downloads/details.aspx?FamilyID=1beeac6f-2ea1-4769-9948-74a74bd604fa&DisplayLang=en#Installed MOSS 2007 and SP1 on VPC image#Service accounts are domain (earlier it was local)Please help!

Hi, Dose this occur when you change the date/time of the system clock. If so, this is a known issue that Timer service consuming excessive CPU cycles in virtualized environment after change the date of the system clock, but currently we do not have a hotfix to resolve it. You can work around this issue by restarting the timer service after adjusting the date and time. Let me know if I misunderstand you. Xue-Mei Chang

Yes we have changed Time-Zone (not time) from US to IST..........after restarting.. for a while owstimer.exe CPU consumption is nill... but after few mins it again takes up 100%.....Just a question, do we need to do something in SQL Server 2005 also after changing machine name.....??As you see in second image.. OWSTIMER.exe is looking for some dll.. i.e. dbmslpcn.dll.... and its not able to find....what is the use of "ADVAPI32.dll!LookupPrivilegeValueW"??? if i suspend this module using process exporer..then CPU use comes to normal...

How does your "owstimer.exe.config" file look like?

Where will i find this owstimer.exe.config.. i have searched all drives... but not able to find....??

Hi MarshalDon't think its your problem then.Have had some strange problems with custom owstimer.exe.config files before. Thought that might be youproblem, but guess not.It's under the BIN folder in the 12 hive.

Hello Henrik,we do not have this owstimer.exe.config under 12 hive BIN folder....am bit surpised.....still problempersist..... :(Marshal

Hiyou only have it if you have created a "custom Timer Job" thought that might have been the problem.But now that you dont have the file, its not the problem :)

Does the"Timer Job Status" page report any problems with the jobs?

Just finally fixed this issue on my servers. Ended up being .net updates. Not sure which version but I installed 3.5 sp1 and all updates regarding .net via windows update and my issue went away. was getting 100% CPU on owstimer.exe process if I had the "Workflow" Timer Job turned on in SharePoint.