Printable View
Does anyone else develop asp.net on Windows 2K pro get this error? I get it a lot when I are rebuilding my project. If I am testing my app I can usually just refresh the page, and it will come back, but when I use things like phpMyAdmin to manage my mySQL database, I get this error there too, but cannot get rid of it unless I restart IIS.
IIS installed with Win2K has a hardcoded limit of 10 connections - it's a developer licence I'm afraid
No, I get that, but I am the only one doing anything on it. I have 2 things running, my .net application and phpMyAdmin, but I get this error a lot and have to restart IIS. There should be no more than 2 connections at any one time.Quote:
Originally posted by axion_sa
IIS installed with Win2K has a hardcoded limit of 10 connections - it's a developer licence I'm afraid
Hmmm - what's your default connection timeout? In IIS - right click on Default Web Site & properties, under the Web Site tab
900 seconds
I really should read questions thoroughly more often :rolleyes: How does phpMyAdmin work? Does it run through IIS?
hehe... yeah, it is a web based management tool for mySQL databases and yes it runs in IIS.
Google has nothing to say about phpMyAdmin persisting connections. Um - would you be amenable to using another DB manager? Coz that's all I can think of :/
I know it is not phpMyAdmin that is causing the trouble, it just the one feeling the pain :) There is a stand alone mySQL manager, but I hate it. phpMyAdmin does it all. I just wondered why either Visual Studio .Net or the framework was using up all my connections.