No Workflow Manager in Related Links section

As in the title...
I log into EM as SYS or owf_mgr (my default user for OW), but don't get the link to Workflow Manager in the Related Links.
Why is that?
Help!
Aliq.

Hi shrikantnew,
I'd like to know the meaning when you sya performed with intranet, and it would be better to post the screenshot here for the report url that append ":8080" in the url. In case your account is not verified, you can post the link(remove hyperlink
if necessary) to the screenshot that saved in OneDrive.
For your situation, you can also check if your account is set to reporting service reader account in TFS Administration Console, or whether your account in corresponding groups that have access to view the reports.
You can have a try to clean team foundation cache on your machine, also delete credentials in credential manager and the browser cookies.
Clean the Cache folder on client computer. The folder path is: C:\Users\username(Team Explorer user name)\AppData\Local\Microsoft\Team Foundation\5.0\Cache. (os: Windows Server 2008 R2)
Clean the Cache folder on Server machine. The folder path is: C:\ProgramData\Microsoft\Team Foundation\Web Access\Cache_v11.0. (os: Windows Server 2008 R2)
After cleaned, on Server machine, click Start and select Run… to open the dialog box, then input iisreset.exe and click OK, wait it run completely.
Another option have a try to rebuild TFS data warehouse and analysis cube manually. Check this
page for more information about the instruction. If the issue persists, please elaborate more details about your scenario.
Best regards,
We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
Click
HERE to participate the survey.

Similar Messages

Informatica Workflow Manager ODBC Relational Connection for ETL in DAC

In Informatica Workflow Manager, I have created a Relational Connection of type ODBC and specified Connect String as "DSN=BIEEDW" where "BIEEDW" is the System ODBC DSN already set pointing to a SQL Server 2008 database.
However, when the ETL run in DAC, the following error occurs in Session log files showing that the database and driver cannot be located:
MAPPING> CMN_1569 Server Mode: [UNICODE]
MAPPING> CMN_1570 Server Code page: [MS Windows Traditional Chinese, superset of Big 5]
MAPPING> TM_6151 The session sort order is [Binary].
MAPPING> TM_6156 Using low precision processing.
MAPPING> TM_6180 Deadlock retry logic will not be implemented.
MAPPING> TM_6187 Session target-based commit interval is [10000].
MAPPING> TM_6307 DTM error log disabled.
MAPPING> TE_7022 TShmWriter: Initialized
MAPPING> DBG_21075 Connecting to database [DSN=BIEEDW], user [bieedw02]
MAPPING> CMN_1761 Timestamp Event: [Wed May 22 01:29:17 2013]
MAPPING> CMN_1022 Database driver error...
CMN_1022 [
[Microsoft][ODBC Driver Manager] Data source name not found and no default driver specified
Database driver error...
Function Name : Connect
Database driver error...
Function Name : Connect
Database Error: Failed to connect to database using user [bieedw02] and connection string [DSN=BIEEDW].]
Any hint in setting the Connect String for ODBC Relational Connection?

Hi,
Let me tell you the real story:
Our server architecture consists of two servers:
Windows Server 2008 R2 (64-bit) platform with the following installed:
- SQL Server 2008
- DAC 10.1.3.4.1
- OBIEE 11g
- BI Apps (Financial Analytics) 7.9.6.3
- Informatica Server 9.1.0 HotFix 2
Windows Server 2003 Enterprise Edition SP2 (32-bit) platform with the following installed:
- Informatica Clients (i.e. Workflow Manager, Repository Manager, Designer and Workflow Monitor)
And thus the ODBC Relational Connection is configured in Informatica Client machine (Workflow Manager) which is a 32-bit platform.
Any idea?

Oracle Workflow Manager, Agent Listener, and Java Mailer problem

Hi,
I am not sure this topic to this forum, since this might be installation issue.
But I am hitting a big wall.
I had Windows 2000 SP4.
I have already installed Oracle Database 10gR1, Oracle Developer 10gR2, and Oracle Workflow 2.6.3 Standalone previously.
Including :
- Oracle Workflow Server 2.6.3
- Oracle Workflow Builder 2.6.3.5
- Apache HTTP Server 9.0.4
- Workflow Middle Tier
Anything seems to right, including the Notification Mailer and the Business Event.
And I had also made backup of them surely.
Now,
I'd like to change into Oracle Database 10gR2 because :
1. Some errors I found when I tried to call a Report from Oracle Form.
Unable to connect to Report Server ...
I thought Oracle Database 10gR1 is not suitable for Oracle Developer 10gR2.
2. And in the OWF 2.6.3 Workflow Home Page, there was no Logout button (which I found in OWF 2.6.4)
I removed my previous installation including Oracle Workflow.
After strugglineg in the installation of Oracle Database 10gR2, now I am facing another problem with Oracle Workflow.
I succesfully installed Oracle Workflow 2.6.4 Server and Oracle Workflow Manager (standalone version),
and the Oracle Workflow Middle Tier.
After I launch Oracle Workflow Configuration Assisstant, everthing seems to be normal.
I succed to open the Oracle Workflow Home Page (and found the Logout button there)
Next, I tried to navigate to the Oracle Workflow Manager.
1. I start the OC4J_Workflow_Management_Container --> initialized
2. OC4J_Workflow_Component_Container
The following error line appeared in the OC4J command prompt
06/05/26 10:31:40 LOG_ID_UNKNOWN : oracle.apps.fnd.cp.gsc.Logger.Logger(String,
int) : Logging to System.out until necessary parameters are retrieved for Logger
to be properly started.
06/05/26 10:31:40 LOG_ID_UNKNOWN : oracle.apps.fnd.cp.gsc.SvcComponentContainer.
initializeStateMachine() : BEGIN [default implementation]
06/05/26 10:31:40 LOG_ID_UNKNOWN : oracle.apps.fnd.cp.gsc.SvcComponentContainer.
getNewWorkflowContext() : BEGIN
06/05/26 10:31:45 LOG_ID_UNKNOWN : oracle.apps.fnd.cp.gsc.SvcComponentContainer.
loadGlobalParameters() : BEGIN
06/05/26 10:31:48 oracle.apps.fnd.wf.common.ContextFactoryException: Unable to g
et connection from data source because the following Exception occurred -> java.
sql.SQLException: ORA-28000: the account is locked
06/05/26 10:33:57 Oracle Application Server Containers for J2EE 10g (9.0.4.1.0)
initialized
3. finally it initialized
Next I tried to go to Oracle Workflow Manager from related link of Enterprise Manager
It is said that the OWF_MGR is locked
(I surprised since I had UNLOCKED the OWF_MGR after the installation and succeed to login at the Workflow Home Page)
And the following error line appeared in the commaned prompt after that
06/05/26 10:35:03 OrionCMTConnection not closed, check your code!
06/05/26 10:35:03 Logical connection not closed, check your code!
06/05/26 10:35:03 (Use -Djdbc.connection.debug=true to find out where the leaked
connection was created)
4. I re-UNLOCK the OWF_MGR and login to Oracle Workflow Manager
I noticed that the Agent Listener and Notification Service is Unavailable
(In OWF 2.6.3, The Agent Listener was started and Notification Service was waiting to be configured)
I tried to start one of the Agent Listener, but the following error appeared
ERROR: The Service Component Container is not running
Well, I had the same problem when installing the OWF 2.6.3
I tried to uninstall (remove) and re-install it like I had done before in OWF 2.6.3
(based on someone's post in Oracle's forum)
But this time, the re-installation won't fix this problem. (It was succeed in the OWF 2.6.3)
Everytime I start the OC4J, using wfmgrstart.bat and wfsvcstart.bat
the OWF_MGR is re-LOCKED(TIME) automatically.
And the servlet (WFALSNRSVC and WFMLRSVC) are not running.
I am worry, since I cannot use the Notification Mailer if this problem had not fixed yet.
(In OWF 2.6.3, the mailer was not available until those servlet is Started)
Sorry for the long post.
Any help would be grateful.
Many thanks,
Buntoro

