Connecting to Exchange Server 2013 using IMAP command gives authenication error

Hello All,
My application (it is a C# code) connects to Microsoft exchange server 2013 using POP3 and IMAP, processes the emails, marks as read and move to particular folder if it is processed successfully else to an different folder. In this sometimes,
I am getting authentication failed error from IMAP however same mail is processed when it is executed next time. Few times it is processed with out error. I am not sure what is causing this issue.We are connecting to IMAP using tcpIMAP command.
This is the same application which we used with exchange server 2010 now we are upgrading to exchange server 2013. I have verified that the setting of exchange 2010 and 2013 are the same.
To verify the IMAP command I created a sample application using C# which will try to connect to IMAP service and log in to exchange server 2013; it fails to authenticate the user after connecting for few times and then it starts to authenticate
successfully then again fails for few times and then authenticates. I am not sure why this is happening.
Please suggest how can I resolve this.
Thank you, Santha

Since I've upgraded to Snow Leopard I've also moved from Entourage 2008 to Mail, iCal & Addressbook with the new Exchange support.
My company exchange server is Exchange 2007.
Mail works fine except the occasional Mail crash.
iCal worked fine the first two days and then it came with an error the it cannot connect to the Exchange server and asks me to type my email address again. Doesn't work so I need to put my exchange calendar in iCal in offline. But now there is no syncing with the Echange server.
This only occurs when I add a meeting request in iCal.
My Exchange administrator has reset my mailbox on the Exchange server.
This helped for about 4 hours. Now it's the same problem.
I have a feeling the when you setup your exchange account in Mail it uses different settings for Mail and iCal with the autoconfig.
Anybody has a solution? My Exchange admin cannot find any problems on his side. Do I need to make changes on my iCal client or do we need to wait for OS 10.6.1 ?

Similar Messages

Outlook 2013 not connect with Exchange server 2013 in internal network

Hello All,
I Have two Exchange server 2013 in our environment. Both server install mailbox and CAS role. After configure exchange server 2013, Outlook 2013 not connect in internal network. I have configure outlook manually. i tried by using the suggestion from blog
but not work. Outlook show that Server cannot connect/ server name could not be resolved. in outlook setting i also put exchange proxy setting. In exchange admin center i have changed the OWA, OAB, Auto discover name. But still not work.
I know that outlook can be connect from external by using ssl certificate and publish outlook anywhere but i did my configure from internal network.
Can you please suggest as soon as possible.
Thanks,
Parvez

Hi,
Firstly, I’d like to explain, same with external users, internal users use Outlook Anywhere to connect with Exchange server and use Autodiscover get all settings.
Thus, let’s try the following resolutions:
1. run the following command: get-clientaccessservice |fl autodiscoverserviceinternaluri
2. check if the host name in the above URL is in the DNS server and there is a DNS entry about the host name points to the proper IP address.
3. Check if the above host name is in your certificate.
Thanks,
Angela
Angela Shi
TechNet Community Support

Writing client app to connect to Exchange Server 2013 and set OOF for users on vacation

I am coding an C# app that should connect to Exchange Server 2013 on-premise (Servers Location is not in our Company). I`ve got an account (User and Pass) with readonly admin-rights for now and want to read and set OutOfOffice Objects for other users. I
decide to use EWS Managed API over Autodiscovery but I am bit confuse how
I tried to connect with "service.UseDefaultCredentials = true" and read contacts -> this code works:
try
            ExchangeService _service
= new ExchangeService(ExchangeVersion.Exchange2013_SP1);
            _service.Credentials
= new WebCredentials("service.exchange",
"1234", "domain");
            _service.TraceEnabled
= true;
            _service.TraceFlags
= TraceFlags.All; _service.UseDefaultCredentials
= true;
            _service.AutodiscoverUrl("[email protected]",
RedirectionUrlValidationCallback);
            foreach
(Contact contact in _service.FindItems(WellKnownFolderName.Contacts,
new ItemView(2)))
var test = contact;
        catch
(Exception exception)
            Console.WriteLine(exception);
After that I tried the same with _service.UseDefaultCredentials = false; got error -> "The Autodiscover service couldn't be located." I am not shure if this "direct log on" is the right way, On msdn I've read about "delegate access"
and "Impersonation" (NTLM and Basic Authentication) I'am a bit confused. Can anybody help me?

hi,
when you set a credential, you don't have to set the UseDefaultCredentials property (it is already updated).
For autodiscover, you should try to set the property EnableScpLookup to True if you are in the Exchange domain or it is known by the current domain.
Autodiscover uses a domain query (through Active Directory) and/or a dns query (this requires a DNS register for autodiscover.domain.net) to determine the access to the autodiscover service URI.
Regards,
Désiré GOVIN Refresh IT Solutions

Can ColdFusion 10 connects to Exchange Server 2013?

There are lots of forums and chats about ColdFusion 10 connecting to Exchange Server 2010. Does anybody knows whether ColdFusion 10 can connects to Exchange Server 2013. If you do know, what are the steps involved? I have tried all the tricks used in ColdFusion 10 connecting to Exchange Server 2010 and still cannot connect to Exchange Server 2013.

Found a solution. Yes you can connect ColdFusion 10 to Exchange Server 2013 but there is a slight twist to the solution if you want to use cfexchangeXXXXX functionalities.
1. Ensure that you have imported the Exchange Server 2013 certificate into ColdFusion 10 server.
2. When calling cfexchangeconnection, add:
serverversion="2010"
Protocol="https"
formbasedauthentication="TRUE"
formbasedauthenticationURL="XXXXXX"
If serverversion is missing, it will default to 2007 server.

Implementing HA for On-Premise Exchange Server 2013 using Azure

Hi!
I want to implement Exchange 2013 high availability using Azure.
I have an on-premise multirole Exchange 2013 server and I am wondering if I can implement High Availability for example configuring a DAG with an Exchange Server 2013 running in a virtual machine in Azure.
What is the best option?
Thanks in advance,
Cristian L Ruiz

Hi!
I want to implement Exchange 2013 high availability using Azure.
I have an on-premise multirole Exchange 2013 server and I am wondering if I can implement High Availability for example configuring a DAG with an Exchange Server 2013 running in a virtual machine in Azure.
What is the best option?
Thanks in advance,
Cristian
Cristian L Ruiz
Not supported yet
http://blogs.technet.com/b/exchange/archive/2013/08/07/database-availability-groups-and-windows-azure.aspx
Twitter!:
Please Note: My Posts are provided “AS IS” without warranty of any kind, either expressed or implied.
Your answer is incorrect for my question. The link you gave is for a implementation of 2 datacenters using Azure as the wittness server, and that is not possible because you can make only 1 site-to-site VPN connection to Azure and having 2 datacenters you
would need 2 of them.
But my scenario is different, I have 1 datacenter and I want to use Azure as my 2nd datacenter for Exchange and for my witness server. I suppose that using the only 1 site-to site VPN that Azure provides is enough for that situation, but, the question is....
Is there any issue with that scenario? Did anyone try it?
Thanks
Cristian L Ruiz

Exchange Server 2013 Missing file on ISO install Error Code 1603

Hi all, a mystery needs solving any suggestions much appreciated:
We are trying to install Exchange Server 2013 on Windows 2012 server.
The ISO File being used is: SW_DVD9_Exchange_Svr_2013w_SP1_MultiLang_Std_Ent_MLF_X19-35118
All preparation and requisites in place.
During Stage 2 Copying files, we receive an error code 1603 and installation halts.
The error states:
Installing product F:\exchangeserver.msi failed. Fatal error during installation. Error code is 1603. Last error reported by the MSI package is 'Source file not found: F:\Setup\ServerRoles\ClientAccess\Owa\prem\version\resources\themes\base\0\microsoft.o365.controls.timeline.mouse.css.
Verify that the file exists and that you can access it.'.
We have verified that the Path in the error is correct and exists BUT the file is not present within the 0 folder.
We have downloaded the ISO from our Action Pack resources twice and attempted 4 separate installations.
We have tried both Mailbox/Client Access and Mailbox only installations.
The missing file: microsoft.o365.controls.timeline.mouse.css. Hopefully the only file misisng???
Any ideas anyone, could we source a different ISO or copy of the file or ?????
Many thanks in advance

Had the same issue with Exchange 2013 SP 1 Downloaded as an ISO from the Volume License Center, installing on a new Server 2012R2 STD box. I found the equivalent file in another ISO but discovered it was just an empty CSS file. So the easiest way is to not
bother trying to find the file but: 1) open notepad, 2) set save to "All Files", and 3) save an empty CSS file with that filename then place it in the directory indicated in the path given in the error. (Make sure it saves as
a CSS and not as a TXT.)
I reran the install and it completed without issue.

RV 220W connect to exchange server 2013

Hello,
i want to send remote protocol to my own Exchange Server.
There is no working with "Login Plan" or "Cram-MD5".
Error:
[rv220w][System][PLATFORM] dbRecordValueGet failed for toAddr column
Is there a solution?
Thank you!

Hello,
i want to send remote protocol to my own Exchange Server.
There is no working with "Login Plan" or "Cram-MD5".
Error:
[rv220w][System][PLATFORM] dbRecordValueGet failed for toAddr column
Is there a solution?
Thank you!

Windows Server 2012 R2 with Exchange Server 2013 SP1 Completely fresh install giving errors signing into EAC

Hi,
I am struggling with a completely clean installation of Server 2012 R2 and Exchange 2013 SP1. I followed these steps:
Installed Server OS
Windows Updates
Added Active Directory Role (This is a single standalone server that would have been SBS until it was dropped)
Added DHCP & DNS
Added Certificate Services
Added Windows Server Update Services (WID Database & WSUS Services)
Windows Updates
Added Media Foundation
Added File Server Resource Manager and Work Folders
Added Windows Server Backup
Windows Updates
Checked all running without errors in Server Manager and performed a full bare bones backup.
Ran Setup.exe from Exchange 2013 SP1 disc.
Installed Pre-requisites and then rebooted
Windows Updates
Ran Setup.exe from Exchange 2013 SP1 disc.
Installation completed without errors
Rebooted
Checked all running without errors in Server Manager.
I Launch Exchange Administrative Center and get "problem with website's server certificate error" (normal on machine with self-assigned certificates). Click Continue to Website and get:
Windows Security dialog box:
iexplore - "The server localhost is asking for your username and password. The server reports that it is from Digest"
however no username and password combination will work: have tried [Administrator]; [Domain\Administrator] even created a user to no avail.
I believe the issue is somewhere in the IIS configuration because I also get the same error when trying to log into the server website from either the server or another machine on the network.
I have tried the complete installation three times now: (full disclosure not all of the same features/roles each time). On the first attempt I got this error immediately and on try number 2 was able to get into the EAC and created the mailboxes
but then it started giving the same error. The above steps are try number 3.
Any ideas?
Thanks in advance.
Andy Halford
P.S. A Follow up which might be significant: The Default Web Site is not running and will not start (it was previously running before the Exchange installation) and when I try I get the message that Another Website may be using the same port however none
of the others (Exchange Back End or WSUS Administration) are using ports 80 or 443 and I still get the error when they are both stopped.

Could you post the list of sites:
appcmd list site
The ones listening on port 80:
appcmd list site /bindings:http/*:80:
And on port 443:
appcmd list site /bindings:https/*:443:
Step by Step Screencasts and Video Tutorials

Exchange Server 2013 // MFCMAPI could connect with errors

While connecting with Exchange Server 2013 I have started facing problem with my application.
My application fails to connect to Exchange with below parameters, then i have tried using MFCMAPI to if everything is okay. MFCMAPI could connect with above errors.
And I have tried with program using below parameters, i still get network error from MAPI call. Can you kindly help, I can provide any additional
details needed.
___ props[prop_count].ulPropTag = PR_PROFILE_UNRESOLVED_NAME;
    props[prop_count].Value.lpszA   = <ProfileUnresolvedName>;
    prop_count++;
    props[prop_count].ulPropTag     = PR_PROFILE_UNRESOLVED_SERVER;
    props[prop_count].Value.lpszA   = <[email protected]>;
    prop_count++;
    // Setting this to TRUE causes OpenMsgStore() to fail with MAPI_E_UNCONFIGURED
    props[prop_count].ulPropTag      = PR_CONVERSION_PROHIBITED;
    props[prop_count].Value.b        = FALSE;
    prop_count++;
    props[prop_count].ulPropTag     = PR_PROFILE_CONFIG_FLAGS;
    props[prop_count].Value.l       = CONFIG_SERVICE /*| CONFIG_PROMPT_FOR_CREDENTIALS
| CONFIG_SHOW_CONNECT_UI */;
    prop_count++;
    props[prop_count].ulPropTag     = PR_DISPLAY_NAME;
    props[prop_count].Value.lpszA   = <Mailbox Profile Name>;
    prop_count++;
    //Above setting used to be sufficient to connect using RPC
    //Below parameters added to connect via HTTPS
    LPSTR pwszUser = "domain\\username"; //also tried
[email protected] AND username
    LPWSTR pwszPassword = L"paswword"; // Password has been encrypted using CryptProtectData
    props[prop_count].ulPropTag = PR_PROFILE_RPC_PROXY_SERVER_W;
   props[prop_count].Value.lpszW = L"https://ProxyHostname.domain";
    prop_count++;
    props[prop_count].ulPropTag = PR_PROFILE_RPC_PROXY_SERVER_AUTH_PACKAGE;
    props[prop_count].Value.l = RPC_C_AUTHN_NONE;      // RPC_C_HTTP_AUTHN_SCHEME_NTLM,
RPC_C_HTTP_AUTHN_SCHEME_BASIC
    prop_count++;
    props[prop_count].ulPropTag = PR_PROFILE_RPC_PROXY_SERVER_FLAGS;
    props[prop_count].Value.l = PRXF_ENABLED | PRXF_SSL;// | PRXF_IGNORE_SEC_WARNING; // | PRXF_IGNORE_SEC_WARNING;
    prop_count++;
    props[prop_count].ulPropTag = PR_PROFILE_RPC_PROXY_SERVER_PRINCIPAL_W;
    props[prop_count].Value.lpszW = L"msstd:certificateserverhostname.domain";
    prop_count++;
    props[prop_count].ulPropTag = PR_PROFILE_AUTH_PACKAGE;
    props[prop_count].Value.l = RPC_C_AUTHN_GSS_NEGOTIATE;
// RPC_C_AUTHN_WINNT, RPC_C_AUTHN_GSS_NEGOTIATE, RPC_C_AUTHN_NONE
    prop_count++;
    props[prop_count].ulPropTag = PR_PROFILE_AUTH_USER_W;
    props[prop_count].Value.lpszA = pwszUser;
    prop_count++;
    props[prop_count].ulPropTag = PR_PROFILE_AUTH_PASSWORD;
    props[prop_count].Value.bin.lpb = dataBlobOut.pbData;
    props[prop_count].Value.bin.cb = dataBlobOut.cbData;
    prop_count++;
    DB( (DB_PR _T("ConfigureExchangeService() About to configureMsgService\r\n"),
this ) );
    hres = lpServiceAdmin->ConfigureMsgService( exchUID, 0, config_flags, prop_count, props
    I still get MAPI_E_NETWORK not found
Are there any configuration changes need to be done on Exchange Server?
Is there any mistake in above parameters?
Kindly suggest.

You can refer Dave's blog post @
http://blogs.msdn.com/b/dvespa/archive/2013/05/21/how-to-mfcmapi-create-mapi-profile-exchange-2013.aspx
DeVa, M.S., {MSFT} Please remember to mark the replies as answers if they help

Sizing IIS ARR for Exchange Server 2013

Hi Everyone,..
I planned to publish Exchange 2013 through IIS ARR server, but I've had trouble finding any data on CPU / memory usage for a dedicated ARR server based on Microsoft recommendation. There are 8000 users that will be access from ARR server.
Hopefully you can help for sizing so
there isn't bottleneck on that server.
Thanks
~IH~

Hi Irfan
The concurrent connections depends upon appConcurrentRequestLimit which has a default value of 5000. I think you need to increase this if in your case the concurrent connections exceed 5000
I have found few articles for your reference
http://www.iis.net/learn/extensions/configuring-application-request-routing-(arr)/achieving-high-availability-and-scalability-arr-and-nlb
http://blogs.technet.com/b/tristank/archive/2008/03/11/maxuserport-what-it-is-what-it-does-when-it-s-important.aspx
https://blogs.technet.com/b/exchange/archive/2013/07/19/reverse-proxy-for-exchange-server-2013-using-iis-arr-part-1.aspx
https://blogs.technet.com/b/exchange/archive/2013/08/02/part-2-reverse-proxy-for-exchange-server-2013-using-iis-arr.aspx
https://blogs.technet.com/b/exchange/archive/2013/08/05/part-3-reverse-proxy-for-exchange-server-2013-using-iis-arr.aspx
Its better to submit this to http://forums.iis.net/ since this is more kind of IIS related issue and you will get better response
Good Luck !!
Remember to mark as helpful if you find my contribution useful or as an answer if it does answer your question.That will encourage me - and others - to take time out to help you Check out my latest blog posts on http://exchangequery.com

External Clients cannot connect to Exchange Server

Hello all:
My external clients using outlook cannot connect to Exchange Server 2013. We have on-presmise version updated to Cu3 and after the Cu3 update we lost connectivity with Outlook clients. Many of the settings in IIS were changed after the Cu3 update,
I noticed after my http->https redirect was not applied anymore to the default website. Here is my Get-OutlookAnywhere results:
RunspaceId : 6379fab1-f692-484f-8118-99e48330d4c4
ServerName : EXCHSERV
SSLOffloading : True
ExternalHostname : mail.domain.com
InternalHostname : mail.domain.com
ExternalClientAuthenticationMethod : Negotiate
InternalClientAuthenticationMethod : Ntlm
IISAuthenticationMethods : {Basic}
XropUrl :
ExternalClientsRequireSsl : True
InternalClientsRequireSsl : True
MetabasePath : IIS://EXCHSERV.domain.com/W3SVC/1/ROOT/Rpc
Path : D:\Program Files\Microsoft\Exchange Server\V15\FrontEnd\HttpProxy\rpc
ExtendedProtectionTokenChecking : None
ExtendedProtectionFlags : {}
ExtendedProtectionSPNList : {}
AdminDisplayVersion : Version 15.0 (Build 775.38)
Server : EXCHSERV
AdminDisplayName :
ExchangeVersion : 0.20 (15.0.0.0)
Name : Rpc (Default Web Site)
DistinguishedName : CN=Rpc (Default Web
Site),CN=HTTP,CN=Protocols,CN=EXCHSERV,CN=Servers,CN=Exchange Administrative
Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=domain,CN=Microsoft
Exchange,CN=Services,CN=Configuration,DC=domain,DC=com
Identity : EXCHSERV\Rpc (Default Web Site)
Guid : 596ed7a1-ceec-4a36-9cbc-617ac5214463
ObjectCategory : domain.com/Configuration/Schema/ms-Exch-Rpc-Http-Virtual-Directory
ObjectClass : {top, msExchVirtualDirectory, msExchRpcHttpVirtualDirectory}
WhenChanged : 12/23/2013 2:20:41 AM
WhenCreated : 11/25/2013 2:51:36 PM
WhenChangedUTC : 12/23/2013 7:20:41 AM
WhenCreatedUTC : 11/25/2013 7:51:36 PM
OrganizationId :
OriginatingServer : DOMAINCONTROLLER.domain.com
IsValid : True
ObjectState : Changed
Thanks in advance

Hi,
According to your description, users cannot connect to Exchange server 2013 both internal and external.
Please run Test E-mail AutoConfiguration in Outlook to check your autodiscover service. Also
reset your Exchange virtual directory to connect correctly. If the issue still continues after all configurations are setting properly, collect some Event logs would be helpful.
If there is any question, please post the results here for further analysis.
Thanks,
Winnie Liang
TechNet Community Support

Exchange Server 2013 SP1 Standard: Installation failing can't progress

I'm trying to install Exchange Server 2013 and I keep getting this error and I am unable to progress, I can't find any support on the issue and frankly I don't want to/can't afford to spend $500 to ask Microsoft for technical support (what kind of racket
do they think they're running?).
The error message:
Error:
The following error was generated when "$error.Clear();
New-PushNotificationsVirtualDirectory -Role Mailbox -DomainController $RoleDomainController;
" was run: "The Active Directory object for virtual directory 'IIS://SVR02.OFFICE.local/W3SVC/24/ROOT/PushNotifications' on 'SVR02' could not be created. This might be because the object already exists in Active Directory. Remove the object from Active Directory, then re-create it.".
Yet, I see no PushNotifications virtual directory or anything remotely related to that on IIS or in the inetpub folders and files. If I try to resume the set-up after this error I get:
Error:
The following error was generated when "$error.Clear();
New-PushNotificationsVirtualDirectory -Role Mailbox -DomainController $RoleDomainController;
" was run: "The AD configuration for virtual directory 'PushNotifications' already exists in 'CN=PushNotifications (Exchange Back End),CN=HTTP,CN=Protocols,CN=SVR02,CN=Servers,CN=Exchange Administrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=OFFICE,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=OFFICE,DC=local', please remove this AD configuration manually.
Parameter name: VirtualDirectoryName".
And I have to remove this config using ADSI Edit, which just returns me to the first error.

1. Prodution
2. Just 1 DC for 1 site.
3. Setup.EXE
4. Matches SP1 version numbers
5. That's just what was made available to me via MSPP, the installer doesn't see any updates?
6. Here is the log files:
[03/23/2015 22:06:52.0940] [1] Setup failed previously while performing the action Install. Looking for the failed task with ID ClientAccessComponent___75f8c93d15314369983d33ec0742e189.
[03/23/2015 22:06:52.0941] [1] 131 tasks were found to run.
[03/23/2015 22:06:52.0941] [1] Processing component 'Client Access Configuration' (Configuring Mailbox role: Client Access service.).
[03/23/2015 22:06:52.0941] [1] Executing:
New-PushNotificationsVirtualDirectory -Role Mailbox -DomainController $RoleDomainController;
[03/23/2015 22:06:52.0955] [2] Active Directory session settings for 'New-PushNotificationsVirtualDirectory' are: View Entire Forest: 'True', Configuration Domain Controller: 'SVR01.OFFICE.local', Preferred Global Catalog: 'SVR01.OFFICE.local', Preferred Domain Controllers: '{ SVR01.OFFICE.local }'
[03/23/2015 22:06:52.0956] [2] User specified parameters: -Role:'Mailbox' -DomainController:'SVR01.OFFICE.local'
[03/23/2015 22:06:52.0956] [2] Beginning processing New-PushNotificationsVirtualDirectory
[03/23/2015 22:06:52.0999] [2] Searching objects "SVR02.OFFICE.local" of type "Server" under the root "$null".
[03/23/2015 22:06:53.0066] [2] Previous operation run on domain controller 'SVR01.OFFICE.local'.
[03/23/2015 22:06:53.0068] [2] Processing object "SVR02\PushNotifications".
[03/23/2015 22:06:56.0763] [2] The properties changed on the object '' (CN=PushNotifications (Exchange Back End),CN=HTTP,CN=Protocols,CN=SVR02,CN=Servers,CN=Exchange Administrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=OFFICE,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=OFFICE,DC=local) are: "{ MetabasePath[msExchMetabasePath]='IIS://SVR02.OFFICE.local/W3SVC/24/ROOT/PushNotifications', AuthenticationMethodFlags[msExchInternalAuthenticationMethods]='Ntlm, WindowsIntegrated', AuthenticationMethodFlags[msExchExternalAuthenticationMethods]='Ntlm, WindowsIntegrated', Id[distinguishedName]='SVR02\PushNotifications (Exchange Back End)', InternalAuthenticationMethods[msExchInternalAuthenticationMethods]={ 'Ntlm', 'WindowsIntegrated' }, ExternalAuthenticationMethods[msExchExternalAuthenticationMethods]={ 'Ntlm', 'WindowsIntegrated' }, OrganizationId[msExchOURoot, msExchCU]='' }".
[03/23/2015 22:06:56.0764] [2] Saving object "SVR02\PushNotifications (Exchange Back End)" of type "ADPushNotificationsVirtualDirectory" and state "New".
[03/23/2015 22:06:57.0073] [2] Previous operation run on domain controller 'SVR01.OFFICE.local'.
[03/23/2015 22:06:57.0587] [2] [ERROR] The Active Directory object for virtual directory 'IIS://SVR02.OFFICE.local/W3SVC/24/ROOT/PushNotifications' on 'SVR02' could not be created. This might be because the object already exists in Active Directory. Remove the object from Active Directory, then re-create it.
[03/23/2015 22:06:57.0591] [2] [ERROR] Filename: \\?\C:\Windows\system32\inetsrv\config\applicationHost.config
Line number: 630
Error: Can not log on locally to C:\Program Files\Microsoft\Exchange Server\V15\ClientAccess\PushNotifications as user OFFICE\Administrator with virtual directory password
[03/23/2015 22:06:58.0378] [2] [ERROR] The Active Directory object for virtual directory 'IIS://SVR02.OFFICE.local/W3SVC/24/ROOT/PushNotifications' on 'SVR02' could not be created. This might be because the object already exists in Active Directory. Remove the object from Active Directory, then re-create it.
[03/23/2015 22:06:58.0378] [2] [ERROR] Filename: \\?\C:\Windows\system32\inetsrv\config\applicationHost.config
Line number: 630
Error: Can not log on locally to C:\Program Files\Microsoft\Exchange Server\V15\ClientAccess\PushNotifications as user OFFICE\Administrator with virtual directory password
[03/23/2015 22:06:58.0386] [2] Ending processing New-PushNotificationsVirtualDirectory
[03/23/2015 22:06:58.0388] [1] The following 1 error(s) occurred during task execution:
[03/23/2015 22:06:58.0388] [1] 0. ErrorRecord: The Active Directory object for virtual directory 'IIS://SVR02.OFFICE.local/W3SVC/24/ROOT/PushNotifications' on 'SVR02' could not be created. This might be because the object already exists in Active Directory. Remove the object from Active Directory, then re-create it.
[03/23/2015 22:06:58.0389] [1] 0. ErrorRecord: System.InvalidOperationException: The Active Directory object for virtual directory 'IIS://SVR02.OFFICE.local/W3SVC/24/ROOT/PushNotifications' on 'SVR02' could not be created. This might be because the object already exists in Active Directory. Remove the object from Active Directory, then re-create it. ---> System.Runtime.InteropServices.COMException: Filename: \\?\C:\Windows\system32\inetsrv\config\applicationHost.config
Line number: 630
Error: Can not log on locally to C:\Program Files\Microsoft\Exchange Server\V15\ClientAccess\PushNotifications as user OFFICE\Administrator with virtual directory password
at Microsoft.Web.Administration.Interop.IAppHostAdminManager.GetAdminSection(String bstrSectionName, String bstrPath)
at Microsoft.Web.Administration.Configuration.GetSectionInternal(ConfigurationSection section, String sectionPath, String locationPath)
at Microsoft.Exchange.Management.SystemConfigurationTasks.ExchangeServiceVDirHelper.SetAuthModule(Boolean EnableModule, Boolean isChildVDirApplication, String moduleName, String moduleType, ExchangeVirtualDirectory advdir)
at Microsoft.Exchange.Management.SystemConfigurationTasks.ExchangeServiceVDirHelper.SetLiveIdBasicAuthModule(Boolean EnableModule, Boolean isChildVDirApplication, ADExchangeServiceVirtualDirectory advdir)
at Microsoft.Exchange.Management.SystemConfigurationTasks.NewExchangeServiceVirtualDirectory`1.InternalProcessComplete()
at Microsoft.Exchange.Management.SystemConfigurationTasks.NewPushNotificationsVirtualDirectory.InternalProcessComplete()
at Microsoft.Exchange.Management.SystemConfigurationTasks.NewExchangeVirtualDirectory`1.InternalProcessRecord()
--- End of inner exception stack trace ---
at Microsoft.Exchange.Configuration.Tasks.Task.WriteError(Exception exception, ErrorCategory category, Object target, Boolean reThrow, String helpUrl)
at Microsoft.Exchange.Configuration.Tasks.Task.WriteError(Exception exception, ErrorCategory category, Object target)
at Microsoft.Exchange.Management.SystemConfigurationTasks.NewExchangeVirtualDirectory`1.InternalProcessRecord()
at Microsoft.Exchange.Configuration.Tasks.Task.ProcessRecord()
[03/23/2015 22:06:58.0389] [1] [ERROR] The following error was generated when "$error.Clear();
New-PushNotificationsVirtualDirectory -Role Mailbox -DomainController $RoleDomainController;
" was run: "The Active Directory object for virtual directory 'IIS://SVR02.OFFICE.local/W3SVC/24/ROOT/PushNotifications' on 'SVR02' could not be created. This might be because the object already exists in Active Directory. Remove the object from Active Directory, then re-create it.".
[03/23/2015 22:06:58.0389] [1] [ERROR] The Active Directory object for virtual directory 'IIS://SVR02.OFFICE.local/W3SVC/24/ROOT/PushNotifications' on 'SVR02' could not be created. This might be because the object already exists in Active Directory. Remove the object from Active Directory, then re-create it.
[03/23/2015 22:06:58.0389] [1] [ERROR] Filename: \\?\C:\Windows\system32\inetsrv\config\applicationHost.config
Line number: 630
Error: Can not log on locally to C:\Program Files\Microsoft\Exchange Server\V15\ClientAccess\PushNotifications as user OFFICE\Administrator with virtual directory password
[03/23/2015 22:06:58.0390] [1] [ERROR-REFERENCE] Id=ClientAccessComponent___75f8c93d15314369983d33ec0742e189 Component=EXCHANGE14:\Current\Release\Shared\Datacenter\Setup
[03/23/2015 22:06:58.0390] [1] Setup is stopping now because of one or more critical errors.
[03/23/2015 22:06:58.0390] [1] Finished executing component tasks.
[03/23/2015 22:06:58.0406] [1] Ending processing Install-ClientAccessRole
It says it can not log on with the supplied details, but the account is an Administrator account with full privileges so I can't see why this would be the case.

Recover mailbox from Exchange server 2010 information store to exchange server 2013

I have a big issue. I have a correct exchange server 2010 where the active directory is corrupt but the information store is good.
I would like to recover a couple of mailboxes to an exchange server 2013.
Can anyone give me a detailed walk through of how I can accomplish this?
Thank in advance

Well if your AD is messed up that leaves you in a jam for sure because;
1. Database portability ONLY works within the same organization, so you cannot just install a new 2010 server in a completely different forest and then move the DB in hopes that DB portability will work.
2. As Ed said you should build a new Exchange 2010 server and use portability but it has to be in the same organization.
3. Here is a good article on how to accomplish
http://exchangeserverpro.com/exchange-2010-database-portability-disaster-recovery/
4. Now if you by chance have an AD backup before it went south you could build a separate network with same names etc just keep it isolated from the production server and then restore AD to that environment and you could then use DB portability.
That said if you don't have any other machines to work with then you are in a bit of a pickle and will have to use a 3rd party product to get to that data within the 2010 DB. We make a product that can do this (DigiScope), however if you don't
have any budget to handle its a non-issue.
The only other thing you could consider is to restore your AD from a previous point in time, however BE VERY CAREFUL if you consider this since it could cause more issues then you have now.
BTW if you AD is messed up, where are you putting this new 2013 server?
Search, Recover, & Extract Mailboxes, Folders, & Email Items from Offline Exchange Mailbox and Public Folder EDB's and Live Exchange Servers or Import/Migrate direct from Offline EDB to Any Production Exchange Server, even cross version i.e. 2003 -->
2007 --> 2010 --> 2013 with Lucid8's
DigiScope

Connect to Exchange 2013 using IMAP/SMTP from the Internet

Hello,
I would like to enable connectivity to my exchange server using imap and smtp. my exchange server is using the default configuration for imap and smtp which are port 143 and 25 respectively. I have two exchange servers both with CAS and MB roles
installed. I also have an edge server on my DMZ. I have also published my OWA using IIS ARR module. I wonder where I should direct my traffic from my firewall to enable IMAP connectivity taking into considerations my two servers with CAS and MB roles are inside
my network. I also wonder how I can enable redundancy for IMAP connections. Thanks a lot.
Regards,
Pooriya
Pooriya Aghaalitari

Hi Pooriya,
When you install Microsoft Exchange Server 2013, IMAP4 client connectivity isn't enabled. We can do the following steps to configure it:
1. Start two IMAP services: the Microsoft Exchange IMAP4 service and the Microsoft Exchange IMAP4 Backend service.
Set-service msExchangeIMAP4 -startuptype automatic
Start-service msExchangeIMAP4
Set-service msExchangeIMAP4BE -startuptype automatic
Start-service msExchangeIMAP4BE
2. Make sure there is an valid certificate which is assigned with IMAP service. Also confirm the Published Exchange server name (For example: mail.domain.com) has been included in this certificate:
Get-ExchangeCertificate | FL
3. Configure the external IMAP connection settings:
Set-ImapSettings -ExternalConnectionSetting {mail.domain.com:993:SSL}
4. Configure SMTP settings:
Get-ReceiveConnector "*\client Frontend*" | Set-ReceiveConnector -AdvertiseClientSettings $true -Fqdn mail.domain.com
5. You must restart IIS service (running IISReset /noforce from the Command Prompt window) after applying all settings.
For more information about IMAP in Exchange 2013, please refer to:
http://technet.microsoft.com/en-us/library/jj657728(v=exchg.150).aspx
Regards,
Winnie Liang
TechNet Community Support

How to get list of Users[MailBoxes] in Exchange Server 2013 by using EWS Managed API

Hi all,
I need list of Users exists in my Exchange server 2013 , i.e Mail Box Users login name.
I was created Full Access permissions of all users to Admin user account, to access each user Mailbox programatically
i need the list of Mailboxes in exchange server .
MailBox mailbox = new MailBox("user");
Please share your ideas

Hi,
We can run the following command in Exchange Management Shell to get all user mailboxes name and export it to a .csv file:
Get-Mailbox -ResultSize Unlimited | Select Name,Alias,RecipientTypeDetails | Export-Csv c:\Users.csv
If you want to retrieve the list of users by using EWS Managed API, I suggest you can ask a question in Exchange Development forum for more suggestion:
http://social.technet.microsoft.com/Forums/en-US/exchangesvrdevelopment/threads
Regards,
Winnie Liang
TechNet Community Support

Connecting to Exchange Server 2013 using IMAP command gives authenication error

Similar Messages

Maybe you are looking for