I have a simple C# Windows Forms application I'm trying to create. on Form1_Load I query my database with a simple request to fill a DataGridView.
If I debug the application, the query executes immediately without issue.
If I "Start without debugging," the connection to the database times out every time with SqlException: Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.
This is affecting multiple different projects which used to work flawlessly before today, so I'm pretty certain it's an issue with Visual Studio and not my code. Here's hoping someone knows what could be causing this.
After a fresh install of VS2008 on a new machine, I'm still experiencing the issue. I was able to run the project without debugging, and the first time connecting to the database worked fine, but now it always fails as described above. Possibly some kind of weird connection pool issue in VS?
Check your antivirus software.
My antivirus was flagging every new application I tried to run without debugging, but I had alerts for my antivirus turned off so I had no idea.
I turned on alerts and suddenly when I ran my app I got a notice from my antivirus. I just allowed it permanently and now everything runs smoothly.
Related
I have a Clickonce app from Visual Studio 2015 SP3 that is published to the network server and used in-house only. The program works just fine when launched from Visual Studio. It runs just fine on a Windows machine that does not have the 1803 update. But once a machine updates to 1803, the application no longer starts. I get the "Checking for updates..." window then nothing. On a fresh install, I usually get the Smartscreen telling me the program may be dangerous. It doesn't get that far.
I've created the Clickonce from a computer with the 1803 update and the problem still exists.
I've disconnected the machine from the network. The application starts but then has no database access and it needs the database. It's also written to hide buttons that would use the database to prevent users from trying to do things that require it.
I found a workaround (third paragraph) at https://social.technet.microsoft.com/Forums/en-US/7cbd16f5-526e-4b0b-a186-3ebf41b7b349/smartscreen-prompt-does-not-show-for-clickonce-app-since-windows-10-update-1803?forum=win10itprogeneral. When I start the application from the directory mentioned, I get the Smartscreen and can tell it to run anyway. Every time I click the desktop icon, it works just fine.
If a new release is published, the new release is downloaded and the program updated, but the Smartscreen no longer appears and the application never starts.
So somewhere between installing the latest update and the Smartscreen, this is failing. Anyone else experiencing this and have an idea as to why?
Yes, frustratingly I also experienced this today. Presumably a security update that they'll release another patch for given this is quite a pain for developers and users of small business apps.
Rather than disable Defender or SmartScreen I chose to add my deployment website to the Trusted Sites in Internet Explorer and that then re-instated the warning dialog and my app updated and ran as before.
Really annoying given the nature of the issue and how long it took to figure out, but at the same time I had to use IE today, which is a rare event nowadays.
This works for me...Warn doesnt warn anymore...
After running in the same problem, I just found that my application was going to halt after a stupid uncaught exception.
Despite the fact that the image below is in Portuguese, Event Viewer shows the right error cause.
In my case, was a corrupted settings file!
It appears as though some subsequent Windows Updates have fixed the issue on several of our PC's that were previously experiencing the issue.
Check for the updates listed here.
https://www.catalog.update.microsoft.com/Search.aspx?q=KB4338548
Running winver.exe will show you which build you have.
I'm having a bit of problem debugging in VS for our web application, basically all requests are painfully slow, requests that used to take <1s are taking over 15s which as you can imagine makes developing a nightmare!
This is on my newly installed laptop (done it twice recently and the problem is the same both times on both laptops).
I've tried the following without success:
Run without debugging (ctrl+F5)
Run in release mode
Disable diagnostics panel in VS
Disable unused debugging options in VS
Different browsers (Chrome, FF, Edge)
Disable Antivirus
Disable ReSharper/Uninstalled
The solution is a mix of WebForms, MVC, WebAPI, Classic ASP with standard SQL connections (calling stored procs) and Entity Framework.
I have also tried Visual Studio 2017 and I'm getting the same issue there too.
Does anyone have any idea what could be causing it? I've googled and tried several things people have suggested without any success.
It turns out that the issue was down to have the Data Source value of the connection string set to (local), where as on my old laptop I know that in some instances this was set to the computer name.
I'm not sure which connection string was a fault as we have several in a fair few config files (about 20 connection strings in total) and I just changed them all.
However I'm still unsure why there is a noticeable difference in using computer name and (local) in this situation.
Has anyone seen the issue when debugging an Asp.Net 5 (core) application where the application seems to just go to sleep. Selecting another function/page in the browser just says "Waiting for LocalHost" (as I am running it locally on IIS Express).
We have a staged version of the Asp.Net app and it has no such problem. It runs wonderfully, but in Debug mode, it can have serious delay issues in executing code. Nothing is reported in the output window, during the time it appears to be doing nothing. Nothing on the Diagnostic tools windows either
A lot of the time - it will ultimately come back if you let it do its thing. But sometimes it can take up to 15-30 seconds.
The issue seems to become more prevalent when you change the Razor or javascript client files while the app is running?
Soemtimes pressing F5 on the web page makes it get out of its sleep mode (but not always, and it seems the more times you do this it, the slower it gets). Is it perhaps rebuilding the page that changed? but why the delay?
Again this works fine in Staging or Production (as none of the back end client side files would be changing). But it can be very annoying
Any ideas?
For me it was my Anti Virus. As soon as I disable AVG all requests get immediately run by the debugger.
So I found I didn't have the web tool extensions even installed - and after I installed it - the Freeze disappeared, but a colleague of mine still has the problem (as he already had the extension loaded and there is no way to uninstall it once its loaded
i was trying to change the table's width in IDE and then saving and refreshing my localhost version of the application. it was working fine but suddenly i found that whenever i made any changes to my design the IDE gets hang and it says not responding and it takes quite much time to resume. after several time of this happening and restarting IDE and computer, i still got the same problem and when i closed the not responding IDE by force then in view error detail i found that APPHangB1 is causing problem, it says something like this "program is unable to communicate with windows due to AppHangB1 ". what is teh problem kindly tell? shall i reinstall my VS 2010. i have stuck in the middle and have to complete my application fast. kindly suggest solutions if u faced any. i m in hurry
I have a strange issue. Have a windows service running on Windows Server 2008 that receives files over TCP and saves to disk. Initially service was running as Local System account. It worked ok for 7 days and stopped receiving. From the sender side connection succeeds but send fails. The service blocks forever on receive and connection times out.
I changed the user account to "Network Service" and it started working again for 7 days and stopped. I then changed it to run as administrator. It ran for 4 days and stopped again. Now whatever I try it does not work. Rebuilt the code re-installed the service but same issue.
Does anybody ever face such an issue? is it a virus or something? Is windows blocking it? any suggestions will be greatly appreciated.
Note: If I run it as a windows form application it just works fine. Also disabled the firewall but it did not help. While debugging the code I never see any issues. Because it works as a forms app and also worked perfectly as a service for 15-20 days now.
I figured out the problem. When the issue started happening I ran the Filemon utility and figured that the service was failing to access a temp file created using GetTempFileName().
This seems to be a known issue with Windows server 2008R2 and happens randomly.
Here is a solution/Hotfix from Microsoft: http://support.microsoft.com/kb/982613