Re: Very Very Urgent, Please Help
- From: Jéjé <willgart@xxxxxxxxxxxxxxxxx>
- Date: Thu, 8 Sep 2005 19:06:08 -0400
does the SQL Agent service run under a known account?
"DKRReddy" <dkrreddy@xxxxxxxxxxx> wrote in message news:%23SWDRmJtFHA.664@xxxxxxxxxxxxxxxxxxxxxxx
When running the dts package as a job , it's failing while opening the package itself. Security log in keep filling, is this the cause?
"Darren Gosbell" <dgosbell_at_yahoo_dot_com> wrote in message news:MPG.1d88f7c738031b6f989685@xxxxxxxxxxxxxxxxxxxxx This sounds like a permissions issue. If you can run the packages from Enterprise manager then the issue is not necessarily with the packages themselves.
If the packages are executed via a SQL agent job that launches them using dtsrun, then I suggest you check which account the SQL Agent service is running under. It might also have something to do with the owner of the Agent jobs.
Packages run via Enterprise Manager run in the security context of the currently logged on user. Packages launched via SQL Agent run in the context of the account that the SQL Agent Service logs in under.
-- Regards Darren Gosbell <dgosbell_at_yahoo_dot_com> Blog: http://www.geekswithblogs.net/darrengosbell
In article <eP$UU6osFHA.3164@xxxxxxxxxxxxxxxxxxxx>, dkrreddy@xxxxxxxxxxx says...All packages are refering to the new server only.If I run the package fromif
enterprise manager runs fine no timeout errors.
"Jéjé" <willgart@xxxxxxxxxxxxxxxxx> wrote in message
news:OHhuUhnsFHA.3404@xxxxxxxxxxxxxxxxxxxxxxx
> does your packages are stored in the MSDB database?
> Have you changed your main package to use the right SQL Server > instance?
>
> if your main dts package try to open a package on the <old server> and> this server is down, then you'll receive a timeout error.
>
>
> "DKRReddy" <dkrreddy@xxxxxxxxxxx> wrote in message
> news:Osp3hXnsFHA.236@xxxxxxxxxxxxxxxxxxxxxxx
> > My Main dts package calls many other simple dts packages.
> > When my main dts package calls other dts packages getting timeout
> > immediately.
> >
> > Is there any settings at package level to increase the timeout.
> >
> >
> >
> > "Jéjé" <willgart@xxxxxxxxxxxxxxxxx> wrote in message
> > news:OITN%23MmsFHA.332@xxxxxxxxxxxxxxxxxxxxxxx
> >> can you create a new empty package and create a new connection to > >> the
> >> database?
> >>
> >> have you validated the connections in your packages?
> >>
> >>
> >>
> >> "DKRReddy" <dkrreddy@xxxxxxxxxxx> wrote in message
> >> news:OeJz4AlsFHA.3604@xxxxxxxxxxxxxxxxxxxxxxx
> >> > Recently we have migrated the datawarehouse server to windows > >> > 2003
> > server
> >> > from windows 2000 server.
> >> > Since then all dts packages are getting timedout with the > >> > following
> > error.
> >> >
> >> > Step Error Source: Microsoft OLE DB Provider for SQL Server
> >> > Step Error Description:Timeout expired
> >> > Step Error code: 80004005
> >> > Step Error Help File:
> >> > Step Error Help Context ID:0
> >> >
> >> >
> >> > The new server is very high end server which has 8 processors and
12GB
.
- Follow-Ups:
- Re: Very Very Urgent, Please Help
- From: Darren Gosbell
- Re: Very Very Urgent, Please Help
- References:
- Very Very Urgent, Please Help
- From: DKRReddy
- Re: Very Very Urgent, Please Help
- From: Jéjé
- Re: Very Very Urgent, Please Help
- From: DKRReddy
- Re: Very Very Urgent, Please Help
- From: Jéjé
- Re: Very Very Urgent, Please Help
- From: DKRReddy
- Re: Very Very Urgent, Please Help
- From: Darren Gosbell
- Re: Very Very Urgent, Please Help
- From: DKRReddy
- Very Very Urgent, Please Help
- Prev by Date: Re: Very Very Urgent, Please Help
- Next by Date: Re: Very Very Urgent, Please Help
- Previous by thread: Re: Very Very Urgent, Please Help
- Next by thread: Re: Very Very Urgent, Please Help
- Index(es):
Relevant Pages
|
Loading