Friday, March 30, 2012

Network integration for fresh install of 2005

I am working as a consultant on a project to upgrade an Access 2000 db to SQL Server. My client has bought off on everything, and they're ordering a new dedicated box this week. They're getting a rackmount machine running Windows Server and SQL Server 2005.

My expectation was that their IT people would take care of administrative & security issues such as setting the machine up, installing & starting SQL Server and configuring the proper accounts. Suprisingly though, they're going to mount the machine in the rack, turn it on and let me do all of this.

I'm new at SQL Server, but I'm comfortable working with database objects (tables, views, etc...) I'm not so comfortable with the networking or administrative side of things. It took me a couple of hours to be able to connect to the DB on my desktop machine over my home network. You can see why I'm intimidated at the prospect of getting things integrated & running on a pretty large corporate network.

Maybe I'm overblowing this, but this just gives me the willies.

Are my fears justified? Am I going to be ok if I just follow the standard procedures for allowing TCP/IP connections to the server? Am I going to have to deal with firewalls? (I think I know the answer - "it depends on their network.." - that's what I'm scared of.. I don't know anything about their network, and I don't know enough about networking in general to figure things out..)

Are there any other best practices that I should follow for a fresh install?So much depends on their network configuration that only their network people can give you a complete and correct answer to your questions. With that said, the general setup isn't difficult or complicated, the only problems I've ever run into arise when coping with installation specific problems.

Specific points to consider. If you don't know that you or your project need it, don't enable it. This especially applies to network protocols (only enable TCP/IP unless there is compelling reason for another protocol). If you don't need SQL Authentication, only select Windows Authentication.

Their network administrators are giving you a "blank check" to set things up as you'd like. This is idiocy on their part, but you should take advantage of it! Get the box running, in a minimal configuration. Set the box up as a "lone wolf" machine, then only after you are done getting things set up to suit yourself tell them you need a domain administrator login to join the box to their domain (this should put them into an outright panic), then stand back and watch the fun as they backpeddle furiously! At that point, you already have a tested, working configuration... Their only choices are to either a) give you the network equivalent of god-like powers, or b) pick up the ball that you've handed them and very quickly figure out how to run with it.

Note: This is evil, but they have brought it on themselves. The network administrators have already done one of the most stupid things that they are capable of doing, in order to force you to do all of their legwork for them. You are simply doing what they've asked, and will be presenting them with the most awful choice possible, but one that they ought to know is coming because there isn't any alternative.

-PatP|||Sorry I haven't been back for a few days..

I really don't want to do anything to create any friction with them. So far they've been fairly cooperative in allowing an outside consultant (me) to do development work for a department that's under their jurisdiction. They could easily send one email to upper management that would a) make my primary client's life miserable and b) completely cut me out of any work for them in the future.

After talking with one of their network techs yesterday, the server is up & running. It's 2005, running on a Windows Server 2003 Virtual Machine. She's going to be there, so hopefully she can take care of any network issues that arise. From what she said yesterday, they don't have any internal firewalls, so that should simplify things.

I'm going over there in a few hours to establish my login account, create a test database, and verify connectivity between it and an Access installation on an end user's machine.

Any final words of wisdom?

Network I/O error in SQL 2000 with SP4 ?

Can anyone explain this NETWORK I/O error I received using SP4, SQL 2K.
"spid85 Process ID 90 killed by hostname tester, host process ID 23328"It would seem that a user by the name of "tester" issued a KILL command for
your connection. Virtual homicide? Nah... Look up KILL in Books Online.
ML
http://milambda.blogspot.com/sql

Network I/O error in SQL 2000 ?

SQL 2000 with SP4 what causes a network I/O error which kept the data from
reaching the workstations?Hi
It is unlikely that this is a specific SP4 issue. You don't say whether this
is an intermitent or constant problem or exacly which error number and
message you are getting. You also don't say if this is happening on all
workstations and or the server.
So things to try: check the protocols that being used on server and client,
check for firewalls/virus checkers stopping the port/pipe, make sure that you
can ping/telnet the server, check the name is resolved correctly, check
timeouts...
John
"DGreg" wrote:
> SQL 2000 with SP4 what causes a network I/O error which kept the data from
> reaching the workstations?
>|||John
The error is related to the wait time and wait request on sql2000.
"John Bell" wrote:
> Hi
> It is unlikely that this is a specific SP4 issue. You don't say whether this
> is an intermitent or constant problem or exacly which error number and
> message you are getting. You also don't say if this is happening on all
> workstations and or the server.
> So things to try: check the protocols that being used on server and client,
> check for firewalls/virus checkers stopping the port/pipe, make sure that you
> can ping/telnet the server, check the name is resolved correctly, check
> timeouts...
> John
> "DGreg" wrote:
> > SQL 2000 with SP4 what causes a network I/O error which kept the data from
> > reaching the workstations?
> >|||Hi
Are you refering to DBCC SQLPERF? Changes were made regarding some of the
reporting such as latch waits but I don't know of anything that changed with
network I/O
John
"DGreg" wrote:
> John
> The error is related to the wait time and wait request on sql2000.
> "John Bell" wrote:
> > Hi
> >
> > It is unlikely that this is a specific SP4 issue. You don't say whether this
> > is an intermitent or constant problem or exacly which error number and
> > message you are getting. You also don't say if this is happening on all
> > workstations and or the server.
> >
> > So things to try: check the protocols that being used on server and client,
> > check for firewalls/virus checkers stopping the port/pipe, make sure that you
> > can ping/telnet the server, check the name is resolved correctly, check
> > timeouts...
> >
> > John
> >
> > "DGreg" wrote:
> >
> > > SQL 2000 with SP4 what causes a network I/O error which kept the data from
> > > reaching the workstations?
> > >|||It relates to spid85 where I saw the network I/O ERROR.
"John Bell" wrote:
> Hi
> Are you refering to DBCC SQLPERF? Changes were made regarding some of the
> reporting such as latch waits but I don't know of anything that changed with
> network I/O
> John
> "DGreg" wrote:
> > John
> >
> > The error is related to the wait time and wait request on sql2000.
> >
> > "John Bell" wrote:
> >
> > > Hi
> > >
> > > It is unlikely that this is a specific SP4 issue. You don't say whether this
> > > is an intermitent or constant problem or exacly which error number and
> > > message you are getting. You also don't say if this is happening on all
> > > workstations and or the server.
> > >
> > > So things to try: check the protocols that being used on server and client,
> > > check for firewalls/virus checkers stopping the port/pipe, make sure that you
> > > can ping/telnet the server, check the name is resolved correctly, check
> > > timeouts...
> > >
> > > John
> > >
> > > "DGreg" wrote:
> > >
> > > > SQL 2000 with SP4 what causes a network I/O error which kept the data from
> > > > reaching the workstations?
> > > >|||Hi
This will be a user connection, you may want to check the machine that is
was trying to connect.
John
"DGreg" wrote:
> It relates to spid85 where I saw the network I/O ERROR.
>
> "John Bell" wrote:
> > Hi
> >
> > Are you refering to DBCC SQLPERF? Changes were made regarding some of the
> > reporting such as latch waits but I don't know of anything that changed with
> > network I/O
> >
> > John
> >
> > "DGreg" wrote:
> >
> > > John
> > >
> > > The error is related to the wait time and wait request on sql2000.
> > >
> > > "John Bell" wrote:
> > >
> > > > Hi
> > > >
> > > > It is unlikely that this is a specific SP4 issue. You don't say whether this
> > > > is an intermitent or constant problem or exacly which error number and
> > > > message you are getting. You also don't say if this is happening on all
> > > > workstations and or the server.
> > > >
> > > > So things to try: check the protocols that being used on server and client,
> > > > check for firewalls/virus checkers stopping the port/pipe, make sure that you
> > > > can ping/telnet the server, check the name is resolved correctly, check
> > > > timeouts...
> > > >
> > > > John
> > > >
> > > > "DGreg" wrote:
> > > >
> > > > > SQL 2000 with SP4 what causes a network I/O error which kept the data from
> > > > > reaching the workstations?
> > > > >|||Thanks John for the responses back, I'll have to look deeper into this.
Greg
"John Bell" wrote:
> Hi
> This will be a user connection, you may want to check the machine that is
> was trying to connect.
> John
> "DGreg" wrote:
> > It relates to spid85 where I saw the network I/O ERROR.
> >
> >
> > "John Bell" wrote:
> >
> > > Hi
> > >
> > > Are you refering to DBCC SQLPERF? Changes were made regarding some of the
> > > reporting such as latch waits but I don't know of anything that changed with
> > > network I/O
> > >
> > > John
> > >
> > > "DGreg" wrote:
> > >
> > > > John
> > > >
> > > > The error is related to the wait time and wait request on sql2000.
> > > >
> > > > "John Bell" wrote:
> > > >
> > > > > Hi
> > > > >
> > > > > It is unlikely that this is a specific SP4 issue. You don't say whether this
> > > > > is an intermitent or constant problem or exacly which error number and
> > > > > message you are getting. You also don't say if this is happening on all
> > > > > workstations and or the server.
> > > > >
> > > > > So things to try: check the protocols that being used on server and client,
> > > > > check for firewalls/virus checkers stopping the port/pipe, make sure that you
> > > > > can ping/telnet the server, check the name is resolved correctly, check
> > > > > timeouts...
> > > > >
> > > > > John
> > > > >
> > > > > "DGreg" wrote:
> > > > >
> > > > > > SQL 2000 with SP4 what causes a network I/O error which kept the data from
> > > > > > reaching the workstations?
> > > > > >|||John,
What I'm experiencing is locked transactions. Intermittently, we experience
a transaction/process which will not complete. The process info display in
enterprise manager displays a "Wait Type" of Network I/O. Although, we do
expect to receive this type of message from time to time because of the
application not responding in a timely fashion, network collision, etc., the
process wait will usually either finish or remove itself from the list. The
problem comes forward when the "waiting" process never quits or otherwise
removes itself after any period of time (wait time continues to grow). This
results in subsequent transactions/processes waiting on this particular
error. Consequently, we experience a system wide data outage on the table
with the lock on it as no other processes can access it. We were under the
impression that this type of "latch" or "hang" was corrected in SP4, but
since it's raised it's head again with SP4 applied to the SQL instance, we
are worried about potential outages in the future. Please let me know if we
have any work arounds for these type of process "latches".
Sincerely,
DGreg
"DGreg" wrote:
> Thanks John for the responses back, I'll have to look deeper into this.
> Greg
>
> "John Bell" wrote:
> > Hi
> >
> > This will be a user connection, you may want to check the machine that is
> > was trying to connect.
> >
> > John
> >
> > "DGreg" wrote:
> >
> > > It relates to spid85 where I saw the network I/O ERROR.
> > >
> > >
> > > "John Bell" wrote:
> > >
> > > > Hi
> > > >
> > > > Are you refering to DBCC SQLPERF? Changes were made regarding some of the
> > > > reporting such as latch waits but I don't know of anything that changed with
> > > > network I/O
> > > >
> > > > John
> > > >
> > > > "DGreg" wrote:
> > > >
> > > > > John
> > > > >
> > > > > The error is related to the wait time and wait request on sql2000.
> > > > >
> > > > > "John Bell" wrote:
> > > > >
> > > > > > Hi
> > > > > >
> > > > > > It is unlikely that this is a specific SP4 issue. You don't say whether this
> > > > > > is an intermitent or constant problem or exacly which error number and
> > > > > > message you are getting. You also don't say if this is happening on all
> > > > > > workstations and or the server.
> > > > > >
> > > > > > So things to try: check the protocols that being used on server and client,
> > > > > > check for firewalls/virus checkers stopping the port/pipe, make sure that you
> > > > > > can ping/telnet the server, check the name is resolved correctly, check
> > > > > > timeouts...
> > > > > >
> > > > > > John
> > > > > >
> > > > > > "DGreg" wrote:
> > > > > >
> > > > > > > SQL 2000 with SP4 what causes a network I/O error which kept the data from
> > > > > > > reaching the workstations?
> > > > > > >|||Hi
It is my understanding that SP4 improved the reporting of such problems
rather than curing them see http://support.microsoft.com/kb/906344 although I
believe that it is more to do with accessing data pages
http://support.microsoft.com/kb/822101/. Assuming that your lastwaittype is
NETWORKIO then you are waiting on the client to process your data. You may
want to look at what is happening on the client such as the specification of
the machine, also you may want to check if you are returning unnecessary
information such as result sets that are too wide, or procedures that should
be consolidated into one. Check out the scope of your transactions to see if
they can be made shorter and if there are unnecessary transactions, tuning
long running queries will also help. You also mentioned that you are seeing
network collissions, therefore this should be addressed.
John
"DGreg" wrote:
> John,
> What I'm experiencing is locked transactions. Intermittently, we experience
> a transaction/process which will not complete. The process info display in
> enterprise manager displays a "Wait Type" of Network I/O. Although, we do
> expect to receive this type of message from time to time because of the
> application not responding in a timely fashion, network collision, etc., the
> process wait will usually either finish or remove itself from the list. The
> problem comes forward when the "waiting" process never quits or otherwise
> removes itself after any period of time (wait time continues to grow). This
> results in subsequent transactions/processes waiting on this particular
> error. Consequently, we experience a system wide data outage on the table
> with the lock on it as no other processes can access it. We were under the
> impression that this type of "latch" or "hang" was corrected in SP4, but
> since it's raised it's head again with SP4 applied to the SQL instance, we
> are worried about potential outages in the future. Please let me know if we
> have any work arounds for these type of process "latches".
> Sincerely,
> DGreg
> "DGreg" wrote:
> > Thanks John for the responses back, I'll have to look deeper into this.
> >
> > Greg
> >
> >
> > "John Bell" wrote:
> >
> > > Hi
> > >
> > > This will be a user connection, you may want to check the machine that is
> > > was trying to connect.
> > >
> > > John
> > >
> > > "DGreg" wrote:
> > >
> > > > It relates to spid85 where I saw the network I/O ERROR.
> > > >
> > > >
> > > > "John Bell" wrote:
> > > >
> > > > > Hi
> > > > >
> > > > > Are you refering to DBCC SQLPERF? Changes were made regarding some of the
> > > > > reporting such as latch waits but I don't know of anything that changed with
> > > > > network I/O
> > > > >
> > > > > John
> > > > >
> > > > > "DGreg" wrote:
> > > > >
> > > > > > John
> > > > > >
> > > > > > The error is related to the wait time and wait request on sql2000.
> > > > > >
> > > > > > "John Bell" wrote:
> > > > > >
> > > > > > > Hi
> > > > > > >
> > > > > > > It is unlikely that this is a specific SP4 issue. You don't say whether this
> > > > > > > is an intermitent or constant problem or exacly which error number and
> > > > > > > message you are getting. You also don't say if this is happening on all
> > > > > > > workstations and or the server.
> > > > > > >
> > > > > > > So things to try: check the protocols that being used on server and client,
> > > > > > > check for firewalls/virus checkers stopping the port/pipe, make sure that you
> > > > > > > can ping/telnet the server, check the name is resolved correctly, check
> > > > > > > timeouts...
> > > > > > >
> > > > > > > John
> > > > > > >
> > > > > > > "DGreg" wrote:
> > > > > > >
> > > > > > > > SQL 2000 with SP4 what causes a network I/O error which kept the data from
> > > > > > > > reaching the workstations?
> > > > > > > >

Network I/O error in SQL 2000 ?

SQL 2000 with SP4 what causes a network I/O error which kept the data from
reaching the workstations?Hi
It is unlikely that this is a specific SP4 issue. You don't say whether this
is an intermitent or constant problem or exacly which error number and
message you are getting. You also don't say if this is happening on all
workstations and or the server.
So things to try: check the protocols that being used on server and client,
check for firewalls/virus checkers stopping the port/pipe, make sure that yo
u
can ping/telnet the server, check the name is resolved correctly, check
timeouts...
John
"DGreg" wrote:

> SQL 2000 with SP4 what causes a network I/O error which kept the data from
> reaching the workstations?
>|||John
The error is related to the wait time and wait request on sql2000.
"John Bell" wrote:
[vbcol=seagreen]
> Hi
> It is unlikely that this is a specific SP4 issue. You don't say whether th
is
> is an intermitent or constant problem or exacly which error number and
> message you are getting. You also don't say if this is happening on all
> workstations and or the server.
> So things to try: check the protocols that being used on server and client
,
> check for firewalls/virus checkers stopping the port/pipe, make sure that
you
> can ping/telnet the server, check the name is resolved correctly, check
> timeouts...
> John
> "DGreg" wrote:
>|||Hi
Are you refering to DBCC SQLPERF? Changes were made regarding some of the
reporting such as latch waits but I don't know of anything that changed with
network I/O
John
"DGreg" wrote:
[vbcol=seagreen]
> John
> The error is related to the wait time and wait request on sql2000.
> "John Bell" wrote:
>

Network Error...

Hi All,
I have a windows 2003 server and MS SQL Server 2000 Enterprise edtion
installed in it... From past few days I am the schedule jobs are getting
failed... its giving below error...
[Microsoft][ODBC SQL Server Driver][Named Pipes]ConnectionRead
(WrapperRead()).
Server: Msg 11, Level 16, State 1, Line 0
General network error. Check your network documentation.
Plz advice how to get rid of this...
Thanks in advance.
-Mohit.Refer this KB Article. This talks about similar error message when restoring
database.
http://support.microsoft.com/default.aspx?scid=kb;en-us;827452
It looks like it is MDAC bug and work around is change the SQL Server to use
TCP/IP
Ravi
"Mohit" wrote:
> Hi All,
> I have a windows 2003 server and MS SQL Server 2000 Enterprise edtion
> installed in it... From past few days I am the schedule jobs are getting
> failed... its giving below error...
> [Microsoft][ODBC SQL Server Driver][Named Pipes]ConnectionRead
> (WrapperRead()).
> Server: Msg 11, Level 16, State 1, Line 0
> General network error. Check your network documentation.
>
> Plz advice how to get rid of this...
> Thanks in advance.
> -Mohit.
>

Network Error...

Hi All,
I have a windows 2003 server and MS SQL Server 2000 Enterprise edtion
installed in it... From past few days I am the schedule jobs are getting
failed... its giving below error...
[Microsoft][ODBC SQL Server Driver][Named Pipes]ConnectionRead
(WrapperRead()).
Server: Msg 11, Level 16, State 1, Line 0
General network error. Check your network documentation.
Plz advice how to get rid of this...
Thanks in advance.
-Mohit.
Refer this KB Article. This talks about similar error message when restoring
database.
http://support.microsoft.com/default...b;en-us;827452
It looks like it is MDAC bug and work around is change the SQL Server to use
TCP/IP
Ravi
"Mohit" wrote:

> Hi All,
> I have a windows 2003 server and MS SQL Server 2000 Enterprise edtion
> installed in it... From past few days I am the schedule jobs are getting
> failed... its giving below error...
> [Microsoft][ODBC SQL Server Driver][Named Pipes]ConnectionRead
> (WrapperRead()).
> Server: Msg 11, Level 16, State 1, Line 0
> General network error. Check your network documentation.
>
> Plz advice how to get rid of this...
> Thanks in advance.
> -Mohit.
>

Network Error...

Hi All,
I have a windows 2003 server and MS SQL Server 2000 Enterprise edtion
installed in it... From past few days I am the schedule jobs are getting
failed... its giving below error...
[Microsoft][ODBC SQL Server Driver][Named Pipes]ConnectionRead
(WrapperRead()).
Server: Msg 11, Level 16, State 1, Line 0
General network error. Check your network documentation.
Plz advice how to get rid of this...
Thanks in advance.
-Mohit.Refer this KB Article. This talks about similar error message when restoring
database.
http://support.microsoft.com/defaul...kb;en-us;827452
It looks like it is MDAC bug and work around is change the SQL Server to use
TCP/IP
Ravi
"Mohit" wrote:

> Hi All,
> I have a windows 2003 server and MS SQL Server 2000 Enterprise edtion
> installed in it... From past few days I am the schedule jobs are getting
> failed... its giving below error...
> [Microsoft][ODBC SQL Server Driver][Named Pipes]ConnectionRea
d
> (WrapperRead()).
> Server: Msg 11, Level 16, State 1, Line 0
> General network error. Check your network documentation.
>
> Plz advice how to get rid of this...
> Thanks in advance.
> -Mohit.
>sql

Network error.

Hi,
I am facing a weird network problem. I am running a SQL 2000 SP2
enterprise edition over a Windows 2003 enterprise edition machine.
I am getting the network error messages (see below) while trying to
connect to the server. However if i am connected to the server before
the problem occurs i can continue running queries from the query
analyzer but cannot use the object browser to view the tables/ views
etc.
The problem is temporarily fixed if i restart the sql server service
but reappears after some times.
Seems to me it is is not a network problem otherwise the connection
would have broken.
Error 1:
[ODBC SQL Server Driver][DBNETLIB]General network error. Check your
network documentation.
Error 2:
[ODBC SQL Server Driver][DBNETLIB]ConnectionRead (recv()).
Any idea why this is happening?
Thanks in advance
Taw.
Consider applying SP4, or at least SP3a, to your SQL 2000 instance.
Hope this helps.
Dan Guzman
SQL Server MVP
"Taw" <tawfiq.choudhury@.grameenphone.com> wrote in message
news:1185800793.766706.9030@.l70g2000hse.googlegrou ps.com...
> Hi,
> I am facing a weird network problem. I am running a SQL 2000 SP2
> enterprise edition over a Windows 2003 enterprise edition machine.
> I am getting the network error messages (see below) while trying to
> connect to the server. However if i am connected to the server before
> the problem occurs i can continue running queries from the query
> analyzer but cannot use the object browser to view the tables/ views
> etc.
> The problem is temporarily fixed if i restart the sql server service
> but reappears after some times.
> Seems to me it is is not a network problem otherwise the connection
> would have broken.
> Error 1:
> [ODBC SQL Server Driver][DBNETLIB]General network error. Check your
> network documentation.
> Error 2:
> [ODBC SQL Server Driver][DBNETLIB]ConnectionRead (recv()).
> Any idea why this is happening?
> Thanks in advance
> Taw.
>

Network error.

Hi,
I am facing a weird network problem. I am running a SQL 2000 SP2
enterprise edition over a Windows 2003 enterprise edition machine.
I am getting the network error messages (see below) while trying to
connect to the server. However if i am connected to the server before
the problem occurs i can continue running queries from the query
analyzer but cannot use the object browser to view the tables/ views
etc.
The problem is temporarily fixed if i restart the sql server service
but reappears after some times.
Seems to me it is is not a network problem otherwise the connection
would have broken.
Error 1:
[ODBC SQL Server Driver][DBNETLIB]General network error. Check your
network documentation.
Error 2:
[ODBC SQL Server Driver][DBNETLIB]ConnectionRead (recv()).
Any idea why this is happening?
Thanks in advance
Taw.Consider applying SP4, or at least SP3a, to your SQL 2000 instance.
Hope this helps.
Dan Guzman
SQL Server MVP
"Taw" <tawfiq.choudhury@.grameenphone.com> wrote in message
news:1185800793.766706.9030@.l70g2000hse.googlegroups.com...
> Hi,
> I am facing a weird network problem. I am running a SQL 2000 SP2
> enterprise edition over a Windows 2003 enterprise edition machine.
> I am getting the network error messages (see below) while trying to
> connect to the server. However if i am connected to the server before
> the problem occurs i can continue running queries from the query
> analyzer but cannot use the object browser to view the tables/ views
> etc.
> The problem is temporarily fixed if i restart the sql server service
> but reappears after some times.
> Seems to me it is is not a network problem otherwise the connection
> would have broken.
> Error 1:
> [ODBC SQL Server Driver][DBNETLIB]General network error. Check you
r
> network documentation.
> Error 2:
> [ODBC SQL Server Driver][DBNETLIB]ConnectionRead (recv()).
> Any idea why this is happening?
> Thanks in advance
> Taw.
>

Network error.

Hi,
I am facing a weird network problem. I am running a SQL 2000 SP2
enterprise edition over a Windows 2003 enterprise edition machine.
I am getting the network error messages (see below) while trying to
connect to the server. However if i am connected to the server before
the problem occurs i can continue running queries from the query
analyzer but cannot use the object browser to view the tables/ views
etc.
The problem is temporarily fixed if i restart the sql server service
but reappears after some times.
Seems to me it is is not a network problem otherwise the connection
would have broken.
Error 1:
[ODBC SQL Server Driver][DBNETLIB]General network error. Check your
network documentation.
Error 2:
[ODBC SQL Server Driver][DBNETLIB]ConnectionRead (recv()).
Any idea why this is happening?
Thanks in advance
Taw.Consider applying SP4, or at least SP3a, to your SQL 2000 instance.
--
Hope this helps.
Dan Guzman
SQL Server MVP
"Taw" <tawfiq.choudhury@.grameenphone.com> wrote in message
news:1185800793.766706.9030@.l70g2000hse.googlegroups.com...
> Hi,
> I am facing a weird network problem. I am running a SQL 2000 SP2
> enterprise edition over a Windows 2003 enterprise edition machine.
> I am getting the network error messages (see below) while trying to
> connect to the server. However if i am connected to the server before
> the problem occurs i can continue running queries from the query
> analyzer but cannot use the object browser to view the tables/ views
> etc.
> The problem is temporarily fixed if i restart the sql server service
> but reappears after some times.
> Seems to me it is is not a network problem otherwise the connection
> would have broken.
> Error 1:
> [ODBC SQL Server Driver][DBNETLIB]General network error. Check your
> network documentation.
> Error 2:
> [ODBC SQL Server Driver][DBNETLIB]ConnectionRead (recv()).
> Any idea why this is happening?
> Thanks in advance
> Taw.
>

Network error while connecting to the Database through sql server 2005

Hi
I have this error

[DBNETLIB] [ConnectionOpen(PreloginHandshake()].]General Network error. Check your network documentation.

while connecting to the database through sql server 2005. How to solve this problem. Plz help me. plz give me the solution A.S.A.P.Check this out:

http://www.eggheadcafe.com/aspnet_answers/SQLServerprogramming/Mar2006/post26535127.asp

Guy had to reinstall server to make it work.|||Read this as well:

http://support.microsoft.com/kb/311111

Network error while backup

We get an error when we are trying to run a backup of the SQL db here, we just got a new ISP to this company and al the routers and the like has been reconfigured (if that might be the problem). Would apreciate a speedy help with this one.
Here is the error message we get

un OnStart: DTSStep_DTSExecuteSQLTask_2 DTSRun OnError: DTSStep_DTSExecuteSQLTask_2, Error = -2147467259 (80004005) Error string: [DBNETLIB][ConnectionRead (recv()).]General network error. Check your network documentation. Error source: Microsoft OLE DB Provider for SQL Server Help file: Help context: 0 Error Detail Records: Error: -2147467259 (80004005); Provider Error: 11 (B) Error string: [DBNETLIB][ConnectionRead (recv()).]General network error. Check your network documentation. Error source: Microsoft OLE DB Provider for SQL Server Help file: Help context: 0 DTSRun OnFinish: DTSStep_DTSExecuteSQLTask_2 DTSRun OnStart: DTSStep_DTSExecuteSQLTask_1 DTSRun OnError: DTSStep_DTSExecuteSQLTask_1, Error = -2147467259 (80004005) Error string: Connection failure Error source: Microsoft OLE DB Provider for SQL Server Help file: Help conte... Process Exit Code 1. The step failed.Why you're using DTS to take backup, the best option would be to perform a local backup of database on the server and use FTP or other file transfer options to transfer the file.

The potential causes of general network would be:
- any issues with network routers, hubs involved.
- check event viewer for any network issues
- SQL Server is not listening on the protocol or port that you are using to connect. The Server Network Utility on the server determines which protocols SQL Server will use and on which TCP/IP ports SQL Server will listen.
- The Client Network Utility, an MDAC data source name (DSN), or your connection string determines which protocol and port your client uses when it connects.|||Thansk for the help i will look in to this :)|||What are the privileges held for MSSQLSErver & SQLAgent service account?|||Admin and connecting using Remote Desktop thru a TS server|||How about privileges on the desktop/remote server for these accounts?|||full acces for the admin
they got all the neccesary priveliges
the error ocuurd after the change of ISP it has worked fine before that so we are thinking it might be routing or something like that but we are not sure.|||Thats better, then dig out from other end/|||hehe :) we have looked in to that but we cant find anything wrong with it at the moment :) thats why i posted it here to get some feedback what it might be so thanks for the help m8|||Any firewall involved or any new tools installed recently at ISP and your end?

In order to determine whether this "general network error" is a
Net-Library, a Network Protocol, or a name resolution problem, there are a few troubleshooting steps that should be tried.

Take help from this KBA http://support.microsoft.com/default.aspx?scid=http://support.microsoft.com:80/support/kb/articles/q169/7/90.asp&NoWebContent=1 to troubleshoot if TCP/IP is defaulted.

Best option to talk to ISP techies for useful information.|||yea we will do that i do also think they have done some configuring here that our network and SQL server didnt like.
If we dont solve this our self they will have e great weekend fixing this shit here :)

thanks again|||Only this backup job fails or a simple DTS also fails which involves file copy.

ALso try to OS level to copy the files.|||Will do that... looks like it will be work for me this weekend to :(
But i dont think there is anything wrong with the filecopying i think it is when it tries to resolve all the backup locations in the network here but as i said i will try everthing that might help :)sql

Network error when running a query

Running long queries (mostly DBCC commands) on SQL Server 2000 SP3 I receive
an error very often
"[Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionRead (WrapperRead())
Server: Msg 11, Level 16, State 1, Line 0
General network error. Check your network documentation."
How can I fix it?Hi,
Do you have SQL Server on Windows 2003?
If you do, try removing Named Pipes from Enabled Network Libraries in Server
Network Utility.
--
Danijel Novak
"Elena" <Elena@.discussions.microsoft.com> wrote in message
news:07702D19-01BA-4A62-9F1B-CC758C1C4460@.microsoft.com...
> Running long queries (mostly DBCC commands) on SQL Server 2000 SP3 I
> receive
> an error very often
> "[Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionRead
> (WrapperRead())
> Server: Msg 11, Level 16, State 1, Line 0
> General network error. Check your network documentation."
> How can I fix it?
>|||Thanks for reply, Danijel. Yes, SQL Server 2000 is running on Windows Server
2003 machine. But how will removing Named Piies influence application
performance? Do I need to stop and restart production server after
reconfiguration?
Elena
"Danijel Novak" wrote:
> Hi,
> Do you have SQL Server on Windows 2003?
> If you do, try removing Named Pipes from Enabled Network Libraries in Server
> Network Utility.
> --
> Danijel Novak
>
> "Elena" <Elena@.discussions.microsoft.com> wrote in message
> news:07702D19-01BA-4A62-9F1B-CC758C1C4460@.microsoft.com...
> > Running long queries (mostly DBCC commands) on SQL Server 2000 SP3 I
> > receive
> > an error very often
> > "[Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionRead
> > (WrapperRead())
> > Server: Msg 11, Level 16, State 1, Line 0
> > General network error. Check your network documentation."
> > How can I fix it?
> >
>
>|||Hi,
removing Named Pipes should not influence application performance. Just keep
TCP/IP in there.
I'm not sure about restarting the service but I think you don't have to
restart SQL Server for that.
--
Danijel Novak
"Elena" <Elena@.discussions.microsoft.com> wrote in message
news:0CD3D9ED-DA33-4D7B-BDD3-C3C486158A68@.microsoft.com...
> Thanks for reply, Danijel. Yes, SQL Server 2000 is running on Windows
> Server
> 2003 machine. But how will removing Named Piies influence application
> performance? Do I need to stop and restart production server after
> reconfiguration?
> Elena
> "Danijel Novak" wrote:
>> Hi,
>> Do you have SQL Server on Windows 2003?
>> If you do, try removing Named Pipes from Enabled Network Libraries in
>> Server
>> Network Utility.
>> --
>> Danijel Novak
>>
>> "Elena" <Elena@.discussions.microsoft.com> wrote in message
>> news:07702D19-01BA-4A62-9F1B-CC758C1C4460@.microsoft.com...
>> > Running long queries (mostly DBCC commands) on SQL Server 2000 SP3 I
>> > receive
>> > an error very often
>> > "[Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionRead
>> > (WrapperRead())
>> > Server: Msg 11, Level 16, State 1, Line 0
>> > General network error. Check your network documentation."
>> > How can I fix it?
>> >
>>

Network error when running a query

Running long queries (mostly DBCC commands) on SQL Server 2000 SP3 I receive
an error very often
"[Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionRead (WrapperRead())
Server: Msg 11, Level 16, State 1, Line 0
General network error. Check your network documentation."
How can I fix it?
Hi,
Do you have SQL Server on Windows 2003?
If you do, try removing Named Pipes from Enabled Network Libraries in Server
Network Utility.
Danijel Novak
"Elena" <Elena@.discussions.microsoft.com> wrote in message
news:07702D19-01BA-4A62-9F1B-CC758C1C4460@.microsoft.com...
> Running long queries (mostly DBCC commands) on SQL Server 2000 SP3 I
> receive
> an error very often
> "[Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionRead
> (WrapperRead())
> Server: Msg 11, Level 16, State 1, Line 0
> General network error. Check your network documentation."
> How can I fix it?
>
|||Thanks for reply, Danijel. Yes, SQL Server 2000 is running on Windows Server
2003 machine. But how will removing Named Piies influence application
performance? Do I need to stop and restart production server after
reconfiguration?
Elena
"Danijel Novak" wrote:

> Hi,
> Do you have SQL Server on Windows 2003?
> If you do, try removing Named Pipes from Enabled Network Libraries in Server
> Network Utility.
> --
> Danijel Novak
>
> "Elena" <Elena@.discussions.microsoft.com> wrote in message
> news:07702D19-01BA-4A62-9F1B-CC758C1C4460@.microsoft.com...
>
>
|||Hi,
removing Named Pipes should not influence application performance. Just keep
TCP/IP in there.
I'm not sure about restarting the service but I think you don't have to
restart SQL Server for that.
Danijel Novak
"Elena" <Elena@.discussions.microsoft.com> wrote in message
news:0CD3D9ED-DA33-4D7B-BDD3-C3C486158A68@.microsoft.com...[vbcol=seagreen]
> Thanks for reply, Danijel. Yes, SQL Server 2000 is running on Windows
> Server
> 2003 machine. But how will removing Named Piies influence application
> performance? Do I need to stop and restart production server after
> reconfiguration?
> Elena
> "Danijel Novak" wrote:

Network error when running a query

Running long queries (mostly DBCC commands) on SQL Server 2000 SP3 I receive
an error very often
"[Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionRead (Wr
apperRead())
Server: Msg 11, Level 16, State 1, Line 0
General network error. Check your network documentation."
How can I fix it?Hi,
Do you have SQL Server on Windows 2003?
If you do, try removing Named Pipes from Enabled Network Libraries in Server
Network Utility.
Danijel Novak
"Elena" <Elena@.discussions.microsoft.com> wrote in message
news:07702D19-01BA-4A62-9F1B-CC758C1C4460@.microsoft.com...
> Running long queries (mostly DBCC commands) on SQL Server 2000 SP3 I
> receive
> an error very often
> "[Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionRead
> (WrapperRead())
> Server: Msg 11, Level 16, State 1, Line 0
> General network error. Check your network documentation."
> How can I fix it?
>|||Thanks for reply, Danijel. Yes, SQL Server 2000 is running on Windows Server
2003 machine. But how will removing Named Piies influence application
performance? Do I need to stop and restart production server after
reconfiguration?
Elena
"Danijel Novak" wrote:

> Hi,
> Do you have SQL Server on Windows 2003?
> If you do, try removing Named Pipes from Enabled Network Libraries in Serv
er
> Network Utility.
> --
> Danijel Novak
>
> "Elena" <Elena@.discussions.microsoft.com> wrote in message
> news:07702D19-01BA-4A62-9F1B-CC758C1C4460@.microsoft.com...
>
>|||Hi,
removing Named Pipes should not influence application performance. Just keep
TCP/IP in there.
I'm not sure about restarting the service but I think you don't have to
restart SQL Server for that.
Danijel Novak
"Elena" <Elena@.discussions.microsoft.com> wrote in message
news:0CD3D9ED-DA33-4D7B-BDD3-C3C486158A68@.microsoft.com...[vbcol=seagreen]
> Thanks for reply, Danijel. Yes, SQL Server 2000 is running on Windows
> Server
> 2003 machine. But how will removing Named Piies influence application
> performance? Do I need to stop and restart production server after
> reconfiguration?
> Elena
> "Danijel Novak" wrote:
>

Network Error (dns_unresolved_hostname

Dear Sir,

This is commanly i am facing the problem Network Error (dns_unresolved_hostname

How to solve this problem pls advise me.

my mail id : meshaikgous@.hotmail.com

meshaikgous@.yahoo.com

I am awaiting for u r reply asap.

Thank u very much.

yours faithfullly

Shaik. Gousoddin

Normally, such issue is a network configuration issue. You need to contact your network admin ( provider) in order to solve such issue. You can provide result of the following commands to them "ping servername" and "ping -a serveripaddress".

|||

Hi are you using Apache server?

Network Error (dns_unresolved_hostname

Dear Sir,

This is commanly i am facing the problem Network Error (dns_unresolved_hostname

How to solve this problem pls advise me.

my mail id : meshaikgous@.hotmail.com

meshaikgous@.yahoo.com

I am awaiting for u r reply asap.

Thank u very much.

yours faithfullly

Shaik. Gousoddin

Normally, such issue is a network configuration issue. You need to contact your network admin ( provider) in order to solve such issue. You can provide result of the following commands to them "ping servername" and "ping -a serveripaddress".

|||

Hi are you using Apache server?

sql

Network error

When I unplug my server from the network, I lose connection to SQL Server. I
don't understand why it is happening. All my applications have to be closed
and reopened to talk to the database again. Can anyone please let me know wh
y
this is happening?
I am using SQL Server 2005 SP1 and Windows Server 2003.
Any help is appreciated.FYI: I am connected to the local server and not to a server on the network.
"KMP" wrote:

> When I unplug my server from the network, I lose connection to SQL Server.
I
> don't understand why it is happening. All my applications have to be close
d
> and reopened to talk to the database again. Can anyone please let me know
why
> this is happening?
> I am using SQL Server 2005 SP1 and Windows Server 2003.
> Any help is appreciated.|||Please verify on your sql server what protocol is using if is using tcp/ip a
s
default thats why. also you can create a local host file with the localip or
just 127.0.0.1
Santos Martinez,MCSE, MCDBA, MCTS
IT Community Staff of Puerto Rico
http://www.itcspr.org
"KMP" wrote:
[vbcol=seagreen]
> FYI: I am connected to the local server and not to a server on the network
.
> "KMP" wrote:
>|||Thanks. But I don't understand what you are trying to tell me. Yes, SQL
Server is using TCP/IP. Can you be more specific on the host file thing?
"Santos Martinez" wrote:
[vbcol=seagreen]
> Please verify on your sql server what protocol is using if is using tcp/ip
as
> default thats why. also you can create a local host file with the localip
or
> just 127.0.0.1
>
> --
> Santos Martinez,MCSE, MCDBA, MCTS
> IT Community Staff of Puerto Rico
> http://www.itcspr.org
>
> "KMP" wrote:
>|||KMP wrote:
> Thanks. But I don't understand what you are trying to tell me. Yes, SQL
> Server is using TCP/IP. Can you be more specific on the host file thing?
>
When you connect to a TCP/IP networked computer, you either do it by
specifying the IP address of the machine, or the hostname of the
machine. If you specify the hostname, then your computer will talk to a
DNS or WINS server to find out what IP address that hostname equates to.
If your machine is disconnected from the network, it can't communicate
with a DNS or WINS, and therefore can't figure out that MACHINEX = IP
10.10.10.1, for example. Since you're connecting back to your own
machine, you can avoid this by specifying an IP address of 127.0.0.1, or
a machine name of "localhost" - either one will loop back to your own
machine. Basic networking stuff...
Tracy McKibben
MCDBA
http://www.realsqlguy.com|||So can you please tell me where and how I would be making the changes?
"Tracy McKibben" wrote:

> KMP wrote:
> When you connect to a TCP/IP networked computer, you either do it by
> specifying the IP address of the machine, or the hostname of the
> machine. If you specify the hostname, then your computer will talk to a
> DNS or WINS server to find out what IP address that hostname equates to.
> If your machine is disconnected from the network, it can't communicate
> with a DNS or WINS, and therefore can't figure out that MACHINEX = IP
> 10.10.10.1, for example. Since you're connecting back to your own
> machine, you can avoid this by specifying an IP address of 127.0.0.1, or
> a machine name of "localhost" - either one will loop back to your own
> machine. Basic networking stuff...
>
> --
> Tracy McKibben
> MCDBA
> http://www.realsqlguy.com
>|||Hi, Can someone help me get past this stumbling block? Thanks.
"KMP" wrote:
[vbcol=seagreen]
> So can you please tell me where and how I would be making the changes?
> "Tracy McKibben" wrote:
>|||KMP wrote:
> So can you please tell me where and how I would be making the changes?
>
I'm not sure what you're looking to change. As I stated, if you simply
connect to "127.0.0.1" or "localhost", things should work whether you're
on the network or not. Query Analyzer and/or Management Studio will
prompt you for a server name, use "localhost". In Enterprise Manager,
you'll have to register a new server to represent "localhost".
Tracy McKibben
MCDBA
http://www.realsqlguy.com|||have you try to modify the hosts on %windir%\system32\drivers\etc.
put localhost = 127.0.0.1 or yourmachinename = 127.0.0.1
also have you take a look into the network client network utility and server
network utility.
regards,
Santos Martinez,MCSE, MCDBA, MCTS
IT Community Staff of Puerto Rico
http://www.itcspr.org
"Tracy McKibben" wrote:

> KMP wrote:
> I'm not sure what you're looking to change. As I stated, if you simply
> connect to "127.0.0.1" or "localhost", things should work whether you're
> on the network or not. Query Analyzer and/or Management Studio will
> prompt you for a server name, use "localhost". In Enterprise Manager,
> you'll have to register a new server to represent "localhost".
>
> --
> Tracy McKibben
> MCDBA
> http://www.realsqlguy.com
>

network error

Hi,
Running a stored procedure in query analyser returns data but when running the asp.net page which uses that stored procedure returns an exception which is:
General network error. Check your network documentation

Do you know what the problem could be please?
ThanksNetwork errors are your SQL Server is installed with the local systems account which leaves SQL Server Agent without Network permissions. The solution you have to install SQL Server with a service account. Hope this helps.

Kind regards,
Gift Peddie|||Hi,
Are you sure this is the solution?
It's just that the query works for some and not for all of the queries that are passed through the network.
Thanks|||Installing SQL Server with a service account is good practice in all but free standing developer boxes because after SQL Server Service, SQL Server Agent is the next most important service in SQL Server. Some distributed queries will fail and you cannot run Replication because the Local Systems account leaves SQL Server Agent without Network permissions. Hope this helps.

Kind regards,
Gift Peddie

network error

Hello,
I get the following error:
Server: Msg 11, Level 16, State 1, Line 1
General network error. Check your network documentation.
Need help.
I have 2 sql server instances on two different machines.
Created a linked serve between SERVE1 and SERVER2.
Tried to run a select query using four-part-naming-convention from server1
to get the query results.
From Server1 ran the following query:
select * from servername2.datbasename.owner.tablename
got the following error message:
Server: Msg 11, Level 16, State 1, Line 1
General network error. Check your network documentation.
Need help to resolve this issue.
Don
Go into Enterprise Manager and click on the linked server. See if you can
see any of the tables. If not, you haven't got the connection setup
correctly. Take the parameters from the linked table and try to connect
with the same authentication in Query Analyzer. Does that work? I'm
assuming you can ping the other server? Also, if the second server is an
instance, let us know if you have "Hide Server" checked in the server
configuration on that server.
"Dony" <donb@.yahoo.com> wrote in message
news:enTc1PMtEHA.1216@.TK2MSFTNGP10.phx.gbl...
> Hello,
> I get the following error:
> Server: Msg 11, Level 16, State 1, Line 1
> General network error. Check your network documentation.
>
> Need help.
> I have 2 sql server instances on two different machines.
> Created a linked serve between SERVE1 and SERVER2.
> Tried to run a select query using four-part-naming-convention from server1
> to get the query results.
> From Server1 ran the following query:
> select * from servername2.datbasename.owner.tablename
> got the following error message:
> Server: Msg 11, Level 16, State 1, Line 1
> General network error. Check your network documentation.
> Need help to resolve this issue.
> Don
>
>

network error

Hello,
> I get the following error:
> Server: Msg 11, Level 16, State 1, Line 1
> General network error. Check your network documentation.
>
> Need help.
> I have 2 sql server instances on two different machines.
> Created a linked serve between SERVE1 and SERVER2.
> Tried to run a select query using four-part-naming-convention from server1
> to get the query results.
> From Server1 ran the following query:
> select * from servername2.datbasename.owner.tablename
> got the following error message:
> Server: Msg 11, Level 16, State 1, Line 1
> General network error. Check your network documentation.
> Need help to resolve this issue.
> Don
>
>
Hi
Check the destination server for login failures.
See if you can run a system stored procedure like sp_who2 against server2.
Regards
Mike
"Dony" wrote:

> Hello,
>
>
>

Network error

When I unplug my server from the network, I lose connection to SQL Server. I
don't understand why it is happening. All my applications have to be closed
and reopened to talk to the database again. Can anyone please let me know why
this is happening?
I am using SQL Server 2005 SP1 and Windows Server 2003.
Any help is appreciated.FYI: I am connected to the local server and not to a server on the network.
"KMP" wrote:
> When I unplug my server from the network, I lose connection to SQL Server. I
> don't understand why it is happening. All my applications have to be closed
> and reopened to talk to the database again. Can anyone please let me know why
> this is happening?
> I am using SQL Server 2005 SP1 and Windows Server 2003.
> Any help is appreciated.|||Please verify on your sql server what protocol is using if is using tcp/ip as
default thats why. also you can create a local host file with the localip or
just 127.0.0.1
Santos Martinez,MCSE, MCDBA, MCTS
IT Community Staff of Puerto Rico
http://www.itcspr.org
"KMP" wrote:
> FYI: I am connected to the local server and not to a server on the network.
> "KMP" wrote:
> > When I unplug my server from the network, I lose connection to SQL Server. I
> > don't understand why it is happening. All my applications have to be closed
> > and reopened to talk to the database again. Can anyone please let me know why
> > this is happening?
> >
> > I am using SQL Server 2005 SP1 and Windows Server 2003.
> >
> > Any help is appreciated.|||Thanks. But I don't understand what you are trying to tell me. Yes, SQL
Server is using TCP/IP. Can you be more specific on the host file thing?
"Santos Martinez" wrote:
> Please verify on your sql server what protocol is using if is using tcp/ip as
> default thats why. also you can create a local host file with the localip or
> just 127.0.0.1
>
> --
> Santos Martinez,MCSE, MCDBA, MCTS
> IT Community Staff of Puerto Rico
> http://www.itcspr.org
>
> "KMP" wrote:
> > FYI: I am connected to the local server and not to a server on the network.
> >
> > "KMP" wrote:
> >
> > > When I unplug my server from the network, I lose connection to SQL Server. I
> > > don't understand why it is happening. All my applications have to be closed
> > > and reopened to talk to the database again. Can anyone please let me know why
> > > this is happening?
> > >
> > > I am using SQL Server 2005 SP1 and Windows Server 2003.
> > >
> > > Any help is appreciated.|||KMP wrote:
> Thanks. But I don't understand what you are trying to tell me. Yes, SQL
> Server is using TCP/IP. Can you be more specific on the host file thing?
>
When you connect to a TCP/IP networked computer, you either do it by
specifying the IP address of the machine, or the hostname of the
machine. If you specify the hostname, then your computer will talk to a
DNS or WINS server to find out what IP address that hostname equates to.
If your machine is disconnected from the network, it can't communicate
with a DNS or WINS, and therefore can't figure out that MACHINEX = IP
10.10.10.1, for example. Since you're connecting back to your own
machine, you can avoid this by specifying an IP address of 127.0.0.1, or
a machine name of "localhost" - either one will loop back to your own
machine. Basic networking stuff...
Tracy McKibben
MCDBA
http://www.realsqlguy.com|||So can you please tell me where and how I would be making the changes?
"Tracy McKibben" wrote:
> KMP wrote:
> > Thanks. But I don't understand what you are trying to tell me. Yes, SQL
> > Server is using TCP/IP. Can you be more specific on the host file thing?
> >
> When you connect to a TCP/IP networked computer, you either do it by
> specifying the IP address of the machine, or the hostname of the
> machine. If you specify the hostname, then your computer will talk to a
> DNS or WINS server to find out what IP address that hostname equates to.
> If your machine is disconnected from the network, it can't communicate
> with a DNS or WINS, and therefore can't figure out that MACHINEX = IP
> 10.10.10.1, for example. Since you're connecting back to your own
> machine, you can avoid this by specifying an IP address of 127.0.0.1, or
> a machine name of "localhost" - either one will loop back to your own
> machine. Basic networking stuff...
>
> --
> Tracy McKibben
> MCDBA
> http://www.realsqlguy.com
>|||Hi, Can someone help me get past this stumbling block? Thanks.
"KMP" wrote:
> So can you please tell me where and how I would be making the changes?
> "Tracy McKibben" wrote:
> > KMP wrote:
> > > Thanks. But I don't understand what you are trying to tell me. Yes, SQL
> > > Server is using TCP/IP. Can you be more specific on the host file thing?
> > >
> >
> > When you connect to a TCP/IP networked computer, you either do it by
> > specifying the IP address of the machine, or the hostname of the
> > machine. If you specify the hostname, then your computer will talk to a
> > DNS or WINS server to find out what IP address that hostname equates to.
> > If your machine is disconnected from the network, it can't communicate
> > with a DNS or WINS, and therefore can't figure out that MACHINEX = IP
> > 10.10.10.1, for example. Since you're connecting back to your own
> > machine, you can avoid this by specifying an IP address of 127.0.0.1, or
> > a machine name of "localhost" - either one will loop back to your own
> > machine. Basic networking stuff...
> >
> >
> > --
> > Tracy McKibben
> > MCDBA
> > http://www.realsqlguy.com
> >|||KMP wrote:
> So can you please tell me where and how I would be making the changes?
>
I'm not sure what you're looking to change. As I stated, if you simply
connect to "127.0.0.1" or "localhost", things should work whether you're
on the network or not. Query Analyzer and/or Management Studio will
prompt you for a server name, use "localhost". In Enterprise Manager,
you'll have to register a new server to represent "localhost".
Tracy McKibben
MCDBA
http://www.realsqlguy.com|||have you try to modify the hosts on %windir%\system32\drivers\etc.
put localhost = 127.0.0.1 or yourmachinename = 127.0.0.1
also have you take a look into the network client network utility and server
network utility.
regards,
--
Santos Martinez,MCSE, MCDBA, MCTS
IT Community Staff of Puerto Rico
http://www.itcspr.org
"Tracy McKibben" wrote:
> KMP wrote:
> > So can you please tell me where and how I would be making the changes?
> >
> I'm not sure what you're looking to change. As I stated, if you simply
> connect to "127.0.0.1" or "localhost", things should work whether you're
> on the network or not. Query Analyzer and/or Management Studio will
> prompt you for a server name, use "localhost". In Enterprise Manager,
> you'll have to register a new server to represent "localhost".
>
> --
> Tracy McKibben
> MCDBA
> http://www.realsqlguy.com
>sql

network error

Hello,
> I get the following error:
> Server: Msg 11, Level 16, State 1, Line 1
> General network error. Check your network documentation.
>
> Need help.
> I have 2 sql server instances on two different machines.
> Created a linked serve between SERVE1 and SERVER2.
> Tried to run a select query using four-part-naming-convention from server1
> to get the query results.
> From Server1 ran the following query:
> select * from servername2.datbasename.owner.tablename
> got the following error message:
> Server: Msg 11, Level 16, State 1, Line 1
> General network error. Check your network documentation.
> Need help to resolve this issue.
> Don
>
>Hi
Check the destination server for login failures.
See if you can run a system stored procedure like sp_who2 against server2.
Regards
Mike
"Dony" wrote:

> Hello,
>
>
>

network error

Hello,
I get the following error:
Server: Msg 11, Level 16, State 1, Line 1
General network error. Check your network documentation.
Need help.
I have 2 sql server instances on two different machines.
Created a linked serve between SERVE1 and SERVER2.
Tried to run a select query using four-part-naming-convention from server1
to get the query results.
From Server1 ran the following query:
select * from servername2.datbasename.owner.tablename
got the following error message:
Server: Msg 11, Level 16, State 1, Line 1
General network error. Check your network documentation.
Need help to resolve this issue.
DonGo into Enterprise Manager and click on the linked server. See if you can
see any of the tables. If not, you haven't got the connection setup
correctly. Take the parameters from the linked table and try to connect
with the same authentication in Query Analyzer. Does that work? I'm
assuming you can ping the other server? Also, if the second server is an
instance, let us know if you have "Hide Server" checked in the server
configuration on that server.
"Dony" <donb@.yahoo.com> wrote in message
news:enTc1PMtEHA.1216@.TK2MSFTNGP10.phx.gbl...
> Hello,
> I get the following error:
> Server: Msg 11, Level 16, State 1, Line 1
> General network error. Check your network documentation.
>
> Need help.
> I have 2 sql server instances on two different machines.
> Created a linked serve between SERVE1 and SERVER2.
> Tried to run a select query using four-part-naming-convention from server1
> to get the query results.
> From Server1 ran the following query:
> select * from servername2.datbasename.owner.tablename
> got the following error message:
> Server: Msg 11, Level 16, State 1, Line 1
> General network error. Check your network documentation.
> Need help to resolve this issue.
> Don
>
>

Network drives not available on Database Maintenance

I am trying to establish a Database Maintenance plan for our SQL server and when I choose
Database Maintenance Plan
Complete Backup Tab
Under choose directory when I choose the (...) icon to choose a directory only the C and D drive of the server appears, I do not see the network drives.
I resolved this in the past but forgot how to.
Thanks
Jeffrey
What I used to do in 6.5 was run a scheduled task that had the ID that SQL was running under to map the network drive. I have not had a need to try this in 2k but it is worth a shot.
Jeff
MCDBA, MCSE+I
|||Not too sure if you can do this on Database Maintenance Plans
Put you can create a Backup device pointing to a Network drive and create
backup jobs to that network device(s)
Regards
J
"Jeffrey Sheldon" <jsheldon@.projecthope.org> wrote in message
news:34DCEFE7-6054-44BB-B6E1-BF1AB9F79CDD@.microsoft.com...
> I am trying to establish a Database Maintenance plan for our SQL server
and when I choose
> Database Maintenance Plan
> Complete Backup Tab
> Under choose directory when I choose the (...) icon to choose a directory
only the C and D drive of the server appears, I do not see the network
drives.
> I resolved this in the past but forgot how to.
> Thanks
|||Type in the UNC name of the share. Make sure the SQL server service account
has permissions to that share.
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com
I support the Professional Association for SQL Server
www.sqlpass.org
"Jeffrey Sheldon" <jsheldon@.projecthope.org> wrote in message
news:34DCEFE7-6054-44BB-B6E1-BF1AB9F79CDD@.microsoft.com...
> I am trying to establish a Database Maintenance plan for our SQL server
and when I choose
> Database Maintenance Plan
> Complete Backup Tab
> Under choose directory when I choose the (...) icon to choose a directory
only the C and D drive of the server appears, I do not see the network
drives.
> I resolved this in the past but forgot how to.
> Thanks

Network drives not available on Database Maintenance

I am trying to establish a Database Maintenance plan for our SQL server and
when I choose
Database Maintenance Plan
Complete Backup Tab
Under choose directory when I choose the (...) icon to choose a directory on
ly the C and D drive of the server appears, I do not see the network drives.
I resolved this in the past but forgot how to.
ThanksJeffrey
What I used to do in 6.5 was run a scheduled task that had the ID that SQL w
as running under to map the network drive. I have not had a need to try thi
s in 2k but it is worth a shot.
Jeff
MCDBA, MCSE+I|||Not too sure if you can do this on Database Maintenance Plans
Put you can create a Backup device pointing to a Network drive and create
backup jobs to that network device(s)
Regards
J
"Jeffrey Sheldon" <jsheldon@.projecthope.org> wrote in message
news:34DCEFE7-6054-44BB-B6E1-BF1AB9F79CDD@.microsoft.com...
> I am trying to establish a Database Maintenance plan for our SQL server
and when I choose
> Database Maintenance Plan
> Complete Backup Tab
> Under choose directory when I choose the (...) icon to choose a directory
only the C and D drive of the server appears, I do not see the network
drives.
> I resolved this in the past but forgot how to.
> Thanks|||Type in the UNC name of the share. Make sure the SQL server service account
has permissions to that share.
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com
I support the Professional Association for SQL Server
www.sqlpass.org
"Jeffrey Sheldon" <jsheldon@.projecthope.org> wrote in message
news:34DCEFE7-6054-44BB-B6E1-BF1AB9F79CDD@.microsoft.com...
> I am trying to establish a Database Maintenance plan for our SQL server
and when I choose
> Database Maintenance Plan
> Complete Backup Tab
> Under choose directory when I choose the (...) icon to choose a directory
only the C and D drive of the server appears, I do not see the network
drives.
> I resolved this in the past but forgot how to.
> Thanks

network drives

i have several sql servers 2000 sp3.
all have several network drives mapped.
on some i can't browse to those drives when trying to backup or restore
databases.
basically i will only see local drives.
how do i make sql server see mapped drives?
thanks
Backup to a UNC share that the account that SQL Server is running under has
access to.
BACKUP DATABASE master TO DISK = '\\SomeServer\SomeShare\master.bak' WITH
INIT
RESTORE DATABASE foo FROM DISK = '\\SomeServer\SomeShare\foo.bak' ...
Keith
"milosmaj" <milosmaj@.discussions.microsoft.com> wrote in message
news:B9EBA86D-EB0F-4844-BB89-534D3C9BA8A9@.microsoft.com...
> i have several sql servers 2000 sp3.
> all have several network drives mapped.
> on some i can't browse to those drives when trying to backup or restore
> databases.
> basically i will only see local drives.
> how do i make sql server see mapped drives?
> thanks
|||I agree with Keith, use UNC names, but the reason is that drive mappings
occur when someone logs on to the server... So what if someone else (with
different drive mappings) , logs on to the server, and now your backups
either fail, or go to Hoboken?...
UNC names prevent those kinds of problems from occurring..
Hope this helps...
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"milosmaj" <milosmaj@.discussions.microsoft.com> wrote in message
news:B9EBA86D-EB0F-4844-BB89-534D3C9BA8A9@.microsoft.com...
> i have several sql servers 2000 sp3.
> all have several network drives mapped.
> on some i can't browse to those drives when trying to backup or restore
> databases.
> basically i will only see local drives.
> how do i make sql server see mapped drives?
> thanks
sql

network drives

i have several sql servers 2000 sp3.
all have several network drives mapped.
on some i can't browse to those drives when trying to backup or restore
databases.
basically i will only see local drives.
how do i make sql server see mapped drives?
thanksBackup to a UNC share that the account that SQL Server is running under has
access to.
BACKUP DATABASE master TO DISK = '\\SomeServer\SomeShare\master.bak' WITH
INIT
RESTORE DATABASE foo FROM DISK = '\\SomeServer\SomeShare\foo.bak' ...
Keith
"milosmaj" <milosmaj@.discussions.microsoft.com> wrote in message
news:B9EBA86D-EB0F-4844-BB89-534D3C9BA8A9@.microsoft.com...
> i have several sql servers 2000 sp3.
> all have several network drives mapped.
> on some i can't browse to those drives when trying to backup or restore
> databases.
> basically i will only see local drives.
> how do i make sql server see mapped drives?
> thanks|||I agree with Keith, use UNC names, but the reason is that drive mappings
occur when someone logs on to the server... So what if someone else (with
different drive mappings) , logs on to the server, and now your backups
either fail, or go to Hoboken?...
UNC names prevent those kinds of problems from occurring..
Hope this helps...
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"milosmaj" <milosmaj@.discussions.microsoft.com> wrote in message
news:B9EBA86D-EB0F-4844-BB89-534D3C9BA8A9@.microsoft.com...
> i have several sql servers 2000 sp3.
> all have several network drives mapped.
> on some i can't browse to those drives when trying to backup or restore
> databases.
> basically i will only see local drives.
> how do i make sql server see mapped drives?
> thanks

Network Drives

Dear all,
I want to take backup of my Sql server 2000 databases on network drive but I am unable to find the network drive only local drive are seen in Enterprise Manager of my Sql server. Actually I have tried both by, maping my network drive thru Domain/Administrator password as well as domain/users password also but it will not showing my network drives.I am also changed my Sqlserver services with this account also.
Kindly help, Thanx in advance.
Lokesh/Ravishrikrishna
Hi
SQL Server and SQL Agent need to run under a domain account that has
permissions on the destination share. Do not map a drive, rather address it
as \\servername\sharename. EM does not understand it, so you can not backup
using the maintenance plan wizard. You have to write T-SQL code (BACKUP
DATABASE ...) and run it as a SQL Server Agent Job.
Regards
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Lokesh Bhatnagar" <lokesh@.webdunia.com> wrote in message
news:%23S9ccuAwFHA.908@.tk2msftngp13.phx.gbl...
Dear all,
I want to take backup of my Sql server 2000 databases on network drive but I
am unable to find the network drive only local drive are seen in Enterprise
Manager of my Sql server. Actually I have tried both by, maping my network
drive thru Domain/Administrator password as well as domain/users password
also but it will not showing my network drives.I am also changed my
Sqlserver services with this account also.
Kindly help, Thanx in advance.
Lokesh/Ravishrikrishna

network drives

i have several sql servers 2000 sp3.
all have several network drives mapped.
on some i can't browse to those drives when trying to backup or restore
databases.
basically i will only see local drives.
how do i make sql server see mapped drives?
thanksBackup to a UNC share that the account that SQL Server is running under has
access to.
BACKUP DATABASE master TO DISK = '\\SomeServer\SomeShare\master.bak' WITH
INIT
RESTORE DATABASE foo FROM DISK = '\\SomeServer\SomeShare\foo.bak' ...
--
Keith
"milosmaj" <milosmaj@.discussions.microsoft.com> wrote in message
news:B9EBA86D-EB0F-4844-BB89-534D3C9BA8A9@.microsoft.com...
> i have several sql servers 2000 sp3.
> all have several network drives mapped.
> on some i can't browse to those drives when trying to backup or restore
> databases.
> basically i will only see local drives.
> how do i make sql server see mapped drives?
> thanks|||I agree with Keith, use UNC names, but the reason is that drive mappings
occur when someone logs on to the server... So what if someone else (with
different drive mappings) , logs on to the server, and now your backups
either fail, or go to Hoboken?...
UNC names prevent those kinds of problems from occurring..
Hope this helps...
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"milosmaj" <milosmaj@.discussions.microsoft.com> wrote in message
news:B9EBA86D-EB0F-4844-BB89-534D3C9BA8A9@.microsoft.com...
> i have several sql servers 2000 sp3.
> all have several network drives mapped.
> on some i can't browse to those drives when trying to backup or restore
> databases.
> basically i will only see local drives.
> how do i make sql server see mapped drives?
> thanks

Network Drives

Dear all,
I want to take backup of my Sql server 2000 databases on network drive but I
am unable to find the network drive only local drive are seen in Enterprise
Manager of my Sql server. Actually I have tried both by, maping my network
drive thru Domain/Administrator password as well as domain/users password al
so but it will not showing my network drives.I am also changed my Sqlserver
services with this account also.
Kindly help, Thanx in advance.
Lokesh/RavishrikrishnaHi
SQL Server and SQL Agent need to run under a domain account that has
permissions on the destination share. Do not map a drive, rather address it
as \\servername\sharename. EM does not understand it, so you can not backup
using the maintenance plan wizard. You have to write T-SQL code (BACKUP
DATABASE ...) and run it as a SQL Server Agent Job.
Regards
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Lokesh Bhatnagar" <lokesh@.webdunia.com> wrote in message
news:%23S9ccuAwFHA.908@.tk2msftngp13.phx.gbl...
Dear all,
I want to take backup of my Sql server 2000 databases on network drive but I
am unable to find the network drive only local drive are seen in Enterprise
Manager of my Sql server. Actually I have tried both by, maping my network
drive thru Domain/Administrator password as well as domain/users password
also but it will not showing my network drives.I am also changed my
Sqlserver services with this account also.
Kindly help, Thanx in advance.
Lokesh/Ravishrikrishna

Network drive backup

Dear all,
I want to take backup of my Sql server 2000 databases on network drive but I
am unable to find the network drive only local drive are seen in Enterprise
Manager of my Sql server. Actually I have tried both by, maping my network
drive thru Domain/Administrator password as well as domain/users password
also but it will not showing my network drives.I am also changed my
Sqlserver services with this account also.
Kindly help, Thanx in advance.
Lokesh/RavishrikrishnaBOL
Transact-SQL Reference\BACKUP
--
Nik Marshall-Blank MCSD/MCDBA
"Lokesh Bhatnagar" <lokesh@.webdunia.com> wrote in message
news:errRL%23lwFHA.1252@.TK2MSFTNGP09.phx.gbl...
> Dear all,
> I want to take backup of my Sql server 2000 databases on network drive but
> I
> am unable to find the network drive only local drive are seen in
> Enterprise
> Manager of my Sql server. Actually I have tried both by, maping my network
> drive thru Domain/Administrator password as well as domain/users password
> also but it will not showing my network drives.I am also changed my
> Sqlserver services with this account also.
> Kindly help, Thanx in advance.
> Lokesh/Ravishrikrishna
>
>|||Hi Lokesh,
DO u have logon services permission on ur account.
U have to do backup by script.
from example backup database path='192.168.1.234\foldername'
dont use the drive name
when u share the folder add the username from which ur sql services are
running.
the mappnetwork drive may or may not work.
HTP
from
Doller|||You will not anything else in EM other than physical disks connected to the
SQL Server.
You must type the UNC name \\servername\folder in the backup directory and
ensure that the SQL Logon account has both priviliges for the network drive
and network access.
--
Nik Marshall-Blank MCSD/MCDBA
"Lokesh Bhatnagar" <lokesh@.webdunia.com> wrote in message
news:errRL%23lwFHA.1252@.TK2MSFTNGP09.phx.gbl...
> Dear all,
> I want to take backup of my Sql server 2000 databases on network drive but
> I
> am unable to find the network drive only local drive are seen in
> Enterprise
> Manager of my Sql server. Actually I have tried both by, maping my network
> drive thru Domain/Administrator password as well as domain/users password
> also but it will not showing my network drives.I am also changed my
> Sqlserver services with this account also.
> Kindly help, Thanx in advance.
> Lokesh/Ravishrikrishna
>
>|||Hi,
1.You Should start SQL server using Domain user who got access to remote
machine Share
2. Should have share in the remote machine
3. If you need to schedule this as a job then SQL Agent should use the same
Domain user in which SQL server was started
4. Restart the services
Now you can execute the Backup script with UNC path
BACKUP Database <dbname> to disk='\\computername\sharename­­\dbname.bak'
with init
Note:
Backup to remote machine will not work if you start SQL server using Local
system account
Thanks
Hari
SQL Server MVP
"Lokesh Bhatnagar" <lokesh@.webdunia.com> wrote in message
news:errRL%23lwFHA.1252@.TK2MSFTNGP09.phx.gbl...
> Dear all,
> I want to take backup of my Sql server 2000 databases on network drive but
> I
> am unable to find the network drive only local drive are seen in
> Enterprise
> Manager of my Sql server. Actually I have tried both by, maping my network
> drive thru Domain/Administrator password as well as domain/users password
> also but it will not showing my network drives.I am also changed my
> Sqlserver services with this account also.
> Kindly help, Thanx in advance.
> Lokesh/Ravishrikrishna
>
>|||Lokesh Bhatnagar wrote:
> Dear all,
> I want to take backup of my Sql server 2000 databases on network drive but I
> am unable to find the network drive only local drive are seen in Enterprise
> Manager of my Sql server. Actually I have tried both by, maping my network
> drive thru Domain/Administrator password as well as domain/users password
> also but it will not showing my network drives.I am also changed my
> Sqlserver services with this account also.
> Kindly help, Thanx in advance.
> Lokesh/Ravishrikrishna
>
>
You'll have to use a UNC path to do it. If you create a backup device
from EM, you'll have to type in the unc path to where you wan't the
backup file. If you do it from QA, you have to use the backup command
with ...TO DISK = '\\YourServerName\BackupFolder\YourBackupFileName.BAK'
If I'm not wrong, you can't create a Maintenance Plan that backs up to a
UNC path.
Regards
Steensql

Network drive backup

Dear all,
I want to take backup of my Sql server 2000 databases on network drive but I
am unable to find the network drive only local drive are seen in Enterprise
Manager of my Sql server. Actually I have tried both by, maping my network
drive thru Domain/Administrator password as well as domain/users password
also but it will not showing my network drives.I am also changed my
Sqlserver services with this account also.
Kindly help, Thanx in advance.
Lokesh/Ravishrikrishna
BOL
Transact-SQL Reference\BACKUP
Nik Marshall-Blank MCSD/MCDBA
"Lokesh Bhatnagar" <lokesh@.webdunia.com> wrote in message
news:errRL%23lwFHA.1252@.TK2MSFTNGP09.phx.gbl...
> Dear all,
> I want to take backup of my Sql server 2000 databases on network drive but
> I
> am unable to find the network drive only local drive are seen in
> Enterprise
> Manager of my Sql server. Actually I have tried both by, maping my network
> drive thru Domain/Administrator password as well as domain/users password
> also but it will not showing my network drives.I am also changed my
> Sqlserver services with this account also.
> Kindly help, Thanx in advance.
> Lokesh/Ravishrikrishna
>
>
|||Hi Lokesh,
DO u have logon services permission on ur account.
U have to do backup by script.
from example backup database path='192.168.1.234\foldername'
dont use the drive name
when u share the folder add the username from which ur sql services are
running.
the mappnetwork drive may or may not work.
HTP
from
Doller
|||You will not anything else in EM other than physical disks connected to the
SQL Server.
You must type the UNC name \\servername\folder in the backup directory and
ensure that the SQL Logon account has both priviliges for the network drive
and network access.
Nik Marshall-Blank MCSD/MCDBA
"Lokesh Bhatnagar" <lokesh@.webdunia.com> wrote in message
news:errRL%23lwFHA.1252@.TK2MSFTNGP09.phx.gbl...
> Dear all,
> I want to take backup of my Sql server 2000 databases on network drive but
> I
> am unable to find the network drive only local drive are seen in
> Enterprise
> Manager of my Sql server. Actually I have tried both by, maping my network
> drive thru Domain/Administrator password as well as domain/users password
> also but it will not showing my network drives.I am also changed my
> Sqlserver services with this account also.
> Kindly help, Thanx in advance.
> Lokesh/Ravishrikrishna
>
>
|||Hi,
1.You Should start SQL server using Domain user who got access to remote
machine Share
2. Should have share in the remote machine
3. If you need to schedule this as a job then SQL Agent should use the same
Domain user in which SQL server was started
4. Restart the services
Now you can execute the Backup script with UNC path
BACKUP Database <dbname> to disk='\\computername\sharenameXX\dbname.bak'
with init
Note:
Backup to remote machine will not work if you start SQL server using Local
system account
Thanks
Hari
SQL Server MVP
"Lokesh Bhatnagar" <lokesh@.webdunia.com> wrote in message
news:errRL%23lwFHA.1252@.TK2MSFTNGP09.phx.gbl...
> Dear all,
> I want to take backup of my Sql server 2000 databases on network drive but
> I
> am unable to find the network drive only local drive are seen in
> Enterprise
> Manager of my Sql server. Actually I have tried both by, maping my network
> drive thru Domain/Administrator password as well as domain/users password
> also but it will not showing my network drives.I am also changed my
> Sqlserver services with this account also.
> Kindly help, Thanx in advance.
> Lokesh/Ravishrikrishna
>
>
|||Lokesh Bhatnagar wrote:
> Dear all,
> I want to take backup of my Sql server 2000 databases on network drive but I
> am unable to find the network drive only local drive are seen in Enterprise
> Manager of my Sql server. Actually I have tried both by, maping my network
> drive thru Domain/Administrator password as well as domain/users password
> also but it will not showing my network drives.I am also changed my
> Sqlserver services with this account also.
> Kindly help, Thanx in advance.
> Lokesh/Ravishrikrishna
>
>
You'll have to use a UNC path to do it. If you create a backup device
from EM, you'll have to type in the unc path to where you wan't the
backup file. If you do it from QA, you have to use the backup command
with ...TO DISK = '\\YourServerName\BackupFolder\YourBackupFileName. BAK'
If I'm not wrong, you can't create a Maintenance Plan that backs up to a
UNC path.
Regards
Steen

Network drive backup

Dear all,
I want to take backup of my Sql server 2000 databases on network drive but I
am unable to find the network drive only local drive are seen in Enterprise
Manager of my Sql server. Actually I have tried both by, maping my network
drive thru Domain/Administrator password as well as domain/users password
also but it will not showing my network drives.I am also changed my
Sqlserver services with this account also.
Kindly help, Thanx in advance.
Lokesh/RavishrikrishnaBOL
Transact-SQL Reference\BACKUP
Nik Marshall-Blank MCSD/MCDBA
"Lokesh Bhatnagar" <lokesh@.webdunia.com> wrote in message
news:errRL%23lwFHA.1252@.TK2MSFTNGP09.phx.gbl...
> Dear all,
> I want to take backup of my Sql server 2000 databases on network drive but
> I
> am unable to find the network drive only local drive are seen in
> Enterprise
> Manager of my Sql server. Actually I have tried both by, maping my network
> drive thru Domain/Administrator password as well as domain/users password
> also but it will not showing my network drives.I am also changed my
> Sqlserver services with this account also.
> Kindly help, Thanx in advance.
> Lokesh/Ravishrikrishna
>
>|||Hi Lokesh,
DO u have logon services permission on ur account.
U have to do backup by script.
from example backup database path='192.168.1.234\foldername'
dont use the drive name
when u share the folder add the username from which ur sql services are
running.
the mappnetwork drive may or may not work.
HTP
from
Doller|||You will not anything else in EM other than physical disks connected to the
SQL Server.
You must type the UNC name \\servername\folder in the backup directory and
ensure that the SQL Logon account has both priviliges for the network drive
and network access.
Nik Marshall-Blank MCSD/MCDBA
"Lokesh Bhatnagar" <lokesh@.webdunia.com> wrote in message
news:errRL%23lwFHA.1252@.TK2MSFTNGP09.phx.gbl...
> Dear all,
> I want to take backup of my Sql server 2000 databases on network drive but
> I
> am unable to find the network drive only local drive are seen in
> Enterprise
> Manager of my Sql server. Actually I have tried both by, maping my network
> drive thru Domain/Administrator password as well as domain/users password
> also but it will not showing my network drives.I am also changed my
> Sqlserver services with this account also.
> Kindly help, Thanx in advance.
> Lokesh/Ravishrikrishna
>
>|||Hi,
1.You Should start SQL server using Domain user who got access to remote
machine Share
2. Should have share in the remote machine
3. If you need to schedule this as a job then SQL Agent should use the same
Domain user in which SQL server was started
4. Restart the services
Now you can execute the Backup script with UNC path
BACKUP Database <dbname> to disk='\\computername\sharename__\dbname.bak'
with init
Note:
Backup to remote machine will not work if you start SQL server using Local
system account
Thanks
Hari
SQL Server MVP
"Lokesh Bhatnagar" <lokesh@.webdunia.com> wrote in message
news:errRL%23lwFHA.1252@.TK2MSFTNGP09.phx.gbl...
> Dear all,
> I want to take backup of my Sql server 2000 databases on network drive but
> I
> am unable to find the network drive only local drive are seen in
> Enterprise
> Manager of my Sql server. Actually I have tried both by, maping my network
> drive thru Domain/Administrator password as well as domain/users password
> also but it will not showing my network drives.I am also changed my
> Sqlserver services with this account also.
> Kindly help, Thanx in advance.
> Lokesh/Ravishrikrishna
>
>|||Lokesh Bhatnagar wrote:
> Dear all,
> I want to take backup of my Sql server 2000 databases on network drive but
I
> am unable to find the network drive only local drive are seen in Enterpris
e
> Manager of my Sql server. Actually I have tried both by, maping my network
> drive thru Domain/Administrator password as well as domain/users password
> also but it will not showing my network drives.I am also changed my
> Sqlserver services with this account also.
> Kindly help, Thanx in advance.
> Lokesh/Ravishrikrishna
>
>
You'll have to use a UNC path to do it. If you create a backup device
from EM, you'll have to type in the unc path to where you wan't the
backup file. If you do it from QA, you have to use the backup command
with ...TO DISK = '\\YourServerName\BackupFolder\YourBacku
pFileName.BAK'
If I'm not wrong, you can't create a Maintenance Plan that backs up to a
UNC path.
Regards
Steen

network disk(SAN) for backup

Hello all,
Can I use network disk(SAN) to take a backup on a database?
I tested it, but it failed.
I use SQL Server 2000 and Windows Server 2000 and 2003.
Thanks in advance,
Do.
Message posted via droptable.com
http://www.droptable.com/Uwe/Forums...erver/200510/1
Check out:
http://www.microsoft.com/technet/pro.../spltmirr.mspx
and
http://www.redbooks.ibm.com/abstracts/sg245470.html
HTH
Jerry
"Do Park via droptable.com" <u3287@.uwe> wrote in message
news:55d595770f944@.uwe...
> Hello all,
> Can I use network disk(SAN) to take a backup on a database?
> I tested it, but it failed.
> I use SQL Server 2000 and Windows Server 2000 and 2003.
> Thanks in advance,
> Do.
>
> --
> Message posted via droptable.com
> http://www.droptable.com/Uwe/Forums...erver/200510/1
|||How did you try? What was the error message?
Andrew J. Kelly SQL MVP
"Do Park via droptable.com" <u3287@.uwe> wrote in message
news:55d595770f944@.uwe...
> Hello all,
> Can I use network disk(SAN) to take a backup on a database?
> I tested it, but it failed.
> I use SQL Server 2000 and Windows Server 2000 and 2003.
> Thanks in advance,
> Do.
>
> --
> Message posted via droptable.com
> http://www.droptable.com/Uwe/Forums...erver/200510/1

network disk(SAN) for backup

Hello all,
Can I use network disk(SAN) to take a backup on a database?
I tested it, but it failed.
I use SQL Server 2000 and Windows Server 2000 and 2003.
Thanks in advance,
Do.
Message posted via droptable.com
http://www.droptable.com/Uwe/Forum...server/200510/1Check out:
http://www.microsoft.com/technet/pr...n/spltmirr.mspx
and
http://www.redbooks.ibm.com/abstracts/sg245470.html
HTH
Jerry
"Do Park via droptable.com" <u3287@.uwe> wrote in message
news:55d595770f944@.uwe...
> Hello all,
> Can I use network disk(SAN) to take a backup on a database?
> I tested it, but it failed.
> I use SQL Server 2000 and Windows Server 2000 and 2003.
> Thanks in advance,
> Do.
>
> --
> Message posted via droptable.com
> http://www.droptable.com/Uwe/Forum...server/200510/1|||How did you try? What was the error message?
Andrew J. Kelly SQL MVP
"Do Park via droptable.com" <u3287@.uwe> wrote in message
news:55d595770f944@.uwe...
> Hello all,
> Can I use network disk(SAN) to take a backup on a database?
> I tested it, but it failed.
> I use SQL Server 2000 and Windows Server 2000 and 2003.
> Thanks in advance,
> Do.
>
> --
> Message posted via droptable.com
> http://www.droptable.com/Uwe/Forum...server/200510/1