"The specified module could not be found", Server Network Utility

Has any body had a problem whereby when you try and load the Server Network
Utility you get the error "The specified module could not be found". I have
SQL Server 2000 developer installed on my machine and 3 instances of MSDE and
2 of wMSDE. I have reinstalled sql server sp4, this has had no effect. Any
ideas anybody?
This issue is typically caused by a damaged installation of client tools. I
suggest that you reinstall the client tools through the following steps:
1. Insert the SQL Server 2000 compact disc into your CD-ROM drive. If the
compact disc does not autorun, double-click Autorun.exe in the root
directory of the compact disc.
2. Select SQL Server 2000 Components, select Install Database Server, and
then click Next at the Welcome screen of the SQL Server Installation Wizard.
3. In Computer Name dialog box, Local Computer is the default option, and
the local computer name appears in the edit box. Click Next.
4. In the Installation Selection dialog box, click Create a new instance of
SQL Server, or install Client Tools, and then click Next.
5. Follow the directions on the User Information, Software License
Agreement, and related screens.
6. In the Installation Definition dialog box, click Client tools only, and
then click Next.
7. In the Select Components dialog box, accept the defaults or select the
components you want, and then click Next.
8. In the Start Copying Files dialog box, click Next to complete the
installation of the client tools.
9. Check whether the Server Network Utility works correctly. If it works,
reapply SP4.
If the issue persists, I'd like to use the Dependency Walker tool to track
the module that cannot be loaded. To do so, follow these steps:
1) Download Dependency Walker utility from www.dependencywalker.com.
2) Create a new folder on your system and extract the files from this
executable into the folder.
3) Start Dependency Walker utility by double-clicking depends.exe.
4) From the File menu, click Open and choose the file C:\Program
Files\Microsoft Sql Server\80\Tools\Binn\svrnetcn.exe.
5) Click menu option Profile -> Start Profiling.
6) Select all checkboxes on the "Profile Module" dialog box.
7) Click OK to start profiling.
8) After the profiling finished, go to File-Save As-> save as svrnetcn.dwi.
9) Zip the .dwi file and e-mail it to me at v-rxwang@.microsoft.com.
Third-Party Link Disclaimer
===========
This response contains a reference to a third-party World Wide Web site.
Microsoft is providing this information as a convenience to you. Microsoft
does not control these sites and has not tested any software or information
found on these sites; therefore, Microsoft cannot make any representations
regarding the quality, safety, or suitability of any software or
information found there. There are inherent dangers in the use of any
software found on the Internet, and Microsoft cautions you to make sure
that you completely understand the risk before retrieving any software from
the Internet.
If anything is unclear, feel free to let me know.
Sincerely,
William Wang
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
This posting is provided "AS IS" with no warranties, and confers no rights.
--
>Thread-Topic: "The specified module could not be found", Server Network
Utility
>thread-index: AcV5tMB8B0i7JmcNRia3obumQYfDXQ==
>X-WBNR-Posting-Host: 213.152.39.142
>From: "=?Utf-8?B?bmlja25hbWU=?=" <nickname@.online.nospam>
>Subject: "The specified module could not be found", Server Network Utility
>Date: Sat, 25 Jun 2005 11:36:08 -0700
>Lines: 5
>Message-ID: <02512271-F9D5-4CE4-8FE7-F9F92D841595@.microsoft.com>
>MIME-Version: 1.0
>Content-Type: text/plain;
>charset="Utf-8"
>Content-Transfer-Encoding: 7bit
>X-Newsreader: Microsoft CDO for Windows 2000
>Content-Class: urn:content-classes:message
>Importance: normal
>Priority: normal
>X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
>Newsgroups: microsoft.public.sqlserver.tools
>NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.2.250
>Path: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGXA02.phx.gbl!TK2MSF TNGXA03.phx.gbl
>Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.sqlserver.tools:4640
>X-Tomcat-NG: microsoft.public.sqlserver.tools
>Has any body had a problem whereby when you try and load the Server
Network
>Utility you get the error "The specified module could not be found". I
have
>SQL Server 2000 developer installed on my machine and 3 instances of MSDE
and
>2 of wMSDE. I have reinstalled sql server sp4, this has had no effect. Any
>ideas anybody?
>

"Suddently" can't connect to sql server (SP security prob, maybe?)

