RE: Run a ssis package on SQL Server 2005 Error

Tech-Archive recommends: Fix windows errors by optimizing your registry

Hi Peter,

Thank you for your reply.
I don't think I have the permission issue, because
1. I can run the SSIS package succesfully in BIDS under the same user as SQL
Agent
2. The user is a domin user and it has full permission on the remote server,
which the "Flat File Connection Manager" connect to.
3. It also works in command prompt.
4. It also works in Integration Service

If I run it as job, then I received teh following message:
Executed as user: Domin\xxxxx The package execution failed. The step failed

In SQL Server Integration Service Log, I found the the following message:
Event Name: OnError
Message: Connection "Flat File Connection Manager" failed validation
The connection(Flat File Connection Manager) is for the task --export data
to a remote server as txt file.

SQL Server 2005 and Agent are run under Domin\xxxxx, but Integration Service
is run by another user. Is it cause the issue?

Thanks
Kevin



""Peter Yang[MSFT]"" wrote:

Hello

It seems that you encounter the permission issue described in the following
KB:

933835 Error message when an SSIS package runs that is scheduled to run as
a SQL Server Agent job: "An OLE DB error has occurred. Error code:
0x80004005"
http://support.microsoft.com/default.aspx?scid=kb;EN-US;933835

Please check if this resolves the problem. 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.


.

Relevant Pages

  • Re: Outlook for MAPI on SBS
    ... I wound up looking at another thread here on installing SQL 2005 which I ... I have noticed something interesting here in SBS ... agent from the SBS Monitoring Agent to the 2005 agent instance. ... Is there an easy way to set up notifications from SQL Server ...
    (microsoft.public.windows.server.sbs)
  • Re: Outlook for MAPI on SBS
    ... I wound up looking at another thread here on installing SQL 2005 which I ... particularly 2005 on SBS. ... agent from the SBS Monitoring Agent to the 2005 agent instance. ... Is there an easy way to set up notifications from SQL Server ...
    (microsoft.public.windows.server.sbs)
  • Setting DCOMCNFG LaunchPermission registry value for everyone group back to "special access"
    ... trying to push content from one SQL server to a cluster server. ... Also this replication ... got TimeOut exipred messages when the agent ran - the specific error message ... SQL Server Agent could not access the replication agent. ...
    (microsoft.public.sqlserver.connect)
  • Setting DCOMCNFG LaunchPermission registry value for everyone group back to "special access"
    ... trying to push content from one SQL server to a cluster server. ... Also this replication ... got TimeOut exipred messages when the agent ran - the specific error message ... SQL Server Agent could not access the replication agent. ...
    (microsoft.public.sqlserver.clustering)
  • Setting DCOMCNFG LaunchPermission registry value for everyone group back to "special access"
    ... trying to push content from one SQL server to a cluster server. ... Also this replication ... got TimeOut exipred messages when the agent ran - the specific error message ... SQL Server Agent could not access the replication agent. ...
    (microsoft.public.sqlserver.security)