We have a Win 2k3 SP2 R2 server, Dual 1400 Mhz, 2 gb RAM. It is
hosting right around 200 Lexmark printers. (Its only purpose in
life) Out of the blue, it will hang and nobody can print to it
anymore. When you go to the console or RD to it it is basically
unresponsive. What we have found is in the task manager
"lmabcoms.exe" runs at %99 to %100 usage and is the culprit. A hard
reboot and it is peachy again for a couple of days.

During normal operation, lmabcoms.exe does not take any CPU cycles,
just chugs along in task manager. I am wondering if anyone else has
similar problems using Lexmark printers hosted from a print server.
We are in constant communication with Lexmark about the issue but they
have not been able to solve it yet.

We have rebuilt the server from scratch on several different hardware
platforms and continue to have the same problem.

lmabcoms.exe is the process for the Lexmark Enhanced Port and Lexmark
Network Port, at least thats what Lemark and our researching point
to. We have even had Lemark send us their latest and greatest version
of lmabcoms.exe.

Any ideas?

>We have a Win 2k3 SP2 R2 server, Dual 1400 Mhz, 2 gb RAM. It is
>hosting right around 200 Lexmark printers. (Its only purpose in
>life) Out of the blue, it will hang and nobody can print to it
>anymore. When you go to the console or RD to it it is basically
>unresponsive. What we have found is in the task manager
>"lmabcoms.exe" runs at %99 to %100 usage and is the culprit. A hard
>reboot and it is peachy again for a couple of days.
>
>During normal operation, lmabcoms.exe does not take any CPU cycles,
>just chugs along in task manager. I am wondering if anyone else has
>similar problems using Lexmark printers hosted from a print server.
>We are in constant communication with Lexmark about the issue but they
>have not been able to solve it yet.
>
>We have rebuilt the server from scratch on several different hardware
>platforms and continue to have the same problem.
>
>lmabcoms.exe is the process for the Lexmark Enhanced Port and Lexmark
>Network Port, at least thats what Lemark and our researching point
>to. We have even had Lemark send us their latest and greatest version
>of lmabcoms.exe.
>
>Any ideas?

I have a few for you as I have been dealing with issues like this on
our print server and HP .exe's. Try this first:

1. Right-click each printer and do a Properties.
2. On the Advanced tab, see what the print-processor is set to be.
HP's like to hi-jack the default processor and plug in their own junk
(HPZPP*.exe) If it's anything other than WinPrint, set it WinPrint and
apply the changes. Do this for either your busiest printer(s) or all
printers.

You can also try unchecking the "Enable Advanced Printing Features"
and see if it helps.

I'm guessing that lmabcoms.exe is Lexmark's print processor. I find
that anything that tries to take the place of the Microsoft print
processor usually does a half-assed job and causes these issues or
crashes the spooler service.

Let me know if it helps.

- Thee Chicago Wolf

On May 1, 10:43*am, Thee Chicago Wolf <.@.> wrote:
> >We have a Win 2k3 SP2 R2 server, Dual 1400 Mhz, 2 gb RAM. *It is
> >hosting right around 200 Lexmark printers. *(Its only purpose in
> >life) *Out of the blue, it will hang and nobody can print to it
> >anymore. *When you go to the console or RD to it it is basically
> >unresponsive. *What we have found is in the task manager
> >"lmabcoms.exe" runs at %99 to %100 usage and is the culprit. *A hard
> >reboot and it is peachy again for a couple of days.
>
> >During normal operation, lmabcoms.exe does not take any CPU cycles,
> >just chugs along in task manager. *I am wondering if anyone else has
> >similar problems using Lexmark printers hosted from a print server.
> >We are in constant communication with Lexmark about the issue but they
> >have not been able to solve it yet.
>
> >We have rebuilt the server from scratch on several different hardware
> >platforms and continue to have the same problem.
>
> >lmabcoms.exe is the process for the Lexmark Enhanced Port and Lexmark
> >Network Port, at least thats what Lemark and our researching point
> >to. *We have even had Lemark send us their latest and greatest version
> >of lmabcoms.exe.
>
> >Any ideas?
>
> I have a few for you as I have been dealing with issues like this on
> our print server and HP .exe's. Try this first:
>
> 1. Right-click each printer and do a Properties.
> 2. On the Advanced tab, see what the print-processor is set to be.
> HP's like to hi-jack the default processor and plug in their own junk
> (HPZPP*.exe) If it's anything other than WinPrint, set it WinPrint and
> apply the changes. Do this for either your busiest printer(s) or all
> printers.
>
> You can also try unchecking the "Enable Advanced Printing Features"
> and see if it helps.
>
> I'm guessing that lmabcoms.exe is Lexmark's print processor. I find
> that anything that tries to take the place of the Microsoft print
> processor usually does a half-assed job and causes these issues or
> crashes the spooler service.
>
> Let me know if it helps.
>
> - Thee Chicago Wolf- Hide quoted text -
>
> - Show quoted text -

Good tips! I went out and looked and I did see some printers that
have some of Lemarks junk in place of WinPrint. We will go through
and set all our printers for WinPrint and then see how things go. Our
second course of action will be the Enable Advanced Printing Features.

I will post back in a week or two if the server continues to run (or
doesn't). It usually takes that long before it randomly hangs-up.

Thanks!

Robert

>Good tips! I went out and looked and I did see some printers that
>have some of Lemarks junk in place of WinPrint. We will go through
>and set all our printers for WinPrint and then see how things go. Our
>second course of action will be the Enable Advanced Printing Features.
>
>I will post back in a week or two if the server continues to run (or
>doesn't). It usually takes that long before it randomly hangs-up.
>
>Thanks!

You're welcome. I'm sure others out there besides myself are eager to
hear what happens.

- Thee Chicago Wolf

"robert.curry" wrote:

> On May 1, 10:43 am, Thee Chicago Wolf <.@.> wrote:
> > >We have a Win 2k3 SP2 R2 server, Dual 1400 Mhz, 2 gb RAM. It is
> > >hosting right around 200 Lexmark printers. (Its only purpose in
> > >life) Out of the blue, it will hang and nobody can print to it
> > >anymore. When you go to the console or RD to it it is basically
> > >unresponsive. What we have found is in the task manager
> > >"lmabcoms.exe" runs at %99 to %100 usage and is the culprit. A hard
> > >reboot and it is peachy again for a couple of days.
> >
> > >During normal operation, lmabcoms.exe does not take any CPU cycles,
> > >just chugs along in task manager. I am wondering if anyone else has
> > >similar problems using Lexmark printers hosted from a print server.
> > >We are in constant communication with Lexmark about the issue but they
> > >have not been able to solve it yet.
> >
> > >We have rebuilt the server from scratch on several different hardware
> > >platforms and continue to have the same problem.
> >
> > >lmabcoms.exe is the process for the Lexmark Enhanced Port and Lexmark
> > >Network Port, at least thats what Lemark and our researching point
> > >to. We have even had Lemark send us their latest and greatest version
> > >of lmabcoms.exe.
> >
> > >Any ideas?
> >
> > I have a few for you as I have been dealing with issues like this on
> > our print server and HP .exe's. Try this first:
> >
> > 1. Right-click each printer and do a Properties.
> > 2. On the Advanced tab, see what the print-processor is set to be.
> > HP's like to hi-jack the default processor and plug in their own junk
> > (HPZPP*.exe) If it's anything other than WinPrint, set it WinPrint and
> > apply the changes. Do this for either your busiest printer(s) or all
> > printers.
> >
> > You can also try unchecking the "Enable Advanced Printing Features"
> > and see if it helps.
> >
> > I'm guessing that lmabcoms.exe is Lexmark's print processor. I find
> > that anything that tries to take the place of the Microsoft print
> > processor usually does a half-assed job and causes these issues or
> > crashes the spooler service.
> >
> > Let me know if it helps.
> >
> > - Thee Chicago Wolf- Hide quoted text -
> >
> > - Show quoted text -
>
> Good tips! I went out and looked and I did see some printers that
> have some of Lemarks junk in place of WinPrint. We will go through
> and set all our printers for WinPrint and then see how things go. Our
> second course of action will be the Enable Advanced Printing Features.
>
> I will post back in a week or two if the server continues to run (or
> doesn't). It usually takes that long before it randomly hangs-up.
>
> Thanks!
>
> Robert
>

We have the exact problem here too. But i didn't find any printers with
anything other then winprint in the Print-processor. I didn't try to uncheck
Enable Advanced Printing though, it may be something to try.

So far the server does not hang quite as much. It still has an
occasional hang, but setting all to WINPRINT seemed to help. We are
not sure about unchecking the advanced printing features since most of
our printers are using them for additional add-ons. (paper trays,
duplexers, etc)

>So far the server does not hang quite as much. It still has an
>occasional hang, but setting all to WINPRINT seemed to help. We are
>not sure about unchecking the advanced printing features since most of
>our printers are using them for additional add-ons. (paper trays,
>duplexers, etc)

You may want to investigate some of these hotfixes as they may help
out to further stabilize the print server:

http://support.microsoft.com/kb/934885
http://support.microsoft.com/kb/946198
http://support.microsoft.com/kb/948046
http://support.microsoft.com/kb/937193

Also, check out the info in this article as well:
http://support.microsoft.com/kb/947477

- Thee Chicago Wolf