SQL Server 2014 support for Workflow Manager?

Is this configuration supported?
The prerequisite requirements for Workflow Manager are out of date and do not even list SQL 2012 R2 as a supported DB server.

Hi JB
We installed Workflow Manager 1.0 on a Dev SharePoint 2013 SP1 + April 2014 CU Farm running Against SQLServer 2014 which I suspect in not much different under the hood to your SQL2012R2.
Freelance consultant

Similar Messages

SQL Server 2014 supported for scheduled refresh?

The following link, which lists the supported data sources for scheduled refresh in Power BI, lists all versions of SQL Server from 2005 to 2012:
https://support.office.com/en-gb/article/Supported-Data-Sources-and-Data-Types-cb69a30a-2225-451f-a9d0-59d24419782e?ui=en-US&rs=en-GB&ad=GB
However 2014 is not listed. Is this an oversight or is SQL Server 2014 really not supported?
Thanks,
Chris
Check out my MS BI blog I also do
SSAS, PowerPivot, MDX and DAX consultancy and run
public SQL Server and BI training courses in the UK

Chris, have you heard about this?
I'm checking with our tech writing team.
Thanks!
Ed Price, Azure & Power BI Customer Program Manager (Blog,
Small Basic,
Wiki Ninjas,
Wiki)
Answer an interesting question?
Create a wiki article about it!

How do you allow SQL Server 2014 Express for remote connection and in firewall?

I'm sorry if this was answered here before.
I installed SQL Server 2014 Express and it is working perfectly. I want my server to be accessed through LAN. It is a named instance.
I searched the internet and here's what i did:
1. Through the SQL Configuration manager, I enabled all the Protocols of my Instance (TCP/IP, Named Pipes and Shared Memory). I changed in the IP Addresses the "IP ALL" TCP Dynamic Ports to 1434.
2. In the Firewall I made an Inbound Rule to allow the Program (%ProgramFiles% (x86)\Microsoft SQL Server\MSSQL12.MyInstance\MSSQL\Binn\sqlservr.exe)
3. I also made 2 Inbound Rules to allow (TCP/IP Port 1433) and (UDP Port 1434).
4. Restarted my instance. SQL Server Browser and SQL Server Reporting Services are also running.
5. No Luck I cant still access the server using a different computer in the network.
Please help.

Hello,
In Express Edition by default remote connections are disabled, you have to enable it first:
Configure the remote access Server Configuration Option
It's always a two way communication, so you have to create also outbound rules, not only inbound, and this on server as well as on client side; see
Configure a Windows Firewall for Database Engine Access
Olaf Helper
[ Blog] [ Xing] [ MVP]

Create MS SQL Server 2014 instance for TSQL2012 sample database Training kit (70-461)

Hi,
I just bought the Training kit (70-461) Querying Microsoft SQL server 2012. I downloaded Microsoft SQL Server 2014. I have also downloaded the script for the sample database -
TSQL2012.sql.
Basically I want to set up the sample database and practice my SQL queries. How do I log into
Microsoft SQL Server 2014? Basically I am doing this on my home computer. It is asking me for Server type, Server name, and Authentication. Do I have to set up a server instance to run and create the sample database? How?
Thanks.
Peter

Do you see anything in the Server Name at all?
So, in the first drop down you need to select Database Engine.
In the second (for Server Name) if you see anything, then try selecting it.
If there is nothing, try methods described in this article
http://sqlserver-help.com/2011/06/19/help-whats-my-sql-server-name/
to find the actual name.
Then, try choosing Windows Authentication and try connecting. If this would not work, then you do need to try using sa and sa's password. If there is no way to find that sa password, then perhaps it's better to clearly uninstall and re-install. If you want,
I'll move your thread into either 'Getting Started' or Data Access forum as it doesn't seem to be related with Transact SQL.
For every expert, there is an equal and opposite expert. - Becker's Law
My blog
My TechNet articles

SQL Server Enterprise support for Offline / Online Application development

Hi,
We have suggested to use the SQL Server 2012 as Database for our Enterprise application. We have the Offline/Online two set of application. Can you suggest any offline database to sync the Online SQL Server database.
Thanks,
Sethu

What is an offline database?
One can setup an "online" database and an "offline" database using SQL Server 2012 Enterprise Edition.
SSIS packages can be used to synch data between the databases:
http://blogs.msdn.com/b/jorgepc/archive/2010/12/07/synchronize-two-tables-using-sql-server-integration-services-ssis-part-i-of-ii.aspx?Redirected=true
Kalman Toth Database & OLAP Architect
SELECT Video Tutorials 4 Hours
New Book / Kindle: Exam 70-461 Bootcamp: Querying Microsoft SQL Server 2012

