After installing and configuring Workflow Manager and Service Bus, I'm getting 403.

I've spent the day installing SharePoint 2013 on a Windows Server 2012 environment. This server is not the domain controller. Following instructions on how to install and configure Workflow Manager and service bus, it appears although I'm following the instructions
(and I get no errors), something is not working.
If I try to go to the website that it creates in IIS
http://localhost:12291 I get a 403 error. Also if I perform the powershell query to get the port number "Get-WFFarm | ft WFMgmtHttpPort" I don't get any value returned to me.
Until I validate that the Workflow Manager is installed and working, I will not attempt to pair it to the SharePoint 2013 farm. Which hopefully makes this a Workflow Manager question not a SharePoint issue.
Can anyone offer any suggestions please? Should I even get a valid webpage if I hit localhost:12291? According to one walkthrough I've looked at I should get an XML display of workflow and security configurations.

I experienced the same two issues mentioned in this thread today.
Regarding the proper XML not appearing at <workflowhost>:12291 I was experiencing the same with an error message in Chrome saying the caller lacked read permissions, and 403 in IE. I had checked IIS, database permissions and connections and more.
All of the setup messages and status checks were a-okay. I voted Zimo's comment as helpful because it cued me in to examine the service in Central Administration - where I found there was no administrator assigned to the workflow service. As soon as that was
done, the workflow host site was brows-able.
The resolution to SharePoint Designer not offering 2013 workflows as an option was in my case that there was an additional WFE on which I had not installed the Workflow Manager
Client. This is noted with a bright yellow box in the section about configuring workflow with HTTP here:
http://technet.microsoft.com/en-us/library/jj658588(v=office.15)
If puzzles are good for your BRAIN then SharePoint will keep it really healthy!
Ramona Maxwell MCPD
SharePoint 2010, MCITP
SQL Server 2008

Similar Messages

How to configure workflow manager 1.0 ? Scenario "sharepoint 2013 and sql server 2012 workflow manager in one server" .

i have sharepoint 2013 and sql server 2012 in one server . how to configure workflow manager 1.0 on the same server ?

Please follow below technet article :
http://technet.microsoft.com/en-us/library/jj658588(v=office.15).aspx
Installing and Configuring Workflow Manager 1.0 (Step by Step)
Note: The steps in this article apply to SharePoint Server 2013.
The SharePoint 2013 Workflow platform is not supported in SharePoint Foundation 2013.
If my contribution helps you, please click Mark As Answer on that post and
Vote as Helpful
Thanks, ShankarSingh(MCP)

Workflow Manager Backend services starts and then immediately stops.

I cannot start the Workflow Manager Backend service. It starts and then immediately stops. The event log shows the error "Service cannot be started. System.Security.Crytography.CryptographicException: Keyset does not exist".
This problem may have started when the password for the account that the service runs under expired.
The Windows Fabric Host Service and the Service Bus Gateway and Service Bus Message Broker services are all running.
SJT00

I cannot start the Workflow Manager Backend service. It starts and then immediately stops. The event log shows the error "Service cannot be started. System.Security.Crytography.CryptographicException: Keyset does not exist".
This problem may have started when the password for the account that the service runs under expired.
The Windows Fabric Host Service and the Service Bus Gateway and Service Bus Message Broker services are all running.
SJT00

Timeout while configuring workflow manager (service bus services are stuck on strarting)

