Failed to schedule DTS in SQL 2005

Hello,

I am trying to to schedule DTS Package but this message appear .

Message
The job failed. The Job was invoked by User sa. The last step to run was step 1 (1). and this

Message
Executed as user: Computer name\SYSTEM. The package execution failed. The step failed

so how I can schedule DTS Package in sql 2005 .

Do you have logging enabled for this package? if enabled check the log file it should have more detailed information on the error.

The error you have posted is a very generic error from the job agent, and it does not give any information.

Thanks

|||

Sounds like you might have some issues with the account settings. See the following thread for tips on setting up proxies / credentials / jobs etc.

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1955723&SiteID=1

|||

Thanks, all

But still the same problem even I did all thing to solve but still can't schedule DTS, but when I see th proparites of the

SQL Server Agent-->Connection and found the sql server connection grayed out and can't select or change it . so may be this is the problem but how to run the agent under sa account .

|||

Assuming you are talking about the connection infromation on the left hand side of the job properties screen, that connection information is how you are currently connected to the sql server. You would need to look at the steps tab and click edit on the step associated with the package you are trying to run. At the top of this screen there will be a place for the step name (i.e. run package x), the type (sql server integration services package) and the run as. You would select the correct proxy name from the run as drop down that ties to your sa account...

|||

Thanks very much for you reply but I still can't schedule the DTS even though when I execute the dts it's work fine and I did all thing what said here http://www.codeproject.com/useritems/Schedule__Run__SSIS__DTS.asp

|||

I am trying to schedule working DTS in sql server 2005 sp 2 . but I it failed and got this message . I searched at Internet and found this

http://support.microsoft.com/kb/904796

but I can’t understand how to solve it, any one can help please .

Message

Executed as user: ComputrName\Administrator. ...00.3042.00 for 32-bitCopyright (C) Microsoft Corp 1984-2005. All rights reserved.Started:10:16:11 ?Error: 2007-08-17 22:16:12.95Code: 0x00000000Source: Copy Data from ROOM toDBNamedboER_ROOMTaskDescription: System.Runtime.InteropServices.COMException (0x80040427): Execution was canceled by user.at DTS.PackageClass.Execute()at Microsoft.SqlServer.Dts.Tasks.Exec80PackageTask.Exec80PackageTask.ExecuteThread()End ErrorError: 2007-08-17 22:16:14.75Code: 0x00000000Description: System.Runtime.InteropServices.COMException (0x80040427): Execution was canceled by user.at DTS.PackageClass.Execute()at Microsoft.SqlServer.Dts.Tasks.Exec80PackageTask.Exec80PackageTask.ExecuteThread()End ErrorError: 2007-08-17 22:16:15.14Code: 0x00000000The package execution fa...The step failed.

|||

how to Reinstall the SQL Server 2000 tools? where to find it .

Still no solution can solve this issue .

sql

Failed to notify 'DBA' via email

