General network error.

This error message is generated from ODBC, and not really
from SQL Server. It is generated when a connection
something the ODBC fails ie DB2 (see Microsoft) so
although SQL Server is reporting it, it is not the cause.
I would sugest that you go through the Event View on your
NT, or put in a trace to see exactly where it fails.
J

>--Original Message--
>Receiving error:
>"General network error. Check your network documentation.
[SQLSTATE 08S01]
>(Error 11)".
>Running on SQLServer 2000 EE, SP3, Windows 2000 Adv.
>This started after we rebuild the server. We have tens
of jobs that run at
>night. This error is happening only randomly as some
days nothing happens
>and same job runs fine but other day it blows up. It is
not happening with
>same job either. Then we restart the job and it runs
fine.
>
>.
>
Nothing in the event log or SQLServer log accept that error message.
"Julie" <anonymous@.discussions.microsoft.com> wrote in message
news:1302301c4433d$9f6096f0$a101280a@.phx.gbl...[vbcol=seagreen]
> This error message is generated from ODBC, and not really
> from SQL Server. It is generated when a connection
> something the ODBC fails ie DB2 (see Microsoft) so
> although SQL Server is reporting it, it is not the cause.
> I would sugest that you go through the Event View on your
> NT, or put in a trace to see exactly where it fails.
> J
>
> [SQLSTATE 08S01]
> of jobs that run at
> days nothing happens
> not happening with
> fine.
|||Hi ilovesql,
We are expiriencing the same issue - I was woundering if you had this resolved.
I also wanted to ask you - when you rebuild the server did it have the same configuration as before or you installed SP3 for SQL Server?
We went from Win2000 server SQL server 2000 SP2 to WIN2003 server SP3 and we started to have this problem from that day on. Microsoft is working on it but this is the second day and they haven't came up with the solution.
I think it is SP3 - something is not right with it.
Thanks,
Anna
"ilovesql" wrote:

> Nothing in the event log or SQLServer log accept that error message.
>
> "Julie" <anonymous@.discussions.microsoft.com> wrote in message
> news:1302301c4433d$9f6096f0$a101280a@.phx.gbl...
>
>

General network error.

This error message is generated from ODBC, and not really
from SQL Server. It is generated when a connection
something the ODBC fails ie DB2 (see Microsoft) so
although SQL Server is reporting it, it is not the cause.
I would sugest that you go through the Event View on your
NT, or put in a trace to see exactly where it fails.
J

>--Original Message--
>Receiving error:
>"General network error. Check your network documentation.
[SQLSTATE 08S01]
>(Error 11)".
>Running on SQLServer 2000 EE, SP3, Windows 2000 Adv.
>This started after we rebuild the server. We have tens
of jobs that run at
>night. This error is happening only randomly as some
days nothing happens
>and same job runs fine but other day it blows up. It is
not happening with
>same job either. Then we restart the job and it runs
fine.
>
>.
>Nothing in the event log or SQLServer log accept that error message.
"Julie" <anonymous@.discussions.microsoft.com> wrote in message
news:1302301c4433d$9f6096f0$a101280a@.phx
.gbl...[vbcol=seagreen]
> This error message is generated from ODBC, and not really
> from SQL Server. It is generated when a connection
> something the ODBC fails ie DB2 (see Microsoft) so
> although SQL Server is reporting it, it is not the cause.
> I would sugest that you go through the Event View on your
> NT, or put in a trace to see exactly where it fails.
> J
>
> [SQLSTATE 08S01]
> of jobs that run at
> days nothing happens
> not happening with
> fine.|||Hi ilovesql,
We are expiriencing the same issue - I was woundering if you had this resolv
ed.
I also wanted to ask you - when you rebuild the server did it have the same
configuration as before or you installed SP3 for SQL Server?
We went from Win2000 server SQL server 2000 SP2 to WIN2003 server SP3 and we
started to have this problem from that day on. Microsoft is working on it b
ut this is the second day and they haven't came up with the solution.
I think it is SP3 - something is not right with it.
Thanks,
Anna
"ilovesql" wrote:

> Nothing in the event log or SQLServer log accept that error message.
>
> "Julie" <anonymous@.discussions.microsoft.com> wrote in message
> news:1302301c4433d$9f6096f0$a101280a@.phx
.gbl...
>
>sql

Full-Text Search gets syntax error and kills the transaction

I am having problems with syntax errors being generated from the search clause of a full-text search. When the syntax error is raised, the batch and transaction are stopped. Placing the search within a SQL Try/Catch allows the batch to continue, but the transaction is uncommitable.

I need to trap and handle the full-text search syntax error then control the commit or rollback of the transaction based on other transactions.

Below is a simplified version of the type of logic I am working with. The XACT_STATE goes to -1 because of the syntax error generated by the full-text search. This forces a rollback of the whole transaction.

Declare@.sSearch NVarChar(50)

/* @.sSearch is passed by a web page and could come back empty or with an invalid Full-Text search clause*/

Begin Transaction

Begin Try

Print XACT_STATE()

Select*

/*The table 'KnowledgeBase' is a table with a populated Full-Text Search*/

FromContainstable(KnowledgeBase,*,@.sSearch)

End Try

Begin Catch

Print XACT_STATE()

Print 'Number- ' + Convert(VarChar,ERROR_NUMBER()) + ', ' +

'Severity- ' + Convert(VarChar,ERROR_SEVERITY()) + ', ' +

'State- ' + Convert(VarChar,ERROR_STATE()) + ', ' +

'Message- "' + ERROR_MESSAGE() + '"'

End Catch

/*Some other logic would be here*/

Commit Transaction

I'm moving this post to the Transact-SQL forum because it's a better venue for code-related questions.

Regards,

Gail