Exchange Server TechCenter >
Exchange Server Forums
>
Exchange Software Updates
>
Exchange 2007 SP2 on Windows Server 2003 SP2
Exchange 2007 SP2 on Windows Server 2003 SP2
- We just attempted to install Exchange 2007 SP2 on Windows Server 2003 SP2. The server is running the Client Access Role and Hub Transport Role with SP1 and Rollup 9. When running the upgrade tp SP2 the schema updates work, the Hub Transport Role updates correctly, but when it gets to Client Access role it appears to get about half way through then errors out with the below error.Error:An error occurred. The error code was 3221685950. The message was The remote procedure call failed..There is an event in the application event log, event 1002. The event has the exact same wording as the setup application gives.I did some searching, but of course google, bing, and the MS premeir site gives nothing to go on.We tried rebooting the server and rerunning the service pack 2, but it gives the same result.
Answers
- I've just solve the same probem yesterday.
So I'll share you all my findings:
First, I also checked log, and get same RPC 1726 error.
Then I gathered a network data capture by netmon3.3 and I found when the Exchange setup UI send a RPC request to DC, the DC reset the TCP session!
Just before the RPC request, the TCP session has been idle for exactly 1 minutes.
I found 2 similar TCP reset sent from DC.
Then I think this might be caused by DC's too fast TCP session state destruction. (maybe related to SNP, which was introduced in Win2k3 SP2)
I don't want to change anything on DC. So I tried to add "HKLM\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\keepAliveTime" (value=30000, means 30 seconds) on the exchange server to have a test.
After a server reboot, to my great joy, it worked!
Hope this can help u!- Marked As Answer byXiu Zhang - MSFTMSFT, ModeratorTuesday, December 01, 2009 4:08 AM
- Proposed As Answer byBrekkjen Monday, November 30, 2009 10:59 AM
All Replies
- Anything in the Exchange setup logs located at: %SystemDrive%\ExchangeSetupLogs ?
- Below is the section of the setup log that seems to pertain to the issue.[8/25/2009 4:35:29 PM] [2] ScUserDNFromLoginName (f:\08.02.0176\sources\dev\admin\src\libs\exsetup\exmisc.cxx:1439)Error code 0XC00706BE (1726): The remote procedure call failed.[8/25/2009 4:35:29 PM] [2] ScGetServerDNSNameFromDS (f:\08.02.0176\sources\dev\admin\src\libs\exsetup\dsmisc.cxx:3480)Error code 0XC00706BE (1726): The remote procedure call failed.[8/25/2009 4:35:29 PM] [2] Leaving ScGetServerDNSNameFromDS[8/25/2009 4:35:29 PM] [2] ScSetServerNetworkAddresses (f:\08.02.0176\sources\dev\admin\src\udog\excommon\ptudutil.cxx:1023)Error code 0XC00706BE (1726): The remote procedure call failed.[8/25/2009 4:35:29 PM] [2] Leaving ScSetServerNetworkAddresses[8/25/2009 4:35:29 PM] [2] CAtomServer::ScAddOrRefreshDSObjects (f:\08.02.0176\sources\dev\admin\src\udog\exsetdata\components\server\a_server.cxx:298)Error code 0XC00706BE (1726): The remote procedure call failed.[8/25/2009 4:35:29 PM] [2] CAtomServer::ScAddDSObjects (f:\08.02.0176\sources\dev\admin\src\udog\exsetdata\components\server\a_server.cxx:364)Error code 0XC00706BE (1726): The remote procedure call failed.[8/25/2009 4:35:29 PM] [2] CBaseAtom::ScReinstall (f:\08.02.0176\sources\dev\admin\src\udog\setupbase\basecomp\baseatom.cxx:813)Error code 0XC00706BE (1726): The remote procedure call failed.[8/25/2009 4:35:29 PM] [2] Leaving CBaseAtom(Microsoft Exchange Server-Level Objects)::ScReinstall[8/25/2009 4:35:29 PM] [2] Service = '' CBaseServiceAtom::ScReinstall (f:\08.02.0176\sources\dev\admin\src\udog\setupbase\basecomp\basesvcatom.cxx:240)Error code 0XC00706BE (1726): The remote procedure call failed.[8/25/2009 4:35:29 PM] [2] Leaving CBaseServiceAtom(Microsoft Exchange Server-Level Objects)::ScReinstall[8/25/2009 4:35:29 PM] [2] mode = 'Reinstall' (61955) CBaseAtom::ScSetup (f:\08.02.0176\sources\dev\admin\src\udog\setupbase\basecomp\baseatom.cxx:535)Error code 0XC00706BE (1726): The remote procedure call failed.[8/25/2009 4:35:29 PM] [2] ScSetupAtom (f:\08.02.0176\sources\dev\admin\src\udog\exsetdata\exsetds.cxx:897)Error code 0XC00706BE (1726): The remote procedure call failed.[8/25/2009 4:35:29 PM] [2] Leaving ScSetupAtom[8/25/2009 4:35:29 PM] [2] [ERROR] An error occurred. The error code was 3221685950. The message was The remote procedure call failed..[8/25/2009 4:35:29 PM] [1] The following 1 error(s) occurred during task execution:[8/25/2009 4:35:29 PM] [1] 0. ErrorRecord: An error occurred. The error code was 3221685950. The message was The remote procedure call failed..[8/25/2009 4:35:29 PM] [1] 0. ErrorRecord: Microsoft.Exchange.Management.Deployment.ExsetdataException: An error occurred. The error code was 3221685950. The message was The remote procedure call failed..[8/25/2009 4:35:29 PM] [1] [ERROR] An error occurred. The error code was 3221685950. The message was The remote procedure call failed..
- This same issue has happened on both of the CAS/HUB servers that we have tried to upgrade to SP2
Ok, so the forest steps went fine...Havent seen that specific error before, however, any invalid/inactive DCs or Exchange servers objects still present in AD?
Any duplicates in DNS for any existing Exchange Server? ( check both forward and reverse zones)
Using an account with the correct Exchange org perms?
If you run ExBpa for both health and permissions, does it flag anything?
I'm looking specfically at those early errors:
ScGetServerDNSNameFromDS
ScUserDNFromLoginName- As Andy mentioned can you paste the errors ABOVE the ScUserDNFromLoginName ?
Also please double check the permissions of the account that you are trying to use for the install. Hi,
Let me clarify some information with you:
1. What is the scenario of your Exchange Org? Edge+hub+cas+mailbox?NLB CAS?CCR?
2. Whether all the server roles installed on seperately?
3. How many DCs in the network?
3. Have you do any customize work on OWA?
Then I'd like to collect the following information and send them to me for further troubleshooting.
1. Please run ExBPA on the Server.
2. Please run MPS_Report(Mpsrpt_exchange.exe).
3.Please find the ExchangeSetuplog.log
Besides, I recommend you to use the account which you use to setup Exchange Server Org to install SP2 and disable all the AV applications on the server.
Regards,
Xiu- I ran into the very same problem.
First I installed SP2 on one CAS/HUB and everyting was fine, customer account was used and that account was used to install Exchange in the first place.
Then I installed SP2 on CAS/HUB #2 with an other account (also Exchange org admin) and had the issue.
After some investigation I rerun SP2 (this time with the first account) and it worked, seems like this was the issuse.
Edit: In this case it was Windows 2008 Server on all servers, a CCR-cluster and HUB/CAS without NLB
Magnus Björk www.mailmaster.se/blog - There are no errors above ScUserDNFromLoginName in the logs. I only pasted the part of the logs where there were errors in an effort to make it readable.This is a pristine AD/Exchange environment. The SP was released the day after the servers were installed.The account used to upgrade was the account used to install the servers in the first place. It is Exchange Org Admin, Enterprise Admin, Schema Admin, Domain Admin.1. Two CAS/HUB servers with a CCR cluster. SP2 worked fine with the CCR cluster. Yes, I know you are supposed to upgrade the CAS and HUB roles first, but after the SP2 failure on the CAS role we were curious to see if the MBX role would work.2. CAS and HUB roles are installed together on the two servers that are not working.3. There are two DCs in the environement. DCDiag and NetDiag both run with all passes.4. No OWA customizations at all.I will run ExBPA and MPS_Reports and send them along with the logs to you Xiu.
- Hi,
I have not got the logs from you. - Don't know, if it would help in this case? I had the same error message.
Details about it and the solution you will find here: http://social.technet.microsoft.com/Forums/en-US/exchangesoftwareupdate/thread/9188aafb-fcec-41d7-b59b-52802c725a45
regards, Reisenhofer Andreas - I've just solve the same probem yesterday.
So I'll share you all my findings:
First, I also checked log, and get same RPC 1726 error.
Then I gathered a network data capture by netmon3.3 and I found when the Exchange setup UI send a RPC request to DC, the DC reset the TCP session!
Just before the RPC request, the TCP session has been idle for exactly 1 minutes.
I found 2 similar TCP reset sent from DC.
Then I think this might be caused by DC's too fast TCP session state destruction. (maybe related to SNP, which was introduced in Win2k3 SP2)
I don't want to change anything on DC. So I tried to add "HKLM\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\keepAliveTime" (value=30000, means 30 seconds) on the exchange server to have a test.
After a server reboot, to my great joy, it worked!
Hope this can help u!- Marked As Answer byXiu Zhang - MSFTMSFT, ModeratorTuesday, December 01, 2009 4:08 AM
- Proposed As Answer byBrekkjen Monday, November 30, 2009 10:59 AM
- This solved the problem for me. Had the remote procedure call failed and event log 1002 on upgrading Client Access Role.
This was on a new 2007 standard on a 2008 Datacenter server. new install into a 2003 Exchange organization.
Added KeepAliveTime, rebooted and tried again and it worked.
Thanks a lot!
