RE: Run a ssis package on SQL Server 2005 Error

#41

Peter,

Thank you for your reply,

I can run the package OK from the command line with the commands you posted.

The problem I am having now is I cannot edit the command line in SQL Server
Agent. I select the Job and select properties. then Select Setps and Edit
then select Data sources and select the SourceConnection I need to edit then
select Command line then select "Edit the command line manually" and then I
can edit the command line and add the "password=xxxxxx" in the connection
string or the "De "xxxxx" in the command. Then I press OK There is no save
button. When I try to run the Job I get the error about a failed login that
indicates that there is no password. The very one that I just entered. When I
go back to the command line the password is not in there. It was not saved.
So there does not seem to be a way to edit the command line even though there
is a selection that allows editing of the command line.

At this point the package will run in VS2005, I can run it in ssis, I can
run it from the command line. But cannot run it form SQL Agent.

It seems to me there is something very simple that I am missing about
editing the command line in SQL Agent. There is a edit function but no save
button or the user I am logged in as does not have permissions or something
but the Editor is not telling me what is wrong It just does not save the line
I typed in.

I have also checked the save password in VS2005 but it also will not save
the password.If the command string needs a password there should be a way to
save the password. At this point the only way I can get the password in the
command line is the use the dtexec command line. Maybe the password is in the
command line but encripted but there is a way to unencritpt it. I just need
to know what it is.
--
Jerry

""Peter Yang[MSFT]"" wrote:

Quote:

Hello Jerry,

Thank you for your reply. From the symptoms, it seems that you don't save
password properly in your package. Did you check "save password" in
connection manager in VS2005 before you deploy the package to SSIS?

I used the following command to test and it works fine:

dtexec /SQL "\dotnetconnection" /SERVER "." /CONNECTION "Flat File
Connection Manager";"C:\sql\ssistest\dotconnectiontest.txt" /CONNECTION
"test.mytest";"\"Data Source=sha-petery-01;User ID=sa;Initial
Catalog=mytest;Pooling=False;Password=password\"" /MAXCONCURRENT " -1 "
/CHECKPOINTING OFF /REPORTING E /De "password"

Based on my further test, I found that without connection argument, it also
works fine both in dtexec and job exectuion.

dtexec /SQL "\dotnetconnection" /SERVER "." " /MAXCONCURRENT " -1 "
/CHECKPOINTING OFF /REPORTING E /De "password"

If the issue still occurs, will you let's know the exact error message you
see when you run following commands?

dtexec /SQL "\Triveni cvs" /SERVER xxxxxxxxxx /CONNECTION
SourceConnectionOLEDB;"\"Data Source=xxxxxxxxx;User ID=xxxxxess;Initial
Catalog=ContentDepot;Provider=SQLNCLI.1;Persist Security Info=True;Auto
Translate=false;password=xxxxx\"" /MAXCONCURRENT " -1 " /CHECKPOINTING OFF
/De "password"

dtexec /SQL "\Triveni cvs" /SERVER xxxxxxxxxx " /MAXCONCURRENT " -1 "
/CHECKPOINTING OFF /De "password"

I look foward to your reply. Thank you.

Best Regards,

Peter Yang
MCSE2000/2003, MCSA, MCDBA
Microsoft Online Partner Support

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

When responding to posts, please "Reply to Group" via your
newsreader so that others may learn and benefit from this issue.
================================================== ====
This posting is provided "AS IS" with no warranties, and confers no rights.

#42

Peter,

Thank you for your reply,

I can run the package OK from the command line with the commands you posted.

The problem I am having now is I cannot edit the command line in SQL Server
Agent. I select the Job and select properties. then Select Setps and Edit
then select Data sources and select the SourceConnection I need to edit then
select Command line then select "Edit the command line manually" and then I
can edit the command line and add the "password=xxxxxx" in the connection
string or the "De "xxxxx" in the command. Then I press OK There is no save
button. When I try to run the Job I get the error about a failed login that
indicates that there is no password. The very one that I just entered. When I
go back to the command line the password is not in there. It was not saved.
So there does not seem to be a way to edit the command line even though there
is a selection that allows editing of the command line.

At this point the package will run in VS2005, I can run it in ssis, I can
run it from the command line. But cannot run it form SQL Agent.

It seems to me there is something very simple that I am missing about
editing the command line in SQL Agent. There is a edit function but no save
button or the user I am logged in as does not have permissions or something
but the Editor is not telling me what is wrong It just does not save the line
I typed in.

I have also checked the save password in VS2005 but it also will not save
the password.If the command string needs a password there should be a way to
save the password. At this point the only way I can get the password in the
command line is the use the dtexec command line. Maybe the password is in the
command line but encripted but there is a way to unencritpt it. I just need
to know what it is.
--
Jerry

""Peter Yang[MSFT]"" wrote:

Quote:

Hello Jerry,

Thank you for your reply. From the symptoms, it seems that you don't save
password properly in your package. Did you check "save password" in
connection manager in VS2005 before you deploy the package to SSIS?

I used the following command to test and it works fine:

dtexec /SQL "\dotnetconnection" /SERVER "." /CONNECTION "Flat File
Connection Manager";"C:\sql\ssistest\dotconnectiontest.txt" /CONNECTION
"test.mytest";"\"Data Source=sha-petery-01;User ID=sa;Initial
Catalog=mytest;Pooling=False;Password=password\"" /MAXCONCURRENT " -1 "
/CHECKPOINTING OFF /REPORTING E /De "password"

Based on my further test, I found that without connection argument, it also
works fine both in dtexec and job exectuion.

dtexec /SQL "\dotnetconnection" /SERVER "." " /MAXCONCURRENT " -1 "
/CHECKPOINTING OFF /REPORTING E /De "password"

If the issue still occurs, will you let's know the exact error message you
see when you run following commands?

dtexec /SQL "\Triveni cvs" /SERVER xxxxxxxxxx /CONNECTION
SourceConnectionOLEDB;"\"Data Source=xxxxxxxxx;User ID=xxxxxess;Initial
Catalog=ContentDepot;Provider=SQLNCLI.1;Persist Security Info=True;Auto
Translate=false;password=xxxxx\"" /MAXCONCURRENT " -1 " /CHECKPOINTING OFF
/De "password"

dtexec /SQL "\Triveni cvs" /SERVER xxxxxxxxxx " /MAXCONCURRENT " -1 "
/CHECKPOINTING OFF /De "password"

I look foward to your reply. Thank you.

Best Regards,

Peter Yang
MCSE2000/2003, MCSA, MCDBA
Microsoft Online Partner Support

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

When responding to posts, please "Reply to Group" via your
newsreader so that others may learn and benefit from this issue.
================================================== ====
This posting is provided "AS IS" with no warranties, and confers no rights.

#43

Peter,

Thank you for your reply,

I can run the package OK from the command line with the commands you posted.

The problem I am having now is I cannot edit the command line in SQL Server
Agent. I select the Job and select properties. then Select Setps and Edit
then select Data sources and select the SourceConnection I need to edit then
select Command line then select "Edit the command line manually" and then I
can edit the command line and add the "password=xxxxxx" in the connection
string or the "De "xxxxx" in the command. Then I press OK There is no save
button. When I try to run the Job I get the error about a failed login that
indicates that there is no password. The very one that I just entered. When I
go back to the command line the password is not in there. It was not saved.
So there does not seem to be a way to edit the command line even though there
is a selection that allows editing of the command line.

At this point the package will run in VS2005, I can run it in ssis, I can
run it from the command line. But cannot run it form SQL Agent.

It seems to me there is something very simple that I am missing about
editing the command line in SQL Agent. There is a edit function but no save
button or the user I am logged in as does not have permissions or something
but the Editor is not telling me what is wrong It just does not save the line
I typed in.

I have also checked the save password in VS2005 but it also will not save
the password.If the command string needs a password there should be a way to
save the password. At this point the only way I can get the password in the
command line is the use the dtexec command line. Maybe the password is in the
command line but encripted but there is a way to unencritpt it. I just need
to know what it is.
--
Jerry

""Peter Yang[MSFT]"" wrote:

Quote:

Hello Jerry,

Thank you for your reply. From the symptoms, it seems that you don't save
password properly in your package. Did you check "save password" in
connection manager in VS2005 before you deploy the package to SSIS?

I used the following command to test and it works fine:

dtexec /SQL "\dotnetconnection" /SERVER "." /CONNECTION "Flat File
Connection Manager";"C:\sql\ssistest\dotconnectiontest.txt" /CONNECTION
"test.mytest";"\"Data Source=sha-petery-01;User ID=sa;Initial
Catalog=mytest;Pooling=False;Password=password\"" /MAXCONCURRENT " -1 "
/CHECKPOINTING OFF /REPORTING E /De "password"

Based on my further test, I found that without connection argument, it also
works fine both in dtexec and job exectuion.

dtexec /SQL "\dotnetconnection" /SERVER "." " /MAXCONCURRENT " -1 "
/CHECKPOINTING OFF /REPORTING E /De "password"

If the issue still occurs, will you let's know the exact error message you
see when you run following commands?

dtexec /SQL "\Triveni cvs" /SERVER xxxxxxxxxx /CONNECTION
SourceConnectionOLEDB;"\"Data Source=xxxxxxxxx;User ID=xxxxxess;Initial
Catalog=ContentDepot;Provider=SQLNCLI.1;Persist Security Info=True;Auto
Translate=false;password=xxxxx\"" /MAXCONCURRENT " -1 " /CHECKPOINTING OFF
/De "password"

dtexec /SQL "\Triveni cvs" /SERVER xxxxxxxxxx " /MAXCONCURRENT " -1 "
/CHECKPOINTING OFF /De "password"

I look foward to your reply. Thank you.

Best Regards,

Peter Yang
MCSE2000/2003, MCSA, MCDBA
Microsoft Online Partner Support

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

When responding to posts, please "Reply to Group" via your
newsreader so that others may learn and benefit from this issue.
================================================== ====
This posting is provided "AS IS" with no warranties, and confers no rights.

#44

Peter,

Thank you for your reply,

I can run the package OK from the command line with the commands you posted.

The problem I am having now is I cannot edit the command line in SQL Server
Agent. I select the Job and select properties. then Select Setps and Edit
then select Data sources and select the SourceConnection I need to edit then
select Command line then select "Edit the command line manually" and then I
can edit the command line and add the "password=xxxxxx" in the connection
string or the "De "xxxxx" in the command. Then I press OK There is no save
button. When I try to run the Job I get the error about a failed login that
indicates that there is no password. The very one that I just entered. When I
go back to the command line the password is not in there. It was not saved.
So there does not seem to be a way to edit the command line even though there
is a selection that allows editing of the command line.

At this point the package will run in VS2005, I can run it in ssis, I can
run it from the command line. But cannot run it form SQL Agent.

It seems to me there is something very simple that I am missing about
editing the command line in SQL Agent. There is a edit function but no save
button or the user I am logged in as does not have permissions or something
but the Editor is not telling me what is wrong It just does not save the line
I typed in.

I have also checked the save password in VS2005 but it also will not save
the password.If the command string needs a password there should be a way to
save the password. At this point the only way I can get the password in the
command line is the use the dtexec command line. Maybe the password is in the
command line but encripted but there is a way to unencritpt it. I just need
to know what it is.
--
Jerry

""Peter Yang[MSFT]"" wrote:

Quote:

Hello Jerry,

Thank you for your reply. From the symptoms, it seems that you don't save
password properly in your package. Did you check "save password" in
connection manager in VS2005 before you deploy the package to SSIS?

I used the following command to test and it works fine:

dtexec /SQL "\dotnetconnection" /SERVER "." /CONNECTION "Flat File
Connection Manager";"C:\sql\ssistest\dotconnectiontest.txt" /CONNECTION
"test.mytest";"\"Data Source=sha-petery-01;User ID=sa;Initial
Catalog=mytest;Pooling=False;Password=password\"" /MAXCONCURRENT " -1 "
/CHECKPOINTING OFF /REPORTING E /De "password"

Based on my further test, I found that without connection argument, it also
works fine both in dtexec and job exectuion.

dtexec /SQL "\dotnetconnection" /SERVER "." " /MAXCONCURRENT " -1 "
/CHECKPOINTING OFF /REPORTING E /De "password"

If the issue still occurs, will you let's know the exact error message you
see when you run following commands?

dtexec /SQL "\Triveni cvs" /SERVER xxxxxxxxxx /CONNECTION
SourceConnectionOLEDB;"\"Data Source=xxxxxxxxx;User ID=xxxxxess;Initial
Catalog=ContentDepot;Provider=SQLNCLI.1;Persist Security Info=True;Auto
Translate=false;password=xxxxx\"" /MAXCONCURRENT " -1 " /CHECKPOINTING OFF
/De "password"