Hi,
Finally, I have found the solution.
Step :
1. Start all of the Oracle Service, except for the OC4J
If you have already started OC4J, then stop them
Unlocked the <wf_manager_user>
2. Search in your Oracle Home : data-sources.xml
There should be two files,
one is in the ...\OC4J_Workflow_Component_Container\application-deployments\WFALSNRSVCApp
the other is in ...\OC4J_Workflow_Component_Container\application-deployments\WFMLRSVCApp
3. Make sure, you create back up of them.
4. Replace the following line
password="->pwForOwfMgr"
with
password="<your_wf_manager_password>",
should be look like this
password="a"
5. Now start the OC4J using wfmgrstart.bat and wfsvcstart.bat
6. Next, login to the Oracle Workflow Manager
This worked for me.
Hope this will help someone who has the same problem.
Buntoro

How to remove bullets and spacing for url links in the Related Links iview?

I tried to look for a property that I can edit the look-n-feel of the url links in the Related Link iView using "Theme Editor".
All I need is to remove the bullets and increase some vertical spacing between the links.
Currently, it looks like this:
URL iView A
URL Iview B
I go through the whole section of Related Links properties, none of them seems to do what I want.
Here are the list of properties in Related Link section (of Navigation Panel):
Link Color
Text Decoration of Link
Hover Color
Text Decoration of Hovered Link
Initially, I thought "Text Decoration of Link" should be the right property I should look at. But there are a drop-down with 5 options: None, Underline, Blinking, Overline and Line-Through, which really can't achieve what I want.
Thanks for advice.
Kent
Post with Diagram Illustration:
<a href="http://sapnetweaverforum.blogspot.com/2006/11/how-to-remove-bullets-and-spacing-for.html">How to remove bullets and spacing for url links in the Related Links iview?</a>
Message was edited by: Kent C.

Hi, Kai.
I checked the Related iView properties (URL Template), I don't see what layoutset it is really using. I am not sure, is that a layout set apply to the Related Link Iview?
For the regular KM iView, I will see what Layout Set I want to apply, then I can go and change the properties (of layout coontroller, collection renderer & resource renderer)you mentioned. But for this Related Link iView, I really don't know. I guess it may be in the code itself.
If there is a layout set for Related Link iView (or the place to apply layout set to it), can you point to me which one is that? (I did a search through the layout set names, I only find the AppQuicklinkExplorer (I used this for Dynamic Nav. Link iView before), if I can aply this layout set to Related Link iView, my problem will be solved.)
Thanks for help.
Kent

Related links

Hi,
I would like to mimic the design of the user administration functionality for my application. however, I am having problems managing the related links in the detailed navigation. The links open in a new window, and I wish them to open in the cenral area. Also, I don't wish to have the black page tabs at the top, only th elinks. Does anyone have a solution.
thanks in advance,
Mariana

Hi
Permanent display is within the default framework, not your Page. It can be found in PCD>Portal Users>Standard Portal Users>Default Framework Page
Thanks and regards
Kwong Tat

Workflow Manager 1.0 (SharePoint 2013): The process was terminated due to an unhandled exception

I am seeing large numbers of the following errors appearing in the event log of the SharePoint 2013 application server hosting Workflow Manager 1.0:
Log Name: Application
Source: Application Error
Date: [Date/Time]
Event ID: 1000
Task Category: (100)
Level: Error
Keywords: Classic
User: N/A
Computer: [Application Server]
Description:
Faulting application name: Microsoft.Workflow.ServiceHost.exe, version: 1.0.20922.0, time stamp: 0x505e1b24
Faulting module name: KERNELBASE.dll, version: 6.2.9200.16864, time stamp: 0x531d34d8
Exception code: 0xe0434352
Fault offset: 0x0000000000047b8c Faulting process id: 0x691c Faulting application start time: 0x01cfc2776b3f0d74
Faulting application path: C:\Program Files\Workflow Manager\1.0\Workflow\Artifacts\Microsoft.Workflow.ServiceHost.exe
Faulting module path: C:\Windows\system32\KERNELBASE.dll Report Id: b8157bf8-2e6a-11e4-9413-00155d38891d Faulting package full name:
Faulting package-relative application ID: Event Xml:
Log Name: Application
Source: .NET Runtime
Date: [date/time]
Event ID: 1026
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: [same application server]
Description:
Application: Microsoft.Workflow.ServiceHost.exe Framework Version: v4.0.30319 Description: The process was terminated due to an unhandled exception. Exception
Info: Microsoft.Workflow.Common.FatalException Stack: at Microsoft.Workflow.Common.Fx+<>c__DisplayClass2.<failfast>b__0() at System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object,
Boolean) at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean) at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object)
at System.Threading.ThreadHelper.ThreadStart()
Event Xml:
Log Name: System
Source: Service Control Manager
Date: [date/time]
Event ID: 7031
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: [Same application server]
Description:
The Workflow Manager Backend service terminated unexpectedly. It has done this 895 time(s). The following corrective action will be taken in 30000 milliseconds: Restart the service.
Event Xml:
The SharePoint 2013 farm is updated through the September 2014 PU (KB2995902). Topology: 1 App, 2 WFEs. Workflow Manager 1.0 installed to the App server. Workflow Manager 1.0 cumulative updates one
and two have not been installed. The Service Bus Gateway and Service Bus Message Broker services are started. The Workflow Manager Backend service can be started, but then quickly stops.
Thoughts? Resolution? I would be grateful for any assistance.

Hi Stephan,
As I understand, you are encountering the issue that Workflow Manager Backend service terminating each time. May I know did you run the update cmdlets after you installed the updates for SharePoint server 2013? Please confirm it per the link below:
http://technet.microsoft.com/en-us/library/dn133867.aspx
If you haven’t run the updates cmdlets, I suspect this is an install issue. I’d suggest you re-install workflow manager to resolve the issue:
1) Leave WFM/SB Farm
2) Uninstall updates and application in the following order and one at a time:
Service Bus CU1
Workflow Manager CU1
Service Bus 1.0
Workflow Manager 1.0
Workflow Manager Client 1.0
Microsoft Windows Fabric
3) Log into SQL server and delete Service Bus and Workflow Manager databases.
SBManagementDB
SBGatewayDB
SBMessageContainer01
WFManagementDB
WFInstanceManagementDB
WFResourceManagementDB
4) Install in the following order one at a time through Web Platforms Installer:
Workflow Manager 1.0
Service Bus 1.0 CU1
Workflow Manager 1.0 CU1
Regards,
Rebecca Tu
TechNet Community Support

Workflow Manager and SharePoint Designer publishing error

Hello all,
I'm hoping for some help in fixing this issue.
I've been trying to publish a workflow using SharePoint Designer only to find that I get this error:
"Errors were found when compilint the workflow. The workflow files were saved but cannot be run."
After clicking on the advanced button it shows error:
System.InvalidOperationException: Operation failed with error Microsoft.Workflow.Client.WorkflowCommunicationException: The request was aborted: The request was canceled. Client ActivityId : 6a78ad9c-6ac6-f03a-0680-003bd46e5f68. ---> System.Net.WebException:
The request was aborted: The request was canceled. ---> Microsoft.SharePoint.SPException: The requested operation requires an HTTPS (SSL) channel.
Ensure that the target endpoint address supports SSL and try again.
Target endpoint address:
Note: the message cuts off after the "Target endpoint address".
Looking on the SharePoint server, when I try and pull up the Workflow Manager site (https://localhost:12290/) I get this response:
<?xml version="1.0"?>
xmlns:i="http://www.w3.org/2001/XMLSchema-instance">
<Code>AuthorizationError</Code><message><Message>The caller does not have the necessary
permissions required for this operation. Permissions granted: None. Required permissions: ReadScope.</Message></message></Error>
I am running this farm with HTTPS and I have registered the SP workflow service with the appropriate application. I have also set the Workflow Management Site bindings in IIS to utilize the same certificate as the default SharePoint site.
At this point, I don't know if the error that I received from Designer is related to the Site error, although I do know that I also have a Development environment that is able to publish workflows just fine. However, this farm uses HTTP rather than HTTPS
so I can only assume that the differences are what's causing the issue. I would appreciate any help that anyone can offer. Thanks!

Hi,
As I understand, you encountered the issue when you published a workflow on SharePoint 2013 workflow platform.
I wonder does it work well before when using 2013 workflow platform? If it works before, did you install any updates or change the configuration to the workflow related settings?
If this is the first time after you installed workflow manager 2013, then I’d recommend you try re-registering workflow service per the link below and post the result:
http://technet.microsoft.com/en-us/library/jj663115(v=office.15).aspx
http://technet.microsoft.com/en-us/library/jj658588(v=office.15).aspx
From the message you accessed workflow host uri, please make sure the account to wfsetup and wfservice account are both in wfadmins group.
http://blogs.msdn.com/b/briangre/archive/2013/02/20/least-privilege-configuration-for-windows-azure-workflow-with-sharepoint-2013.aspx
Regards,
Rebecca Tu
TechNet Community Support

Territories Related Information Section

Hi All
In the Automotive edition, on the Dealer detail page, there is a Territories related information section that does not appear to be linked to the Territories that I have set up in my Territory Management. Are these not the same? Am not sure if I have misunderstood something or is this an error?
Appreciate any help.
Thanks
Gail

You will need to replicate your territories again via "Record Type Setup" -> "Dealer Territory Field Setup" -> Edit Picklist of field "Name".
- Prakash

Workflow Manager Server certificate expired, how to renew it?

Hello,
We use Sharepoint 2013 and WorkFlow Manager 1.0. The certificate for the WorkFlow Manager farm has expired, and now I am not able to publish new workflows. The WorkFlow Manager configuration wizard does not open, and it logs an error in the windows' event logs
related to certificates. Now I can see in the certificate snap-in that the certificate is expired.
I do not know how to renew it, so I tried to configure a new certificate following the steps described in this link (http://www.harbar.net/articles/wfm3.aspx), but when I run Set-SBCertificate -FarmCertificateThumbprint $cert.Thumbprint -EncryptionCertificateThumbprint $cert.Thumbprint
in PowerShell I receive the next error:
I need to update-renew the expired certificate or configure a new one to solve this as soon as possible.
What could I do?
Melvintt
MCTS, Windows Server 2008 R2: Network Infrastructure
MCTS, Windows Server 2008 R2: Active Directory, Configuring

Try re install it
https://social.technet.microsoft.com/Forums/windowsserver/en-US/bfd3c92b-1a05-4cc5-9b90-8c5c8877dd2c/changing-expired-certificate-for-sharepoint-2013-workflow-manager?forum=sharepointadmin
http://www.experts-exchange.com/OS/Microsoft_Operating_Systems/Server/MS-SharePoint/Q_28226363.html
If this helped you resolve your issue, please mark it Answered. You can reach me through http://itfreesupport.com/
Reinstall the entire farm again for an expired certificate does not seem to be a good workaround, but I think I have to do it. What is the process to remove and reinstall the Workflow Manager?
Melvintt
MCTS, Windows Server 2008 R2: Network Infrastructure
MCTS, Windows Server 2008 R2: Active Directory, Configuring

Undesired Root Relative Link

Document relative link changes to root relative link in new documents created from a template. When saving changes to the template, this link changes back to document relative in the new document. The link points to the content source for an iframe.
What will I have to do to make this link remain a document relative link? Making and undoing a change to the template and re-saving it every time a new document is created constitutes a workflow problem. It also unnecessarily updates all other existing documents based on that template and uploads all of them to the server during synchronization.
I looked through the preferences and couldn't find anything that I might have accidentally changed to cause this phenomenon.

Ah - that's not a root relative link, it's a file:/// link (I don't think there is any name for it), and it's definitely wrong if you are finding it in a file that you have SAVED. But it's how all links in a newly created child page will look BEFORE IT'S SAVED. Once you have saved the file within the site, then DW can manage the links so that they reflect the location where you saved the file.
I do that because the links in the header's navigation change whenever new content is added to a category and the current content moves to the archive. So far I changed the links in the basic template and re-uploaded all the child pages. That's getting a little too much already, so I want to have to update only a single file with the header that the iframes in the uploaded pages are already linked to.
Good golly man, use Server-side includes, not IFrames! This kind of this is exactly what SSI is for.
Not all child pages are at the same level. Most are just one folder down from the top, others are two and even three folders down. That's why proper updating is important. I may stick with the absolute URL.
You must use real ROOT relative links in the include files - then all things will work. With a root relative link it doesn't matter where the page carrying the link is located within the site.

Workflow manager IIS site throws a 403 Forbidden error and published workflows throw an error 400 bad request

Hello All , Request your help on the below issue ,
We have a single server farm SP 2013 where workflow was working as expected but its broken now , Not sure
what caused this. Workflow manager is installed alongside Service Bus. Workflow Manager client is installed on the same SP server.
We are able to create and publish the workflows from SP Designer without errors but when we start the workflow from SharePoint list we get an error " Sorry something went wrong". We have tried creating new workflows but the same problem.
We receive the below error in event viewer.
Error processing management request. Method: PUT, RequestUri: http://server URL:12291/$Workflows/89c767d2-82d2-4bd9-8e5e-dcace81d844f, Error: System.ArgumentException: The remote server returned an error: (400) Bad Request. ---> System.Net.WebException:
The remote server returned an error: (400) Bad Request.
at System.Net.HttpWebRequest.EndGetResponse(IAsyncResult asyncResult)
at Microsoft.ServiceBus.Messaging.ServiceBusResourceOperations.GetAsyncResult`1.EndGetResponse(GetAsyncResult`1 thisPtr, IAsyncResult ar)
at Microsoft.ServiceBus.Messaging.IteratorAsyncResult`1.StepCallback(IAsyncResult result)
--- End of inner exception stack trace ---
Server stack trace:
Exception rethrown at [0]:
at Microsoft.Workflow.Common.AsyncResult.End[TAsyncResult](IAsyncResult result)
at Microsoft.Workflow.Gateway.HttpAsyncResult.End[TAsyncResult](IAsyncResult result)
at Microsoft.Workflow.Gateway.WorkflowServiceGateway.<>c__DisplayClass6a.<EndCreateOrUpdateWorkflow>b__69()
at Microsoft.Workflow.Gateway.WorkflowServiceGateway.ExceptionFilter[T](Func`1 body)
at System.Threading.Tasks.TaskFactory`1.FromAsyncCoreLogic(IAsyncResult iar, Func`2 endFunction, Action`1 endAction, Task`1 promise, Boolean requiresSynchronization)
ULS logs give below error
Error 1 - Microsoft.Workflow.Client.InternalServerException: An internal error occured. For more details, please see the server logs. HTTP headers received from the server - ActivityId: ba6e77cb-aaae-41a0-9cc8-1ea817d0045e. NodeId: Servername.
Scope: /SharePoint/default/bc694777-7bbb-473e-ab2d-20087221a97a/5229793b-31a1-44b1-9b0b-374f38b762fd. Client ActivityId : a6daec9c-7139-7034-b4ee-edeb1f96ec2a. ---> System.Net.WebException: The remote server returned an error: (500) Internal Server Error.
at Microsoft.Workflow.Common.AsyncResult.End[TAsyncResult](IAsyncResult result)
at Microsoft.Workflow.Client.HttpGetResponseAsyncResult`1.End(IAsyncResult result)
at Microsoft.Workflow.Client.ClientHelpers.SendRequest[T](HttpWebRequest request, T content) -
-- End of inner exception stack trace ---
at Microsoft.Workflow.Client.ClientHelpers.SendRequest[T](HttpWebRequest request, T content)
at Microsoft.Workflow.Client.WorkflowManagementClient.SendRequest[T](HttpWebRequest request, T content)
at Microsoft.Workflow.Client.WorkflowManager.Publish(WorkflowDescription description, Boolean terminateActiveInstances)
at Microsoft.SharePoint.WorkflowServices.FabricWorkflowManagementClient.PublishWorkflow(String serviceGroupName, WorkflowDescription workflow)
at Microsoft.SharePoint.WorkflowServices.WorkflowProxy.CreateDefinitionSubscription(String subscriptionName, String eventSource, List`1 eventTypes, String definitionName, IDictionary`2 metadata, WorkflowEventContext eventContext) StackTrace:
at Microsoft.Office.Server.Native.dll: (sig=35339f9c-8871-4ef1-9118-9c1bd0cb6598|2|microsoft.office.server.native.pdb, offset=131CE)
at Microsoft.Office.Server.Native.dll: (offset=21B4D)
Error 2 - Error publishing workflow subscription (republish or retry publish) information: Microsoft.Workflow.Client.InternalServerException: An internal error occured. For more details, please see the server logs. HTTP headers received
from the server - ActivityId: ba6e77cb-aaae-41a0-9cc8-1ea817d0045e. NodeId:
ServerName. Scope: /SharePoint/default/bc694777-7bbb-473e-ab2d-20087221a97a/5229793b-31a1-44b1-9b0b-374f38b762fd. Client ActivityId : a6daec9c-7139-7034-b4ee-edeb1f96ec2a. ---> System.Net.WebException: The remote server returned an error: (500)
Internal Server Error.
at Microsoft.Workflow.Common.AsyncResult.End[TAsyncResult](IAsyncResult result)
at Microsoft.Workflow.Client.HttpGetResponseAsyncResult`1.End(IAsyncResult result)
at Microsoft.Workflow.Client.ClientHelpers.SendRequest[T](HttpWebRequest request, T content) -
-- End of inner exception stack trace ---
at Microsoft.Workflow.Client.ClientHelpers.SendRequest[T](HttpWebRequest request, T content)
at Microsoft.Workflow.Client.WorkflowManagementClient.SendRequest[T](HttpWebRequest request, T content)
at Microsoft.Workflow.Client.WorkflowManager.Publish(WorkflowDescription description, Boolean terminateActiveInstances)
at Microsoft.SharePoint.WorkflowServices.FabricWorkflowManagementClient.PublishWorkflow(String serviceGroupName, WorkflowDescription workflow)
at Microsoft.SharePoint.WorkflowServices.WorkflowProxy.CreateDefinitionSubscription(String subscriptionName, String eventSource, List`1 eventTypes, String definitionName, IDictionary`2 metadata, WorkflowEventContext eventContext)
at Microsoft.SharePoint.WorkflowServices.FabricSubscriptionService.<>c__DisplayClass1.<CreateDefinitionSubscription>b__0()
at Microsoft.SharePoint.WorkflowServices.WorkflowServiceContextExtensions.InvokeWithEcosystemRetry(WorkflowServicesContext context, EcosystemRequiredMethod method)
at Microsoft.SharePoint.WorkflowServices.FabricSubscriptionService.CreateDefinitionSubscription(String subscriptionName, Guid eventSourceId, String eventSource, List`1 eventNames, String definitionName, IDictionary`2 metadata, WorkflowEventContext eventContext)
at Microsoft.SharePoint.WorkflowServices.WorkflowSubscriptionStorageEventReceiver.ItemUpdating(SPItemEventProperties properties)
Error3 - Microsoft.Workflow.Client.InternalServerException: An internal error occured. For more details, please see the server logs. HTTP headers received from the server - ActivityId: ba6e77cb-aaae-41a0-9cc8-1ea817d0045e. NodeId: ServerName.
Scope: /SharePoint/default/bc694777-7bbb-473e-ab2d-20087221a97a/5229793b-31a1-44b1-9b0b-374f38b762fd. Client ActivityId : a6daec9c-7139-7034-b4ee-edeb1f96ec2a. ---> System.Net.WebException: The remote server returned an error: (500) Internal Server Error.
at SPRequest.AddOrUpdateItem: UserPrincipalName=i:0).w|s-1-5-21-182846760-3036401646-508972453-351846, AppPrincipalName= ,bstrUrl=http://sharepointsite ,bstrListName={48A21758-9123-48F0-9BDE-9EB632B07BC6} ,bAdd=False ,bSystemUpdate=False ,bPreserveItemVersion=False
,bPreserveItemUIVersion=False ,bUpdateNoVersion=False ,pbstrNewDocId=00000000-0000-0000-0000-000000000000 ,bHasNewDocId=False ,bstrVersion=16 ,bCheckOut=False ,bCheckin=False ,bUnRestrictedUpdateInProgress=True ,bMigration=False ,bPublish=False ,bstrFileName=<null>
Any help appreciated. Thanks in advance.

