Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Causes SQL connection errors? #32

Closed
davidpricedev opened this issue Apr 7, 2015 · 3 comments
Closed

Causes SQL connection errors? #32

davidpricedev opened this issue Apr 7, 2015 · 3 comments

Comments

@davidpricedev
Copy link

Causes SQL connection errors. When I install this extension, VS2013 constantly locks up and after a bit it will show an error message: "A netowrk-related or instance-specific error occurred while establishing a connection to SQL Server. ...". I can click OK to make that message go away, but VS will lock up again immediately and be locked until it throws that error message again (repeated until I kill VS with Task Manager). I uninstalled this extension and the issue went away. So it is definitely something this extension is doing.

In the background while VS was locked up, I noticed that this plugin did work - it found my tests and ran them. I'm excited about getting this into our process.

Any idea what I'm doing wrong?

@MortenHoustonLudvigsen
Copy link
Owner

I am honestly baffled by ths issue. I am quite sure, that the adapter does not try to connect to an SQL server anywhere in the code. Could you be using another extension, that does connect to an SQL server, and somehow conflcts with the adapter?
I would be interested in seeing your log file (you should be able to find one here: %LocalAppData%/2PS/KarmaTestAdapter/KarmaTestAdapter.log).

@davidpricedev
Copy link
Author

I don't see much in the log that would indicate any issues. I did another test, my first attempt was with an asp.net forms project together with a front-end project. I tried opening the front-end project on its own and re-installed the plugin and everything worked fine. So whatever is causing the problem must be only with the asp.net forms application. I tried with a blank new asp.net forms app and the problem did not recur. So the issue is some interaction with that particular forms app. I'm thinking this is probably not something you can solve.

I've tried a bunch of other things and things seem to be working now. There has to be something strange going on with the VS user settings on the project or solution that was causing this - or maybe some temporary files created to help facilitate testing - since it was also tied at least partially to when the test explorer window was open.

Sorry to bother you with an non-relevant issue. Thanks for the quick response!

Here are the other extensions I have installed:

  • CodeMaid
  • Grunt Launcher
  • Open Command Line
  • Package Intellisense
  • Productivity Power tools
  • Shared Project Reference Manager
  • Task Runner Explorer
  • Web Essentials
  • (and a bunch of others that come from Microsoft and are probably in every install of VS)

Here is the log file:

[07.04.2015 11:25:50.365] [Karma] [Debug] TestContainerDiscoverer created
[07.04.2015 11:27:02.149] [Karma] [Debug] [DSpa] Creating TestContainer for karma.conf.js
[07.04.2015 11:27:02.162] [Karma] [Debug] [DSpa] Watching KarmaTestAdapter.json
[07.04.2015 11:27:02.165] [Karma] [Debug] [DSpa] Watching karma.conf.js
[07.04.2015 11:27:03.041] [Karma] [Debug] [DSpa] [Server] Starting Karma: "C:\Program Files\nodejs\node.exe" C:\USERS\DAVID\APPDATA\LOCAL\MICROSOFT\VISUALSTUDIO\12.0\EXTENSIONS\QZWFZFD2.CWN\KarmaTestServer\Start.js --name DSpa --karma karma.conf.js
[07.04.2015 11:27:03.043] [Karma] [Debug] [DSpa] TestContainer created
[07.04.2015 11:27:03.500] [Karma] [Debug] [DSpa] INFO [karma]: starting karma server
[07.04.2015 11:27:04.211] [Karma] [Debug] [DSpa] INFO [VS Reporter]: Created
[07.04.2015 11:27:04.220] [Karma] [Debug] [DSpa] INFO [VS Jasmine]: Ready
[07.04.2015 11:27:04.228] [Karma] [Debug] [DSpa] Karma started using port 61062
[07.04.2015 11:27:04.613] [Karma] [Debug] [DSpa] INFO [VS Server]: Started - port: 61062
[07.04.2015 11:27:04.616] [Karma] [Debug] [DSpa] INFO [karma]: Karma v0.12.31 server started at http://localhost:61061/
[07.04.2015 11:27:04.619] [Karma] [Debug] [DSpa] INFO [launcher]: Starting browser Chrome
[07.04.2015 11:27:04.625] [Karma] [Warning] [DSpa] WARN [watcher]: Pattern "c:/Dev/Framework/Portal/TsSrc/src/3rdParty/*.js" does not match any file.
[07.04.2015 11:27:04.869] [Karma] [Debug] Refreshing containers: Karma started for DSpa
[07.04.2015 11:27:05.206] [Karma] [Debug] [DSpa] [Discover] Start
[07.04.2015 11:27:06.143] [Karma] [Debug] [DSpa] DEBUG [karma]: A browser has connected on socket SobwljRiMdnrukc6tN8p
[07.04.2015 11:27:06.151] [Karma] [Debug] [DSpa] INFO [Chrome 41.0.2272 (Windows 7)]: Connected on socket SobwljRiMdnrukc6tN8p with id 66552397
[07.04.2015 11:27:06.155] [Karma] [Debug] [DSpa] DEBUG [karma]: All browsers are ready, executing
[07.04.2015 11:27:06.158] [Karma] [Debug] [DSpa] INFO [VS Server]: Test run start
[07.04.2015 11:27:06.404] [Karma] [Debug] Refreshing containers: Test run started for DSpa
[07.04.2015 11:27:06.808] [Karma] [Debug] [DSpa] INFO [VS Server]: Test run complete
[07.04.2015 11:27:06.898] [Karma] [Debug] [DSpa] [Discover] Complete: 3 tests
[07.04.2015 11:27:06.901] [Karma] [Discover] 3 tests discovered in 1 test containers
[07.04.2015 11:28:15.650] [Karma] [Debug] [DSpa] [Discover] Start
[07.04.2015 11:28:15.656] [Karma] [Debug] [DSpa] [Discover] Complete: 3 tests
[07.04.2015 11:28:15.658] [Karma] [Discover] 3 tests discovered in 1 test containers
[07.04.2015 11:28:16.110] [Karma] [Debug] [DSpa] [Run] Start
[07.04.2015 11:28:16.374] [Karma] [Debug] [DSpa] [Run] Complete: 3 tests
[07.04.2015 11:28:16.376] [Karma] [Run] 3 tests run in 1 test containers

@MortenHoustonLudvigsen
Copy link
Owner

@davidpricedev
I'm just glad you got it working!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants