Temporary Server Error

Trying to access BBM since this morning without success. Error "temporary server error - A temporary server error has occurred. Please try again later."
I have reset the phone and reinstalled the latest BBM software. I have read through other threads and this has been an issue since early Feb 2013, is it resolved now? What is the work around to it?
Thank you for your assistance.
Kind Regards
Mayson Arnagiri

Hi,
Firstly, what version of the OS are you running? Check in settings - about - Software.
I know that this issue has previously been reported as a known issue for 10.0.9.2372 and the only known workaround is to keep trying a battery pull and then relaunch BBM
I appreciate it's not a fix, but it is something that I have also experienced myself until a recent OS update.

Similar Messages

Exchange 2013 "451 4.7.0 Temporary server error. Please try again later. PRX5" Error

I know this error message is discussed on other topics on several different forums including TechNet but I ended up opening this as the suggestions that solved the problems with the previous threads dos not work on mine.
We have a ticketing software that runs on client computers which sends mails to local Exchange server for notifications using port 25.
Approximately 1 out of 5 mails end up getting the "451 4.7.0 Temporary server error. Please try again later. PRX5" error. I have confirmed this by running Wireshark on the clients, saw the exact error message. This has been replicated with
several client machines running Win7 & 8.
I have tried several solutions to this, one of them being this:
http://www.techieshelp.com/exchange-2013-451-4-7-0-temporary-server-error-please-try-again-later-prx5/
I still get the same error from time to time after doing this, so it is not the issue. All the records in local hosts file, receive connector is listening to port 25 on all IPv4 addresses.
The server has a single NIC and the DNS lookups are done through that single NIC, not through "All available adapters" as set by default on ECP.
Almost everyone seems to be convinced that this is related to DNS but looking at how fast I get the error message, it doesn't look like it's waiting for a timeout (maybe unrelated, just an observation). Do you think it is possible that the DNS servers themselves
are causing this issue?
Also, I see Event 5504 on the primary dns server almost all of them coming from the mail server, saying that the DNS query was invalid. It may be related.
Additional Notes:
- CU6 is applied but did not fix the issue.
- None of these have solved it for me: http://www.servolutions.com/support/articles/Temporaryservererror2013.htm
- Receive Connectors do listen to separate ports 25 & 2525 -> There is a single instance of both Transport Service and Edge Transport service respectively. Anonymous users are accepted in both Receive connectors.

Thank you for your post.
This is a quick note to let you know that we are performing research on this issue.
Niko Cheng
TechNet Community Support
Thank you Niko. I'm looking forward to your answer as I've gone through every post regarding this and none of them worked. I will let everyone know if I can find a solution to this.

451 4.7.0 temporary server error. please try again later. prx4

Hello,
in my environment i can send/receive mail.
When doing some checks i will end up with this error :
451 4.7.0 temporary server error. please try again later. prx4
I have tried the following without results :
Exchange 2013 SMTP error "451 4.7.0 Temporary server error. Please try again later. PRX3"
This error message seems to be caused by DNS issues in the Exchange 2013 set up. Exchange then rejects all emails like this. It is not quite clear what Microsoft means with this error code and the various PRX-numbers at the end - we've also seen PRX1, PRX3,
PRX7. There is no list and no documentation on them available.
From customer feedback we found these ways to solve the problem:
Disable all unused network cards.
Check all DNS server entries in the configuration of your network cards (check
all network adapters) and make sure not to reference server 127.0.0.1 as DNS server but to use the real IP address instead.
If you have more than one fixed IP address in the server add an entry for each IP address in the hosts file (C:\Windows\System32\drivers\etc\hosts) formatted like "192.168.1.1 SERVERNAME".
Important: Do load the latest Exchange 2013 updates, especially CU1 if you haven't done that already.
Please delete the receive connectors in Exchange and create one new receive connector. Use the "front end" instead of "hub transport" setting and vice versa.
What do do, to fix this issue?
Thx

Hello,
Please use dcdiag command to check if all DC run normally.
Please use repadmin /showrepl command to verify DC replication status.
Please check if there is any related error in application log.
Cara Chen
TechNet Community Support

Exchange Receive Connector Temporary Server Error. Please Try again later. PRX4

Hi ,
I installated Exchange server 2013 on Windows 2012 R2 Servers..
Topology ;
1 Active Directory Server : Windows 2012 r2 all updates installed.
1 Exchange 2013 Server : Windows 2012 r2 all updates installed.
I configured send Connector settings and I checked Receive connectors Default Frontend Exchange settings. Anonymous users is ok and don't have any problem.
When I send mail Exchange -> Internet mail goes. this is ok.
But when I send mail Internet -> Exchange I am getting this error ;
Message or connection acked with status Retry and response 451 4.4.0 Primary target IP address responded with: ""501 5.5.4 Required arguments not present."" Attempted failover to alternate host, but that did not succeed. Either there
are no alternate hosts, or delivery failed to all alternate hosts. The last endpoint attempted was xxx.xxx.xxx.xxx:2525
telnet results are below ;
220 exchange.bulut.email Microsoft ESMTP MAIL Service ready at Tue, 30 Dec 2014
14:12:19 +0200
EHLO bulut.email 250-exchange.bulut.email Hello [xxxxxxxxxxxxxxxxx]
250-SIZE 37748736
250-PIPELINING
250-DSN
250-ENHANCEDSTATUSCODES
250-STARTTLS
250-X-ANONYMOUSTLS
250-AUTH NTLM
250-X-EXPS GSSAPI NTLM
250-8BITMIME
250-BINARYMIME
250-CHUNKING
250 XRDST
MAIL FROM:[email protected] 250 2.1.0 Sender OK
RCPT TO:[email protected] NOTIFY=success,failure 250 2.1.5 Recipient OK
DATA354 Start mail input; end with <CRLF>.<CRLF>
Subject: Test from Contosoa
This is a test message
451 4.7.0 Temporary server error. Please try again later. PRX4
QUIT 221 2.0.0 Service closing transmission channel
Thanks. Regards.

Hi,
If the CAS and MBX servers are collocated on the same server the SMTP Receive connection for the Transport service will listen on 2525 instead of 25. This is because two services (FET and Transport Service) can’t listen on the same port.
Refer from this article:
http://blogs.technet.com/b/rischwen/archive/2013/03/13/exchange-2013-mail-flow-demystified-hopefully.aspx
Please try to create an endpoint for 2525 on default receive connector to test mail flow by the following steps:
EAC -> mail flow -> receive connectors -> Default EXCHANGE
Click Edit then click scoping tab.
Under Network adapter bindings, click
add button to create port 2525 for all available Ipv4/Ipv6 addresses.
Best Regards.

Blackberry Z10,post security wipe...BBM Not working..Showcasing error Unable to complete Set Up and Temporary Server Error"

I would request you to please help fixing the BBM error - Unable to complete Set Up and Temporary Server Error”.
I am using a BB Z10 with Software version 10.1.0.4181 and OS version 10.1.0.4633
Already tried resetting device to Factory Settings and Security Wipe...
Please help.

Hey KaranPrabhakar,
Welcome to the BlackBerry Support Community Forums.
Thanks for the question.
Follow the steps in this KB article to resolve the issue: www.blackberry.com/btsc/KB33780
Let me know if you have any more questions.
Cheers.
-ViciousFerret
Come follow your BlackBerry Technical Team on Twitter! @BlackBerryHelp
Be sure to click Like! for those who have helped you.
Click Accept as Solution for posts that have solved your issue(s)!

451 4.7.0 Temporary server error. Please try again later. PRX2 on sending emails to Office 365 Business Essentials email.

I've signed up for Office 365 Business Essentials service, and I have trouble sending and receiving emails. All the messages I send to my email associated with this account get a reply with error message
451 4.7.0 Temporary server error. Please try again later. PRX2
Additionally, all the mails I send from Outlook OWA in a browser and with iPhone app are stuck in Drafts folder and are not sent anywhere.
This is what I tried:
Checked the mail flow in Exchange admin center. There are no mail rules, no inbound or outbound connectors
Checked for DNS issues with my domain by clicking "Manage domains" in Admin center. Message was "barsukov.net domain is set up correctly. No action is
required."
Checked the MX records of my domain, barsukov.net, which point to a correct domain suggested by Microsoft.
Most of the search results related to this error suggest to add entries to hosts file on server with Exchange. This is not applicable to my case, obviously, since I use a cloud version of Exchange.
How to fix this issue?

It takes some time for newly added domains to be recognized by the service. If the issue persists, open a case with MS support:
http://virtualchat.support.microsoft.com/client/default.aspx?siteid=32ECF580-B446-44E5-8B4D-25F0AFE07779&query=Support%20phone%20number

Error in Edge server mail queue LED=451 4.7.0 Temporary server error. Please try again later. PRX6

We have two Edge servers deployed at our Central location where it accepts mails from all other site and send it to Internet and vice versa. There is no problem for outgoing mails but while receiving the mails from the internet there is always an average
queue of 600 to 700 mails (some time goes up to 2000). After analysing the issue we found the below errors..
LED=451 4.7.0 Temporary server error. Please try again later. PRX6
451 4.4.0 SMTPSEND.SuspiciousRemoteServerError; remote server disconnected abruptly; retry will be delayed
421 4.4.2 Connection dropped due to TimedOut
We have then picked random 10/12 recipients from the error queue and found all of ‘em were
from a specific site.
we have tried the below solution... after searching for resolution on the Internet
Tried enabling protocol logging but nothing found
Since it was more likely to be a DNS issue, tried manually adding DNS server IPs in the ‘Default front end receive connector’ properties.
Tried adding DNS server IPs manually into both Transport servers in ‘DNS Lookup’ setting in the server properties.
Tried adding local server's IP to the hosts file.
Checked if SMTP fixup is enabled on Firewall.
Verified the receive connector security settings.
Verified the CPU and Memory utilization is normal.
Disabled the Performance Counter on both Transport Server to ensure memory usage.
but nothing seems helping
now the problem is because of this there is a mail delay of at least 20 minutes for incoming mails.
Need help resolving the same.
Neilesh

I think its working now ..
after researching a lot on events on Transport servers we got to know that 'Default Frontend Receive Connector' was rejecting some messages...
we have then increased the value for the parameter "MaxInboundConnectionPerSource" from 20 to unlimited and
MaxInboundConnectionPercentagePerSource
from 2 to 10.. we have the waited for 2 to three hours .. the queue then came down from 1500 to 5 and petty stable thereafter.
we will be monitoring the same for few days from now.
Neilesh

Delivery fails: "The server response was: 4.7.0 Temporary server error. Please try again later. PRX3"

Trying to setup an Exchange 2013 server, with the DC and Exchange on same machine. WHen I try to deliver for either of the 2 mailboxes I have setup, I get this error.
The server returned status code 451 - Error in processing. The server response was: 4.7.0 Temporary server error. Please try again later. PRX3
It doesn't seem to be a resource issue (I'm running an XL instance on Azure), and all other connectivity works fine (and fast). I just can't receive email there.
Looking in the event logs, I saw one issue related to the Front End HTTP proxy, but I wouldn't assume that's relevant here. (And connectivity via Outlook & OWA seem to be fine, with the exception
of some redirect issues on the latter).
I did end up installing Exchange on a secondary drive for space considerations, so the location is different... not sure if that would factor in either.
Any ideas? I don't even really know where to start debugging this. I'm trying to set this up to work on some event sync/forwarding code.

Ok, I think I solved my problem but figured I would update here for others who may be running into the same issue.
In my \Exchange\TransportRoles\Logs\FrontEnd\ProtocolLog\SmtpReceive\*.LOG, I found more detailed information on the issue.
"Message or connection acked with status Retry and response
451 4.4.0 Error encountered while communicating with primary target IP address: ""421 4.2.1 Unable to connect.""
Attempted failover to alternate host, but that did not succeed. Either there are no alternate hosts, or delivery failed to all alternate hosts. The last endpoint attempted was 10.10.10.1:2525"
I thought creating an endpoint for 25 would be sufficient, but once I created another endpoint for 2525 then my tests started working.

Cannot receive mail on Exchange 2013 CAS: 451 4.7.0 Temporary server error. Please try again later. PRX4

Hi all,
I have just deployed Exchange 2013 on two CAS boxes and two MBX boxes as follows:
10.10.20.11
CAS01
10.10.20.12
CAS02
10.10.10.11
MBX01
10.10.10.12
MBX02
If I telnet to the internet facing IP on CAS01 and attempt to send an email internally (to a mailbox on MBX01) I get the following:
220 smtp.myrealdomain.com Microsoft ESMTP MAIL Service ready at Wed, 26 Mar 2014 01:14:24 +1000
EHLO test.com
250-smtp.myrealdomain.com Hello [10.10.20.11]
250-SIZE 36700160
250-PIPELINING
250-DSN
250-ENHANCEDSTATUSCODES
250-STARTTLS
250-AUTH
250-8BITMIME
250-BINARYMIME
250 CHUNKING
MAIL FROM:[email protected]
250 2.1.0 Sender OK
RCPT TO:[email protected]
250 2.1.5 Recipient OK
DATA
354 Start mail input; end with <CRLF>.<CRLF>
Subject:Test email 452
This is test email 452
451 4.7.0 Temporary server error. Please try again later. PRX4
Connectivity Log on CAS01:
2014-03-25T15:27:15.353Z,08D11605A575FAE1,SMTP,internalproxy,+,Undefined 00000000-0000-0000-0000-000000000000;QueueLength=<no priority counts>
2014-03-25T15:27:15.353Z,08D11605A575FAE1,SMTP,internalproxy,>,"MBX02.myaddomain.com[10.10.10.12], MBX01.myaddomain.com[10.10.10.11]"
2014-03-25T15:27:15.353Z,08D11605A575FAE1,SMTP,internalproxy,>,Established connection to 10.10.10.12
2014-03-25T15:27:15.369Z,08D11605A575FAE1,SMTP,internalproxy,-,Messages: 0 Bytes: 0 (Attempting next target)
2014-03-25T15:27:15.369Z,08D11605A575FAE2,SMTP,internalproxy,+,Undefined 00000000-0000-0000-0000-000000000000;QueueLength=<no priority counts>
2014-03-25T15:27:15.369Z,08D11605A575FAE2,SMTP,internalproxy,>,Established connection to 10.10.10.11
2014-03-25T15:27:15.369Z,08D11605A575FAE2,SMTP,internalproxy,-,Messages: 0 Bytes: 0 (Retry : EHLO Options do not match for proxy)
2014-03-25T15:28:10.328Z,08D11605A575FAFA,SMTP,internalproxy,+,Undefined 00000000-0000-0000-0000-000000000000;QueueLength=<no priority counts>
2014-03-25T15:28:21.669Z,08D11605A575FAFA,SMTP,internalproxy,>,"MBX01.myaddomain.com[10.10.10.11], MBX02.myaddomain.com[10.10.10.12]"
2014-03-25T15:28:21.669Z,08D11605A575FAFA,SMTP,internalproxy,>,Established connection to 10.10.10.11
2014-03-25T15:28:21.669Z,08D11605A575FAFA,SMTP,internalproxy,-,Messages: 0 Bytes: 0 (Attempting next target)
2014-03-25T15:28:21.669Z,08D11605A575FAFF,SMTP,internalproxy,+,Undefined 00000000-0000-0000-0000-000000000000;QueueLength=<no priority counts>
2014-03-25T15:28:21.669Z,08D11605A575FAFF,SMTP,internalproxy,>,Established connection to 10.10.10.12
2014-03-25T15:28:21.669Z,08D11605A575FAFF,SMTP,internalproxy,-,Messages: 0 Bytes: 0 (Retry : EHLO Options do not match for proxy)
SmtpSend Log on CAS01:
2014-03-25T15:32:34.158Z,Inbound Proxy Internal Send Connector,08D11605A575FB5E,1,10.10.20.11:25495,10.10.10.12:25,+,,
2014-03-25T15:32:34.158Z,Inbound Proxy Internal Send Connector,08D11605A575FB5E,2,10.10.20.11:25495,10.10.10.12:25,<,220 ********************************************************************************************************************,
2014-03-25T15:32:34.158Z,Inbound Proxy Internal Send Connector,08D11605A575FB5E,3,10.10.20.11:25495,10.10.10.12:25,*,,Proxying inbound session with session id 08D11605A575FB5D
2014-03-25T15:32:34.158Z,Inbound Proxy Internal Send Connector,08D11605A575FB5E,4,10.10.20.11:25495,10.10.10.12:25,>,EHLO CAS01.myaddomain.com,
2014-03-25T15:32:34.158Z,Inbound Proxy Internal Send Connector,08D11605A575FB5E,5,10.10.20.11:25495,10.10.10.12:25,<,250-MBX02.myaddomain.com Hello [10.10.20.11],
2014-03-25T15:32:34.158Z,Inbound Proxy Internal Send Connector,08D11605A575FB5E,6,10.10.20.11:25495,10.10.10.12:25,<,250-SIZE,
2014-03-25T15:32:34.158Z,Inbound Proxy Internal Send Connector,08D11605A575FB5E,7,10.10.20.11:25495,10.10.10.12:25,<,250-PIPELINING,
2014-03-25T15:32:34.158Z,Inbound Proxy Internal Send Connector,08D11605A575FB5E,8,10.10.20.11:25495,10.10.10.12:25,<,250-DSN,
2014-03-25T15:32:34.158Z,Inbound Proxy Internal Send Connector,08D11605A575FB5E,9,10.10.20.11:25495,10.10.10.12:25,<,250-ENHANCEDSTATUSCODES,
2014-03-25T15:32:34.158Z,Inbound Proxy Internal Send Connector,08D11605A575FB5E,10,10.10.20.11:25495,10.10.10.12:25,<,250-XXXXXXXA,
2014-03-25T15:32:34.158Z,Inbound Proxy Internal Send Connector,08D11605A575FB5E,11,10.10.20.11:25495,10.10.10.12:25,<,250-XXXXXXXXXXXXXB,
2014-03-25T15:32:34.158Z,Inbound Proxy Internal Send Connector,08D11605A575FB5E,12,10.10.20.11:25495,10.10.10.12:25,<,250-AUTH NTLM,
2014-03-25T15:32:34.158Z,Inbound Proxy Internal Send Connector,08D11605A575FB5E,13,10.10.20.11:25495,10.10.10.12:25,<,250-XXXXXXXXXXXXXXXXXC,
2014-03-25T15:32:34.158Z,Inbound Proxy Internal Send Connector,08D11605A575FB5E,14,10.10.20.11:25495,10.10.10.12:25,<,250-8BITMIME,
2014-03-25T15:32:34.158Z,Inbound Proxy Internal Send Connector,08D11605A575FB5E,15,10.10.20.11:25495,10.10.10.12:25,<,250-BINARYMIME,
2014-03-25T15:32:34.158Z,Inbound Proxy Internal Send Connector,08D11605A575FB5E,16,10.10.20.11:25495,10.10.10.12:25,<,250-XXXXXXXD,
2014-03-25T15:32:34.158Z,Inbound Proxy Internal Send Connector,08D11605A575FB5E,17,10.10.20.11:25495,10.10.10.12:25,<,250-XXXXXXE,
2014-03-25T15:32:34.158Z,Inbound Proxy Internal Send Connector,08D11605A575FB5E,18,10.10.20.11:25495,10.10.10.12:25,<,250-XXXXF,
2014-03-25T15:32:34.158Z,Inbound Proxy Internal Send Connector,08D11605A575FB5E,19,10.10.20.11:25495,10.10.10.12:25,<,250 XXXXXXXXXXXXXG,
2014-03-25T15:32:34.158Z,Inbound Proxy Internal Send Connector,08D11605A575FB5E,20,10.10.20.11:25495,10.10.10.12:25,*,,"EHLO options between current server and proxy target do not match : Chunking, Xrdst. Critical non
matching options : Chunking, Xrdst. Failing over."
2014-03-25T15:32:34.158Z,Inbound Proxy Internal Send Connector,08D11605A575FB67,0,,10.10.10.11:25,*,,attempting to connect
2014-03-25T15:32:34.158Z,Inbound Proxy Internal Send Connector,08D11605A575FB5E,21,10.10.20.11:25495,10.10.10.12:25,>,QUIT,
2014-03-25T15:32:34.158Z,Inbound Proxy Internal Send Connector,08D11605A575FB67,1,10.10.20.11:25496,10.10.10.11:25,+,,
2014-03-25T15:32:34.158Z,Inbound Proxy Internal Send Connector,08D11605A575FB5E,22,10.10.20.11:25495,10.10.10.12:25,<,221 2.0.0 Service closing transmission channel,
2014-03-25T15:32:34.158Z,Inbound Proxy Internal Send Connector,08D11605A575FB5E,23,10.10.20.11:25495,10.10.10.12:25,-,,Local
2014-03-25T15:32:34.158Z,Inbound Proxy Internal Send Connector,08D11605A575FB67,2,10.10.20.11:25496,10.10.10.11:25,<,220 ********************************************************************************************************************,
2014-03-25T15:32:34.158Z,Inbound Proxy Internal Send Connector,08D11605A575FB67,3,10.10.20.11:25496,10.10.10.11:25,*,,Proxying inbound session with session id 08D11605A575FB5D
2014-03-25T15:32:34.158Z,Inbound Proxy Internal Send Connector,08D11605A575FB67,4,10.10.20.11:25496,10.10.10.11:25,>,EHLO CAS01.myaddomain.com,
2014-03-25T15:32:34.158Z,Inbound Proxy Internal Send Connector,08D11605A575FB67,5,10.10.20.11:25496,10.10.10.11:25,<,250-MBX01.myaddomain.com Hello [10.10.20.11],
2014-03-25T15:32:34.158Z,Inbound Proxy Internal Send Connector,08D11605A575FB67,6,10.10.20.11:25496,10.10.10.11:25,<,250-SIZE,
2014-03-25T15:32:34.158Z,Inbound Proxy Internal Send Connector,08D11605A575FB67,7,10.10.20.11:25496,10.10.10.11:25,<,250-PIPELINING,
2014-03-25T15:32:34.158Z,Inbound Proxy Internal Send Connector,08D11605A575FB67,8,10.10.20.11:25496,10.10.10.11:25,<,250-DSN,
2014-03-25T15:32:34.158Z,Inbound Proxy Internal Send Connector,08D11605A575FB67,9,10.10.20.11:25496,10.10.10.11:25,<,250-ENHANCEDSTATUSCODES,
2014-03-25T15:32:34.158Z,Inbound Proxy Internal Send Connector,08D11605A575FB67,10,10.10.20.11:25496,10.10.10.11:25,<,250-XXXXXXXA,
2014-03-25T15:32:34.158Z,Inbound Proxy Internal Send Connector,08D11605A575FB67,11,10.10.20.11:25496,10.10.10.11:25,<,250-XXXXXXXXXXXXXB,
2014-03-25T15:32:34.158Z,Inbound Proxy Internal Send Connector,08D11605A575FB67,12,10.10.20.11:25496,10.10.10.11:25,<,250-AUTH NTLM,
2014-03-25T15:32:34.158Z,Inbound Proxy Internal Send Connector,08D11605A575FB67,13,10.10.20.11:25496,10.10.10.11:25,<,250-XXXXXXXXXXXXXXXXXC,
2014-03-25T15:32:34.158Z,Inbound Proxy Internal Send Connector,08D11605A575FB67,14,10.10.20.11:25496,10.10.10.11:25,<,250-8BITMIME,
2014-03-25T15:32:34.158Z,Inbound Proxy Internal Send Connector,08D11605A575FB67,15,10.10.20.11:25496,10.10.10.11:25,<,250-BINARYMIME,
2014-03-25T15:32:34.158Z,Inbound Proxy Internal Send Connector,08D11605A575FB67,16,10.10.20.11:25496,10.10.10.11:25,<,250-XXXXXXXD,
2014-03-25T15:32:34.158Z,Inbound Proxy Internal Send Connector,08D11605A575FB67,17,10.10.20.11:25496,10.10.10.11:25,<,250-XXXXXXE,
2014-03-25T15:32:34.158Z,Inbound Proxy Internal Send Connector,08D11605A575FB67,18,10.10.20.11:25496,10.10.10.11:25,<,250-XXXXF,
2014-03-25T15:32:34.158Z,Inbound Proxy Internal Send Connector,08D11605A575FB67,19,10.10.20.11:25496,10.10.10.11:25,<,250 XXXXXXXXXXXXXG,
2014-03-25T15:32:34.158Z,Inbound Proxy Internal Send Connector,08D11605A575FB67,20,10.10.20.11:25496,10.10.10.11:25,*,,"EHLO options between current server and proxy target do not match : Chunking, Xrdst. Critical non
matching options : Chunking, Xrdst. Failing over."
2014-03-25T15:32:34.158Z,Inbound Proxy Internal Send Connector,08D11605A575FB67,21,10.10.20.11:25496,10.10.10.11:25,>,QUIT,
2014-03-25T15:32:34.158Z,Inbound Proxy Internal Send Connector,08D11605A575FB67,22,10.10.20.11:25496,10.10.10.11:25,<,221 2.0.0 Service closing transmission channel,
2014-03-25T15:32:34.158Z,Inbound Proxy Internal Send Connector,08D11605A575FB67,23,10.10.20.11:25496,10.10.10.11:25,-,,Local
Can anyone help? I'm at the end of my Googling!

The answer has been found. In our case, we had to disable the Mailguard feature of the Cisco ASA between the CAS subnet and the MBX subnet. Essentially it was stripping AUTH commands from the SMTP handshake which meant the servers could not authenticate
to each other and establish a secured connection.
I guess for future reference, if you're getting a PRX4 error code you should look at any device that could be inspecting SMTP between your CAS and MBX servers.
This Microsoft KB article has more information: http://support.microsoft.com/kb/320027

Temporary server error message in Mail

I cannot send or receive mail from my Mail application.
When I open mail and it tries to connect I ge this mesage
Mail could not log in to the account “MAC” because of a temporary server error. Try again later.
The server returned the error: Service Temporarily Unavailable
Any ideas?

Mail> preferences> Accounts > Account Information. Check to see if the defunct account is listed

The server response was: 4.7.0 Temporary server error. Please try again later. PRX3

Hello,
I just setup an exchange 2013 server with hosted with the same machine of Active Domain Controller.
I tested the connectivity of the server , i found that the mailbox can only send email to external mailbox however it cant receive any mail neither from external mail nor internal mail.
I ran a test from exchange connectivity analyzer for inbound mail and it failed with the following message.
The server returned status code 451 - Error in processing. The server response was: 4.7.0 Temporary server error. Please try again later. PRX3
I did a search on this forum and found the following thread
social.technet.microsoft.com/Forums/exchange/en-US/288e1619-ce56-4c3a-8bb1-4886835520fe/delivery-fails-the-server-response-was-470-temporary-server-error-please-try-again-later?forum=exchangesvrdeploy
but no luck , i dont know how to set an alternative host, would somebody please help.
error details:
Message: Error in processing. The server response was: 4.7.0 Temporary server error. Please try again later. PRX3
Type: System.Net.Mail.SmtpException
Stack trace:
at System.Net.Mail.DataStopCommand.CheckResponse(SmtpStatusCode statusCode, String serverResponse)
at System.Net.Mail.DataStopCommand.Send(SmtpConnection conn)
at System.Net.Mail.SmtpClient.Send(MailMessage message)
at Microsoft.Exchange.Tools.ExRca.Tests.SmtpMessageTest.PerformTestReally()
The server returned status code 451 - Error in processing. The server response was: 4.7.0 Temporary server error. Please try again later. PRX3
Exception details:
Message: Error in processing. The server response was: 4.7.0 Temporary server error. Please try again later. PRX3
Type: System.Net.Mail.SmtpException
Stack trace:
at System.Net.Mail.DataStopCommand.CheckResponse(SmtpStatusCode statusCode, String serverResponse)
at System.Net.Mail.DataStopCommand.Send(SmtpConnection conn)
at System.Net.Mail.SmtpClient.Send(MailMessage message)
at Microsoft.Exchange.Tools.ExRca.Tests.SmtpMessageTest.PerformTestReally()
Elapsed Time: 3107 ms.
The server returned status code 451 - Error in processing. The server response was: 4.7.0 Temporary server error. Please try again later. PRX3
Exception details:
Message: Error in processing. The server response was: 4.7.0 Temporary server error. Please try again later. PRX3
Type: System.Net.Mail.SmtpException
Stack trace:
at System.Net.Mail.DataStopCommand.CheckResponse(SmtpStatusCode statusCode, String serverResponse)
at System.Net.Mail.DataStopCommand.Send(SmtpConnection conn)
at System.Net.Mail.SmtpClient.Send(MailMessage message)
at Microsoft.Exchange.Tools.ExRca.Tests.SmtpMessageTest.PerformTestReally()
Elapsed Time: 3107 ms.

Thanks god, finally i found the solution :) , i can go to sleep
i added my ad domain name to the host table then all the problems are solved!!!
source
http://www.techieshelp.com/exchange-2013-451-4-7-0-temporary-server-error-please-try-again-later-prx5/

451 4.7.0 Temporary server error. Please try again later. PRX5

I've noticed that on occassion when I connect to my Exchange 2013 CU 1 server, the server will respond with "451 4.7.0 Temporary server error. Please try again later. PRX5" after I submit an e-mail for delivery. It accepts the sender, verifies
the recipient, asks for data and fails only upon submission. Trying again right after the failure usually takes care of the problem what that's not a fix. What's causing the problem? Anyone else seen this?

whohoo, i FINALLY figured it out - and what can i say? the cause was another hickup of the ECP, i would call it a bug but what do i know? ;)
turns out that ex2013 has huge problems when you leave the DNS lookups setting in the server properties to "All network adapters", instead you should select a specific NIC or enter the IPs of your DNS servers manually. well, this is mentioned in numerous threads
all over the forums and obviously for many people, that was the solution.
BUT...i still had no mail flow after setting the DNS servers manually and my logs still filled up with DNS errors. in the end it turned out that the setting in the ECP only configures the transport service, but NOT the the frontend transport service. you can
easily check this with get-transportservice and get-frontendtransportservice and looking at the ExternalDNS and InternalDNS settings...sure enough, for me only the Transport Service had the configuration applied that i set in the ECP.
so, i configured set-frontendtransportservice with the same DNS settings as the transport service, and finally my mailflow is working...i can hardly believe it, and i can't believe that i found literally nothing about this behavior/bug of the ECP on the net.
so, this is my solution - maybe it helps someone else :)

451 4.7.0 Temporary server error. Please try again later. PRX2

I'm getting the dreaded "
451 4.7.0 Temporary server error. Please try again later. PRX2
" error when receiving SMTP mail.
does anyone know exactly what causes this error? there are many references to it on the web, but nobody seems to know exactly what causes it. maybe it's something to do with DNS?
can someone please ask someone on the exchange team to help document this?

Option A works for me...
Important: DNS Lookup issues
may prevent or delay message delivery or cause items to sit in OWA Drafts folder (7/22)
I’ve been following a thread on this since CU1\April but just now getting around to post it here, sorry for the delay if you’ve hit this issue
Tony Redmond’s also covered this on his blog here:http://thoughtsofanidlemind.wordpress.com/2013/03/25/exchange-2013-dns-stuck-messages/
In some environment message delivery will fail with the following error or be delayed by many seconds or minutes.
451 4.7.0 Temporary server error. Please try again later. PRX5
Threads on MS TechNet Forums: http://bit.ly/14A1JQY &http://bit.ly/13UG1ks
Quick Fix:
Option A: Set the NIC to use for “External DNS lookups” in EAC under Servers
Option B: Set ExternalDNSAdapterEnabled and InternalDNSAdapterEnabled to $false and set DNS servers on ExternalDNSServers and InternalDNSServers with the Set-FrontendTransportService command
Others have used a host file with the Exchange 2013 servers in it, but the above method is easier to manage

Help! "4.7.0 Temporary server error. Please try again later. PRX4"

I am in the process of migrating a single Exchange 2013 install (CAS+MBX co-located) to two separate installs, a CAS and MBX server. Mail has been flowing in via my new CAS for around a week now, I had altered DNS and IPs for this. Yesterday I migrated
the last mailboxes off the old server and then un-installed Exchange, which appeared to happen cleanly and without issue. I am now facing an issue where my CAS server will not receive emails, reporting "4.7.0
Temporary server error. Please try again later. PRX4" when I try to send an email. If I send emails directly to the MBX server, they arrive without issue.
This was working before I removed the old Exchange server. Any ideas? I'm really stuck here.

Hello,
Please use the following test tool to check the root cause:
https://testconnectivity.microsoft.com/
Thanks,
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact
[email protected]
Simon Wu
TechNet Community Support

451 4.4.3 Temporary server error. Please try again later ATT3.1

I currently have Exchange 2007 and 2010 in my organization with all of the mailboxes located on 2010. 2007 exists solely because our ILM2007 still provisions the accounts to 2007 first, and then we migrate those mailboxes to 2010. Last week, we setup Office
365 in hybrid mode, and have our MX records pointed at O365. We do not have any problem with inbound email arriving in users on-premises mailboxes. For the most part, we do not have any problem with outbound email, except to other Office 365 domains.
Email messages sent to domains that have MX records pointing at O365 all sit in the queue pending deliver with the subject error, and are ultimately returned to the user with an NDR. I've verified everything that I know of, but have been unable to correct
this issue. Help?
-Richard

Hi Richard,
I recommend you refer to the following similar thread and check if any helps:
http://community.office365.com/en-us/f/158/t/271032.aspx
In addition, I recommend you post this in Office 365 forum
also, as they should have
more professional knowledge on troubleshooting Office 365 issue and you may
get effective solution timely.
Best regards,
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected]
Niko Cheng
TechNet Community Support

Temporary Server Error

Similar Messages

Maybe you are looking for