Exchange 2007 Version Issue

We are installing an Exchange 2013 Server in a small environment with an Exchange 2007 server.
When going through the Readiness Checks during the Exchange 2013 Install it fails for the following reason:
"All Exchange 2007 servers in the organization must have Exchange 2007 SP3 or later installed."
This is an issue because on SP3 has been installed on the Exchange 2007 server, but when looking at the version in EMC it shows as (8.1) which corresponds to SP1.
I checked out the following blog post, and it states to check version based on the properties of the EXSetup.exe file.
http://blogs.technet.com/b/exchange/archive/2010/03/08/3409469.aspx
When I did this, I found that the version installed is in fact:
08.03.0342.004
Which corresponds to Exchange 2007 SP3.
While most posts seem to say "It's fine, the server is updated without issue", this is a problem for me because it won't let me install Exchange 2013 in the environment.
Anyone have any ideas to how to resolve the issue with the Exchange 2007 server, or to continue the installation of Exchange 2013.
Thank you,

Hi Gabriel,
You need to have Exchange 2007 SP3 RU11 inorder to bring exchange 2013 in the environment.Only then it will allow you to install Exchange 2013.
I would suggest you to install the latest rollup Exchange 2007 SP3 RU12 and proceed with Exchange 2013 installation
link for Ex2007 Ru11 -
http://www.microsoft.com/en-us/download/details.aspx?id=41393
Please 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.
Regards,
Sathish
website - exchangequery.wordpress.com

Similar Messages

  • Snow Leopard and Exchange 2007 Configuration Issues

    I know this topic may have been covered in here previously but I have yet to find a solution.
    Here is the background. Our CEO has a Mac Book and two weekends ago he updated to Snow Leopard and now wants to use the Mail client on his Mac rather than OWA to get his email. We have Exchange 2007 (I am the Admin) and have all the latest patches and Roll Ups installed. We run OWA without issue and have 10 iPhones working perfectly (i realized they use different technology to sync). I enabled EWS by following this link http://technet.microsoft.com/en-us/library/bb201695.aspx and this is the actual command i used:
    Set-WebServicesVirtualDirectory -identity exchaname\EWS* -externalurl https://webmail.domain.com/EWS/Exchange.asmx -BasicAuthentication:$True
    Seems to have run properly and there are no errors reported.
    Now when I go to connect using the Mac it does not Auto Discover and I must enter manually. I enter what i think it needed and its not working. On the Account Information Tab I have the following:
    Description: generic name
    Email Address: [email protected]
    Full Name: The Person's Name
    Internal Server: webmail.domain.com *Not sure what should be here
    External Server: Webmail.domain.com *Again not sure if this is correct
    Username: AD user name Also tried domain\username
    Password: AD password
    Ougoing Mail Server: not sure what should be here
    Next is the Mailbox behavior Tab:
    Did not change anything
    Advanced Tab:
    Internal Server Path: EWS/Exchange.asmx
    Port:80 SSL unchecked
    External Server: EWS/Exchange.asmx
    Port: 80 SSL unchecked
    I get no connections and I am sure somehting is not correct in the above but I am lost and new to Exchange as it is. Also new to Mac's
    Help Please

    We are already using webmail.domain.com for our OWA URL, well actually it is webmail.domain.com\OWA. Would I need one for the EWS & Autodiscover to use webmail.domian.com\ews?
    We have rules in the firewall for Exchange and OWA. Would we need another for this?

  • Exchange 2007 Mail issue, server rejecting password

    Hi all.
    We have installed Exchange 2007 server today and configured it and all windows clients and iPhones. windows clients on normal RPC settings and laptops on RPC over HTTP.
    Webmail has also been configured which works fine with a trusted root certificate. webmail works fine in safari also.
    we have a problem configuring Mail on two SL macbooks. when running the setup and entering the password the client app comes back repeatedly and says 'The Exchange 2007 server “exchange.domain.co.uk” rejected the password for user “username” '
    i have tried this on both machines and im kind of stuck since the exchange server is fully function for all other devices.
    For info, the exchange server is on SP1 rollup 9. running on windows server 2008 R2 x64
    i changed the outgoing server field to be the internal IP just to check and i get the prompt for the SSL (obviously since the SSL does not include the IP. i click to import and accept which it does but i still get my password rejected.
    Any ideas?

    Seems like an issue with a December update. I found the following info that basically tells you to go to IIS SSL settings for the OWA (and related sites) and change the client to "accept certificate". It worked for me so hopefully this will help someone else.
    The following text was found on:
    http://social.technet.microsoft.com/Forums/en/exchangesvrgeneral/thread/383d130e -869f-4fce-9502-8b340904b0ba
    EDIT: Found a fix for me potentially via - http://social.technet.microsoft.com/Forums/en-US/exchangesvrdeploy/thread/c1e72d 2a-d360-4ff0-b2f5-1a9ae149df18 and http://www.microsoft.com/communities/newsgroups/list/en-us/default.aspx?dg=micro soft.public.exchange.admin&mid=00d4a681-f588-4eed-b4f8-5c3645e7376c&sloc=en-us
    I had an issue similar to this. Win2k3 Ex07. All of my Outlook 2007
    users were getting prompted over and over for the username and
    password. It wasn't checking the certificate that they had installed
    via internet explorer. To fix the problem, I opened IIS on the
    Exchange server and checked the following directories under the
    default website (the root site(default web site), oab, autodiscover).
    Under the directory security tab, click Edit in the Secure
    Communications section. I had the require SSL checked and the 128bit
    encryption, but under Client Certificates, it was set to ignore. Once
    I changed that to Accept for each of the folders, stopped and started
    IIS, I stopped being prompted all the time for credentials. Hopefully
    this will help someone in the future.
    Just confirmed fixed for client!!!
    -IL

  • IMAP Exchange 2007 & Password Issue

    Anybody else having trouble with getting the IMAP 2007 Exchange account to hold a password?
    When I set account up, it downloads my email to Mail but then keeps asking me for the password and doesn't show it in the account.
    Only way I can get my email from it is to delete and recreate account.????

    I have the same problem. I am using nhs.net. I can have mail open for hours and then it just starts rejecting my password, requiring me to get my account reset (nhs.net automatically logs you out after 3 failed attempts). nhs.net does use Exchange 2007. When it happened today I noticed it was shortly after I had opened addressbook, I cannot remember whether the other times this has happened it is after opening addressbook.
    However on looking in addressbook preferences I notice there are 2 exchange settings for nhs.net giving me 2 nhs.net addressbooks - each with a different server depending on whether I connect from within the network or from outside the network. The same is true of ical, but not mail. Why is this so - does this have something to do with the problem i.e the password is only getting updated in one so that the other is returning the old password and getting me logged out?

  • Outlook 2013 ask credential for connecting to Exchange 2007

    Hi,
    i've a big problem into my business from about 2 weeks. We have deployed 5 new pc with Office 2013 Professional and Windows 7 professional, into our server we have exchange 2007 version 8.3 and build 83.6
    Only for 1 client outlook works correctly but into other 4 client we have same problem. After open outlook 2013 is all ok and i see "connected to Microsoft Exchange" but after 2 minutes outlook always asks for password prompt. When i insert the
    password the client request the same password into loop. 
    Despite asks for credential i receive correctly the emails.
    From now i've tried this solution that i read online but none of these works correctly.
    1- delete and create new outlook profile
    2- I have changed the authentication to NTLM instead of Basic Authentication
    3- Delete credential from Control Panel --> Credential Manager
    4- Disable the setting "Always prompt for logon credentials"
    5- try to change user password from owa
    Other information:
    User can access to owa and work correctly, autodiscover is running correctly because i setup the account with it.
    I've tried to test outlook connection with press ctrl and left click into outlook taskbar.
    Why outlook always ask me for credential? This is very frustrating because only 1 client works correcly.
    I'm waiting for your kindly response.
    Matteo

    Hi Matteo,
    What’s your Outlook connection status? Confirm your Protocol is RPC/TCP (internal) or RPC/HTTP (external)? Please try to configure your problematic account in the Outlook client which is the only one working correctly to check whether the issue persists.
    If all other 4 accounts can work well in the “good” one client, please check whether there is any difference between the account settings in different PC.
    Thanks,
    Winnie Liang
    TechNet Community Support

  • Updated Office 2011 for Mac (14.4.1), cannot connect to Exchange server (Exchange 2007).

    I updated Office 2011 for Mac to its 14.4.1 version and, out of the blue, it could not connect to the Exchange server anymore. At my office they use Exchange 2007 and I am the only Mac in the building. I've deleted the account and added it again countless
    times, and it reports username, password or security configuration issues. 
    I checked the HD (everything OK) and repaired the main identity (everything OK). 
    Still, I cannot get the color button to go from orange to green. 
    Hope someone can help. 

    That's weird. I'll try to reproduce it in our labs.
    What's the Exchange 2007 version? You can get it in EMS (Exchange Management Shell) with:
    GCM exsetup |%{$_.Fileversioninfo}
    I guess you are running Mavericks v10.9.3, and you are trying to connect locally?
    Step by Step Screencasts and Video Tutorial

  • Exchange 2007 to 2013 Migration issues. Prompt for credentials, Public Folders inaccessible, Apps not working

    Exchange 2013 Migration issues
    I have three issues and decided to list them here. Please pick and choose to assist. Thanks in advance.
    Environment:
    Mixed 2007 SP3 R12 and 2013 CU3. 2007 Environment was webmail.domain.com. I installed new Exchange 2013 (1 CAS, 1 Mailbox) according to:
    http://technet.microsoft.com/en-us/library/ff805032(v=exchg.150).aspx. Exchange 2007 is now legacy.domain.com and Exchange 2013 CAS is webmail.domain.com.
    Machine 1: Windows 8.1, not domain joined, using Outlook Anywhere external. Outlook 2013
    Machine 2: Windows 7, domain joined, using Outlook Anywhere internal. Outlook 2010 SP2
    I have migrated 1 user so far to Exchange 2013. This user was a Domain Admin. I have removed that membership. I checked the box to inherit permissions of the security of the object and reset the AdminCount attribute in ADSIedit to 0 and verified this replicated
    to all domain controllers. ( I originally thought this to be the issue with it prompting for the password. )
    Here is a Get-OutlookAnywhere cmdlet...
    ServerName                         : EXCHANGE2007SVR
    SSLOffloading                      : False
    ExternalHostname                   : legacy.domain.com
    InternalHostname                   :
    ExternalClientAuthenticationMethod : Basic
    InternalClientAuthenticationMethod : Basic
    IISAuthenticationMethods           : {Basic}
    XropUrl                            :
    ExternalClientsRequireSsl          : True
    InternalClientsRequireSsl          : False
    MetabasePath                       : IIS://EXCHANGE2007SVR.domain.local/W3SVC/1/ROOT/Rpc
    Path                               : C:\WINDOWS\System32\RpcProxy
    ExtendedProtectionTokenChecking    : None
    ExtendedProtectionFlags            : {}
    ExtendedProtectionSPNList          : {}
    AdminDisplayVersion                : Version 8.3 (Build 83.6)
    Server                             :
    EXCHANGE2007SVR
    AdminDisplayName                   :
    ExchangeVersion                    : 0.1 (8.0.535.0)
    Name                               : Rpc (Default Web Site)
    DistinguishedName                  : CN=Rpc (Default Web Site),CN=HTTP,CN=Protocols,CN=EXCHANGE2007SVR,CN=Servers,CN=Exchange
                                         Administrative Group (FYDIBOHF23SPDLT),CN=Administrative
                                         Groups,CN=DOMAIN,CN=Microsoft
                                         Exchange,CN=Services,CN=Configuration,DC=DOMAIN,DC=local
    Identity                           : EXCHANGE2007SVR\Rpc (Default Web Site)
    Guid                               : 4901bb14-ab81-4ded-8bab-d5ee57785416
    ObjectCategory                     : domain.local/Configuration/Schema/ms-Exch-Rpc-Http-Virtual-Directory
    ObjectClass                        : {top, msExchVirtualDirectory, msExchRpcHttpVirtualDirectory}
    WhenChanged                        : 12/31/2013 4:08:04 PM
    WhenCreated                        : 7/18/2008 10:56:46 AM
    WhenChangedUTC                     : 12/31/2013 9:08:04 PM
    WhenCreatedUTC                     : 7/18/2008 2:56:46 PM
    OrganizationId                     :
    OriginatingServer                  : DC1.domain.local
    IsValid                            : True
    ObjectState                        : Changed
    ServerName                         :
    EXCHANGE2013SVR
    SSLOffloading                      : True
    ExternalHostname                   : webmail.domain.com
    InternalHostname                   : webmail.domain.com
    ExternalClientAuthenticationMethod : Basic
    InternalClientAuthenticationMethod : Ntlm
    IISAuthenticationMethods           : {Basic, Ntlm}
    XropUrl                            :
    ExternalClientsRequireSsl          : True
    InternalClientsRequireSsl          : True
    MetabasePath                       : IIS://EXCHANGE2013SVR.domain.local/W3SVC/1/ROOT/Rpc
    Path                               : C:\Program Files\Microsoft\Exchange Server\V15\FrontEnd\HttpProxy\rpc
    ExtendedProtectionTokenChecking    : None
    ExtendedProtectionFlags            : {}
    ExtendedProtectionSPNList          : {}
    AdminDisplayVersion                : Version 15.0 (Build 775.38)
    Server                             : EXCHANGE2013SVR
    AdminDisplayName                   :
    ExchangeVersion                    : 0.20 (15.0.0.0)
    Name                               : Rpc (Default Web Site)
    DistinguishedName                  : CN=Rpc (Default Web Site),CN=HTTP,CN=Protocols,CN=EXCHANGE2013SVR,CN=Servers,CN=Exchange
                                         Administrative Group (FYDIBOHF23SPDLT),CN=Administrative
                                         Groups,CN=DOMAIN,CN=Microsoft
                                         Exchange,CN=Services,CN=Configuration,DC=DOMAIN,DC=local
    Identity                           : EXCHANGE2013SVR\Rpc (Default Web Site)
    Guid                               : d983a4b1-6921-4a7f-af37-51de4a61b003
    ObjectCategory                     : domain.local/Configuration/Schema/ms-Exch-Rpc-Http-Virtual-Directory
    ObjectClass                        : {top, msExchVirtualDirectory, msExchRpcHttpVirtualDirectory}
    WhenChanged                        : 1/7/2014 11:29:05 AM
    WhenCreated                        : 12/31/2013 1:17:42 PM
    WhenChangedUTC                     : 1/7/2014 4:29:05 PM
    WhenCreatedUTC                     : 12/31/2013 6:17:42 PM
    OrganizationId                     :
    OriginatingServer                  : DC1.domain.local
    IsValid                            : True
    ObjectState                        : Changed
    ISSUE 1
    Issue: On Machine 1 (reference above) Windows Security prompt that says "Connecting to
    [email protected]". Almost always prompts when Outlook is first opened. Afterwards (if it goes away) seemingly random on when it asks for it. I put in the credentials (absolutely correct) and it fails and prompts again.
    I always check the box for it to save the password. To get rid of it, I click the Cancel button at which Outlook reports "NEED PASSWORD", but still acts fine sending and receiving emails. Eventually the "NEED PASSWORD" sometimes changes
    to say "CONNECTED", but it works regardless.
    No issues on Machine 2 so I don't know where the problem might be as there are a lot of variables in play here.
    ISSUE 2
    Migrated user is unable to open Public folders from Exchange 2007.
    Cannot expan the folder. Microsoft Exchange is not available. Either there are network problems or the Exchange server is down for maintenance. (/o=...).
    This error occurs on Machine 1, Machine 2 and from OWA, same error each time.
    ISSUE 3
    Apps. Installed by default are 4 apps (Bing Maps, Suggested Meetings, Unsubscribe, Action Items). I have made sure the apps are enabled in OWA and they show up in mail items on both Machine 1 (Outlook 2013) and OWA. They do not show up in Machine 2 (Outlook
    2010). I'm assuming that isn't supported.
    In OWA, when I go to the installed apps listing it shows all of the apps but has a broken link on the image describing the app.
    When I click the app in either Outlook 2013 or in OWA, I get "APP ERROR, Sorry we can't load the app. Please make sure you have network and/or internet connectivity. Click "Retry" once you're back online.
    Current workaround is just disabling them through OWA.

    Hello,
    In order to avoid confusion, we troubleshoot a issue per thread usually.
    For your first isue, I agree with Ed's suggestion to check if your certificate name is correct.
    Besides, I recommend you change ExternalClientAuthenticationMethod from Basic authentication to Negotiate authentication to check the result.
    For the second issue and third issue, please create a new post.
    If you have any feedback on our support, please click here
    Cara Chen
    TechNet Community Support

  • TS4136 Apple Mail ActiveSync issue during Exchange 2007 to Exchange 2010 migration

    When customer configures the ActiveSync account on Apple Mail (using Exchange Server 2010 CAS array name) for the user whose mailbox is on Exchange Server 2007, they are not able to get any mail and account displays offline. It shows the mailbox empty as well, even though mailbox has the email items in it.
    But when same account is configured using ActiveSync (using Exchange 2007 CAS Server name) it works fine.
    ActiveSync & Web Services URLs for Exchange 2010 and Exchange 2007 are given as below:
    S#
    Virtual Directory
    URL
    Exchange Server 2010
    Exchange Server 2007
    1
    Web Services Virtual Directory
    Internal URL
    https://email2.domain.ae/EWS/Exchange.asmx
    https://email.domain.ae/EWS/Exchange.asmx
    2
    Web Services Virtual Directory
    External URL
    https://email2.domain.ae/EWS/Exchange.asmx
    https://email.domain.ae/EWS/Exchange.asmx
    3
    ActiveSync Virtual Directory
    Internal URL
    https://email2.domain.ae/Microsoft-Server-ActiveSync
    https://email.domain.ae/Microsoft-Server-ActiveSync
    4
    ActiveSync Virtual Directory
    External URL
    https://email2.domain.ae/Microsoft-Server-ActiveSync
    https://email.domain.ae/Microsoft-Server-ActiveSync
    Following error is logged on Console on Mac when this issue happens:
    30/10/12 3:27:28.398 AM
    Mail
    *** Assertion failure in -[EWSConnection _fetchRootFolderId:], /SourceCache/Message/Message-1278/MessageStores.subproj/EWSConnection.m:202
    EWS fetchRootFolderId: expected one folder in response, received: 0
    0   Message                             0x00007fff8cdeeef8 -[MFAssertionHandler _handleFailureWithPreamble:description:arguments:] + 116
    1   Message                             0x00007fff8cdef08e -[MFAssertionHandler handleFailureInMethod:object:file:lineNumber:description:] + 185
    2   Message                             0x00007fff8cd1c8db -[EWSConnection _fetchRootFolderId:] + 768
    3   Message                             0x00007fff8cd1deba -[EWSConnection _connectAndAuthenticateUsingAccount:] + 650
    4   Message                             0x00007fff8cd1c42d -[EWSConnection connectUsingAccount:] + 462
    5   Message                             0x00007fff8cd1996a -[EWSAccount authenticatedConnection] + 437
    6   Message                             0x00007fff8cd2c00e -[EWSGateway connection] + 55
    7   Message                             0x00007fff8cd2dddf -[EWSGateway sendMessage:forRequest:] + 43
    8   Message                             0x00007fff8cd3e54c -[EWSRequestOperation executeOperation] + 108
    9   Message                             0x00007fff8ce0f97f -[MonitoredOperation main] + 228
    10  Foundation                          0x00007fff94aae6b4 -[__NSOperationInternal start] + 705
    11  Foundation                          0x00007fff94ac1912 ____NSOQSchedule_block_invoke_2 + 124
    12  libdispatch.dylib                   0x00007fff8adc8a86 _dispatch_call_block_and_release + 18
    13  libdispatch.dylib                   0x00007fff8adc9965 _dispatch_worker_thread2 + 255
    14  libsystem_c.dylib                   0x00007fff8a32c3da _pthread_wqthread + 316
    15  libsystem_c.dylib                   0x00007fff8a32db85 start_wqthread + 13

    Hi Akebono,
    Let's check a few things in your server:
    1. From the Organization Configuration - Client Access - Exchange Activesync policies - Default: Verify if the option "Allow non-provisionable devices" is ON.
    2. From Server Configuration - pointing <YourExchange2010> - Certificates: Verify if your SSL certificate is assigned to IIS. (You should also be able to see this certificate from OWA https session)
    3. The problem may also reside in iPhone outdated software, try to test activesync connection from iPhone with the latest OS version.
    4. Take a look at logs in C:\inetpub\logs\LogFiles\W3SVC1\ of Exchange 2010, those might give some more details on connectivity problems.
    5. If you still experience such problems - post the ExRCA error report here.
    ▲ Vote if Helpful / Mark if Answer
    MCSE: Messaging 2013 Charter / Private Cloud / Server Infrastructure
    MaximumExchange.ru

  • Exchange 2007 transaction log issue

    Hi All,
    One of my clients if having an Issue with their exchange 2007 server, running multiple exchange dbs for different sections of their business.
    1 of the 4 dbs (the smallest one) is having drop out issues, the exchange server has dismounted the db each night this week when the backup Exec 2010 running it fails with code E000032D. Which according to Symantec literature means as bad transaction
    log.
    upon looking at the files in the log folder i noticed there are a number of logs that have been duplicated and have a .delete file type.
    Can anyone give me any info on how to fix this???
    I have tried running an NTback in the hope that a more simple backup program might be more forgiving with the damaged logs.
    When this didn't work (failed to backup of stay mounted last night) I have tried to use circular logging to purge the logs today followed by another NTbackup of the exchange store in question. 
    The logs folder is still showing the .delete version of the log and I guessing we are nort going to get a successful backup tonight.
    The issue arose at the end of last week when a disk failed due to overheating when the server rooms AC went out for the weekend.
    Thanks in advance for your help,
    Joseph Atie

    Hi Joseph,
    From your description, I recommend you follow the steps below for troubleshooting:
    1. Please move the transaction log files to a safe directory of a different store at first.
    2. Mount this store and start the backup.
    What's more, circular logging is not recommended. Here is a blog for your reference.
    Exchange Circular Logging and VSS Backups
    http://blogs.technet.com/b/exchange/archive/2010/08/18/3410672.aspx
    Hope it helps.
    If there are any problems, please feel free to let me know.
    Best regards,
    Amy
    Amy Wang
    TechNet Community Support

  • Intermittent OWA authtication issue for new users on Exchange 2007

    Hi
    We are experiencing a strange issue with OWA authentication and its happening with new users only including me. We are a small organization with approx. 70 users. Issue is with
    new user accounts only.
    Access to OWA stops working from any machine for the new users also they get authentication error on their phones. I have checked permissions on Virtual Directory on exchange server,
    all seems to be in place. I have checked event viewer but it doesn't have any event for auth. failure.
    IIS logs have the following Message,
    2014-02-05 09:37:28 W3SVC1 (EXCHANGE SERVER IP) GET /owa/ - 443 myusername 77.88.97.134 Mozilla/5.0+(Windows+NT+6.3;+WOW64;+Trident/7.0;+rv:11.0)+like+Gecko
    401 1 1326
    Server details
    Server 2003 Ent. x64 R2
    Exchange Server 2007 Version: 08.03.0342.000
    IIS 6.0
    Rebooting the exchange server resolves the issue sometime for 2 days sometime for 3-4 weeks.
    Please advise.
    Best Regards
    Prabhash

    Hi,
    According to your description, new users cannot login OWA .
    And to narrow down the cause, I recommend the following troubleshooting:
    1. Check if the option"User must change password on next login" has been selected for the new users.
    2. Check if the new users can login Outlook when the issue happens.
    3. Check if it’s configured to use Integrated Windows authentication for OWA web site:
    http://support.microsoft.com/kb/871179
    If you have any question, please feel free to let me know. 
    Thanks,
    Angela Shi
    TechNet Community Support

  • Issue moving remote user from exchange 2007 to 2013

    have moved over 60 people so far from exchange 2007 to 2013, it was going well with no major problems.
    during migration I have created a DNS setting called legacy.mydomain.com, and it points to the old exchange server, while mail.mydomain.com points to the new exchange server.  
    outlook was working connecting to both servers, and OWA was working on both servers.
    couple of remote users who connect via SSL-VPN and outlook 2010 had issues connecting, but as soon as I moved them to 2013 exchange they connected without vpn using outlook anywhere.
    but - I have one remote user who even though the mailbox move to the new 2013 server was successful, their outlook still points to the 2007 exchange server.
    if I try creating a new profile in outlook 2013, it fails because it cannot contact exchange server, even when ssl-vpn is running.
    when I started troubleshooting I found lots of spyware on his laptop, symantec had been blocking some trojans, obviously he had downloaded something he shouldnt have.
    could this have caused my outlook connectivity issue?
    I ran malawarebytes, and it shows clean now, but still unable to get his outlook to connect.
    I had thought about moving his mailbox back to the old server, seeing if it works on outlook, then moving it to the new one again.
    any suggestions?

    I had thought about moving his mailbox back to the old server, seeing if it works on outlook, then moving it to the new one again.
    Hi,
    Have you done this step? Sometimes moving mailbox to another database can auto-fix problems.
    According to your description, I know that all migrated mailboxes work well except a specific user. I notice that the user's laptop has a lots of spyware, and symantec has been clocking some trojans.
    Please try to logon OWA to check whether this user works.
    If works in OWA, it seems that the mailbox has been migrated to 2013 successfully.
    Generally, re-creating profile can fix this issue. Unfortunately, you have tried it and failed.
    Please try to run Outlook under safe mode to avoid AVs and add-ins.
    Thanks
    Mavis Huang
    TechNet Community Support

  • MS Exchange 2007 - 64 bit and Entourage Client issue

    Hi guys -
    I'm a new one with Mac and I have got this problem so far:
    I have Exchange 2007 on 32 and 64 bit platforms
    from the Entourage I can see all mailboxes that are on Exchange 32 bit server and no issues at all here... I just go and add Exchange account and that's it...
    but the problem is when I do the same for any mailbox which is sitting on Exchange 64 bit server -> nothing happens no errors, nothing... I don't see anything at all...
    The question is: what I have missed here? or perhaps, it's not supported yet... Is there any kind of workaround
      Mac OS X (10.4.9)  

    Since Entourage is not an Apple product, you'll get better response if you use a forum dedicated to Microsoft's Mac products such as <http://groups.google.com/groups/dir?sel=33607053> rather than an Apple forum.
    Be sure to search the forum first in case someone has already had a similar question answered. You'll get your answer faster this way. Post your question in the forum if you don't find anything that helps you.

  • Exchange 2007 Active Sync Issue with 1 users mailbox

    Good Afternoon,
    Server OS:  Small Business Server 2008
    Exchange:  2007 Standard - Update Rollup 13 SP3
    Mobile phone:  Blackberry Z10
    We are in the process of decommissioning our Blackberry Enterprise Server, and down to one user.  I am able to setup Exchange on his new non BES server tied phone, but it will not sync any email, all Meetings, and only some contacts.  I have tried
    adding this account to an Android phone with the same results.  I have numerous times went into EMC and delete the Mobile device, when re-adding the account, everything seems to point to his exchange account being the culprit.  I am getting the below
    Active Sync error after adding his account.  I have Bing / Googled around, and nothing of substance I have found.  Thank you in advance!
    Log Name:      Application
    Source:        MSExchange ActiveSync
    Date:          3/24/2015 2:01:15 PM
    Event ID:      1008
    Task Category: Requests
    Level:         Warning
    Keywords:      Classic
    User:          N/A
    Computer:      SISBS.internaldomain.local
    Description:
    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=/Microsoft-Server-ActiveSync/default.eas?Cmd=FolderSync&DeviceType=BlackBerry&User=bbevers&DeviceId=BB3359D356
    --- Exception start ---
    Exception type: Microsoft.Exchange.AirSync.AirSyncPermanentException
    Exception message: 
    Exception level: 0
    HttpStatusCode: 200
    AirSyncStatusCode: 6
    XmlResponse: 
    <?xml version="1.0" encoding="utf-8" ?>
    <FolderSync xmlns="FolderHierarchy:">
    <Status>6</Status>
    </FolderSync>
    Exception stack trace:    at Microsoft.Exchange.AirSync.FolderCommand.Execute()
       at Microsoft.Exchange.AirSync.Command.WorkerThread()
    Inner exception follows...
    Exception type: Microsoft.Exchange.Data.Storage.FolderSaveException
    Exception message: Unable to save sync state folder Root due to PartiallySucceeded, Property = [0x7c020102] SyncCustomState, PropertyErrorCode = MapiCallFailed, PropertyErrorCode = Properties could not be set.
    Exception = Microsoft.Exchange.Data.Storage.AccessDeniedException: Cannot set properties. ---> Microsoft.Mapi.MapiExceptionNoAccess: MapiExceptionNoAccess: Unable to set properties on object. (hr=0x80070005, ec=-2147024891)
    Diagnostic context:
        Lid: 18969   EcDoRpcExt2 called [length=7783]
        Lid: 27161   EcDoRpcExt2 returned [ec=0x0][length=88][latency=0]
        Lid: 23226   --- ROP Parse Start ---
        Lid: 27962   ROP: ropSetProps [10]
        Lid: 17082   ROP Error: 0x80070005
        Lid: 30561  
        Lid: 21921   StoreEc: 0x80070005
        Lid: 27962   ROP: ropExtendedError [250]
        Lid: 1494    ---- Remote Context Beg ----
        Lid: 26426   ROP: ropSetProps [10]
        Lid: 4559    StoreEc: 0x80070005
        Lid: 1750    ---- Remote Context End ----
        Lid: 26849  
        Lid: 21817   ROP Failure: 0x80070005
        Lid: 25761  
        Lid: 1940    StoreEc: 0x80070005
        Lid: 25297  
        Lid: 21201   StoreEc: 0x80070005
       at Microsoft.Mapi.MapiExceptionHelper.ThrowIfError(String message, Int32 hresult, Object objLastErrorInfo)
       at Microsoft.Mapi.MapiProp.SetProps(PropValue[] pva)
       at Microsoft.Exchange.Data.Storage.MapiPropertyBag.<SetProperties>b__3(PropValue[] propValues)
       at Microsoft.Exchange.Data.Storage.MapiPropertyBag.InternalSetProperties(PropertyDefinition[] propertyDefinitions, Object[] propertyValues, MapiSetProps mapiSetProps)
       --- End of inner exception stack trace ---
       at Microsoft.Exchange.Data.Storage.MapiPropertyBag.InternalSetProperties(PropertyDefinition[] propertyDefinitions, Object[] propertyValues, MapiSetProps mapiSetProps)
       at Microsoft.Exchange.Data.Storage.StoreObjectPropertyBag.FlushSetProperties()
       at Microsoft.Exchange.Data.Storage.FolderPropertyBag.SaveFolderPropertyBag(Boolean needVersionCheck)..
    Exception level: 1
    Exception stack trace:    at Microsoft.Exchange.Data.Storage.FolderSaveResult.ToException(String exceptionMessage)
       at Microsoft.Exchange.Data.Storage.SyncState.Commit(PropertyDefinition[] properties, Object[] values, Int32[] sizes)
       at Microsoft.Exchange.AirSync.FolderCommand.Execute()
    --- Exception end ---.
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="MSExchange ActiveSync" />
        <EventID Qualifiers="32772">1008</EventID>
        <Level>3</Level>
        <Task>1</Task>
        <Keywords>0x80000000000000</Keywords>
        <TimeCreated SystemTime="2015-03-24T19:01:15.000Z" />
        <EventRecordID>4756229</EventRecordID>
        <Channel>Application</Channel>
        <Computer>SISBS.internaldomain.local</Computer>
        <Security />
      </System>
      <EventData>
        <Data>/Microsoft-Server-ActiveSync/default.eas?Cmd=FolderSync&amp;DeviceType=BlackBerry&amp;User=bbevers&amp;DeviceId=BB3359D356</Data>
        <Data>--- Exception start ---
    Exception type: Microsoft.Exchange.AirSync.AirSyncPermanentException
    Exception message: 
    Exception level: 0
    HttpStatusCode: 200
    AirSyncStatusCode: 6
    XmlResponse: 
    &lt;?xml version="1.0" encoding="utf-8" ?&gt;
    &lt;FolderSync xmlns="FolderHierarchy:"&gt;
    &lt;Status&gt;6&lt;/Status&gt;
    &lt;/FolderSync&gt;
    Exception stack trace:    at Microsoft.Exchange.AirSync.FolderCommand.Execute()
       at Microsoft.Exchange.AirSync.Command.WorkerThread()
    Inner exception follows...
    Exception type: Microsoft.Exchange.Data.Storage.FolderSaveException
    Exception message: Unable to save sync state folder Root due to PartiallySucceeded, Property = [0x7c020102] SyncCustomState, PropertyErrorCode = MapiCallFailed, PropertyErrorCode = Properties could not be set.
    Exception = Microsoft.Exchange.Data.Storage.AccessDeniedException: Cannot set properties. ---&gt; Microsoft.Mapi.MapiExceptionNoAccess: MapiExceptionNoAccess: Unable to set properties on object. (hr=0x80070005, ec=-2147024891)
    Diagnostic context:
        Lid: 18969   EcDoRpcExt2 called [length=7783]
        Lid: 27161   EcDoRpcExt2 returned [ec=0x0][length=88][latency=0]
        Lid: 23226   --- ROP Parse Start ---
        Lid: 27962   ROP: ropSetProps [10]
        Lid: 17082   ROP Error: 0x80070005
        Lid: 30561  
        Lid: 21921   StoreEc: 0x80070005
        Lid: 27962   ROP: ropExtendedError [250]
        Lid: 1494    ---- Remote Context Beg ----
        Lid: 26426   ROP: ropSetProps [10]
        Lid: 4559    StoreEc: 0x80070005
        Lid: 1750    ---- Remote Context End ----
        Lid: 26849  
        Lid: 21817   ROP Failure: 0x80070005
        Lid: 25761  
        Lid: 1940    StoreEc: 0x80070005
        Lid: 25297  
        Lid: 21201   StoreEc: 0x80070005
       at Microsoft.Mapi.MapiExceptionHelper.ThrowIfError(String message, Int32 hresult, Object objLastErrorInfo)
       at Microsoft.Mapi.MapiProp.SetProps(PropValue[] pva)
       at Microsoft.Exchange.Data.Storage.MapiPropertyBag.&lt;SetProperties&gt;b__3(PropValue[] propValues)
       at Microsoft.Exchange.Data.Storage.MapiPropertyBag.InternalSetProperties(PropertyDefinition[] propertyDefinitions, Object[] propertyValues, MapiSetProps mapiSetProps)
       --- End of inner exception stack trace ---
       at Microsoft.Exchange.Data.Storage.MapiPropertyBag.InternalSetProperties(PropertyDefinition[] propertyDefinitions, Object[] propertyValues, MapiSetProps mapiSetProps)
       at Microsoft.Exchange.Data.Storage.StoreObjectPropertyBag.FlushSetProperties()
       at Microsoft.Exchange.Data.Storage.FolderPropertyBag.SaveFolderPropertyBag(Boolean needVersionCheck)..
    Exception level: 1
    Exception stack trace:    at Microsoft.Exchange.Data.Storage.FolderSaveResult.ToException(String exceptionMessage)
       at Microsoft.Exchange.Data.Storage.SyncState.Commit(PropertyDefinition[] properties, Object[] values, Int32[] sizes)
       at Microsoft.Exchange.AirSync.FolderCommand.Execute()
    --- Exception end ---</Data>
      </EventData>
    </Event>

    Hello,
    Yes, it means the mailbox is corrupted. The most efficeint way is to rebuild the user's mailbox.
    Thanks,
    Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact
    [email protected]
    Simon Wu
    TechNet Community Support

  • ICal + Exchange 2007 - recurring events issues

    Hi all
    Not sure if this has been brought up before, couldn't find anything on the boards.
    Anyway, our client has 20 macbook pros all running OS 10.6.2. They also have an Exchange 2007 server (previously they had a 2003 exchange server and were using entourage).
    The problem they appear to be having is when creating a recurring event they invite selected users but the invites either don't get through or upon accepting the invite it doesn't show up in the other user's calendar. I've heard there are some issues with iCal and recurring events - is this true or does anyone know a way to fix this?
    Thanks in advance.

    https://developer.apple.com/bugreporter/
    You can also try http://www.apple.com/feedback/macosx.html but I don't think that's as useful.

  • Exchange 2007 SP3 default quota issue

    This is an odd one.
    We use Exchange 2007 SP3 running on Server 2003 R2, the domain is 2008 R2.
    We have a default mailbox size limit of 900MB (issue warning) 1GB (stop sending) 1.25GB (stop send and receive). This has been in place since before I started working here 8 months ago. Until yesterday we had no reason to look at this in too much detail,
    we have plenty of storage and have only ever had issues with log files filling up previously.
    However, yesterday afternoon we suddenly had over 130 mailboxes unable to send or receive, others unable to send and a number of users got warnings that they were close to their limit. Some of the ones unable to send or receive have the default quota set
    yet had mailboxes almost double the upper limit. It's as if the rule had never applied then suddenly decided to enforce itself.
    Additionally, some of the executive level users, as standard they have a manually set quota, were included in the default rule.
    Initially I thought someone was doing a cleanup and had changed the settings on these accounts, but Exchange and AD both show no amendments to any of these accounts in the last 36 hours, so it was not that.
    The scan for mailbox size is set to run once a day at 01:00, given we are in the Central time zone (GMT -6 hours, though we have already moved the clocks forward so we are 5 hours behind for the moment)) even if we take it that the 01:00 is UTC it should
    not have run until 20:00 Central, the sudden enforcement of the quota happened at around 15:00 so that doesn't explain it either.
    No patches or updates have been installed on the Exchange servers this month, the servers have not rebooted and we did not failover to the secondary server.
    Does anyone have any idea what could have caused this? I have some very unhappy executives and senior managers who want an answer I can't give them right now....

    So, which are you more concerned with: the fact that quotas may have been altered, or what it was that filled the mailboxes?
    If it's with modifications to the AD, I think the first order of business would be to review who has permission to make such modifications. Maybe forcing everyone to change their password would be a good thing (and enforcing a strong password policy in the
    process).
    If it's "what filled the mailboxes", I'll ask the question again: what filled the mailboxes? You can examine individual mailboxes or use the message tracking logs as a starting point.
    --- Rich Matheisen MCSE&I, Exchange MVP

Maybe you are looking for