Hi,
As I understand, you encountered the issue when you published a workflow on SharePoint 2013 workflow platform.
I wonder does it work well before when using 2013 workflow platform? If it works before, did you install any updates or change the configuration to the workflow related settings?
If this is the first time after you installed workflow manager 2013, then I’d recommend you try re-registering workflow service per the link below and post the result:
http://technet.microsoft.com/en-us/library/jj663115(v=office.15).aspx
http://technet.microsoft.com/en-us/library/jj658588(v=office.15).aspx
From the message you accessed workflow host uri, please make sure the account to wfsetup and wfservice account are both in wfadmins group.
http://blogs.msdn.com/b/briangre/archive/2013/02/20/least-privilege-configuration-for-windows-azure-workflow-with-sharepoint-2013.aspx
Regards,
Rebecca Tu
TechNet Community Support

Workflow Manager - Setup question

I have installed SQL server 2012 express and sharepoint 2013 on a windows 2008 server. I did this to "kick the tires" on the newest sharepoint version. I had previously chosen the development option but I always got stuck in the same spot. Workflow
manager. Specifically in registering the workflow service.
I am a newbie so I apologize if this is something relatively simple. I have tried numerous things to try and get 2013 workflows running on the server but I have not been successful. When I open up a site in designer and click on workflows, I only see 2010
workflows, and underneath that, I see "the option for the sharepoint 2013 workflow platform is not available because the workflow service is not configured on the server. Please contact your service administrator."
I have tried to register the workflow service using both http, and https. I did not check 'allow http' during workflow setup, but the site collection opens with HTTP://myservername/sites/workflows, so I added https to this site in IIS.
When I check the workflow management site in IIS, under browse web site, it says browse *:12290 (https). When I click on browse, it brings up an IE browser window and the URL is https://localhost:12290. It says that there is a problem with this website's
security certificate. The security certificate presented by this website was issued for a different website's address.
When I click on continue to this website, this appears on the page.
Root Scope2013-05-09T17:33:00.6172013-05-09T17:33:00.617/Microsoft.Workflow.Management.Security.WindowsSecurityConfigurationBUILTIN\AdministratorsActive
There is a little popup at the bottom saying that only secure content is displayed. When I click on show all content, this is what appears on the page:
<?xml version="1.0"?>
-<ScopeInfo xmlns="http://schemas.microsoft.com/workflow/2012/xaml/activities" xmlns:i="http://www.w3.org/2001/XMLSchema-instance"><DefaultWorkflowConfiguration/><Description>Root Scope</Description><LastModified>2013-05-09T17:33:00.617</LastModified><LastRevised>2013-05-09T17:33:00.617</LastRevised><Path>/</Path>-<SecurityConfigurations>-<ScopedSecurityConfiguration
i:type="WindowsSecurityConfiguration"><Name>Microsoft.Workflow.Management.Security.WindowsSecurityConfiguration</Name><WorkflowAdminGroupName>BUILTIN\Administrators</WorkflowAdminGroupName></ScopedSecurityConfiguration></SecurityConfigurations><Status>Active</Status></ScopeInfo>
Being that this is all on the same server, maybe I am not putting in the right info. I input the following into sharepoint 2013 management shell, run as administrator:
register-spworkflowservice -spsite "https://sharepoint-ki3/sites/workflows" -workflowhosturi "https:localhost:12291"
I get the following error message:
register-spworkflowservice : The underlying connection was closed: An unexpected error occurred on a send. Client ActivityId: e218b8a2-0655-4d09-8f4d-5cbc09f3ddf7. At line:1 char:1
+ register-spworkflowservice -spsite "https://sharepoint-ki2/sites/workflows"
-wor ...
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : InvalidData (Microsoft.SHare...workflowservice:RegisterSPWorkflowservice) [Register-spworkflowservice], WorkflowCommunicationException.
+ FullyQualifiedErrorId: Microsoft.Sharepoint.WorkflowServices.Powershell.RegisterSPWorkflowService
Any idea how to resolve this? Should I just install workflow manager on another machine and be done with it?
Any help would be greatly appreciated. Thanks for checking this out.

The link under the workflow section of
http://social.technet.microsoft.com/wiki/contents/articles/15289.sharepoint-2013-best-practices-creating-a-development-environment.aspx#Configure_Workflows_for_SharePoint_TwentyThirteen explains how to set up workflow manager and configure it within sharepoint.
Here are some general installation resources:
http://social.technet.microsoft.com/wiki/contents/articles/12438.sharepoint-2013-best-practices.aspx#Installation
Kind regards,
Margriet Bruggeman
Lois & Clark IT Services
web site: http://www.loisandclark.eu
blog: http://www.sharepointdragons.com

Trouble in installing Workflow Manager 1.0

Hi All,
When I tried to install Workflow Manager 1.0 , I got the following error.
I downloaded the Web Platform Installer and installed it.
Still I get the same error.
Please help me to troubleshoot the error.

Hi Muthukumar;
You must ensure Web Platform Installer version should be same on the server where you are downloading Workflow Manager 1.0 files and on the server where you are installing Workflow Manager 1.0 files for offline installation scenarios.Workflow Manager 1.0
Installation requires valid Web Platform Installer Version on Workflow Server.
If you want to install Workflow Manager 1.0 on servers without internet connectivity, you will run into problems with the Web Platform Installer, the only tool Workflow Manager 1.0 can be installed with.
There is a command line tool of Web Platform Installer, where you can download the installation files and all of its dependencies to a internet accessible machine, move it over to one of your servers and install it in offline mode.
Take the following steps to do so:
Download the
WebPICMD.exe Package from the MS Download Center and unzip it to a folder (C:\WebPICMD\WebPICMD.exe in our case)
Open a Command Prompt, navigate to the folder you extracted the tool and execute the following command:
WebpiCmd.exe /Offline /Products:WorkflowManager /Path:D:\Temp\WorkflowManager\
This will initiate a download with all the related components into the provided folder.
Copy the WebPICMD.exe to the server where you want to install the WorkflowManager 1.0, in our example to
D:\Temp\WebPICMD\WebPICMD.exe
Copy the downloaded files to your server where you want to install the WorkflowManager 1.0, in our example to
D:\Temp\WorkflowManager
Open a Command Prompt, navigate to the folder you copied the WebPICMD.exe tool and execute the following command:
WebPICMD.exe /Install /Products:WorkflowManager
/AcceptEULA /SuppressReboot
/Log:./WorkflowManager.log /Xml:file:///D:\Temp\WorkflowManager\feeds\shadow-webproductlist.xmlThis will initiate the installation of the Workflow Manager 1.0 and its dependencies. The outcome of the installation will be logged to the WorkflowManager.log
file. The above line will suppress reboots and will accept the license terms automatically.
A log file will be created at the following path, where you can see the process and the warnings/errors/information about the installation:
%localappdata%\microsoft\web platform installer\logs\webpicmd
You could also go through these helpful
links .
Please revert back for any further help.
Regards
Prasant Chhetri

How to make site root-relative links work in DW and Server both?

See details on buggy DW image link behavior, below. My question is:
1) how to make site root-relative links work in DW and Server both? Or…
2) how to reliably automate the change of several hundred legacy root-relative links of the form
/images/image.jpg to document-relative?
That is, to
../images/image.jpg or
../../images/image.jpg or
../../../images/image.jpg etc…depending on where the directory is.
The old format (/images/image.jpg ) used to work fine in my previous DW 8 configuration but appear grey in DW after “upgrading” to DW cs5.5 mac. (they look fine on the server, but it’s hard to edit image-heavy pages locally when they are all grey).
I tried changing the files to how DW creates root relative links now:
/public_html/images/image.jpg, which is a very easy, attractive root flow since there’s a one-to-one mapping. These look great in DW but are broken on the server!
I looked at the “advanced” site setup, and it looked like it might be possible to nuke the /public_html/ part of my server info…but it also looked like there was the potential for doing damage changing these settings, which are automatically generated from our server connection settings, which seem to work.
The “links relative to document/ site root” toggle…does that change how DW interprets existing links, or just change the default when you are adding a link? I have made 80% of the file links document relative…before wondering if root-relative isn’t better?
It sure seems less ambiguous for all those images if theres a way to make root relative work for DW design view, DW link check, and server.
Summary of buggy behavior: (see test with images here)
"old style" site root link
      /images/img_book/WScover120x150_NEW.jpg
      Design veiw in DW: broken (grey w/ broken icon)
      Link check in DW: "external link" (i.e., uncheckable, + file could appear orphaned)
      Browser: good
      Ease of switching: n/a (existing format)