dtexec /SQL "\Triveni cvs" /SERVER xxxxxxxxxx " /MAXCONCURRENT " -1 "
/CHECKPOINTING OFF /De "password"

I look foward to your reply. Thank you.

Best Regards,

Peter Yang
MCSE2000/2003, MCSA, MCDBA
Microsoft Online Partner Support

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

When responding to posts, please "Reply to Group" via your
newsreader so that others may learn and benefit from this issue.
================================================== ====
This posting is provided "AS IS" with no warranties, and confers no rights.

#45

Peter,

Thank you for your reply,

I can run the package OK from the command line with the commands you posted.

The problem I am having now is I cannot edit the command line in SQL Server
Agent. I select the Job and select properties. then Select Setps and Edit
then select Data sources and select the SourceConnection I need to edit then
select Command line then select "Edit the command line manually" and then I
can edit the command line and add the "password=xxxxxx" in the connection
string or the "De "xxxxx" in the command. Then I press OK There is no save
button. When I try to run the Job I get the error about a failed login that
indicates that there is no password. The very one that I just entered. When I
go back to the command line the password is not in there. It was not saved.
So there does not seem to be a way to edit the command line even though there
is a selection that allows editing of the command line.

At this point the package will run in VS2005, I can run it in ssis, I can
run it from the command line. But cannot run it form SQL Agent.

It seems to me there is something very simple that I am missing about
editing the command line in SQL Agent. There is a edit function but no save
button or the user I am logged in as does not have permissions or something
but the Editor is not telling me what is wrong It just does not save the line
I typed in.

I have also checked the save password in VS2005 but it also will not save
the password.If the command string needs a password there should be a way to
save the password. At this point the only way I can get the password in the
command line is the use the dtexec command line. Maybe the password is in the
command line but encripted but there is a way to unencritpt it. I just need
to know what it is.
--
Jerry

""Peter Yang[MSFT]"" wrote:

Quote:

Hello Jerry,

Thank you for your reply. From the symptoms, it seems that you don't save
password properly in your package. Did you check "save password" in
connection manager in VS2005 before you deploy the package to SSIS?

I used the following command to test and it works fine:

dtexec /SQL "\dotnetconnection" /SERVER "." /CONNECTION "Flat File
Connection Manager";"C:\sql\ssistest\dotconnectiontest.txt" /CONNECTION
"test.mytest";"\"Data Source=sha-petery-01;User ID=sa;Initial
Catalog=mytest;Pooling=False;Password=password\"" /MAXCONCURRENT " -1 "
/CHECKPOINTING OFF /REPORTING E /De "password"

Based on my further test, I found that without connection argument, it also
works fine both in dtexec and job exectuion.

dtexec /SQL "\dotnetconnection" /SERVER "." " /MAXCONCURRENT " -1 "
/CHECKPOINTING OFF /REPORTING E /De "password"

If the issue still occurs, will you let's know the exact error message you
see when you run following commands?

dtexec /SQL "\Triveni cvs" /SERVER xxxxxxxxxx /CONNECTION
SourceConnectionOLEDB;"\"Data Source=xxxxxxxxx;User ID=xxxxxess;Initial
Catalog=ContentDepot;Provider=SQLNCLI.1;Persist Security Info=True;Auto
Translate=false;password=xxxxx\"" /MAXCONCURRENT " -1 " /CHECKPOINTING OFF
/De "password"

dtexec /SQL "\Triveni cvs" /SERVER xxxxxxxxxx " /MAXCONCURRENT " -1 "
/CHECKPOINTING OFF /De "password"

I look foward to your reply. Thank you.

Best Regards,

Peter Yang
MCSE2000/2003, MCSA, MCDBA
Microsoft Online Partner Support

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

When responding to posts, please "Reply to Group" via your
newsreader so that others may learn and benefit from this issue.
================================================== ====
This posting is provided "AS IS" with no warranties, and confers no rights.

#46

Peter,

Thank you for your reply,

I can run the package OK from the command line with the commands you posted.

The problem I am having now is I cannot edit the command line in SQL Server
Agent. I select the Job and select properties. then Select Setps and Edit
then select Data sources and select the SourceConnection I need to edit then
select Command line then select "Edit the command line manually" and then I
can edit the command line and add the "password=xxxxxx" in the connection
string or the "De "xxxxx" in the command. Then I press OK There is no save
button. When I try to run the Job I get the error about a failed login that
indicates that there is no password. The very one that I just entered. When I
go back to the command line the password is not in there. It was not saved.
So there does not seem to be a way to edit the command line even though there
is a selection that allows editing of the command line.

At this point the package will run in VS2005, I can run it in ssis, I can
run it from the command line. But cannot run it form SQL Agent.

It seems to me there is something very simple that I am missing about
editing the command line in SQL Agent. There is a edit function but no save
button or the user I am logged in as does not have permissions or something
but the Editor is not telling me what is wrong It just does not save the line
I typed in.

I have also checked the save password in VS2005 but it also will not save
the password.If the command string needs a password there should be a way to
save the password. At this point the only way I can get the password in the
command line is the use the dtexec command line. Maybe the password is in the
command line but encripted but there is a way to unencritpt it. I just need
to know what it is.
--
Jerry

""Peter Yang[MSFT]"" wrote:

Quote:

Hello Jerry,

Thank you for your reply. From the symptoms, it seems that you don't save
password properly in your package. Did you check "save password" in
connection manager in VS2005 before you deploy the package to SSIS?

I used the following command to test and it works fine:

dtexec /SQL "\dotnetconnection" /SERVER "." /CONNECTION "Flat File
Connection Manager";"C:\sql\ssistest\dotconnectiontest.txt" /CONNECTION
"test.mytest";"\"Data Source=sha-petery-01;User ID=sa;Initial
Catalog=mytest;Pooling=False;Password=password\"" /MAXCONCURRENT " -1 "
/CHECKPOINTING OFF /REPORTING E /De "password"

Based on my further test, I found that without connection argument, it also
works fine both in dtexec and job exectuion.

dtexec /SQL "\dotnetconnection" /SERVER "." " /MAXCONCURRENT " -1 "
/CHECKPOINTING OFF /REPORTING E /De "password"

If the issue still occurs, will you let's know the exact error message you
see when you run following commands?

dtexec /SQL "\Triveni cvs" /SERVER xxxxxxxxxx /CONNECTION
SourceConnectionOLEDB;"\"Data Source=xxxxxxxxx;User ID=xxxxxess;Initial
Catalog=ContentDepot;Provider=SQLNCLI.1;Persist Security Info=True;Auto
Translate=false;password=xxxxx\"" /MAXCONCURRENT " -1 " /CHECKPOINTING OFF
/De "password"

dtexec /SQL "\Triveni cvs" /SERVER xxxxxxxxxx " /MAXCONCURRENT " -1 "
/CHECKPOINTING OFF /De "password"

I look foward to your reply. Thank you.

Best Regards,

Peter Yang
MCSE2000/2003, MCSA, MCDBA
Microsoft Online Partner Support

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

When responding to posts, please "Reply to Group" via your
newsreader so that others may learn and benefit from this issue.
================================================== ====
This posting is provided "AS IS" with no warranties, and confers no rights.

#47

Peter,

Thank you for your reply,

I can run the package OK from the command line with the commands you posted.

The problem I am having now is I cannot edit the command line in SQL Server
Agent. I select the Job and select properties. then Select Setps and Edit
then select Data sources and select the SourceConnection I need to edit then
select Command line then select "Edit the command line manually" and then I
can edit the command line and add the "password=xxxxxx" in the connection
string or the "De "xxxxx" in the command. Then I press OK There is no save
button. When I try to run the Job I get the error about a failed login that
indicates that there is no password. The very one that I just entered. When I
go back to the command line the password is not in there. It was not saved.
So there does not seem to be a way to edit the command line even though there
is a selection that allows editing of the command line.

At this point the package will run in VS2005, I can run it in ssis, I can
run it from the command line. But cannot run it form SQL Agent.

It seems to me there is something very simple that I am missing about
editing the command line in SQL Agent. There is a edit function but no save
button or the user I am logged in as does not have permissions or something
but the Editor is not telling me what is wrong It just does not save the line
I typed in.

I have also checked the save password in VS2005 but it also will not save
the password.If the command string needs a password there should be a way to
save the password. At this point the only way I can get the password in the
command line is the use the dtexec command line. Maybe the password is in the
command line but encripted but there is a way to unencritpt it. I just need
to know what it is.
--
Jerry

""Peter Yang[MSFT]"" wrote:

Quote:

Hello Jerry,

Thank you for your reply. From the symptoms, it seems that you don't save
password properly in your package. Did you check "save password" in
connection manager in VS2005 before you deploy the package to SSIS?

I used the following command to test and it works fine:

dtexec /SQL "\dotnetconnection" /SERVER "." /CONNECTION "Flat File
Connection Manager";"C:\sql\ssistest\dotconnectiontest.txt" /CONNECTION
"test.mytest";"\"Data Source=sha-petery-01;User ID=sa;Initial
Catalog=mytest;Pooling=False;Password=password\"" /MAXCONCURRENT " -1 "
/CHECKPOINTING OFF /REPORTING E /De "password"

Based on my further test, I found that without connection argument, it also
works fine both in dtexec and job exectuion.

dtexec /SQL "\dotnetconnection" /SERVER "." " /MAXCONCURRENT " -1 "
/CHECKPOINTING OFF /REPORTING E /De "password"

If the issue still occurs, will you let's know the exact error message you
see when you run following commands?

dtexec /SQL "\Triveni cvs" /SERVER xxxxxxxxxx /CONNECTION
SourceConnectionOLEDB;"\"Data Source=xxxxxxxxx;User ID=xxxxxess;Initial
Catalog=ContentDepot;Provider=SQLNCLI.1;Persist Security Info=True;Auto
Translate=false;password=xxxxx\"" /MAXCONCURRENT " -1 " /CHECKPOINTING OFF
/De "password"

dtexec /SQL "\Triveni cvs" /SERVER xxxxxxxxxx " /MAXCONCURRENT " -1 "
/CHECKPOINTING OFF /De "password"

I look foward to your reply. Thank you.

Best Regards,

Peter Yang
MCSE2000/2003, MCSA, MCDBA
Microsoft Online Partner Support

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

When responding to posts, please "Reply to Group" via your
newsreader so that others may learn and benefit from this issue.
================================================== ====
This posting is provided "AS IS" with no warranties, and confers no rights.

#48

Peter,

Thank you for your reply,

I can run the package OK from the command line with the commands you posted.

The problem I am having now is I cannot edit the command line in SQL Server
Agent. I select the Job and select properties. then Select Setps and Edit
then select Data sources and select the SourceConnection I need to edit then
select Command line then select "Edit the command line manually" and then I
can edit the command line and add the "password=xxxxxx" in the connection
string or the "De "xxxxx" in the command. Then I press OK There is no save
button. When I try to run the Job I get the error about a failed login that
indicates that there is no password. The very one that I just entered. When I
go back to the command line the password is not in there. It was not saved.
So there does not seem to be a way to edit the command line even though there
is a selection that allows editing of the command line.

At this point the package will run in VS2005, I can run it in ssis, I can
run it from the command line. But cannot run it form SQL Agent.

It seems to me there is something very simple that I am missing about
editing the command line in SQL Agent. There is a edit function but no save
button or the user I am logged in as does not have permissions or something
but the Editor is not telling me what is wrong It just does not save the line
I typed in.

I have also checked the save password in VS2005 but it also will not save
the password.If the command string needs a password there should be a way to
save the password. At this point the only way I can get the password in the
command line is the use the dtexec command line. Maybe the password is in the
command line but encripted but there is a way to unencritpt it. I just need
to know what it is.
--
Jerry

""Peter Yang[MSFT]"" wrote:

Quote:

Hello Jerry,

Thank you for your reply. From the symptoms, it seems that you don't save
password properly in your package. Did you check "save password" in
connection manager in VS2005 before you deploy the package to SSIS?

I used the following command to test and it works fine:

dtexec /SQL "\dotnetconnection" /SERVER "." /CONNECTION "Flat File
Connection Manager";"C:\sql\ssistest\dotconnectiontest.txt" /CONNECTION
"test.mytest";"\"Data Source=sha-petery-01;User ID=sa;Initial
Catalog=mytest;Pooling=False;Password=password\"" /MAXCONCURRENT " -1 "
/CHECKPOINTING OFF /REPORTING E /De "password"

Based on my further test, I found that without connection argument, it also
works fine both in dtexec and job exectuion.

dtexec /SQL "\dotnetconnection" /SERVER "." " /MAXCONCURRENT " -1 "
/CHECKPOINTING OFF /REPORTING E /De "password"

If the issue still occurs, will you let's know the exact error message you
see when you run following commands?

dtexec /SQL "\Triveni cvs" /SERVER xxxxxxxxxx /CONNECTION
SourceConnectionOLEDB;"\"Data Source=xxxxxxxxx;User ID=xxxxxess;Initial
Catalog=ContentDepot;Provider=SQLNCLI.1;Persist Security Info=True;Auto
Translate=false;password=xxxxx\"" /MAXCONCURRENT " -1 " /CHECKPOINTING OFF
/De "password"

dtexec /SQL "\Triveni cvs" /SERVER xxxxxxxxxx " /MAXCONCURRENT " -1 "
/CHECKPOINTING OFF /De "password"

I look foward to your reply. Thank you.

Best Regards,

Peter Yang
MCSE2000/2003, MCSA, MCDBA
Microsoft Online Partner Support

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

When responding to posts, please "Reply to Group" via your
newsreader so that others may learn and benefit from this issue.
================================================== ====
This posting is provided "AS IS" with no warranties, and confers no rights.

#49

Hello Jerry,

As I mentioned, it's normal that the command line shown after you save is
not the same as you have saved. Also, when you check "save password" in VS
2005, you will still be prompted to input password again when you edit the
connection. However, the password is actually stored in the package.

I'd like to confirm that the both commands work properly for your server

dtexec /SQL "\Triveni cvs" /SERVER "xxxxxxxxxx" /CONNECTION
SourceConnectionOLEDB;"\"Data Source=xxxxxxxxx;User ID=xxxxxess;Initial
Catalog=ContentDepot;Provider=SQLNCLI.1;Persist Security Info=True;Auto
Translate=false;password=xxxxx\"" /MAXCONCURRENT " -1 " /CHECKPOINTING OFF
/De "password"

dtexec /SQL "\Triveni cvs" /SERVER "xxxxxxxxxx" /CHECKPOINTING OFF /De
"password"

I still suspect that the command line you use in command line window is not
exact same as that works in command prompt.

If so, please just copy the commands line without "dtexec" when you edit
command line to replace the existing command. After that, click OK to save,
and run the job at this time to test. You may try both commands one by one.

Actually, you could work around the issue by running command directly in
job step by choosing operation system(cmdexec) type, and then use the
command directly:

dtexec /SQL "\dotnetconnection" /SERVER "xxxxxxxxxx" /CHECKPOINTING OFF
/REPORTING E /De "Password01!"

If you have any update, please feel free to let's know. Thank you.

Best Regards,

Peter Yang
MCSE2000/2003, MCSA, MCDBA
Microsoft Online Partner Support

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

When responding to posts, please "Reply to Group" via your
newsreader so that others may learn and benefit from this issue.
================================================== ====
This posting is provided "AS IS" with no warranties, and confers no rights.

#50

Hello Jerry,

As I mentioned, it's normal that the command line shown after you save is
not the same as you have saved. Also, when you check "save password" in VS
2005, you will still be prompted to input password again when you edit the
connection. However, the password is actually stored in the package.

I'd like to confirm that the both commands work properly for your server

dtexec /SQL "\Triveni cvs" /SERVER "xxxxxxxxxx" /CONNECTION
SourceConnectionOLEDB;"\"Data Source=xxxxxxxxx;User ID=xxxxxess;Initial
Catalog=ContentDepot;Provider=SQLNCLI.1;Persist Security Info=True;Auto
Translate=false;password=xxxxx\"" /MAXCONCURRENT " -1 " /CHECKPOINTING OFF
/De "password"

dtexec /SQL "\Triveni cvs" /SERVER "xxxxxxxxxx" /CHECKPOINTING OFF /De
"password"

I still suspect that the command line you use in command line window is not
exact same as that works in command prompt.

If so, please just copy the commands line without "dtexec" when you edit
command line to replace the existing command. After that, click OK to save,
and run the job at this time to test. You may try both commands one by one.

Actually, you could work around the issue by running command directly in
job step by choosing operation system(cmdexec) type, and then use the
command directly:

dtexec /SQL "\dotnetconnection" /SERVER "xxxxxxxxxx" /CHECKPOINTING OFF
/REPORTING E /De "Password01!"

If you have any update, please feel free to let's know. Thank you.

Best Regards,

Peter Yang
MCSE2000/2003, MCSA, MCDBA
Microsoft Online Partner Support

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

When responding to posts, please "Reply to Group" via your
newsreader so that others may learn and benefit from this issue.
================================================== ====
This posting is provided "AS IS" with no warranties, and confers no rights.