Re: Very Very Urgent, Please Help
- From: "DKRReddy" <dkrreddy@xxxxxxxxxxx>
- Date: Mon, 5 Sep 2005 19:52:58 -0700
All packages are refering to the new server only.If I run the package from
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 if
> 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
> >> > RAM,
> >> > and All dts packages are having simple deletes and data transfer
tasks.
> >> >
> >> > Daily updatestats was running during off hours and proper indices
are
> >> > there.
> >> > Ran the checkdb on all dbs, found no errors.
> >> >
> >> > I never seen these kind of erros on windows2000 and sql 2000 ee sp3.
> >> >
> >> > Is there any reason that sql2000 EE SP3 is not fully supported by
> > Windows
> >> > 2003 server.
> >> >
> >> > I have verified the query timeout settings on source and destination
> >> > server
> >> > which is 0 (unlimited)
> >> >
> >> > Please let me know if settings need to be checked.
> >> >
> >> >
> >> >
> >> > (Migration : dettahed the databases from windows 2000 server and
> >> > sql200
> >> > EE
> >> > sp3 and attached to the windows2003 server and Sql 200 EE sp3)
> >> >
> >> >
> >> > If any queries that were run from query analyzer are failing with the
> >> > following error afetr few minutes :
> >> >
> >> > [Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionRead
> >> > (WrapperRead()).
> >> > Server: Msg 11, Level 16, State 1, Line 0
> >> > General network error. Check your network documentation.
> >> > Connection Broken
> >> >
> >> >
> >> >
> >>
> >
> >
>
.
- 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é
- Very Very Urgent, Please Help
- Prev by Date: Re: Very Very Urgent, Please Help
- Next by Date: Re: Select And Insert
- Previous by thread: Re: Very Very Urgent, Please Help
- Next by thread: Re: Very Very Urgent, Please Help
- Index(es):
Relevant Pages
|