Failed to Install SQL Server MDS Workflow Integration Service - sql-server

I tried to create a custom workflow by the following this article:
https://learn.microsoft.com/en-us/sql/master-data-services/develop/create-a-custom-workflow-master-data-services.
C:\Program Files\Microsoft SQL Server\130\Master Data
Services\WebApplication\bin>C:\Windows\Microsoft.NET\Framework\v4.0.30319\InstallUtil
Microsoft.MasterDataServices.Workflow.exe
Microsoft (R) .NET Framework
Installation utility Version 4.7.2053.0 Copyright (C) Microsoft
Corporation. All rights reserved.
System.BadImageFormatException: Could not load file or assembly
'file:///C:\Program Files\Microsoft SQL Server\130\Master Data
Services\WebApplication\bin\Microsoft.MasterDataServices.Workflow.exe'
or one of its dependencies. An attempt was made to load a program with
an incorrect format.
Any advice?
I'm running CMD with admin rights.

Solved. Just select 64 bit version.

Related

SSIS Error "To run a SSIS package outside of SQL Server Data Tools you must install Standard Edition (64-bit) of Integration Services "

I am using Visual studio ultimate 2012, SQL Server 2017 and Sql Server Data tools 2012. I am working with windows 10 64 bit.
My package consists of script tasks(c#) and Sql commands and it runs successfully from SSDT, but while trying to run my package from CMD i am getting
To run a SSIS package outside of SQL Server Data Tools you must install Standard Edition (64-bit) of Integration Services.
If i make another empty package and try to run it then it runs successfully too.
Please help.
(1) Integration Services (Shared feature) installation
I think that the issue is that you have installed SQL Server Data Tools (SSDT) for Visual Studio but you didn't install the Integration Services (Shared feature) from the SQL Server Installation which is necessary to execute .dtsx packages outside of visual studio.
For more information check the following link:
SSIS Error – “To run a SSIS package outside of SQL Server Data Tools you must install…”
(2) Execute using dtexec(32-bit)
Another thing you can try is to execute package via 32-bit dtexec.
As mentioned in the following Microsoft Documentation:
On a 64-bit computer, Integration Services installs a 64-bit version of the dtexec utility (dtexec.exe). If you have to run certain packages in 32-bit mode, you will have to install the 32-bit version of the dtexec utility. To install the 32-bit version of the dtexec utility, you must select either Client Tools or Business Intelligence Development Studio during setup.
By default, a 64-bit computer that has both the 64-bit and 32-bit versions of an Integration Services command prompt utility installed will run the 32-bit version at the command prompt. The 32-bit version runs because the directory path for the 32-bit version appears in the PATH environment variable before the directory path for the 64-bit version. (Typically, the 32-bit directory path is :\Program Files(x86)\Microsoft SQL Server\100\DTS\Binn, while the 64-bit directory path is :\Program Files\Microsoft SQL Server\100\DTS\Binn.)
More info at:
How to execute a package in 32-bit mode using dtexec.exe?
Also, similar issues was mentioned in other links, you can check them for more information:
SQL Server Central Forum - Run a SSIS package outside of SQL Server Data Tools you must install of Integration
Code Project - How To run a SSIS package outside of SQL Server Data Tools ?
MSDN - To run a SSIS package outside of SQL Server Data Tools you must install Standard Edition of Integration Services or higher
To run a SSIS package outside of SQL Server Data Tools you must install Move File to Archive of Integration Services or higher
SE DBA - Error: “To run a ssis package outside of sql server data tools you must install [send successful email] of Integration Services or higher.”
Adding to Hadi's answer, the change would be to use the right version which in my case was to use
C:\Program Files\Microsoft SQL Server\130\DTS\Binn>
Instead of
C:\Program Files (x86)\Microsoft SQL Server\130\DTS\Binn>
I had the same error and my integration services of 2017 was installed, so the suggested solution was not relevant.
i tried many options including uninstall and re-install, what solved finally was an upgrade to ENTERPRISE EDITION!
I found out that in a server where the dtexec ran successfully an ENTERPRISE VERSION was installed, while in the problematic server there was not an ENTERPRISE edition.
How did i find it? i ran the following in both servers:
run setup.exe file of SQL SERVER 2017 installation
on the left menu you will see "tools" - press the link
find: "installed SQL server features discovery report"
you will see in edition column an empty cell vs. "Enterprise Edition"
which is the successful one!
how did i upgrade in the problematic server?
run setup.exe file of SQL SERVER 2017 installation
on the left menu you will see "maintenance" - press the link
find: "edition upgrade"
follow the instructions, in my case since my organization had an automatic updated key i just pressed "next" a few times until a successful upgrade
good luck!

powershell script to automate installation of SQL Server 2014 management studio

I'm new to power shell and I want to automate the installation of SQL Server 2014 Management Studio on windows server using power shell and need to run remotely using chef cookbook.
PS C:\Users\vagrant\Downloads\SQLManagementStudio_x64_ENU> .\SETUP.EXE /ACTION=install /PARAMETER=true /Q /IACCEPTTHELIC
ENSETERMS=true
Microsoft (R) SQL Server 2014 12.00.2000.08
Copyright (c) Microsoft Corporation. All rights reserved.
The following error occurred:
The setting 'PARAMETER' specified is not recognized.
Error result: -2068578301
Result facility code: 1204
Result error code: 3
Please review the summary.txt log for further details
The PARAMETER in the documentation means that you put a parameter there that you want to adjust, not the word "PARAMETER". The parameters are listed in the Installation Parameters section.

No mapping between account names and security IDs was done - Install SQL Server MDS Workflow Integration Service

I try to create custom workflow by following article in https://learn.microsoft.com/en-us/sql/master-data-services/develop/create-a-custom-workflow-master-data-services.
I try to run InstallUtil Microsoft.MasterDataServices.Workflow.exe, but it failes. I wonder why.
I have specifed as servername\mds_workflow_service user when prompted during installation. I have just for case reset password to make sure that password is correct. The user have read and execute rights to the \bin folder. What could be wrong?
C:\Program Files\Microsoft SQL Server\130\Master Data Services\WebApplication\bin>InstallUtil Microsoft.MasterDataServices.Workflow.exe
Microsoft (R) .NET Framework Installation utility Version 4.7.2053.0
Copyright (C) Microsoft Corporation. All rights reserved.
Running a transacted installation.
Beginning the Install phase of the installation.
See the contents of the log file for the C:\Program Files\Microsoft SQL Server\130\Master Data Services\WebApplication\bin\Microsoft.MasterDataServices.Workflow.exe assembly's progress.
The file is located at C:\Program Files\Microsoft SQL Server\130\Master Data Services\WebApplication\bin\Microsoft.MasterDataServices.Workflow.InstallLog.
Installing assembly 'C:\Program Files\Microsoft SQL Server\130\Master Data Services\WebApplication\bin\Microsoft.MasterDataServices.Workflow.exe'.
Affected parameters are:
logtoconsole =
assemblypath = C:\Program Files\Microsoft SQL Server\130\Master Data Services\WebApplication\bin\Microsoft.MasterDataServices.Workflow.exe
logfile = C:\Program Files\Microsoft SQL Server\130\Master Data Services\WebApplication\bin\Microsoft.MasterDataServices.Workflow.InstallLog
An exception occurred during the Install phase.
System.ComponentModel.Win32Exception: No mapping between account names and security IDs was done
Solved by enterering service account in format in .\mds_workflow_service

SSIS runtime error /missing assembly when task is run

I couldn't find this error in the community.
"Microsoft.SqlServer.Dts.Tasks.WebServiceTask.WebserviceTaskException: Could not execute the Web method.”
The error complains an assembly reference is missing.
Some context: I'm running 1 WebServiceTask and I'm almost certain it's configured correctly since I read the docs. I'm using VS Community 2015 but also have an earlier VS 2013 with an expired developer license.
I think it could be related to this, perhaps SSIS is selecting the wrong assembly reference. Can this be resolved easily by deleting one? If not, how can I safely solve this issue?
64-bit Operating System, find the file Microsoft.SQLServer.ManagedDTS.dll in the following path:
C:\Program Files (x86)\Microsoft SQL Server\100\SDK\Assemblies
32-bit Operating System, find the file Microsoft.SQLServer.ManagedDTS.dll in the following path:
C:\Program Files\Microsoft SQL Server\100\SDK\Assemblies
The folder 90 under Microsoft SQL Server represents SQL Server 2005.
The folder 100 under Microsoft SQL Server represents SQL Server 2008.

ASCMD for SQL Server 2012

Till now, I used ascmd to execute some queries to SSAS 2008R2. My company begin to install some new SSAS 2012 servers and I want to re-use all my maintenance scripts with these new servers. I can't find any ascmd tool in SQL Server 2012 neither any documents or relatives on the internet.
Does anyone have some information about that? Or a link to download the tool?
When I try to execute a query with my version, i get the following message:
"Microsoft (R) Analysis Services 2008 Command Line Tool
Version 10.0.87.5 X86
Copyright (C) 2008 Microsoft Corporation. All Rights Reserved.
Ascmd: Exception trying to impersonate user: Could not load file o
crosoft.AnalysisServices, Version=10.0.0.0, Culture=neutral, Publi
5dcd8080cc91' or one of its dependencies. The system cannot find t
ied.
Ascmd: Execution failed: Could not load file or assembly 'Microsof
ices, Version=10.0.0.0, Culture=neutral, PublicKeyToken=89845dcd80
of its dependencies. The system cannot find the file specified."
When I check in C:\Windows\Assembly, I can see that I have the 11.0.0.0 version.
How can I deal with it? I can't use PowerShell script...
Thanks!
You can download the 2008 R2 Analysis Management Objects from this page. That includes the 10.0.0.0 version.
take the old ascmd solution from microsoft samples, delete the old reference dll and add new one it will solve ur problem

Resources