Re: Difficulty logging on to server

On Nov 12, 2:36 pm, "Claus" <cjo...@xxxxxxxxxxxxx> wrote:
Yup, I know, that is an issue. I had never had to deal with it. If I find
something I will post back.

--
Claus"Byteguy" <Byte...@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message

news:8B90815F-766B-476A-8823-67872FE7895E@xxxxxxxxxxxxxxxx

Apparently, as you mention, there are issues with Outlook 2003 and Win
2003
SBS. I understand that even if I uninstall Outlook, the "damage" has been
done and we will probably have to attempt a repair.

I've been looking for the "fix" for this situation, short of doing a
repair.
Do you have any knowledge of this?

"Claus" wrote:

With the free disk space you reported it is very unlikely that cache
files
or log files are the reason for this. If it happens after only 30
minutes,
watching the system as I suggested in my earlier answer seems to me the
best
approach. The Office programs should definitely get uninstalled.
Especially
Outlook is not supported at all.

As to the AntiVirus, TrendMicro CSM (current version is 3.6) is a well
tested good solution for an SBS setup that takes also care of the
Exchange
server.

--
Claus
"Byteguy" <Byte...@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:4F834AE2-B7F0-4A80-9D30-B93E975FC521@xxxxxxxxxxxxxxxx
I'll advise the client to remove Office. I'm not sure if the
accounting
software is running anything at startup. If it does, it really
shouldn't
be
an issue, as the company that supports it tells us that the software
only
runs on a server, and this is why the machine was built.
Anti-virus is Trend Internet Security.

The thing that really is strange is the server allowing any user to log
in
for a while and then suddenly rejecting all logins. Might help if I
try
logins one at a time until it locks me out. At least I'll be able to
tell
if
I can replicate the problem.

My client had no problems just logging in to the console. It was when
we
started coming in with remote desktop that the strange behavior
started.

I would need to review the event logs (can't right now as I don't
remember
the IP), but I will when I return to the office.

It's almost as though there is a cache gradually filling as folks log
in,
and it suddenly gets full.

Thanks
Art

"Claus" wrote:

Office should not be installed on the server. I'm also pretty sure
that
your
business software runs some services in the background.
And what about AntiVirus software, backup software etc?
If you want to see what consumes your resources, open the Task Manager
and
watch the processes. I would also add the Thread count to the view.

--
Claus
"Byteguy" <Byte...@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:DA03FA3A-DF44-489B-81CA-5903EA0E2DDF@xxxxxxxxxxxxxxxx
At startup, there are no third party progs running. There is a
"high-powered" accounting-business software (MAS 90 ERP) that is
accessed
on
the server, but it does not run until it is started by a user. Only
other
progs installed: Office 2003.
The system is new, 160 GB RAID with maybe 140GB free, 2 GB RAM.

"Claus" wrote:

Sounds more like a memory leak. What 3rd party software is
installed?
How
big is the system drive and how much free space does it have?
Have you tried a "clean reboot" (disabling all non-ms programs)?
Does
the
error show up?
You could also watch the memory usage and thread count while the
system
is
running to see if there are any suspicious processes running.

--
Claus
"Byteguy" <Byte...@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:3C08AE11-4BAB-4751-B806-418DC648D2F3@xxxxxxxxxxxxxxxx
In Win 2003 SBS--we can log onto the system in console or using
remote
desktop. At least we can for a while. At some point--we can no
longer
log
on either way.
It wasn't until I visited the server that I saw the error
message.
It
was:

System cannot log in due to the following error:
Not enough storage is available to process this command

Rebooting the server solves the problem for a while, and then it
just
seems
The problem has been identified! Winlogon is leaking memory--really
fast. Starts when a remote user logs on and stops when they log off.
The only reason a remote user can stay on for a while is the fact that
we have 2GB of memory. But then that runs out and we have to reboot.

Can't seem to find out why this is happening

Art

to start all over again. I can't replicate it except I know it
will
happen
within maybe 30 minutes or so.

Last time I cleaned all the temp files and the problem took a
little
longer
to manifest itself. I'm thinking somehow it is not clearing a
cache
or
something.

Art


.