Sharepoint 2007 Workflow problem

John_Mc

Hi,

I deactivated the Routing Workflows feature in Site Collection features, and then reactivated it having realised I deactived the wrong feature. Now whenever my users try to submit pages for approval (this is a publishing site), the parrallel approval gives this error :

"The workflow failed to start due to an internal error."

I've tried an IIS reset and a server restart but the problem still remains. Anyone have any suggestions for solving this show stopping bug?

Thanks,
John

stevenmu

My guess would be that the pages library is referring to specific workflow id that would have been deleted when you disabled routing workflows.

Not sure if you can do this or not, and equally not sure if it would screw something up even worse (so take a good backup if you're going to try it, at you own risk etc), but if you go to the settings for the pages library I think you should be able to turn off approval and then turn it back on again.

John_Mc

stevenmu wrote: »

My guess would be that the pages library is referring to specific workflow id that would have been deleted when you disabled routing workflows.

Not sure if you can do this or not, and equally not sure if it would screw something up even worse (so take a good backup if you're going to try it, at you own risk etc), but if you go to the settings for the pages library I think you should be able to turn off approval and then turn it back on again.

Hi Steven,

Thanks a lot for your reply, and sorry for the delay but I was out of the country. Unfortunately, that didn't work.

Would you have any other suggestions?

FindingNemo

have you tried

lodctr c:\Windows\Microsoft.Net\Framework\v3.0\Windows Workflow
Foundation\perfcounters.ini

Ginger

Go into the 12 hive (namely C:\Program Files\Common Files\Microsoft Shared\Web Services\12) and look at the error logs. It will tell you why the workflow failed to start.

Once you have the error code, you should be able to find out why it didnt start

John_Mc

FindingNemo wrote: »

have you tried

lodctr c:\Windows\Microsoft.Net\Framework\v3.0\Windows Workflow
Foundation\perfcounters.ini

Yeah I tried resetting the counters but no luck

The Logs are huge in size, and I'm having great difficulty locating the problem in them. It'd be great if the logs contained only errors, and not every action being performed!

Ginger

Search for WorkFlow in the logs, that should limit it to what you need...

John_Mc

Ginger wrote: »

Search for WorkFlow in the logs, that should limit it to what you need...

Yep tried that but to no avail. I also recorded the time I started an approval workflow and checked that time in the logs but there's nothing there.

Ginger

Is the workflow giving a failed to start error? Then you should be able to find it in the logs using that string...

John_Mc

Ginger wrote: »

Is the workflow giving a failed to start error? Then you should be able to find it in the logs using that string...

Yes it was, but I've disabled the approval workflow because my client needed to add new content. Will turn it on again and see if I can track it down, thanks for the help - much appreciated!

Ginger

Once you get the source of the error, post it here and we can take a look for you

John_Mc

Ginger wrote: »

Once you get the source of the error, post it here and we can take a look for you

There's nothing in the Logs about the error. I reactivated the approval workflow but it's still giving the error.

Here's an extract from the Log files which may indicate the error, but I can't make out what it is...

12/12/2007 09:55:16.98 	w3wp.exe (0x5A18)                       	0x65DC	CMS                           	Publishing                    	7fz3	Medium  	Setting [Display] as the FormContext.FormMode for the current page	acb0244a-7541-42b6-8cbd-298aae270602
12/12/2007 09:55:16.98 	w3wp.exe (0x5A18)                       	0x65DC	CMS                           	Publishing                    	7fz3	Medium  	Setting [Display] as the FormContext.FormMode for the current page	acb0244a-7541-42b6-8cbd-298aae270602
12/12/2007 09:55:16.98 	w3wp.exe (0x5A18)                       	0x65DC	CMS                           	Publishing                    	7fz3	Medium  	Setting [Display] as the FormContext.FormMode for the current page	acb0244a-7541-42b6-8cbd-298aae270602
12/12/2007 09:55:16.98 	w3wp.exe (0x5A18)                       	0x65DC	CMS                           	Publishing                    	7fz3	Medium  	Setting [Display] as the FormContext.FormMode for the current page	acb0244a-7541-42b6-8cbd-298aae270602
12/12/2007 09:55:16.98 	w3wp.exe (0x5A18)                       	0x65DC	CMS                           	Publishing                    	7fz3	Medium  	Setting [Display] as the FormContext.FormMode for the current page	acb0244a-7541-42b6-8cbd-298aae270602
12/12/2007 09:55:17.21 	w3wp.exe (0x5A18)                       	0x0CD8	CMS                           	Publishing                    	8zug	Medium  	PublishingHttpModule.Init() calling AppDomainUnloadListener.Register()	 
12/12/2007 09:55:17.21 	w3wp.exe (0x5A18)                       	0x0CD8	CMS                           	Publishing                    	8x0a	High    	AppDomainUnloadListener.RegisterSelf() entered lock(this=32347029)	 
12/12/2007 09:55:17.76 	Microsoft.Office.Server.Convers (0x04A4)	0x66F8	Document Conversions          	Load Balancer Service         	7jhf	Medium  	RegisterLauncher called with uri http://WSUS:8082/HtmlTrLauncher	 
12/12/2007 09:55:18.57 	w3wp.exe (0x5F14)                       	0x4218	SharePoint Portal Server      	Runtime                       	8gp7	Medium  	Topology cache updated. (AppDomain: /LM/W3SVC/240621585/Root-1-128419009329146054)	 
12/12/2007 09:55:20.65 	w3wp.exe (0x5A18)                       	0x0CD8	CMS                           	Publishing                    	7fz3	Medium  	Setting [Display] as the FormContext.FormMode for the current page	 
12/12/2007 09:55:20.65 	w3wp.exe (0x5A18)                       	0x0CD8	CMS                           	Publishing                    	7fz3	Medium  	Setting [Display] as the FormContext.FormMode for the current page	 
12/12/2007 09:55:20.65 	w3wp.exe (0x5A18)                       	0x0CD8	CMS                           	Publishing                    	7fz3	Medium  	Setting [Display] as the FormContext.FormMode for the current page	 
12/12/2007 09:55:20.65 	w3wp.exe (0x5A18)                       	0x0CD8	CMS                           	Publishing                    	7fz3	Medium  	Setting [Display] as the FormContext.FormMode for the current page	 
12/12/2007 09:55:20.65 	w3wp.exe (0x5A18)                       	0x0CD8	CMS                           	Publishing                    	7fz3	Medium  	Setting [Display] as the FormContext.FormMode for the current page	 
12/12/2007 09:55:20.85 	w3wp.exe (0x5A18)                       	0x0CD8	Forms Server                  	Forms Services Runtime        	0	Medium  	Regenerating object: ProcessId:[6] CacheId: IpfsSolution::meta:1278226c-ae7c-4ea0-9ce2-d3dd084c8c19:ver:12.0.0.1	 
12/12/2007 09:55:20.85 	w3wp.exe (0x5A18)                       	0x0CD8	Forms Server                  	Forms Services Runtime        	0	Medium  	Object is not in Cache. ProcessId:[6] CacheId: IpfsSolution::soln:1278226c-ae7c-4ea0-9ce2-d3dd084c8c19:ver:12.0.0.1	 
12/12/2007 09:55:20.85 	w3wp.exe (0x5A18)                       	0x0CD8	Forms Server                  	Forms Services Runtime        	0	Medium  	Entering Locked region: ProcessId:[6] CacheId: IpfsSolution::soln:1278226c-ae7c-4ea0-9ce2-d3dd084c8c19:ver:12.0.0.1	 
12/12/2007 09:55:20.85 	w3wp.exe (0x5A18)                       	0x0CD8	Forms Server                  	Forms Services Runtime        	0	High    	Regenerating object: ProcessId:[6] CacheId: IpfsSolution::soln:1278226c-ae7c-4ea0-9ce2-d3dd084c8c19:ver:12.0.0.1	 
12/12/2007 09:55:20.87 	w3wp.exe (0x5A18)                       	0x0CD8	Forms Server                  	Forms Services Runtime        	0	Medium  	Finished cache object creation: ProcessId:[6] CacheId: IpfsSolution::soln:1278226c-ae7c-4ea0-9ce2-d3dd084c8c19:ver:12.0.0.1	 
12/12/2007 09:55:20.87 	w3wp.exe (0x5A18)                       	0x0CD8	Forms Server                  	Forms Services Runtime        	0	Medium  	Exiting Locked region: ProcessId:[6] CacheId: IpfsSolution::soln:1278226c-ae7c-4ea0-9ce2-d3dd084c8c19:ver:12.0.0.1	 
12/12/2007 09:55:20.88 	w3wp.exe (0x5A18)                       	0x0CD8	CMS                           	Publishing                    	8ztg	Medium  	Got List Item Version, but item was null.	b43fad59-482f-491a-bfc3-b0f3437a8c92
12/12/2007 09:55:20.93 	w3wp.exe (0x5A18)                       	0x0CD8	Forms Server                  	Forms Services Runtime        	0	Medium  	Regenerating object: ProcessId:[6] CacheId: SiteFeatures_292199bf-034e-4374-8d11-985471b4ae16	b43fad59-482f-491a-bfc3-b0f3437a8c92
12/12/2007 09:55:20.93 	w3wp.exe (0x5A18)                       	0x0CD8	Windows SharePoint Services   	General                       	0	Medium  	Potentially excessive number of SPRequest objects (9) currently unreleased on thread 6.  Ensure that this object or its parent (such as an SPWeb or SPSite) is being properly disposed.  Allocation Id for this object: {F3E642EB-1827-48AA-BDCA-694087BB8581} Stack trace of current allocation:    at Microsoft.SharePoint.SPRequestManager.Add(SPRequest request, Boolean shareable)     at Microsoft.SharePoint.SPGlobal.CreateSPRequestAndSetIdentity(Boolean bNotGlobalAdminCode, String strUrl, Boolean bNotAddToContext, Byte[] UserToken, String userName, Boolean bIgnoreTokenTimeout, Boolean bAsAnonymous)     at Microsoft.SharePoint.SPWeb.InitializeSPRequest()     at Microsoft.SharePoint.SPWeb.EnsureSPRequest()     at Microsoft.SharePoint.SPWeb.get_Request()     at Microsoft.SharePoint.SPWeb.InitWebPubl...	 
12/12/2007 09:55:20.93*	w3wp.exe (0x5A18)                       	0x0CD8	Windows SharePoint Services   	General                       	0	Medium  	...ic()     at Microsoft.SharePoint.SPWeb.get_Language()     at Microsoft.Office.InfoPath.Server.SolutionLifetime.SiteObjectsCache.<>c__DisplayClass5.<>c__DisplayClass7.<EnsureFeaturesPerSite>b__2()     at Microsoft.Office.Server.Diagnostics.FirstChanceHandler.ExceptionFilter(Boolean fRethrowException, TryBlock tryBlock, FilterBlock filter, CatchBlock catchBlock, FinallyBlock finallyBlock)     at Microsoft.Office.Server.Diagnostics.ULS.SendWatsonOnExceptionTag(ULSTagID tagID, ULSCat categoryID, String output, Boolean fRethrowException, TryBlock tryBlock, CatchBlock catchBlock, FinallyBlock finallyBlock)     at Microsoft.Office.InfoPath.Server.SolutionLifetime.SiteObjectsCache.<>c__DisplayClass5.<EnsureFeaturesPerSite>b__1()     at Microsoft.Office.InfoPath.Server.SolutionLifetime.SolutionCach...

Ginger

Can you zip the log, and post it here, I can take a look at it then

John_Mc

Ginger wrote: »

Can you zip the log, and post it here, I can take a look at it then

The problem seems to be fixed now. I have no idea why, but changing the versioning settings to use only Major did the trick?

On an even better note, the content editor is a lot happier with the process now as there's far less steps in getting content published. HAPPY DAYS

Thanks very much for your help. I must admit, I hate sharepoint because when things go wrong - getting help is near impossible on the MSDN forums.

Ginger

Sweet, have no idea what happened for you .. but if it works .. its all good