We have some SQL jobs those run on a schedule basis. These jobs are setup to
notify us via email in case of job fails. However, Some time we get this
error "Failed to notify 'DBA' via email." Initially I thought it may be b/c
of mail server was not available but our exchnage server admin has looked at
exchange logs and not found any thing at that time. I also looked at the SQL
server logs and did not find any issues. My question is: is there any thing
can go wrong in the SQL server that can cause this probelm?
Help is appreciated.
Thanks,
MohMoh,
FWIW - SQL Server MAPI will only wait a certain amount of time to deliver a
message. If it cannot get out, then the mail will 'fail' even though
Exchange is up and running and healthy. It might be Exchange, networking,
domain issues, etc. that cause the problem.
If you Google on "sql mail Failed to notify" you will see a few comments on
this, without any real help that I could find.
(Unless xp_smtp_sendmail would work for you.)
RLF
"Moh Abb" <mabbas@.aligntech.com> wrote in message
news:eiv3swh3EHA.3376@.TK2MSFTNGP12.phx.gbl...
> We have some SQL jobs those run on a schedule basis. These jobs are setup
to
> notify us via email in case of job fails. However, Some time we get this
> error "Failed to notify 'DBA' via email." Initially I thought it may be
b/c
> of mail server was not available but our exchnage server admin has looked
at
> exchange logs and not found any thing at that time. I also looked at the
SQL
> server logs and did not find any issues. My question is: is there any
thing
> can go wrong in the SQL server that can cause this probelm?
> Help is appreciated.
> Thanks,
> Moh
>|||"Russell Fields" <RussellFields@.NoMailPlease.Com> wrote in message
news:ePA64pj3EHA.2600@.TK2MSFTNGP09.phx.gbl...
> Moh,
> FWIW - SQL Server MAPI will only wait a certain amount of time to deliver
a
> message. If it cannot get out, then the mail will 'fail' even though
> Exchange is up and running and healthy. It might be Exchange, networking,
> domain issues, etc. that cause the problem.
> If you Google on "sql mail Failed to notify" you will see a few comments
on
> this, without any real help that I could find.
Generally I find if you don't absolutely need to use Exchange, setup a local
SMTP server right on teh SQL box and send email through that directly.
Eliminates timeouts, etc.
> (Unless xp_smtp_sendmail would work for you.)
> RLF
> "Moh Abb" <mabbas@.aligntech.com> wrote in message
> news:eiv3swh3EHA.3376@.TK2MSFTNGP12.phx.gbl...
> > We have some SQL jobs those run on a schedule basis. These jobs are
setup
> to
> > notify us via email in case of job fails. However, Some time we get this
> > error "Failed to notify 'DBA' via email." Initially I thought it may be
> b/c
> > of mail server was not available but our exchnage server admin has
looked
> at
> > exchange logs and not found any thing at that time. I also looked at the
> SQL
> > server logs and did not find any issues. My question is: is there any
> thing
> > can go wrong in the SQL server that can cause this probelm?
> >
> > Help is appreciated.
> >
> > Thanks,
> > Moh
> >
> >
>
>

Failed scheduled job

I have a scheduled job which has been failing for a while,
and the only way I have now been able to have it concluded
successfully and with required data transfer result is
when the service-account is member of the domain-admins
group. Adding the service-account only to the local-admins
group of concerned systems gives successfull job
completion but with empty result.
Thus my question is, why must the service-account be
member of the domain-admins group, when the job itself is
to run under the domain-admin account that has full
permission on all systems.
I will appreciated any clarification.What exactly is the job trying to do ?
--
HTH
Jasper Smith (SQL Server MVP)
I support PASS - the definitive, global
community for SQL Server professionals -
http://www.sqlpass.org
"topokin" <bimosekin@.hotmail.com> wrote in message
news:b9c101c381a1$241e5030$a601280a@.phx.gbl...
I have a scheduled job which has been failing for a while,
and the only way I have now been able to have it concluded
successfully and with required data transfer result is
when the service-account is member of the domain-admins
group. Adding the service-account only to the local-admins
group of concerned systems gives successfull job
completion but with empty result.
Thus my question is, why must the service-account be
member of the domain-admins group, when the job itself is
to run under the domain-admin account that has full
permission on all systems.
I will appreciated any clarification.|||Whether or not you need a domain admin account depends on what you are
trying to do. In general, there is really no need for the service account or
the account tha runs the job to be a member of the domain admin. In most
places, you'd be told to get lost by the NT admin if you ask for the domain
admin rights.
I'd suggest you carefully log your jobs. For instance, you can specify an
output file for each step in its Advanced tab. You can then review this
output file to find more about the nature of the failure.
--
Linchi Shea
linchi_shea@.NOSPAMml.com
"topokin" <bimosekin@.hotmail.com> wrote in message
news:b9c101c381a1$241e5030$a601280a@.phx.gbl...
> I have a scheduled job which has been failing for a while,
> and the only way I have now been able to have it concluded
> successfully and with required data transfer result is
> when the service-account is member of the domain-admins
> group. Adding the service-account only to the local-admins
> group of concerned systems gives successfull job
> completion but with empty result.
> Thus my question is, why must the service-account be
> member of the domain-admins group, when the job itself is
> to run under the domain-admin account that has full
> permission on all systems.
> I will appreciated any clarification.
>

