dbTalk Databases Forums  

Re: Using Dynamic Properties Task to Set and Call Execute Package Task

microsoft.public.sqlserver.dts microsoft.public.sqlserver.dts


Discuss Re: Using Dynamic Properties Task to Set and Call Execute Package Task in the microsoft.public.sqlserver.dts forum.



Reply
 
Thread Tools Display Modes
  #1  
Old   
Sean Walsh
 
Posts: n/a

Default Re: Using Dynamic Properties Task to Set and Call Execute Package Task - 10-08-2003 , 07:30 AM






Hi

I try this and get a message:
"Invalid GUID Specified"

I can get it to work without setting the package id in the DP task, but
i want to do it using the DP task as if I ever edit the package and
forget to re-delete the guid through disconnected edit, then it errors
again (as it has re-created the guid, which is then not found on the
STAGING server).

Any reasons/ideas why I get this error??

Thanks
Sean



*** Sent via Developersdex http://www.developersdex.com ***
Don't just participate in USENET...get rewarded for it!

Reply With Quote
  #2  
Old   
Allan Mitchell
 
Posts: n/a

Default Re: Using Dynamic Properties Task to Set and Call Execute Package Task - 10-08-2003 , 01:39 PM






Have you read this ?

Make the Execute Package Task name dependent only
(http://www.sqldts.com/default.aspx?216)

--
--

Allan Mitchell (Microsoft SQL Server MVP)
MCSE,MCDBA
www.SQLDTS.com
I support PASS - the definitive, global community
for SQL Server professionals - http://www.sqlpass.org

"Sean Walsh" <plugwalsh (AT) yahoo (DOT) com> wrote

Quote:
Hi

I try this and get a message:
"Invalid GUID Specified"

I can get it to work without setting the package id in the DP task, but
i want to do it using the DP task as if I ever edit the package and
forget to re-delete the guid through disconnected edit, then it errors
again (as it has re-created the guid, which is then not found on the
STAGING server).

Any reasons/ideas why I get this error??

Thanks
Sean



*** Sent via Developersdex http://www.developersdex.com ***
Don't just participate in USENET...get rewarded for it!



Reply With Quote
  #3  
Old   
Sean Walsh
 
Posts: n/a

Default Re: Using Dynamic Properties Task to Set and Call Execute Package Task - 10-09-2003 , 07:22 AM



Hi Allan

Yes, I have read that. That's where the abnormal behaviour comes in -
everyone else seems to assign a blank string to the PackageID property
using a Dynamic Task Property, and that works fine for them. I tried
that, but it gives me an error, "Invalid GUID Specified". When I open
the package and look at what it has done, it has set the value of the
PackageID to "<not displayable>". (You really just want this to be
blank, dont you?).

So that solution doesnt seem to work - and only in my case, as it
would appear!

Any ideas?
Sean



"Allan Mitchell" <allan (AT) no-spam (DOT) sqldts.com> wrote

Quote:
Have you read this ?

Make the Execute Package Task name dependent only
(http://www.sqldts.com/default.aspx?216)

--
--

Allan Mitchell (Microsoft SQL Server MVP)
MCSE,MCDBA
www.SQLDTS.com
I support PASS - the definitive, global community
for SQL Server professionals - http://www.sqlpass.org

"Sean Walsh" <plugwalsh (AT) yahoo (DOT) com> wrote in message
news:Obs47fZjDHA.1004 (AT) TK2MSFTNGP09 (DOT) phx.gbl...
Hi

I try this and get a message:
"Invalid GUID Specified"

I can get it to work without setting the package id in the DP task, but
i want to do it using the DP task as if I ever edit the package and
forget to re-delete the guid through disconnected edit, then it errors
again (as it has re-created the guid, which is then not found on the
STAGING server).

Any reasons/ideas why I get this error??

Thanks
Sean



*** Sent via Developersdex http://www.developersdex.com ***
Don't just participate in USENET...get rewarded for it!

Reply With Quote
  #4  
Old   
Allan Mitchell
 
Posts: n/a

Default Re: Using Dynamic Properties Task to Set and Call Execute Package Task - 10-09-2003 , 10:54 AM



What does it think the GUID is ?

Can you call LoadFromSQLServer leaving the GUID part blank ?



--
--

Allan Mitchell (Microsoft SQL Server MVP)
MCSE,MCDBA
www.SQLDTS.com
I support PASS - the definitive, global community
for SQL Server professionals - http://www.sqlpass.org

"Sean Walsh" <plugNOwalshSPAM (AT) yahoo (DOT) com> wrote

Quote:
Hi Allan

Yes, I have read that. That's where the abnormal behaviour comes in -
everyone else seems to assign a blank string to the PackageID property
using a Dynamic Task Property, and that works fine for them. I tried
that, but it gives me an error, "Invalid GUID Specified". When I open
the package and look at what it has done, it has set the value of the
PackageID to "<not displayable>". (You really just want this to be
blank, dont you?).

So that solution doesnt seem to work - and only in my case, as it
would appear!

Any ideas?
Sean



"Allan Mitchell" <allan (AT) no-spam (DOT) sqldts.com> wrote

Have you read this ?

Make the Execute Package Task name dependent only
(http://www.sqldts.com/default.aspx?216)

--
--

Allan Mitchell (Microsoft SQL Server MVP)
MCSE,MCDBA
www.SQLDTS.com
I support PASS - the definitive, global community
for SQL Server professionals - http://www.sqlpass.org

"Sean Walsh" <plugwalsh (AT) yahoo (DOT) com> wrote in message
news:Obs47fZjDHA.1004 (AT) TK2MSFTNGP09 (DOT) phx.gbl...
Hi

I try this and get a message:
"Invalid GUID Specified"

I can get it to work without setting the package id in the DP task,
but
i want to do it using the DP task as if I ever edit the package and
forget to re-delete the guid through disconnected edit, then it errors
again (as it has re-created the guid, which is then not found on the
STAGING server).

Any reasons/ideas why I get this error??

Thanks
Sean



*** Sent via Developersdex http://www.developersdex.com ***
Don't just participate in USENET...get rewarded for it!



Reply With Quote
Reply




Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off



Powered by vBulletin Version 3.5.3
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.