Hi,
We have recently begun to experience a problem that is stumping us. We
have a DTS package that is run every morning as a scheduled job but
always fails. The job runs perfectly fine when kicked off manually
(either all at once from the Enterprise Manager or one step at a time
from DTS). The job history says it failed on step 1, but we've
determined that at least the first few steps run successfully. I've
attempted to turn package logging on but we never get any results (I've
tried to save the log both in the SQL Server log as well as a local
text file ... nothing ever appears in either location).
This is extremely frustrating and we're all getting tired of waking up
at 3am to kick the job off. Any ideas?
Thanks!!This article may help.
http://support.microsoft.com/kb/269074/EN-US/
Regards,
Dave Patrick ...Please no email replies - reply in newsgroup.
Microsoft Certified Professional
Microsoft MVP [Windows]
http://www.microsoft.com/protect
"Rich" wrote:
| Hi,
|
| We have recently begun to experience a problem that is stumping us. We
| have a DTS package that is run every morning as a scheduled job but
| always fails. The job runs perfectly fine when kicked off manually
| (either all at once from the Enterprise Manager or one step at a time
| from DTS). The job history says it failed on step 1, but we've
| determined that at least the first few steps run successfully. I've
| attempted to turn package logging on but we never get any results (I've
| tried to save the log both in the SQL Server log as well as a local
| text file ... nothing ever appears in either location).
|
| This is extremely frustrating and we're all getting tired of waking up
| at 3am to kick the job off. Any ideas?
|
| Thanks!!
||||Hi Dave,
Thanks for the article. I've read it and checked a few things out on
our SQL Server 2000 installation. The job was running under a different
account than I would have expected, but the account has full access to
the system and is a member of the system administrator group. Just to
be safe, I changed the owner of the job to the Administrator account
(which is what our other DTS packages run under). However, this didn't
work either.
I then deleted the scheduled job and recreated it on the server
desktop. The owner is again the Administrator account. It is scheduled
to run tonight, but I highly doubt anything is going to change.
Are there some security settings I could double-check perhaps?
Thanks,
-Rich
Dave Patrick wrote:
> This article may help.
> http://support.microsoft.com/kb/269074/EN-US/
> --
> Regards,
> Dave Patrick ...Please no email replies - reply in newsgroup.
> Microsoft Certified Professional
> Microsoft MVP [Windows]
> http://www.microsoft.com/protect
> "Rich" wrote:
> | Hi,
> |
> | We have recently begun to experience a problem that is stumping us. We
> | have a DTS package that is run every morning as a scheduled job but
> | always fails. The job runs perfectly fine when kicked off manually
> | (either all at once from the Enterprise Manager or one step at a time
> | from DTS). The job history says it failed on step 1, but we've
> | determined that at least the first few steps run successfully. I've
> | attempted to turn package logging on but we never get any results (I've
> | tried to save the log both in the SQL Server log as well as a local
> | text file ... nothing ever appears in either location).
> |
> | This is extremely frustrating and we're all getting tired of waking up
> | at 3am to kick the job off. Any ideas?
> |
> | Thanks!!
> ||||Something here may help.
http://www.sqldts.com/?106
Regards,
Dave Patrick ...Please no email replies - reply in newsgroup.
Microsoft Certified Professional
Microsoft MVP [Windows]
http://www.microsoft.com/protect
"Rich" wrote:
| Hi Dave,
|
| Thanks for the article. I've read it and checked a few things out on
| our SQL Server 2000 installation. The job was running under a different
| account than I would have expected, but the account has full access to
| the system and is a member of the system administrator group. Just to
| be safe, I changed the owner of the job to the Administrator account
| (which is what our other DTS packages run under). However, this didn't
| work either.
|
| I then deleted the scheduled job and recreated it on the server
| desktop. The owner is again the Administrator account. It is scheduled
| to run tonight, but I highly doubt anything is going to change.
|
| Are there some security settings I could double-check perhaps?
|
| Thanks,
| -Rich|||Thanks Dave,
I've looked at a few things suggested in the link you provided but
nothing worked. Finally, I created a new login for the windows
Administrator account and added it to the SysAdmin role. This worked!
Now, this stumps me, because the Windows workgroup "Administrators" is
already a member of SysAdmin, and the Windows Administrator account is
already assigned to the Administrators role... so it should have had
permissions already. Any thoughts on this?
Additionally, I mentioned that the job was not recording its log file.
This was mistaken - I was looking under the SQL Server logs (under
"Management"), but I just found them under DTS, "package logs".
However, there are no entries for when the package ran as a scheduled
job ... a log entry was recorded only when I ran the job manually. This
was really puzzling to me, but then I realized that it had to be a
security problem. The job wasn't getting anywhere, because the SQL
Agent was running under an account that didn't have the right
permissions applied (apparently).
-Rich
Dave Patrick wrote:
> Something here may help.
> http://www.sqldts.com/?106
> --
> Regards,
> Dave Patrick ...Please no email replies - reply in newsgroup.
> Microsoft Certified Professional
> Microsoft MVP [Windows]
> http://www.microsoft.com/protect
> "Rich" wrote:
> | Hi Dave,
> |
> | Thanks for the article. I've read it and checked a few things out on
> | our SQL Server 2000 installation. The job was running under a different
> | account than I would have expected, but the account has full access to
> | the system and is a member of the system administrator group. Just to
> | be safe, I changed the owner of the job to the Administrator account
> | (which is what our other DTS packages run under). However, this didn't
> | work either.
> |
> | I then deleted the scheduled job and recreated it on the server
> | desktop. The owner is again the Administrator account. It is scheduled
> | to run tonight, but I highly doubt anything is going to change.
> |
> | Are there some security settings I could double-check perhaps?
> |
> | Thanks,
> | -Rich|||They may know more about this here.
http://www.microsoft.com/communitie...oft.com/protect
"Rich" wrote:
| Thanks Dave,
|
| I've looked at a few things suggested in the link you provided but
| nothing worked. Finally, I created a new login for the windows
| Administrator account and added it to the SysAdmin role. This worked!
| Now, this stumps me, because the Windows workgroup "Administrators" is
| already a member of SysAdmin, and the Windows Administrator account is
| already assigned to the Administrators role... so it should have had
| permissions already. Any thoughts on this?
|
| Additionally, I mentioned that the job was not recording its log file.
| This was mistaken - I was looking under the SQL Server logs (under
| "Management"), but I just found them under DTS, "package logs".
| However, there are no entries for when the package ran as a scheduled
| job ... a log entry was recorded only when I ran the job manually. This
| was really puzzling to me, but then I realized that it had to be a
| security problem. The job wasn't getting anywhere, because the SQL
| Agent was running under an account that didn't have the right
| permissions applied (apparently).
|
| -Rich
