I have had this problem before and I cannot seem to fix it now. There is a
post with the same subject line to review.

I think the solution I used is method 3 from Article ID 918760 but now I am
not able to edit the Command line in the SQL server Agent Job I think I used
/DE "password" but I put that line in and say OK but it does not save.

Any help

Thank you
--
Jerry

I have had this problem before and I cannot seem to fix it now. There is a
post with the same subject line to review.

I think the solution I used is method 3 from Article ID 918760 but now I am
not able to edit the Command line in the SQL server Agent Job I think I used
/DE "password" but I put that line in and say OK but it does not save.

Any help

Thank you
--
Jerry

I have had this problem before and I cannot seem to fix it now. There is a
post with the same subject line to review.

I think the solution I used is method 3 from Article ID 918760 but now I am
not able to edit the Command line in the SQL server Agent Job I think I used
/DE "password" but I put that line in and say OK but it does not save.

Any help

Thank you
--
Jerry

I have had this problem before and I cannot seem to fix it now. There is a
post with the same subject line to review.

I think the solution I used is method 3 from Article ID 918760 but now I am
not able to edit the Command line in the SQL server Agent Job I think I used
/DE "password" but I put that line in and say OK but it does not save.

Any help

Thank you
--
Jerry

I have had this problem before and I cannot seem to fix it now. There is a
post with the same subject line to review.

I think the solution I used is method 3 from Article ID 918760 but now I am
not able to edit the Command line in the SQL server Agent Job I think I used
/DE "password" but I put that line in and say OK but it does not save.

Any help

Thank you
--
Jerry

I have had this problem before and I cannot seem to fix it now. There is a
post with the same subject line to review.

I think the solution I used is method 3 from Article ID 918760 but now I am
not able to edit the Command line in the SQL server Agent Job I think I used
/DE "password" but I put that line in and say OK but it does not save.

Any help

Thank you
--
Jerry

I have had this problem before and I cannot seem to fix it now. There is a
post with the same subject line to review.

I think the solution I used is method 3 from Article ID 918760 but now I am
not able to edit the Command line in the SQL server Agent Job I think I used
/DE "password" but I put that line in and say OK but it does not save.

Any help

Thank you
--
Jerry

I have had this problem before and I cannot seem to fix it now. There is a
post with the same subject line to review.

I think the solution I used is method 3 from Article ID 918760 but now I am
not able to edit the Command line in the SQL server Agent Job I think I used
/DE "password" but I put that line in and say OK but it does not save.

Any help

Thank you
--
Jerry

Hello Jerry,


This is supposed to be the normal behavior since it's to protect
information in the command line. Each time it's edited, it's prompted for
default command line. However, when it's saved, it's actually saved. Please
note, you should select the connections used in the packge under "data
source" tab before you try to change command line.

If the issue persists, you may try to check if you could run the pcakge
directly in command prompt by using your password.


dtexec /SQL "\packagename" /SERVER "." /MAXCONCURRENT " -1 "
/CHECKPOINTING OFF /REPORTING E /De "Password"


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

Best Regards,

Peter Yang
MCSE2000/2003, MCSA, MCDBA
Microsoft Online Community Support
==================================================
Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscripti...ult.aspx#notif
ications
<http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx>.
Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from the community or a Microsoft Support
Engineer within 1 business day is acceptable. Please note that each follow
up response may take approximately 2 business days as the support
professional working with you may need further investigation to reach the
most efficient resolution. The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by contacting
Microsoft Customer Support Services (CSS) at
<http://msdn.microsoft.com/subscriptions/support/default.aspx>.
==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.

Hello Jerry,


This is supposed to be the normal behavior since it's to protect
information in the command line. Each time it's edited, it's prompted for
default command line. However, when it's saved, it's actually saved. Please
note, you should select the connections used in the packge under "data
source" tab before you try to change command line.

If the issue persists, you may try to check if you could run the pcakge
directly in command prompt by using your password.


dtexec /SQL "\packagename" /SERVER "." /MAXCONCURRENT " -1 "
/CHECKPOINTING OFF /REPORTING E /De "Password"


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

Best Regards,

Peter Yang
MCSE2000/2003, MCSA, MCDBA
Microsoft Online Community Support
==================================================
Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscripti...ult.aspx#notif
ications
<http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx>.
Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from the community or a Microsoft Support
Engineer within 1 business day is acceptable. Please note that each follow
up response may take approximately 2 business days as the support
professional working with you may need further investigation to reach the
most efficient resolution. The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by contacting
Microsoft Customer Support Services (CSS) at
<http://msdn.microsoft.com/subscriptions/support/default.aspx>.
==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.