Hello,
I cant finish workflow manager configuration. help me please.
I tried:
1) leave the farm (Workflow manager configuration), delete databases, create new farm with default settings - it creates SB&WF farms and on 3d stage I get timeout error.
2) leave the farm, delete databases, delete workflow manager and service bus software, install it again, create new farm with defaults - the same result.
3) leave the farm, delete databases, get powershell commands for "create new farm with default settings", run it step by step - same result.
there are generated powershell commands:
New-SBFarm -SBFarmDBConnectionString '... ManagementDB con string ...' -InternalPortRangeStart 9000 -TcpPort 9354 -MessageBrokerPort 9356 -RunAsAccount 'domain\acc' -AdminGroup 'BUILTIN\Administrators' -GatewayDBConnectionString '... gateway con string
...' -CertificateAutoGenerationKey $SBCertificateAutoGenerationKey -MessageContainerDBConnectionString '... message container con string ...' -Verbose;
New-WFFarm -WFFarmDBConnectionString '... WF managementDB con string ...' -RunAsAccount 'domain\acc' -AdminGroup 'BUILTIN\Administrators' -HttpsPort 12290 -HttpPort 12291 -InstanceDBConnectionString '... WF instanceDB con string ...' -ResourceDBConnectionString
'... wf resourceDB con string ...' -CertificateAutoGenerationKey $WFCertAutoGenerationKey -Verbose;
Add-SBHost -SBFarmDBConnectionString '... ManagementDB con string ...' -RunAsPassword $SBRunAsPassword -EnableFirewallRules $true -CertificateAutoGenerationKey $SBCertificateAutoGenerationKey -Verbose;
I don't see any errors in event log, only timeout error in setup log.
Service bus gateway service is started successfully, Service bus message broker is stuck starting.

dmadelung, thank you for your message.
the problem was with ports. 9000 port was used already. moving to different ports resolved the problem

Login problem after installing and activating OS X Server app in Yosemite

After installing and activating file sharing on OS X Server on my MacBook Air, the MBA was restarted. At the login screen I enter my password into my account and it directs me to a 'Guest' login screen, asking for a password which I did not create.
HELP!!!!!

There is no longer any provision for starting a PostgreSQL process other than the ones reserved for built-in services. Create a launch daemon with content such as the following:
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple Computer//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<dict>
     <key>Label</key>
     <string>org.postgresql.postgres</string>
     <key>UserName</key>
     <string>_postgres</string>
     <key>GroupName</key>
     <string>_postgres</string>
     <key>ProgramArguments</key>
     <array>
          <string>/Applications/Server.app/Contents/ServerRoot/usr/bin/postgres</string>
          <string>--apple-configuration</string>
          <string>/Library/Server/PostgreSQL/Config/org.postgresql.postgres.plist</string>
     </array>
     <key>KeepAlive</key>
     <dict>
          <key>PathState</key>
          <dict>
               <key>/Library/Server/PostgreSQL/Data</key>
               <true/>
          </dict>
     </dict>
     <key>StandardErrorPath</key>
     <string>/Library/Logs/PostgreSQL/PostgreSQL.log</string>
     <key>StandardOutPath</key>
     <string>/Library/Logs/PostgreSQL/PostgreSQL.log</string>
</dict>
</plist>
<plist version="1.0">
Also create these directories and files, owned by _postgres:_postgres:
/Library/Logs/PostgreSQL
/Library/Server/PostgreSQL
/Library/Server/PostgreSQL/Backup
/Library/Server/PostgreSQL/Config
/Library/Server/PostgreSQL/Config/org.postgresql.postgres.plist
/Library/Server/PostgreSQL/Data
Finally, initialize the database with a suitable invocation of initdb(1).
For more details, see the PostgreSQL documentation. You may find it easier to use a packaged third-party distribution independent of the built-in one.

Getting error 16 in CC2014 Photoshop even after installing and re-installing mac maverick latest update 10.9.5

Getting error 16 in CC2014 Photoshop even after installing and re-installing mac maverick latest update 10.9.5

Check if this helps. http://helpx.adobe.com/x-productkb/policy-pricing/configuration-error-cs5.html
~ Arpit

Hi I am getting an update failed message (49) when trying to update photoshop after installing and whenever I start photoshop and try to access the file menu it crashes

Hi I am getting an update failed message (49) when trying to update photoshop after installing and whenever I start photoshop and try to access the file menu it crashes

Duplicate thread.

When i make internet recovery i see question mark after install and reboot. Why?

When i make internet recovery on clear HDD's with created striped software RIDE 0 with two HDD in mac mini.
I see question mark after install and reboot. Why?

Make a "Genius" appointment at an Apple Store to have the machine tested. Back up all data before you go.

No iCloud after installing and updating Lion

I had wireless issues (still do) so I formatted, reinstalled Snow Leopard, re-downloaded Lion, updated Lion and I still do not have icloud Anyone have any suggestions?

So after many hours of searching and testing, I find that I was stuck on the 10.7.2 11C35 version of Lion, not the 11C74 (go to About This Mac and click on Version) even though it kept telling me that my software was up-to-date. In order to resolve this I had to boot in recovery mode and re-install Lion from the App Store which now has the updated Lion so minimal updates after install and on first boot asked me to setup iCloud. Still have my wireless issues but now I can sync my iphones, work pc and my mba contacts easier.

Cd burning issue after installing and updating snow leopard

After installing and updating snow leapard to the latest version, the cd burner for i-tunes quit working. it says" burning disk initializing" then "burning disk finishing" comes up with the error "the attempt to burn a disk failed. the disc drive didn't respond properly and can't recover or retry. Any suggestions to fix this problem?

First try other disks, brand new, then try another brand, then consider backup user files and (clean and polish then) c booting off the 10.6.3 disk and simply reinstalling OS X then updating to 10.6.8 again.
Hopefully this should fix the issue in OS X software, you may have to reinstall certain third party software again that it's kext files got kicked out of OS X by the reinstall.
If you get hung booting at any time, simply hold the shift key down and then update your software then reboot normally

Facing some problem while configuring Workflow Manager 1.0.

Hi,
I am facing some problem while configuring Workflow Manager 1.0. in my farm.
Scenario is,
I have installed and configured workflow manager in my farm, it was working well with no issue. But one of team member played with AD and deleted Farm administrator's entry from AD by mistake. So suddenly workflows get affected and stopped working.
Then I added administrator entry in AD, uninstalled the Workflow Manager and installed it again. But now while configuring workflow manager I am facing some issues that "Failure to adding user in BUILTIN\Administrative group. Please add it manually"
And after sometime it shows another error message that, "Starting service Service Bus Massage broken failed: Timed out has expired, the operation has not been completed"
If I go for services then "Service bus Message broker" service is not running properly (Its status is just showing "Starting") and don't starts.
I have also added the user in BUILTIN\Administrator, IIS_IUSER, WSS_WPG group of the machine from computer manager - user and groups.
Also given permission to databases, and assign role of sysadmin and dbcreator to user
I also tried following steps
1) Stop all services associated to workflows
2) Uninstalled workflow manager
3) Deleted all databases associated with workflows
4) Installed workflow manager and tried to configure.
But showing same error.
If I use another SharePoint server farm to configure workflows, there I am not getting first error of adding user to BUILTIN\Administrator group. but second error remains same.
We having SQL server and Active directory at another machine and FARM at another machine, if I use local admin for configuration of the workflows (as local admin can start any services) but entry of local admin is not Active directory so can not assign SQL's
sysadmin, and dbcreator role to local admin.
I am attaching snapshot of error for better understanding.
Your help will be very precious to me.
Thanks,
Rajesh
Rajesh Agravat

Rajesh
Check to see what the service accounts are being used for these Workflow Manager 1.0 services:
Service Bus Message Broker
Service Bus Gateway
Workflow Manager Backend
All of these should be running and your workflow service account should be running all of these. If any are still configured under the old service account, they'll need to be updated. Next, check to see what service accounts have access to the
Workflow Manager 1.0 databases:
SbGatewayDatabase
SbManagement
SbMessageContainer
WFInstanceManagement
WFManagement
WFResourceManagement
The Workflow Manager service account should be mapped as the DBO for all of these. if any are still configured under the old service account, they'll need to be updated.
Given the complete loss of the original workflow service account, and the resultant impact on security configuration throughout the workflow farm, I would recommend performing a re-installation. Do it thus:
Launch Workflow Manager Configuration Wizard
Select the Leave Workflow Manager Farm
Stop all workflow services (see above list)
Repeat steps 1-3 for each instance of Workflow Manager 1.0 Server installed.
Delete all Workflow Manager databases (see above list).
reboot.
Start new installation.

Workflow Manager Backend service fails to start - FatalException

Hi,
I installed Workflow Manager 1.0 (with default recommended configuration) and the Cummulative Update 1 and activated the feature on SharePoint 2013. I restarted my server.
The Workflow Manager Backend service cannot start. An attempt is done every 30" but it's always fails. The errors I see in the event viewer (every 30") are the following:
Error 1
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()
Error 2
Faulting application name: Microsoft.Workflow.ServiceHost.exe, version: 1.0.20922.0, time stamp: 0x505e1b24
Faulting module name: KERNELBASE.dll, version: 6.2.9200.16451, time stamp: 0x50988aa6
Exception code: 0xe0434352
Fault offset: 0x000000000003811c
Faulting process id: 0x25c0
Faulting application start time: 0x01cefd844175ec32
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: 7fb79f6a-6977-11e3-9401-0050569055b0
Faulting package full name:
Faulting package-relative application ID:
As a result I cannot deploy workflows on SharePoint using Visual Studio. I get a 500 error during activation of the related feature.
Any ideas?
Dimitris Papadimitriou, Software Development Professional

Hi,
I am not sure if you have solved this but it seems that the WF 1.1 Update requires some more updates in one of the tables in the configuration
database for the Workflow installation. Checkout the database [WFResourceManagementDB] and the table [WorkflowServiceConfig]. You need the flowing entries and values:
WorkflowServiceScopeSnapshotProcessBatchSize
20
WorkflowServiceScopeSnapshotProcessLoopInterval
00:05:00
WorkflowServiceSuspendedInstanceRetentionDuration
30.00:00:00
WorkflowServiceMaxInstanceCompressedSizeKB
5120
BR
Magnus Danielson

Unable to find the User Named Account Name@Domain Name while Configuring Workflow Manager

Hi,
I have installed Work Flow Manager,Service Bus and its Cumulative Updates.
While Configuring Workflow Manger using Workflow Manager configuration wizard i am getting the error while creating a Service Bus Namespace.
I have provided the Service Accounts for both Workflow Manager and Service Bus as Domain\Account instead of
Account@Domain.
While looking in to the Power Shell scripts that are poupulated by the GUI i have identified that
Account@Domain is appended to the ManageUsers switch while creating a Service Bus Namespace and the GUI configuration is failing.
    New-SBNamespace -Name 'WorkflowDefaultNamespace' -AddressingScheme 'Path' -ManageUsers 'Domain\Account','Account@Domain' -Verbose;
So i need to modify the Powershell script as below and need to run the Powershell scripts for configuring Workflow Manager.
Is this a bug in GUI Workflow Configuration Wizard or am i doing something wrong.
Please help.
    New-SBNamespace -Name 'WorkflowDefaultNamespace' -AddressingScheme 'Path' -ManageUsers 'Domain\Account' -Verbose;