Failed Maintenance Plan Job

Could anybody tell me why this job would be failing based on this log?
Running SQL 2000 SP4.
Microsoft (R) SQLMaint Utility (Unicode), Version Logged on to SQL
Server 'servername' as 'domain\username' (trusted)
Starting maintenance plan 'DB Maintenance Plan2' on 4/25/2006 4:35:16
PM
Backup can not be performed on database 'axdata_live'. This sub task is
ignored.
Backup can not be performed on database 'axdata_test'. This sub task is
ignored.
Backup can not be performed on database 'Northwind'. This sub task is
ignored.
Backup can not be performed on database 'pubs'. This sub task is
ignored.
Deleting old text reports... 1 file(s) deleted.
End of maintenance plan 'DB Maintenance Plan2' on 4/25/2006 4:35:16 PM
SQLMAINT.EXE Process Exit Code: 1 (Failed)My guess would be that those databases are in Simple recovery mode and you
are attempting to issue a Log backup. Take out the log backup and it should
work.
--
Andrew J. Kelly SQL MVP
<bjorgenson@.charter.net> wrote in message
news:1146001380.696610.165740@.g10g2000cwb.googlegroups.com...
> Could anybody tell me why this job would be failing based on this log?
> Running SQL 2000 SP4.
>
> Microsoft (R) SQLMaint Utility (Unicode), Version Logged on to SQL
> Server 'servername' as 'domain\username' (trusted)
> Starting maintenance plan 'DB Maintenance Plan2' on 4/25/2006 4:35:16
> PM
> Backup can not be performed on database 'axdata_live'. This sub task is
> ignored.
> Backup can not be performed on database 'axdata_test'. This sub task is
> ignored.
> Backup can not be performed on database 'Northwind'. This sub task is
> ignored.
> Backup can not be performed on database 'pubs'. This sub task is
> ignored.
> Deleting old text reports... 1 file(s) deleted.
> End of maintenance plan 'DB Maintenance Plan2' on 4/25/2006 4:35:16 PM
> SQLMAINT.EXE Process Exit Code: 1 (Failed)
>

Failed Maintenance Plan Job

Could anybody tell me why this job would be failing based on this log?
Running SQL 2000 SP4.
Microsoft (R) SQLMaint Utility (Unicode), Version Logged on to SQL
Server 'servername' as 'domain\username' (trusted)
Starting maintenance plan 'DB Maintenance Plan2' on 4/25/2006 4:35:16
PM
Backup can not be performed on database 'axdata_live'. This sub task is
ignored.
Backup can not be performed on database 'axdata_test'. This sub task is
ignored.
Backup can not be performed on database 'Northwind'. This sub task is
ignored.
Backup can not be performed on database 'pubs'. This sub task is
ignored.
Deleting old text reports... 1 file(s) deleted.
End of maintenance plan 'DB Maintenance Plan2' on 4/25/2006 4:35:16 PM
SQLMAINT.EXE Process Exit Code: 1 (Failed)My guess would be that those databases are in Simple recovery mode and you
are attempting to issue a Log backup. Take out the log backup and it should
work.
Andrew J. Kelly SQL MVP
<bjorgenson@.charter.net> wrote in message
news:1146001380.696610.165740@.g10g2000cwb.googlegroups.com...
> Could anybody tell me why this job would be failing based on this log?
> Running SQL 2000 SP4.
>
> Microsoft (R) SQLMaint Utility (Unicode), Version Logged on to SQL
> Server 'servername' as 'domain\username' (trusted)
> Starting maintenance plan 'DB Maintenance Plan2' on 4/25/2006 4:35:16
> PM
> Backup can not be performed on database 'axdata_live'. This sub task is
> ignored.
> Backup can not be performed on database 'axdata_test'. This sub task is
> ignored.
> Backup can not be performed on database 'Northwind'. This sub task is
> ignored.
> Backup can not be performed on database 'pubs'. This sub task is
> ignored.
> Deleting old text reports... 1 file(s) deleted.
> End of maintenance plan 'DB Maintenance Plan2' on 4/25/2006 4:35:16 PM
> SQLMAINT.EXE Process Exit Code: 1 (Failed)
>

failed jobs ..to restart automatically.

hi
my job was scheduled at 11.45 pm..but server went down at 11.40..and restart
ed at 12.10 am..
i want to know
1) how can we reschedule our jobs..so that if server went down and job was s
chedule somewhere in between it should automatically start..
jobs can be anything like backup/reindex//etc
regards
sunnyHi,
Set SQL server agent to start automatically, when the server starts. And the
n schedule your job to run automatically at the startup, i.e when the agent
starts up.
You can use the following stored proc
sp_add_jobschedule
and set @.freq_type = 64
The value 64, sets the job to start automatically, when the sql server agent
starts.
Thanks
GYK

failed jobs ..to restart automatically.

h
my job was scheduled at 11.45 pm..but server went down at 11.40..and restarted at 12.10 am.
i want to kno
1) how can we reschedule our jobs..so that if server went down and job was schedule somewhere in between it should automatically start.
jobs can be anything like backup/reindex//et
regard
sunnHi,
Set SQL server agent to start automatically, when the server starts. And then schedule your job to run automatically at the startup, i.e when the agent starts up
You can use the following stored pro
sp_add_jobschedul
and set @.freq_type = 64
The value 64, sets the job to start automatically, when the sql server agent starts
Thank
GYK

failed job with my user name as the owner.

Hi,
I am working on sql 2000 and one of the DBAs in my team.
All the jobs with me as the owner failed miserablly today
on one of my servers. They have been run fine forever
before.
Message: The job failed. Unable to determine if the owner
(domainname\jwang) of jobname has server access (reason:
Could not obtain information about Windows NT group/user
domainname\jwang'. [SQLSTATE 42000] (Error 8198)).
And when I try to connect to the server through EM on my
laptop, it returns this error message: 'a connection could
not be established to the servername. Reason: 'Cannot
generate SSPI context'.
This actually happened to several people who tried the
same thing.
Why all of a sudden this? We have be applying window
updates and sql patches to some of our servers, but not to
all of them yet. This server is one of the highest patch
level server. Could this cause a problem?
Urgent help please. Many thanks.
JJTry logging on to that server as jwang on that domain, see what happens.
Maybe there is a connectivity issue, you'll get better error messages
possibly from dong that.
--
*************************************
Andy S.
andy_mcdba@.yahoo.com
*************************************
"JJ Wang" <jwang@.leapwireless.com> wrote in message
news:086101c379be$b18ed1a0$a101280a@.phx.gbl...
> Hi,
> I am working on sql 2000 and one of the DBAs in my team.
> All the jobs with me as the owner failed miserablly today
> on one of my servers. They have been run fine forever
> before.
> Message: The job failed. Unable to determine if the owner
> (domainname\jwang) of jobname has server access (reason:
> Could not obtain information about Windows NT group/user
> domainname\jwang'. [SQLSTATE 42000] (Error 8198)).
> And when I try to connect to the server through EM on my
> laptop, it returns this error message: 'a connection could
> not be established to the servername. Reason: 'Cannot
> generate SSPI context'.
> This actually happened to several people who tried the
> same thing.
> Why all of a sudden this? We have be applying window
> updates and sql patches to some of our servers, but not to
> all of them yet. This server is one of the highest patch
> level server. Could this cause a problem?
>
> Urgent help please. Many thanks.
> JJ
>|||In article <086101c379be$b18ed1a0$a101280a@.phx.gbl>, "JJ Wang" <jwang@.leapwireless.com> wrote:
>Hi,
>I am working on sql 2000 and one of the DBAs in my team.
>All the jobs with me as the owner failed miserablly today
>on one of my servers. They have been run fine forever
>before.
>Message: The job failed. Unable to determine if the owner
>(domainname\jwang) of jobname has server access (reason:
>Could not obtain information about Windows NT group/user
>domainname\jwang'. [SQLSTATE 42000] (Error 8198)).
>And when I try to connect to the server through EM on my
>laptop, it returns this error message: 'a connection could
>not be established to the servername. Reason: 'Cannot
>generate SSPI context'.
>This actually happened to several people who tried the
>same thing.
>Why all of a sudden this? We have be applying window
>updates and sql patches to some of our servers, but not to
>all of them yet. This server is one of the highest patch
>level server. Could this cause a problem?
>
>Urgent help please. Many thanks.
>JJ
>
Anything going on with your PDC/Active Directory Servers?|||Thank you, Andy, I know that it will work with sql login, there is
something funky going on with the domain authentication on this server.
JJ
*** Sent via Developersdex http://www.developersdex.com ***
Don't just participate in USENET...get rewarded for it!

Failed Job Message

This is a post
I am in desparate need of some help with SQL Server 2000. I recently created several jobs to run at night to update several tables in my SQL Server. I then realized that I could schedule one job with various steps, so I tried to delete the original jobs
with the stored proc. but could not seem to get it to work. While examining the sysjob table in the msdn database I deleted one of the old jobs. This is where the problem started. I have since deleted the job steps out of the sysjobsteps and the sysjo
bschedule as well as systaskids for that same job. I am still getting the error notification each morning that the job failed Unable to retrieve steps for the certain job. Where is this notification coming from? Because there is no jobs or job steps in
any of the tables. Any help would greatly be appreciated.
There is a bit more that goes on in deleting a job than just
deleting rows from these tables. Jobs can be stored in the
job cache so there are also procedures that check the job
cache and update it if necessary - I think it's through
sp_agent_notify if I remember correctly. There could also be
some other references to the jobs in some of the other job
tables. That's why modifying these tables directly isn't
recommended. You could try restarting SQL Agent if you
didn't do so after modifying the tables but I'd guess you
could still have some other dangling references to the job
which may or may not affect things.
You may want to consider restoring your msdb database from
prior to your modifying the job tables and then delete the
jobs using sp_delete_job which is the supported method of
dropping a job. Using sp_delete_job will handle all the
details, update the job cache if necessary, etc.
-Sue
On Tue, 20 Apr 2004 10:51:04 -0700, "Cartman"
<anonymous@.discussions.microsoft.com> wrote:

>This is a post
>I am in desparate need of some help with SQL Server 2000. I recently created several jobs to run at night to update several tables in my SQL Server. I then realized that I could schedule one job with various steps, so I tried to delete the original job
s with the stored proc. but could not seem to get it to work. While examining the sysjob table in the msdn database I deleted one of the old jobs. This is where the problem started. I have since deleted the job steps out of the sysjobsteps and the sysj
obschedule as well as systaskids for that same job. I am still getting the error notification each morning that the job failed Unable to retrieve steps for the certain job. Where is this notification coming from? Because there is no jobs or job steps i
n any of the tables. Any help would greatly be appreciated.

Failed Job Message

This is a post
I am in desparate need of some help with SQL Server 2000. I recently created several jobs to run at night to update several tables in my SQL Server. I then realized that I could schedule one job with various steps, so I tried to delete the original jobs with the stored proc. but could not seem to get it to work. While examining the sysjob table in the msdn database I deleted one of the old jobs. This is where the problem started. I have since deleted the job steps out of the sysjobsteps and the sysjobschedule as well as systaskids for that same job. I am still getting the error notification each morning that the job failed Unable to retrieve steps for the certain job. Where is this notification coming from? Because there is no jobs or job steps in any of the tables. Any help would greatly be appreciatedThere is a bit more that goes on in deleting a job than just
deleting rows from these tables. Jobs can be stored in the
job cache so there are also procedures that check the job
cache and update it if necessary - I think it's through
sp_agent_notify if I remember correctly. There could also be
some other references to the jobs in some of the other job
tables. That's why modifying these tables directly isn't
recommended. You could try restarting SQL Agent if you
didn't do so after modifying the tables but I'd guess you
could still have some other dangling references to the job
which may or may not affect things.
You may want to consider restoring your msdb database from
prior to your modifying the job tables and then delete the
jobs using sp_delete_job which is the supported method of
dropping a job. Using sp_delete_job will handle all the
details, update the job cache if necessary, etc.
-Sue
On Tue, 20 Apr 2004 10:51:04 -0700, "Cartman"
<anonymous@.discussions.microsoft.com> wrote:
>This is a post
>I am in desparate need of some help with SQL Server 2000. I recently created several jobs to run at night to update several tables in my SQL Server. I then realized that I could schedule one job with various steps, so I tried to delete the original jobs with the stored proc. but could not seem to get it to work. While examining the sysjob table in the msdn database I deleted one of the old jobs. This is where the problem started. I have since deleted the job steps out of the sysjobsteps and the sysjobschedule as well as systaskids for that same job. I am still getting the error notification each morning that the job failed Unable to retrieve steps for the certain job. Where is this notification coming from? Because there is no jobs or job steps in any of the tables. Any help would greatly be appreciated.

Failed Job Message

This is a post
I am in desparate need of some help with SQL Server 2000. I recently create
d several jobs to run at night to update several tables in my SQL Server. I
then realized that I could schedule one job with various steps, so I tried
to delete the original jobs
with the stored proc. but could not seem to get it to work. While examining
the sysjob table in the msdn database I deleted one of the old jobs. This
is where the problem started. I have since deleted the job steps out of the
sysjobsteps and the sysjo
bschedule as well as systaskids for that same job. I am still getting the e
rror notification each morning that the job failed Unable to retrieve steps
for the certain job. Where is this notification coming from? Because there
is no jobs or job steps in
any of the tables. Any help would greatly be appreciated.There is a bit more that goes on in deleting a job than just
deleting rows from these tables. Jobs can be stored in the
job cache so there are also procedures that check the job
cache and update it if necessary - I think it's through
sp_agent_notify if I remember correctly. There could also be
some other references to the jobs in some of the other job
tables. That's why modifying these tables directly isn't
recommended. You could try restarting SQL Agent if you
didn't do so after modifying the tables but I'd guess you
could still have some other dangling references to the job
which may or may not affect things.
You may want to consider restoring your msdb database from
prior to your modifying the job tables and then delete the
jobs using sp_delete_job which is the supported method of
dropping a job. Using sp_delete_job will handle all the
details, update the job cache if necessary, etc.
-Sue
On Tue, 20 Apr 2004 10:51:04 -0700, "Cartman"
<anonymous@.discussions.microsoft.com> wrote:

>This is a post
>I am in desparate need of some help with SQL Server 2000. I recently created sever
al jobs to run at night to update several tables in my SQL Server. I then realized
that I could schedule one job with various steps, so I tried to delete the original
job
s with the stored proc. but could not seem to get it to work. While examini
ng the sysjob table in the msdn database I deleted one of the old jobs. Thi
s is where the problem started. I have since deleted the job steps out of t
he sysjobsteps and the sysj
obschedule as well as systaskids for that same job. I am still getting the
error notification each morning that the job failed Unable to retrieve steps
for the certain job. Where is this notification coming from? Because ther
e is no jobs or job steps i
n any of the tables. Any help would greatly be appreciated.

Failed integrity check

The accounting system we support runs on SQL 2000. We have setup a SQL Job that checks the integrity of a each accounting database each evening. After running successufully for a few weeks the job started retuning a failed message. I checked the job log and the reason for the failure was because one of the databases couldn't be set to single user mode. When I first saw this I figured OK someone forgot to logout before leaving for the night. When discussing this with the accounting staff, they swear this couldn't be the case with this particular database since only 1 person accesses it and then only rarley, and he says he hasn't been in for days. The amount of activity in this database is minimal
The server was cycled and eveything ran fine for about 3 weeks. Then the same thing happned again over a span of a few nights consecutive. The are no overnight business processes. There are database backups that are scheduled in the evening, including one for this particualr database. Nothing is showing in the active processes during the day to this database, i.e. no run away processes. Any ideas on what is causing the SQL Server to think there is a open connection to this database?
Thanks much for any ideas!If these jobs are set up through maintenance plans, remove
the option for Attempt to repair any minor problems.
You really don't want this to run automatically anyway. If
you have problems with DBCCs, you should be investigating
the cause first before taking any action.
-Sue
On Sat, 18 Oct 2003 12:41:04 -0700, "DL"
<anonymous@.discussions.microsoft.com> wrote:
>The accounting system we support runs on SQL 2000. We have setup a SQL Job that checks the integrity of a each accounting database each evening. After running successufully for a few weeks the job started retuning a failed message. I checked the job log and the reason for the failure was because one of the databases couldn't be set to single user mode. When I first saw this I figured OK someone forgot to logout before leaving for the night. When discussing this with the accounting staff, they swear this couldn't be the case with this particular database since only 1 person accesses it and then only rarley, and he says he hasn't been in for days. The amount of activity in this database is minimal
>The server was cycled and eveything ran fine for about 3 weeks. Then the same thing happned again over a span of a few nights consecutive. The are no overnight business processes. There are database backups that are scheduled in the evening, including one for this particualr database. Nothing is showing in the active processes during the day to this database, i.e. no run away processes. Any ideas on what is causing the SQL Server to think there is a open connection to this database?
>Thanks much for any ideas!

Fail to run as job but success execute in VS2005

hi all,

please help,

i using Execute DTS 2000 Package Task to create a package.dtsx, and execute successful in VS2005

but when i created it as a job and it fail to run.

the package.dtsx is calling a package2000.dts, which having 2 steps to run.

i execute the job by step, and the i found that the 1st job is running successful but the 2nd job was fail.

may i know where can i found the error log? or any where to debug it?

please help......

thanks 1st.....

Hi Khin,

* Note that configuring log for SSIS will not provide the log for Individual steps run in the Execute DTS 2000 Package task.

* Configure a Separate log for the DTS file enclosed by opening it in DTS designer, right click -> Properties ->Logging -> <Give a file Path to Store this log file >.

Thanks

Subhash Subramanyam

Fail to Invoke Job from ASP .NET

Hi,

I have an ASP .NET page which invoke a SQL Agent Job. It works fine in debugging but when I run the web application in deplyment environnment it does not work. The Web Application is configured in Basic Authentication. The error message is not very detailed: "Invoke failed to job XXX".

I tried to add credentials information in my code using:

myServer.ConnectionContext.LoginSecure = false;
myServer.ConnectionContext.Login = "DOMAIN\Login";
myServer.ConnectionContext.Password = "pwd";

or

myServer.ConnectionContext.LoginSecure = false;
myServer.ConnectionContext.ConnectAsUserName = "DOMAIN\Login";
myServer.ConnectionContext.ConnectAsUserPassword = "pwd";

but it does not change anything.

Any help will be appreciated.

When you specify LoginSecure=false you're telling the server to use a SQL login, then you're supplying a domain login. You need to establish a SQL Login with the necessary credentials on the server in this circumstance.|||Hi,

if you want to impersonate the curretn thread with another security token than the actual it is running on (as you told the basic authentication) you will have to create an impersonation context, if you want to use the current security context your can just set the LoginSecure = true.

HTH, Jens K. Suessmeyer.

http://www.sqlserver2005.de