Starting
System.Management.Automation.CmdletInvocationException: An object or column name is missing or empty. For SELECT INTO statements, verify each column has a name. For other statements, look for empty alias names. Aliases defined as "" or [] are not allowed. Change the alias to a valid name.
An object or column name is missing or empty. For SELECT INTO statements, verify each column has a name. For other statements, look for empty alias names. Aliases defined as "" or [] are not allowed. Change the alias to a valid name.
An object or column name is missing or empty. For SELECT INTO statements, verify each column has a name. For other statements, look for empty alias names. Aliases defined as "" or [] are not allowed. Change the alias to a valid name. ---> System.Data.SqlClient.SqlException: An object or column name is missing or empty. For SELECT INTO statements, verify each column has a name. For other statements, look for empty alias names. Aliases defined as "" or [] are not allowed. Change the alias to a valid name.
An object or column name is missing or empty. For SELECT INTO statements, verify each column has a name. For other statements, look for empty alias names. Aliases defined as "" or [] are not allowed. Change the alias to a valid name.
An object or column name is missing or empty. For SELECT INTO statements, verify each column has a name. For other statements, look for empty alias names. Aliases defined as "" or [] are not allowed. Change the alias to a valid name.
    System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection, Action`1 wrapCloseInAction)
    System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj, Boolean callerHasConnectionLock, Boolean asyncClose)
    System.Data.SqlClient.TdsParser.TryRun(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj, Boolean& dataReady)
    System.Data.SqlClient.SqlCommand.FinishExecuteReader(SqlDataReader ds, RunBehavior runBehavior, String resetOptionsString)
    System.Data.SqlClient.SqlCommand.RunExecuteReaderTds(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, Boolean async, Int32 timeout, Task& task, Boolean asyncWrite)
    System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method, TaskCompletionSource`1 completion, Int32 timeout, Task& task, Boolean asyncWrite)
    System.Data.SqlClient.SqlCommand.InternalExecuteNonQuery(TaskCompletionSource`1 completion, String methodName, Boolean sendToPipe, Int32 timeout, Boolean asyncWrite)
    System.Data.SqlClient.SqlCommand.ExecuteNonQuery()
    System.Data.Linq.SqlClient.SqlProvider.Execute(Expression query, QueryInfo queryInfo, IObjectReaderFactory factory, Object[] parentArgs, Object[] userArgs, ICompiledSubQuery[] subQueries, Object lastResult)
    System.Data.Linq.SqlClient.SqlProvider.ExecuteAll(Expression query, QueryInfo[] queryInfos, IObjectReaderFactory factory, Object[] userArguments, ICompiledSubQuery[] subQueries)
    System.Data.Linq.SqlClient.SqlProvider.System.Data.Linq.Provider.IProvider.Execute(Expression query)
    Microsoft.ServiceBus.Commands.Common.ServerManagementStoreDataContext.CreateServerAdministratorLogin(String loginName)
    Microsoft.ServiceBus.Commands.Common.SecurityHelper.CreateServerAdministratorRole(String accountName, String connectionString)
    Microsoft.ServiceBus.Commands.NewSBFarmBase.InstallManagementDB(String connectionString, String adminGroup, String runAsName)
    Microsoft.ServiceBus.Commands.NewSBFarmBase.ProcessRecord()
   --- ---
    System.Management.Automation.PowerShell.EndInvoke(IAsyncResult asyncResult)
    Microsoft.Workflow.Deployment.ConfigWizard.CommandletHelper.InvokePowershell(Command command, Action`2 updateProgress)
    Microsoft.Workflow.Deployment.ConfigWizard.ProgressPageViewModel.CreateSBFarm(FarmCreationModel model)

the solution to this issue is the naming convention used in filling up the user account for workflow manager configuration 

the issue arrises with the use of  

the upnlogon which is of the format useraccount@***.com

if you use useraccount@AD 

it works 

that fixed the issue for me it just the naming convent to be used

the account should be in the format of accountname@domain

• Proposed as answer by José Salinas Francia Thursday, May 08, 2014 3:42 PM

Hi, I have tried in two separate environments to create a new workflow farm and am getting the same error. I have already installed the Feb CU for both workflow manager and the service bus. I rebooted all servers after installing. 

I noticed a message in the UI saying "Configuration operation failed. Please drop databases and use Create a New Farm again." When I look in SQL Management Studio no databases have been created. The new farm wizard fails on the first step.

Any ideas on a fix for this? Changing the format of the account as above didn't work for me. I am using a SQL alias on my server, would this cause any problems? When I test the connection to the DB from the wizard all tests pass.

• Proposed as answer by Ki Bang Tuesday, May 21, 2013 3:58 PM
• Unproposed as answer by Ki Bang Tuesday, May 21, 2013 3:58 PM

I would try to uninstall the workflow manager cumulative update and then try again. I had the same problem, looked on this forum, and that was the suggestion. I tried it and then I was able to configure the workflow manager and service bus just fine.

• Proposed as answer by Dennis Gaida Tuesday, June 11, 2013 8:40 PM
• Unproposed as answer by Dennis Gaida Tuesday, June 11, 2013 8:40 PM
• Proposed as answer by Dennis Gaida Tuesday, June 11, 2013 8:40 PM

As stupid as it is - uninstalling the CUs works. One can reinstall them afterwards.

I had this exact same issue. I hadn't installed he CUs yet for the service bus and workflow manager. Once I installed these two CUs, I was able to successfully configure using the workflow manager config wizard. Note, you'll be forced to install the service bus CU first. Then you'll need to exit out of the Microsoft Web Platform Installer and get back in to install the service bus CU. If you don't exit out between the installed, when you try to install the workflow manager CU, it only gives you the option to decline when installing it.

the solution to this issue is the naming convention used in filling up the user account for workflow manager configuration 

the issue arrises with the use of  

the upnlogon which is of the format useraccount@***.com

if you use useraccount@AD 

it works 

that fixed the issue for me it just the naming convent to be used

the account should be in the format of accountname@domain

I did this, It works!.

Thank you.

mallelarama's fix worked for me. 

I had specified the user account with a UPN suffix such as:

user@upnsuffix.net

The configuration utility requires that the user account be specified in NetBIOS format as follows:

user\NetBIOSName

What an awful and non-standard requirement....