April 15, 2009 at 7:14 am
Hi!
I'm trying to run SSIS package but I'm receiving following error!
Error: 2009-04-15 15:46:38.52
Code: 0xC0000033
Source: Test
Description: Integration Services evaluation period has expired.
End Error
Warning: 2009-04-15 15:46:38.54
Code: 0x80047034
Source: Go go go DTS.Pipeline
Description: The DataFlow task has no components. Add components or remove the task.
End Warning
I've 2 servers - SQL and application server and I'm trying to execute it from application server via batch file, but it fails. I can run it if the same batch file is executed on SQL server.
Dtexec /Ser "server name" /SQ "Test" /U "sa" /P "password"
BTW! DataFlow task has components added!
Could you please help me, I can't use SQL Job because I have to track execution progress of this package.
April 15, 2009 at 8:31 am
Are you running a Trial version? Maybe it has expired and wont let you carry on using it...
Hint:
Description: Integration Services evaluation period has expired.
April 16, 2009 at 12:49 am
It can't be the case I'm using STANDARD edition all way long. Although I only yesterday installed tools to execute DTSExec from application server but SQL Native Client and SQL CMD Query Tool was already installed some time ago. Does these tools have evaluation period?
April 16, 2009 at 7:35 am
ugis.revelis (4/15/2009)
Hi!I'm trying to run SSIS package but I'm receiving following error!
Error: 2009-04-15 15:46:38.52
Code: 0xC0000033
Source: Test
Description: Integration Services evaluation period has expired.
End Error
Warning: 2009-04-15 15:46:38.54
Code: 0x80047034
Source: Go go go DTS.Pipeline
Description: The DataFlow task has no components. Add components or remove the task.
End Warning
I've 2 servers - SQL and application server and I'm trying to execute it from application server via batch file, but it fails. I can run it if the same batch file is executed on SQL server.
Dtexec /Ser "server name" /SQ "Test" /U "sa" /P "password"
BTW! DataFlow task has components added!
Could you please help me, I can't use SQL Job because I have to track execution progress of this package.
When you execute a package from your application server, it is in fact executed on your application server using the local machine resources. The remote server simply serves as a store providing only the package file. You have to find a way to run the execution command on the SQL Server remotely.
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply