December 2, 2005 at 3:15 pm
I read several of the responses of how to execute a DTS package from QUERY ANALYZER. When I run the below DTS command from query analyzer, I received the following errors:
declare @package_name varchar(128)
declare @cmd varchar(255)
set @package_name = 'pistoltimport'
set @cmd =' dtsrun /Sservername /E /N ' + @package_name
execute master..xp_cmdshell @cmd
Error string: Disk or network error.
Error source: Microsoft JET Database Engine
Help file:
Help context: 5003043
Error: -2147467259 (80004005); Provider Error: -66847741 (FC03FC03)
December 2, 2005 at 3:23 pm
Check BOL. xp_cmdshell probably isn't running under the user you think it is, and the user it is running as probably doesn't have access to a UNC or share or drive mapping that the pckage is depending on.
From BOL:
When xp_cmdshell is invoked by a user who is a member of the sysadmin fixed server role, xp_cmdshell will be executed under the security context in which the SQL Server service is running. When the user is not a member of the sysadmin group, xp_cmdshell will impersonate the SQL Server Agent proxy account, which is specified using xp_sqlagent_proxy_account. If the proxy account is not available, xp_cmdshell will fail. This is true only for Microsoft® Windows NT® 4.0 and Windows 2000. On Windows 9.x, there is no impersonation and xp_cmdshell is always executed under the security context of the Windows 9.x user who started SQL Server.
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply