sql server - SSIS Package stalls when run as a SQL Job -


here short version of problem: have discrete dtsx file works fine on our production server, doesn't on our new dev server.

symptom: when run sql-server job, job starts , nothing @ happens, , never finishes... hangs, using little system resources.

some info: prod, packages developed on sql-server 2012 , run on nt 2008 server. new dev server sql-server 2012, runs on nt 2012 server (in case matters). have duplicated folder/file structure exactly, including drive name. package uses external dtsconfig file, said - folder/file structure identical.

the ssis service, sql-server agent, , remote login same, , member of server administrator group on dev box. if copy command line text sql job , run in cmd window using dtexec.exe, package executes correctly. job owner login, , "run as" sql-agent, - mentioned - same login. since in package uses integrated security, should running using same login whether on command line or via sql-agent, should eliminate user permission/credentials issues.

i tried adding ssis logging package, logging could. when run package command line, ton of messages in log. when run package via sql job, there no messages @ in log - nothing.

whatever going on, it's not getting far enough ssis package generate single log entry. it's stopping not exiting or throwing error. fwiw - have same problem every other package i've tried.

any ideas appreciated...

i found cause of problem. ms-sql server service using different login ssis server service , nt agent service (it using local service account).

once changed ms-sql server login match others (and restarted service), job ran correctly.


Comments

Popular posts from this blog

ruby - Trying to change last to "x"s to 23 -

jquery - Clone last and append item to closest class -

c - Unrecognised emulation mode: elf_i386 on MinGW32 -