SQLDUMPER error when trying to change packageID using dtutil for pkg stored in msdb
-
Hi All,
I’m having a problem changing the ID of an SSIS package stored to the msdb. I have two subfolders, each underneath the MSDB folder, named MsdbTest and MsdbProd. The programmer develops the package on the client and then imports the package into \MSDB\MsdbTest on the QA Sql Server under his ownership. This allows the programmer to test the package on the server until it’s ready for production. At this point a dba (sa) imports the package into \MSDB\MsdbProd under dba ownership. But I need the production package to have a different ID than the test package (package name is the same, e.g. LoadMyTables). When I run the following command I get a SQLDUMPER_ERRORLOG as shown. It also creates a SqlDmpr0001.mdmp file in C:\Program Files\Microsoft SQL Server\90\Shared\ErrorDumps.
dtutil /I /DTS "MSDB\MsdbProd\LoadMyTables"
09/19/07 11:06:10, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Input parameters: 4 supplied
09/19/07 11:06:10, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, ProcessID = 3224
09/19/07 11:06:10, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, ThreadId = 0
09/19/07 11:06:10, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Flags = 0x0
09/19/07 11:06:10, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, MiniDumpFlags = 0x0
09/19/07 11:06:10, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, SqlInfoPtr = 0x01011590
09/19/07 11:06:10, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, DumpDir = <NULL>
09/19/07 11:06:10, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, ExceptionRecordPtr = 0x00000000
09/19/07 11:06:10, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, ContextPtr = 0x00000000
09/19/07 11:06:10, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, ExtraFile = <NULL>
09/19/07 11:06:10, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, InstanceName = <NULL>
09/19/07 11:06:10, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, ServiceName = <NULL>
09/19/07 11:06:10, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Callback type 11 not used
09/19/07 11:06:10, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Callback type 7 not used
09/19/07 11:06:10, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, MiniDump completed: C:\Program Files\Microsoft SQL Server\90\Shared\ErrorDumps\SQLDmpr0004.mdmp
09/19/07 11:06:11, ACTION, dtutil.exe, Watson Invoke: No
The server is Windows Server 2003 with Sql Server 2000 sp3 and Sql Server 2005 sp1 installed . The package is very simple, with no Config file or other supporting files. When it was imported to the server, the protection level was set to ‘rely on sql server’. The programmer was granted the db_dstltduser role in the msdb database. Everything is using Windows Authentication. Does anyone have any ideas? By the way, I can run the following commands successfully:
dtutil /Ex /DTS "MSDB\MsdbProd\LoadMyTables" -- works; returns "The specified package exists"
dtutil /Fdi DTS;"MSDB\LoadMyTables" --works; returns the 2 packages in the folder
dtutil /Fdi DTS;"MSDB;S" --works; returns the all packages in the all folders
-
Does the package run if you run it as a file and not from msdb, on the server, under the same context as agent?
Cheers,CrispinI can't die, there are too many people who still have to meet me!It's not a bug, SQL just misunderstood me!
-
Not sure what you mean. My question wasn't about running the package, but rather about getting a Sql dump when I try to use dtutil to regen the package ID. What I found out was, I don't think it matters. I wanted to make sure that if the package was changed under the msdbTest folder, it didn't modify the package under the msdbProd folder... and it doesn't.
The package relys on the version number under each folder. The modifications I make in test don't impact production until I import the package from msdbTest to msdbProd.
Still, it doesn't seem like dtutil should be throwing a Sql dump. 😀
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply