Thank you for being a valued part of the CNET community. As of December 1, 2020, the forums are in read-only format. In early 2021, CNET Forums will no longer be available. We are grateful for the participation and advice you have provided to one another over the years.

Thanks,

CNET Support

Question

Windows 2000 Terminal Server Logon Problems

Jun 30, 2011 2:16AM PDT

Help! I have a windows 2000 terminal server
that is not allowing very many users to log on at once. They are
getting the error "Could not load profile, please increase registry size
and restart" - If I go into terminal services manager and kick some
people off that have been idle for a while, and reset the sessions I
just disconnected, more users can connect. I have tried everything I
can find online and I still have this issue! What the heck is going on
here? Thanks

Discussion is locked

- Collapse -
Answer
No details?
Jun 30, 2011 9:19AM PDT

How many users?

Is the machine big enough for them?

Do you have the CALS?
Bob

- Collapse -
users
Jun 30, 2011 10:31AM PDT

Right now only about 20-25 users can be logged on concurrently before more users start to receive the registry error message upon attempting to log in.

I have plenty of CALs..... and even as recently as last week I had 40-50 users working on this server concurrently with no issues (well other than the normal w2k issues Silly )

- Collapse -
Again no details.
Jul 1, 2011 2:59AM PDT

As time passes some updates can cause what was a working machine to need more RAM or a change.

The change was noted in the error message yet you didn't tell why you didn't do that.

I know some get stuck on "it worked before" and we have to give those folk more time to work it out.
Bob

- Collapse -
Tried that
Jul 1, 2011 4:15AM PDT

I have increased the registry size, tried all the tricks like adjusting registry elements by hand, etc... Deleted user profiles so that a new one would be created... No luck. I'm working on setting up a 2008 terminal server that I can test my apps on right now.

- Collapse -
Good luck.
Jul 1, 2011 2:45PM PDT

Let me part with a note from the past about the memory setting noted in the error message. I've had to boost that about 10x the default in systems. It was fine in 2000 but even a new browser could swamp that old default.

Working with so few details I don't have much to offer.
Bob

- Collapse -
a year later...
Oct 2, 2012 4:20AM PDT

Bob:
Please excuse an elementry question: On the TS side of things, which log would be best to view evidence of sessions being Terminated, "kicked off", or booted out and reasons for un-expected errors and terminations?
thanx

- Collapse -
None that I know of.
Oct 2, 2012 4:32AM PDT

We have to take into account all the user is reporting, take a look at the Event Viewer and maybe use Process Explorer.

But all this is going to overtax the everyday user. That is, they are usually not ready to dive in or expect tutorials.
Bob

- Collapse -
might even be the cisco in my case
Oct 2, 2012 6:15AM PDT

could be the cisco pix has reached it's lic limit. I have to look into that too. I'll check the logs in there.
thanx Bob