General NetWork Error Check network configuration

Hi to all
i have two sql servers
the first one is a win 2000 sever serverA
and the second one is a win xp ServerB
..i have created a push subscription at sql server ServerA
..i had many problems finally i installed the sp3 on both machine
..the first time i ran the replication at serverA via a dial up connection
with modem
it took 45 mins for 11135 inserts.
It had also certain conficts.
So i re run the replication but this time i have an error
"General network error. Check your network documentation.
(Source: MAILVXE (Data source); Error number: 11)"
I restarted the mahine but in vain the same error is repeated.
Please help me .
Thanks in advance
Soobrassen
General network error means there is a problem with your link. It could be
name resolution (unlikely as it was resolving ok for 45 minutes), bandwidth,
or a problem with the connection.
I am not sure where you are in deploying your snapshot, it sounds like it is
deployed. If so, you should wrap your distribution agent in an infinite
loop, have step 3 on failure, return to step 1.
To check name resolution problems issue a ping -a subscriber ip from the
publisher if you are doing a push, or a ping -a publisher ip from the
subscriber. To check to bandwidth copy a 1 Mg file and see how long it
takes. Copying smaller files will not necessarily give meaningful results.
You can also run keep alive scripts, like ping -t subscriber name to
discover when your connection fails, or to determine how lossy or unstable
your connection is.
There is another possibility where your publisher or subscriber gets so
bogged down that it can't respond in the time window allotted to your
distribution agent. Running perform on the subcriber or publisher and
monitoring cpu usage can help you here.
Hilary Cotter
Looking for a SQL Server replication book?
Now available for purchase at:
http://www.nwsu.com/0974973602.html
"Soobrassen Thoplan" <Soobrassen Thoplan@.discussions.microsoft.com> wrote in
message news:AFA9A029-80FC-44CA-A830-04A604D612EC@.microsoft.com...
> Hi to all
> i have two sql servers
> the first one is a win 2000 sever serverA
> and the second one is a win xp ServerB
> .i have created a push subscription at sql server ServerA
> .i had many problems finally i installed the sp3 on both machine
> .the first time i ran the replication at serverA via a dial up connection
> with modem
> it took 45 mins for 11135 inserts.
> It had also certain conficts.
> So i re run the replication but this time i have an error
> "General network error. Check your network documentation.
> (Source: MAILVXE (Data source); Error number: 11)"
> I restarted the mahine but in vain the same error is repeated.
> Please help me .
> Thanks in advance
> Soobrassen
>

General network error causes

What are some reasons for why we could see General network error at times ?
Is it purely network related by its name? Or are there other possible causes
for obtaining the message.
Using SQL 2005Drivers, Nic, Cable, Routers, MDAC issues, etc.
I've never seen a GNE that wasn't network related, but that doens't mean it
couldn't happen
--
Kevin Hill
IC3 North Texas
www.ChristianCycling.com
Please support me in the 2008 MS150:
http://www.ms150.org/dallas/donate/donate.cfm?id=208000
"Hassan" <hassan@.hotmail.com> wrote in message
news:OmHPVPXTIHA.1204@.TK2MSFTNGP03.phx.gbl...
> What are some reasons for why we could see General network error at times
> ? Is it purely network related by its name? Or are there other possible
> causes for obtaining the message.
> Using SQL 2005
>|||Hi
If there is nothing in the SQL Server Event log then it is most likely a
network issue, although it may be related to something such as a virus
checker or IDS system. Check the protocol being used is what you expect.
Check out the windows event log for any other network type issue that occurs
around the same time. Also check the network settings are correct and make
sure that you don't have DNS issues, check all cables and hubs/routers for
collisions or hardware issues.
John
"Hassan" wrote:
> What are some reasons for why we could see General network error at times ?
> Is it purely network related by its name? Or are there other possible causes
> for obtaining the message.
> Using SQL 2005
>
>|||John Bell wrote:
> Hi
> If there is nothing in the SQL Server Event log then it is most likely a
> network issue, although it may be related to something such as a virus
> checker or IDS system. Check the protocol being used is what you expect.
> Check out the windows event log for any other network type issue that occurs
> around the same time. Also check the network settings are correct and make
> sure that you don't have DNS issues, check all cables and hubs/routers for
> collisions or hardware issues.
> John
> "Hassan" wrote:
>
>> What are some reasons for why we could see General network error at times ?
>> Is it purely network related by its name? Or are there other possible causes
>> for obtaining the message.
>> Using SQL 2005
>>
>>
Also, you can get General Network Errors if you have your command
timeout set to 0.|||... and you can also get them using SSL, Lightweight Pooling, mice/rats
eating cables...!!
You may want to watch http://support.microsoft.com/kb/875285
John
"Jeffrey Williams" wrote:
> John Bell wrote:
> > Hi
> >
> > If there is nothing in the SQL Server Event log then it is most likely a
> > network issue, although it may be related to something such as a virus
> > checker or IDS system. Check the protocol being used is what you expect.
> >
> > Check out the windows event log for any other network type issue that occurs
> > around the same time. Also check the network settings are correct and make
> > sure that you don't have DNS issues, check all cables and hubs/routers for
> > collisions or hardware issues.
> >
> > John
> >
> > "Hassan" wrote:
> >
> >
> >> What are some reasons for why we could see General network error at times ?
> >> Is it purely network related by its name? Or are there other possible causes
> >> for obtaining the message.
> >>
> >> Using SQL 2005
> >>
> >>
> >>
> >>
> Also, you can get General Network Errors if you have your command
> timeout set to 0.
>

