RE: Print Spooler Error 14
From: Bill Peng [MSFT] (v-bpeng_at_online.microsoft.com)
Date: 01/27/05
- Next message: Bill Peng [MSFT]: "RE: SBS4.5 to SBS2003 Exchange migration problem"
- Previous message: Jim G: "Install Norton Ghost 9.0 on SBS2K3?"
- In reply to: Mindy: "RE: Print Spooler Error 14"
- Messages sorted by: [ date ] [ thread ]
Date: Thu, 27 Jan 2005 01:54:52 GMT
Hi Mindy,
I understand that it appears the spooler is not able to start. However, I
think the cause of the issue is some other service or application took
large dll usage.
Please take your time to check the root cause and I look forward to your
update.
Have a nice day!
Bill Peng
MCSE 2000, MCDBA
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
=====================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=====================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
--------------------
>Thread-Topic: Print Spooler Error 14
>thread-index: AcUDqwExaOhUb8INQjeMq+8qrq80+w==
>X-WBNR-Posting-Host: 70.57.51.118
>From: "=?Utf-8?B?TWluZHk=?=" <Mindy@discussions.microsoft.com>
>References: <4A081269-7598-4076-88EE-465C39E4BBC6@microsoft.com>
<NK#y762AFHA.764@cpmsftngxa10.phx.gbl>
>Subject: RE: Print Spooler Error 14
>Date: Wed, 26 Jan 2005 05:29:04 -0800
>Lines: 151
>Message-ID: <E6290DB6-93C1-40AF-9B80-2677EC40E517@microsoft.com>
>MIME-Version: 1.0
>Content-Type: text/plain;
> charset="Utf-8"
>Content-Transfer-Encoding: 7bit
>X-Newsreader: Microsoft CDO for Windows 2000
>Content-Class: urn:content-classes:message
>Importance: normal
>Priority: normal
>X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
>Newsgroups: microsoft.public.windows.server.sbs
>NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.1.29
>Path: cpmsftngxa10.phx.gbl!TK2MSFTNGXA03.phx.gbl
>Xref: cpmsftngxa10.phx.gbl microsoft.public.windows.server.sbs:140837
>X-Tomcat-NG: microsoft.public.windows.server.sbs
>
>The actual chain of events is that printing fails from the server
>(unfortunately the client uses it as his desktop and won't listen to
reason).
>I try to restart the Print Spooler service and the error pops up. The
Print
>Spooler service does not start and the only way I have found to start it
is
>to reboot.
>
>I'm sure it is logged in the Event Log as well, I'm not onsite to verify
>that right now.
>
>SQL server should be disabled, but I will verify that fact. It is not in
use.
>
>As soon as I can duplicate the problem, I will check the processes.
>
>Thank you so much,
>Mindy
>
>""Bill Peng [MSFT]"" wrote:
>
>> Hi Mindy,
>>
>> I understand the problem is event 14 appears in Event log and spooler
>> service has no memory to complete the job.
>>
>> If I misunderstood your concern, please don't hesitate to let me know.
>>
>> To narrow down the root cause of the issue, we have to know which
process
>> took high memory usage. To do so:
>>
>> 1. Right-click taskbar and click Task Manager.
>> 2. Click Processes tab.
>> 3. Click Mem Usage to find out which process caused high Memory usage.
>>
>> [Note] The root cause of the issue may be different, sometimes, it is
>> caused by third party startup services or programs. If you found that
that
>> it is caused by third party ones, you can use msconfig tool or
services.msc
>> snap-in to disable appropriate application/service from starting.
>>
>> The following SQL memory issue is one aspect.
>> =============================
>> If you're using SQL Server, I'd like to provide you with the following
info
>> for your reference (it may take high mem usage):
>>
>> SQL Server is designed to use memory. It caches data and query plans to
>> memory so that it will be able to quickly access data. All relational
>> database management systems do this. Unless you are experiencing
problems
>> because of the high memory usage from SQL Server, I would not worry.
>>
>> When you start SQL Server, SQL Server memory usage may continue to
steadily
>> increase and not decrease, even when activity on the server is low.
>> Additionally, the Task Manager and Performance Monitor may show that the
>> physical memory available on the computer is steadily decreasing until
the
>> available memory is between 4 to 10 MB.
>>
>> This behavior alone does not indicate a memory leak. This behavior is
>> normal and is an intended behavior of the SQL Server buffer pool.
>>
>> By default, SQL Server dynamically grows and shrinks the size of its
buffer
>> pool (cache) depending on the physical memory load reported by the
>> operating system. As long as enough memory is available to prevent
paging
>> (between 4 - 10 MB), the SQL Server buffer pool will continue to grow.
As
>> other processes on the same computer as SQL Server allocate memory, the
SQL
>> Server buffer manager will release memory as needed. SQL Server can free
>> and acquire several megabytes of memory each second, allowing it to
quickly
>> adjust to memory allocation changes.
>>
>> For more information, please see the article below:
>>
>> 321363 INF: SQL Server Memory Usage
>> http://support.microsoft.com/?id=321363
>>
>> However, we can use max server memory to prevent SQL Server from using
more
>> that the specified amount of memory (we can also use min server memory
to
>> guarantee a minimum amount of memory to an instance of SQL Server). To
do
>> so, open a command prompt and run the following command:
>>
>> osql -E -S sbsserver\SBSMONITORING
>>
>> You will enter the osql command prompt. Run the commends below (replace
>> <xxx> with the amount of memory):
>>
>> 1> EXEC sp_configure ''show advanced options'', 1
>> 2> reconfigure
>> 3> go
>>
>> 1> EXEC sp_configure ''min server memory'', <xxx>
>> 2> reconfigure
>> 3> go
>>
>> 1> EXEC sp_configure ''max server memory'', <xxx>
>> 2> reconfigure
>> 3> go
>>
>> After doing the above steps, you may run the commands to check the
>> configured memory usage:
>>
>> 1> EXEC sp_configure
>> 2> go
>>
>> I hope the above info helps.
>>
>> If you have any update, please feel free to let me know.
>>
>> Have a nice day!
>>
>> Bill Peng
>> MCSE 2000, MCDBA
>> Microsoft Online Partner Support
>>
>> Get Secure! - www.microsoft.com/security
>> =====================================================
>> When responding to posts, please "Reply to Group" via your newsreader so
>> that others may learn and benefit from your issue.
>> =====================================================
>> This posting is provided "AS IS" with no warranties, and confers no
rights.
>>
>> --------------------
>> >Thread-Topic: Print Spooler Error 14
>> >thread-index: AcUDPy5Bbd8eOwfNS5uLQp+g0CA+fQ==
>> >X-WBNR-Posting-Host: 70.57.51.118
>> >From: "=?Utf-8?B?TWluZHk=?=" <Mindy@discussions.microsoft.com>
>> >Subject: Print Spooler Error 14
>> >Date: Tue, 25 Jan 2005 16:37:14 -0800
>> >Lines: 8
>> >Message-ID: <4A081269-7598-4076-88EE-465C39E4BBC6@microsoft.com>
>> >MIME-Version: 1.0
>> >Content-Type: text/plain;
>> > charset="Utf-8"
>> >Content-Transfer-Encoding: 7bit
>> >X-Newsreader: Microsoft CDO for Windows 2000
>> >Content-Class: urn:content-classes:message
>> >Importance: normal
>> >Priority: normal
>> >X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
>> >Newsgroups: microsoft.public.windows.server.sbs
>> >NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.1.29
>> >Path: cpmsftngxa10.phx.gbl!TK2MSFTNGXA03.phx.gbl
>> >Xref: cpmsftngxa10.phx.gbl microsoft.public.windows.server.sbs:140687
>> >X-Tomcat-NG: microsoft.public.windows.server.sbs
>> >
>> >SBS 2003: I keep getting "Error 14: Not enough storage space is
available
>> to
>> >complete this operation" on the Print Spooler service.
>> >
>> >Basically, printing fails, try to restart the spooler, get the error,
>> >reboot, all is well for a day or two.
>> >
>> >Any ideas? Please help!
>> >
>> >
>>
>>
>
- Next message: Bill Peng [MSFT]: "RE: SBS4.5 to SBS2003 Exchange migration problem"
- Previous message: Jim G: "Install Norton Ghost 9.0 on SBS2K3?"
- In reply to: Mindy: "RE: Print Spooler Error 14"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
