Exchange 2007 SP3 RU compatibility with Exchange 2013 lattest CU
Hi Team,
I have question, I want to migrate my exchange 2007 to 2013.
right now exchange 2013 already provide CU7.
My question is, is exchange 2013 CU7 compatible with Exchange 2007 SP3 lattest RU (SP3 RU15) ?
is there any limitation of version if i want to upgrade Exchange 2007 to 2013
Thanks Before
Hello,
The first thing I would say, is that the MINIMUM supported update for Exchange 2007 is SP3 RU 10, so you should be ok with RU15 installed with Exchange 2013 Cu7.
https://technet.microsoft.com/en-us/library/aa996719(v=exchg.150).aspx
The second thing I would say, and I am not sure how you're current environment is configured and how you plan on configuring your future environment, but if you are using Public Folders, Exchange 2013 CU7 changes the way public folders are handled during
coexistence. I would recommend taking a look at this blog post from The Exchange Team
https://technet.microsoft.com/en-us/library/aa996719(v=exchg.150).aspx
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread
Similar Messages
-
Can Exchange 2007 to be integrated with SharePoint 2013
Can Exchange 2007 to be integrated with SharePoint 2013?
In the sense of using Incoming and Outgoing email, absolutely. But not for other things, like Site Mailboxes, which require Exchange 2013.
Trevor Seward
Follow or contact me at...
  
