Visual C# 2005 Express Beta 2 Debugger Fails to Start

Visual C# 2005 Express Beta 2 Debugger Fails to Start

• smarlowe

  1. The instance name is MSSQL$SQLEXPRESS
  2. I only have one instance of SQL on my box
  3. The error log contains the following lines:
  
  2005-04-19 07:53:16.65 Logon       Error: 17830, Severity: 20, State: 2.
  2005-04-19 07:53:16.65 Logon       A network error occurred while establishing a connection; the connection has been closed. This may have been caused by client or server login timeout expiration. Time spent during login: total 410 ms, enqueued 1 ms, network writes 1 ms, network reads 351 ms, establishing SSL 339 ms, negotiating SSPI 0 ms, validating login 0 ms. [CLIENT: <local machine>]
  2005-04-19 07:53:42.82 Server      Using 'dbghelp.dll' version '4.0.5'
  2005-04-19 07:53:42.92 Server      ***Unable to get thread context - no pss
  2005-04-19 07:53:42.92 Server      Stack Signature for the dump is 0x00000000
  2005-04-19 07:53:44.35 Server      External dump process return code 0x20000001.
  External dump process returned no errors.

  2005-04-19 07:53:44.37 Server      Process 51:0:0 (0xa80) Worker 0x02FEA0D8 appears to be non-yielding on Scheduler 0. Thread creation time: 0. Approx Thread CPU Used: kernel 0 ms, user 0 ms. Process Utilization 0%. Interval: 20015 ms.
  2005-04-19 07:53:49.37 Server      Process 51:0:0 (0xa80) Worker 0x02FEA0D8 appears to be non-yielding on Scheduler 0. Thread creation time: 0. Approx Thread CPU Used: kernel 0 ms, user 0 ms. Process Utilization 0%. Interval: 26781 ms.
  2005-04-19 07:53:54.37 Server      Process 51:0:0 (0xa80) Worker 0x02FEA0D8 appears to be non-yielding on Scheduler 0. Thread creation time: 0. Approx Thread CPU Used: kernel 0 ms, user 0 ms. Process Utilization 0%. Interval: 31781 ms.
  2005-04-19 07:53:59.37 Server      Process 51:0:0 (0xa80) Worker 0x02FEA0D8 appears to be non-yielding on Scheduler 0. Thread creation time: 0. Approx Thread CPU Used: kernel 0 ms, user 0 ms. Process Utilization 0%. Interval: 36781 ms.
  2005-04-19 07:54:04.37 Server      Process 51:0:0 (0xa80) Worker 0x02FEA0D8 appears to be non-yielding on Scheduler 0. Thread creation time: 0. Approx Thread CPU Used: kernel 0 ms, user 0 ms. Process Utilization 0%. Interval: 41781 ms.
  2005-04-19 07:54:09.37 Server      Process 51:0:0 (0xa80) Worker 0x02FEA0D8 appears to be non-yielding on Scheduler 0. Thread creation time: 0. Approx Thread CPU Used: kernel 0 ms, user 0 ms. Process Utilization 0%. Interval: 46781 ms.
  2005-04-19 07:54:14.37 Server      Process 51:0:0 (0xa80) Worker 0x02FEA0D8 appears to be non-yielding on Scheduler 0. Thread creation time: 0. Approx Thread CPU Used: kernel 0 ms, user 0 ms. Process Utilization 0%. Interval: 51781 ms.
  2005-04-19 07:54:17.06 Logon       Error: 15372, Severity: 16, State: 1.
  2005-04-19 07:54:17.06 Logon       Failed to generate a user instance of SQL Server due to a failure in starting the process for the user instance. The connection will be closed. [CLIENT: <local machine>]
  2005-04-19 07:54:17.07 Logon       Error: 17830, Severity: 20, State: 1.
  2005-04-19 07:54:17.07 Logon       A network error occurred while establishing a connection; the connection has been closed. This may have been caused by client or server login timeout expiration. Time spent during login: total 60584 ms, enqueued 16 ms, network writes 1 ms, network reads 100 ms, establishing SSL 100 ms, negotiating SSPI 42 ms, validating login 60407 ms. [CLIENT: <local machine>]
  
  Thanks
  
  Donald

  
  

• Brian The Gaffer

  I had that problem with the Febuarty CTP build.  The solution was to delete the following:
  
  C:\Documents and Settings\<your user name>\Application data\Microsoft\VCSExpress directory.
  
  C:\Documents and Settings\<your user name>\Local Settings\Application data\Microsoft\VCSExpress directory.
  
  and finally delete the registry key:
  HKCU\Software\Microsoft\VCSExpress
  
  Make sure you only delete the directories from under your user name (not the ones under All Users)  and that you are in the the H-Key Current User hive in the registry.  If you delete the keys under HKey Local Machine, you'll have to re-install VC#.   I'd delete the directories first, then check to see if that fixed the problem.   If not, delete the directories again (they'll have been rebuilt), and delete the registry key.  You'll most likely lose your settings in the IDE, but your projects will be unaffected.  
  
  Hope this helps,
  Ben
  
  

• mindplayr

  Thanks Ben,
  
  This solved my problem with both the debugger and SQL Express!
  
  Donald
  

• Pardha Saradhi K

  Does this behave any differently if you add code / controls before launching the app for debugging
  
  Also, did you have any previous VS 2005 / C# or SQL 2005 builds installed before installing beta 2
  
  -Bret Grinslade
  VS / .NET Framework Setup Team
  

• Joeman345

  It does not matter if I add code, the debugger stills fails. 
  
  I had Visual C# 2005 Express Beta 1 Feb CTP previously installed along with the SQL Express version that was installed with it.  I followed the uninstall instructions before installing beta 2.
  
  I checked Windows Event log and whenever the debugger fails, I get the following error messages in the log:
  
  Source: Microsoft Visual C# Express:

  Faulting application vcsexpress.exe, version 8.0.50215.44, stamp 42577231, faulting module msenv.dll, version 8.0.50215.44, stamp 42578832, debug 0, fault address 0x0010348b.
  
  Source: .NET  Runtime
  

  NET Runtime version 2.0.50215.44 - Fatal Execution Engine Error (79B075CD) (0)
  
  I'm thinking about uninstalling everything and reinstalling beta 2 too see if that will make a difference.
  
  
  Thanks,
  
  Donald

  
  

• flwid

  1. What is the insance name when you can access db via command line Is it MSSQL$SQLEXPRESS
  2. Do you have multiple insance SQL on your box
  3. What does the latest ERRORLOG at C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\ERRORLOG (This path may be different depending on your box) say
  
  Hong Gao

  
  
  
• Visual C# 2005 Express Beta 2 Debugger Fails to Start