Correct approach to catching execution time errors in a custom task

Hi,

I'm building a custom task and just wondering what is the correct way of passing errors back to SSIS. Is there a rcommended approach to doing this. Currently I just wrap everything in a TRY...CATCH and use componentEvents to fire it back! Here's my code:

public override DTSExecResult Execute(Connections connections, VariableDispenser variableDispenser,IDTSComponentEvents componentEvents, IDTSLogging log, object transaction)
{
bool failed = false;
try
{
/*
* do stuff in here
*/
}
catch (Exception e)
{
componentEvents.FireError(-1, "", e.Message, "", 0);
failed = true;
}
if (failed)
{
return DTSExecResult.Failure;
}
else
{
return DTSExecResult.Success;
}
}

Any comments?

-Jamie

Anyone?|||the boolean flag isn't necessary. the line: return DTSExecResult.Failure;
could be in the catch block.|||

Good point. cheers Duane!! So it should be:

public override DTSExecResult Execute(Connections connections, VariableDispenser variableDispenser,IDTSComponentEvents componentEvents, IDTSLogging log, object transaction)
{
try
{
/*
* do stuff in here
*/

return DTSExecResult.Success;
}
catch (Exception e)
{
componentEvents.FireError(-1, "", e.Message, "", 0);
return DTSExecResult.Failure;
}
}

-Jamie

[Microsoft follow-up]

|||

Hi Jamie,

this looks like the correct approach to me.

sql

Correct approach to catching execution time errors in a custom task

Hi,

I'm building a custom task and just wondering what is the correct way of passing errors back to SSIS. Is there a rcommended approach to doing this. Currently I just wrap everything in a TRY...CATCH and use componentEvents to fire it back! Here's my code:

public override DTSExecResult Execute(Connections connections, VariableDispenser variableDispenser,IDTSComponentEvents componentEvents, IDTSLogging log, object transaction)
{
bool failed = false;
try
{
/*
* do stuff in here
*/
}
catch (Exception e)
{
componentEvents.FireError(-1, "", e.Message, "", 0);
failed = true;
}
if (failed)
{
return DTSExecResult.Failure;
}
else
{
return DTSExecResult.Success;
}
}

Any comments?

-Jamie

Anyone?|||the boolean flag isn't necessary. the line: return DTSExecResult.Failure;
could be in the catch block.|||

Good point. cheers Duane!! So it should be:

public override DTSExecResult Execute(Connections connections, VariableDispenser variableDispenser,IDTSComponentEvents componentEvents, IDTSLogging log, object transaction)
{
try
{
/*
* do stuff in here
*/

return DTSExecResult.Success;
}
catch (Exception e)
{
componentEvents.FireError(-1, "", e.Message, "", 0);
return DTSExecResult.Failure;
}
}

-Jamie

[Microsoft follow-up]

|||

Hi Jamie,

this looks like the correct approach to me.

copying sql server 6.5 to another machine

Hi All,
It is with great sadness that I am posing this question. I have been
assigned a task to copy the contents from one existing sql server 6.5 to a
new machine. I know .. I know.. its going to be a pain. I know its not
supported and all that. I can't find any article that explains how I can
copy databases and logins and all the pertinent information from one existin
g
server to a new machine.
Does anyone have any information on it? I would greatly appreciate it since
my knowledge of sql 6.4 is minimal.
Thanks in advance,
sqlgirlIs it possible for you to have the same directory structure on the both mach
ines?
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"sqlgirl" <sqlgirl@.discussions.microsoft.com> wrote in message
news:82C7C7C3-C332-4494-8630-E3B4C54B9976@.microsoft.com...
> Hi All,
> It is with great sadness that I am posing this question. I have been
> assigned a task to copy the contents from one existing sql server 6.5 to a
> new machine. I know .. I know.. its going to be a pain. I know its not
> supported and all that. I can't find any article that explains how I can
> copy databases and logins and all the pertinent information from one exist
ing
> server to a new machine.
> Does anyone have any information on it? I would greatly appreciate it sin
ce
> my knowledge of sql 6.4 is minimal.
> Thanks in advance,
> sqlgirl|||yes.. its possible to get the same directory structure.
The only problem is old server is NT 4.0.
the new one is Windows 2000 server.
Our ultimate goal is to use this new server as a test server to upgrade sql
6.5 to sql 2000.
Thanks
"Tibor Karaszi" wrote:

> Is it possible for you to have the same directory structure on the both ma
chines?
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
> Blog: http://solidqualitylearning.com/blogs/tibor/
>
> "sqlgirl" <sqlgirl@.discussions.microsoft.com> wrote in message
> news:82C7C7C3-C332-4494-8630-E3B4C54B9976@.microsoft.com...
>|||If you have the same directory structure, you could try:
Installing SQL Server on the new machine.
Stop both SQL Servers
Copy *all* the database device files to the new machine. Put in same directo
ry as on the source
machine. Default extension for database device file pre-7 is .DAT.
Start the new SQL Server.
sp_dropserver and sp_addserver on the new machine so that sysservers in mast
er is correct (read
about the LOCAL option for sp_addserver).
The last thing now would be your Windows logins. The mapping you have done i
n SQL Security Manager
is stored in some (to me) secret place. So you might need to re-create the W
indows logins (this
mapping) using SQL Security Manager. I'm vague on this point as I haven't t
ouched 6.5 for many
years now.
Above method is not supported. Supported method is backup/restore which is f
ar from as easy as it is
in the new architecture. Test thoroughly. Hire a consultant with 6.5 experie
nce if that makes you
sleep better.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"sqlgirl" <sqlgirl@.discussions.microsoft.com> wrote in message
news:EBC0B769-A304-4C1E-9096-24E1FFAB7DF6@.microsoft.com...[vbcol=seagreen]
> yes.. its possible to get the same directory structure.
> The only problem is old server is NT 4.0.
> the new one is Windows 2000 server.
> Our ultimate goal is to use this new server as a test server to upgrade sq
l
> 6.5 to sql 2000.
> Thanks
> "Tibor Karaszi" wrote:
>|||Hi,
To add on to the valuable informations from Tibor; Ensure that you install
the same service pack in both the server.
Prefered SQL 6.5 service pack is SP5a + Post SP5a update.
But try to upgrade your SQL Server version to 2000. If you have compatibiily
issues then upgrade the 6.5 database to 2000 and
keep your user databases compatibily level to 6.5
See sp_dbcmptlevel in SQL 2000 books online
Thanks
Hari
SQL Server MVP
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:esGmtSooFHA.1412@.TK2MSFTNGP09.phx.gbl...
> If you have the same directory structure, you could try:
> Installing SQL Server on the new machine.
> Stop both SQL Servers
> Copy *all* the database device files to the new machine. Put in same
> directory as on the source machine. Default extension for database device
> file pre-7 is .DAT.
> Start the new SQL Server.
> sp_dropserver and sp_addserver on the new machine so that sysservers in
> master is correct (read about the LOCAL option for sp_addserver).
> The last thing now would be your Windows logins. The mapping you have done
> in SQL Security Manager is stored in some (to me) secret place. So you
> might need to re-create the Windows logins (this mapping) using SQL
> Security Manager. I'm vague on this point as I haven't touched 6.5 for
> many years now.
> Above method is not supported. Supported method is backup/restore which is
> far from as easy as it is in the new architecture. Test thoroughly. Hire a
> consultant with 6.5 experience if that makes you sleep better.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
> Blog: http://solidqualitylearning.com/blogs/tibor/
>
> "sqlgirl" <sqlgirl@.discussions.microsoft.com> wrote in message
> news:EBC0B769-A304-4C1E-9096-24E1FFAB7DF6@.microsoft.com...
>|||> Ensure that you install the same service pack in both the server.
> Prefered SQL 6.5 service pack is SP5a + Post SP5a update.
Good thinking, Hari!
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"Hari Prasad" <hari_prasad_k@.hotmail.com> wrote in message
news:%232goMHpoFHA.2472@.tk2msftngp13.phx.gbl...
> Hi,
> To add on to the valuable informations from Tibor; Ensure that you install
the same service pack
> in both the server.
> Prefered SQL 6.5 service pack is SP5a + Post SP5a update.
> But try to upgrade your SQL Server version to 2000. If you have compatibii
ly issues then upgrade
> the 6.5 database to 2000 and
> keep your user databases compatibily level to 6.5
> See sp_dbcmptlevel in SQL 2000 books online
>
> Thanks
> Hari
> SQL Server MVP
> "Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote i
n message
> news:esGmtSooFHA.1412@.TK2MSFTNGP09.phx.gbl...
>|||Hi
As far as I remember, SQL Server 6.5 is not supported on Windows 2000. Only
up to NT4.0
Regards
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"sqlgirl" <sqlgirl@.discussions.microsoft.com> wrote in message
news:EBC0B769-A304-4C1E-9096-24E1FFAB7DF6@.microsoft.com...[vbcol=seagreen]
> yes.. its possible to get the same directory structure.
> The only problem is old server is NT 4.0.
> the new one is Windows 2000 server.
> Our ultimate goal is to use this new server as a test server to upgrade
> sql
> 6.5 to sql 2000.
> Thanks
> "Tibor Karaszi" wrote:
>|||Hmm, I'm pretty sure I had 6.5 running on my W2K pro machine. Doesn't mean i
t was supported, though
(important distinction). I know for sure I couldn't make it install on XP. I
don't remember whether
6.5 was/is supported on W2K, so running something where which isn't supporte
d anymore where the
config wasn't even supported to begin with probably isn't a good idea...
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"Mike Epprecht (SQL MVP)" <mike@.epprecht.net> wrote in message
news:uTXZAuqoFHA.1872@.TK2MSFTNGP10.phx.gbl...
> Hi
> As far as I remember, SQL Server 6.5 is not supported on Windows 2000. Onl
y up to NT4.0
> Regards
> --
> Mike Epprecht, Microsoft SQL Server MVP
> Zurich, Switzerland
> IM: mike@.epprecht.net
> MVP Program: http://www.microsoft.com/mvp
> Blog: http://www.msmvps.com/epprecht/
> "sqlgirl" <sqlgirl@.discussions.microsoft.com> wrote in message
> news:EBC0B769-A304-4C1E-9096-24E1FFAB7DF6@.microsoft.com...
>|||Mike Epprecht (SQL MVP) (mike@.epprecht.net) writes:
> As far as I remember, SQL Server 6.5 is not supported on Windows 2000.
> Only up to NT4.0
I'm pretty sure that SQL 6.5 SP5a was supported. In any case I do have
6.5 running on Windows 2000.
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se
Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techin.../2000/books.asp

copying sql server 6.5 to another machine

Hi All,
It is with great sadness that I am posing this question. I have been
assigned a task to copy the contents from one existing sql server 6.5 to a
new machine. I know .. I know.. its going to be a pain. I know its not
supported and all that. I can't find any article that explains how I can
copy databases and logins and all the pertinent information from one existing
server to a new machine.
Does anyone have any information on it? I would greatly appreciate it since
my knowledge of sql 6.4 is minimal.
Thanks in advance,
sqlgirlIs it possible for you to have the same directory structure on the both machines?
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"sqlgirl" <sqlgirl@.discussions.microsoft.com> wrote in message
news:82C7C7C3-C332-4494-8630-E3B4C54B9976@.microsoft.com...
> Hi All,
> It is with great sadness that I am posing this question. I have been
> assigned a task to copy the contents from one existing sql server 6.5 to a
> new machine. I know .. I know.. its going to be a pain. I know its not
> supported and all that. I can't find any article that explains how I can
> copy databases and logins and all the pertinent information from one existing
> server to a new machine.
> Does anyone have any information on it? I would greatly appreciate it since
> my knowledge of sql 6.4 is minimal.
> Thanks in advance,
> sqlgirl|||yes.. its possible to get the same directory structure.
The only problem is old server is NT 4.0.
the new one is Windows 2000 server.
Our ultimate goal is to use this new server as a test server to upgrade sql
6.5 to sql 2000.
Thanks
"Tibor Karaszi" wrote:
> Is it possible for you to have the same directory structure on the both machines?
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
> Blog: http://solidqualitylearning.com/blogs/tibor/
>
> "sqlgirl" <sqlgirl@.discussions.microsoft.com> wrote in message
> news:82C7C7C3-C332-4494-8630-E3B4C54B9976@.microsoft.com...
> > Hi All,
> >
> > It is with great sadness that I am posing this question. I have been
> > assigned a task to copy the contents from one existing sql server 6.5 to a
> > new machine. I know .. I know.. its going to be a pain. I know its not
> > supported and all that. I can't find any article that explains how I can
> > copy databases and logins and all the pertinent information from one existing
> > server to a new machine.
> >
> > Does anyone have any information on it? I would greatly appreciate it since
> > my knowledge of sql 6.4 is minimal.
> >
> > Thanks in advance,
> >
> > sqlgirl
>|||If you have the same directory structure, you could try:
Installing SQL Server on the new machine.
Stop both SQL Servers
Copy *all* the database device files to the new machine. Put in same directory as on the source
machine. Default extension for database device file pre-7 is .DAT.
Start the new SQL Server.
sp_dropserver and sp_addserver on the new machine so that sysservers in master is correct (read
about the LOCAL option for sp_addserver).
The last thing now would be your Windows logins. The mapping you have done in SQL Security Manager
is stored in some (to me) secret place. So you might need to re-create the Windows logins (this
mapping) using SQL Security Manager. I'm vague on this point as I haven't touched 6.5 for many
years now.
Above method is not supported. Supported method is backup/restore which is far from as easy as it is
in the new architecture. Test thoroughly. Hire a consultant with 6.5 experience if that makes you
sleep better.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"sqlgirl" <sqlgirl@.discussions.microsoft.com> wrote in message
news:EBC0B769-A304-4C1E-9096-24E1FFAB7DF6@.microsoft.com...
> yes.. its possible to get the same directory structure.
> The only problem is old server is NT 4.0.
> the new one is Windows 2000 server.
> Our ultimate goal is to use this new server as a test server to upgrade sql
> 6.5 to sql 2000.
> Thanks
> "Tibor Karaszi" wrote:
>> Is it possible for you to have the same directory structure on the both machines?
>> --
>> Tibor Karaszi, SQL Server MVP
>> http://www.karaszi.com/sqlserver/default.asp
>> http://www.solidqualitylearning.com/
>> Blog: http://solidqualitylearning.com/blogs/tibor/
>>
>> "sqlgirl" <sqlgirl@.discussions.microsoft.com> wrote in message
>> news:82C7C7C3-C332-4494-8630-E3B4C54B9976@.microsoft.com...
>> > Hi All,
>> >
>> > It is with great sadness that I am posing this question. I have been
>> > assigned a task to copy the contents from one existing sql server 6.5 to a
>> > new machine. I know .. I know.. its going to be a pain. I know its not
>> > supported and all that. I can't find any article that explains how I can
>> > copy databases and logins and all the pertinent information from one existing
>> > server to a new machine.
>> >
>> > Does anyone have any information on it? I would greatly appreciate it since
>> > my knowledge of sql 6.4 is minimal.
>> >
>> > Thanks in advance,
>> >
>> > sqlgirl
>>|||Hi,
To add on to the valuable informations from Tibor; Ensure that you install
the same service pack in both the server.
Prefered SQL 6.5 service pack is SP5a + Post SP5a update.
But try to upgrade your SQL Server version to 2000. If you have compatibiily
issues then upgrade the 6.5 database to 2000 and
keep your user databases compatibily level to 6.5
See sp_dbcmptlevel in SQL 2000 books online
Thanks
Hari
SQL Server MVP
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:esGmtSooFHA.1412@.TK2MSFTNGP09.phx.gbl...
> If you have the same directory structure, you could try:
> Installing SQL Server on the new machine.
> Stop both SQL Servers
> Copy *all* the database device files to the new machine. Put in same
> directory as on the source machine. Default extension for database device
> file pre-7 is .DAT.
> Start the new SQL Server.
> sp_dropserver and sp_addserver on the new machine so that sysservers in
> master is correct (read about the LOCAL option for sp_addserver).
> The last thing now would be your Windows logins. The mapping you have done
> in SQL Security Manager is stored in some (to me) secret place. So you
> might need to re-create the Windows logins (this mapping) using SQL
> Security Manager. I'm vague on this point as I haven't touched 6.5 for
> many years now.
> Above method is not supported. Supported method is backup/restore which is
> far from as easy as it is in the new architecture. Test thoroughly. Hire a
> consultant with 6.5 experience if that makes you sleep better.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
> Blog: http://solidqualitylearning.com/blogs/tibor/
>
> "sqlgirl" <sqlgirl@.discussions.microsoft.com> wrote in message
> news:EBC0B769-A304-4C1E-9096-24E1FFAB7DF6@.microsoft.com...
>> yes.. its possible to get the same directory structure.
>> The only problem is old server is NT 4.0.
>> the new one is Windows 2000 server.
>> Our ultimate goal is to use this new server as a test server to upgrade
>> sql
>> 6.5 to sql 2000.
>> Thanks
>> "Tibor Karaszi" wrote:
>> Is it possible for you to have the same directory structure on the both
>> machines?
>> --
>> Tibor Karaszi, SQL Server MVP
>> http://www.karaszi.com/sqlserver/default.asp
>> http://www.solidqualitylearning.com/
>> Blog: http://solidqualitylearning.com/blogs/tibor/
>>
>> "sqlgirl" <sqlgirl@.discussions.microsoft.com> wrote in message
>> news:82C7C7C3-C332-4494-8630-E3B4C54B9976@.microsoft.com...
>> > Hi All,
>> >
>> > It is with great sadness that I am posing this question. I have been
>> > assigned a task to copy the contents from one existing sql server 6.5
>> > to a
>> > new machine. I know .. I know.. its going to be a pain. I know its
>> > not
>> > supported and all that. I can't find any article that explains how I
>> > can
>> > copy databases and logins and all the pertinent information from one
>> > existing
>> > server to a new machine.
>> >
>> > Does anyone have any information on it? I would greatly appreciate it
>> > since
>> > my knowledge of sql 6.4 is minimal.
>> >
>> > Thanks in advance,
>> >
>> > sqlgirl
>>
>|||> Ensure that you install the same service pack in both the server.
> Prefered SQL 6.5 service pack is SP5a + Post SP5a update.
Good thinking, Hari!
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"Hari Prasad" <hari_prasad_k@.hotmail.com> wrote in message
news:%232goMHpoFHA.2472@.tk2msftngp13.phx.gbl...
> Hi,
> To add on to the valuable informations from Tibor; Ensure that you install the same service pack
> in both the server.
> Prefered SQL 6.5 service pack is SP5a + Post SP5a update.
> But try to upgrade your SQL Server version to 2000. If you have compatibiily issues then upgrade
> the 6.5 database to 2000 and
> keep your user databases compatibily level to 6.5
> See sp_dbcmptlevel in SQL 2000 books online
>
> Thanks
> Hari
> SQL Server MVP
> "Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in message
> news:esGmtSooFHA.1412@.TK2MSFTNGP09.phx.gbl...
>> If you have the same directory structure, you could try:
>> Installing SQL Server on the new machine.
>> Stop both SQL Servers
>> Copy *all* the database device files to the new machine. Put in same directory as on the source
>> machine. Default extension for database device file pre-7 is .DAT.
>> Start the new SQL Server.
>> sp_dropserver and sp_addserver on the new machine so that sysservers in master is correct (read
>> about the LOCAL option for sp_addserver).
>> The last thing now would be your Windows logins. The mapping you have done in SQL Security
>> Manager is stored in some (to me) secret place. So you might need to re-create the Windows logins
>> (this mapping) using SQL Security Manager. I'm vague on this point as I haven't touched 6.5 for
>> many years now.
>> Above method is not supported. Supported method is backup/restore which is far from as easy as it
>> is in the new architecture. Test thoroughly. Hire a consultant with 6.5 experience if that makes
>> you sleep better.
>> --
>> Tibor Karaszi, SQL Server MVP
>> http://www.karaszi.com/sqlserver/default.asp
>> http://www.solidqualitylearning.com/
>> Blog: http://solidqualitylearning.com/blogs/tibor/
>>
>> "sqlgirl" <sqlgirl@.discussions.microsoft.com> wrote in message
>> news:EBC0B769-A304-4C1E-9096-24E1FFAB7DF6@.microsoft.com...
>> yes.. its possible to get the same directory structure.
>> The only problem is old server is NT 4.0.
>> the new one is Windows 2000 server.
>> Our ultimate goal is to use this new server as a test server to upgrade sql
>> 6.5 to sql 2000.
>> Thanks
>> "Tibor Karaszi" wrote:
>> Is it possible for you to have the same directory structure on the both machines?
>> --
>> Tibor Karaszi, SQL Server MVP
>> http://www.karaszi.com/sqlserver/default.asp
>> http://www.solidqualitylearning.com/
>> Blog: http://solidqualitylearning.com/blogs/tibor/
>>
>> "sqlgirl" <sqlgirl@.discussions.microsoft.com> wrote in message
>> news:82C7C7C3-C332-4494-8630-E3B4C54B9976@.microsoft.com...
>> > Hi All,
>> >
>> > It is with great sadness that I am posing this question. I have been
>> > assigned a task to copy the contents from one existing sql server 6.5 to a
>> > new machine. I know .. I know.. its going to be a pain. I know its not
>> > supported and all that. I can't find any article that explains how I can
>> > copy databases and logins and all the pertinent information from one existing
>> > server to a new machine.
>> >
>> > Does anyone have any information on it? I would greatly appreciate it since
>> > my knowledge of sql 6.4 is minimal.
>> >
>> > Thanks in advance,
>> >
>> > sqlgirl
>>
>|||Hi
As far as I remember, SQL Server 6.5 is not supported on Windows 2000. Only
up to NT4.0
Regards
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"sqlgirl" <sqlgirl@.discussions.microsoft.com> wrote in message
news:EBC0B769-A304-4C1E-9096-24E1FFAB7DF6@.microsoft.com...
> yes.. its possible to get the same directory structure.
> The only problem is old server is NT 4.0.
> the new one is Windows 2000 server.
> Our ultimate goal is to use this new server as a test server to upgrade
> sql
> 6.5 to sql 2000.
> Thanks
> "Tibor Karaszi" wrote:
>> Is it possible for you to have the same directory structure on the both
>> machines?
>> --
>> Tibor Karaszi, SQL Server MVP
>> http://www.karaszi.com/sqlserver/default.asp
>> http://www.solidqualitylearning.com/
>> Blog: http://solidqualitylearning.com/blogs/tibor/
>>
>> "sqlgirl" <sqlgirl@.discussions.microsoft.com> wrote in message
>> news:82C7C7C3-C332-4494-8630-E3B4C54B9976@.microsoft.com...
>> > Hi All,
>> >
>> > It is with great sadness that I am posing this question. I have been
>> > assigned a task to copy the contents from one existing sql server 6.5
>> > to a
>> > new machine. I know .. I know.. its going to be a pain. I know its
>> > not
>> > supported and all that. I can't find any article that explains how I
>> > can
>> > copy databases and logins and all the pertinent information from one
>> > existing
>> > server to a new machine.
>> >
>> > Does anyone have any information on it? I would greatly appreciate it
>> > since
>> > my knowledge of sql 6.4 is minimal.
>> >
>> > Thanks in advance,
>> >
>> > sqlgirl
>>|||Hmm, I'm pretty sure I had 6.5 running on my W2K pro machine. Doesn't mean it was supported, though
(important distinction). I know for sure I couldn't make it install on XP. I don't remember whether
6.5 was/is supported on W2K, so running something where which isn't supported anymore where the
config wasn't even supported to begin with probably isn't a good idea...
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"Mike Epprecht (SQL MVP)" <mike@.epprecht.net> wrote in message
news:uTXZAuqoFHA.1872@.TK2MSFTNGP10.phx.gbl...
> Hi
> As far as I remember, SQL Server 6.5 is not supported on Windows 2000. Only up to NT4.0
> Regards
> --
> Mike Epprecht, Microsoft SQL Server MVP
> Zurich, Switzerland
> IM: mike@.epprecht.net
> MVP Program: http://www.microsoft.com/mvp
> Blog: http://www.msmvps.com/epprecht/
> "sqlgirl" <sqlgirl@.discussions.microsoft.com> wrote in message
> news:EBC0B769-A304-4C1E-9096-24E1FFAB7DF6@.microsoft.com...
>> yes.. its possible to get the same directory structure.
>> The only problem is old server is NT 4.0.
>> the new one is Windows 2000 server.
>> Our ultimate goal is to use this new server as a test server to upgrade sql
>> 6.5 to sql 2000.
>> Thanks
>> "Tibor Karaszi" wrote:
>> Is it possible for you to have the same directory structure on the both machines?
>> --
>> Tibor Karaszi, SQL Server MVP
>> http://www.karaszi.com/sqlserver/default.asp
>> http://www.solidqualitylearning.com/
>> Blog: http://solidqualitylearning.com/blogs/tibor/
>>
>> "sqlgirl" <sqlgirl@.discussions.microsoft.com> wrote in message
>> news:82C7C7C3-C332-4494-8630-E3B4C54B9976@.microsoft.com...
>> > Hi All,
>> >
>> > It is with great sadness that I am posing this question. I have been
>> > assigned a task to copy the contents from one existing sql server 6.5 to a
>> > new machine. I know .. I know.. its going to be a pain. I know its not
>> > supported and all that. I can't find any article that explains how I can
>> > copy databases and logins and all the pertinent information from one existing
>> > server to a new machine.
>> >
>> > Does anyone have any information on it? I would greatly appreciate it since
>> > my knowledge of sql 6.4 is minimal.
>> >
>> > Thanks in advance,
>> >
>> > sqlgirl
>>
>|||Mike Epprecht (SQL MVP) (mike@.epprecht.net) writes:
> As far as I remember, SQL Server 6.5 is not supported on Windows 2000.
> Only up to NT4.0
I'm pretty sure that SQL 6.5 SP5a was supported. In any case I do have
6.5 running on Windows 2000.
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se
Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techinfo/productdoc/2000/books.asp

copying sql server 6.5 to another machine

Hi All,
It is with great sadness that I am posing this question. I have been
assigned a task to copy the contents from one existing sql server 6.5 to a
new machine. I know .. I know.. its going to be a pain. I know its not
supported and all that. I can't find any article that explains how I can
copy databases and logins and all the pertinent information from one existing
server to a new machine.
Does anyone have any information on it? I would greatly appreciate it since
my knowledge of sql 6.4 is minimal.
Thanks in advance,
sqlgirl
Is it possible for you to have the same directory structure on the both machines?
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"sqlgirl" <sqlgirl@.discussions.microsoft.com> wrote in message
news:82C7C7C3-C332-4494-8630-E3B4C54B9976@.microsoft.com...
> Hi All,
> It is with great sadness that I am posing this question. I have been
> assigned a task to copy the contents from one existing sql server 6.5 to a
> new machine. I know .. I know.. its going to be a pain. I know its not
> supported and all that. I can't find any article that explains how I can
> copy databases and logins and all the pertinent information from one existing
> server to a new machine.
> Does anyone have any information on it? I would greatly appreciate it since
> my knowledge of sql 6.4 is minimal.
> Thanks in advance,
> sqlgirl
|||yes.. its possible to get the same directory structure.
The only problem is old server is NT 4.0.
the new one is Windows 2000 server.
Our ultimate goal is to use this new server as a test server to upgrade sql
6.5 to sql 2000.
Thanks
"Tibor Karaszi" wrote:

> Is it possible for you to have the same directory structure on the both machines?
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
> Blog: http://solidqualitylearning.com/blogs/tibor/
>
> "sqlgirl" <sqlgirl@.discussions.microsoft.com> wrote in message
> news:82C7C7C3-C332-4494-8630-E3B4C54B9976@.microsoft.com...
>
|||If you have the same directory structure, you could try:
Installing SQL Server on the new machine.
Stop both SQL Servers
Copy *all* the database device files to the new machine. Put in same directory as on the source
machine. Default extension for database device file pre-7 is .DAT.
Start the new SQL Server.
sp_dropserver and sp_addserver on the new machine so that sysservers in master is correct (read
about the LOCAL option for sp_addserver).
The last thing now would be your Windows logins. The mapping you have done in SQL Security Manager
is stored in some (to me) secret place. So you might need to re-create the Windows logins (this
mapping) using SQL Security Manager. I'm vague on this point as I haven't touched 6.5 for many
years now.
Above method is not supported. Supported method is backup/restore which is far from as easy as it is
in the new architecture. Test thoroughly. Hire a consultant with 6.5 experience if that makes you
sleep better.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"sqlgirl" <sqlgirl@.discussions.microsoft.com> wrote in message
news:EBC0B769-A304-4C1E-9096-24E1FFAB7DF6@.microsoft.com...[vbcol=seagreen]
> yes.. its possible to get the same directory structure.
> The only problem is old server is NT 4.0.
> the new one is Windows 2000 server.
> Our ultimate goal is to use this new server as a test server to upgrade sql
> 6.5 to sql 2000.
> Thanks
> "Tibor Karaszi" wrote:
|||Hi,
To add on to the valuable informations from Tibor; Ensure that you install
the same service pack in both the server.
Prefered SQL 6.5 service pack is SP5a + Post SP5a update.
But try to upgrade your SQL Server version to 2000. If you have compatibiily
issues then upgrade the 6.5 database to 2000 and
keep your user databases compatibily level to 6.5
See sp_dbcmptlevel in SQL 2000 books online
Thanks
Hari
SQL Server MVP
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:esGmtSooFHA.1412@.TK2MSFTNGP09.phx.gbl...
> If you have the same directory structure, you could try:
> Installing SQL Server on the new machine.
> Stop both SQL Servers
> Copy *all* the database device files to the new machine. Put in same
> directory as on the source machine. Default extension for database device
> file pre-7 is .DAT.
> Start the new SQL Server.
> sp_dropserver and sp_addserver on the new machine so that sysservers in
> master is correct (read about the LOCAL option for sp_addserver).
> The last thing now would be your Windows logins. The mapping you have done
> in SQL Security Manager is stored in some (to me) secret place. So you
> might need to re-create the Windows logins (this mapping) using SQL
> Security Manager. I'm vague on this point as I haven't touched 6.5 for
> many years now.
> Above method is not supported. Supported method is backup/restore which is
> far from as easy as it is in the new architecture. Test thoroughly. Hire a
> consultant with 6.5 experience if that makes you sleep better.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
> Blog: http://solidqualitylearning.com/blogs/tibor/
>
> "sqlgirl" <sqlgirl@.discussions.microsoft.com> wrote in message
> news:EBC0B769-A304-4C1E-9096-24E1FFAB7DF6@.microsoft.com...
>
|||> Ensure that you install the same service pack in both the server.
> Prefered SQL 6.5 service pack is SP5a + Post SP5a update.
Good thinking, Hari!
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"Hari Prasad" <hari_prasad_k@.hotmail.com> wrote in message
news:%232goMHpoFHA.2472@.tk2msftngp13.phx.gbl...
> Hi,
> To add on to the valuable informations from Tibor; Ensure that you install the same service pack
> in both the server.
> Prefered SQL 6.5 service pack is SP5a + Post SP5a update.
> But try to upgrade your SQL Server version to 2000. If you have compatibiily issues then upgrade
> the 6.5 database to 2000 and
> keep your user databases compatibily level to 6.5
> See sp_dbcmptlevel in SQL 2000 books online
>
> Thanks
> Hari
> SQL Server MVP
> "Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in message
> news:esGmtSooFHA.1412@.TK2MSFTNGP09.phx.gbl...
>
|||Hi
As far as I remember, SQL Server 6.5 is not supported on Windows 2000. Only
up to NT4.0
Regards
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"sqlgirl" <sqlgirl@.discussions.microsoft.com> wrote in message
news:EBC0B769-A304-4C1E-9096-24E1FFAB7DF6@.microsoft.com...[vbcol=seagreen]
> yes.. its possible to get the same directory structure.
> The only problem is old server is NT 4.0.
> the new one is Windows 2000 server.
> Our ultimate goal is to use this new server as a test server to upgrade
> sql
> 6.5 to sql 2000.
> Thanks
> "Tibor Karaszi" wrote:
|||Hmm, I'm pretty sure I had 6.5 running on my W2K pro machine. Doesn't mean it was supported, though
(important distinction). I know for sure I couldn't make it install on XP. I don't remember whether
6.5 was/is supported on W2K, so running something where which isn't supported anymore where the
config wasn't even supported to begin with probably isn't a good idea...
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"Mike Epprecht (SQL MVP)" <mike@.epprecht.net> wrote in message
news:uTXZAuqoFHA.1872@.TK2MSFTNGP10.phx.gbl...
> Hi
> As far as I remember, SQL Server 6.5 is not supported on Windows 2000. Only up to NT4.0
> Regards
> --
> Mike Epprecht, Microsoft SQL Server MVP
> Zurich, Switzerland
> IM: mike@.epprecht.net
> MVP Program: http://www.microsoft.com/mvp
> Blog: http://www.msmvps.com/epprecht/
> "sqlgirl" <sqlgirl@.discussions.microsoft.com> wrote in message
> news:EBC0B769-A304-4C1E-9096-24E1FFAB7DF6@.microsoft.com...
>
|||Mike Epprecht (SQL MVP) (mike@.epprecht.net) writes:
> As far as I remember, SQL Server 6.5 is not supported on Windows 2000.
> Only up to NT4.0
I'm pretty sure that SQL 6.5 SP5a was supported. In any case I do have
6.5 running on Windows 2000.
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se
Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techinf...2000/books.asp

Copying instead of backing up SQL 2005 db

I just found out that our backup software (MS DPM) is conflicting with the
SQL Maintenance jobs. We can't use back up database task in maintenace jobs.
Is there a way to copy a database? I'd like to add this to maintenance jobs
as a t-sql script, or sql server agent job.
Thanks in advance...
The BACKUP command has an option named COPY_ONLY that allows to perform
database backups without affecting the normal sequence of full, differential
and transaction log backups.
See more details on COPY_ONLY on BACKUP on BOL.
Hope this helps,
Ben Nevarez
"Artunc" wrote:

> I just found out that our backup software (MS DPM) is conflicting with the
> SQL Maintenance jobs. We can't use back up database task in maintenace jobs.
> Is there a way to copy a database? I'd like to add this to maintenance jobs
> as a t-sql script, or sql server agent job.
> Thanks in advance...
|||My question would be why are you trying to back it up twice then? How
exactly is it conflicting?
Andrew J. Kelly SQL MVP
Solid Quality Mentors
"Artunc" <Artunc@.discussions.microsoft.com> wrote in message
news:96113D5A-2B6E-4EDC-9D3E-91979FC7E3B5@.microsoft.com...
>I just found out that our backup software (MS DPM) is conflicting with the
> SQL Maintenance jobs. We can't use back up database task in maintenace
> jobs.
> Is there a way to copy a database? I'd like to add this to maintenance
> jobs
> as a t-sql script, or sql server agent job.
> Thanks in advance...
|||No other reson than having a second set of backup for importand dbs.
This is the error I am getting in DPM when backup maintenance job and DPM
backup job run for the same databases:
"DPM tried to do a SQL log backup, either as part of a backup job or a
recovery to latest point in time job. The SQL log backup job has detected a
discontinuity in the SQL log chain for SQL Server 2005 database database
SQLSVR\DB1 since the last backup. All incremental backup jobs will fail until
an express full backup runs. (ID 30140 Details: Internal error code:
0x80990D11)"
"Andrew J. Kelly" wrote:

> My question would be why are you trying to back it up twice then? How
> exactly is it conflicting?
> --
> Andrew J. Kelly SQL MVP
> Solid Quality Mentors
>
> "Artunc" <Artunc@.discussions.microsoft.com> wrote in message
> news:96113D5A-2B6E-4EDC-9D3E-91979FC7E3B5@.microsoft.com...
>

Copying instead of backing up SQL 2005 db

I just found out that our backup software (MS DPM) is conflicting with the
SQL Maintenance jobs. We can't use back up database task in maintenace jobs.
Is there a way to copy a database? I'd like to add this to maintenance jobs
as a t-sql script, or sql server agent job.
Thanks in advance...The BACKUP command has an option named COPY_ONLY that allows to perform
database backups without affecting the normal sequence of full, differential
and transaction log backups.
See more details on COPY_ONLY on BACKUP on BOL.
Hope this helps,
Ben Nevarez
"Artunc" wrote:
> I just found out that our backup software (MS DPM) is conflicting with the
> SQL Maintenance jobs. We can't use back up database task in maintenace jobs.
> Is there a way to copy a database? I'd like to add this to maintenance jobs
> as a t-sql script, or sql server agent job.
> Thanks in advance...|||My question would be why are you trying to back it up twice then? How
exactly is it conflicting?
--
Andrew J. Kelly SQL MVP
Solid Quality Mentors
"Artunc" <Artunc@.discussions.microsoft.com> wrote in message
news:96113D5A-2B6E-4EDC-9D3E-91979FC7E3B5@.microsoft.com...
>I just found out that our backup software (MS DPM) is conflicting with the
> SQL Maintenance jobs. We can't use back up database task in maintenace
> jobs.
> Is there a way to copy a database? I'd like to add this to maintenance
> jobs
> as a t-sql script, or sql server agent job.
> Thanks in advance...|||No other reson than having a second set of backup for importand dbs.
This is the error I am getting in DPM when backup maintenance job and DPM
backup job run for the same databases:
"DPM tried to do a SQL log backup, either as part of a backup job or a
recovery to latest point in time job. The SQL log backup job has detected a
discontinuity in the SQL log chain for SQL Server 2005 database database
SQLSVR\DB1 since the last backup. All incremental backup jobs will fail until
an express full backup runs. (ID 30140 Details: Internal error code:
0x80990D11)"
"Andrew J. Kelly" wrote:
> My question would be why are you trying to back it up twice then? How
> exactly is it conflicting?
> --
> Andrew J. Kelly SQL MVP
> Solid Quality Mentors
>
> "Artunc" <Artunc@.discussions.microsoft.com> wrote in message
> news:96113D5A-2B6E-4EDC-9D3E-91979FC7E3B5@.microsoft.com...
> >I just found out that our backup software (MS DPM) is conflicting with the
> > SQL Maintenance jobs. We can't use back up database task in maintenace
> > jobs.
> >
> > Is there a way to copy a database? I'd like to add this to maintenance
> > jobs
> > as a t-sql script, or sql server agent job.
> >
> > Thanks in advance...
>|||You should decide which backup method is more important to you. Let this do both database and log
backups. Let the other do only database backup, which will not disrupt the log backup chain (for the
other backup method).
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"Artunc" <Artunc@.discussions.microsoft.com> wrote in message
news:B5F12DC7-47DE-41E4-B8CD-2F9158EEC288@.microsoft.com...
> No other reson than having a second set of backup for importand dbs.
> This is the error I am getting in DPM when backup maintenance job and DPM
> backup job run for the same databases:
> "DPM tried to do a SQL log backup, either as part of a backup job or a
> recovery to latest point in time job. The SQL log backup job has detected a
> discontinuity in the SQL log chain for SQL Server 2005 database database
> SQLSVR\DB1 since the last backup. All incremental backup jobs will fail until
> an express full backup runs. (ID 30140 Details: Internal error code:
> 0x80990D11)"
>
> "Andrew J. Kelly" wrote:
>> My question would be why are you trying to back it up twice then? How
>> exactly is it conflicting?
>> --
>> Andrew J. Kelly SQL MVP
>> Solid Quality Mentors
>>
>> "Artunc" <Artunc@.discussions.microsoft.com> wrote in message
>> news:96113D5A-2B6E-4EDC-9D3E-91979FC7E3B5@.microsoft.com...
>> >I just found out that our backup software (MS DPM) is conflicting with the
>> > SQL Maintenance jobs. We can't use back up database task in maintenace
>> > jobs.
>> >
>> > Is there a way to copy a database? I'd like to add this to maintenance
>> > jobs
>> > as a t-sql script, or sql server agent job.
>> >
>> > Thanks in advance...
>>

copying data from a foreign database to Sql Server 2000

I am going to be setting up some Stored procedures that will be copying
data from a foreign database that will have an ODBC connection.
This task will need to be executed at night or from a .NET web page and
I was wondering what would the best way to copy the data from this
procedure.
It won't be necessarily be copying all the data from the database, but
could copy selected tables at different times.
Is this easily done from a Stored Procedure?
Thanks,
Tom.I would play with DTS if I were you. Seems a better candidate than a sproc
without using Linked Servers and such...
Greg Jackson
PDX, Oregon|||Jaxon wrote:

> I would play with DTS if I were you. Seems a better candidate than a sproc
> without using Linked Servers and such...
>
The question is, can it be run from ASP.NET? They want to run this
during the day when necessary, not just at a particular time of day and
don't want to run it from EM.
Tom.

> Greg Jackson
> PDX, Oregon
>
>

copying data accross databases for backup

I am not an expert in SQL
I am faced with the task of copying certain attributes froma table in a
database to create a table in another database to have a sort of refined
backup database.I have to do it through a script to run in Sqlserver query
analyser I have created a query of sort ->
select attrib1, attrib2. into back_up_database_table From
Actual_database..Actual_table where <some condition>
I am logged to query analyser using the backup_database
I am promted to use the command sp_addlinkedserver for the actual database
however still i am getting the error SQLserver doesnot exist or access denie
d
How can I use an accross databes script
Can any help
Thanks in advance
AbhishekWhat kind of a DB are you copying from? Is it a SQL to SQL or access to SQL
?
"adg" wrote:

> I am not an expert in SQL
> I am faced with the task of copying certain attributes froma table in a
> database to create a table in another database to have a sort of refined
> backup database.I have to do it through a script to run in Sqlserver query
> analyser I have created a query of sort ->
> select attrib1, attrib2. into back_up_database_table From
> Actual_database..Actual_table where <some condition>
> I am logged to query analyser using the backup_database
> I am promted to use the command sp_addlinkedserver for the actual database
> however still i am getting the error SQLserver doesnot exist or access den
ied
> How can I use an accross databes script
> Can any help
> Thanks in advance
> Abhishek
>|||When selecting from a table on a linked SQL Server, keep in mind that the
server name prefix and object owner (typically DBO) are required. For
example, if you have a linked server called SERVERNAME:
select attrib1, attrib2. into back_up_database_table From
SERVERNAME.Actual_database.DBO.Actual_table where <some condition>
"adg" <u17748@.uwe> wrote in message news:5a7c9fe20d792@.uwe...
>I am not an expert in SQL
> I am faced with the task of copying certain attributes froma table in a
> database to create a table in another database to have a sort of refined
> backup database.I have to do it through a script to run in Sqlserver query
> analyser I have created a query of sort ->
> select attrib1, attrib2. into back_up_database_table From
> Actual_database..Actual_table where <some condition>
> I am logged to query analyser using the backup_database
> I am promted to use the command sp_addlinkedserver for the actual database
> however still i am getting the error SQLserver doesnot exist or access
> denied
> How can I use an accross databes script
> Can any help
> Thanks in advance
> Abhishek|||I was copying a sqlserver databases Thanks JT giving the fullname of the
database has solved the problem.Its working fine.
Thanks again
JT wrote:
>When selecting from a table on a linked SQL Server, keep in mind that the
>server name prefix and object owner (typically DBO) are required. For
>example, if you have a linked server called SERVERNAME:
>select attrib1, attrib2. into back_up_database_table From
>SERVERNAME.Actual_database.DBO.Actual_table where <some condition>
>
>[quoted text clipped - 13 lines]
Message posted via webservertalk.com
http://www.webservertalk.com/Uwe/Forum...amming/200601/1

Copying and moving tasks between DTSX

hi,

When you copy a sequence container between dtsx you obtain a different size at destination. Any way to avoid this? I'd like to see that task with the same size.

Maybe some posh from my side...

No, you'll have to resize it yourself after pasting I'm afraid.

-Jamie

CopyFile in DTS ActiveX Script Task

I am trying to copy a file and giving it a name with a date behind it. Belo
w
is my code I'm using in my DTS ActiveX Script Task. I'm getting a "File Not
Found" message on Line 25 (I marked it below). Can someone see the problem
with my code'
Dim NYear
Dim NMonth
Dim NDate
NYear = Year(Date)
NMonth = Month(Date)
NDate = CStr(NYear) + CStr(NMonth)
Dim oFSO
Dim sSourceFile
Dim sDestinationFile
Set oFSO = CreateObject("Scripting.FileSystemObject")
sSourceFile =
" \\wstlfp02\ebs$\SQLDataAccess\WPE\PandGI
nvoicesToMCFA\PGInvoiceDetailYYYYMM
"
sDestinationFile =
" \\wstlfp02\ebs$\SQLDataAccess\WPE\PandGI
nvoicesToMCFA\PGInvoiceDetail" +
"_RunDate_" + NDate
oFSO.CopyFile sSourceFile, sDestinationFile '***(This is Line 25)***
' Clean Up
Set oFSO = Nothing
Main = DTSTaskExecResult_SuccessHi
I assume you have tried outputting the file names in a MsgBox and validated
that they are correct? http://www.sqldts.com/default.aspx?292 has an example
of using the filesystem object to copy a file, and
http://www.sqldts.com/default.aspx?200 has an example of using the date as
part of a filename.
Make sure that the account that you are running this has permissions to the
share, it may be worth getting it working with a local drive first.
John
"atchleykl" wrote:

> I am trying to copy a file and giving it a name with a date behind it. Be
low
> is my code I'm using in my DTS ActiveX Script Task. I'm getting a "File N
ot
> Found" message on Line 25 (I marked it below). Can someone see the proble
m
> with my code'
> Dim NYear
> Dim NMonth
> Dim NDate
> NYear = Year(Date)
> NMonth = Month(Date)
> NDate = CStr(NYear) + CStr(NMonth)
> Dim oFSO
> Dim sSourceFile
> Dim sDestinationFile
> Set oFSO = CreateObject("Scripting.FileSystemObject")
> sSourceFile =
> " \\wstlfp02\ebs$\SQLDataAccess\WPE\PandGI
nvoicesToMCFA\PGInvoiceDetailYYYY
MM"
> sDestinationFile =
> " \\wstlfp02\ebs$\SQLDataAccess\WPE\PandGI
nvoicesToMCFA\PGInvoiceDetail" +
> "_RunDate_" + NDate
> oFSO.CopyFile sSourceFile, sDestinationFile '***(This is Line 25)***
> ' Clean Up
> Set oFSO = Nothing
> Main = DTSTaskExecResult_Success
>

Copy(paste) ''serialize'' error always occurs with task, never with components

Some more insight into the error I am getting.

It always occurs at the task (control flow) level and never at the component (data flow) level

It always occurs on the 'copy' action.

I have tried all the msxml/registry recommendations to no avail.

once again here are the error details

===================================

An error occurred while objects were being copied. SSIS Designer could not serialize the SSIS runtime objects. (Microsoft Visual Studio)

===================================

Could not copy object 'SQT Drop Create RAWMigDeal RAWBarrier table' to the clipboard.
(Microsoft.DataTransformationServices.Design)

For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft%u00ae+Visual+Studio%u00ae+2005&ProdVer=8.0.50727.762&EvtSrc=Microsoft.DataTransformationServices.Design.SR&EvtID=SerializeComponentsFailed&LinkId=20476

Program Location:

at Microsoft.DataTransformationServices.Design.DtsClipboardCommandHelper.SerializeRuntimeObjects(ICollection logicalObjects)
at Microsoft.DataTransformationServices.Design.ControlFlowClipboardCommandHelper.InternalMenuCopy(MenuCommand sender, CommandHandlingArgs args)

===================================

Invalid access to memory location. (Exception from HRESULT: 0x800703E6) (Microsoft.SqlServer.ManagedDTS)

Program Location:

at Microsoft.SqlServer.Dts.Runtime.PersistImpl.SaveToXML(XmlDocument& doc, XmlNode node, IDTSEvents events)
at Microsoft.SqlServer.Dts.Runtime.DtsContainer.SaveToXML(XmlDocument& doc, XmlNode node, IDTSEvents events)
at Microsoft.DataTransformationServices.Design.DtsClipboardCommandHelper.SerializeRuntimeObjects(ICollection logicalObjects)Does that copy to clipboard error occur each time an attempt is made to copy any Execute SQL task from any SSIS package?|||brand new ssis solution
add a data flow task
right click copy
BANG! same error

here is the package..... (after receiving the error, so not sure what state it is in)
<?xml version="1.0"?><DTS:Executable xmlnsTS="www.microsoft.com/SqlServer/Dts" DTS:ExecutableType="MSDTS.Package.1"><DTSroperty DTS:Name="PackageFormatVersion">2</DTSroperty><DTSroperty DTS:Name="VersionComments"></DTSroperty><DTSroperty DTS:Name="CreatorName">CSFB\npearse</DTSroperty><DTSroperty DTS:Name="CreatorComputerName">XXXXXXXXXXXXX</DTSroperty><DTSroperty DTS:Name="CreationDate" DTSataType="7">8/20/2007 9:52:03 AM</DTSroperty><DTSroperty DTS:Name="PackageType">5</DTSroperty><DTSroperty DTS:Name="ProtectionLevel">1</DTSroperty><DTSroperty DTS:Name="MaxConcurrentExecutables">-1</DTSroperty><DTSroperty DTS:Name="PackagePriorityClass">0</DTSroperty><DTSroperty DTS:Name="VersionMajor">1</DTSroperty><DTSroperty DTS:Name="VersionMinor">0</DTSroperty><DTSroperty DTS:Name="VersionBuild">1</DTSroperty><DTSroperty DTS:Name="VersionGUID">{557D24A8-D190-486E-BD86-A836815DE6DA}</DTSroperty><DTSroperty DTS:Name="EnableConfig">0</DTSroperty><DTSroperty DTS:Name="CheckpointFileName"></DTSroperty><DTSroperty DTS:Name="SaveCheckpoints">0</DTSroperty><DTSroperty DTS:Name="CheckpointUsage">0</DTSroperty><DTSroperty DTS:Name="SuppressConfigurationWarnings">0</DTSroperty>
<DTSackageVariable><DTSroperty DTS:Name="PackageVariableValue" DTSataType="8">&lt;TaskHost xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlnsdl2="http://schemas.microsoft.com/analysisservices/2003/engine/2" xmlnsdl2_2="http://schemas.microsoft.com/analysisservices/2003/engine/2/2" xmlnswd="http://schemas.microsoft.com/DataWarehouse/Designer/1.0"&gt;&lt;dwdtsDataFlowDiagram&gt;&lt;dwd:Layout&gt;&lt;dds&gt;
&lt;diagram fontclsid="{0BE35203-8F91-11CE-9DE3-00AA004BB851}" mouseiconclsid="{0BE35204-8F91-11CE-9DE3-00AA004BB851}" defaultlayout="Microsoft.DataWarehouse.Layout.GraphLayout" defaultlineroute="Microsoft.DataWarehouse.Layout.GraphLayout" version="7" nextobject="4" scale="100" pagebreakanchorx="0" pagebreakanchory="0" pagebreaksizex="0" pagebreaksizey="0" scrollleft="0" scrolltop="0" gridx="150" gridy="150" marginx="1000" marginy="1000" zoom="100" x="8467" y="7620" backcolor="15334399" defaultpersistence="2" PrintPageNumbersMode="3" PrintMarginTop="0" PrintMarginBottom="635" PrintMarginLeft="0" PrintMarginRight="0" marqueeselectionmode="1" mousepointer="0" snaptogrid="0" autotypeannotation="1" showscrollbars="0" viewpagebreaks="0" donotforceconnectorsbehindshapes="0" backpictureclsid="{00000000-0000-0000-0000-000000000000}"&gt;
&lt;font&gt;
&lt;ddsxmlobjectstreamwrapper binary="01000000900144420100144d6963726f736f66742053616e73205365726966" /&gt;
&lt;/font&gt;
&lt;mouseicon&gt;
&lt;ddsxmlobjectstreamwrapper binary="6c74000000000000" /&gt;
&lt;/mouseicon&gt;
&lt;/diagram&gt;
&lt;layoutmanager&gt;
&lt;ddsxmlobj /&gt;
&lt;/layoutmanager&gt;
&lt;/dds&gt;&lt;/dwd:Layout&gt;&lt;/dwdtsDataFlowDiagram&gt;&lt;/TaskHost&gt;</DTSroperty><DTSroperty DTS:Name="Namespace">dts-designer-1.0</DTSroperty><DTSroperty DTS:Name="ObjectName">{1DB3E9F2-E9DA-4CC2-B0BD-B50C68313755}</DTSroperty><DTSroperty DTS:Name="DTSID">{90FA5082-2489-4857-AA8B-B7CC0A62D7C7}</DTSroperty><DTSroperty DTS:Name="Description"></DTSroperty><DTSroperty DTS:Name="CreationName"></DTSroperty></DTSackageVariable>
<DTSackageVariable><DTSroperty DTS:Name="PackageVariableValue" DTSataType="8">&lt;Package xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlnsdl2="http://schemas.microsoft.com/analysisservices/2003/engine/2" xmlnsdl2_2="http://schemas.microsoft.com/analysisservices/2003/engine/2/2" xmlnswd="http://schemas.microsoft.com/DataWarehouse/Designer/1.0"&gt;&lt;dwdtsControlFlowDiagram&gt;&lt;dwd:BoundingTop&gt;4128&lt;/dwd:BoundingTop&gt;&lt;dwd:Layout&gt;&lt;dds&gt;
&lt;diagram fontclsid="{0BE35203-8F91-11CE-9DE3-00AA004BB851}" mouseiconclsid="{0BE35204-8F91-11CE-9DE3-00AA004BB851}" defaultlayout="Microsoft.DataWarehouse.Layout.GraphLayout" defaultlineroute="Microsoft.DataWarehouse.Layout.GraphLayout" version="7" nextobject="4" scale="100" pagebreakanchorx="0" pagebreakanchory="0" pagebreaksizex="0" pagebreaksizey="0" scrollleft="0" scrolltop="0" gridx="150" gridy="150" marginx="1000" marginy="1000" zoom="100" x="33179" y="18283" backcolor="15334399" defaultpersistence="2" PrintPageNumbersMode="3" PrintMarginTop="0" PrintMarginBottom="635" PrintMarginLeft="0" PrintMarginRight="0" marqueeselectionmode="1" mousepointer="0" snaptogrid="0" autotypeannotation="1" showscrollbars="0" viewpagebreaks="0" donotforceconnectorsbehindshapes="1" backpictureclsid="{00000000-0000-0000-0000-000000000000}"&gt;
&lt;font&gt;
&lt;ddsxmlobjectstreamwrapper binary="01010000900180380100065461686f6d61" /&gt;
&lt;/font&gt;
&lt;mouseicon&gt;
&lt;ddsxmlobjectstreamwrapper binary="6c74000000000000" /&gt;
&lt;/mouseicon&gt;
&lt;/diagram&gt;
&lt;layoutmanager&gt;
&lt;ddsxmlobj /&gt;
&lt;/layoutmanager&gt;
&lt;ddscontrol controlprogid="DdsShapes.DdsObjectManagedBridge.1" tooltip="Data Flow Task" left="11695" top="4128" logicalid="3" controlid="3" masterid="0" hint1="0" hint2="0" width="3598" height="1164" noresize="0" nomove="0" nodefaultattachpoints="0" autodrag="1" usedefaultiddshape="1" selectable="1" showselectionhandles="1" allownudging="1" isannotation="0" dontautolayout="0" groupcollapsed="0" tabstop="1" visible="1" snaptogrid="0"&gt;
&lt;control&gt;
&lt;ddsxmlobjectstreaminitwrapper binary="000800000e0e00008c040000" /&gt;
&lt;/control&gt;
&lt;layoutobject&gt;
&lt;ddsxmlobj&gt;
&lt;property name="LogicalObject" value="{1DB3E9F2-E9DA-4CC2-B0BD-B50C68313755}" vartype="8" /&gt;
&lt;property name="ShowConnectorSource" value="0" vartype="2" /&gt;
&lt;/ddsxmlobj&gt;
&lt;/layoutobject&gt;
&lt;shape groupshapeid="0" groupnode="0" /&gt;
&lt;/ddscontrol&gt;
&lt;/dds&gt;&lt;/dwd:Layout&gt;&lt;/dwdtsControlFlowDiagram&gt;&lt;/Package&gt;</DTSroperty><DTSroperty DTS:Name="Namespace">dts-designer-1.0</DTSroperty><DTSroperty DTS:Name="ObjectName">{7F14B299-8F44-4202-9A3C-6B5D970B5ADA}</DTSroperty><DTSroperty DTS:Name="DTSID">{B505F61E-B095-4522-9FA2-8145F92E7976}</DTSroperty><DTSroperty DTS:Name="Description"></DTSroperty><DTSroperty DTS:Name="CreationName"></DTSroperty></DTSackageVariable><DTSroperty DTS:Name="ForceExecValue">0</DTSroperty><DTSroperty DTS:Name="ExecValue" DTSataType="3">0</DTSroperty><DTSroperty DTS:Name="ForceExecutionResult">-1</DTSroperty><DTSroperty DTS:Name="Disabled">0</DTSroperty><DTSroperty DTS:Name="FailPackageOnFailure">0</DTSroperty><DTSroperty DTS:Name="FailParentOnFailure">0</DTSroperty><DTSroperty DTS:Name="MaxErrorCount">1</DTSroperty><DTSroperty DTS:Name="ISOLevel">1048576</DTSroperty><DTSroperty DTS:Name="LocaleID">2057</DTSroperty><DTSroperty DTS:Name="TransactionOption">1</DTSroperty><DTSroperty DTS:Name="DelayValidation">0</DTSroperty>
<DTS:LoggingOptions><DTSroperty DTS:Name="LoggingMode">0</DTSroperty><DTSroperty DTS:Name="FilterKind">1</DTSroperty><DTSroperty DTS:Name="EventFilter" DTSataType="8"></DTSroperty></DTS:LoggingOptions>
<DTS:Executable DTS:ExecutableType="DTS.Pipeline.1"><DTSroperty DTS:Name="ExecutionLocation">0</DTSroperty><DTSroperty DTS:Name="ExecutionAddress"></DTSroperty><DTSroperty DTS:Name="TaskContact">Performs high-performance data extraction, transformation and loading;Microsoft Corporation; Microsoft SQL Server v9; (C) 2004 Microsoft Corporation; All Rights Reserved;http://www.microsoft.com/sql/support/default.asp;1</DTSroperty><DTSroperty DTS:Name="ForceExecValue">0</DTSroperty><DTSroperty DTS:Name="ExecValue" DTSataType="3">0</DTSroperty><DTSroperty DTS:Name="ForceExecutionResult">-1</DTSroperty><DTSroperty DTS:Name="Disabled">0</DTSroperty><DTSroperty DTS:Name="FailPackageOnFailure">0</DTSroperty><DTSroperty DTS:Name="FailParentOnFailure">0</DTSroperty><DTSroperty DTS:Name="MaxErrorCount">1</DTSroperty><DTSroperty DTS:Name="ISOLevel">1048576</DTSroperty><DTSroperty DTS:Name="LocaleID">-1</DTSroperty><DTSroperty DTS:Name="TransactionOption">1</DTSroperty><DTSroperty DTS:Name="DelayValidation">0</DTSroperty>
<DTS:LoggingOptions><DTSroperty DTS:Name="LoggingMode">0</DTSroperty><DTSroperty DTS:Name="FilterKind">1</DTSroperty><DTSroperty DTS:Name="EventFilter" DTSataType="8"></DTSroperty></DTS:LoggingOptions><DTSroperty DTS:Name="ObjectName">Data Flow Task</DTSroperty><DTSroperty DTS:Name="DTSID">{1DB3E9F2-E9DA-4CC2-B0BD-B50C68313755}</DTSroperty><DTSroperty DTS:Name="Description">Data Flow Task</DTSroperty><DTSroperty DTS:Name="CreationName">DTS.Pipeline.1</DTSroperty><DTSroperty DTS:Name="DisableEventHandlers">0</DTSroperty><DTSbjectData><pipeline id="0" name="pipelineXml" description="pipelineXml" defaultBufferMaxRows="10000" engineThreads="5" defaultBufferSize="10485760" BLOBTempStoragePath="" bufferTempStoragePath="" runInOptimizedMode="true"/></DTSbjectData></DTS:Executable><DTSroperty DTS:Name="ObjectName">Package</DTSroperty><DTSroperty DTS:Name="DTSID">{7F14B299-8F44-4202-9A3C-6B5D970B5ADA}</DTSroperty><DTSroperty DTS:Name="Description"></DTSroperty><DTSroperty DTS:Name="CreationName">MSDTS.Package.1</DTSroperty><DTSroperty DTS:Name="DisableEventHandlers">0</DTSroperty></DTS:Executable>|||Paste the package xml in a code block, via the Mark Code block button, and you will not get the smilies all over the place.|||

Code Snippet

<?xml version="1.0"?><DTS:Executable xmlns:DTS="www.microsoft.com/SqlServer/Dts" DTS:ExecutableType="MSDTS.Package.1"><DTS:Property DTS:Name="PackageFormatVersion">2</DTS:Property><DTS:Property DTS:Name="VersionComments"></DTS:Property><DTS:Property DTS:Name="CreatorName">CSFB\npearse</DTS:Property><DTS:Property DTS:Name="CreatorComputerName">XXXXXXXXXXXXX</DTS:Property><DTS:Property DTS:Name="CreationDate" DTS:DataType="7">8/20/2007 9:52:03 AM</DTS:Property><DTS:Property DTS:Name="PackageType">5</DTS:Property><DTS:Property DTS:Name="ProtectionLevel">1</DTS:Property><DTS:Property DTS:Name="MaxConcurrentExecutables">-1</DTS:Property><DTS:Property DTS:Name="PackagePriorityClass">0</DTS:Property><DTS:Property DTS:Name="VersionMajor">1</DTS:Property><DTS:Property DTS:Name="VersionMinor">0</DTS:Property><DTS:Property DTS:Name="VersionBuild">1</DTS:Property><DTS:Property DTS:Name="VersionGUID">{557D24A8-D190-486E-BD86-A836815DE6DA}</DTS:Property><DTS:Property DTS:Name="EnableConfig">0</DTS:Property><DTS:Property DTS:Name="CheckpointFileName"></DTS:Property><DTS:Property DTS:Name="SaveCheckpoints">0</DTS:Property><DTS:Property DTS:Name="CheckpointUsage">0</DTS:Property><DTS:Property DTS:Name="SuppressConfigurationWarnings">0</DTS:Property>
<DTS:PackageVariable><DTS:Property DTS:Name="PackageVariableValue" DTS:DataType="8">&lt;TaskHost xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:ddl2="http://schemas.microsoft.com/analysisservices/2003/engine/2" xmlns:ddl2_2="http://schemas.microsoft.com/analysisservices/2003/engine/2/2" xmlns:dwd="http://schemas.microsoft.com/DataWarehouse/Designer/1.0"&gt;&lt;dwd:DtsDataFlowDiagram&gt;&lt;dwd:Layout&gt;&lt;dds&gt;
&lt;diagram fontclsid="{0BE35203-8F91-11CE-9DE3-00AA004BB851}" mouseiconclsid="{0BE35204-8F91-11CE-9DE3-00AA004BB851}" defaultlayout="Microsoft.DataWarehouse.Layout.GraphLayout" defaultlineroute="Microsoft.DataWarehouse.Layout.GraphLayout" version="7" nextobject="4" scale="100" pagebreakanchorx="0" pagebreakanchory="0" pagebreaksizex="0" pagebreaksizey="0" scrollleft="0" scrolltop="0" gridx="150" gridy="150" marginx="1000" marginy="1000" zoom="100" x="8467" y="7620" backcolor="15334399" defaultpersistence="2" PrintPageNumbersMode="3" PrintMarginTop="0" PrintMarginBottom="635" PrintMarginLeft="0" PrintMarginRight="0" marqueeselectionmode="1" mousepointer="0" snaptogrid="0" autotypeannotation="1" showscrollbars="0" viewpagebreaks="0" donotforceconnectorsbehindshapes="0" backpictureclsid="{00000000-0000-0000-0000-000000000000}"&gt;
&lt;font&gt;
&lt;ddsxmlobjectstreamwrapper binary="01000000900144420100144d6963726f736f66742053616e73205365726966" /&gt;
&lt;/font&gt;
&lt;mouseicon&gt;
&lt;ddsxmlobjectstreamwrapper binary="6c74000000000000" /&gt;
&lt;/mouseicon&gt;
&lt;/diagram&gt;
&lt;layoutmanager&gt;
&lt;ddsxmlobj /&gt;
&lt;/layoutmanager&gt;
&lt;/dds&gt;&lt;/dwd:Layout&gt;&lt;/dwd:DtsDataFlowDiagram&gt;&lt;/TaskHost&gt;</DTS:Property><DTS:Property DTS:Name="Namespace">dts-designer-1.0</DTS:Property><DTS:Property DTS:Name="ObjectName">{1DB3E9F2-E9DA-4CC2-B0BD-B50C68313755}</DTS:Property><DTS:Property DTS:Name="DTSID">{90FA5082-2489-4857-AA8B-B7CC0A62D7C7}</DTS:Property><DTS:Property DTS:Name="Description"></DTS:Property><DTS:Property DTS:Name="CreationName"></DTS:Property></DTS:PackageVariable>
<DTS:PackageVariable><DTS:Property DTS:Name="PackageVariableValue" DTS:DataType="8">&lt;Package xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:ddl2="http://schemas.microsoft.com/analysisservices/2003/engine/2" xmlns:ddl2_2="http://schemas.microsoft.com/analysisservices/2003/engine/2/2" xmlns:dwd="http://schemas.microsoft.com/DataWarehouse/Designer/1.0"&gt;&lt;dwd:DtsControlFlowDiagram&gt;&lt;dwd:BoundingTop&gt;4128&lt;/dwd:BoundingTop&gt;&lt;dwd:Layout&gt;&lt;dds&gt;
&lt;diagram fontclsid="{0BE35203-8F91-11CE-9DE3-00AA004BB851}" mouseiconclsid="{0BE35204-8F91-11CE-9DE3-00AA004BB851}" defaultlayout="Microsoft.DataWarehouse.Layout.GraphLayout" defaultlineroute="Microsoft.DataWarehouse.Layout.GraphLayout" version="7" nextobject="4" scale="100" pagebreakanchorx="0" pagebreakanchory="0" pagebreaksizex="0" pagebreaksizey="0" scrollleft="0" scrolltop="0" gridx="150" gridy="150" marginx="1000" marginy="1000" zoom="100" x="33179" y="18283" backcolor="15334399" defaultpersistence="2" PrintPageNumbersMode="3" PrintMarginTop="0" PrintMarginBottom="635" PrintMarginLeft="0" PrintMarginRight="0" marqueeselectionmode="1" mousepointer="0" snaptogrid="0" autotypeannotation="1" showscrollbars="0" viewpagebreaks="0" donotforceconnectorsbehindshapes="1" backpictureclsid="{00000000-0000-0000-0000-000000000000}"&gt;
&lt;font&gt;
&lt;ddsxmlobjectstreamwrapper binary="01010000900180380100065461686f6d61" /&gt;
&lt;/font&gt;
&lt;mouseicon&gt;
&lt;ddsxmlobjectstreamwrapper binary="6c74000000000000" /&gt;
&lt;/mouseicon&gt;
&lt;/diagram&gt;
&lt;layoutmanager&gt;
&lt;ddsxmlobj /&gt;
&lt;/layoutmanager&gt;
&lt;ddscontrol controlprogid="DdsShapes.DdsObjectManagedBridge.1" tooltip="Data Flow Task" left="11695" top="4128" logicalid="3" controlid="3" masterid="0" hint1="0" hint2="0" width="3598" height="1164" noresize="0" nomove="0" nodefaultattachpoints="0" autodrag="1" usedefaultiddshape="1" selectable="1" showselectionhandles="1" allownudging="1" isannotation="0" dontautolayout="0" groupcollapsed="0" tabstop="1" visible="1" snaptogrid="0"&gt;
&lt;control&gt;
&lt;ddsxmlobjectstreaminitwrapper binary="000800000e0e00008c040000" /&gt;
&lt;/control&gt;
&lt;layoutobject&gt;
&lt;ddsxmlobj&gt;
&lt;property name="LogicalObject" value="{1DB3E9F2-E9DA-4CC2-B0BD-B50C68313755}" vartype="8" /&gt;
&lt;property name="ShowConnectorSource" value="0" vartype="2" /&gt;
&lt;/ddsxmlobj&gt;
&lt;/layoutobject&gt;
&lt;shape groupshapeid="0" groupnode="0" /&gt;
&lt;/ddscontrol&gt;
&lt;/dds&gt;&lt;/dwd:Layout&gt;&lt;/dwd:DtsControlFlowDiagram&gt;&lt;/Package&gt;</DTS:Property><DTS:Property DTS:Name="Namespace">dts-designer-1.0</DTS:Property><DTS:Property DTS:Name="ObjectName">{7F14B299-8F44-4202-9A3C-6B5D970B5ADA}</DTS:Property><DTS:Property DTS:Name="DTSID">{B505F61E-B095-4522-9FA2-8145F92E7976}</DTS:Property><DTS:Property DTS:Name="Description"></DTS:Property><DTS:Property DTS:Name="CreationName"></DTS:Property></DTS:PackageVariable><DTS:Property DTS:Name="ForceExecValue">0</DTS:Property><DTS:Property DTS:Name="ExecValue" DTS:DataType="3">0</DTS:Property><DTS:Property DTS:Name="ForceExecutionResult">-1</DTS:Property><DTS:Property DTS:Name="Disabled">0</DTS:Property><DTS:Property DTS:Name="FailPackageOnFailure">0</DTS:Property><DTS:Property DTS:Name="FailParentOnFailure">0</DTS:Property><DTS:Property DTS:Name="MaxErrorCount">1</DTS:Property><DTS:Property DTS:Name="ISOLevel">1048576</DTS:Property><DTS:Property DTS:Name="LocaleID">2057</DTS:Property><DTS:Property DTS:Name="TransactionOption">1</DTS:Property><DTS:Property DTS:Name="DelayValidation">0</DTS:Property>
<DTS:LoggingOptions><DTS:Property DTS:Name="LoggingMode">0</DTS:Property><DTS:Property DTS:Name="FilterKind">1</DTS:Property><DTS:Property DTS:Name="EventFilter" DTS:DataType="8"></DTS:Property></DTS:LoggingOptions>
<DTS:Executable DTS:ExecutableType="DTS.Pipeline.1"><DTS:Property DTS:Name="ExecutionLocation">0</DTS:Property><DTS:Property DTS:Name="ExecutionAddress"></DTS:Property><DTS:Property DTS:Name="TaskContact">Performs high-performance data extraction, transformation and loading;Microsoft Corporation; Microsoft SQL Server v9; (C) 2004 Microsoft Corporation; All Rights Reserved;http://www.microsoft.com/sql/support/default.asp;1</DTS:Property><DTS:Property DTS:Name="ForceExecValue">0</DTS:Property><DTS:Property DTS:Name="ExecValue" DTS:DataType="3">0</DTS:Property><DTS:Property DTS:Name="ForceExecutionResult">-1</DTS:Property><DTS:Property DTS:Name="Disabled">0</DTS:Property><DTS:Property DTS:Name="FailPackageOnFailure">0</DTS:Property><DTS:Property DTS:Name="FailParentOnFailure">0</DTS:Property><DTS:Property DTS:Name="MaxErrorCount">1</DTS:Property><DTS:Property DTS:Name="ISOLevel">1048576</DTS:Property><DTS:Property DTS:Name="LocaleID">-1</DTS:Property><DTS:Property DTS:Name="TransactionOption">1</DTS:Property><DTS:Property DTS:Name="DelayValidation">0</DTS:Property>
<DTS:LoggingOptions><DTS:Property DTS:Name="LoggingMode">0</DTS:Property><DTS:Property DTS:Name="FilterKind">1</DTS:Property><DTS:Property DTS:Name="EventFilter" DTS:DataType="8"></DTS:Property></DTS:LoggingOptions><DTS:Property DTS:Name="ObjectName">Data Flow Task</DTS:Property><DTS:Property DTS:Name="DTSID">{1DB3E9F2-E9DA-4CC2-B0BD-B50C68313755}</DTS:Property><DTS:Property DTS:Name="Description">Data Flow Task</DTS:Property><DTS:Property DTS:Name="CreationName">DTS.Pipeline.1</DTS:Property><DTS:Property DTS:Name="DisableEventHandlers">0</DTS:Property><DTS:ObjectData><pipeline id="0" name="pipelineXml" description="pipelineXml" defaultBufferMaxRows="10000" engineThreads="5" defaultBufferSize="10485760" BLOBTempStoragePath="" bufferTempStoragePath="" runInOptimizedMode="true"/></DTS:ObjectData></DTS:Executable><DTS:Property DTS:Name="ObjectName">Package</DTS:Property><DTS:Property DTS:Name="DTSID">{7F14B299-8F44-4202-9A3C-6B5D970B5ADA}</DTS:Property><DTS:Property DTS:Name="Description"></DTS:Property><DTS:Property DTS:Name="CreationName">MSDTS.Package.1</DTS:Property><DTS:Property DTS:Name="DisableEventHandlers">0</DTS:Property></DTS:Executable>

|||

At this point, if you've re-installed and this basic operation (clipboard cut/copy) continues to occur, I would see if you can get SSIS working in a VPC (virtual PC 2007 is a free download) with undo disks set to on, so you can just get back to a clean slate if need be.

Now, using the SSIS package xml provided, cut/copy and paste from a Windows Vista x64 OS work fine. There was not, nor has their ever been (on that machine) or any of the approximately 15 different SSIS installs (some Vista, some XP, some Win2k3, some 32 bit, some 64 bit, some VPC), that error. So, all that means the package xml is not the issue.

Now, looking at the dlls and assemblies being pulled in, the following below 2 are prominently used, which you've already re-registered.

msxml3.dll

msxml6.dll