This post is my own opinion and does not necessarily reflect the opinion or view of Microsoft, its employees, or other MVPs. -
SBS2008: Move email from Exchange 2007 to new server with Exchange 2013
We have an old server (SBS2008) and plan to buy a new server with (Server 2012). I need to move all the exchange emails, contacts & calendars to the new server. We will no longer use the old server.
Is there a document or migration tool that will help me understand how to move this data form the old exchange server to the new one?
Old Server:
SBS2008 running Exchange 2007
New Server:
Server 2012
Exchange 2013
Any help is appreciated!Hi Dave,
It can be done, and as Larry suggested you will consider two Server 2012 installs in order to achieve an environment that looks like your current SBS roles; Exchange 2013 on an Active Directory controller isn't a good long-term solution (SBS did this for
you in the past).
For your size operation, a virtual server host, with a Windows Server 2012 license, and two virtual machines would probably be a suitable design model. In this manner, you have Server 2012 license that permits 1 +2 licenses (one host for virtualization,
up to 2 Virtual Machines on same host).
There's no migration tool. That comes with experience and usually trial and error. You earn the skills in this migration path, and for the average SBS support person you should plan on spending 3x (or more) your efforts estimate in hours planning your migration.
You can find a recommended migration path at this link to give you an idea of the steps, but its not exactly point by point going to cover you off for an sbs2008 to server 2012 w/exchange 2013 migration. But the high points are in here. If it looks
like something you would be comfortable with then you should research more.
http://blogs.technet.com/b/infratalks/archive/2012/09/07/transition-from-small-business-server-to-standard-windows-server.aspx
Specific around integrating Exchange 2013 into an Exchange 2007 environment, guidance for that can be found here:
http://technet.microsoft.com/en-us/library/jj898582(v=exchg.150).aspx
If that looks like something beyond your comfort level, then you might consider building a new 2012 server with Exchange 2013 environment out as new, manually export your exchange 2007 mailbox contents (to PST) and then import them into the new mail server,
and migrate your workstations out of old domain into new domain. Whether this is more or less work at your workstation count is dependent upon a lot of variables.
If you have more questions about the process, update the thread and we'll try to assist.
Hopefully this info answered your original question.
Cheers,
-Jason
Jason Miller B.Comm (Hons), MCSA, MCITP, Microsoft MVP -
Exchange 2007 SP3 Install on 2008R2 Fails with "The data passed to a system call is too small"
I'm installing Exchange 2007 SP3 onto Server 2008 R2. I have run this install in compatibility mode and in normal install mode with the same results. Error code 3221684346: The data area passed to a system call is too small. I am installing directly from
the SP3 files, this is not an upgrade. What do I have to do to get this to work?
[2/15/2011 7:24:18 AM] [2] Interpreting line <CreateSecureKey:MSExchangeIS\ParametersPrivate> -- ID:31259 --
[2/15/2011 7:24:18 AM] [2] CInsParser::ScProcessLine (f:\08.03.0083\sources\dev\admin\src\libs\exsetup\hiddenw1.cxx:1199)
Error code 0XC007007A (122): The data area passed to a system call is too small.
[2/15/2011 7:24:18 AM] [2] Processing file 'C:\Exchange Server\Setup\data\mdb_reg.ins', at or near line 77 (CreateSecureKey:MSExchangeIS\ParametersPrivate) -- ID:31111 -- CInsParser::ScProcessLine (f:\08.03.0083\sources\dev\admin\src\libs\exsetup\hiddenw1.cxx:488)
Error code 0XC007007A (122): The data area passed to a system call is too small.
[2/15/2011 7:24:18 AM] [2] Registry file name: 'C:\Exchange Server\Setup\data\mdb_reg.ins' CRegistryManager::ScProcessFile (f:\08.03.0083\sources\dev\admin\src\udog\setupbase\tools\regmgr.cxx:125)
Error code 0XC007007A (122): The data area passed to a system call is too small.
[2/15/2011 7:24:18 AM] [2] Filename = 'C:\Exchange Server\Setup\data\mdb_reg' CBaseAtom::ScRunRegistryFile (f:\08.03.0083\sources\dev\admin\src\udog\setupbase\basecomp\baseatom.cxx:1379)
Error code 0XC007007A (122): The data area passed to a system call is too small.
[2/15/2011 7:24:18 AM] [2] Leaving CBaseAtom(Information Store Service)::ScRunRegistryFile
[2/15/2011 7:24:18 AM] [2] Filename = 'C:\Exchange Server\Setup\data\mdb_reg' CBaseAtom::ScAddRegistryKeys (f:\08.03.0083\sources\dev\admin\src\udog\setupbase\basecomp\baseatom.cxx:1249)
Error code 0XC007007A (122): The data area passed to a system call is too small.
[2/15/2011 7:24:18 AM] [2] Leaving CBaseAtom(Information Store Service)::ScAddRegistryKeys
[2/15/2011 7:24:18 AM] [2] CAtomBaseMDB::ScAddRegistryKeys (f:\08.03.0083\sources\dev\admin\src\udog\exsetdata\components\server\a_basemdb.cxx:132)
Error code 0XC007007A (122): The data area passed to a system call is too small.
[2/15/2011 7:24:18 AM] [2] Leaving CAtomBaseMDB::ScAddRegistryKeys
[2/15/2011 7:24:18 AM] [2] CBaseAtom::ScAdd (f:\08.03.0083\sources\dev\admin\src\udog\setupbase\basecomp\baseatom.cxx:639)
Error code 0XC007007A (122): The data area passed to a system call is too small.
[2/15/2011 7:24:18 AM] [2] Leaving CBaseAtom(Information Store Service)::ScAdd
[2/15/2011 7:24:18 AM] [2] Service = 'MSExchangeIS' CBaseServiceAtom::ScAdd (f:\08.03.0083\sources\dev\admin\src\udog\setupbase\basecomp\basesvcatom.cxx:203)
Error code 0XC007007A (122): The data area passed to a system call is too small.
[2/15/2011 7:24:18 AM] [2] Leaving CBaseServiceAtom(Information Store Service)::ScAdd
[2/15/2011 7:24:18 AM] [2] mode = 'Install' (61953) CBaseAtom::ScSetup (f:\08.03.0083\sources\dev\admin\src\udog\setupbase\basecomp\baseatom.cxx:535)
Error code 0XC007007A (122): The data area passed to a system call is too small.
[2/15/2011 7:24:18 AM] [2] ScSetupAtom (f:\08.03.0083\sources\dev\admin\src\udog\exsetdata\exsetds.cxx:897)
Error code 0XC007007A (122): The data area passed to a system call is too small.
[2/15/2011 7:24:18 AM] [2] Leaving ScSetupAtom
[2/15/2011 7:24:18 AM] [2] [ERROR] An error occurred. The error code was 3221684346. The message was The data area passed to a system call is too small..
[2/15/2011 7:24:18 AM] [1] The following 1 error(s) occurred during task execution:
[2/15/2011 7:24:18 AM] [1] 0. ErrorRecord: An error occurred. The error code was 3221684346. The message was The data area passed to a system call is too small..
[2/15/2011 7:24:18 AM] [1] 0. ErrorRecord: Microsoft.Exchange.Management.Deployment.ExsetdataException: An error occurred. The error code was 3221684346. The message was The data area passed to a system call is too small..
[2/15/2011 7:24:18 AM] [1] [ERROR] An error occurred. The error code was 3221684346. The message was The data area passed to a system call is too small..
[2/15/2011 7:24:18 AM] [1] Setup is halting task execution because of one or more errors in a critical task.
[2/15/2011 7:24:18 AM] [1] Finished executing component tasks.
[2/15/2011 7:24:18 AM] [1] Ending processing.
[2/15/2011 7:42:08 AM] [0] End of Setup
[2/15/2011 7:42:08 AM] [0] **********************************************I would probably rebuild the host machine. The Exchange installation should occur without any issues, and where a problem does occur that can be an indication of a more widespread problem. Rebuild the machine, reinstall the prerequisites and try again.
Simon.
Simon Butler, Exchange MVP
Blog |
Exchange Resources | In the UK?
Hire Me.
Hello Poster.
I am having the same issue, however it is most likely NOT a host box problem. The above advice is not a fix. I have 3 servers that are cloned with the same setup. 2 were fixed by doing the Vista compatibility trick, this one gave a different error (which
happened to be the same as above). This org was a 5.5 to 2000. to 2003 coexistence with 2007 currently(because the mailbox role won't install). It has something to do with AD or permissions. Server 2008 r2 inherently has problems installing exchange.
Example, having to use vista compatibility to get the mailbox role to install. SP2 patch gives the same error to some people, and also doesn't upgrade the mailbox role properly in some cases. Some people have had luck restarting the IIS admin service, but
that did not solve my copy of this error. I will repost here if I find a solution to this issue...
Same exact setup log for me as well.
[3/4/2011 10:45:51 AM] [2] Interpreting line <OpenMachineKey:SYSTEM\CurrentControlSet\Services> -- ID:31259 --
[3/4/2011 10:45:51 AM] [2] Interpreting line <CreateSecureKey:MSExchangeIS\ParametersPrivate> -- ID:31259 --
[3/4/2011 10:45:51 AM] [2] CInsParser::ScProcessLine (f:\08.03.0083\sources\dev\admin\src\libs\exsetup\hiddenw1.cxx:1199)
Error code 0XC007007A (122): The data area passed to a system call is too small.
[3/4/2011 10:45:51 AM] [2] Processing file 'C:\Program Files\Microsoft\Exchange Server\Setup\data\mdb_reg.ins', at or near line 77 (CreateSecureKey:MSExchangeIS\ParametersPrivate) -- ID:31111 -- CInsParser::ScProcessLine (f:\08.03.0083\sources\dev\admin\src\libs\exsetup\hiddenw1.cxx:488)
Error code 0XC007007A (122): The data area passed to a system call is too small.
[3/4/2011 10:45:51 AM] [2] Registry file name: 'C:\Program Files\Microsoft\Exchange Server\Setup\data\mdb_reg.ins' CRegistryManager::ScProcessFile (f:\08.03.0083\sources\dev\admin\src\udog\setupbase\tools\regmgr.cxx:125)
Error code 0XC007007A (122): The data area passed to a system call is too small.
[3/4/2011 10:45:51 AM] [2] Filename = 'C:\Program Files\Microsoft\Exchange Server\Setup\data\mdb_reg' CBaseAtom::ScRunRegistryFile (f:\08.03.0083\sources\dev\admin\src\udog\setupbase\basecomp\baseatom.cxx:1379)
Error code 0XC007007A (122): The data area passed to a system call is too small.
[3/4/2011 10:45:51 AM] [2] Leaving CBaseAtom(Information Store Service)::ScRunRegistryFile
[3/4/2011 10:45:51 AM] [2] Filename = 'C:\Program Files\Microsoft\Exchange Server\Setup\data\mdb_reg' CBaseAtom::ScAddRegistryKeys (f:\08.03.0083\sources\dev\admin\src\udog\setupbase\basecomp\baseatom.cxx:1249)
Error code 0XC007007A (122): The data area passed to a system call is too small.
[3/4/2011 10:45:51 AM] [2] Leaving CBaseAtom(Information Store Service)::ScAddRegistryKeys
[3/4/2011 10:45:51 AM] [2] CAtomBaseMDB::ScAddRegistryKeys (f:\08.03.0083\sources\dev\admin\src\udog\exsetdata\components\server\a_basemdb.cxx:132)
Error code 0XC007007A (122): The data area passed to a system call is too small.
[3/4/2011 10:45:51 AM] [2] Leaving CAtomBaseMDB::ScAddRegistryKeys
[3/4/2011 10:45:51 AM] [2] CBaseAtom::ScAdd (f:\08.03.0083\sources\dev\admin\src\udog\setupbase\basecomp\baseatom.cxx:639)
Error code 0XC007007A (122): The data area passed to a system call is too small.
[3/4/2011 10:45:51 AM] [2] Leaving CBaseAtom(Information Store Service)::ScAdd
[3/4/2011 10:45:51 AM] [2] Service = 'MSExchangeIS' CBaseServiceAtom::ScAdd (f:\08.03.0083\sources\dev\admin\src\udog\setupbase\basecomp\basesvcatom.cxx:203)
Error code 0XC007007A (122): The data area passed to a system call is too small.
[3/4/2011 10:45:51 AM] [2] Leaving CBaseServiceAtom(Information Store Service)::ScAdd
[3/4/2011 10:45:51 AM] [2] mode = 'Install' (61953) CBaseAtom::ScSetup (f:\08.03.0083\sources\dev\admin\src\udog\setupbase\basecomp\baseatom.cxx:535)
Error code 0XC007007A (122): The data area passed to a system call is too small.
[3/4/2011 10:45:51 AM] [2] ScSetupAtom (f:\08.03.0083\sources\dev\admin\src\udog\exsetdata\exsetds.cxx:897)
Error code 0XC007007A (122): The data area passed to a system call is too small.
[3/4/2011 10:45:51 AM] [2] Leaving ScSetupAtom
[3/4/2011 10:45:51 AM] [2] [ERROR] An error occurred. The error code was 3221684346. The message was The data area passed to a system call is too small..
[3/4/2011 10:45:51 AM] [1] The following 1 error(s) occurred during task execution:
[3/4/2011 10:45:51 AM] [1] 0. ErrorRecord: An error occurred. The error code was 3221684346. The message was The data area passed to a system call is too small..
[3/4/2011 10:45:51 AM] [1] 0. ErrorRecord: Microsoft.Exchange.Management.Deployment.ExsetdataException: An error occurred. The error code was 3221684346. The message was The data area passed to a system call is too small..
[3/4/2011 10:45:51 AM] [1] [ERROR] An error occurred. The error code was 3221684346. The message was The data area passed to a system call is too small..
[3/4/2011 10:45:51 AM] [1] Setup is halting task execution because of one or more errors in a critical task.
[3/4/2011 10:45:51 AM] [1] Finished executing component tasks.
[3/4/2011 10:45:51 AM] [1] Ending processing.
Just curious though, how long is your FQDN? Mine is 34 characters plus whatever exchange is adding to it during setup for this particular string. I found a post with the same error for ISA server and some buffer is only 100 characters for a system call.
ERROR_INSUFFICIENT_BUFFER 122 (0x7A) The data area passed to a system call is too small. http://msdn.microsoft.com/en-us/library/ms681382(v=vs.85).aspx Indicates a msft programming problem.
Outsource Technology Inc. MSFT Professional Consultant -
Contacts created with Lotus notes are not seen in Exchange 2007 SP3 Rollup 7.
Contacts created with Lotus notes are not seen in Microsoft Exchange 2007 SP3 Rollup 7. the same is seen in Microsoft Exchange 2010 without issues.
when we create a new contact on Microsoft Exchange 2007, the contacts gets created but it is not seen unless we filter the EMC to list the contacts. Microsoft Exchange 2010 does not have any issues.
any help or inputs will be appreciated.
Thanks,
SidYou shouldn't be using the 2007 EMC or cmdlets to create new objects if you have a more recent release installed in your organization. Use the 2010 software.
If you create the mail-enabled contact with the 2010 EMC or cmdlets do you see it in the 2007 EMC?
When you say the contact "is not seen unless we filter the EMC to list the contacts", does that mean you don't see the contact when you're looking at the "Recipient configuration" container? Is there a default filter on that container? Do you have a limit
on the number of objects shown?
As for the objects created by 3rd-party software (Lotus), are they creating the contacts correctly?
--- Rich Matheisen MCSE&I, Exchange MVP -
Migration from Exchange 2007 SP3 to Exchange 2010
Hello,
We are planning a single server migration from Exchange 2007 SP3 to Exchange 2010. I'll be building the 2010 server on a 2008 R2 box. My question is, can I make the jump directly to Exchange 2010 SP3, or do I need to install exchange 2010 SP1 first
- migrate from 2007 SP3, and then install SP3 for exchange 2010 later?
Thanks,
Eric@ Hasan
Dimdik - TAT,
That's not correct at all, you can migrate exchange server 2007 SP3 and RollUp Update 10 minimum to Exchange Server 2013 with minimum CU1.
Cheers,
Gulab Prasad,
Technology Consultant
Blog:
www.exchangeranger.com
Twitter:
LinkedIn:
Check out CodeTwo’s tools for Exchange admins
Note: Posts are provided “AS IS” without warranty of any kind, either expressed or implied, including but not limited to the implied warranties of merchantability and/or fitness for a particular purpose. -
We are in the process of planning the deployment of Windows Server 2008 SP2, latest MS updates, and update rollup 13 for Exchange 2007 SP3. Looking to migrate to Exchange 2013 & Exchange online in the future
Are there any issues that we need to be aware of before proceeding with the big updates. Exchange is running fine, but we're not able to fully patch these servers unless SP2 is installed. Thanks a bunch.
Environment:
running Exchange 2007 SP3 with update rollup 5 for all of our email servers (CCR, HUB/CAS w/WNLB). The OS installed for all of these are Windows 2008 SP1 (6.0.6001
Service Pack 1 Build 6001), latest MS critical updates are the only recent updates installed.
We also have Forefront Security for Exchange that I might remove.Hello,
Do you mean you want to upgrade Windows Server 2008 SP1 to Windows Server 2008 SP2, and then upgrade Exchange 2007 SP3 with rollup 5 to rollup 13? If so, the OS not being upgraded to a new version.
If you want to deploy Exchange 2007 SP3 with rollup13, you must install Windows Server 2008 SP2 on a computer that does not have Exchange installed, and then install Exchange 2007 SP3 with rollup 13, and move your mailboxes to new Exchange Server.
Based on your environment, you need to upgrade a clustered mailbox server, you must build a new failover cluster using Windows Server 2008 SP2 as the operating system for all nodes, and then migrate the data from the old cluster to new cluster.
If you have any feedback on our support, please click
here
Cara Chen
TechNet Community Support -
Exchange 2007 SP3 failed and cannot comeback to upgrade Menu
Hi team,
I plan to migrate from Exchange 2007 to 2013. so I wan to upgrade exchange 2007 from SP1 to SP3
I have two exchange 2007 SP1 Server, Server 1 CAS+HT. Server 2 CAS+HT+MBX.
I already upgrade Server1 (CAS+HT). upgrade success without issue. but when I upgrade Server2 (CAS+MBX+HT)
I found error at HT upgrade step.
this is the error
Error:
This role cannot be installed because the following roles are not current: ClientAccessRole MailboxRole AdminToolsRole
after this error I change registry HKLM\Software\Microsoft\Exchange\v8.0\
and config same version between Unpacked Version and configured Version. I change from 8.1.240.6 to 8.3.83.6. so all unpacked and configure version become 8.3.83.6
. this is the link
http://blogs.technet.com/b/exchange/archive/2007/05/21/3402900.aspx
But, after I restart the Server, Exchange installation not continue to upgrade from SP1 to SP3.
the Menu seems to appear like new Exchange installation menu. like attached picture bellow
its weird, if I click next, the menu appear like exchange 2007 new installation.
can I back to Exchange 2007 upgrade menu GUI?.
I suggest to use setup.com /m:upgrade. but is this a suitable method?
please help team :)
Thanks
RegardsHi,
According to your description, I understand that cannot upgrade to Exchange 2007 SP3 with error “This role cannot be installed because the following roles are not current: ClientAccessRole MailboxRole AdminToolsRole”.
If I misunderstand your concern, please do not hesitate to let me know.
If the upgrade isn’t complete, the version of current Exchange server (SP1) is 8.1.240.6. The version of 8.3.83.6 is related to Exchange 2007 SP3.
Therefore, please change the setting back and try again.
Besides, I find a similar thread about this error message when upgrade to Exchange 2007 SP3, for your reference:
https://social.technet.microsoft.com/Forums/en-US/fba6fd70-a406-4d79-8a07-0385ac04c600/exchange-service-pack-2-install-fails
“In the end I solved my issue here by re-running the /prepareAD and /preparedomain. I then deleted the watermark keys in the regestry as described above and happy days.”
Best Regards,
Allen Wang -
Exchange 2007 on Windows 2008R2 with Windows 2012 DC
Hi All,
I am going to update DC from Windows 2003 Sp2 to Windows 2012 R2 (Add a new Windows 2012 DC at first and turn off Windows 2003 DC after). Just think about our Exchange server, which is Exchange 2007 SP3 (08.03.0297.001) on Windows 2008R2 SP1. Do I need
update Exchange to 2010 or I can keep it as is?
Thanks,What service pack, what rollup?
With SP3, RU13, you should be OK for the domain controller itself:
http://technet.microsoft.com/en-us/library/ff728623(v=exchg.150).aspx
However...
The domain / forest functional level cannot be at Windows 2012 R2.
Maybe that will be supported in a future rollup (?).
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. -
Restore Exchange 2007 SP3 to Windows 2008 R2 from Windows 2003
Perhaps I'm being dense, but I had Exchange 2007 SP3 installed on a Windows 2003 Server, and I've used "setup /mode:recoverserver" to restore it to a Windows 2008 R2 server... how do I restore the databases which I backed up with the Windows backup tool
on 2003?
I installed KB974674, the restore tool onto the 2008 R2 server but when I try and restore the backup it comes up with "this feature is no longer supported". Something I'm missing here?These things marked as answers are not answers.
I have now thoroughly tested using setup /mode:recoverserver and it works fine going from Windows 2003 to Windows 2008 R2 with Exchange 2007 SP3, done several installations now without a problem.
"Setup /m:RecoverServer cannot be used across operating systems. A server that was originally running Windows Server 2003 can be recovered only on Windows Server 2003, and a server that was originally running Windows Server 2008 can
be recovered only on Windows Server 2008."
This appears to be wrong, unless someone can tell me why it's right (I haven't tried moving Unified Messaging yet). I've done it to 2008 R2 several times now and also in the other direction, from 2008 R2 to 2003, I can't find anything that didn't work
afterward, although I haven't really thoroughly tested OWA yet, I admit (but it does appear to be working).
I think that documentation is out-of-date as it doesn't mention R2 plus I think it was written before SP3 came out and that paragraph is just wrong.
Basically how I do it is like this:
Dismount databases from the 2003 server and copy the storage group folders to a network location or removable media.
Install the Windows 2008 R2 server using the same machine account that was being used by the 2003 server. Install the prerequisites needed for Exchange 2007 SP3 installation on 2008 R2 (note in addition to the IIS components and RPC over HTTP this
also requires the AD tools in RSAT, which I haven't found mentioned in technical documentation). Install the relevant windows updates.
Install Exchange 2007 SP3 using setup /mode:recoverserver Install the update rollup.
Copy the storage groups into the relevant folders on the new server and mount them. Migrate any relevant certificates (e.g. for ActiveSync).
Obviously then check it all over with the diagnostic tools and check it with EXBPA. The backups are obviously totally different, but really I think you should be using DPM anyway.
To me that was pretty easy to do, to be honest. About 1.5 on a scale of one to ten. Basically install it, recover it, copy over some files and mount them.
Seriously on a halfway decent server I've done it in under an hour. -
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 -
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 ?
JoeHi 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. -
Q10 + Exchange 2007 SP3 - random calendar entries not synching
Hi,
We have an executive user with a BB Q10 with software v10.1.0.314.
The devices connects via WiFi or 3G to our Exchange 2007 SP3 server and mail/contacts/etc all appear to be flowing normally.
However, the user has reported that some calendar appointment/meeting entries are not showing on their handset. There doesn't appear to be a pattern as to which entries don't show.
I've confirmed that the entries are available on the Exchange 2007 server in the users calendar, however they will not sync to the handset.
If I create a new appointment or meeting request, they sync both ways, whether created on the handset or via Outlook/OWA on the Exchange server.
Any thoughts on why these random appointments/meetings aren't synching?
Are there any logs I could check for errors? The obvious Exchange/Windows ones don't seem to indicate any issues.Hi robert_petbam and welcome to the BlackBerry Support Community Forums!
Are the missing appointments more than 30 days old? The BlackBerry Q10 will only show the last 30 days worth of calendar appointments.
Thanks.
-CptS
Come follow your BlackBerry Technical Team on twitter! @BlackBerryHelp
Be sure to click Kudos! for those who have helped you.Click Solution? for posts that have solved your issue(s)! -
Exchange 2007 SP3 Search Problems
I reset all the search indices on my mailbox databases. Event viewer has told me the crawl is complete and everything checks out when I do “test-exchangeSearch”
from PS. However, the index folders are considerably smaller than the original ones, (1.3GB vs 7GB) and only about 1% of database size. Multiple users can prove to me that searches are incomplete and not returning reliable results when just doing basic folder
searches from Outlook 2007. help!
IanAfter speaking with a senior MS Engineer, if you already have SP3 applied and tried to reinstall the search as I outlined above, you have corrupt your Exchange install and the ONLY option is to rebuild the box. After reinstalling Windows and Exchange, the
proper procedure to get search working perfectly is outlined below:
4. If you haven’t already,
upgrade toExchange Server 2007 Service Pack 3.
Exchange 2007 SP3 includes several major Search-related fixes and upgrades MSSearch 3.0 to MSSearch 3.1. This is a highly significant
upgrade.
5. Update to the latest available Rollup Update.
There are some very significant search fixes in the Rollup Updates for Exchange 2007 SP3. Some of these fixes are absolutely essential to install.
For example, Exchange 2007 SP3 Rollup Update 2 includes a fix that allows Exchange server to index emails even when the attachment cannot
be parsed – this is the number one call generator for Exchange 2007 search support cases.
To restate, upgrade to the very latest available Exchange 2007 SP3 rollup update, as there are many more search fixes available in the latest
rollup updates.
6.
Install IFilters and register them – follow ALL the steps below.
Install Filter Pack 1.0, which allows Exchange 2007 to index Office 2007 documents:
2007 Office System Converter: Microsoft Filter Pack
http://www.microsoft.com/download/en/details.aspx?displaylang=en&id=20109
7. Install the hotfix which addresses a known issue when search crawls a .vsd file.
960502 Description of the 2007 Office system hotfix package (Offfiltx.msp, Visfilter.msp): December 16, 2008
http://support.microsoft.com/default.aspx?scid=kb;EN-US;960502
Additional Information on the hotfix:
960166 Error message when a search process crawls a .vsd file on a Windows 64-bit operating system that is running the 2007 Office Filter
Pack: "The filtering process has been terminated"
http://support.microsoft.com/default.aspx?scid=kb;EN-US;960166
8.
Register the Filter Pack 1.0 IFilters. This is a manual process with Exchange 2007 but we have created a script to automate the process.:
944516 How to register Filter Pack IFilters with Exchange Server 2007
http://support.microsoft.com/default.aspx?scid=kb;EN-US;944516
9. Install Filter Pack 2.0 which allows Exchange to index Office 2010 attachments as well as some additional file types.
Download details: Microsoft Office 2010 Filter Packs
http://www.microsoft.com/downloads/en/details.aspx?FamilyID=5CD4DCD7-D3E6-4970-875E-ABA93459FBEE&displaylang=en
10. Register IFilters 2.0 with Exchange 2007.
How to Register IFilters 2.0 with Exchange 2007 and Exchange 2010
http://technet.microsoft.com/en-us/library/ff354976(EXCHG.80).aspx
11. Disable signature verification for the Exchange 2007 search services by putting 127.0.0.1 crl.microsoft.com in the HOSTS file.
Certificate Revocation List
When the Microsoft .NET Framework 2.0 loads a managed assembly, the managed assembly calls the CryptoAPI function to verify the Authenticode signature
on the assembly files. The CryptoAPI function checks a Certificate Revocation List
(CRL) that is available at http://crl.microsoft.com
. This action requires an Internet connection.
The
Microsoft Search Indexer service (Microsoft.Exchange.Search.ExSearch.exe)
is a managed assembly that is loaded by Microsoft .NET Framework 2.0. After installing Exchange 2007 SP3, if the Exchange server or DNS cannot resolve
http://crl.microsoft.com for any reason
the outgoing HTTP requests may be dropped and an error message is not returned. This delay causes the CRL to time out and cached CRLs will expire. This affects the Microsoft Search Indexer service in such a way that any new email fails to be indexed.
Instructions to Modify HOSTS file on the Exchange 2007 Server
Add the following:
127.0.0.1 crl.microsoft.com – here are the instructions:
a. Go Start – Programs and choose Command Prompt and choose Run as Administrator.
b. Within the Command Prompt, change to this directory (the drive will be the one where you installed the OS):
C:\Windows\System32\drivers\etc\hosts
c. Add the following entry to the HOSTS file:
127.0.0.1 crl.microsoft.com
d. Save the HOSTS file.
13.
Rebuild Indexes
using ResetSearchIndexes.ps1
How to Rebuild the Full-Text Index Catalog
http://technet.microsoft.com/en-us/library/aa995966(EXCHG.80).aspx
a. Go Start – Programs and choose Exchange Management Shell and choose Run as Administrator.
b. Change to this directory (the drive will be the one where you installed Exchange 2007):
C:\Program Files\Microsoft\Exchange Server\Scripts
c. It is suggested that you rebuild indexes for one or a few databases at a time – use the following command to rebuild the indexes for 1
databases called dbname1 and dbname2:
.\ResetSearchIndex.ps1 –force dbname1 dbname2
d. It is suggested not to run the following command unless you have 1 Exchange 2007 server only in your environment because it will cause
all databases on all Exchange 2007 (and all Exchange 2010 servers, if there are any) to be reindexed at that same time:
.\ResetSearchIndex.ps1 –force all
14.
Monitor the Application Event Log for Event ID 110 for a particular database.
This will indicate the new index is complete for that database.
15. After receiving Event ID 110 for a database, check to see if the size of the CatalogData folder for that database is the expected
5% to 10% of the database size. If the size of the CatalogData folder is significantly smaller than that or if the size is a few kb or a few mb, go
to Step 17.
16. After you have received Event ID 110 and the size of the CatalogData folder is normal, test searching in Outlook online mode
and OWA to make sure search is working.
<strike>
</strike>
Ian -
Hello Guys,
exchange 2007 SP3
windows 2008 r2
we have one user who unable to login to owa with error -"The user name or password that you entered is not valid. Try entering it again."
we checked mailbox feature in EMC and owa is enable
checked adsiedit - looks good
we checked allow inheritance - checked
we reset the password and try to login to owa from exchange server , no luck
user can login to her computer and outlook without any issue
we also moved her mailbox to another server
user facing the same issue from office and VPN
any suggestion ?
Thanks
Sandip
sandipHello Lynn
thanks for the reply. but I already checked that and allow inheritance already checked .
when user unable to access webmail with error "The user name or password that you entered is not valid"
will it generate any event id on exchange server or domain controller ?
in our case we have mailbox and CAS on different servers
any suggestion .
Regards
Sandip
sandip
Maybe you are looking for
-
My daughters ipod touch has been disabled because of a wrong passcode. After 2 days of trying to get into Itunes, it will not help without a passcode and is not recognizing it as a device even though the computer is recognizing the USB. I know I ha
-
Windows Vista not working correctly with Leopard 10.5
I just updated my MacBook Pro 17" by installing Leopard 10.5xx (erased and installed), then used BootCamp to partition disk and install Windows Vista. In Windows, my volume control is on, but no sound. I just got the error, "This problem was caused b
-
Hi all, I am going to explain my issue: First of all, in my interface I have a mapping that converts Idocs to an outbound structure. Then, that structure is used to call a BPM that gets another information. If I launch 5 IDocs, in sxmb_moni transacti
-
I have Dreamweaver MX 2004 and I downloaded an update for the application. When I tried to update it, the updater said it couldn't find the application file in the folder that was selected... yet the file is there! Any ideas as to what is wrong?
-
808 pureview Update 113.010.1508
This update is causing my windows 8 pc to BSOD (blue screen of death) during the firmware installation after the phones first USB disconnect i get a BSOD stating a kernel failure and then the pc shuts down The first time it happened i had thought som