Error during SQL 2000 SP3a upgrade

I received the following error while executing the
REPLCOM.SQL script during the upgrade.
[DBNETLIB]General network error. Check your network
documentation.
[DBNETLIB]ConnectionRead (recv()).
This was the only output in REPLCOM.OUT.
Any ideas, I upgraded other servers and this did not
happen. I was upgrading from SQL 2000 SP2.
Mark,
Is the SQL Server service pack directory you are installing from on the
network or on your local machine? Perhaps there was a network outage
whilst the upgrade was running?
Can you copy the install directory locally and run it again?
Mark Allison, SQL Server MVP
http://www.markallison.co.uk
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602m.html
Mark Gozick wrote:
> I received the following error while executing the
> REPLCOM.SQL script during the upgrade.
> [DBNETLIB]General network error. Check your network
> documentation.
> [DBNETLIB]ConnectionRead (recv()).
> This was the only output in REPLCOM.OUT.
> Any ideas, I upgraded other servers and this did not
> happen. I was upgrading from SQL 2000 SP2.
sql

Error during SQL 2000 SP3a upgrade

I received the following error while executing the
REPLCOM.SQL script during the upgrade.
[DBNETLIB]General network error. Check your network
documentation.
[DBNETLIB]ConnectionRead (recv()).
This was the only output in REPLCOM.OUT.
Any ideas, I upgraded other servers and this did not
happen. I was upgrading from SQL 2000 SP2.Mark,
Is the SQL Server service pack directory you are installing from on the
network or on your local machine? Perhaps there was a network outage
whilst the upgrade was running?
Can you copy the install directory locally and run it again?
--
Mark Allison, SQL Server MVP
http://www.markallison.co.uk
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602m.html
Mark Gozick wrote:
> I received the following error while executing the
> REPLCOM.SQL script during the upgrade.
> [DBNETLIB]General network error. Check your network
> documentation.
> [DBNETLIB]ConnectionRead (recv()).
> This was the only output in REPLCOM.OUT.
> Any ideas, I upgraded other servers and this did not
> happen. I was upgrading from SQL 2000 SP2.

Error during SQL 2000 SP3a upgrade

I received the following error while executing the
REPLCOM.SQL script during the upgrade.
[DBNETLIB]General network error. Check your network
documentation.
[DBNETLIB]ConnectionRead (recv()).
This was the only output in REPLCOM.OUT.
Any ideas, I upgraded other servers and this did not
happen. I was upgrading from SQL 2000 SP2.Mark,
Is the SQL Server service pack directory you are installing from on the
network or on your local machine? Perhaps there was a network outage
whilst the upgrade was running?
Can you copy the install directory locally and run it again?
--
Mark Allison, SQL Server MVP
http://www.markallison.co.uk
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602m.html
Mark Gozick wrote:
> I received the following error while executing the
> REPLCOM.SQL script during the upgrade.
> [DBNETLIB]General network error. Check your network
> documentation.
> [DBNETLIB]ConnectionRead (recv()).
> This was the only output in REPLCOM.OUT.
> Any ideas, I upgraded other servers and this did not
> happen. I was upgrading from SQL 2000 SP2.

Error During Job

We have getting an intermitant error when running
some of our Jobs.
ConnectionCheckForData (checkfordata)
[sqlstate 01000][message 10054]
General Network Error. Check Network Documentation
[sqlstat 08s01][error 11]
We can put retries on this step, and sometimes it
works after a couple of retries.. Other times
the job dies. If we restart the job, it will
usually complete.
We don't know why this is happening. The only thing
that step is doing is some inserts and deletes to a
couple of tables.
The connection problem seems to get worse as time goes
by... If we refresh the indexes, and do some other
database cleanup... it gets better.
Can anyone help us in preventing this problem
answered above - sometimes these newsgroups take a few minutes for posts to
appear...
Regards,
Greg Linwood
SQL Server MVP
"scot" <sstyer@.alltel.net> wrote in message
news:481001c42bcd$eff4bba0$a001280a@.phx.gbl...
> We have getting an intermitant error when running
> some of our Jobs.
> ConnectionCheckForData (checkfordata)
> [sqlstate 01000][message 10054]
> General Network Error. Check Network Documentation
> [sqlstat 08s01][error 11]
> We can put retries on this step, and sometimes it
> works after a couple of retries.. Other times
> the job dies. If we restart the job, it will
> usually complete.
> We don't know why this is happening. The only thing
> that step is doing is some inserts and deletes to a
> couple of tables.
> The connection problem seems to get worse as time goes
> by... If we refresh the indexes, and do some other
> database cleanup... it gets better.
> Can anyone help us in preventing this problem
>

Error during backup verify

SQL Server 2000.
Doing an SQL backup to a network shared drive on our file server.
Any help appreciated ...
During the verify on several different databases, I find the following
error in the Maintenance Plan log:
[Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 3203:
[Microsoft][ODBC SQL Server Driver][SQL Server]Read on
'\\Pfcdata\SQLBackup\PFCSQLT\pfcgold_db_200402102300.BAK' failed,
status = 64. See the SQL Server error log for more details.
[Microsoft][ODBC SQL Server Driver][SQL Server]VERIFY DATABASE is
terminating abnormally.
I get the following info from the SQL Server Error Log:
BackupMedium::ReportIoError: read failure on backup device
'\\Pfcdata\SQLBackup\PFCSQLT\pfcgold_db_200402162359.BAK'. Operating
system error 64(The specified network name is no longer available.).That is a common NT error. Could you test the network connections by copying
large files between the servers. Also have you checked the NT eventlogs on
the file server to see if you have any messages releated to network
problems.
Simon
This posting is provided "as is" with no warranties and confers no rights.
"SoCal Snapper" <snapperjackson@.juno.com> wrote in message
news:2d4f003f.0402251113.6c36d43d@.posting.google.com...
> SQL Server 2000.
> Doing an SQL backup to a network shared drive on our file server.
> Any help appreciated ...
> During the verify on several different databases, I find the following
> error in the Maintenance Plan log:
> [Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 3203:
> [Microsoft][ODBC SQL Server Driver][SQL Server]Read on
> '\\Pfcdata\SQLBackup\PFCSQLT\pfcgold_db_200402102300.BAK' failed,
> status = 64. See the SQL Server error log for more details.
> [Microsoft][ODBC SQL Server Driver][SQL Server]VERIFY DATABASE is
> terminating abnormally.
> I get the following info from the SQL Server Error Log:
> BackupMedium::ReportIoError: read failure on backup device
> '\\Pfcdata\SQLBackup\PFCSQLT\pfcgold_db_200402162359.BAK'. Operating
> system error 64(The specified network name is no longer available.).

Error during backup verify

SQL Server 2000.
Doing an SQL backup to a network shared drive on our file server.
Any help appreciated ...
During the verify on several different databases, I find the following
error in the Maintenance Plan log:
[Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 3203:
[Microsoft][ODBC SQL Server Driver][SQL Server]Read on
'\\Pfcdata\SQLBackup\PFCSQLT\pfcgold_db_
200402102300.BAK' failed,
status = 64. See the SQL Server error log for more details.
[Microsoft][ODBC SQL Server Driver][SQL Server]VERIFY DATABASE i
s
terminating abnormally.
I get the following info from the SQL Server Error Log:
BackupMedium::ReportIoError: read failure on backup device
'\\Pfcdata\SQLBackup\PFCSQLT\pfcgold_db_
200402162359.BAK'. Operating
system error 64(The specified network name is no longer available.).That is a common NT error. Could you test the network connections by copying
large files between the servers. Also have you checked the NT eventlogs on
the file server to see if you have any messages releated to network
problems.
Simon
This posting is provided "as is" with no warranties and confers no rights.
"SoCal Snapper" <snapperjackson@.juno.com> wrote in message
news:2d4f003f.0402251113.6c36d43d@.posting.google.com...
> SQL Server 2000.
> Doing an SQL backup to a network shared drive on our file server.
> Any help appreciated ...
> During the verify on several different databases, I find the following
> error in the Maintenance Plan log:
> [Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 3203:
> [Microsoft][ODBC SQL Server Driver][SQL Server]Read on
> '\\Pfcdata\SQLBackup\PFCSQLT\pfcgold_db_
200402102300.BAK' failed,
> status = 64. See the SQL Server error log for more details.
> [Microsoft][ODBC SQL Server Driver][SQL Server]VERIFY DATABASE
is
> terminating abnormally.
> I get the following info from the SQL Server Error Log:
> BackupMedium::ReportIoError: read failure on backup device
> '\\Pfcdata\SQLBackup\PFCSQLT\pfcgold_db_
200402162359.BAK'. Operating
> system error 64(The specified network name is no longer available.).sql

Error Creating a new cluster on windows 2003 Server EE SP1

Hi,
I'm trying to install cluster service on a Windows 2003 Server Enterprise
Edition SP1.
I've configured Network and Disk.
When I try to create a new a new cluster for the first node, I receive this
error:
Found an existing cluster or node with the name "pippo.mydomain.com". Choose
another name.
A cluster cannot be created with the specified cluster name because that
cluster name is already in use. Specify a different name for the cluster.
I try to change netbios name but it does nothing.(NETBIOS name pippo does
not exsist in mydomain.....i try to use net view \\pippo)
Can You help Me ?
Tank you.
Have you tried to create this cluster before? Chances are that you still
have a DNS entry that needs to be flushed. All Address and Pointer records
for this host/IP address combination need to be flushed before you try and
reinstall.
Sincerely,
Anthony Thomas

"AS" <AS@.discussions.microsoft.com> wrote in message
news:7E9BC8F9-AA47-4D21-B7CF-71E876B9E6F1@.microsoft.com...
Hi,
I'm trying to install cluster service on a Windows 2003 Server Enterprise
Edition SP1.
I've configured Network and Disk.
When I try to create a new a new cluster for the first node, I receive this
error:
Found an existing cluster or node with the name "pippo.mydomain.com". Choose
another name.
A cluster cannot be created with the specified cluster name because that
cluster name is already in use. Specify a different name for the cluster.
I try to change netbios name but it does nothing.(NETBIOS name pippo does
not exsist in mydomain.....i try to use net view \\pippo)
Can You help Me ?
Tank you.

Error ConnectionRead (WrapperRead())

Hi
When I ran the ran the backups of my databases I ahve the next error
ConnectionRead (WrapperRead()). [SQLSTATE 01000]
Msg 11, Sev 16: General network error. Check your network documentation.
[SQLSTATE 08S01]
I’m running windows2000 Server Standard Edition, SQL2000 Server Standard
Edition and MDAC2.6 version.
I found the article 827452 but this article
APPLIES TO
? Microsoft Data Access Components 2.8
? Microsoft SQL Server 2000 Standard Edition, when used with:
Microsoft Windows Server 2003, Standard Edition
Microsoft Windows 2000 Enterprise Edition
I want to know if this article applies for my case
I run the sproc for backup the databases
Thanks very much
See http://support.microsoft.com/default...b;en-us;827452
Adrian
"Valero" <Valero@.discussions.microsoft.com> wrote in message
news:DEE2A24E-F805-4E56-BDD6-265C6A217912@.microsoft.com...
> Hi
> When I ran the ran the backups of my databases I ahve the next error
> ConnectionRead (WrapperRead()). [SQLSTATE 01000]
> Msg 11, Sev 16: General network error. Check your network documentation.
> [SQLSTATE 08S01]
>
> I'm running windows2000 Server Standard Edition, SQL2000 Server Standard
> Edition and MDAC2.6 version.
> I found the article 827452 but this article
> APPLIES TO
> . Microsoft Data Access Components 2.8
> . Microsoft SQL Server 2000 Standard Edition, when used with:
> Microsoft Windows Server 2003, Standard Edition
> Microsoft Windows 2000 Enterprise Edition
> I want to know if this article applies for my case
> I run the sproc for backup the databases
> Thanks very much
>