Quantcast
Channel: Exchange Server 2013 - Setup, Deployment, Updates, and Migration 论坛
Viewing all 7008 articles
Browse latest View live

Exchange 2013 setup progress error step 7 of 14:mailbox role:Transport service

$
0
0

Error

The following error was generated when "$error.Clear();

      if ($RoleStartTransportservice)

      {

           start-SeetupService-ServiceName FMS

      }

      "was run: "Service 'FMS' failed to reach status 'Running' on this server.".

i am running windows 2012R2 on vmware / hyper-v

getting the same error on both.

anybody please,any idea,what am i missing 


sturbon install 2010

$
0
0

heres my install msg exchagne 2010 on and server 2012 r2 domain.

i dont want to reload the DC but its looking more and more like im going to have to ..

length of the access control list exceed the allowed

and heres the last part of the exchange setup logs

05/29/2015 22:15:05.0523] [1] [ERROR] The following error was generated when "$error.Clear();
          if ($RolePrepareAllDomains)
          {
              initialize-DomainPermissions -AllDomains:$true -CreateTenantRoot:($RoleIsDatacenter -or $RoleIsPartnerHosted);
          }
          elseif ($RoleDomain -ne $null)
          {
              initialize-DomainPermissions -Domain $RoleDomain -CreateTenantRoot:($RoleIsDatacenter -or $RoleIsPartnerHosted);
          }
          else
          {
              initialize-DomainPermissions -CreateTenantRoot:($RoleIsDatacenter -or $RoleIsPartnerHosted);
          }
        " was run: "Length of the access control list exceed the allowed maximum.".
[05/29/2015 22:15:05.0523] [1] [ERROR] Length of the access control list exceed the allowed maximum.
[05/29/2015 22:15:05.0523] [1] [ERROR-REFERENCE] Id=DomainGlobalConfig___27a706ffe123425f9ee60cb02b930e81 Component=EXCHANGE14:\Current\Release\Shared\Datacenter\Setup
[05/29/2015 22:15:05.0539] [1] Setup is stopping now because of one or more critical errors.
[05/29/2015 22:15:05.0539] [1] Finished executing component tasks.
[05/29/2015 22:15:05.0570] [1] Ending processing Install-ExchangeOrganization
[05/29/2015 22:19:55.0793] [0] End of Setup
[05/29/2015 22:19:55.0793] [0] **********************************************

bending my head over this one.. yes i have been all over google.. and get the same soulition and well it doesnt work for me..

or maybe im doing something wrong..

Stuck Migration 2007 -> 2013

$
0
0
Hello,

I need assistance with configuring our environment for co-existence.  I am following the following steps without any luck: http://www.msexchange.org/articles-tutorials/exchange-server-2013/migration-deployment/planning-and-migrating-small-organization-exchange-2007-2013-part13.html

Our Environment: 

Exchange 2007 AD Computer Name: mail.xbb.local
DNS Entry: mail.xbb.local  10.0.1.2  (only DNS entry - no additional DNS entries for autodiscover)
(all internal)
AutoDiscover URI: https://mail.xbb.local/AutoDiscover/AutoDiscover.xml
OWA: https://mail.xbb.local/OWA
OAB: https://mail.xbb.local/OAB
EWS: https://mail.xbb.local/EWS/Exchange.asmx
Active-Sync Internal: https://mail.xbb.local/Microsoft-Server-ActiveSync
Active-Sync External: https://ll.xbb.local/Microsoft-Server-ActiveSync


Exchange 2013 AD Computer Name: exchange.xbb.local
DNS Entry: exchange.xbb.local   10.0.1.3

Steps taken:

Created Certificate on Exchange 2013 server for 2013-2007 server co-existence

change AutoDiscover SCP on Exchange 2013 to https://mail.xbb.local/AutoDiscover/AutoDiscover.xml

Changed all URL's on Exchange 2013 to match 2007:

OWA: https://mail.xbb.local/OWA
OAB: https://mail.xbb.local/OAB
EWS: https://mail.xbb.local/EWS/Exchange.asmx
Active-Sync Internal: https://mail.xbb.local/Microsoft-Server-ActiveSync
Active-Sync External: https://ll.xbb.local/Microsoft-Server-ActiveSync

After changing URL's, I enabled co-existence certificate on 2007.

Created Legacy DNS entry: legacy.xbb.local   10.0.1.2

Changed URLs: 

OWA: https://legacy.xbb.local/OWA
OAB: https://legacy.xbb.local/OAB
EWS: https://legacy,xbb.local/EWS/Exchange.asmx
Active-Sync Internal: https://legacy.xbb.local/Microsoft-Server-ActiveSync

Changed MAIL DNS Entry to 10.0.1.3  (only 1 DNS entry - used for AutoDiscover and Exchange 2007 Server AD name!)

Added legacy.xbb.local as 10.0.1.2 (same IP shared as Exchange 2007 AD Computer Name - Mail)

I am running into issues with connecting to 2007 mailboxes after making this change.  

What do I need to do differently since the same mail.xbb.local is shared as the Exchange 2007 Computer name and AutoDiscover?

Any help will be appreciated.

Thank you,

unified communications managed api 4.0 hash value is not correct

$
0
0
I keep receiving this error when trying to install Microsoft Unified Communications Managed API4.0: Microsoft Unified Communications Managed API 4.0 i get The hash value is not correct! There is no other instance of Microsoft Unified Communications Managed API installed. Thanks in advance.

Exchange 2013: Content Index State Failed

$
0
0

I am running two, two node DAG's with Exchange 2013.

One DAG pair is running 5 databases with Server 2012 Standard and the second DAG pair is running Server 2008 R2 SP1 Standard with a single shared database.

No matter what I try, ALL 6 databases show "ContentIndexState: Failed" with "ContentIndexErrorMessage: An internal error occurred for the database or its index.".

I have tried rebuilding the indexes manually, automatically and manually copying the database files between servers.  I also receive errors when trying to failover the databases because the content index state is failed.

In my test environment I have a very similar setup working fine with no issues.

Please let me know what I can try to get this resolved.

The error I receive when running the following set of commands is:

suspend-MailboxDatabaseCopy dag2db1\mbox1

update-MailboxDatabaseCopy dag2db1\mbox1 -deleteexistingfiles

[PS] C:\Windows\system32>update-mailboxdatabasecopy dag2db1\mbox1 -deleteexistingfiles

Confirm
Are you sure you want to perform this action?
Updating database copy DAG2DB1\MBOX1 on server MBOX1
[Y] Yes  [A] Yes to All  [N] No  [L] No to All  [?] Help (default is "Y"): a
WARNING: Seeding of content index catalog for database 'DAG2DB1' failed. Please verify that the Microsoft Search (Exchange) and the Host Controller service for Exchange services are running and try the operation again. Error: Therevwas no endpoint listening at net.tcp://localhost:17063/Management/SeedingAgent-0A2745DF-4522-42AB-9115-5DDE9EDEF1C612/Single that could accept the message. This is often caused by an incorrect address or SOAP action. See InnerException, if present, for more details..
[PS] C:\Windows\system32>

Mailbox move stuck

$
0
0

Hello,

I'm trying to move mailboxes from Exchange 2007 to 2013. The move request seems to be stuck in the "Syncing" mode.
Exchange 2007 environment consists of CAS and MBX servers, Exchange 2013 has both roles on the same machine.
Mail traffic between servers, to/from internet works without issues.
Where would I start to troubleshoot it?

Thanks.


Memento Mori


Unable to access ECP/OWA

$
0
0

I installed Exchange 2013 on 2 brand new Server 2012 virtual machines, one with the mailbox role and another with the CAS roles. The installation completed without errors but I cannot log on to the ECP (or OWA for that matter). As I enter my user/pass, the password field goes blank and a number of event log entries are added (see below).

I'm using the default administrator account (also Enterprise Admin, Domain Admin and member of the Organization Management security groups). I mail-enabled the account with enable-mailuser + enable-mailbox. I can execute Exchange Powershell cmdlets when logged on with this account, so security looks good.

The problem is OWA/ECP which consistenly logs the following errors when I attempt to access the OWA:

[Ecp] An internal server error occurred. The unhandled exception was: System.Security.Cryptography.CryptographicException: Invalid provider type specified.

   at System.Security.Cryptography.Utils.CreateProvHandle(CspParameters parameters, Boolean randomKeyContainer)

   at System.Security.Cryptography.Utils.GetKeyPairHelper(CspAlgorithmType keyType, CspParameters parameters, Boolean randomKeyContainer, Int32 dwKeySize, SafeProvHandle& safeProvHandle, SafeKeyHandle& safeKeyHandle)

   at System.Security.Cryptography.RSACryptoServiceProvider.GetKeyPair()

   at System.Security.Cryptography.X509Certificates.X509Certificate2.get_PrivateKey()

   at Microsoft.Exchange.HttpProxy.FbaModule.ParseCadataCookies(HttpApplication httpApplication)

   at Microsoft.Exchange.HttpProxy.FbaModule.OnBeginRequestInternal(HttpApplication httpApplication)

   at Microsoft.Exchange.HttpProxy.ProxyModule.<>c__DisplayClassa.<OnBeginRequest>b__9()

   at Microsoft.Exchange.Common.IL.ILUtil.DoTryFilterCatch(TryDelegate tryDelegate, FilterDelegate filterDelegate, CatchDelegate catchDelegate)

---------------------------------------------------------------------

[Owa] An internal server error occurred. The unhandled exception was: System.Security.Cryptography.CryptographicException: Invalid provider type specified.

   at System.Security.Cryptography.Utils.CreateProvHandle(CspParameters parameters, Boolean randomKeyContainer)

   at System.Security.Cryptography.Utils.GetKeyPairHelper(CspAlgorithmType keyType, CspParameters parameters, Boolean randomKeyContainer, Int32 dwKeySize, SafeProvHandle& safeProvHandle, SafeKeyHandle& safeKeyHandle)

   at System.Security.Cryptography.RSACryptoServiceProvider.GetKeyPair()

   at System.Security.Cryptography.X509Certificates.X509Certificate2.get_PrivateKey()

   at Microsoft.Exchange.HttpProxy.FbaModule.ParseCadataCookies(HttpApplication httpApplication)

   at Microsoft.Exchange.HttpProxy.FbaModule.OnBeginRequestInternal(HttpApplication httpApplication)

   at Microsoft.Exchange.HttpProxy.ProxyModule.<>c__DisplayClassa.<OnBeginRequest>b__9()

   at Microsoft.Exchange.Common.IL.ILUtil.DoTryFilterCatch(TryDelegate tryDelegate, FilterDelegate filterDelegate, CatchDelegate catchDelegate)

---------------------------------------------------------------------------

Event code: 3005

Event message: An unhandled exception has occurred.

Event time: 28/11/2012 0:47:38

Event time (UTC): 27/11/2012 23:47:38

Event ID: 12c0aac14e0c45b093e860f6699b0d76

Event sequence: 4

Event occurrence: 3

Event detail code: 0

Application information:

    Application domain: /LM/W3SVC/1/ROOT/Rpc-2-129985330412727995

    Trust level: Full

    Application Virtual Path: /Rpc

    Application Path: C:\Program Files\Microsoft\Exchange Server\V15\FrontEnd\HttpProxy\rpc\

    Machine name: <cleaned up>

Process information:

    Process ID: 4848

    Process name: w3wp.exe

    Account name: NT AUTHORITY\SYSTEM

Exception information:

    Exception type: HttpException

    Exception message: The client disconnected.

   at Microsoft.Exchange.HttpProxy.ProxyRequestHandler.EndProcessRequest(IAsyncResult result)

   at System.Web.HttpApplication.CallHandlerExecutionStep.OnAsyncHandlerCompletion(IAsyncResult ar)

Request information:

    Request URL: http://<cleaned up>/rpc/rpcproxy.dll?688b9c54-fc83-47a6-bf82-343799d288d5@falcora.net:6001

    Request path: /rpc/rpcproxy.dll

User host address: fe80::d58e:d780:34ed:af68C:\Program Files\Microsoft\Exchange Server\V15\FrontEnd\HttpProxy\rpc\

    User: FALCORA\SM_29bd07d0480e4b41a

    Is authenticated: True

    Authentication Type: NTLM

    Thread account name: NT AUTHORITY\SYSTEM

Thread information:

    Thread ID: 18

    Thread account name: NT AUTHORITY\SYSTEM

    Is impersonating: False

    Stack trace:    at Microsoft.Exchange.HttpProxy.ProxyRequestHandler.EndProcessRequest(IAsyncResult result)

   at System.Web.HttpApplication.CallHandlerExecutionStep.OnAsyncHandlerCompletion(IAsyncResult ar)

 

I have spent hours wading through log files and posts, and cannot get my head around this one. 

Removing a dead Exchange Server from my Domain

$
0
0

Hello,

I have a dead Exchange Server 2003 which was installed on Windows 2000 Advanced Server.  I would like to remove it from my domain which consisted of Windows 2003 Server also.  How do I go about doing that since i'm upgrading  my domain to 2008 & 2013 Servers?

Thanks for any suggestions you may make.


Exchange 2013 fails multiple times during installs.

$
0
0

I am trying to install Exchange 2013 on server 2012 R2 standard. After going through the prerequisites I still fail on step 7. The error is listed below. I have uninstalled it and used adsiedit to remove mailboxes and database. I have read through the suggested fixes for this issue, most stem from around 2013. I'm wondering if anyone else has ran into this issue? Thank you in advance!

Error:
The following error was generated when "$error.Clear();
            if ($RoleProductPlatform -eq "amd64")
            {
                $useAttachMode = $false;
                $fastInstallConfigPath = Join-Path -Path $RoleBinPath -ChildPath "Search\Ceres\Installer";
                $command = Join-Path -Path $fastInstallConfigPath -ChildPath "InstallConfig.ps1";
                $fastDefaultDataFolderPath = Join-Path -Path $RoleBinPath -ChildPath "Search\Ceres\HostController\Data";
                $dataFolderPath = $fastDefaultDataFolderPath;
               
                if ([System.IO.Directory]::Exists($fastDefaultDataFolderPath))
                {
                    $useAttachMode = $true;
                }
                else
                {
                    if ($RoleIsDatacenter -eq $true)
                    {
                        $preferredDataFolderPathRoot = "D:\";
                        if ([System.IO.Directory]::Exists($preferredDataFolderPathRoot))
                        {
                            $dataFolderPath = Join-Path -Path $preferredDataFolderPathRoot -ChildPath "ExchangeSearchData";
                            if ([System.IO.Directory]::Exists($dataFolderPath))
                            {
                                $useAttachMode = $true;
                            }
                        }
                    }
                }
               
                if ($useAttachMode -eq $true)
                {
                    &$command -action a -dataFolder $dataFolderPath -silent;
                }
                else
                {
                    try
                    {  
                        &$command -action i -dataFolder $dataFolderPath -silent;
                    }
                    catch
                    {
                        $errorMsg = "Failure running SearchFoundation installconfig.ps1 - " + $_.Exception.Message;
                        Write-ExchangeSetupLog -Error $errorMsg;
                        &$command -action u -silent;
                        try
                        {
                            if ([System.IO.Directory]::Exists($dataFolderPath))
                            {
                                [System.IO.Directory]::Delete($dataFolderPath, $true);
                            }
                        }
                        catch
                        {
                            $deleteErrorMsg = "Failure cleaning up SearchFoundation Data folder. - " + $dataFolderPath+ " - " +

$_.Exception.Message;
                            Write-ExchangeSetupLog -Error $deleteErrorMsg;
                        }
                    }
                }
            }
        " was run: "Failure running SearchFoundation installconfig.ps1 - Error occurred while configuring Search Foundation for

Exchange.System.TypeLoadException: Could not load type 'System.Runtime.Diagnostics.ITraceSourceStringProvider' from assembly

'System.ServiceModel.Internals, Version=4.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35'.
   at System.ServiceModel.Channels.BinaryMessageEncoderFactory..ctor(MessageVersion messageVersion, Int32 maxReadPoolSize, Int32

maxWritePoolSize, Int32 maxSessionSize, XmlDictionaryReaderQuotas readerQuotas, Int64 maxReceivedMessageSize, BinaryVersion version,

CompressionFormat compressionFormat)
   at System.ServiceModel.Channels.BinaryMessageEncodingBindingElement.CreateMessageEncoderFactory()
   at System.ServiceModel.Channels.TransportChannelFactory`1..ctor(TransportBindingElement bindingElement, BindingContext context)
   at System.ServiceModel.Channels.ConnectionOrientedTransportChannelFactory`1..ctor(ConnectionOrientedTransportBindingElement bindingElement,

BindingContext context, String connectionPoolGroupName, TimeSpan idleTimeout, Int32 maxOutboundConnectionsPerEndpoint, Boolean

supportsImpersonationDuringAsyncOpen)
   at System.ServiceModel.Channels.TcpTransportBindingElement.BuildChannelFactory[TChannel](BindingContext context)
   at System.ServiceModel.Channels.Binding.BuildChannelFactory[TChannel](BindingParameterCollection parameters)
   at System.ServiceModel.Channels.ServiceChannelFactory.BuildChannelFactory(ServiceEndpoint serviceEndpoint, Boolean useActiveAutoClose)
   at System.ServiceModel.ChannelFactory.CreateFactory()
   at System.ServiceModel.ChannelFactory.OnOpening()
   at System.ServiceModel.Channels.CommunicationObject.Open(TimeSpan timeout)
   at System.ServiceModel.ChannelFactory.EnsureOpened()
   at System.ServiceModel.DuplexChannelFactory`1.CreateChannel(InstanceContext callbackInstance, EndpointAddress address, Uri via)
   at Microsoft.Ceres.HostController.WcfClient.WcfHostControllerClient.CreateProxy()
   at Microsoft.Ceres.HostController.WcfClient.WcfHostControllerClient.get_HostController()
   at Microsoft.Ceres.Exchange.PostSetup.HostControllerManager.ConnectHost(Uri uri, Boolean secure, String userIdentity, Int16 timeoutInSeconds)
   at Microsoft.Ceres.Exchange.PostSetup.DeploymentManager.DeployAdminNode(String installDirectory, String localHostControllerNetTcpUrl, Int32

hostControllerPort)
   at Microsoft.Ceres.Exchange.PostSetup.DeploymentManager.Install(String installDirectory, String dataDirectoryPath, Int32 basePort, String

logFile, Boolean singleNode, String systemName, Boolean attachedMode)
   at CallSite.Target(Closure , CallSite , Type , Object , Object , Object , Object , Object , Object , Boolean )".

 

Exchange 2013 invalid

$
0
0

I am configuring an Exchange 2013 server that we intend to use for our Office 365 hybrid onsite environment. I am having a bit of trouble with the certificate. When I run the Microsoft Remote Connectivity Analyzer, I find that the certificate name is invalid. Names Autodiscover.domain.tld and domain.tld are on the same server using the same certificate. Short of adding another IP or using wildcard certificate how do I fix this?

https://onedrive.live.com/redir?resid=5c08ce5d0589286f!840&authkey=!AM_P7xYKQpHvuPQ&ithint=file%2chtml

https://onedrive.live.com/redir?resid=5c08ce5d0589286f!841&authkey=!AGxkPdkZyvOpePI&ithint=file%2chtml

Powershell Down -> RBAC event 23 + ADAccess 4027

$
0
0

Hello,

I'm facing a strange problem with Exchange 2013 cu3 : powershell doesn't work anymore and I receive the following error when I open it :

New-PSSession : [srv.domain.local] Connecting to remote server srv.domain.local failed with the following
error message : The WinRM client received an HTTP server error status (500), but the remote service did not include
any other information about the cause of the failure. For more information, see the about_Remote_Troubleshooting Help
topic.
At line:1 char:1
+ New-PSSession -ConnectionURI "$connectionUri" -ConfigurationName Microsoft.Excha ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : OpenError: (System.Manageme....RemoteRunspace:RemoteRunspace) [New-PSSession], PSRemotin
   gTransportException
    + FullyQualifiedErrorId : WinRMHttpError,PSSessionOpenFailed

And in the event viewer, these events are loggued :

Event 23, MSExchange RBAC

(Process w3wp.exe, PID 4624) "Exchange AuthZPlugin Fails to finish method Microsoft.Exchange.Data.Directory.ADTopologyUnexpectedException: Unexpected error when calling the Microsoft Exchange Active Directory Topology service on server 'TopologyClientTcpEndpoint (localhost)'. Error details: Access is denied.. ---> System.ServiceModel.Security.SecurityAccessDeniedException: Access is denied.

Event 4027, MSExchange ADAccess

Process w3wp.exe (RemotePS-NoPro) (PID=4624). WCF request (Get Servers for domain.local) to the Microsoft Exchange Active Directory Topology service on server (TopologyClientTcpEndpoint (localhost)) failed. Make sure that the service is running. In addition, make sure that the network ports that are used by Microsoft Exchange Active Directory Topology service are not blocked by a firewall. The WCF call was retried 1 time(s). Error Details 
 System.ServiceModel.Security.SecurityAccessDeniedException: Access is denied.

All services are running and I can't delete and recrete POwershell virtual directory : it appears in IIS but when I try to list the powershell virtual directories, it can't find it.

Any ideas?

Best regards,

Jerry

How to publish friendly url with WAP?

$
0
0

So we have an exchange 2010 environment and have recently deployed 2 exchange 2013 servers.  We also have an ADFS3 farm- 2 ADFS servers, and 2 WAP (web proxy) servers.

We have published several exchange 2013 urls successfully via wap- for example,https://email.myschool.edu/owa works great.

However, the redirect from the "friendly" url of https://email.myschool.edu does not work via WAP.

Internally (not accessing via WAP) it works- https://email.myschool.edu redirects to an OWA login page-

https://email.myschool.edu/owa/auth/logon.aspx?replaceCurrent=1&url=https%3a%2f%2femail.myschool.edu%2fowa%2f

Externally (using WAP)- I get a 404. 

Solutions for this?

Exchange designing

$
0
0

Team,

I want to design and provide solution for exchange 2013 please help me. 

Complete design migration guide.

Autodiscover

$
0
0

Hi everebody

I have an issue im having a hard time fixing. The case is this. I have installed 2 exchange 2013 servers and have set up dag.  When I create a new user on the exchange 2013 server the first time the user logs on and start outlook client I get this


If I manual point to the new exchange server it works, so im struggling with finding out why my autodiscover won't work.

Metadata

  • Mailserver 1 exchange 2010 - Autodiscover URL = mail.domainname.com - Autodiscovervirtualdirectory = mail.domainname.com
  • Mail server 2 (New) Exchange 2013 CU8 Autodiscover URL = mail.domain.com Autodiscovervirtualdirectory = mailix.domainname.com
  • Mailserver 3 (New) Exchange 2013 Autodiscover URL = mail.domain.com Autodiscovervirtualdirectory = mailix.domainname.com
  • Outlook client is 2007

Please advise :(

Best regards

Martin


Exchange 2010 - EWS and disabling TLS 1.0

$
0
0

Hi all,

Due to the POODLE vulnerability and TLS 1.0 showing as enabled on one of our external scans, we were informed that we would need to disable SSL 3.0 and TLS 1.0 on our Exchange server.

Apparently, this wouldn't even be possible until Update Rollup 9 was released on 3/16/15:

Rollup resolves:

KB 3029667 SMTP is not transported over TLS 1.1 or TLS 1.2 protocol in an Exchange Server 2010 environment

After installing this update, SSL 3.0 and TLS 1.0 were disabled and the servers rebooted (cross site, same domain, two Exchange servers).  After resolving some issues with certificates that apparently broke as a result of the changes, we found that EWS was not working - the log full of these errors:

Process 5776: ProxyWebRequest CrossSite from S-1-5-21-3895483984-2032760896-3917300074-1259 tohttps://mail.exchange.com:443/ews/exchange.asmx failed. Caller SIDs: NetworkCredentials. The exception returned is Microsoft.Exchange.InfoWorker.Common.Availability.ProxyWebRequestProcessingException: System.Net.WebException: The underlying connection was closed: An unexpected error occurred on a send. ---> System.IO.IOException: Unable to read data from the transport connection: An existing connection was forcibly closed by the remote host.

------------------------------------------------------

The EWS directory in IIS on both servers are set to use Anonymous and Windows Authentication.  The main issues observed outside of the above errors was that free/busy information could not be viewed.

After rebuilding the EWS virtual directory and a couple reboots later, we tried enabling TLS 1.0 on both servers, rebooted, and there were no more EWS errors to be found - free/busy was also working.

So it appears that although this rollup allows SMTP to use TLS 1.1 or 1.2, EWS is still attempting to use TLS 1.0, and I don't see that it is possible to change this


http error 400 the size of the request headers is too long

$
0
0

We have Exchange 2010 SP3 with CU4 and Exchange 2013 CU8.
We switched the CAS from 2010 to 2013.
Most users can succesfull connect to OWA and Outlook.
Unfortunately some users get on OWA > http error 400 the size of the request headers is too long
And when they start Outlook > server is not available

I found this post > http://smtp4it.net/2013/12/05/exchange-2013-to-2007-outlook-anywhere-proxy-issue/ and some other technet artciles but they all mention Exchange 2003 or 2007.
Also I read 1000+ groups we not have nearly that amount of groups.

When i switch CAS back to 2010 user can succesfully open OWA.

In exchange 2013 server in httper folder/log i see

2015-06-03 08:30:08 10.212.119.31 31657 10.212.119.31 444 HTTP/1.1 RPC_IN_DATA /rpc/rpcproxy.dll?server1.contoso.com:6001 400 2 BadRequest MSExchangeRpcProxyAppPool

Please any guidance


when run setup exchange 2013 get [ERROR] "dс2.domain.root" isn't a valid SMTP domain.

$
0
0

found old installation exchange in DC.

Delete  with ADSIEdit:
CN=Microsoft Exchange
CN=Microsoft Exchange ... Objects
other path not found

but this not help me..

get error again: [ERROR] "dс2.domain.root" isn't a valid SMTP domain.

Where can I findthe problem?


System for new exchange server - clear with windows 2012 R2  standard

Error: The type initializer for 'Microsoft.Exchange.Configuration.Tasks.ThrottlingModule`1' threw an exception.

Exchange 2013 proxy configuration (WinHTTP?)

$
0
0

Having problems getting Exchange to support internal free/busy and inter-org mailbox migrations at the same time.  It looks like the Exchange 2013 powershell command (Set-ExchangeServer-Identityyourservername-InternetWebProxy) doesn't allow for a proxy bypass so that we can ensure all our local traffic stays local.   I've found many articles that indicate that this issue can be overcome in Exchange 2010 by modifying the proxy config associated with WinHTTP.... Unfortunately I'm unable to find any reference to Exchange 2013 using WinHTTP.   Can you provide insight into how a proxy bypass can be specified in Exchange 2013?

Here's the article that covers Exchange 2010.  Unfortunately no reference to Exchange 2013 in this article.   I'm hoping for some document from Microsoft that details proxy bypass for Exchange 2013 because I need to share this information with my client.

Configuring Proxy Settings for WinHTTP

Thank you in advance!

Exchange email account work with Office 365 at a same time

$
0
0

Hi support team,

I have a question about Exchange 2007 and Office 365.

We have Exchange 2007 to provide email service for our worldwide users.

One of our location would like to change use your Office 365 service.

For safety, they want us to keep their existings in Exchange server for a short period.

The problem was their domain will record to Office 365 for email server.

That means our Exchange server and Office 365 will share same domain in a short period for receiving emails.

This should have some conflicts because duplicate email address and their domain was registered in our DNS server.

It should caused our internal user cannot delivery emails to them.

Could you please help to check is it any setting or chance for Exchange and Office 365 work at the same time?

Thank you.

Best regards

Cary

Viewing all 7008 articles
Browse latest View live


<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>