Exchange 2007 EXCDO 8206 error in Exchange 2007 SP2 with Rollup 4

Dear sir,
    We have a problem on Exchange 2007 Server. When user use OWA to access web mail calendar, server event log will show EXCDO error 8206:
Calendaring agent failed with error code 0x8000ffff while saving appointment
Type: Error
Event ID: 8207
Category: General.
     Moreover server becomes working in very slow web mail response during any user click web mail calendar.   Server performance return back after error message appeared  in event log.
It doesn't has problem if using Outlook to access mailbox calendar.
Any suggestion to fix it ?
Joe

Hi Joe,
We are also finding the same issue with getting that EXCDO error. The problem stemmed when users noticed some previously accepted appointments disappeared (As I suspect you discovered with your users). 
The workaround has been to get the user to accept the appointment again by going into deleted items, this seems to add the appointment as it should have the first time.
We have done the following but it didn't fix the problem:
Disabled extra SEP features on the clients - No Change
Disabled non-essential Outlook add-ons - No Change 
Removed BES Express and CDO MAPI From Exchange server - No Change
Disabled MS Defender on Exchange - No Change
Fixed any Public folder errors - No Change
Disable Window services WSS and UNC sharing feature in Active Sync - No Change
Also ensured Autoupdate and auto process was enabled for affected users - No Change
I'm going to try the reg change mentioned in this thread but other than the built in MS Defender we don't have anti-virus on our mail server. 
At first we thought it was Active Sync as it only seem to impact those with a A/S device, but now it's intermittent for other users using Outlook.  We are currently using Exchange 2007 SP3 with RU13. We are looking at trying an update
to RU14 but I am doubtful it will fix the problem. Did you have any luck finding a solution?
Thank you in Advance.

