尝试使用项目部署模型运行 dtexec 时出现 sqldumper 错误 [英] sqldumper error when trying to run dtexec with project deployment model
问题描述
我有一个包含多个包的 SSIS 项目，它使用项目部署模型，这意味着存在项目级参数和连接.
I have a SSIS project with several packages which uses the Project deployment model, which means that there are project level parameters and connections.
基于这个原因，要使用dtexec执行包，需要使用两个参数来指定项目，从中获取连接和参数，以及包.
Beacuse of this reason, to execute the packages using dtexec, it's necessary to use two parameters to specify the project, to get the connections and parameters from, and the package.
为此，首先您必须构建项目以获取将提供给 /project 参数的 .ispac 文件.
To do so, first you have to build the project to get the .ispac file which will be provided to the /project parameter.
然后你必须像这样调用 dtexec:
And then you have to invoke dtexec like this:
dtexec.exe /project ".ispac file name" /package ".dtsx file name"
问题是当我像这样调用 dtexec 时:
The problem is that when I invoke dtexec like this:
"c:\Program Files (x86)\Microsoft SQL Server\120\DTS\Binn\DTExec.exe"
/Package "d:\MyProjectPath\MyPackage.dtsx"
/Project "d:\MyProject\ProjectName.ispac"
我收到一个丑陋的 sqldumper 错误，如下所示:
I get an ugly sqldumper error, like this:
(3240:2660) 12/15/16 16:45:09, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, AdjustTokenPrivileges () completed with status (00000514)
(3240:2660) 12/15/16 16:45:09, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Input parameters: 4 supplied
(3240:2660) 12/15/16 16:45:09, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Parameter 1: 11176
(3240:2660) 12/15/16 16:45:09, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Parameter 2: 0
(3240:2660) 12/15/16 16:45:09, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Parameter 3: 0:0
(3240:2660) 12/15/16 16:45:09, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Parameter 4: 002FC778
(3240:2660) 12/15/16 16:45:09, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Parsed parameters:
(3240:2660) 12/15/16 16:45:09, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, ProcessID = 11176
(3240:2660) 12/15/16 16:45:09, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, ThreadId = 0
(3240:2660) 12/15/16 16:45:09, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Flags = 0x0
(3240:2660) 12/15/16 16:45:09, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, MiniDumpFlags = 0x0
(3240:2660) 12/15/16 16:45:09, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, SqlInfoPtr = 0x002FC778
(3240:2660) 12/15/16 16:45:09, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, DumpDir = <NULL>
(3240:2660) 12/15/16 16:45:09, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, ExceptionRecordPtr = 0x00000000
(3240:2660) 12/15/16 16:45:09, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, ContextPtr = 0x00000000
(3240:2660) 12/15/16 16:45:09, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, ExtraFile = <NULL>
(3240:2660) 12/15/16 16:45:09, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, PatternForExtraFiles = <NULL>
(3240:2660) 12/15/16 16:45:09, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, InstanceName = <NULL>
(3240:2660) 12/15/16 16:45:09, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, ServiceName = <NULL>
(3240:2660) 12/15/16 16:45:09, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Callback type 11 not used
(3240:2660) 12/15/16 16:45:09, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Callback type 15 not used
(3240:2660) 12/15/16 16:45:09, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Callback type 7 not used
(3240:2660) 12/15/16 16:45:09, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, MiniDump completed: C:\Program Files (x86)\Microsoft SQL Server\120\Shared\ErrorDumps\SQLDmpr0035.mdmp
(3240:2660) 12/15/16 16:45:09, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Total Buffer pool data pages filtered out: 0 KB
(3240:2660) 12/15/16 16:45:09, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Location of module 'dbghelp.dll' : 'C:\Program Files (x86)\Microsoft SQL Server\120\Shared\dbghelp.dll'
(3240:2660) 12/15/16 16:45:09, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, File version of module 'C:\Program Files (x86)\Microsoft SQL Server\120\Shared\dbghelp.dll' : '6.12:2.633'
(3240:2660) 12/15/16 16:45:09, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Product version of module 'C:\Program Files (x86)\Microsoft SQL Server\120\Shared\dbghelp.dll' : '6.12:2.633'
(3240:2660) 12/15/16 16:45:09, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Location of module 'sqldumper.exe' : 'C:\Program Files (x86)\Microsoft SQL Server\120\Shared\SQLDUMPER.EXE'
(3240:2660) 12/15/16 16:45:09, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, File version of module 'C:\Program Files (x86)\Microsoft SQL Server\120\Shared\SQLDUMPER.EXE' : '2014.120:2000.8'
(3240:2660) 12/15/16 16:45:09, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Product version of module 'C:\Program Files (x86)\Microsoft SQL Server\120\Shared\SQLDUMPER.EXE' : '12.0:2000.8'
(3240:2660) 12/15/16 16:45:09, ACTION, sysfer.dll, Watson Invoke: No
如何运行包而不出现该错误?
How can I run the package without getting that error?
推荐答案
问题很容易解决:在/package参数中，而不是像d:\那样指定包路径MyProjectPath\MyPackage.dtsx 你只需要指定包名，就像这样 MyPackage.dtsx
The problem is easy to solve: in the /package parameter, instead of specifying the package path like d:\MyProjectPath\MyPackage.dtsx you have to specify only the package name, like this MyPackage.dtsx
我认为解释是在部署的 .ispac 文件中搜索包，所以，如果你不指定包名，你会得到一个奇怪的错误.
I think the explanation is that the package is searched for inside the deployed .ispac file, so, if you don't specify the package name you get a weird error.
这篇关于尝试使用项目部署模型运行 dtexec 时出现 sqldumper 错误的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
