General network error.

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.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...
> 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.
> >
> >
> >
> >.
> >|||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...
> > 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.
> > >
> > >
> > >
> > >.
> > >
>
>

General network error

I am running on Win2k, SQL Server 2000 (sp3), MDAC 2.8 and using a
TCP/IP client connection.

I get this error when attempting to restore a database.

[Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionRead
(WrapperRead()).
[Microsoft][ODBC SQL Server Driver][DBNETLIB]General network error.
Check your network documentation.

Does anybody know how to resolve this issue?

ThanksHi

Have you checked that there is not a network problem? Try a different port,
check no errors in the event log ...

John

"CD" <carl.davis@.gmail.com> wrote in message
news:fceeddde.0408270623.5c9c9fec@.posting.google.c om...
> I am running on Win2k, SQL Server 2000 (sp3), MDAC 2.8 and using a
> TCP/IP client connection.
> I get this error when attempting to restore a database.
>
> [Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionRead
> (WrapperRead()).
> [Microsoft][ODBC SQL Server Driver][DBNETLIB]General network error.
> Check your network documentation.
>
> Does anybody know how to resolve this issue?
> Thanks|||CD (carl.davis@.gmail.com) writes:
> I am running on Win2k, SQL Server 2000 (sp3), MDAC 2.8 and using a
> TCP/IP client connection.
> I get this error when attempting to restore a database.
>
> [Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionRead
> (WrapperRead()).
> [Microsoft][ODBC SQL Server Driver][DBNETLIB]General network error.
> Check your network documentation.
>
> Does anybody know how to resolve this issue?

That's bad. It appears that your SQL Server thread experiences an
access violation, or other serious execution error and termintates
your thread. This could be because the backup is corrupt or because
of a hardware problem on the disk you are trying to restore to.

If you look in the SQL Server error, you should find a stack dump, but
it is unlikely that this will give you any useful information.

If you are in serious need of that data, you should open a case with
Microsoft.

--
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se

Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techin.../2000/books.asp|||"CD" <carl.davis@.gmail.com> wrote in message
news:fceeddde.0408270623.5c9c9fec@.posting.google.c om...
> I am running on Win2k, SQL Server 2000 (sp3), MDAC 2.8 and using a
> TCP/IP client connection.
> I get this error when attempting to restore a database.
>
> [Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionRead
> (WrapperRead()).
> [Microsoft][ODBC SQL Server Driver][DBNETLIB]General network error.
> Check your network documentation.
>
> Does anybody know how to resolve this issue?
> Thanks

Check out
http://support.microsoft.com/defaul...2&Product=sql2k
as it relates specifically to your issue.

Kevin

Functions and Recompile

Hi,
I just had a strange occurrance on one of my SQL 2000 SP3 machines. (Win 200
3)
I changed the underlying table structure of two table, inserting a field in
the middle of the tables. All of the functions that referenced these did no
t
recompile when I next ran them. They starting giving me errors with data
conversion (Explicit from Varchar to money not allowed). This continued
until I explicitly ran sp_recompile on the function. I had to do this to al
l
of my functions that referenced this table to get them to work.
On another server I did the exact same thing to the exact same tables (the
dev system) and
all of the functions automatically recompiled on the next run.
My question I guess is...
Is there a setting to turn off/on auto recompile? I didn't think there was,
but that's the only reason I can think of the difference.
Or does anyone else have any ideas?
RyanHello Ryan,
Do you know if you turned off Auto update statistics on one database but
not the other?
Aaron Weiker
http://aaronweiker.com/

> Hi,
> I just had a strange occurrance on one of my SQL 2000 SP3 machines.
> (Win 2003)
> I changed the underlying table structure of two table, inserting a
> field in the middle of the tables. All of the functions that
> referenced these did not recompile when I next ran them. They
> starting giving me errors with data conversion (Explicit from Varchar
> to money not allowed). This continued until I explicitly ran
> sp_recompile on the function. I had to do this to all of my functions
> that referenced this table to get them to work.
> On another server I did the exact same thing to the exact same tables
> (the dev system) and all of the functions automatically recompiled on
> the next run.
> My question I guess is...
> Is there a setting to turn off/on auto recompile? I didn't think
> there was,
> but that's the only reason I can think of the difference.
> Or does anyone else have any ideas?
> Ryan
>|||Both of the DBs have auto update statistics set to on.
Thanks for the idea tho'.
Ryan
"Aaron Weiker" wrote:

> Hello Ryan,
> Do you know if you turned off Auto update statistics on one database but
> not the other?
> --
> Aaron Weiker
> http://aaronweiker.com/
>
>
>|||Hello Ryan,
Only other idea I have would be to search through the MS KB and see if there
is anything there about it. But it is definately a pretty odd occurance.
Aaron Weiker
http://aaronweiker.com/
http://sqlprogrammer.org/
> Both of the DBs have auto update statistics set to on.
> Thanks for the idea tho'.
> Ryan
> "Aaron Weiker" wrote:
>

Function sequence error - Merge Replication

We are replicating from 7 publishers to 1 subscriber all running MS SQL
Server 2000 SP3 using Merge Replication.
We are in the process of upgrading our application and due to that we had to
make
some changes to the database schema like add some columns, create a few new
tables, and triggers. We did all this through a script using stored
procedures on 2 of the publisher databases and then ran the snapshot agent.
That's when we started seeing the error.
Error Message: The process could not bulk copy out of table '[dbo].[Invoice]'.
Error details: Function sequence error
(Source: ODBC SQL Server Driver (ODBC); Error number: 0)
------
Does anyone know how to resolve this?
Do we need to do anything on the subscriber database because of the schema
change done on the publisher database ?
Thanks in advance,
I wish I could tell you how to solve this one. The good news is that it
seems to be transient.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Vikram" <Vikram@.discussions.microsoft.com> wrote in message
news:E1A11B74-CE85-4C1B-87F5-248919A882CE@.microsoft.com...
> We are replicating from 7 publishers to 1 subscriber all running MS SQL
> Server 2000 SP3 using Merge Replication.
> We are in the process of upgrading our application and due to that we had
to
> make
> some changes to the database schema like add some columns, create a few
new
> tables, and triggers. We did all this through a script using stored
> procedures on 2 of the publisher databases and then ran the snapshot
agent.
> That's when we started seeing the error.
> Error Message: The process could not bulk copy out of table
'[dbo].[Invoice]'.
> Error details: Function sequence error
> (Source: ODBC SQL Server Driver (ODBC); Error number: 0)
> ----
--
> Does anyone know how to resolve this?
> Do we need to do anything on the subscriber database because of the schema
> change done on the publisher database ?
>
> Thanks in advance,
>

Full-text search - catalog refuses to populate

Hello

I'm trying to get full-text searching to work on SQL Server 2000 (with SP3 installed).

I have a table containing many text fields that I want to search and so far have successfully gone through the "Full-Text wizard" selecting the text fields from the table I want as searchable. I then try and start full population of the catalog but its always remains zero in size when I check its properties. Hence when I try a query like:

SELECT Name FROM tblTextDocs WHERE CONTAINS(mainbody, 'find this')

It results in the error message:

Server: Msg 7619, Level 16, State 1, Line 1
Execution of a full-text operation failed. The catalog does not exist or is currently unavailable. Please retry the action again later and if this symptom persists, contact the system administrator.

It would appear that the catalog simply refuses to populate. I've tried starting population via Enterprise Manager and also by doing sp_fulltext_catalog 'MyCatalog', 'start_full'. The Full-text support service says it is running correctly and no other problems with the server have been experienced.

Any suggestions would be much appreciated.

Regards

SamBy the "Full Text Support Service" do you mean the "Microsoft Search" service?|||Originally posted by MCrowley
By the "Full Text Support Service" do you mean the "Microsoft Search" service?

Yes - the Microsoft Search service. I have no problems in stopping/starting it too.|||This error might occur if changing SQL Server Account to Non-Admin for Full-Text Search Makes Existing Catalogs Unusable.

To access existing full-text search catalogs, rebuild and repopulate them. The existing catalogs can also be accessed by switching back to an administrator account.