Similar Messages

  • SharePoint 2007 - Invalid Token Error when Generating Excel Worksheet with ItemLevelAudit

    All,
    I have the AuditLevel project located here working on a test site:
    https://msdn.microsoft.com/en-us/library/office/bb397403(v=office.12).aspx#MOSS2007ItemLevelAudit_AuditingwithSharePointServer2007
    Since I'm a site collection admin - I can access a document and go to View Audit History.
    When I click the button to Generate Excel Document - if I've viewed the document I get the following error
    since I have a ' in my name - is this due to AD or can this be fixed in code - I did run a
    Replace ' with '' in each of the page loads on any aspx pages I saw
    string s = "'";
    string escaped = s.Replace("'","''");
    '//s:si[s:t='O'Neill, Kevin']' has an invalid token.   at MS.Internal.Xml.XPath.XPathParser.CheckToken(LexKind t)
       at MS.Internal.Xml.XPath.XPathParser.ParsePredicate(AstNode qyInput)
       at MS.Internal.Xml.XPath.XPathParser.ParseStep(AstNode qyInput)
       at MS.Internal.Xml.XPath.XPathParser.ParseRelativeLocationPath(AstNode qyInput)
       at MS.Internal.Xml.XPath.XPathParser.ParseLocationPath(AstNode qyInput)
       at MS.Internal.Xml.XPath.XPathParser.ParsePathExpr(AstNode qyInput)
       at MS.Internal.Xml.XPath.XPathParser.ParseUnionExpr(AstNode qyInput)
       at MS.Internal.Xml.XPath.XPathParser.ParseUnaryExpr(AstNode qyInput)
       at MS.Internal.Xml.XPath.XPathParser.ParseMultiplicativeExpr(AstNode qyInput)
       at MS.Internal.Xml.XPath.XPathParser.ParseAdditiveExpr(AstNode qyInput)
       at MS.Internal.Xml.XPath.XPathParser.ParseRelationalExpr(AstNode qyInput)
       at MS.Internal.Xml.XPath.XPathParser.ParseEqualityExpr(AstNode qyInput)
       at MS.Internal.Xml.XPath.XPathParser.ParseAndExpr(AstNode qyInput)
       at MS.Internal.Xml.XPath.XPathParser.ParseOrExpr(AstNode qyInput)
       at MS.Internal.Xml.XPath.XPathParser.ParseXPathExpresion(String xpathExpresion)
       at MS.Internal.Xml.XPath.QueryBuilder.Build(String query, Boolean allowVar, Boolean allowKey)
       at MS.Internal.Xml.XPath.QueryBuilder.Build(String query, Boolean& needContext)
       at System.Xml.XPath.XPathExpression.Compile(String xpath, IXmlNamespaceResolver nsResolver)
       at System.Xml.XPath.XPathNavigator.Compile(String xpath)
       at System.Xml.XmlNode.SelectSingleNode(String xpath, XmlNamespaceManager nsmgr)
       at ItemAuditing.AuditLogWorkbook.XLInsertStringIntoCell(String sheetName, String addressName, String value)
       at ItemAuditing.AuditLogWorkbook.WriteCell(String celladdress, String cellvalue)
       at ItemAuditing.AuditLogWorkbook.WriteEntry(String User, String Occurred, String Event, String Version)
       at AuditLogWorkbookHandler.<>c__DisplayClass1.<ProcessRequest>b__0() in c:\Program Files\Common Files\Microsoft Shared\web server extensions\12\TEMPLATE\LAYOUTS\AuditLogWorkbook.ashx:line 54
       at Microsoft.SharePoint.SPSecurity.CodeToRunElevatedWrapper(Object state)
       at Microsoft.SharePoint.SPSecurity.<>c__DisplayClass4.<RunWithElevatedPrivileges>b__2()
       at Microsoft.SharePoint.Utilities.SecurityContext.RunAsProcess(CodeToRunElevated secureCode)
       at Microsoft.SharePoint.SPSecurity.RunWithElevatedPrivileges(WaitCallback secureCode, Object param)
       at Microsoft.SharePoint.SPSecurity.RunWithElevatedPrivileges(CodeToRunElevated secureCode)
       at AuditLogWorkbookHandler.ProcessRequest(HttpContext context) in c:\Program Files\Common Files\Microsoft Shared\web server extensions\12\TEMPLATE\LAYOUTS\AuditLogWorkbook.ashx:line 30
       at System.Web.HttpApplication.CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute()
       at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously)

    Hi Alan J Stewart,
    This issue may occur due to the column name in your scenario.
    Would you please change the column name: raised by column to “raised_by”, and export the list with this column, check whether the issue persists.
    I have seen similar issue that caused by the column name.
    Thanks,
    Qiao
    Forum Support
    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]
    Qiao Wei
    TechNet Community Support

  • Exchange 2003 sp2 to exchange 2007 sp1 upgrade error

    Hi,
    We had Windows 2003 DCs and Exchange 2003 servers. We migrated AD DCs to windows 2008 R2 at parent domain.
    We have one parent domain and 10 child domains in remote sites .3 remote sites have been migrated to windows 2008 R2.
    Now at parent domain I am trying to install exchange 2007 SP1 on a server with windows 2008 R2 SP1. I am facing certain issues:
    1. When I run setup /PrepareSchema on this new exchange server , the organization check fails with error stating that : cannot find at least one DC running windows 2003 SP1 or later in DC=xyx,DC=com. This could be the result of moving DC objects in AD. Check
    that at least one DC running windows server 2003 SP1 or later is located in the "Domian Controllers" OU and rerun setup".
    2. When I try to install exchange server 2007 , I get the following error
    Object cannot be saved because its ExchangeVersion property is 0.10 (14.0.100.0), which is not supported
    by the current version 0.1 (8.0.535.0). You will need a later version of Exchange.".
    Can any one shed light on this issue.
    Regards
    Syed
    sa

    You cannot install Exchange 2007 SP1 on Windows 2008 R2 SP1 as it is unsupported.
    Only version of Exchange 2007 supported when OS is Windows 2008 R2 or R2 SP1 is Exchange 2007 SP3.
    Where are you installing Exchange ? child or parent domain ?
    2. When I try to install exchange server 2007 , I get the following error "Object
    cannot be saved because its ExchangeVersion property is 0.10 (14.0.100.0), which is not supported by the current version 0.1 (8.0.535.0). You will need a later version of Exchange.".
    Above error indicates that Exchange setup is trying to modify
    a version of an object which might have been created when organization is prepared for Exchange 2010. don't you have exchange 2010 Servers already in your environment ?
    Please give more information about your current email infrastructure
    and whether if you are installing exchange on parent or child domain?
    Pavan Maganti ~ ( Exchange | 2003/2007/2010/E15(2013)) ~~ Please remember to click “Vote As Helpful&quot; if it really helps and &quot;Mark as Answer” if it answers your question, “Unmark as Answer” if a marked post does not actually answer your
    question. ~~ This Information is provided is &quot;AS IS&quot; and confers NO Rights!!

  • Exchange 2007 mailbox creation error

    Hi,
    We are having problems with our standard AD/Exchange adapter when creating users with a mailbox.
    We currently have the following setup:
    - Sun IdM 8.1.0.7
    - There are 4 DC, and two Exchange 2007 Servers.
    - The gateway runs on a seperate Win2003 R2 32 bit server (but is a member of the AD).
    The error we are getting is this:
    PowerShell:41b59779-b9cb-487f-b200-4b9836dc176d is not a mailbox user.
    It seems like the gateway has a preferred DC when creating accounts.
    But when creating the Exchange account, the Exchange server has a different preferred DC,
    where the AD account is not yet present. (there is an 5 minute replication interval)
    We don't have a test enviroment with the same setup, which makes it a bit tricky to find the problem,
    and testing possible solutions for it. Out test enviroment consists only of 1 DC, and 1 Exchange server so
    the errors does not exist there.
    Is there anyone who has seen something like this before, and in that case, is there a solution for it?
    Or it's maybe better if a put it like this: Is there anyone who is running multiple DC:s and multiple Exchange Servers
    without these problems? And in that case, are you creating the user and the mailbox at the same time?
    I would gladly provide some more info and logs, if you specify what might be interesting to see.
    Thanks and kind regards,
    Henrik

    Some additional info:
    Today the process goes like this:
    First we create the user and does not set the RecipientType -> The user is created in AD (without Mailbox)
    Second we set the following attributes when we want the user to get a Mailbox: (5 min delay)
    EmailAddressPolicyEnabled = false
    PrimarySmtpAddress = [email protected]
    RecipientType = MailboxUser
    Database = <our-db-here>
    The user now gets his mailbox, but the email generated by Exchange is used when I look at the user.
    And also the EmailAddressPolicy stays enabled.
    Any ideas about the attributes I'm trying to set here?
    Regards,
    Henrik
    Edited by: user1154522 on Apr 12, 2011 8:44 AM

  • ActiveSync 500 error and Exchange 2007/2013 coexistence

    Hello,
    We have Exchange 2007, and we've deployed Exchange 2013 and coexistence appears to be working.  We have done a small pilot migration of 11 users, and I have 2 of those users that are not able to get iPhone/ActiveSync working.  OWA and Outlook access
    work without a problem.  https://testconnectivity.microsoft.com/ is telling me "The test of the FolderSync command failed." and "Exchange
    ActiveSync returned an HTTP 500 response (Internal Server Error)"
    The error I'm receiving on the mailbox server event log is:
    An exception occurred and was handled by Exchange ActiveSync. This may have been caused by an outdated or corrupted Exchange ActiveSync device partnership. This can occur if a user tries to modify the same item from multiple computers. If this is the case,
    Exchange ActiveSync will re-create the partnership with the device. Items will be updated at the next synchronization. 
    URL=
    --- Exception start ---
    Exception type: Microsoft.Exchange.AirSync.AirSyncPermanentException
    Exception message: A null value was received for the NTSD security descriptor of container CN=ExchangeActiveSyncDevices,CN=LASTNAME\, FIRSTNAME.,OU=XXX,OU=People,DC=DOMAIN,DC=local. 
    Most articles I've found with this issue say to confirm that "Inherit parent permissions" is check on the AD object, but that is already checked?
    The funny thing is that most of our pilot users don't have this issue.  It is only for some of them.
    Any help is appreciated.

    An update here, I was able to get the 2 pilot user's iPhone/ActiveSync access working by adding the following permissions by hand:
    Add Exchange Servers, in Apply onto select
    msExchActiveSyncDevices objects (note it's plural) and selecting
    Full Control.  
    Once I did this, my problems went away.
    So the big question is why aren't these permissions in place already?  Isn't this something that the adprep/domain prep should have taken care of?
    Thanks!

  • Address list service failed to respond error on Exchange 2007 (after adding first 2013 server)

    Hi,
    We just installed an Exchange 2013 server within an Exchange 2007 environment.
    The Exchange 2013 (CU6) server will be used to setup a hybrid connection with O365, and move mailboxes to O365.
    After installing the Exchange 2013 server it isn't possible anymore to create/enable mailboxes on the Exchange 2007 server.
    We end up with an error :
    Mig1 TestAccount
    Failed
    Error:
    The Exchange server address list service failed to respond. This could be because of an address list or email address policy configuration error.
    Exchange Management Shell command attempted:
    Enable-Mailbox -Identity 'domain.be/customer/TEMP/Mig1 TestAccount' -Alias 'mig1' -Database 'Exchange2007\SG01\DB02'
    When executed via EMS we receive this error :
    The Exchange server address list service failed to respond. This could be because of an address list or email address policy configuration error

    Hi Lyncer
    This error can be caused if the default Public Folder Database not being pointed to the exchange 2007 database which you are trying to create a new mailbox.
    Also it can happen if System Attendant service is not running.
    Troubleshooting steps:
    1) Restart the System Attendant Service 
    2) Point the affected database to the default public folder
    Follow the below steps to do that 
    Open EMC
    Go to Organization Configuration > Mailbox.
    Select the mailbox database that you want to change the default public folder database.
    Right click the database and select properties
    In <Mailbox Database Name> Properties, click the Client Settings tab.
    Next to the Default public folder database box, click Browse.
    In Select Public Folder Database, select the public folder database from the list of public folder databases, and then click OK.
    Cheers!!!
    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 Thanks Sathish
    (MVP)

  • Exchange 2007 Certificate Expired Error when using VPN

    We recently did a server migration to a new domain (split away from part of the company - sept 2013).  I set up the exchange certs and everything worked fine, even when people used the vpn.  Recently (it probably started a few months ago) it has
    started giving cert errors again, but just for VPN users.
    This happens when someone takes their computer or has Outlook 2010 set up on their home computer.  They VPN in and when the program starts, it gives the certificate errors for exchange and for autodiscover saying "The security certificate has expired
    or is not yet valid".  I have checked to make sure that the certs are in fact up to date and are pointing to the correct certificates in IIS.  They haven't changed since I originally set them up.  
    One of the users sent me a picture of the certificate and it is the old cert (that is expired) that used to belong to the previous address when we used the other (completely different) exchange server.  The other users haven't sent me the errors they
    see, but I assume they are similar.  They are able to use exchange if they hit ok on the error box.  I couldn't find anywhere online saying that there was any kind of local caching for certs - it should always call home when connecting.  So
    why are their systems pulling up the old cert when they VPN in, but not when they are hardwired to the internal network on the same computer?
    When using the internal network without the vpn, there aren't any error messages.
    Any ideas?  I've looked around the forums, but I didn't see anything that has helped.  I'm using godaddy for my certs currently.

    Hi,
    Since the Outlook clients work well without VPN, I suggest re-build the VPN (if you don't mind) to verify whether it is a caches issue.
    Thanks
    Mavis
    Mavis Huang
    TechNet Community Support

  • New Exchange 2013 CAS server in existing Exchange 2007 Organization

    Dear Friends,
    We have exchange 2007 SP3 with CU13 installed with single copy cluster for database and 1 OWA server for CAS/HT. We will migrate from current to Exchange 2013SP1. As we want to have HA, we have installed 2 new Exchange 2013 SP1 CAS server on widnows 2012
    R2 after preparing our organisation for Exchange 2013. The setup went smooth without any error and successfully installed CAS with management tools. After installation it ask to reboot the server which we did. Now after reboot, we are not able to run Exchange
    Management Sell. It never connects to the new server. In our old 2007 EMS also doesn't list any exchange 2013 server. We are also not able to connect to new CAS servers with below URL:
    https://servername/ecp/?ExchClientVer=15
    Its says site under maintenance. Please advise what to check. We were thinking of deploying CAS 1st and make it co-exist with Exchange 2007 before deploying Exchange 2013 mailbox server which will be setup in DAG. What are we doing wrong.
    Thanks in advance!!

    Dear Friends,
    We have exchange 2007 SP3 with CU13 installed with single copy cluster for database and 1 OWA server for CAS/HT. We will migrate from current to Exchange 2013SP1. As we want to have HA, we have installed 2 new Exchange 2013 SP1 CAS server on widnows 2012
    R2 after preparing our organisation for Exchange 2013. The setup went smooth without any error and successfully installed CAS with management tools. After installation it ask to reboot the server which we did. Now after reboot, we are not able to run Exchange
    Management Sell. It never connects to the new server. In our old 2007 EMS also doesn't list any exchange 2013 server. We are also not able to connect to new CAS servers with below URL:
    https://servername/ecp/?ExchClientVer=15
    Its says site under maintenance. Please advise what to check. We were thinking of deploying CAS 1st and make it co-exist with Exchange 2007 before deploying Exchange 2013 mailbox server which will be setup in DAG. What are we doing wrong.
    Thanks in advance!!
    If you have only the 2013 CAS installed and not the mailbox role, then nothing will really work. Remember, in 2013, the mailbox role does all the work, the CAS is simply a proxy for the most part.
    Twitter!: Please Note: My Posts are provided “AS IS” without warranty of any kind, either expressed or implied.

  • Remove Last Public Folder Database / Impact on Outlook 2007 - 2013 Clients ?? / Exchange 2010

    Hello together, 
    we have an Exchange 2010 SP3 UR5 Infrastructure. Now the end is in sight for Public Folders :)
    We want to Remove our Last Public Folder Database on our Organization. 
    How can i get this managed and what is the Outlook 2007+++ Client Impact on this Action ?
    The Plan is:
    Remove all Public Folder Content
    Set the OAB to Web Distribution Only
    Clear the “msExchHomePublicMDB” attribute on Exchange Databases
    Clear  the “siteFolderServer” attribute on CN=Exchange Administrative Group (FYDIBOHF23SPDLT) 
    Remove the Public Folder Database with ADSI
    Is there anything else to do ?
    Is there any Outlook Client Impact on this ? Does the Users get a Outlook Error like "your exchange administrator did some changes please restart" or is it transparent for the users ?
    thanks for Feedback, 
    Best, 
    Martin

    Hello,
    Please follow the Naren.Neelam's suggestion.
    Besides, I recommend you remove database via EMC or EMS. If you can't remove the database via EMC or EMS, and then you can use ADSIEDIT to remove the public folder database from the organization.
    When you remove a public folder database, the Exchange database (.edb) file for the database and other files associated with the database aren't automatically deleted. You must delete the public folder database files manually.
    Here are some articles for your reference.
    http://technet.microsoft.com/en-us/library/dd876883(v=exchg.141).aspx
    http://exchangeserverpro.com/exchange-2010-remove-public-folder-database/ (Note: Microsoft
    is providing this information as a convenience to you. The sites are not controlled by Microsoft. Microsoft cannot make any representations regarding the quality, safety, or suitability of any software or information found there. Please make sure that you
    completely understand the risk before retrieving any suggestions from the above link.)
    Cara Chen
    TechNet Community Support

  • Exchange 2013 SP1 Readiness Checks: No Exchange 2007 server detected

    Hi there,
    We are planning to upgrade our current Exchange 2007 server with the new Exchange 2013 SP1. I have been following Exchange Server Deployment Assistant to assist me with this task. Only schema update (setup /PrepareSchema) had been done so
    far. I didn’t run setup /PrepareAD command manually because I wasn’t sure if I need to provide ‘Organisation Name’ with it or not?! I have installed all of the prerequisites as noted in the Microsoft documentation.
    Now, I am a bit confuse with the ‘Readiness Checks’ page during graphical user installation of Exchange 2013 SP1 setup on Windows 2012 R2. Windows 2012 R2 server has all available updates applied.
    ===
    Warning:
    Setup will prepare the organization for Exchange 2013 by using 'Setup /PrepareAD'. No Exchange 2010 server roles have been detected in this topology. After this operation, you will not be able to install any Exchange 2010 servers.
    For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.NoE14ServerWarning.aspx
    ===
    I get the message why setup wants to run preparation for the Ex2013 with the ‘Setup /PrepareAD’. But, why ‘No Exchange 2010 server role have been detected in this topology’?! Ok, in my case setup doesn’t detect Exchange 2007 server. Is that ok to proceed
    with the installation or something else needs to be done first?
    Thanks in advance.

    I need Exchange guru advice here please. Since we already have Exchange 2007 SP3 RU 10 in our Windows 2008R2 Active Directory domain here I need to be 100% confident that pushing Exchange 2013 SP1 “Install” will not override our existing Ex2007 environment.
    That would be a huge disaster!
    Microsoft is saying that: “Microsoft Exchange Server 2013 Setup displayed this warning because
    no Exchange Server 2010 or Exchange Server 2007 server roles exist in the organization.”
    http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.NoE14ServerWarning.aspx
    Ok, I get the message about if I continue with Exchange Server 2013 installation, I won’t be able to add Exchange 2010 or Exchange 2007 servers to the organization at a future date..., and why would I need to do that anyway?!
    Microsoft wording about “some solutions may require the use...” are very confusing since we will require to consider “Coexistence or migration requirements"
    Perhaps, before running Exchange 2013 SP1 setup I need to run setup for preparing AD without “Organisation Name” parameter?! Something like this:
    setup /PrepareAD  /IAcceptExchangeServerLicenseTerms

  • Unbale to install November update on Outlook 2007 SP3 for connecting to Exchange 2013

    Hi
    I was trying to upgrade my outlook 2007 clients for connecting to Exchange 2013 environment. First I have installed Office SP3 (kb2526086). Outlook version after that is 12.0.6607.1000. Later I  tried to install nNovember 2012 update which is a
    prerequisite for connecting to Exchange 2013 clients (support.microsoft.com/kb/2687404/en-us) but it shows me a message "Expected version of the product was not found on the system". No idea  how to proceed now, expecting help.

    I recommend that you post this in the Outlook Forum:  http://social.technet.microsoft.com/Forums/en-US/outlook/threads
    Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."

  • Outlook 2007 - single profile connecting to Exchange 2013 / 2007 mailboxes

    Hi,
    I am in the early part of a migration from Exchange 2007 to Exchange 2013. So far I have 2013 installed and running in a DAG and just moved my own mailbox to the new server.
    I set up a new profile in Outlook 2007 which connects to my mailbox on Exchange 2013. The problem is that I need to add additional mailboxes to my profile which are still hosted on Exchange 2007, however this is not working.
    I thought at one stage I tested this and was able to get it work with a test mailbox also hosted on Exchange 2013.. but maybe I never did.
    Does anyone know if this is possible at all (single Outlook profile, primary mailbox hosted on Exchange 2013 and other mailboxes on Exchange 2007). Most of our users have an additional mailbox mapped in their profile so I hope there is some way around this.
    Thank you!

    Hi,
    It is possible to open a shared mailboxes on a legacy server.
    Your problem could be caused by:
    Not having one of the later CU installed (read CU4 or CU5)
    Incorrect authentication methods configured (see link below)
    Outlook is not at the latest patch level
    Users of Exchange Server 2013 can't open public folders or shared mailboxes on an Exchange 2010 or Exchange 2007 server
    http://support.microsoft.com/kb/2834139
    Martina Miskovic

  • Mail for Exchange E61: getting "system error" whil...

    Hello everybody !
    our company is using MS Exchange 2007.If try try to sync the calender I am getting a "system error".
    Synchronizing the e-mail works fine.If I look in the admin log I see the following error.
    22/04/2007 01:15:49 start Calendar sync
    22/04/2007 01:15:51 client->server adds=0 changes=0 deletes=0 fails=0
    22/04/2007 01:15:51 server->client adds=0 changes=0 deletes=0 fails=0
    22/04/2007 01:15:57 sync died (3), collection=Calendar activity=encoding sync command
    sync died due error 3.Does someone know what err 3 means ? It would be very kind of you if someone interprets this log or is someone experiencing the same problem with MS Exchange 2007.
    I did not have this problem with MS Exchange 2003.
    All help would be greatly appreciated !
    Kind regards,
    Kuskaya

    Hi,
    updated the firmware.It works fine after firmware update.Exchange 2007 requeries the latest firmware.
    Regards,
    Cengiz Kuskaya

  • Exchange 2013 ECP 503 error

    I have a problem with my two Exchange 2013 servers. There are no mailboxes on the servers, because we are just beginning our migration from Exchange 2007. We are running Exchange 2013 SP1 on Server 2012R2
    When I try to access ecp/owa on ex01 (https://localhost or https://ex01.domain.local), I am presented with a login page, but after entering my credentials,
    I get a 503 error:
    Service Unavailable HTTP Error 503. The service is unavailable
    On ex02, I can RDP to the server and log into ecp/owa just fine. However, if I log in (https://ex02.domain.local) from another computer (like my PC), I get the
    same credential page and 503 error.
    I verified the following:
    All of the application pools and Exchange services are started
    I do not have any instances of event 2280 in the Application log
    I have also restarted the server
    Local security policy shows that Administrators and Backup Operators have "Allow log on locally" permission
    This feels like a permissions issue in IIS, but I'm not sure.
    My ECP virtual directory settings (both servers) look like this:
    InternalAuthenticationMethods : {Basic, Fba}
    BasicAuthentication : True
    WindowsAuthentication : False
    DigestAuthentication : False
    FormsAuthentication : True
    LiveIdAuthentication : False
    AdfsAuthentication : False
    OAuthAuthentication : False
    ExternalAuthenticationMethods : {Fba}
    Why won't ex01 let me log in and why would the login on ex02 work from the server, but 503 from my machine? Thanks.

    Hi,
    From your description, I would like to clarify the following things for troubleshooting:
    1. Make sure that the services are running under the Local System account.
    2. Ensure that the mailbox database that you want to access are mounted. Besides, the account you use to access ECP should have a mailbox in the Exchange server you are accessing.
    Hope my clarification can be helpful to you.
    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]
    Amy Wang
    TechNet Community Support

  • Cannot start Outlook 2007, a program error occurred. Tried lots of things....

    I'm getting an error message of: "Cannot start Microsoft Office Outlook. A program error occurred. Quite Outlook and Microsoft Windows and then start again. A program error occurred. Quite Outlook and Microsoft Windows and then start again." when
    I try to start Outlook 2007 running on windows 8.1.  (standalone with pst file, not exchange)
    I have tried:
    Restarting computer (hard boot)
    Running in safe mode: Outlook /safe
    Resetting the nav panel: Outlook /resetnavpane
    Running scanpst on the pst files.
    Outlook /cleanprofile
    Creating a new profile
    Checking if windows search is running (it was) and restarting it.
    All with the same error message.
    I'm stumped. Any ideas how to get Outlook to open? Was there some sort of windows update that ran last night and messed up Outlook? It worked at end of day yesterday.
    Thanks in advance.

    Thank you for the update, seems the problem has been resolved, right? If this issue comes back or you need further assistance on it, please feel free to contact us.
    Cheers,
    Steve Fan
    TechNet Community Support

Maybe you are looking for