Hi! I'm running sql server 2003 on a network for my small business; I'm
having probs connecting to the server from my desktop. What's odd is that
this prob sudently occured yesterday...I had been connecting before that
(like, for several years?) and now I can't hit the box thorugh either Query
Analyzer or Enterprise manager.
The server is online because I can map to it and see the directories. Also:
I have a notebook which still can see the SQL Server box with NO Problems!
Which begs the question: what changed over the weekend? I seem to remember
that a OS SP/Hotfix/etc was automatically downloaded and installed on one of
these two computers recently. Are you aware of any security changes that may
have been slipped in on either the server or the client side to explain this?
I'm running Win Server 2003 on the server and XP Prof SP2 on the desktop.
Thanks in advance for your help. I rally appreciate it!
Roger,

> I have a notebook which still can see the SQL Server box with NO Problems!
The box or the SQL Server i.e., the databases, tables and data. Can you
acesss the SQL Server by IP address? Does the OSQL utility work? What if
you try creating a DSN and 'test the connection' - just to rule out the SQL
tools as a possible cause? Have you tried restarting this client?
HTH
Jerry
"Roger Willcode" <RogerWillcode@.discussions.microsoft.com> wrote in message
news:FA1EA7E3-B9D7-4E06-96B9-D619A211088D@.microsoft.com...
> Hi! I'm running sql server 2003 on a network for my small business; I'm
> having probs connecting to the server from my desktop. What's odd is that
> this prob sudently occured yesterday...I had been connecting before that
> (like, for several years?) and now I can't hit the box thorugh either
> Query
> Analyzer or Enterprise manager.
> The server is online because I can map to it and see the directories.
> Also:
> I have a notebook which still can see the SQL Server box with NO Problems!
> Which begs the question: what changed over the weekend? I seem to remember
> that a OS SP/Hotfix/etc was automatically downloaded and installed on one
> of
> these two computers recently. Are you aware of any security changes that
> may
> have been slipped in on either the server or the client side to explain
> this?
> I'm running Win Server 2003 on the server and XP Prof SP2 on the desktop.
> Thanks in advance for your help. I rally appreciate it!
|||Roger,
So if I read your e-mail correctly from your desktop you can login via
Query Analyzer or Enterprise Manager but from another box you can login
to the SQL Server box using another tool? Could there have been a
network change the happened on the weekend where you box got a new IP or
the network security changed?
If the SQL Server is up [you can login via another client or directly on
the box itself] then the problem has to be with your computer or network
permissions. You may check to see if your IP changed or perhaps they
access from your IP to the server was removed.
Shahryar
Roger Willcode wrote:

>Hi! I'm running sql server 2003 on a network for my small business; I'm
>having probs connecting to the server from my desktop. What's odd is that
>this prob sudently occured yesterday...I had been connecting before that
>(like, for several years?) and now I can't hit the box thorugh either Query
>Analyzer or Enterprise manager.
>The server is online because I can map to it and see the directories. Also:
>I have a notebook which still can see the SQL Server box with NO Problems!
>Which begs the question: what changed over the weekend? I seem to remember
>that a OS SP/Hotfix/etc was automatically downloaded and installed on one of
>these two computers recently. Are you aware of any security changes that may
>have been slipped in on either the server or the client side to explain this?
>I'm running Win Server 2003 on the server and XP Prof SP2 on the desktop.
>Thanks in advance for your help. I rally appreciate it!
>
Shahryar G. Hashemi | Sr. DBA Consultant
InfoSpace, Inc.
601 108th Ave NE | Suite 1200 | Bellevue, WA 98004 USA
Mobile +1 206.459.6203 | Office +1 425.201.8853 | Fax +1 425.201.6150
shashem@.infospace.com | www.infospaceinc.com
This e-mail and any attachments may contain confidential information that is legally privileged. The information is solely for the use of the intended recipient(s); any disclosure, copying, distribution, or other use of this information is strictly prohi
bited. If you have received this e-mail in error, please notify the sender by return e-mail and delete this message. Thank you.

"Suddently" can't connect to sql server (SP security prob, maybe?)

Hi! I'm running sql server 2003 on a network for my small business; I'm
having probs connecting to the server from my desktop. What's odd is that
this prob sudently occured yesterday...I had been connecting before that
(like, for several years?) and now I can't hit the box thorugh either Query
Analyzer or Enterprise manager.
The server is online because I can map to it and see the directories. Also:
I have a notebook which still can see the SQL Server box with NO Problems!
Which begs the question: what changed over the weekend? I seem to remember
that a OS SP/Hotfix/etc was automatically downloaded and installed on one of
these two computers recently. Are you aware of any security changes that may
have been slipped in on either the server or the client side to explain this?
I'm running Win Server 2003 on the server and XP Prof SP2 on the desktop.
Thanks in advance for your help. I rally appreciate it!Roger,
> I have a notebook which still can see the SQL Server box with NO Problems!
The box or the SQL Server i.e., the databases, tables and data. Can you
acesss the SQL Server by IP address? Does the OSQL utility work? What if
you try creating a DSN and 'test the connection' - just to rule out the SQL
tools as a possible cause? Have you tried restarting this client?
HTH
Jerry
"Roger Willcode" <RogerWillcode@.discussions.microsoft.com> wrote in message
news:FA1EA7E3-B9D7-4E06-96B9-D619A211088D@.microsoft.com...
> Hi! I'm running sql server 2003 on a network for my small business; I'm
> having probs connecting to the server from my desktop. What's odd is that
> this prob sudently occured yesterday...I had been connecting before that
> (like, for several years?) and now I can't hit the box thorugh either
> Query
> Analyzer or Enterprise manager.
> The server is online because I can map to it and see the directories.
> Also:
> I have a notebook which still can see the SQL Server box with NO Problems!
> Which begs the question: what changed over the weekend? I seem to remember
> that a OS SP/Hotfix/etc was automatically downloaded and installed on one
> of
> these two computers recently. Are you aware of any security changes that
> may
> have been slipped in on either the server or the client side to explain
> this?
> I'm running Win Server 2003 on the server and XP Prof SP2 on the desktop.
> Thanks in advance for your help. I rally appreciate it!|||Roger,
So if I read your e-mail correctly from your desktop you can login via
Query Analyzer or Enterprise Manager but from another box you can login
to the SQL Server box using another tool? Could there have been a
network change the happened on the weekend where you box got a new IP or
the network security changed?
If the SQL Server is up [you can login via another client or directly on
the box itself] then the problem has to be with your computer or network
permissions. You may check to see if your IP changed or perhaps they
access from your IP to the server was removed.
Shahryar
Roger Willcode wrote:
>Hi! I'm running sql server 2003 on a network for my small business; I'm
>having probs connecting to the server from my desktop. What's odd is that
>this prob sudently occured yesterday...I had been connecting before that
>(like, for several years?) and now I can't hit the box thorugh either Query
>Analyzer or Enterprise manager.
>The server is online because I can map to it and see the directories. Also:
>I have a notebook which still can see the SQL Server box with NO Problems!
>Which begs the question: what changed over the weekend? I seem to remember
>that a OS SP/Hotfix/etc was automatically downloaded and installed on one of
>these two computers recently. Are you aware of any security changes that may
>have been slipped in on either the server or the client side to explain this?
>I'm running Win Server 2003 on the server and XP Prof SP2 on the desktop.
>Thanks in advance for your help. I rally appreciate it!
>
Shahryar G. Hashemi | Sr. DBA Consultant
InfoSpace, Inc.
601 108th Ave NE | Suite 1200 | Bellevue, WA 98004 USA
Mobile +1 206.459.6203 | Office +1 425.201.8853 | Fax +1 425.201.6150
shashem@.infospace.com | www.infospaceinc.com
This e-mail and any attachments may contain confidential information that is legally privileged. The information is solely for the use of the intended recipient(s); any disclosure, copying, distribution, or other use of this information is strictly prohibited. If you have received this e-mail in error, please notify the sender by return e-mail and delete this message. Thank you.|||Jerry, Shahryar:
First: Thanks to both you you for replying! It works now -- although I'm not
exactly sure what changed.
If it helps for anyone else reading this post; I did restart both the client
and the server to no avail. Also, I don't think there was a change in the
network permissions; I'm the only user on this network! I *did* try
connecting with the IP address and that was also a dead end.
Just for TheHalibut, I tried Jerry's suggestion of creating a ODBC
connection. When I selected TCP/IP as the connection it failed to connect.
But when I clicked the "named pipes" radio button it worked. Even more
puzzling was that I can now go back to Enterprise Manager -- and without any
further changes -- it works again.
Any body have any clues as to what happened? Also, Jerry refered to a "OSQL
utility." Sorry to be dense, but what is that?
Thanks again for your help. I'm good for now, and if you get a chance to
post any thouughts you have on my questions, I'll be even better next time!
Take care.
"Jerry Spivey" wrote:
> Roger,
> > I have a notebook which still can see the SQL Server box with NO Problems!
> The box or the SQL Server i.e., the databases, tables and data. Can you
> acesss the SQL Server by IP address? Does the OSQL utility work? What if
> you try creating a DSN and 'test the connection' - just to rule out the SQL
> tools as a possible cause? Have you tried restarting this client?
> HTH
> Jerry
> "Roger Willcode" <RogerWillcode@.discussions.microsoft.com> wrote in message
> news:FA1EA7E3-B9D7-4E06-96B9-D619A211088D@.microsoft.com...
> > Hi! I'm running sql server 2003 on a network for my small business; I'm
> > having probs connecting to the server from my desktop. What's odd is that
> > this prob sudently occured yesterday...I had been connecting before that
> > (like, for several years?) and now I can't hit the box thorugh either
> > Query
> > Analyzer or Enterprise manager.
> >
> > The server is online because I can map to it and see the directories.
> > Also:
> > I have a notebook which still can see the SQL Server box with NO Problems!
> >
> > Which begs the question: what changed over the weekend? I seem to remember
> > that a OS SP/Hotfix/etc was automatically downloaded and installed on one
> > of
> > these two computers recently. Are you aware of any security changes that
> > may
> > have been slipped in on either the server or the client side to explain
> > this?
> >
> > I'm running Win Server 2003 on the server and XP Prof SP2 on the desktop.
> >
> > Thanks in advance for your help. I rally appreciate it!
>
>|||Roger,
The OSQL utility is the CMD line utility for querying SQL Server.
See:
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/coprompt/cp_osql_1wxl.asp
HTH
Jerry
"Roger Willcode" <RogerWillcode@.discussions.microsoft.com> wrote in message
news:1031B9B4-3AF4-4BF3-8B7D-A0A97E92057A@.microsoft.com...
> Jerry, Shahryar:
> First: Thanks to both you you for replying! It works now -- although I'm
> not
> exactly sure what changed.
> If it helps for anyone else reading this post; I did restart both the
> client
> and the server to no avail. Also, I don't think there was a change in the
> network permissions; I'm the only user on this network! I *did* try
> connecting with the IP address and that was also a dead end.
> Just for TheHalibut, I tried Jerry's suggestion of creating a ODBC
> connection. When I selected TCP/IP as the connection it failed to connect.
> But when I clicked the "named pipes" radio button it worked. Even more
> puzzling was that I can now go back to Enterprise Manager -- and without
> any
> further changes -- it works again.
> Any body have any clues as to what happened? Also, Jerry refered to a
> "OSQL
> utility." Sorry to be dense, but what is that?
> Thanks again for your help. I'm good for now, and if you get a chance to
> post any thouughts you have on my questions, I'll be even better next
> time!
> Take care.
>
> "Jerry Spivey" wrote:
>> Roger,
>> > I have a notebook which still can see the SQL Server box with NO
>> > Problems!
>> The box or the SQL Server i.e., the databases, tables and data. Can you
>> acesss the SQL Server by IP address? Does the OSQL utility work? What
>> if
>> you try creating a DSN and 'test the connection' - just to rule out the
>> SQL
>> tools as a possible cause? Have you tried restarting this client?
>> HTH
>> Jerry
>> "Roger Willcode" <RogerWillcode@.discussions.microsoft.com> wrote in
>> message
>> news:FA1EA7E3-B9D7-4E06-96B9-D619A211088D@.microsoft.com...
>> > Hi! I'm running sql server 2003 on a network for my small business; I'm
>> > having probs connecting to the server from my desktop. What's odd is
>> > that
>> > this prob sudently occured yesterday...I had been connecting before
>> > that
>> > (like, for several years?) and now I can't hit the box thorugh either
>> > Query
>> > Analyzer or Enterprise manager.
>> >
>> > The server is online because I can map to it and see the directories.
>> > Also:
>> > I have a notebook which still can see the SQL Server box with NO
>> > Problems!
>> >
>> > Which begs the question: what changed over the weekend? I seem to
>> > remember
>> > that a OS SP/Hotfix/etc was automatically downloaded and installed on
>> > one
>> > of
>> > these two computers recently. Are you aware of any security changes
>> > that
>> > may
>> > have been slipped in on either the server or the client side to explain
>> > this?
>> >
>> > I'm running Win Server 2003 on the server and XP Prof SP2 on the
>> > desktop.
>> >
>> > Thanks in advance for your help. I rally appreciate it!
>>

"Suddently" can't connect to sql server (SP security prob, maybe?)

Hi! I'm running sql server 2003 on a network for my small business; I'm
having probs connecting to the server from my desktop. What's odd is that
this prob sudently occured yesterday...I had been connecting before that
(like, for several years?) and now I can't hit the box thorugh either Query
Analyzer or Enterprise manager.
The server is online because I can map to it and see the directories. Also:
I have a notebook which still can see the SQL Server box with NO Problems!
Which begs the question: what changed over the weekend? I seem to remember
that a OS SP/Hotfix/etc was automatically downloaded and installed on one of
these two computers recently. Are you aware of any security changes that may
have been slipped in on either the server or the client side to explain this
?
I'm running Win Server 2003 on the server and XP Prof SP2 on the desktop.
Thanks in advance for your help. I rally appreciate it!Roger,

> I have a notebook which still can see the SQL Server box with NO Problems!
The box or the SQL Server i.e., the databases, tables and data. Can you
acesss the SQL Server by IP address? Does the OSQL utility work? What if
you try creating a DSN and 'test the connection' - just to rule out the SQL
tools as a possible cause? Have you tried restarting this client?
HTH
Jerry
"Roger Willcode" <RogerWillcode@.discussions.microsoft.com> wrote in message
news:FA1EA7E3-B9D7-4E06-96B9-D619A211088D@.microsoft.com...
> Hi! I'm running sql server 2003 on a network for my small business; I'm
> having probs connecting to the server from my desktop. What's odd is that
> this prob sudently occured yesterday...I had been connecting before that
> (like, for several years?) and now I can't hit the box thorugh either
> Query
> Analyzer or Enterprise manager.
> The server is online because I can map to it and see the directories.
> Also:
> I have a notebook which still can see the SQL Server box with NO Problems!
> Which begs the question: what changed over the weekend? I seem to remember
> that a OS SP/Hotfix/etc was automatically downloaded and installed on one
> of
> these two computers recently. Are you aware of any security changes that
> may
> have been slipped in on either the server or the client side to explain
> this?
> I'm running Win Server 2003 on the server and XP Prof SP2 on the desktop.
> Thanks in advance for your help. I rally appreciate it!|||Roger,
So if I read your e-mail correctly from your desktop you can login via
Query Analyzer or Enterprise Manager but from another box you can login
to the SQL Server box using another tool? Could there have been a
network change the happened on the weekend where you box got a new IP or
the network security changed?
If the SQL Server is up [you can login via another client or directly on
the box itself] then the problem has to be with your computer or network
permissions. You may check to see if your IP changed or perhaps they
access from your IP to the server was removed.
Shahryar
Roger Willcode wrote:

>Hi! I'm running sql server 2003 on a network for my small business; I'm
>having probs connecting to the server from my desktop. What's odd is that
>this prob sudently occured yesterday...I had been connecting before that
>(like, for several years?) and now I can't hit the box thorugh either Query
>Analyzer or Enterprise manager.
>The server is online because I can map to it and see the directories. Also:
>I have a notebook which still can see the SQL Server box with NO Problems!
>Which begs the question: what changed over the weekend? I seem to remember
>that a OS SP/Hotfix/etc was automatically downloaded and installed on one o
f
>these two computers recently. Are you aware of any security changes that ma
y
>have been slipped in on either the server or the client side to explain thi
s?
>I'm running Win Server 2003 on the server and XP Prof SP2 on the desktop.
>Thanks in advance for your help. I rally appreciate it!
>
Shahryar G. Hashemi | Sr. DBA Consultant
InfoSpace, Inc.
601 108th Ave NE | Suite 1200 | Bellevue, WA 98004 USA
Mobile +1 206.459.6203 | Office +1 425.201.8853 | Fax +1 425.201.6150
shashem@.infospace.com | www.infospaceinc.com
This e-mail and any attachments may contain confidential information that is
legally privileged. The information is solely for the use of the intended
recipient(s); any disclosure, copying, distribution, or other use of this in
formation is strictly prohi
bited. If you have received this e-mail in error, please notify the sender
by return e-mail and delete this message. Thank you.

"ORA-03114: not connected to ORACLE".

In a windows service (.NET) on unplugging network cable it use to loose
connection to oracle database.
Once the network connection was up it was found that the service was unable
to restore its connection to oracle database.
The conclusion that we drew after doing R&D was that, the connection pool
was keeping the bad connection in connection pool on network disconnection
which resulted in the service to use those bad connection and keep throwing
exception “not connected to Oracle”.
On Microsoft site there is a mention of Hot Fix. Where can we get this?
http://support.microsoft.com/default...b;en-us;830173
Is there any way we can solve this problem without applying the HOT FIX.
Architect
eBusiness & Intranet
You will need to contact Microsoft PSS Developer Support (contact information
is on the kb article you referenced.) There are two versions of the hotfix,
..NET RTM and .NET 1.1 SP1.
"WEB_CMA" wrote:
> In a windows service (.NET) on unplugging network cable it use to loose
> connection to oracle database.
> Once the network connection was up it was found that the service was unable
> to restore its connection to oracle database.
> The conclusion that we drew after doing R&D was that, the connection pool
> was keeping the bad connection in connection pool on network disconnection
> which resulted in the service to use those bad connection and keep throwing
> exception “not connected to Oracle”.
> On Microsoft site there is a mention of Hot Fix. Where can we get this?
> http://support.microsoft.com/default...b;en-us;830173
>
> Is there any way we can solve this problem without applying the HOT FIX.
> --
> Architect
> eBusiness & Intranet
>

"ORA-03114: not connected to ORACLE".

In a windows service (.NET) on unplugging network cable it use to loose
connection to oracle database.
Once the network connection was up it was found that the service was unable
to restore its connection to oracle database.
The conclusion that we drew after doing R&D was that, the connection pool
was keeping the bad connection in connection pool on network disconnection
which resulted in the service to use those bad connection and keep throwing
exception “not connected to Oracle”.
On Microsoft site there is a mention of Hot Fix. Where can we get this'
http://support.microsoft.com/defaul...kb;en-us;830173
Is there any way we can solve this problem without applying the HOT FIX.
Architect
eBusiness & IntranetYou will need to contact Microsoft PSS Developer Support (contact informatio
n
is on the kb article you referenced.) There are two versions of the hotfix,
.NET RTM and .NET 1.1 SP1.
"WEB_CMA" wrote:
> In a windows service (.NET) on unplugging network cable it use to loose
> connection to oracle database.
> Once the network connection was up it was found that the service was unabl
e
> to restore its connection to oracle database.
> The conclusion that we drew after doing R&D was that, the connection pool
> was keeping the bad connection in connection pool on network disconnection
> which resulted in the service to use those bad connection and keep throwin
g
> exception “not connected to Oracle”.
> On Microsoft site there is a mention of Hot Fix. Where can we get this'
> http://support.microsoft.com/defaul...kb;en-us;830173
>
> Is there any way we can solve this problem without applying the HOT FIX.
> --
> Architect
> eBusiness & Intranet
>

"network name is no longer available"

Hi all,
I'm having a problem with backing up SQL to a network share, often I would
get the "network name is no longer available". Sometimes it works and
sometimes it doesn't. During the backup, both servers - source and
destination are at minimal cpu , memory and network utilization. Network
drivers are also up to date. OS has sp4. Has anyone come across this
before? Any suggestions would be appreciated. Thank you.
I ran into this myself sometimes an these are a few thing I would look for
answers in: What do the SQL Server Error logs say and what do the
application logs on the server say? Is the server you are backing up on a
NAS box or use IDE drives or SCSI drives? Is the server holding the backups
using a static IP address? Does this problem only occur on this one server
holding the backup or on any server you try?
Depending on these answers the problem should be isolated more.
Bryan Bitzer MCP
Senior Database Administrator
Marshall & Swift / Boeckh
www.msbinfo.com
"network name is no longer available" <"network name is no longer
available"@.discussions.microsoft.com> wrote in message
news:A3D0CDBF-0FF4-4FF3-8CCA-529E34AE7F5D@.microsoft.com...
> Hi all,
> I'm having a problem with backing up SQL to a network share, often I would
> get the "network name is no longer available". Sometimes it works and
> sometimes it doesn't. During the backup, both servers - source and
> destination are at minimal cpu , memory and network utilization. Network
> drivers are also up to date. OS has sp4. Has anyone come across this
> before? Any suggestions would be appreciated. Thank you.
>
|||If the network map is \\servername\share it can be a WINS Issue.
You might try \\servername.domain.com\share and see if that fixes the problem.
Tim S
|||Hi,
You seem to be running into the issue described in the Microsoft Knowledge
Base Article No 293403. Please go through the following link to review the
article.
http://support.microsoft.com/?kbid=293403
Hope this resolve the issue. Please keep me updated on the status.
Thanks
Vijay

"General network error. Check your network documentation." After Detach

Hello.
In our application we have to detach a database using a call from our
C# application. The problem is that after that we get random "General
Network Error" messages afterwards. This is all in a local call, both
the application server and the SqlServer are on the same machine.
I read about the Pooling = False switch but this is not an option for
us because this could have major repercusions on the rest of our
application.
Does anyone know how to get rid of this error without using the Pooling
= False?
Using .NET 1.1 and SqlServer 2000
ThanksAre you saying that you are killing database connections before the detach
and that causes the issues with your pooled connections? Is the detached
database specified as the 'Initial Catalog' specification in your connection
string?
If either or both are the case, I suggest you specify a different database
as the 'Initial Catalog' and change the database context to a different
database before closing the connection. That way, the polled connection can
remain open for reuse after the detach.
--
Hope this helps.
Dan Guzman
SQL Server MVP
<escristian@.hotmail.com> wrote in message
news:1148589276.174672.171190@.y43g2000cwc.googlegroups.com...
> Hello.
> In our application we have to detach a database using a call from our
> C# application. The problem is that after that we get random "General
> Network Error" messages afterwards. This is all in a local call, both
> the application server and the SqlServer are on the same machine.
> I read about the Pooling = False switch but this is not an option for
> us because this could have major repercusions on the rest of our
> application.
> Does anyone know how to get rid of this error without using the Pooling
> = False?
> Using .NET 1.1 and SqlServer 2000
> Thanks
>|||The architecture I'm working with basically creates a new SqlConnection
everytime we make a call to the SqlService object (only way to access
database). To detach the database I put the database to offline mode
and then detach, here's the sql syntax I use:
USE master ALTER DATABASE <<dbName>> SET OFFLINE WITH ROLLBACK
IMMEDIATE
USE master EXEC sp_detach_db '<<dbName>>', 'true'
So our architecture will create a new connection before the 1st line of
sql, destroy that connection and then create another connection before
the 2nd call.
I will start reading on the connection pooling cause that seems to be
the cause of all these problems.
Thanks for your help|||Have you tried changing the database context to another database (e.g.
master) before closing the connection as I previously suggested? That way,
pooled connections won't be killed when you execute the ALTER
DATABASE...ROLLBACK.
--
Hope this helps.
Dan Guzman
SQL Server MVP
<escristian@.hotmail.com> wrote in message
news:1148654269.887685.237720@.i39g2000cwa.googlegroups.com...
> The architecture I'm working with basically creates a new SqlConnection
> everytime we make a call to the SqlService object (only way to access
> database). To detach the database I put the database to offline mode
> and then detach, here's the sql syntax I use:
> USE master ALTER DATABASE <<dbName>> SET OFFLINE WITH ROLLBACK
> IMMEDIATE
> USE master EXEC sp_detach_db '<<dbName>>', 'true'
> So our architecture will create a new connection before the 1st line of
> sql, destroy that connection and then create another connection before
> the 2nd call.
> I will start reading on the connection pooling cause that seems to be
> the cause of all these problems.
> Thanks for your help
>

"General network error. Check your network documentation." After Detach

Hello.
In our application we have to detach a database using a call from our
C# application. The problem is that after that we get random "General
Network Error" messages afterwards. This is all in a local call, both
the application server and the SqlServer are on the same machine.
I read about the Pooling = False switch but this is not an option for
us because this could have major repercusions on the rest of our
application.
Does anyone know how to get rid of this error without using the Pooling
= False?
Using .NET 1.1 and SqlServer 2000
ThanksAre you saying that you are killing database connections before the detach
and that causes the issues with your pooled connections? Is the detached
database specified as the 'Initial Catalog' specification in your connection
string?
If either or both are the case, I suggest you specify a different database
as the 'Initial Catalog' and change the database context to a different
database before closing the connection. That way, the polled connection can
remain open for reuse after the detach.
Hope this helps.
Dan Guzman
SQL Server MVP
<escristian@.hotmail.com> wrote in message
news:1148589276.174672.171190@.y43g2000cwc.googlegroups.com...
> Hello.
> In our application we have to detach a database using a call from our
> C# application. The problem is that after that we get random "General
> Network Error" messages afterwards. This is all in a local call, both
> the application server and the SqlServer are on the same machine.
> I read about the Pooling = False switch but this is not an option for
> us because this could have major repercusions on the rest of our
> application.
> Does anyone know how to get rid of this error without using the Pooling
> = False?
> Using .NET 1.1 and SqlServer 2000
> Thanks
>

"General network error. Check your network documentation."

I try to make a replication on my SQL Server2000 SP3 on Windows2000. I want to replicate 8 tables from Server1 to Server2. I found that 6 tables is work fine, however only 2 table that have an error that show below. How can I correct it?

The process could not deliver the snapshot to the Subscriber.

The process could not deliver the snapshot to the Subscriber.
(Source: Merge Replication Provider (Agent); Error number: -2147201001)
----------------------------------
The process could not bulk copy into table '"dbo"."Table1"'.
(Source: Server2 (Agent); Error number: 20037)
----------------------------------
General network error. Check your network documentation.
(Source: Server2 (Data source); Error number: 11)
----------------------------------Ok for the latest time I post my problem is only happen on Table1 but on Table2 is has something difference.

On Table1:
The process could not deliver the snapshot to the Subscriber.

The process could not deliver the snapshot to the Subscriber.
(Source: Merge Replication Provider (Agent); Error number: -2147201001)
----------------------------------
The process could not bulk copy into table '"dbo"."Table1"'.
(Source: Server2 (Agent); Error number: 20037)
----------------------------------
General network error. Check your network documentation.
(Source: Server2 (Data source); Error number: 11)
----------------------------------

On Table2:
The process could not query row metadata at the 'Subscriber'.

The process could not query row metadata at the 'Subscriber'.
(Source: Merge Replication Provider (Agent); Error number: -2147200996)
----------------------------------
Genetal network error. Check your network documentation.
(Source: Server2 (Data source); Error number: 11)
----------------------------------
The process was successfully stopped.
(Source: Merge Replication Provider (Agent); Error number: -2147199469)

"Data Source=localhost;..." fails with : General network error.

I replaced SQL 2000 with SQL 2005 Developer edition and my application could
not connect
to the local SQL server anymore. When connecting from a .Net 1.1 application
using the
following connection string:
"Data Source=localhost;Database=MM;Integrated Security=SSPI"
I always received the following exception message:
"General network error. Check your network documentation."
I had no problem to connect when using the host name instead of "localhost".
The problem
got resolved when I started "SQL Server Surface Area Configuration" and conf
igured it as
follow:
Surface Area Configuration for Services and Connections -> Database Engine -
> Remote
Connections -> Local and remote connections -> Using TCP/IP only.
The SQL 2005 Developer Edition is configured out of the box with "Local conn
ections only"
and "localhost" for some reason is not recognized as a local connection !!!!Try . or (local) or servername or IP address.
"Gaetan" <someone@.somewhere.com> wrote in message
news:14fhn1dr367kni9qt8vp7j5rb70imtelhl@.
4ax.com...
>I replaced SQL 2000 with SQL 2005 Developer edition and my application
>could not connect
> to the local SQL server anymore. When connecting from a .Net 1.1
> application using the
> following connection string:
> "Data Source=localhost;Database=MM;Integrated Security=SSPI"
> I always received the following exception message:
> "General network error. Check your network documentation."
> I had no problem to connect when using the host name instead of
> "localhost". The problem
> got resolved when I started "SQL Server Surface Area Configuration" and
> configured it as
> follow:
> Surface Area Configuration for Services and Connections -> Database
> Engine -> Remote
> Connections -> Local and remote connections -> Using TCP/IP only.
> The SQL 2005 Developer Edition is configured out of the box with "Local
> connections only"
> and "localhost" for some reason is not recognized as a local connection
> !!!!
>

please help System.Data.SqlClient.SqlClientPermission problem

im getting this error when i try to access the application from the network. but in my computer work fine

Request for the permission of type 'System.Data.SqlClient.SqlClientPermission, System.Data, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089' failed.

please help... thanxs

When the asp.net application is deployed onto the webserver the asp.net worker process may be using the context of an account that does not have permissions to the database.

Please check the directory security tab for your website/virtual directory in IIS.

|||

the security tab if the iis is the for anonimous access...

|||

royrfc:

the security tab if the iis is the for anonimous access...

You need to make sure the account specified for anonymous access has permissions to access your database

|||

already add IUSR_ and ASPNET user to the database and nothing.

the application is an windows control library created by me in vs2005 , added to the aspx page

|||

royrfc:

the application is an windows control library created by me in vs2005 , added to the aspx page

So it is the .NET applet trying to access the database. You may need to give it the permissions by using CAS or declaratively I think.

I am not that knowledgable in this area so have a read of these articles, they may help

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

http://msdn2.microsoft.com/en-us/library/Aa302424.aspx

|||

need help with that...

try some forums explaining CAS, but no luck at all

need help