RE: SBS 2003 Exchange startup problem / RPC Question



Hi KenT,

Thank you for your kind update.

As you mentioned, since the Symantec Mail Security is installed on the
server, the RPC is needed for Symantec Mail Security, and the error message
is "The RPC-Server is under too much load", it could most likely be related
to the Symantec Mail Security software. Please temporarily uninstall it,
and check if the issue can be reproduced. Alternatively, you may also
contact the software vendor to require help.

Additionally, please add the ncacn_nb_tcp registry key and check if the
issue can be reproduced. For detailed steps, please refer to my previous
reply.

Otherwise, please open the system Event Viewer on the SBS Server, and check
whether there are any error messages about this issue, then paste the full
context in your reply post.

I am appreciated your time and cooperation. If anything is unclear, please
feel free to let me know. I am looking forward to hearing from you.

Best regards,

Nathan Liu (MSFT)
Microsoft CSS Online Newsgroup Support

Get Secure! - www.microsoft.com/security
======================================================
This newsgroup only focuses on SBS technical issues. If you have issues
regarding other Microsoft products, you'd better post in the corresponding
newsgroups so that they can be resolved in an efficient and timely manner.
You can locate the newsgroup here:
http://www.microsoft.com/communities/newsgroups/en-us/default.aspx

When opening a new thread via the web interface, we recommend you check the
"Notify me of replies" box to receive e-mail notifications when there are
any updates in your thread. When responding to posts via your newsreader,
please "Reply to Group" so that others may learn and benefit from your
issue.

Microsoft engineers can only focus on one issue per thread. Although we
provide other information for your reference, we recommend you post
different incidents in different threads to keep the thread clean. In doing
so, it will ensure your issues are resolved in a timely manner.

For urgent issues, you may want to contact Microsoft CSS directly. Please
check http://support.microsoft.com for regional support phone numbers.

Any input or comments in this thread are highly appreciated.
======================================================
This posting is provided "AS IS" with no warranties, and confers no rights.



--------------------
>Thread-Topic: SBS 2003 Exchange startup problem / RPC Question
>thread-index: AcWhZ8w06xZki4e0S/2cin9mrfmtPQ==
>X-WBNR-Posting-Host: 84.140.242.117
>From: "=?Utf-8?B?S2VuLVQ=?=" <KenT@xxxxxxxxxxxxxxxxxxxxxxxxx>
>References: <7B89FB26-2242-4760-A0F7-B79748D21535@xxxxxxxxxxxxx>
<x#455pLmFHA.944@xxxxxxxxxxxxxxxxxxxxx>
>Subject: RE: SBS 2003 Exchange startup problem / RPC Question
>Date: Mon, 15 Aug 2005 00:06:02 -0700
>Lines: 193
>Message-ID: <F6431D22-14B5-4B43-9481-73C12B3BC4D7@xxxxxxxxxxxxx>
>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.2.250
>Path: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGXA03.phx.gbl
>Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.windows.server.sbs:144347
>X-Tomcat-NG: microsoft.public.windows.server.sbs
>
>Nathan,
>
>thanks for your help with this. Sorry I couldn't post back earlier, but
had
>other issues with the server too.
>
>Basically, yes, we have Symantec Mail Security installed on the server.
>The problem only occurs after a server re-boot - not when the Exchange
>servers are stopped and then re-started after a re-boot.
>
>I checked MS KB 267573 anf find that on our server the setting for
>ncacn_nb_tcp is missing. Could this be the cause of the error?
>
>In our reg key for RPC Client protocols I see :
>Value 0
> Name: ncacn_np
> Typ: REG_SZ
> Daten: rpcrt4.dll
>
>Value 1
> Name: ncacn_ip_tcp
> Typ: REG_SZ
> Daten: rpcrt4.dll
>
>Value 2
> Name: ncadg_ip_udp
> Typ: REG_SZ
> Daten: rpcrt4.dll
>
>Value 3
> Name: ncacn_http
> Typ: REG_SZ
> Daten: rpcrt4.dll
>
>
>We should add the key for ncacn_nb_tcp and see what happens?
>Would the services still re-start as they do with this key missing?
>
>Ken
>
>
>""Nathan Liu [MSFT]"" wrote:
>
>> Hello KenT,
>>
>> Thank you for posting in the SBS newsgroup.
>>
>> Also, many thanks for Jonathan's great input.
>>
>> According to your description, I understand that you received the error
>> "MSExchangeSA. 1005. Unexpected error. The RPC-Server is under too much
>> load. Win32 ID-Nr.: c00706bb." when the Server is re-started. If I have
>> misunderstood your concern, please don't hesitate to let me know.
>>
>> Jonathan is right on target. I have checked the running status of the
>> RpcLocator services in the SBS 2003 Premium SP1 on my testing machine,
it
>> is configured as Manual and Stopped.
>>
>> Based on my research, Event 1005 seems to be a general event code used
to
>> indicate that something the System Attendant needs is missing or
corrupt.
>> Exchange records a 1005 error in various conditions.
>>
>> To narrow down this issue, please answer and perform the following
>> questions and steps:
>>
>> 1. As you mentioned, since the error message is "The RPC-Server is
under
>> too much load.", and the RPC is needed for Symantec Mail Security. Can I
>> assume you have installed the Symantec Mail Security software, please
>> temporarily uninstall it, and check if the issue can be reproduced.
>>
>> 2. This issue may occur if Microsoft Firewall Client is running on the
>> server. If it is the case, please refer to the below KB article to
resolve
>> it:
>>
>> 842471 The Exchange System Attendant service does not start and event
IDs
>> 1004,
>> http://support.microsoft.com/?id=842471
>>
>> 3. This issue may be caused by a lack of registry settings for the RPC
>> protocol, please perform the below steps:
>>
>> a. Open Regedt32
>>
>> b. Add the key ClientProtocols to the following path:
>> HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Rpc\ClientProtocols
>>
>> c. Add the following values to the newly created key ClientProtocols:
>> ncacn_http : REG_SZ : rpcrt4.dll
>> ncacn_ip_tcp: REG_SZ : rpcrt4.dll
>> ncacn_nb_tcp: REG_SZ : rpcrt4.dll
>> ncacn_np: REG_SZ : rpcrt4.dll
>> ncadg_ip_udp: REG_SZ : rpcrt4.dll
>>
>> 267573 XADM: Error 0xc00206b7 When You Start the Exchange Server System
>> http://support.microsoft.com/?id=267573
>>
>> 4. What's the problematic Exchange services? Is it the Microsoft
>> Exchange System Attendant? Please do a screen capture of the error
message,
>> and attach it in your reply.
>>
>> 5. Please locate the Errorlog.txt and Eventlog.txt from the
..\Program
>> Files\Microsoft Integration\Windows Small Business Server 2003\Logs
folder,
>> and check whether there are any error messages noted on this issue, then
>> paste the full context in your reply.
>>
>> I am appreciated your time and cooperation. If anything is unclear,
please
>> feel free to let me know. I am looking forward to hearing from you.
>>
>> Best regards,
>>
>> Nathan Liu (MSFT)
>> Microsoft CSS Online Newsgroup Support
>>
>> Get Secure! - www.microsoft.com/security
>> ======================================================
>> This newsgroup only focuses on SBS technical issues. If you have issues
>> regarding other Microsoft products, you'd better post in the
corresponding
>> newsgroups so that they can be resolved in an efficient and timely
manner.
>> You can locate the newsgroup here:
>> http://www.microsoft.com/communities/newsgroups/en-us/default.aspx
>>
>> When opening a new thread via the web interface, we recommend you check
the
>> "Notify me of replies" box to receive e-mail notifications when there
are
>> any updates in your thread. When responding to posts via your
newsreader,
>> please "Reply to Group" so that others may learn and benefit from your
>> issue.
>>
>> Microsoft engineers can only focus on one issue per thread. Although we
>> provide other information for your reference, we recommend you post
>> different incidents in different threads to keep the thread clean. In
doing
>> so, it will ensure your issues are resolved in a timely manner.
>>
>> For urgent issues, you may want to contact Microsoft CSS directly.
Please
>> check http://support.microsoft.com for regional support phone numbers.
>>
>> Any input or comments in this thread are highly appreciated.
>> ======================================================
>> This posting is provided "AS IS" with no warranties, and confers no
rights.
>>
>> --------------------
>> >Thread-Topic: SBS 2003 Exchange startup problem / RPC Question
>> >thread-index: AcWYECqUiEy040f5TtataIYLwQM3XQ==
>> >X-WBNR-Posting-Host: 84.140.235.179
>> >From: "=?Utf-8?B?S2VuLVQ=?=" <KenT@xxxxxxxxxxxxxxxxxxxxxxxxx>
>> >Subject: SBS 2003 Exchange startup problem / RPC Question
>> >Date: Wed, 3 Aug 2005 02:46:05 -0700
>> >Lines: 24
>> >Message-ID: <7B89FB26-2242-4760-A0F7-B79748D21535@xxxxxxxxxxxxx>
>> >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.2.250
>> >Path: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGXA03.phx.gbl
>> >Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.windows.server.sbs:141068
>> >X-Tomcat-NG: microsoft.public.windows.server.sbs
>> >
>> >Odd effect seems to have started after applying full SP1, including
>> premium
>> >SPs for Exchange and SQL.
>> >
>> >When server is re-started, an Exchange service fails with error :
>> >MSExchangeSA. 1005. Unexpected error. The RPC-Server is under too much
>> load.
>> >Win32 ID-Nr.: c00706bb.
>> >
>> >When the Exchange services are then all re-started by hand, all is fine.
>> >
>> >I have noticed on the server that RPC-Locator service is set to start
type
>> :
>> >Manual
>> >I Think this is the problem, when server is restarted, RPC-Locator is
not
>> >yet running and therefore the error for Exchange since RPC is needed
for
>> >Symantec Mail Security.
>> >
>> >Is this likely? or is there some other possibility?
>> >
>> >Question - Surely RPC-Locator service should be set to Start type
>> Automatic???
>> >
>> >Appreciate any comments, especially a check if RPC-Location is running
as
>> >automatic startup on other SBS Servers.
>> >
>> >Thanks
>> >
>> >
>>
>>
>

.



Relevant Pages

  • Re: Email enable doc lib
    ... Microsoft CSS Online Newsgroup Support ... This newsgroup only focuses on SBS technical issues. ... navigate to the public folder and send some posts with attachments to the ... I have disabled forms base Athentication from the default V.Smtp server ...
    (microsoft.public.windows.server.sbs)
  • Re: Cant logon from workstation as Administrator
    ... server box and let me know if there is any problem related to the issue. ... Microsoft CSS Online Newsgroup Support ... This newsgroup only focuses on SBS technical issues. ... be able to logon using ANY accounts from that workstation. ...
    (microsoft.public.windows.server.sbs)
  • RE: w3wp.exe unable to start properly and mail delivery very slow
    ... I will be here waiting for your updates, please feel free to post back. ... Microsoft CSS Online Newsgroup Support ... This newsgroup only focuses on SBS technical issues. ... |> internal NIC as the DNS server on both client computer and SBS server. ...
    (microsoft.public.windows.server.sbs)
  • Re: Nagging Autorization issue for Companyweb after ISA04 install
    ... Check the companyweb CNAME entry in the DNS Server. ... Does the situation occur when you access companyweb from the ISA ... > 'Microsoft Firewall' service. ... > This newsgroup only focuses on SBS technical issues. ...
    (microsoft.public.windows.server.sbs)
  • Re: Email enable doc lib
    ... server to test the issue. ... Microsoft CSS Online Newsgroup Support ... This newsgroup only focuses on SBS technical issues. ... Please try to logon Public folder list using URL: ...
    (microsoft.public.windows.server.sbs)

Loading