Unable to open power pivot dashboard excel files SQL server 2014 powerpivot for sharepoint

The Execute method of job definition Microsoft.AnalysisServices.SPAddin.UsageProcessingTimerJob (ID 726034a7-b9a9-45a6-b720-640b3f785e49) threw an exception. More information is included below. Call to Excel Services returned an
error.
System.InvalidOperationException: Call to Excel Services returned an error. ---> Microsoft.AnalysisServices.SPClient.Interfaces.ExcelServicesException: We're sorry. We ran into a problem completing your request
Ravi

HI, I got the solution SharePoint Web Services Root application pool was stopped
Faraz Javaid

SCVMM support for Microsoft SQL Server 2014

Hi
Does anybody know if Microsoft SQL Server 2014 supported and/or does it work, when installing SCVMM 2012. Current documentation stills says SQL Sever 2012.
Thanks

hi,
SQL Server 2014 is not supported: https://technet.microsoft.com/en-us/library/dn281933.aspx
I did not test if SQL 2014 works.
regards,
Thomas
Thomas Hanrath [MCT | Regional Lead Germany]
Thomas Hanrath Private Cloud Blog
Microsoft Learning and Certification Blog
Follow me on Twitter

SQL Server 2014 Express LocalDB automatic instance is not created

I have just installed SQL Server 2014 Developer Edition and noticed that there is no v12.0 automatic instance. Instead, there is MSSQLLocalDB automatic instance. Is this a bug?

Hi Alex,
According to your description, we need to verify if you install SQL Server 2014 Developer edition and SQL Server 2014 express edition. LocalDB is only just a lightweight version of Express version that has all its programmability features. If you install
SQL Server 2014 express LocalDB, please ensure you install automatic instances of LocalDB and not named instance of LocalDB. Usually,
when the target machine has the specified version of LocalDB installed, the automatic instance of
LocalDB for that version is available on the target machine as well. The name for the automatic instance is a single v character followed by the
LocalDB release version number in the format
xx.x. For example, v12.0 represents SQL Server 2014. For more information, see:
http://msdn.microsoft.com/en-us/library/hh510202(v=sql.120).aspx
If the issue still exists after checking the above suggestions, you can submit a feedback to Microsoft such issues, I would recommend to submit it to the Microsoft Connect at this link
https://connect.microsoft.com/SQLServer/Feedback. This connect site will serve as a connecting point between you and Microsoft, and ultimately the large community for you and Microsoft to
interact with. Your feedback enables Microsoft to offer the best software and deliver superior services, meanwhile you can learn more about and contribute to the exciting projects on Microsoft Connect.
Thanks,
Sofiya Li
If you have any feedback on our support, please click here.
Sofiya Li
TechNet Community Support

Microsoft Project Server Support for SQL Server 2014

Does anyone know the timeline for Microsoft Project Server to support deployment on SQL Server 2014? Also, has anyone tried this yet as an unsupported deployment, and if so, have they found any issues?

"SQL Server 2014 is not yet supported for Project Server 2013", as per the article Hardware
and software requirements for Project Server 2013: https://technet.microsoft.com/en-us/library/ee683978(v=office.15).aspx updated as on Dec
09, 2014.
Cheers! Happy troubleshooting !!! Dinesh S. Rai - MSFT Enterprise Project Management Please click Mark As Answer; if a post solves your problem or Vote As Helpful if a post has been useful to you. This can be beneficial to other community members reading
the thread.

Attunity SSIS connector support for Sql Server 2014?

Hello,
We've been successfully using Attunity SSIS connector 2.0 for a couple of years with SQL SERVER 2012.
We developed some Visual Studio projects and deployed them on our SSISDB. Then launch them with scheduled jobs. Everything worked fine.
After we upgraded the server to Sql Server 2014 the connector failed with the following error:
The connection type "MSORA" specified for connection manager "XXX" is not recognized as a valid connection manager type.
This error is returned when an attempt is made to create a connection manager for an unknown connection type. Check the spelling in the connection type name.
We tried uninstall/install but was no good. Also 32/64 bits combinations.
We tried DTEXEC utility and worked fine on sqlserver 2012 folder ( \110\DTS\Binn) but didn't work on 2014's folder ( \120\DTS\Binn).
We also tried a fresh 2014 installation but keep getting the same error.
Does Attunity connector 2.0 support Sql Server 2014? If not, should I wait for a new version? Any workaround?
For now, we are using the DTEXEC utility on 2012's folder, but since we have to use the /sql option (/ISSERVER is not working) we can't pass parameters to the .dtsx package.
Any help would be much appreciated.
Regards,
Daniel

I'm with Daniel - Microsoft should be taking the lead in resolving this. We downloaded the previous two versions from Microsoft Download (e.g. link below) with no indication that Microsoft would wash their hands of future support.
http://www.microsoft.com/en-us/download/details.aspx?id=29283
Attunity have replied on the thread on their forum - saying it is Microsoft's responsibility:
http://www.attunity.com/forums/microsoft-ssis-oracle-connector/attunity-ssis-connector-support-sql-server-2963.html
Trying to run, develop and support on parallel versions of SSIS is not a viable solution IMO.
I will advise all my clients who use these connectors not to upgrade to SQL Server 2014 until this is resolved.

Support for SQL Server 2014 for CMS + Audit Repository?

We are currently on BusinessObjects 4.1 SP01 Patch 6 on Windows Server 2008 using SQL Server 2008 R2 for our CMS and Audit repository databases. Is there any information out in regard to when SQL Server 2014 will be supported for the CMS and Audit repositories?
According to the Product Availability Matrix shown in the screenshot below SQL Server 2012 is supported, right? One of our DBAs claims there isn't that much of a difference between SQL Server 2012 and 2014, but I am not willing to try it if it isn't officially supported.
Thanks,
Noel

Denis Konovalov Henry Banks James Rapp Toby Johnston
Need your attention here.

Why is the PWDCOMPARE function not supported on an Azure SQL Server 2014 database

I have tried to publish a database from our local SQL Server to Azure but receive an error saying PWDCOMPARE is not supported with no link to a reason why.
We are using HASHBYTES function to encrypt passwords in our database and
PWDCOMPARE to validate them and we currently don't have an alternative (see article: http://sqlity.net/en/2460/sql-password-hash/). The PWDCOMPARE function is referenced by a stored procedure,
which is what won't publish to Azure.
It would be useful to know if it will be supported or if we should create a VM instead.
EDIT: Further Clarified question above, but basically the functions listed are documented in MSDN and there is no mention of them being undocumented unsupported features.
The error occurs when trying to publish a database to Azure from SQL Server 2014 Management Studio

Hi,
I am not an expert to answer this but am trying my best to answer this query.
Hashes a password and compares the hash to the hash of an existing password. PWDCOMPARE can be used to search for blank SQL Server login passwords or common weak passwords.
Syntax
PWDCOMPARE ( 'clear_text_password'
, password_hash
[ , version ] )
Note: This feature will be removed in the next version of Microsoft SQL Server. Do not use this feature in new development work, and modify applications that currently use this feature as soon as possible.
I am not sure whether this feature is not available on SQL 2014.
I think you can solve this issue by using the EXECUTE AS. Add this query into a procedure with EXECUTE AS with the user/login with sufficient permissions on the server.
Refer to belw link for more details on EXECUTE AS
http://msdn.microsoft.com/en-us/library/ms188354.aspx
create
procedure checkpassword
@UserName
SYSNAME
,@Password
VARCHAR(1000)
WITH
EXECUTE AS
'<UserName>'
as
select
pwdcompare(@Password,convert(nvarchar(128),password))
from master.dbo.syslogins
(nolock)
where name=@UserName
GO
EXEC checkpassword
@UserName='test',@Password='12345678'
Girish Prajwal

When will Attunity SSIS connector support SQL Server 2014?

When will Microsoft be releasing updates to the SSIS Attunity Connector for Oracle, to support SQL Server 2014?
Here's the link to the previous version released by Microsoft, for SQL Server 2012:
http://www.microsoft.com/download/en/details.aspx?id=29283
These are not compatible with SQL Server 2014, as described here:
http://social.msdn.microsoft.com/Forums/sqlserver/en-US/8a6ded27-8f6e-4957-82e3-18b26ee46817/action?threadDisplayName=attunity-ssis-connector-support-for-sql-server-2014
I have multiple clients holding off on SQL Server 2014 upgrades until this issue is resolved.

I think you are muddying the issue. Attunity themselves have not produced the last 2 versions of these components - they have been distributed by Microsoft e.g. the first link from my initial question.
The Attunity Development Manager has already posted a response on their own forum to a similar question stating that "The decision and timeframe in which the connectors will be released for SQL Server 2014 are at Microsoft's discretion and cannot provide
more information at this time."
http://www.attunity.com/forums/microsoft-ssis-oracle-connector/attunity-ssis-connector-support-sql-server-2963.html
So I want a response from Microsoft, stating when they will be addressing this.

Power Pivot Configuration error while refreshing connection on excel sheet for SharePoint 2013 and Sql server 2014

we are getting error while refreshing connection on excel sheet which containing data from data source in form of power pivot.
error is "An error occurred during an attempt to establish a connection to the external data source. The following connections failed to refresh:"
I am confused about Configuring the Analysis Service in SharePoint Mode.
What account should be used for Configuring the Analysis Service in SharePoint Mode?
what are the steps and what permissions are required and where to add it?
can you please explain in detail so i can make sure about my account permission properly in my environment?
Do we need to install Analysis service on sharepoint server box or not? if yes, then what are steps to follow it?
it is mentioned here to have two services are running under manages services under sharepoint central,
https://msdn.microsoft.com/en-us/library/jj682085.aspx#bkmk_verify_powerpivot
but we don't have SQL Server Analysis Services
running under Manage
services on server.
what need to be done here to fix this issue ?
Thanks,
Deepak Patel

Hi Deepak,
We are currently looking into this issue and will give you an update as soon as possible.
Thank you for your understanding and support.
Meanwhile, could you please check if there is any related ULS log for help troubleshoot the issue when error occurs.
http://social.technet.microsoft.com/wiki/contents/articles/3870.troubleshoot-powerpivot-data-refresh.aspx
http://blogs.technet.com/b/excel_services__powerpivot_for_sharepoint_support_blog/archive/2013/04/02/powerpivot-for-sharepoint-manual-data-refresh-failing.aspx
Thanks
Daniel Yang
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]

Hybrid Connection fails for Windows SQL Server 2014 - SSL Provider, error: 0 - The certificate chain was issued by an authority that is not trusted