General network error causes

What are some reasons for why we could see General network error at times ?
Is it purely network related by its name? Or are there other possible causes
for obtaining the message.
Using SQL 2005
Drivers, Nic, Cable, Routers, MDAC issues, etc.
I've never seen a GNE that wasn't network related, but that doens't mean it
couldn't happen
Kevin Hill
IC3 North Texas
www.ChristianCycling.com
Please support me in the 2008 MS150:
http://www.ms150.org/dallas/donate/donate.cfm?id=208000
"Hassan" <hassan@.hotmail.com> wrote in message
news:OmHPVPXTIHA.1204@.TK2MSFTNGP03.phx.gbl...
> What are some reasons for why we could see General network error at times
> ? Is it purely network related by its name? Or are there other possible
> causes for obtaining the message.
> Using SQL 2005
>
|||Hi
If there is nothing in the SQL Server Event log then it is most likely a
network issue, although it may be related to something such as a virus
checker or IDS system. Check the protocol being used is what you expect.
Check out the windows event log for any other network type issue that occurs
around the same time. Also check the network settings are correct and make
sure that you don't have DNS issues, check all cables and hubs/routers for
collisions or hardware issues.
John
"Hassan" wrote:

> What are some reasons for why we could see General network error at times ?
> Is it purely network related by its name? Or are there other possible causes
> for obtaining the message.
> Using SQL 2005
>
>
|||John Bell wrote:[vbcol=seagreen]
> Hi
> If there is nothing in the SQL Server Event log then it is most likely a
> network issue, although it may be related to something such as a virus
> checker or IDS system. Check the protocol being used is what you expect.
> Check out the windows event log for any other network type issue that occurs
> around the same time. Also check the network settings are correct and make
> sure that you don't have DNS issues, check all cables and hubs/routers for
> collisions or hardware issues.
> John
> "Hassan" wrote:
>
Also, you can get General Network Errors if you have your command
timeout set to 0.
|||... and you can also get them using SSL, Lightweight Pooling, mice/rats
eating cables...!!
You may want to watch http://support.microsoft.com/kb/875285
John
"Jeffrey Williams" wrote:

> John Bell wrote:
> Also, you can get General Network Errors if you have your command
> timeout set to 0.
>

General network error causes

What are some reasons for why we could see General network error at times ?
Is it purely network related by its name? Or are there other possible causes
for obtaining the message.
Using SQL 2005Drivers, Nic, Cable, Routers, MDAC issues, etc.
I've never seen a GNE that wasn't network related, but that doens't mean it
couldn't happen
Kevin Hill
IC3 North Texas
www.ChristianCycling.com
Please support me in the 2008 MS150:
http://www.ms150.org/dallas/donate/donate.cfm?id=208000
"Hassan" <hassan@.hotmail.com> wrote in message
news:OmHPVPXTIHA.1204@.TK2MSFTNGP03.phx.gbl...
> What are some reasons for why we could see General network error at times
> ? Is it purely network related by its name? Or are there other possible
> causes for obtaining the message.
> Using SQL 2005
>|||Hi
If there is nothing in the SQL Server Event log then it is most likely a
network issue, although it may be related to something such as a virus
checker or IDS system. Check the protocol being used is what you expect.
Check out the windows event log for any other network type issue that occurs
around the same time. Also check the network settings are correct and make
sure that you don't have DNS issues, check all cables and hubs/routers for
collisions or hardware issues.
John
"Hassan" wrote:

