• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Windows 2000 Server issue

Cpt. Duke

Senior member
Hi,

I am wondering if anyone knows a quick fix for this issue. We've been trying to open our MS Access database on this server, but have received this message -

... "No more connections can be made to this remote computer at this time because there are already as many connections as the computer can accept"

This "remote" computer is actually within our office & domain. Any quick suggestions you have? We only have about 20 employees, and I don't think we've exceeded our licenses ...

Greatly appreciated,
Ryan
 
Server can do this to if you leave the license logging service on and then don't enter enough licenses into the licensing console.

Disable the license logging service and see if it fixes it.
 
Good point, but you would have had to enter an incorrect number of licenses for this to be the case; I suppose if this was the case you could also verify by looking in the event log.
 
Thanks for the replies, fellas.
Upon rebooting the machine (not easy to do since it's a production server) the problem has disappeared.
Perhaps it was holding onto 'hung' connections(?)
Peace
 
If it was server, I would have gone to the Licensing Service also. I would have also just checked the number of connections and see how many and who was using up all those connections. You could have also just killed the connections you knew were inactive and just handled it that way. No reboot needed.
 
Originally posted by: 1DJCherny
Thanks for the replies, fellas.
Upon rebooting the machine (not easy to do since it's a production server) the problem has disappeared.
Perhaps it was holding onto 'hung' connections(?)
Peace

You really should troubleshoot this and find the cause of the problem before it happens again. Review the excellent advice in this thread and check it out. Better to know now and fix it before it causes more problems.
 
I just thought of another possible cause:

IF the server was installed from MSDN media, the ten connection limit is hardcoded. (And it's against the license to run a MSDN version of software in production.)

Regrettably, there's no easy way to tell if the server is from MSDN media. Calling MS support might be able to tell you that.
 
Back
Top