Hello,
I have configured BizTalk Services Hybrid Connection between Standard Azure Website and SQL Server 2014 on premise.
Azure Management portal shows the status of Hybrid Connection as established.
However, the website throws an error when trying to open a connection
<
addname="DefaultConnection"
connectionString="Data
Source=machine name;initial catalog=AdventureWorks2012;Uid=demouser;Password=[my password];MultipleActiveResultSets=True"
providerName="System.Data.SqlClient"
/>
(The same website, with the same connection string deployed on SQL Server machine works correctly).
I tried various options with the connections sting (IP address instead of machine name, Trusted_Connection=False, Encrypt=False, etc. the result is the same
[Win32Exception (0x80004005): The certificate chain was issued by an authority that is not trusted]
[SqlException (0x80131904): A connection was successfully established with the server, but then an error occurred during the login process. (provider: SSL Provider, error: 0 - The certificate chain was issued by an authority that is not trusted.
I tried various machines - on premise and a clean Azure VM with SQL Server and it results in the same error - below full stack
The certificate chain was issued by an authority that is not trusted
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.
Exception Details: System.ComponentModel.Win32Exception: The certificate chain was issued by an authority that is not trusted
Source Error:
An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.
Stack Trace:
[Win32Exception (0x80004005): The certificate chain was issued by an authority that is not trusted]
[SqlException (0x80131904): A connection was successfully established with the server, but then an error occurred during the login process. (provider: SSL Provider, error: 0 - The certificate chain was issued by an authority that is not trusted.)]
System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection, Action`1 wrapCloseInAction) +5341687
System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj, Boolean callerHasConnectionLock, Boolean asyncClose) +546
System.Data.SqlClient.TdsParserStateObject.SNIWritePacket(SNIHandle handle, SNIPacket packet, UInt32& sniError, Boolean canAccumulate, Boolean callerHasConnectionLock) +5348371
System.Data.SqlClient.TdsParserStateObject.WriteSni(Boolean canAccumulate) +91
System.Data.SqlClient.TdsParserStateObject.WritePacket(Byte flushMode, Boolean canAccumulate) +331
System.Data.SqlClient.TdsParser.TdsLogin(SqlLogin rec, FeatureExtension requestedFeatures, SessionData recoverySessionData) +2109
System.Data.SqlClient.SqlInternalConnectionTds.Login(ServerInfo server, TimeoutTimer timeout, String newPassword, SecureString newSecurePassword) +347
System.Data.SqlClient.SqlInternalConnectionTds.AttemptOneLogin(ServerInfo serverInfo, String newPassword, SecureString newSecurePassword, Boolean ignoreSniOpenTimeout, TimeoutTimer timeout, Boolean withFailover) +238
System.Data.SqlClient.SqlInternalConnectionTds.LoginNoFailover(ServerInfo serverInfo, String newPassword, SecureString newSecurePassword, Boolean redirectedUserInstance, SqlConnectionString connectionOptions, SqlCredential credential, TimeoutTimer timeout) +892
System.Data.SqlClient.SqlInternalConnectionTds.OpenLoginEnlist(TimeoutTimer timeout, SqlConnectionString connectionOptions, SqlCredential credential, String newPassword, SecureString newSecurePassword, Boolean redirectedUserInstance) +311
System.Data.SqlClient.SqlInternalConnectionTds..ctor(DbConnectionPoolIdentity identity, SqlConnectionString connectionOptions, SqlCredential credential, Object providerInfo, String newPassword, SecureString newSecurePassword, Boolean redirectedUserInstance, SqlConnectionString userConnectionOptions, SessionData reconnectSessionData) +646
System.Data.SqlClient.SqlConnectionFactory.CreateConnection(DbConnectionOptions options, DbConnectionPoolKey poolKey, Object poolGroupProviderInfo, DbConnectionPool pool, DbConnection owningConnection, DbConnectionOptions userOptions) +278
System.Data.ProviderBase.DbConnectionFactory.CreatePooledConnection(DbConnectionPool pool, DbConnection owningObject, DbConnectionOptions options, DbConnectionPoolKey poolKey, DbConnectionOptions userOptions) +38
System.Data.ProviderBase.DbConnectionPool.CreateObject(DbConnection owningObject, DbConnectionOptions userOptions, DbConnectionInternal oldConnection) +732
System.Data.ProviderBase.DbConnectionPool.UserCreateRequest(DbConnection owningObject, DbConnectionOptions userOptions, DbConnectionInternal oldConnection) +85
System.Data.ProviderBase.DbConnectionPool.TryGetConnection(DbConnection owningObject, UInt32 waitForMultipleObjectsTimeout, Boolean allowCreate, Boolean onlyOneCheckConnection, DbConnectionOptions userOptions, DbConnectionInternal& connection) +1057
System.Data.ProviderBase.DbConnectionPool.TryGetConnection(DbConnection owningObject, TaskCompletionSource`1 retry, DbConnectionOptions userOptions, DbConnectionInternal& connection) +78
System.Data.ProviderBase.DbConnectionFactory.TryGetConnection(DbConnection owningConnection, TaskCompletionSource`1 retry, DbConnectionOptions userOptions, DbConnectionInternal oldConnection, DbConnectionInternal& connection) +196
System.Data.ProviderBase.DbConnectionInternal.TryOpenConnectionInternal(DbConnection outerConnection, DbConnectionFactory connectionFactory, TaskCompletionSource`1 retry, DbConnectionOptions userOptions) +146
System.Data.ProviderBase.DbConnectionClosed.TryOpenConnection(DbConnection outerConnection, DbConnectionFactory connectionFactory, TaskCompletionSource`1 retry, DbConnectionOptions userOptions) +16
System.Data.SqlClient.SqlConnection.TryOpenInner(TaskCompletionSource`1 retry) +94
System.Data.SqlClient.SqlConnection.TryOpen(TaskCompletionSource`1 retry) +110
System.Data.SqlClient.SqlConnection.Open() +96
System.Data.EntityClient.EntityConnection.OpenStoreConnectionIf(Boolean openCondition, DbConnection storeConnectionToOpen, DbConnection originalConnection, String exceptionCode, String attemptedOperation, Boolean& closeStoreConnectionOnFailure) +44
[EntityException: The underlying provider failed on Open.]
System.Data.EntityClient.EntityConnection.OpenStoreConnectionIf(Boolean openCondition, DbConnection storeConnectionToOpen, DbConnection originalConnection, String exceptionCode, String attemptedOperation, Boolean& closeStoreConnectionOnFailure) +203
System.Data.EntityClient.EntityConnection.Open() +104
System.Data.Objects.ObjectContext.EnsureConnection() +75
System.Data.Objects.ObjectQuery`1.GetResults(Nullable`1 forMergeOption) +41
System.Data.Objects.ObjectQuery`1.System.Collections.Generic.IEnumerable<T>.GetEnumerator() +36
System.Collections.Generic.List`1..ctor(IEnumerable`1 collection) +369
System.Linq.Enumerable.ToList(IEnumerable`1 source) +58
CloudShop.Services.ProductsRepository.GetProducts() +216
CloudShop.Controllers.HomeController.Search(String SearchCriteria) +81
CloudShop.Controllers.HomeController.Index() +1130
lambda_method(Closure , ControllerBase , Object[] ) +62
System.Web.Mvc.ActionMethodDispatcher.Execute(ControllerBase controller, Object[] parameters) +14
System.Web.Mvc.ReflectedActionDescriptor.Execute(ControllerContext controllerContext, IDictionary`2 parameters) +193
System.Web.Mvc.ControllerActionInvoker.InvokeActionMethod(ControllerContext controllerContext, ActionDescriptor actionDescriptor, IDictionary`2 parameters) +27
System.Web.Mvc.Async.<>c__DisplayClass42.<BeginInvokeSynchronousActionMethod>b__41() +28
System.Web.Mvc.Async.<>c__DisplayClass8`1.<BeginSynchronous>b__7(IAsyncResult _) +10
System.Web.Mvc.Async.WrappedAsyncResult`1.End() +50
System.Web.Mvc.Async.AsyncControllerActionInvoker.EndInvokeActionMethod(IAsyncResult asyncResult) +32
System.Web.Mvc.Async.<>c__DisplayClass39.<BeginInvokeActionMethodWithFilters>b__33() +58
System.Web.Mvc.Async.<>c__DisplayClass4f.<InvokeActionMethodFilterAsynchronously>b__49() +225
System.Web.Mvc.Async.<>c__DisplayClass37.<BeginInvokeActionMethodWithFilters>b__36(IAsyncResult asyncResult) +10
System.Web.Mvc.Async.WrappedAsyncResult`1.End() +50
System.Web.Mvc.Async.AsyncControllerActionInvoker.EndInvokeActionMethodWithFilters(IAsyncResult asyncResult) +34
System.Web.Mvc.Async.<>c__DisplayClass2a.<BeginInvokeAction>b__20() +23
System.Web.Mvc.Async.<>c__DisplayClass25.<BeginInvokeAction>b__22(IAsyncResult asyncResult) +99
System.Web.Mvc.Async.WrappedAsyncResult`1.End() +50
System.Web.Mvc.Async.AsyncControllerActionInvoker.EndInvokeAction(IAsyncResult asyncResult) +27
System.Web.Mvc.<>c__DisplayClass1d.<BeginExecuteCore>b__18(IAsyncResult asyncResult) +14
System.Web.Mvc.Async.<>c__DisplayClass4.<MakeVoidDelegate>b__3(IAsyncResult ar) +23
System.Web.Mvc.Async.WrappedAsyncResult`1.End() +55
System.Web.Mvc.Controller.EndExecuteCore(IAsyncResult asyncResult) +39
System.Web.Mvc.Async.<>c__DisplayClass4.<MakeVoidDelegate>b__3(IAsyncResult ar) +23
System.Web.Mvc.Async.WrappedAsyncResult`1.End() +55
System.Web.Mvc.Controller.EndExecute(IAsyncResult asyncResult) +29
System.Web.Mvc.Controller.System.Web.Mvc.Async.IAsyncController.EndExecute(IAsyncResult asyncResult) +10
System.Web.Mvc.<>c__DisplayClass8.<BeginProcessRequest>b__3(IAsyncResult asyncResult) +25
System.Web.Mvc.Async.<>c__DisplayClass4.<MakeVoidDelegate>b__3(IAsyncResult ar) +23
System.Web.Mvc.Async.WrappedAsyncResult`1.End() +55
System.Web.Mvc.MvcHandler.EndProcessRequest(IAsyncResult asyncResult) +31
System.Web.Mvc.MvcHandler.System.Web.IHttpAsyncHandler.EndProcessRequest(IAsyncResult result) +9
System.Web.CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() +9651188
System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously) +155
Version Information: Microsoft .NET Framework Version:4.0.30319; ASP.NET Version:4.0.30319.36213
Regards,
Michal
Michal Morciniec

Same issue here, looking for more information !

SQL Server 2014 support for Workflow Manager?

Similar Messages

Maybe you are looking for