Hi Everybody,

I am having problems in DTS packages that runs nightly. It is
always the same Error at the same 'Execute SQL Task'. The ohter Tasks
in
the same DTS packages works fine with the same OLE connection.

"[DBNETLIB][ConnectionRead (recv()).]General network error.
Check your network documentation.".
Possible failure reasons: Problems with the query, "ResultSet" property
not set correctly, parameters not set correctly, or connection not
established correctly."

But if I execute the task manually, it works.

We have SQL server 2005 on WK2003

Any help will be appreciated.
Thanks, gollo007

Please give more details: You are running 2005, so is this an SSIS package
rather than a DTS package? Are you running a DTS package from SSIS? What is
the Execute SQL Task doing?

Hope this helps.

Charles Kangai, MCT, MCDBA
Author of Learning Tree's 4-day course: "SQL Server 2005 Integration
Services" http://www.learningtree.com/courses/134.htm
Author of Learning Tree's 4-day course: "SQL Server Reporting Services"
http://www.learningtree.com/courses/523.htm
email alias: charles
email domain: kangai.demon.co.uk


"gollo007" wrote:

Hi,

we are using SISS package (no DTS package sorry). In the task we have a
SQL that update columns. If I start the task manually, the task run 45
minutes.

Thanks, gollo007



Charles Kangai schrieb:

It could be a security issue. That is usually the main reason why a job that
runs successfully interactively then fails to run when scheduled. Try using
the Run As feature to get round this. To do this, see the following Books
Online topic:
ms-help://MS.SQLCC.v9/MS.SQLSVR.v9.en/extran9/html/69d3958c-6abc-41ae-8428-312917867c9a.htm

Hope this helps.

Charles Kangai, MCT, MCDBA
Author of Learning Tree's 4-day course: "SQL Server 2005 Integration
Services" http://www.learningtree.com/courses/134.htm
Author of Learning Tree's 4-day course: "SQL Server Reporting Services"
http://www.learningtree.com/courses/523.htm
email alias: charles
email domain: kangai.demon.co.uk


"gollo007" wrote:

Thank you for your help,

but this suggestion don't help me.

My problem is that the task start but after a few minutes the task was
canceled with the error 'general Network error' if the task was
scheduled .

We have try follow suggestion
http://support.microsoft.com/default...b;EN-US;899599
but it didn't help.

Thanks, gollo007


Charles Kangai schrieb:

Thank you for your help,

but your suggestion don't help me.

My Problem is, when the task was scheduled, it start but after a few
minutes the task end with 'General network error'.

I've test the follow suggestion but it doesn't help

http://support.microsoft.com/default...b;EN-US;899599

gollo007


Charles Kangai schrieb:

Have you had any luck figuring this out, I seem to be seeing the same error?

Hi Everybody,

I am having problems in DTS packages that runs nightly. It is
always the same Error at the same 'Execute SQL Task'. The ohter Tasks
in
the same DTS packages works fine with the same OLE connection.

"[DBNETLIB][ConnectionRead (recv()).]General network error.
Check your network documentation.".
Possible failure reasons: Problems with the query, "ResultSet" property
not set correctly, parameters not set correctly, or connection not
established correctly."

But if I execute the task manually, it works.

We have SQL server 2005 on WK2003

Any help will be appreciated.
Thanks, gollo007

If the person who created the job is not an administrator, I suggest you get
an administrator to create the job and see whether the error still occurs.
It is very likely that this is a security error. The problem can still occur
if the job creator is a sysadmin but the SQL Server Agent service has no
access to some of the resources required to execute the package [e.g. SQL
Server AGent is running with a Local System account and it needs to access a
domain resource].

You need to create a proxy and specify it in the Run As box of your job
step. Steps to create a proxy are:
1) Create a credential and give it a Windows account. The Windows account
must have access to all the resources required to run the package. Best
choice is the Windows account of the person who interactively successfully
ran the package. Go to Security/Credentials folder in SSMS to do this.
2) Create a proxy and associate it with the credential you just created.
Specify the principals for the proxy. This specifies the logins/users/roles
who are allowed to use the proxy.
3) Make sure that the user creating the job is in one of these three msdb
database roles: SQLAgentUserRole, SQLAgentReaderRole or SQLAgentOperatorRole
(permissions increase in this order).
4) Now create the job and specify the proxy created at Step 2 in the Run As
box of the job step.(The job step type must be set to SQL Server Integration
Services Package).

Note that this is the only supported way of scheduling SSIS packages.

Hope this helps.

Charles Kangai, MCT, MCDBA
Author of Learning Tree's 4-day course: "SQL Server 2005 Integration
Services" http://www.learningtree.com/courses/134.htm
Author of Learning Tree's 4-day course: "SQL Server Reporting Services"
http://www.learningtree.com/courses/523.htm
email alias: charles
email domain: kangai.demon.co.uk



"James Wuerflein" wrote: