PRB: Visual Studio .NET Stops Responding and You Receive a SQL Server Login Dialog Box When You Run an Application (817179)
The information in this article applies to:
- Microsoft Visual Studio .NET (2003), Professional Edition
- Microsoft Visual Studio .NET (2003), Enterprise Architect Edition
- Microsoft Visual Studio .NET (2003), Enterprise Developer Edition
- Microsoft Visual Studio .NET (2003), Academic Edition
SYMPTOMSMicrosoft Visual Studio .NET 2003 stops responding for about 30 seconds when you run an application, and you
receive a SQL Server Login dialog box that prompts you for a
password. If you type the appropriate password and then click
OK, Visual Studio .NET stops responding for about 30 seconds,
and then you receive the following SQL Server Login error message: Connection failed: SQLState: '08001' SQL Server Error:
17 [DBNETLIB][ConnectionOpen (Connect()).]SQL Server does not exist or
access denied. You can click OK in the
SQL Server Login error dialog box and then click
Cancel in the SQL Server Login dialog box.
If you do this, you receive the following Microsoft Development Environment error
message: Operation was canceled. If you click
OK in response to this message, your application runs. Note This issue does not occur in Visual Studio .NET
2002. CAUSEIn Visual Studio .NET, you can set a breakpoint on a stored
procedure that is in a Microsoft SQL Server database. When you do this, the breakpoint is associated with your current project. You can
subsequently stop SQL Server, and then start your project. When you start this
project, the Visual Studio .NET debugger tries to obtain the updated
information about the locations of all breakpoints that are associated with the
project. To obtain this updated information, the Visual Studio .NET debugger
calls Server Explorer. Server Explorer then tries to establish a connection to
SQL Server.
When
Server Explorer tries to establish a connection to SQL Server, Visual Studio
.NET stops responding. This behavior occurs because SQL Server is not currently running. After approximately 30 seconds, you receive the SQL Server Login dialog box that is described in the "Symptoms" section. This 30-second time-out period corresponds to the time-out period for the Server Explorer operation that tries
to establish a connection to SQL Server. If you type the appropriate password
and then click OK, Visual Studio .NET again stops responding
for about 30 seconds. This time-out period also corresponds to the Server Explorer time-out period. You then receive the Microsoft SQL Server Login error
message that is described in the "Symptoms" section.RESOLUTIONTo resolve this problem, remove unnecessary database
connections from Server Explorer. To
do this, follow these steps:
- Quit your application.
- In Server Explorer, right-click any unnecessary database
connections, and then click Delete.
- In the Server Explorer dialog box that appears, click
Yes.
- Quit Visual Studio .NET.
- Start Visual Studio .NET.
- Start your application.
- On the Debug menu, click
Start to run your application. You do not notice the behavior
that is described in the "Symptoms" section, and your application runs as you expect.
STATUS This
behavior is by design.REFERENCESFor more information about debugging, visit the following
Microsoft Developer Network (MSDN) Web site: For more information about Server Explorer, visit the following
Microsoft Developer Network (MSDN) Web site:
Modification Type: | Minor | Last Reviewed: | 10/14/2003 |
---|
Keywords: | kbServer kbide kbDataPooling kbMiscTools kbStoredProc kbDebug kbTSQL kbprb KB817179 kbAudDeveloper |
---|
|