SOLVED

SharePoint 2013 workflow option disappeard from SP designer

%3CLINGO-SUB%20id%3D%22lingo-sub-776495%22%20slang%3D%22en-US%22%3ESharePoint%202013%20workflow%20option%20disappeard%20from%20SP%20designer%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-776495%22%20slang%3D%22en-US%22%3E%3CP%3EHello%2C%3C%2FP%3E%3CP%3EI%20have%20configured%20workflow%20manager%20on%20our%20SharePoint%202016%20environment.%20It%20was%20working%20fine.%20We%20installed%20SharePoint%20patch%20and%20ran%20the%20product%20configuration%20wizard%2C%20after%20running%20it%20the%20SharePoint%202013%20workflow%20options%20disappeared%20from%20SP%20designer.%20I%20am%20asking%20is%20it%20out%20of%20the%20box%20behavior%20or%26nbsp%3B%20we%20have%20some%20incorrect%20configuration%20with%20Workflow%20manager.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-776495%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3E2016%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EAdmin%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3ESharePoint%20Server%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-776718%22%20slang%3D%22en-US%22%3ERe%3A%20SharePoint%202013%20workflow%20option%20disappeard%20from%20SP%20designer%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-776718%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F383316%22%20target%3D%22_blank%22%3E%40Zulfi11%3C%2FA%3E%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIt%20definitely%20sounds%20like%20an%20issue%20with%20the%20Workflow%20Manager%20configuration%20or%20services.%26nbsp%3B%20Workflow%20Mgr%20is%20generally%20separate%20from%20SharePoint%2C%20but%20other%20things%20could%20have%20thrown%20it%20off.%26nbsp%3B%20There%20are%20a%20few%20things%20to%20check%3A%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3COL%3E%3CLI%3EIn%20Central%20Admin%20-%26gt%3B%20Service%20Apps%2C%20do%20you%20see%20the%20Workflow%20service%20Proxy%20listed%20and%20when%20clicked%2C%20it%20shows%20connected%3F%3C%2FLI%3E%3CLI%3EWhat%20is%20the%20status%20of%20all%20the%20workflow%20services%3F%26nbsp%3B%20Service%20Bus%20Broker%2C%20Workflow%20Service%20backend%2C%20etc.%26nbsp%3B%26nbsp%3B%3C%2FLI%3E%3CLI%3EAre%20you%20using%20self-signed%20certs%20(via%20WF%20mgr%20config)%20or%20like%20a%20wildcard%3F%26nbsp%3B%20Be%20sure%20the%20cert%20isn't%20expired%20(I%20doubt%20this%20is%20the%20case).%3C%2FLI%3E%3CLI%3EIs%20this%20a%20single%20server%20farm%20or%20multi%3F%26nbsp%3B%20On%20the%20server%20with%20the%20Workflow%20Manager%20installed%2C%20check%20the%20Workflow%20Mgr%20event%20logs%20to%20see%20if%20you%20see%20any%20errors.%3C%2FLI%3E%3CLI%3ECheck%20the%20health%20of%20the%20WF%20farm%20with%20some%20PowerShell%20using%20like%20Get-WFFarm%20and%20%3CSPAN%3EGet-WFFarmStatus%3C%2FSPAN%3E.%26nbsp%3B%20Follow%20%3CA%20href%3D%22https%3A%2F%2Fblogs.msdn.microsoft.com%2Fwhereismysolution%2F2016%2F12%2F13%2Ffive-steps-to-check-your-wfm%2F%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ethese%3C%2FA%3Esteps.%3C%2FLI%3E%3C%2FOL%3E%3CP%3EWorst%20case%20you%20might%20try%20to%20re-run%20the%26nbsp%3B%3CEM%3ERegister-SPWorkflowService%26nbsp%3B%3C%2FEM%3Ecommand%20to%20re-establish%20a%20connection%20between%20SharePoint%20and%20the%20workflow%20manager.%26nbsp%3B%20Hopefully%20one%20of%20these%20checks%20will%20reveal%20the%20culprit%20and%20lead%20you%20to%20a%20solution.%26nbsp%3B%20Post%20any%20feedback%20and%20we%20can%20try%20to%20point%20you%20in%20a%20more%20precise%20direction.%26nbsp%3B%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-777051%22%20slang%3D%22en-US%22%3ERe%3A%20SharePoint%202013%20workflow%20option%20disappeard%20from%20SP%20designer%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-777051%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F5855%22%20target%3D%22_blank%22%3E%40Doug%20Allen%3C%2FA%3E%26nbsp%3BThank%20you%20so%20much%20for%20your%20response.%26nbsp%3B%3C%2FP%3E%3CP%3EFollowing%20is%20my%20response%20for%20each%20query%3A%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E1.%26nbsp%3BYes.%20Workflow%20Service%20Proxy%20is%20listed%20and%20shows%20connected%3C%2FP%3E%3CP%3E2.%20All%20of%20these%20services%20services%20are%20running%20on%20the%20workflow%20configured%20server.%3C%2FP%3E%3CP%3E3.%26nbsp%3B%20We%20are%20using%20Self-signed%20certificate.%20Expiry%20date%20is%2022%2F11%2F2023%3C%2FP%3E%3CP%3E4.%20It%20is%20multi-server%20farm.%20(2%3DFront%20end%20server%2C%202%3D%20Search%20Servers%2C%202%3D%20Application%20Servers%2C%202%20%3D%20Distributed%20cache%20servers)%2C%20i%20have%20configured%20the%20workflow%20on%20one%20of%20the%20distributed%20cache%20server.%20Do%20you%20think%20it%20could%20be%20a%20problem%20installing%20it%20on%20the%20distributed%20cache%20server%3F%3C%2FP%3E%3CP%3E5.%26nbsp%3B%20All%20the%20services%20are%20running%20on%20the%20farm%2C%20following%20is%20the%20example%3A%3C%2FP%3E%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20style%3D%22width%3A%20678px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F124780iE4930318C7A4DDE8%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20alt%3D%22Services-running.png%22%20title%3D%22Services-running.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-777055%22%20slang%3D%22en-US%22%3ERe%3A%20SharePoint%202013%20workflow%20option%20disappeard%20from%20SP%20designer%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-777055%22%20slang%3D%22en-US%22%3EFurthermore%2C%20Checked%20event%20logs%20Found%20only%20one%20error%20with%20Event%20id%20564%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-777352%22%20slang%3D%22en-US%22%3ERe%3A%20SharePoint%202013%20workflow%20option%20disappeard%20from%20SP%20designer%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-777352%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F383316%22%20target%3D%22_blank%22%3E%40Zulfi11%3C%2FA%3E%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ESounds%20like%20everything%20is%20in%20good%20shape.%26nbsp%3B%20I%20would%20try%20to%20re-register%20the%20workflow%20service%20with%20SharePoint%20and%20see%20if%20that%20takes%20care%20of%20it.%26nbsp%3B%20Do%20you%20the%20patch%20level%20of%20the%20WF%20farm%20like%20CU2%2C3%2C4%20or%205%3F%26nbsp%3B%20You%20don't%20have%20TLS%201.2%20enabled%20in%20your%20environment%20do%20you%3F%26nbsp%3B%20%26nbsp%3B%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-781205%22%20slang%3D%22en-US%22%3ERe%3A%20SharePoint%202013%20workflow%20option%20disappeard%20from%20SP%20designer%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-781205%22%20slang%3D%22en-US%22%3Ei%20tried%20to%20re-register%20and%20also%20installed%20workflow%20manager%20client%20on%20both%20front%20end%20servers%2C%20which%20fixed%20the%20issue.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-781302%22%20slang%3D%22en-US%22%3ERe%3A%20SharePoint%202013%20workflow%20option%20disappeard%20from%20SP%20designer%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-781302%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F383316%22%20target%3D%22_blank%22%3E%40Zulfi11%3C%2FA%3E%26nbsp%3BSince%20nothing%20else%20was%20wrong%20I%20figured%20that%20would%20do%20it.%26nbsp%3B%20Glad%20that%20worked%20for%20you.%26nbsp%3B%20You%20do%20only%20need%20to%20do%20it%20once%20though.%3C%2FP%3E%3C%2FLINGO-BODY%3E
Highlighted
New Contributor

Hello,

I have configured workflow manager on our SharePoint 2016 environment. It was working fine. We installed SharePoint patch and ran the product configuration wizard, after running it the SharePoint 2013 workflow options disappeared from SP designer. I am asking is it out of the box behavior or  we have some incorrect configuration with Workflow manager. 

 

 

6 Replies
Highlighted

@Zulfi11,

 

It definitely sounds like an issue with the Workflow Manager configuration or services.  Workflow Mgr is generally separate from SharePoint, but other things could have thrown it off.  There are a few things to check:

 

  1. In Central Admin -> Service Apps, do you see the Workflow service Proxy listed and when clicked, it shows connected?
  2. What is the status of all the workflow services?  Service Bus Broker, Workflow Service backend, etc.  
  3. Are you using self-signed certs (via WF mgr config) or like a wildcard?  Be sure the cert isn't expired (I doubt this is the case).
  4. Is this a single server farm or multi?  On the server with the Workflow Manager installed, check the Workflow Mgr event logs to see if you see any errors.
  5. Check the health of the WF farm with some PowerShell using like Get-WFFarm and Get-WFFarmStatus.  Follow these steps.

Worst case you might try to re-run the Register-SPWorkflowService command to re-establish a connection between SharePoint and the workflow manager.  Hopefully one of these checks will reveal the culprit and lead you to a solution.  Post any feedback and we can try to point you in a more precise direction.  

Highlighted

@Doug Allen Thank you so much for your response. 

Following is my response for each query:

 

1. Yes. Workflow Service Proxy is listed and shows connected

2. All of these services services are running on the workflow configured server.

3.  We are using Self-signed certificate. Expiry date is 22/11/2023

4. It is multi-server farm. (2=Front end server, 2= Search Servers, 2= Application Servers, 2 = Distributed cache servers), i have configured the workflow on one of the distributed cache server. Do you think it could be a problem installing it on the distributed cache server?

5.  All the services are running on the farm, following is the example:

Services-running.png

Highlighted
Furthermore, Checked event logs Found only one error with Event id 564
Highlighted
Best Response confirmed by Zulfi11 (New Contributor)
Solution

@Zulfi11,

 

Sounds like everything is in good shape.  I would try to re-register the workflow service with SharePoint and see if that takes care of it.  Do you the patch level of the WF farm like CU2,3,4 or 5?  You don't have TLS 1.2 enabled in your environment do you?    

Highlighted
i tried to re-register and also installed workflow manager client on both front end servers, which fixed the issue.
Highlighted

@Zulfi11 Since nothing else was wrong I figured that would do it.  Glad that worked for you.  You do only need to do it once though.