We’re running MOSS 2007 on Server 2003 Enterprise R2 but I’m not sure a lot of that matters in this case. We have several workflows set up and one day they just stopped working. Not just on one site collection but all site collections. When ran it would simply say the workflow failed to start or failed to run.
Here are the event viewer errors we were getting:
Source: Windows SharePoint Services 3
Event ID: 5289
Description: Registry error reading Perfmon configuration.
Source: W3CTRS
Event ID: 2002
Description: Setting up Web Service counters failed, please make sure your Web Service counters are registered correctly.
Source: Perflib
Event ID: 1023
Description: Windows cannot load extensible counter DLL TermService, the first DWORD in data section is the Windows error code.
Source: IISInfoCtrs
Event ID: 1001
Description: Unable to read the first counter index value from the registry. The error code returned by registry is data DWORD 0.
The first thing you should check is to see if the SharePoint and Windows Workflow Foundation performance counters are available in perfmon. To do this simply open a run prompt and type in perfmon. Then drop down “Performance Logs and Alerts” and click on “Counter Logs”. Right Click on “System Overview” and go to Properties. (see image below)
Once you’ve got that screen open click on the “Add Counters” button and drop down the “Performance Object” list. Your list should resemble the list below, having SharePoint objects as well as the last one, Windows Workflow Foundation.
If they are not there it could be several things. I would try reloading the performance counters first by doing the following:
1. Open a command prompt and navigate to C:\WINDOWS\Microsoft.NET\Framework\v3.0\Windows Workflow Foundation
2. type in lodctr perfcounters.ini and press enter (you can also try lodctr /r)
If you get any messages like “Unable to open driver SYSTEM\CurrentControlSet\Services\w3ctrs.ini. Status: 2 then we’ll have to try the next step. This usually means .NET Framework could possibly be corrupted. Next I would try the .NET hotfix located here:
Download the appropriate one for your system and try it out. You will have to reboot when finished.
If this doesn’t fix it you will most likely have to reinstall .NET Framework. I personally didn’t want to do that so I reverted my web front end server to an earlier image of the machine. This will work fine if you have a complete image and the SQL installation is on a separate machine. You will not lose any data since everything except newly created site collections are stored in SQL. If SQL is on the same box you will lose any data from the date of the image.
If you decide to reinstall .NET then once you have it reinstalled you should be able to do an iisreset and see if your sites are back up. Once you have reinstalled .NET install the same hotfix referenced above:
Next you’ll want to perform the lodctr from the directory mentioned above (C:\WINDOWS\Microsoft.NET\Framework\v3.0\Windows Workflow Foundation) and run lodctr perfcounters.ini.
Go back into perfmon and make sure your counters are there and your workflows are functioning properly.
Hope this helps!
SharePoint Expert's Blog for Noobs 
really cool
September 7, 2012 at 5:33 AM
I have been browsing online more than 3 hours these days, but I by no means discovered any interesting article like yours.
It’s pretty price enough for me. Personally, if all site owners and bloggers made excellent content material as you probably did, the web will probably be much more helpful than ever before.
Rachaels Printable Daily Coupons
April 9, 2013 at 10:51 PM
This blog was… how do you say it? Relevant!! Finally I’ve found something which helped me. Kudos!