> What are some reasons for why we could see General network error at times
?
> Is it purely network related by its name? Or are there other possible caus
es
> for obtaining the message.
> Using SQL 2005
>
>|||John Bell wrote:[vbcol=seagreen]
> Hi
> If there is nothing in the SQL Server Event log then it is most likely a
> network issue, although it may be related to something such as a virus
> checker or IDS system. Check the protocol being used is what you expect.
> Check out the windows event log for any other network type issue that occu
rs
> around the same time. Also check the network settings are correct and make
> sure that you don't have DNS issues, check all cables and hubs/routers for
> collisions or hardware issues.
> John
> "Hassan" wrote:
>
Also, you can get General Network Errors if you have your command
timeout set to 0.|||... and you can also get them using SSL, Lightweight Pooling, mice/rats
eating cables...!!
You may want to watch http://support.microsoft.com/kb/875285
John
"Jeffrey Williams" wrote:

> John Bell wrote:
> Also, you can get General Network Errors if you have your command
> timeout set to 0.
>sql

General Network Error / SQL Server does not exist

Hi world,
I get the General Network Error (and sometimes the SqlServer does not
exist).
I used to get this issue for the past few months. What I used to do is
restart SQL Server (from the system tray) one or two times and it used
to continue working. I never cared.
Now one of our customers is complaining the same issue! :-)
Googling about i heard people offering "setting named pipes as the
default". I went to the Sql Server Client Network Utility program and
couldn't find any such option in the "DB-Library Options" tab to change
this default setting.
Or is the above solution for some other problem.
Thanks a lot..
Regards,
MichelleHave you tried setting up an alias to your sql server using tcp/ip?
Please post your os/sql environment as well as your clients
nivek
<mich_stone@.yahoo.com> wrote in message
news:1109590304.342547.188290@.f14g2000cwb.googlegroups.com...
> Hi world,
> I get the General Network Error (and sometimes the SqlServer does not
> exist).
> I used to get this issue for the past few months. What I used to do is
> restart SQL Server (from the system tray) one or two times and it used
> to continue working. I never cared.
> Now one of our customers is complaining the same issue! :-)
> Googling about i heard people offering "setting named pipes as the
> default". I went to the Sql Server Client Network Utility program and
> couldn't find any such option in the "DB-Library Options" tab to change
> this default setting.
> Or is the above solution for some other problem.
> Thanks a lot..
> Regards,
> Michelle
>|||Thanks for the reply. Here is some more info on my problem
OS : Windows XP
Application: On ASP.NET
Sql Server: Developer Edition (also tried with MSDE)
The application always looks at "localhost"
I have "NAMED PIPES" and "TCPIP" in the GENERAL tab selected in the
network client utility. Clicking Properties on NAMED PIPES gives
"Network Protocal Default Value Setup = sql\query". Clicking properties
on TCPIP gives "1433".
I have two aliases defined to two OTHER servers on the internet. I am
just mentioning that for completeness, as those two servers have got
nothing to do with the one having the problem.
DB Library Options File Name = "c:\windows\system32\ntwdlib.dll"
Hope this is enough information for someone to help me out.
Thanks and regards
Michelle
nivek wrote:
> Have you tried setting up an alias to your sql server using tcp/ip?
> Please post your os/sql environment as well as your clients
> nivek
> <mich_stone@.yahoo.com> wrote in message
> news:1109590304.342547.188290@.f14g2000cwb.googlegroups.com...
> > Hi world,
> >
> > I get the General Network Error (and sometimes the SqlServer does
not
> > exist).
> >
> > I used to get this issue for the past few months. What I used to do
is
> > restart SQL Server (from the system tray) one or two times and it
used
> > to continue working. I never cared.
> >
> > Now one of our customers is complaining the same issue! :-)
> >
> > Googling about i heard people offering "setting named pipes as the
> > default". I went to the Sql Server Client Network Utility program
and
> > couldn't find any such option in the "DB-Library Options" tab to
change
> > this default setting.
> >
> > Or is the above solution for some other problem.
> >
> > Thanks a lot..
> >
> > Regards,
> >
> > Michelle
> >

General Network Error / SQL Server does not exist

Hi world,
I get the General Network Error (and sometimes the SqlServer does not
exist).
I used to get this issue for the past few months. What I used to do is
restart SQL Server (from the system tray) one or two times and it used
to continue working. I never cared.
Now one of our customers is complaining the same issue! :-)
Googling about i heard people offering "setting named pipes as the
default". I went to the Sql Server Client Network Utility program and
couldn't find any such option in the "DB-Library Options" tab to change
this default setting.
Or is the above solution for some other problem.
Thanks a lot..
Regards,
Michelle
Have you tried setting up an alias to your sql server using tcp/ip?
Please post your os/sql environment as well as your clients
nivek
<mich_stone@.yahoo.com> wrote in message
news:1109590304.342547.188290@.f14g2000cwb.googlegr oups.com...
> Hi world,
> I get the General Network Error (and sometimes the SqlServer does not
> exist).
> I used to get this issue for the past few months. What I used to do is
> restart SQL Server (from the system tray) one or two times and it used
> to continue working. I never cared.
> Now one of our customers is complaining the same issue! :-)
> Googling about i heard people offering "setting named pipes as the
> default". I went to the Sql Server Client Network Utility program and
> couldn't find any such option in the "DB-Library Options" tab to change
> this default setting.
> Or is the above solution for some other problem.
> Thanks a lot..
> Regards,
> Michelle
>
|||Thanks for the reply. Here is some more info on my problem
OS : Windows XP
Application: On ASP.NET
Sql Server: Developer Edition (also tried with MSDE)
The application always looks at "localhost"
I have "NAMED PIPES" and "TCPIP" in the GENERAL tab selected in the
network client utility. Clicking Properties on NAMED PIPES gives
"Network Protocal Default Value Setup = sql\query". Clicking properties
on TCPIP gives "1433".
I have two aliases defined to two OTHER servers on the internet. I am
just mentioning that for completeness, as those two servers have got
nothing to do with the one having the problem.
DB Library Options File Name = "c:\windows\system32\ntwdlib.dll"
Hope this is enough information for someone to help me out.
Thanks and regards
Michelle
nivek wrote:[vbcol=seagreen]
> Have you tried setting up an alias to your sql server using tcp/ip?
> Please post your os/sql environment as well as your clients
> nivek
> <mich_stone@.yahoo.com> wrote in message
> news:1109590304.342547.188290@.f14g2000cwb.googlegr oups.com...
not[vbcol=seagreen]
is[vbcol=seagreen]
used[vbcol=seagreen]
and[vbcol=seagreen]
change[vbcol=seagreen]

General Network Error / SQL Server does not exist

Hi world,
I get the General Network Error (and sometimes the SqlServer does not
exist).
I used to get this issue for the past few months. What I used to do is
restart SQL Server (from the system tray) one or two times and it used
to continue working. I never cared.
Now one of our customers is complaining the same issue! :-)
Googling about i heard people offering "setting named pipes as the
default". I went to the Sql Server Client Network Utility program and
couldn't find any such option in the "DB-Library Options" tab to change
this default setting.
Or is the above solution for some other problem.
Thanks a lot..
Regards,
MichelleHave you tried setting up an alias to your sql server using tcp/ip?
Please post your os/sql environment as well as your clients
nivek
<mich_stone@.yahoo.com> wrote in message
news:1109590304.342547.188290@.f14g2000cwb.googlegroups.com...
> Hi world,
> I get the General Network Error (and sometimes the SqlServer does not
> exist).
> I used to get this issue for the past few months. What I used to do is
> restart SQL Server (from the system tray) one or two times and it used
> to continue working. I never cared.
> Now one of our customers is complaining the same issue! :-)
> Googling about i heard people offering "setting named pipes as the
> default". I went to the Sql Server Client Network Utility program and
> couldn't find any such option in the "DB-Library Options" tab to change
> this default setting.
> Or is the above solution for some other problem.
> Thanks a lot..
> Regards,
> Michelle
>|||Thanks for the reply. Here is some more info on my problem
OS : Windows XP
Application: On ASP.NET
Sql Server: Developer Edition (also tried with MSDE)
The application always looks at "localhost"
I have "NAMED PIPES" and "TCPIP" in the GENERAL tab selected in the
network client utility. Clicking Properties on NAMED PIPES gives
"Network Protocal Default Value Setup = sql\query". Clicking properties
on TCPIP gives "1433".
I have two aliases defined to two OTHER servers on the internet. I am
just mentioning that for completeness, as those two servers have got
nothing to do with the one having the problem.
DB Library Options File Name = "c:\windows\system32\ntwdlib.dll"
Hope this is enough information for someone to help me out.
Thanks and regards
Michelle
nivek wrote:[vbcol=seagreen]
> Have you tried setting up an alias to your sql server using tcp/ip?
> Please post your os/sql environment as well as your clients
> nivek
> <mich_stone@.yahoo.com> wrote in message
> news:1109590304.342547.188290@.f14g2000cwb.googlegroups.com...
not[vbcol=seagreen]
is[vbcol=seagreen]
used[vbcol=seagreen]
and[vbcol=seagreen]
change[vbcol=seagreen]