Scripts Populated from GUI modified for Making it working:
# To be run in Workflow Manager PowerShell console that has both Workflow Manager and Service Bus installed.
# Create new SB Farm
$SBCertificateAutoGenerationKey = ConvertTo-SecureString -AsPlainText -Force -String 'Run As Password' -Verbose;
New-SBFarm -SBFarmDBConnectionString 'Data Source=Server Name;Initial Catalog=SbManagementDB;Integrated Security=True;Encrypt=False' -InternalPortRangeStart 9000 -TcpPort 9354 -MessageBrokerPort 9356 -RunAsAccount 'Domain\Account' -AdminGroup 'Domain\Domain
Group' -GatewayDBConnectionString 'Data Source=Server Name;Initial Catalog=SbGatewayDatabase;Integrated Security=True;Encrypt=False' -CertificateAutoGenerationKey $SBCertificateAutoGenerationKey -MessageContainerDBConnectionString 'Data Source=Server Name;Initial
Catalog=SBMessageContainer01;Integrated Security=True;Encrypt=False' -Verbose;
# To be run in Workflow Manager PowerShell console that has both Workflow Manager and Service Bus installed.
# Create new WF Farm
$WFCertAutoGenerationKey = ConvertTo-SecureString -AsPlainText -Force -String 'Run As Password' -Verbose;
New-WFFarm -WFFarmDBConnectionString 'Data Source=Server Name;Initial Catalog=WFManagementDB;Integrated Security=True;Encrypt=False' -RunAsAccount 'Domain\Account' -AdminGroup 'Domain\Domain Group' -HttpsPort 12290 -HttpPort 12291 -InstanceDBConnectionString
'Data Source=Server Name;Initial Catalog=WFInstanceManagementDB;Integrated Security=True;Encrypt=False' -ResourceDBConnectionString 'Data Source=Server Name;Initial Catalog=WFResourceManagementDB;Integrated Security=True;Encrypt=False' -CertificateAutoGenerationKey
$WFCertAutoGenerationKey -Verbose;
# Add SB Host
$SBRunAsPassword = ConvertTo-SecureString -AsPlainText -Force -String 'Run As Password' -Verbose;
Add-SBHost -SBFarmDBConnectionString 'Data Source=Server Name;Initial Catalog=SbManagementDB;Integrated Security=True;Encrypt=False' -RunAsPassword $SBRunAsPassword -EnableFirewallRules $true -CertificateAutoGenerationKey $SBCertificateAutoGenerationKey -Verbose;
Try
    # Create new SB Namespace
    New-SBNamespace -Name 'WorkflowDefaultNamespace' -AddressingScheme 'Path' -ManageUsers 'Domain\Account' -Verbose;
    Start-Sleep -s 90
Catch [system.InvalidOperationException]
# Get SB Client Configuration
$SBClientConfiguration = Get-SBClientConfiguration -Namespaces 'WorkflowDefaultNamespace' -Verbose;
# Add WF Host
$WFRunAsPassword = ConvertTo-SecureString -AsPlainText -Force -String 'Run As Password' -Verbose;
Add-WFHost -WFFarmDBConnectionString 'Data Source=Server Name;Initial Catalog=WFManagementDB;Integrated Security=True;Encrypt=False' -RunAsPassword $WFRunAsPassword -EnableFirewallRules $true -SBClientConfiguration $SBClientConfiguration -EnableHttpPort
-CertificateAutoGenerationKey $WFCertAutoGenerationKey -Verbose;
Thanks, Vijay Arockiasamy

Hi Vijay
uninstall this and install the one labeled Refresh 1
Kind Regards,
John Naguib
Senior Consultant
John Naguib Blog
John Naguib Twitter
Please remember to mark this as answered if it helped you

AppFabric and Service Bus

Can someone please tell me what Microsoft AppFabric 1.1 for Windows Server - is doing for SharePoint
and what about the Service Bus?
Reason for asking...got a WF issue...and I was advised to update the service bus...but that wouldn't update because the AppFabric was installed....

Windows Server AppFabric is installed as a prerequisite for SharePoint 2013. AppFabric is installed as an extension to the Windows Server Application Server Role and consist of two main components:
Distributed caching
Service and workflow management
An enterprise service bus (ESB)
is a software architecture model used for designing and implementing communication between mutually interacting software applications in a service-oriented
architecture (SOA).
Read these articles:
http://blogs.msdn.com/b/besidethepoint/archive/2013/03/27/appfabric-caching-and-sharepoint-1.aspx
SharePoint 2013: AppFabric and Distributed Cache Service
Hello Service Bus 1.0, Workflow 1.0 and SharePoint Workflow Host
MS Service Bus
[custom.development]

NotificationExec pop-up after installing Free Agent Drive Manager

I've just installed the Free Agent Drive Manager for a Maxtor 4 One Touch. Now I'm getting a NotificationExec pop-up after installing Free Agent Drive Manager. I've trashed the drive manager but I can't seem to get rid of the pop up. Any suggestions?

Hi Todd,
That's incompatible software, and from reading other posts, it sounds like even the official uninstaller does not get rid of everything. Do a Spotlight search for file name "NotificationExec" and "Free Agent Drive Manager" and include system and invisible files. Trash the files you find, empty your trash and you should be good to go.

After installing and configuring Workflow Manager and Service Bus, I'm getting 403.

Similar Messages

Maybe you are looking for