Workflow Manager 1.0 with SharePoint 2013

Hi Guys,
I understand as per below link that minimum three servers are required to provide high availability for Workflow Manager 1.0 in SharePoint 2013.
http://blogs.msdn.com/b/sanjaynarang/archive/2013/04/06/sizing-and-capacity-planning-for-sharepoint-2013-resources.aspx
Could anyone please point me Microsoft resources or let me know what needs to be installed on the three servers and Hardware pre-requisites? 
Thanks in advance.
Cheers, Badal

Hi Badal,
According to your description, my understanding is that you want to configure the high availability for Workflow Manager 1.0 with SharePoint 2013.
Per my knowledge, the three servers just have the same Hardware pre-requisites:
http://technet.microsoft.com/en-us/library/jj193466.aspx
You can use Network Load Balancing (NLB), Application Request Routing (ARR) or slightly less trivial with another load balancing solution to implement the high availability for Workflow Manager.
http://www.harbar.net/articles/wfm1.aspx
http://technet.microsoft.com/en-us/library/72646b45-646f-4dfb-ab52-e42f187655e7
Best regards.
Thanks
Victoria Xia
TechNet Community Support

Similar Messages

  • Errors when pairing Workflow Manager 1.0 with Sharepoint 2013 or trying to run C# samples to directly communicate with workflow manager

    When I try with Register-SPWorkflowService for SP2013 integration or run C# samples for workflow manager 1.0 I get
    "The  remote server returned an error: (404) Not found".
    With C# sample code runs,
    Scope '/$Activities' was not found.  HTTP headers received from the server - ActivityId: e268765f-9d95-47ed-81fd-c4b38f40bfe0. NodeId: XXXX. Scope: /$Activities/...
    The inner exception is:
    The remote server returned an error: (404) Not Found.
    We have got stuck here for a couple of days and...
    The workflow server runs on a dedicated machine than the SQL server for workflow farm DBs...
    I found one similar complain for the pre-release versions of the workflow and service bus etc.
    Help please...
    muharrem
    Muharrem

    Hi,I had already done disableloopbackcheck and it did not matter.No problem with creating scopes (using powershell) but pairing fails anyway.Here is the config from a local explorer connection to the HTTPS port:(And following it, you may see the result of
    a scope enumerator script)
    <?xml version="1.0"?>
    <ScopeInfo xmlns="http://schemas.microsoft.com/workflow/2012/xaml/activities" xmlns:i="http://www.w3.org/2001/XMLSchema-instance">
    <ChildScopeCount>3</ChildScopeCount>
    <DefaultWorkflowConfiguration/>
    <Description>For / sample only</Description>
    <LastModified>2013-11-08T21:22:00.967</LastModified>
    <LastRevised>2013-11-08T00:04:31.88</LastRevised>
    <Path>/</Path>
    <SecurityConfigurations>
    <ScopedSecurityConfiguration i:type="WindowsSecurityConfiguration">
    <Name>Microsoft.Workflow.Management.Security.WindowsSecurityConfiguration</Name>
    <WorkflowAdminGroupName>altemis\WorkflowAdmins</WorkflowAdminGroupName>
    </ScopedSecurityConfiguration>
    </SecurityConfigurations><
    Status>Active</Status>
    </ScopeInfo>
    PS C:\Shared> C:\Shared\WF Script-Enumaret Scopes.ps1
    Name:
    Path: /
    Status: Active
    User Comments: For / sample only
    Parent: None
    Children: 3
    Exception calling "GetChildScopes" with "0" argument(s): "Scope '/$ChildScopes' was not found.  HTTP headers received from 
    the server - ActivityId: 616224db-0321-450a-92ef-f03384c008a2. NodeId: ALTEMIS-SVR02. Scope: /$ChildScopes. Client 
    ActivityId : 649dba85-dc89-0002-d9bf-9d6489dcce01."
    At C:\Shared\WF Script-Enumaret Scopes.ps1:21 char:9
    +         $manager.GetChildScopes() | % { WriteScopeInfo $scopeUri $_.Path $scope. ...
    +         ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
        + CategoryInfo          : NotSpecified: (:) [], MethodInvocationException
        + FullyQualifiedErrorId : ScopeNotFoundException
    Muharrem

  • Work Manager Configuration Issue with SharePoint 2013

    Hi,
    We are facing issue to configure the Workflow Manager with SharePoint 2013.
    ===========================================================
    Please provide any solution/inputs to resolve this issue.
    Thanks.

    Hi ,
    According to your description, my understanding is that you got an error when you configured Workflow Manager for SharePoint 2013.
    For resolving your issue, please do as the followings:
     1.Start -> Programs -> Workflow Manager 1.0 -> Workflow Manager Configuration -> Remove from Farm     (not to be confused with SharePoint “farm”)
     2.Drop SQL databases for Workflow Manager.   (SbGatewayDatabase, SbManagementDB, SBMessageContainer01, WFInstanceManagementDB, WFManagementDB, WFResourceManagementDB)
     3.Start-> Programs-> Workflow Manager 1.0 -> Workflow Manager Configuration -> Configure Workflow Manager with Default Settings (Recommended)
     4.Ran the wizard just like before and it should be completed successfully this time.
    More information, please refer to the link below:
    http://www.spjeff.com/tag/workflow-manager-1-0/
    I hope this helps.
    Thanks,
    Wendy
    Wendy Li
    TechNet Community Support

  • Getting Error while Installing Workflow Manager 1.0 on Sharepoint 2013 On-Prem server

    I am trying to install Workflow Manager 1.0 on our SharePoint Server 2013 which is On-Prem installation. The SharePoint Server 2013 is functioning correctly. During the installation of Workflow Manager 1.0 on the same SharePoint 2013 server, I receive the
    following message: "Port number 9355 specified for HTTPS Port is blocked" I have checked our firewall Inbound rules and this port is not blocked.
    Any reason why this could be happening or did I miss anything?
    Thanks Snehal H.Rana SharePoint Consultant

    I am happy to inform you that I was able to resolve this error. I configured this on different ports other than 9355. We need to modify 2 files called "ClusterManifest.1.0.xml" and "ClusterManifest.current.xml" in c:\Program
    Files\Windows Fabric\Bin. They were pointing to older FQDN under following node:
     <NodeList>
            <Node NodeName="yourserverfqdn" IPAddressOrFQDN="yourserverfqdn" IsSeedNode="true" NodeTypeRef="DefaultNodeType" />
          </NodeList>
    These files won't let you edit directly in notepad so you will need to make a copy of these files (just in case). Open up the notepad as "Run As Administrator". Drag these files to the notepad. After you are done editing, save these as original
    names but make sure that the extension is .xml
    You will also need to do IISReset
    That did the trick for me.
    Thanks Snehal H.Rana SharePoint Consultant

  • Update Managed Metadata field in SharePoint 2013 Designer Workflow for O365

    Hi Guys,
    I need to update the managed metadata field in SharePoint Custom List using Workflow but its not working. I have also tried to use the HTTP WebService POST Operation but no luck.
    Am doing this for a SharePoint Online (O365) Site.
    Has anyone worked on something similar and was able to get it running ?
    I saw a post to create a custom Workflow Activity but I don't have a choice to go with the custom code option.
    http://patrickboom.wordpress.com/2013/07/23/workflow-activity-set-managed-metadata-column/
    I was able to achieve this by creating a SP 2010 based Workflow for O365. Which means that it worked well with SP 2010.
    Is there a different way to do it in 2013 ? I tried almost all options apart from creating custom Activity but nothing worked out. 
    Any help would be great.
    Thanks,
    Nutan
    Nutan Sharma

    Hi Nutan,
    According to your description, my understanding is that you want to update Managed Metadata field with SharePoint 2013 Designer for SharePoint Online.
    As far as I know, there is not an OOB action to achieve your requirement with SharePoint 2013 Designer for SharePoint 2013. Customizing a workflow action is a better option to achieve it.  Why didn’t you customize a workflow action as Patrick’s blog?
    In addition, please take a look at the article about Nintex workflow, check whether it is useful for you:
    http://habaneroconsulting.com/insights/setting-managed-metadata-fields-in-a-nintex-workflow#.UykBSf6KDHo
    As this issue is about SharePoint Online, I suggest you create a new thread on SharePoint Online forum:
    http://social.technet.microsoft.com/Forums/en-US/home?forum=onlineservicessharepoint . More experts will assist you.
    I hope this helps.
    Thanks,
    Wendy
    Forum Support
    Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact
    [email protected]
    Wendy Li
    TechNet Community Support

  • SSRS 2012 report integrated with SharePoint 2013 issue :Report refreshing after some idle time

    we have SSRS 2012 report integrated with SharePoint 2013  , when we click on any toggle item after some idle time of 60 secs and try again to expand
    another toggle item then  complete report is getting refreshed and  if we are in child report it is redirecting to parent report. . we didn’t set any refreshing property at report level. I hope there will be some idle time setting at sharepoint site
    level.
    what we observed.
    1. there is no problem when we expand toggle items without any idle time.
    2. when we open the report and expand few toggles and keep idle for 60 seconds and try
    again to expand another toggle item then  complete report is getting refreshed (all toggle items are collapsing).
    3. If you keep idle for 60 minutes and if you didn’t do any action like expanding toggle
    items it is not refreshing.
    why it is happening and how to stop that complete refresh.
    Surendra Thota

    Hi Surendra,
    I have tested on my local environment and the issue can be caused by the session time out ,the time out of the report precessing, database timeout,DataSet query execution timeout and so on.
    I would like to confirm that the refresh you have mentioned is the page refresh or the report reloading?
    Please reference to the setting below to don't limit the timeout values if you got the report reloading:
    Point to a report in the library.
    Click the down arrow, and select Manage processing options.
    In Processing Time-out, select Do not time out report processing or
    Limit report processing in seconds if you want to override that value with no time-out or different time-out values.
    If you got the session timeout that refresh the page, please reference to the setting in below article:
    http://msdn.microsoft.com/en-us/library/gg492284.aspx#bkmk_session_settings_section
    Details information in the article below about the timeout setting for your reference:
    Set Processing Options (Reporting Services in SharePoint Integrated Mode)
    If you still have any problem, please feel free to ask.
    Regards
    Vicky Liu
    If you have any feedback on our support, please click
    here.
    Vicky Liu
    TechNet Community Support

  • Error while running SSRS 2012 report integrated with SharePoint 2013

    Hi,
    Our reporting services environment has SSRS 2012 integrated with SharePoint 2013. The SharePoint 2013 farm has 2 web front ends, 1 app server and a separate server for reporting services i.e SSRS 2012 .
    We have created a https web application in SharePoint 2013 and all the SSRS 2012 reports are deployed into a "Report Library" residing in its root site collection.
    The simple reports are running well. But there is a report where we have 3 multi-value parameters. On running this report in IE or Chrome, we get the error "Sys.WebForms.PageRequestManagerParserErrorException: The message received from the
    server could not be parsed. Common causes for this error are when the response is modified by calls to Response.Write(), response filters, HttpModules, or server trace is enabled. Details: Error parsing near ' <!DOCTYPE html PUB'."
    Some of the forums suggested to add the below entry in the web config of the SharePoint web app where the SSRS reports are deployed. We did that too, still the error is appearing. Please can anyone help .
    <appSettings>
    <add key="aspnet:MaxHttpCollectionKeys" value="100000" />
    </appSettings>
    Thanks

    Hi Surendra,
    I have tested on my local environment and the issue can be caused by the session time out ,the time out of the report precessing, database timeout,DataSet query execution timeout and so on.
    I would like to confirm that the refresh you have mentioned is the page refresh or the report reloading?
    Please reference to the setting below to don't limit the timeout values if you got the report reloading:
    Point to a report in the library.
    Click the down arrow, and select Manage processing options.
    In Processing Time-out, select Do not time out report processing or
    Limit report processing in seconds if you want to override that value with no time-out or different time-out values.
    If you got the session timeout that refresh the page, please reference to the setting in below article:
    http://msdn.microsoft.com/en-us/library/gg492284.aspx#bkmk_session_settings_section
    Details information in the article below about the timeout setting for your reference:
    Set Processing Options (Reporting Services in SharePoint Integrated Mode)
    If you still have any problem, please feel free to ask.
    Regards
    Vicky Liu
    If you have any feedback on our support, please click
    here.
    Vicky Liu
    TechNet Community Support

  • Integrate SSRS Native Mode with Sharepoint 2013

    Hi, I have read numerous posts that go back and forth on the question "is SSRS Native Mode supported to work with SharePoint 2013?" and it seems like the answer is no, it is not. Even with SP1 like some people suggested it seems like it is impossible
    to integrate the two.
    In this case is the next step simply to somehow (IIS?) route the Report Server Web Service URL to a SharePoint page?
    What should I do with the fact that everyone in my domain can access the above mentioned URL?
    Thank you for any and all answers, I appreciate it!

    Hi Nestalna,
    As per my understanding, you want to allow everyone in your domain to access Report Server Web Service URL, but you don’t know how to grant permissions, then you think we can control permission using sharepoint, right?
    In native mode, we can grant permissions to access Report Server Web Service URL by following steps:
    From the Start menu, point to Programs, point to Administrative Tools, and then click Computer Management.
    Click to expand the Local Users and Groups node.
    Right-click Groups, then click New Group, type the name and description, then add domain users to the group.
    Start Report Manager.
    Click Site Settings.
    Click Security.
    Click New Role Assignment.
    In Group or user name, enter the group you created above.
    Select a system role, and then click OK.
    In this way, domain users can access report manager. If they want to view, add, and manage report server content, subscriptions, report processing, and report history, we need to assign Item-level role on specific folders or items to them. Besides, in earlier
    version of SQL Server 2012, we can configure Reporting Services to native or sharepoint integrated mode, from SQL Server 2012, we can configure Reporting Services to native and sharepoint integrated mode.
    For more information about Grant User Access to a Report Server, please refer to the following document:
    http://technet.microsoft.com/en-us/library/ms156034(v=SQL.105).aspx
    If you have any more questions, please feel free to ask.
    Thanks,
    Wendy Fu

  • When to use Managed Metadata service in Sharepoint 2013 and 2010

    Hi Folks,
    I have been working on sharepoint from quiet some time now. I have been using managed metadata service also.
    What I have not been able to find out so far is when should I be using MMS.
    What are the real advantages that I can draw out of it.
    I have one application that has Managed Metadata installed and has various terms stores and terms. 
    The Managed metadata service  created is utilized in search,
    What I do not know is what is why are we using it at all. 
    What is benefit of it.
    Managed metadata service could also be used in navigation is what i know.
    But what confused me is when is the best scenario to use it for navigation.
    Why can we not use the navigation provider in the managed metadata service. 
    There might be other uses also, but that is not clear to me.
    Can any one tell me why and in which scenario to really use it.
    I know how to configure the mms and how it works though the jargons around the managed metadata.
    Regards

    Managed Metadata has some specific advantages that make it useful for certain situations.
    A managed metadata column has the following advantages over a lookup or choice column:
    A managed metadata term set can be shared across the entire SharePoint farm, so you can use it in different site collections.
    You can set up "synonyms" so that multiple similar terms resolve to the same underlying piece of information
    Terms can be hierarchical (terms can be nested under other terms), and the SharePoint interface allows hierarchical filtering. For example, if I have a term set for Location, and one of my terms is North America, with terms below that for United States,
    Mexico, and Canada, I could choose to filter my list to show me all records with any North America location (inclusive of US, Mexico, and Canada), or to filter on a specific term (such as Mexico).
    You can allow people to enter new terms, which will then appear in the term set.
    You can specify information owners/stakeholders who maintain the term sets without them needing elevated access to sites; normally only site owners can mess with site columns and content types. Managed metadata lets you separate information management
    (what terms/synonyms should be used) from site management (granting access, creating groups and lists, etc).
    There are some disadvantages too. For example, with a lookup column, the lookup list can store additional columns of information. A managed metadata term set (on the other hand) only really stores terms (and descriptions/synonyms), but not related
    info. You might be tempted to do something like create a term set for part numbers, representing every part that your company produces; the term set would handle the part numbers just fine, but wouldn't let you add extra columns of information for
    description, weight, price, etc. In such a case, a lookup list is the better option.
    Microsoft has some suggested guidelines for when to use managed metadata/term store:
    SharePoint 2013:
    http://technet.microsoft.com/en-us/library/ee519604(v=office.15).aspx
    SharePoint 2010:
    http://technet.microsoft.com/en-us/library/ee519604(v=office.14).aspx
    A brief summary...
    Managed metadata is a good option when the potential metadata meets the following criteria:
    ​Is something for which a user will select a valid value​
    Represents information that is likely to be used multiple times
    ​Has valid values that can be organized hierarchically
    ​Includes synonyms or abbreviations that should be aggregated
    ​Can be applied in one language, but might be viewed in other languages
    Managed metadata is not a good option if the potential metadata meets any of the following criteria:
    Is represented by a built-in column (such as “last modified date”)
    ​Has an infinite number of valid values
    ​Has different valid values in each location that it is used (such as different values for the “version” attribute depending on which product team’s site the item appears in)*
    ​Has only “yes” and “no” as valid values
    *This type of metadata could still be captured in site collection-specific term stores

  • SharePoint 2010 search webservices compatibility with SharePoint 2013

    Please let us know whether the SharePoint 2010 search webservice is compatible with SharePoint 2013.
    When we try to hit the SharePoint 2013 search service with the query developed in the Sharepoint 2010 , we are getting "System.Not supported" exception as response from server.
    Below is the search query we are using:
    "<soap:Envelope xmlns:xsi=\"http://www.w3.org/2001/XMLSchema-instance\" xmlns:xsd=\"http://www.w3.org/2001/XMLSchema\" xmlns:soap=\"http://schemas.xmlsoap.org/soap/envelope/\">"
                + "<soap:Body>"
                + "<Query xmlns=\"urn:Microsoft.Search\">"
                + "<queryXml>"
                + "&lt;QueryPacket xmlns=\"urn:Microsoft.Search.Query\"&gt;"
                + "&lt;Query&gt;"
                + "&lt;Range&gt;&lt;StartAt&gt;1&lt;/StartAt&gt;&lt;Count&gt;50&lt;/Count&gt;&lt;/Range&gt;"
                + "&lt;SupportedFormats&gt;"
                + "&lt;Format&gt;urn:Microsoft.Search.Response.Document:Document&lt;/Format&gt;"
                + "&lt;/SupportedFormats&gt;"
                + "&lt;Context&gt;"
                + "&lt;QueryText type=\"MSSQLFT\"&gt; SELECT fileName,Title,Path,Write,SiteName,URL,FileExtension,isDocument,contentClass FROM scope() WHERE CONTAINS(Path, SITE_PORT)
    and (contentClass = 'STS_Web' OR contentClass = 'STS_ListItem_DocumentLibrary' OR contentClass = 'STS_List_DocumentLibrary') ORDER BY lastModifiedTime DESC &lt;/QueryText&gt;"
                + "&lt;/Context&gt;"
                + "&lt;/Query&gt;"
                + "&lt;/QueryPacket&gt;"
                + "</queryXml>"
                + "</Query>"
                + "</soap:Body>"
                + "</soap:Envelope>";
    Please  help

    Hi Raghuramk,
    is the web service is a search query web service? if yes, i suppose sharepoint 2013 already deprecated,
    Search Query web service
    Description: The Search Query web service is deprecated in SharePoint 2013.
    In SharePoint Server 2010, the Search Query web service exposes the SharePoint Enterprise Search capabilities to client applications. This enables you to access search results from client and web applications outside the context of a SharePoint site.
    Reason for change: The Search Query web service is deprecated because the client object model (CSOM) and a new REST-based web service are available for developing Office-wide extensibility scenarios. The CSOM exposes the same functionality
    as the Search Query web service, and a larger set of functionality for stand-alone client applications.
    http://technet.microsoft.com/en-us/library/ff607742.aspx#section2
    Regards,
    Aries
    Microsoft Online Community Support
    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

  • Excel web app Review tab with SharePoint 2013

    Is there a way to get the review tab to show up in Excel web app with SharePoint 2013 on-prem?  Users want to be able to use the "add comments" feature while in the excel web app.

    Hi,
    That functionality isn't available in Excel Web App on-premise. I just applied the Oct 2014 CU to WAC and do not have it, so the feature just hasn't made it down yet.
    You can use the "add comments" tab in excel client. 
    Here is a similar post, you can take a look at:
    https://social.technet.microsoft.com/Forums/office/en-US/b0f3ab85-8f46-484b-8fdb-407f57846b61/office-wep-app-review-tab-is-not-disponible?forum=sharepointgeneral
    Best Regards,
    Lisa Chen
    TechNet Community Support
    Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact
    [email protected]

  • Using Excel 2010 with SharePoint 2013 Excel services

    Hello:
    What features are we missing when using Excel 2010 (rather than Excel 2013) with SharePoint 2013 Excel services?
    Regards
    Jeff Gorvits

    Hi Jeff,
    You might want to read the articles below:
    https://support.office.com/en-us/article/Whats-new-in-Power-View-in-Excel-2013-and-in-SharePoint-Server-8e3b4259-421e-41fc-a48e-854388ad14d0?ui=en-US&rs=en-US&ad=US
    https://support.office.com/en-us/article/Version-compatibility-between-Power-Pivot-Data-Models-in-Excel-2010-and-Excel-2013-188f44fd-3cfd-4aa7-b4e6-a9402653cbf3?ui=en-US&rs=en-US&ad=US
    Regards,
    Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact
    [email protected] .
    Rebecca Tu
    TechNet Community Support

  • How to Use Team Foundation Server With SharePoint 2013 For Development

    Hi All,
    As i am new to team foundation server and i want to use team foundation server for our development. Please give me good startup point.

    Hi,
    If you wanted to integrate Team Foundation Server with SharePoint 2013,
    there are two articles for your reference:
    http://dumians.wordpress.com/2013/04/01/integrate-team-foundation-server-with-sharepoint-2013/
    http://nakedalm.com/integrate-sharepoint-2013-with-team-foundation-server-2013/
    By the way, you can also post the question in in Visual Studio Team Foundation Server forums and more experts will assist you.
    Team Foundation Server – General  http://social.msdn.microsoft.com/Forums/vstudio/en-US/home?forum=tfsgeneral
    More information:
    SharePoint Products requirements for Team Foundation Server:
    http://msdn.microsoft.com/en-us/library/hh667648.aspx
    Best Regards,
    Linda Li
    Linda Li
    TechNet Community Support

  • Will Office Web Apps Server 2013 work with SharePoint 2013 sites hosted in SP2010 compatibility mode?

    We are planning a upgrade of a SP2010 farm to 2013. There has been a bit of customization so we wish to run the old sites on the new SP2013 platform in SP2010 compatibility mode.
    So my question is will Office Web Apps Server 2013 work with the old sites hosted in compatibility mode?
    I found a similar query from March 2014 found here 
    http://sharepoint.stackexchange.com/questions/93101/office-web-apps-2010-running-on-sharepoint-2013-for-compatibility-mode-sites/116281#116281 
    Has there been an update released to resolve this
    Cheers D

    Hi  ,
    According to your description, my understanding is that you need to know whether Office Web Apps 2013 is working with SharePoint 2013 sites which is in SharePoint 2010 compatibility mode.
    For my test, Office Web Apps 2013 with SharePoint 2013 sites which is in SharePoint 2010 compatibility mode is working fine.
    Thanks,
    Eric
    Forum Support
    Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact
    [email protected]
    Eric Tao
    TechNet Community Support

  • Issues with SharePoint 2013 after upgrading from windows 2012 to 2012 r2

    We have a Sharepoint with Sp1 environment on windows 2012. Recently we upgraded the windows 2012 to 2012 r2. After the upgrade sharepoint environment is completely unstable.
    At first all the sites returned 401 errors. After resolving by resetting the object cache accounts the sites are back.
    Then i see that none of the performance point dashboards work. I figured that claims to windows token service is defaulted to local system account. I previously configured with a domain account. I reconfigured to work with domain account. 
    All the dashboard pages throw error.
           Some Error logs:Failed to get document content data. System.ComponentModel.Win32Exception (0x80004005): Cannot complete this function     at Microsoft.SharePoint.SPSqlClient.GetDocumentContentRow 
    Application error when access /Dashboards/Performance Dashboard/Main.aspx, Error=The EnableScriptGlobalization property cannot be changed during async postbacks or after the Init event.   at System.Web.UI.ScriptManager.set_EnableScriptGlobalization(Boolean
    value)    
      4.  I tried to create a new dashboard and this time the performancepoint designer wont launch. After some troubleshooting i see that c2w host file didnot have the caller  C:\Program Files\Windows Identity Foundation\v3.5. 
           I added <add value="WSS_WPG" /> and now it launches
      5.  Now the Dashboard launches and peruser identity works without having kerberos enabled at IIS. I have all the spn and required delegations setup for this url . But i did not configure at the IIS level
    yet.
    It looks like lot of things got messed up and reset. Can we upgrade to windows 2012 r2 with a sharepoint application inplace. what is the recommended approach and Whats happening with Performancepoint dashboards. IS there a known issue with sharepoint 2013
    sp1.
    Raj-Shpt

    Thanks for the above article. Few issues are solved . One of the main issue is with Performancepoint Dashboard.
     I have all the spn and required delegations setup for this url . But i did not configure at
    the IIS level yet. Still per user identity works without having kerberos enabled at IIS.
    Raj-Shpt

Maybe you are looking for