Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
Home
Discussion Groups
DB Engine
SQL ServerMSDESQL Server CE
Services
Analysis (Data Mining)Analysis (OLAP)DTSIntegration ServicesNotification ServicesReporting Services
Programming
CLRConnectivitySQLXML
Other Technologies
ClusteringEnglish QueryFull-Text SearchReplicationService Broker
General
Data WarehousingPerformanceSecuritySetupSQL Server ToolsOther SQL Server Topics
DirectoryUser Groups
Related Topics
MS AccessOther DB ProductsMS Server Products.NET DevelopmentVB DevelopmentJava DevelopmentMore Topics ...

SQL Server Forum / Services / Integration Services / July 2008

Tip: Looking for answers? Try searching our database.

newbie - problem with scheduling of package

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
Willard - 26 Jun 2008 14:49 GMT
Hi to all,
I've create a package that had to migrate record from an as400 to a
SqlServer2005.
When I launch the package from visual studio it work's fine, but when
I try to scheduled It with the sql server agent I've always this error
massage back

Executed as user: \SYSTEM. The package could not be loaded.  The step
failed.

Someone has some suggestion ?

thank's to all

Willard
matteus - 27 Jun 2008 10:17 GMT
> Hi to all,
> I've create a package that had to migrate record from an as400 to a
[quoted text clipped - 11 lines]
>
> Willard

Hi Willard,
\SYSTEM should be the SQLserver Agent Service Account.

When you have created the job's step which user did you choose for run
as?
And which type of authentication did you select for the connection
inside your package?

I faced (better, I'm facing) similar problems and I'm finding the
right way to execute scheduled packages.
Til now I save the package in sqlserver, setting all inner connections
to WIN authentication (instead of giving the SQL Login of the specific
DB I'm connecting to) and when I execute it through a job (scheduled
or not, i believe this shouldn't be important, sqlserver always uses
the SQLAgent Service Account) it works.
When i save the same package with sql login authentication (for the
inner connections) and execute it, it doesn't.
For both ways (win or sql authentication) when executed from inside
the BI Dev Studio it works.

hope this helps ;)
Willard - 01 Jul 2008 14:23 GMT
> > Hi to all,
> > I've create a package that had to migrate record from an as400 to a
[quoted text clipped - 33 lines]
>
> hope this helps ;)

I'll try to use both sql server autentication then windows
autentication inside sql server intelligence studio
and using sqlAgent Service account, but it dosen't work yet
If i launch my package by hands it works fine ...:(
Where I made mistake ?
matteus - 03 Jul 2008 13:30 GMT
> > > Hi to all,
> > > I've create a package that had to migrate record from an as400 to a
[quoted text clipped - 39 lines]
> If i launch my package by hands it works fine ...:(
> Where I made mistake ?

"Executed as user: \SYSTEM. The package could not be loaded. The step
failed."
Is this the error? And is SYSTEM the sqlagent account? Which account
is set in "Run As" in the related job's Step window?

if so, i'd try to change and set it to a Windows Account (both
administrative and not) using Sqlserver Configuration Manager.
Or better create a proxy account.
Check also this link:
http://support.microsoft.com/?scid=kb%3Ben-us%3B918760&x=10&y=13
or follow these instructions to debug:
http://wiki.sqlis.com/default.aspx/SQLISWiki/ScheduledPackages.html
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2008 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.