"new style" site root relative link
      /public_html/images/img_book/WScover120x150_NEW.jpg
      Design veiw in DW: good
      Link check in DW: good
      Browser: broken
      Ease of switching: easy
Document relative link
      ../../images/img_book/WScover120x150_NEW.jpg
      Design veiw in DW: good
      Link check in DW: good
      Browser: good
      Ease of switching: hard (how to automate?)
Absolute link
      http://www.oasisdesign.net/images/img_book/WScover120x150_NEW.jpg
      Design veiw in DW: broken (grey w/ broken icon)
      Link check in DW: external (i.e., uncheckable, + file could appear orphaned)
      Browser: good
      Ease of switching: n/a...not a real option
Thanks!
Similar discussion on "/"

Hello again Jon!
Thanks for jumping on this.
All clear and understood about where publc_html is etc.
No contemplation of nuking the actual public_html directory on the server, just the "/public_html" text string at the start of the DW-generated links.
"/public_html" is automatically added to the front of the link in DW if I create the link with any of the GUI tools, if I have "site root relative" selected. And ""/public_html" ends up in the code, and gets uploaded that way to the server, where it (obviously) doesn't work.
Doesn't sound like it is supposed to work this way. Also, what seems to be the usual root relative format (/images/image.jpg) shows as a broken link in the GUI and an external link in the DW link check. All this togther makes me thinkI have some obscure setting incorrect?
The setting that caught my eye is manage sites/ site setup/ advance settings/ local info/ web url, which is automatically set to http://www.oasisdesign.net/public_html/
it gives an option to change it but it makes every effort to make this NOT look like something users should mess with:
Having gone through the more careful thought process during this post, I'm ready to do the experiment of changing the remote server web URL (why is it wrong by default?)...think I'll eat dinner first so there's 45 min to avert disaster if anyone knows this to be a bad idea!
Art
PS--don't have a local testing server...don't think this will solve the GUI broken link/ link shows as external problems.
Is there an easy, automated way to change links sitewide from document to root relative?

Configuring Workflow Manager for SharePoint 2013

I have gone through the configurations of Workflow and SharePoint to use the new Workflow Manager 1.0 several times now, and keep getting the below errors.
My environment is set up with 2 servers, 1 SP Web Applicatin and 1 SQL. Workflow is installed on the SQL server. These errors are from the SQL Server.
Event ID 22
Service Bus exception swallowed at location ServiceBusNamespaceListener.GetSessionAndStateWithRetryAsyncResult.HandleException. Microsoft.ServiceBus.Messaging.MessagingException: The token provider service was not avaliable when obtaining a token for 'https://srv22.domain.com:9355/WorkflowDefaultNamespace/$STS/Windows/'. ---> Microsoft.ServiceBus.TokenProviderException: The token provider service was not avaliable when obtaining a token for 'https://srv22.domain.com:9355/WorkflowDefaultNamespace/$STS/Windows/'. ---> System.Net.WebException: The remote server returned an error: (502) Bad Gateway.
at System.Net.HttpWebRequest.GetRequestStream(TransportContext& context)
at System.Net.HttpWebRequest.GetRequestStream()
at Microsoft.ServiceBus.TokenProviderHelper.GetWindowsAccessTokenCore(IEnumerator`1 stsUris, Func`2 uriBuilder, String requestToken, TimeSpan timeout, DateTime& expiresIn)
--- End of inner exception stack trace ---
at Microsoft.ServiceBus.TokenProviderHelper.ThrowException(Uri requestUri, WebException exception)
at Microsoft.ServiceBus.TokenProviderHelper.GetWindowsAccessTokenCore(IEnumerator`1 stsUris, Func`2 uriBuilder, String requestToken, TimeSpan timeout, DateTime& expiresIn)
at Microsoft.ServiceBus.WindowsTokenProvider.OnBeginGetToken(String appliesTo, String action, TimeSpan timeout, AsyncCallback callback, Object state)
at Microsoft.ServiceBus.TokenProvider.GetTokenAsyncResult..ctor(TokenProvider tokenProvider, String appliesTo, String action, Boolean bypassCache, TimeSpan timeout, AsyncCallback callback, Object state)
at Microsoft.ServiceBus.TokenProvider.BeginGetToken(String appliesTo, String action, Boolean bypassCache, TimeSpan timeout, AsyncCallback callback, Object state)
at Microsoft.ServiceBus.TokenProviderUtility.GetMessagingToken(ITokenProvider tokenProvider, Uri baseAddress, String appliesTo, String action, Boolean bypassCache, TimeSpan timeout)
--- End of inner exception stack trace ---
Server stack trace:
at Microsoft.ServiceBus.TokenProviderUtility.GetMessagingToken(ITokenProvider tokenProvider, Uri baseAddress, String appliesTo, String action, Boolean bypassCache, TimeSpan timeout)
at Microsoft.ServiceBus.Messaging.Sbmp.SbmpMessageCreator.GetAuthorizationHeader(String action)
at Microsoft.ServiceBus.Messaging.Sbmp.SbmpMessageCreator.CreateWcfMessageInternal(String action, Object body, Boolean includeToken)
at Microsoft.ServiceBus.Messaging.Sbmp.AcceptMessageSessionForNamespaceAsyncResult..ctor(SbmpMessagingFactory messagingFactory, ReceiveMode receiveMode, Int32 prefetchCount, CreateControlLinkSettings controlLinkSettings, TimeSpan timeout, AsyncCallback callback, Object state)
at Microsoft.ServiceBus.Messaging.Sbmp.SbmpMessagingFactory.OnBeginAcceptMessageSession(ReceiveMode receiveMode, TimeSpan timeout, AsyncCallback callback, Object state)
at Microsoft.ServiceBus.Messaging.MessagingFactory.AcceptMessageSessionAsyncResult.<GetAsyncSteps>b__29(AcceptMessageSessionAsyncResult thisPtr, TimeSpan t, AsyncCallback c, Object s)
at Microsoft.ServiceBus.Messaging.IteratorAsyncResult`1.EnumerateSteps(CurrentThreadType state)
Exception rethrown at [0]:
at Microsoft.Workflow.Common.AsyncResult.End[TAsyncResult](IAsyncResult result)
at Microsoft.Workflow.Dispatcher.ServiceBusNamespaceListener.GetSessionAndStateWithRetryAsyncResult.EndAsyncResult(IAsyncResult result)
at Microsoft.Workflow.Common.BackoffRetryAsyncResult.IsolateWithRetry(IAsyncResult result)
Event ID 370
The Workflow Manager cannot contact Service Bus service after retrying for '12' minutes. Please verify if the Service Bus service is up and running. The Workflow Manager failed at location 'ServiceBusNamespaceListener.GetSessionAndStateWithRetryAsyncResult.HandleException' due to exception: Microsoft.ServiceBus.Messaging.MessagingException: The token provider service was not avaliable when obtaining a token for 'https://srv22.domain.com:9355/WorkflowDefaultNamespace/$STS/Windows/'. ---> Microsoft.ServiceBus.TokenProviderException: The token provider service was not avaliable when obtaining a token for 'https://srv22.domain.com:9355/WorkflowDefaultNamespace/$STS/Windows/'. ---> System.Net.WebException: The remote server returned an error: (502) Bad Gateway.
at System.Net.HttpWebRequest.GetRequestStream(TransportContext& context)
at System.Net.HttpWebRequest.GetRequestStream()
at Microsoft.ServiceBus.TokenProviderHelper.GetWindowsAccessTokenCore(IEnumerator`1 stsUris, Func`2 uriBuilder, String requestToken, TimeSpan timeout, DateTime& expiresIn)
--- End of inner exception stack trace ---
at Microsoft.ServiceBus.TokenProviderHelper.ThrowException(Uri requestUri, WebException exception)
at Microsoft.ServiceBus.TokenProviderHelper.GetWindowsAccessTokenCore(IEnumerator`1 stsUris, Func`2 uriBuilder, String requestToken, TimeSpan timeout, DateTime& expiresIn)
at Microsoft.ServiceBus.WindowsTokenProvider.OnBeginGetToken(String appliesTo, String action, TimeSpan timeout, AsyncCallback callback, Object state)
at Microsoft.ServiceBus.TokenProvider.GetTokenAsyncResult..ctor(TokenProvider tokenProvider, String appliesTo, String action, Boolean bypassCache, TimeSpan timeout, AsyncCallback callback, Object state)
at Microsoft.ServiceBus.TokenProvider.BeginGetToken(String appliesTo, String action, Boolean bypassCache, TimeSpan timeout, AsyncCallback callback, Object state)
at Microsoft.ServiceBus.TokenProviderUtility.GetMessagingToken(ITokenProvider tokenProvider, Uri baseAddress, String appliesTo, String action, Boolean bypassCache, TimeSpan timeout)
--- End of inner exception stack trace ---
Server stack trace:
at Microsoft.ServiceBus.TokenProviderUtility.GetMessagingToken(ITokenProvider tokenProvider, Uri baseAddress, String appliesTo, String action, Boolean bypassCache, TimeSpan timeout)
at Microsoft.ServiceBus.Messaging.Sbmp.SbmpMessageCreator.GetAuthorizationHeader(String action)
at Microsoft.ServiceBus.Messaging.Sbmp.SbmpMessageCreator.CreateWcfMessageInternal(String action, Object body, Boolean includeToken)
at Microsoft.ServiceBus.Messaging.Sbmp.AcceptMessageSessionForNamespaceAsyncResult..ctor(SbmpMessagingFactory messagingFactory, ReceiveMode receiveMode, Int32 prefetchCount, CreateControlLinkSettings controlLinkSettings, TimeSpan timeout, AsyncCallback callback, Object state)
at Microsoft.ServiceBus.Messaging.Sbmp.SbmpMessagingFactory.OnBeginAcceptMessageSession(ReceiveMode receiveMode, TimeSpan timeout, AsyncCallback callback, Object state)
at Microsoft.ServiceBus.Messaging.MessagingFactory.AcceptMessageSessionAsyncResult.<GetAsyncSteps>b__29(AcceptMessageSessionAsyncResult thisPtr, TimeSpan t, AsyncCallback c, Object s)
at Microsoft.ServiceBus.Messaging.IteratorAsyncResult`1.EnumerateSteps(CurrentThreadType state)
Exception rethrown at [0]:
at Microsoft.Workflow.Common.AsyncResult.End[TAsyncResult](IAsyncResult result)
at Microsoft.Workflow.Dispatcher.ServiceBusNamespaceListener.GetSessionAndStateWithRetryAsyncResult.EndAsyncResult(IAsyncResult result)
at Microsoft.Workflow.Common.BackoffRetryAsyncResult.IsolateWithRetry(IAsyncResult result).
The error messages suggested to me that the issue was being caused by our proxy server. I have removed the proxy server from the equation by removing the proxy settings.
I then also tried to navigate to the url in the error messages. When i navigate to https://srv22.domain.com:9355/WorkflowDefaultNamespace/$STS/Windows/ i get a 400 Bad Request. When i change the address to https://srv22.domain.com:9355/WorkflowDefaultNamespace/$sts/Windows/
($sts in Lower Case rather than Upper Case) i get a response from the Workflow server.
I have searched high and low for a solution to this, and cannot find one, can anybody shed any light on the situation.
Thanks in advance
Paul

Hi Paul,
Here is a similar post with bad gateway error related to proxy and gateway settings, you can take a look.
http://social.technet.microsoft.com/Forums/sharepoint/en-US/73a909d2-226d-454e-a8ca-c5e62dc8caac/setup-windows-azure-workflow-addwfhost-error-wfmanagementwftopic-and-token-provider-service
Thanks
Daniel Yang
TechNet Community Support

No Workflow Manager in Related Links section

Similar Messages

Maybe you are looking for