Unable to install Exchange 2007 SP3 Rollup 13

Grettings,
I have a Server 2008 SP2 (64bit) DC with Exchange Server 2007 SP3 installed.
I have followed all the pre-reqs per http://technet.microsoft.com/en-us/library/ee221147%28EXCHG.80%29.aspx?ppud=4
However, it keeps failing. I've run the install in debug mode (/lvx*) and have narrowed it down to the following, but I can't make sense of it.
All the proper services are running (WMI, various exchange services), all proper rights are give (domain admin, exchange admin, etc...) And proper user-rights are setup.
No GPO's are setup.
Need help. Here is a partial log:
MSI (s) (74:14) [12:42:39:535]: Doing action: InstallExecute
Action 12:42:39: InstallExecute.
Action start 12:42:39: InstallExecute.
MSI (s) (74:14) [12:42:39:550]: Running Script: C:\Windows\Installer\MSI16A2.tmp
MSI (s) (74:14) [12:42:39:550]: PROPERTY CHANGE: Adding UpdateStarted property. Its value is '1'.
MSI (s) (74:14) [12:42:39:550]: Machine policy value 'DisableRollback' is 0
MSI (s) (74:14) [12:42:39:550]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\Rollback\Scripts 3: 2
MSI (s) (74:14) [12:42:39:550]: Executing op: Header(Signature=1397708873,Version=405,Timestamp=1151821140,LangId=1033,Platform=589824,ScriptType=1,ScriptMajorVersion=21,ScriptMinorVersion=4,ScriptAttributes=1)
MSI (s) (74:14) [12:42:39:550]: Executing op: ProductInfo(ProductKey={24B2C164-DE66-44FE-B468-A46D9D5E6B31},ProductName=Microsoft Exchange Server,PackageName=exchangeserver.msi,Language=1033,Version=134414419,Assignment=1,ObsoleteArg=0,,,PackageCode={16D94F8A-4406-41EA-9146-7A80F4F42DC1},,,InstanceType=0,LUASetting=0,RemoteURTInstalls=0,ProductDeploymentFlags=3)
MSI (s) (74:14) [12:42:39:550]: Executing op: DialogInfo(Type=0,Argument=1033)
MSI (s) (74:14) [12:42:39:550]: Executing op: DialogInfo(Type=1,Argument=Update Rollup 13 for Exchange Server 2007 Service Pack 3 (KB2917522))
MSI (s) (74:14) [12:42:39:550]: Executing op: RollbackInfo(,RollbackAction=Rollback,RollbackDescription=Rolling back actions,RollbackTemplate=[1],CleanupAction=RollbackCleanup,CleanupDescription=Removing backup files,CleanupTemplate=File: [1])
MSI (s) (74:14) [12:42:39:550]: Executing op: SetBaseline(Baseline=0,ProductVersion=8.3.83)
MSI (s) (74:14) [12:42:39:566]: Executing op: SetBaseline(Baseline=1,)
MSI (s) (74:14) [12:42:39:566]: Executing op: ActionStart(Name=CA_CUSTOMER_PATCH_ROLLBACK,,)
Action 12:42:39: CA_CUSTOMER_PATCH_ROLLBACK.
MSI (s) (74:14) [12:42:39:566]: Executing op: CustomActionSchedule(Action=CA_CUSTOMER_PATCH_ROLLBACK,ActionType=1345,Source=BinaryData,Target=CAQuietExec,CustomActionData="D:\Program Files\Microsoft\Exchange Server\\bin\QuietExe.exe" "C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe"
" -command . 'D:\Program Files\Microsoft\Exchange Server\\scripts\customization\CustomPatchInstallerActions.ps1' PatchRollbackActions")
MSI (s) (74:14) [12:42:39:566]: Executing op: ActionStart(Name=CA_CUSTOMER_PREPATCH_INSTALL,,)
Action 12:42:39: CA_CUSTOMER_PREPATCH_INSTALL.
MSI (s) (74:14) [12:42:39:566]: Executing op: CustomActionSchedule(Action=CA_CUSTOMER_PREPATCH_INSTALL,ActionType=1089,Source=BinaryData,Target=CAQuietExec,CustomActionData="D:\Program Files\Microsoft\Exchange Server\\bin\QuietExe.exe" "C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe"
" -command . 'D:\Program Files\Microsoft\Exchange Server\\scripts\customization\CustomPatchInstallerActions.ps1' PrePatchInstallActions")
MSI (s) (74:14) [12:42:39:566]: Creating MSIHANDLE (17) of type 790536 for thread 5908
MSI (s) (74:F8) [12:42:39:566]: Invoking remote custom action. DLL: C:\Windows\Installer\MSI183A.tmp, Entrypoint: CAQuietExec
MSI (s) (74:EC) [12:42:39:566]: Generating random cookie.
MSI (s) (74:EC) [12:42:39:582]: Created Custom Action Server with PID 4576 (0x11E0).
MSI (s) (74:40) [12:42:39:660]: Running as a service.
MSI (s) (74:40) [12:42:39:675]: Hello, I'm your 32bit Impersonated custom action server.
MSI (s) (74!80) [12:42:40:832]: Creating MSIHANDLE (18) of type 790531 for thread 3712
CAQuietExec: Error 0x80070001: Command line returned an error.
MSI (s) (74!80) [12:42:40:832]: Closing MSIHANDLE (18) of type 790531 for thread 3712
MSI (s) (74!80) [12:42:40:832]: Creating MSIHANDLE (19) of type 790531 for thread 3712
CAQuietExec: Error 0x80070001: CAQuietExec Failed
MSI (s) (74!80) [12:42:40:832]: Closing MSIHANDLE (19) of type 790531 for thread 3712
MSI (s) (74:F8) [12:42:40:832]: Closing MSIHANDLE (17) of type 790536 for thread 5908
MSI (s) (74:14) [12:42:40:847]: Executing op: ActionStart(Name=CA_ROLLBACK_SAVEDATA_STOP_SERVICES,,)
Action 12:42:40: CA_ROLLBACK_SAVEDATA_STOP_SERVICES.
MSI (s) (74:14) [12:42:40:847]: Executing op: CustomActionSchedule(Action=CA_ROLLBACK_SAVEDATA_STOP_SERVICES,ActionType=1281,Source=BinaryData,Target=CAQuietExec,CustomActionData="D:\Program Files\Microsoft\Exchange Server\\bin\QuietExe.exe" "C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe"
" -command . 'D:\Program Files\Microsoft\Exchange Server\\bin\servicecontrol.ps1' AfterPatch")
MSI (s) (74:14) [12:42:40:847]: Executing op: ActionStart(Name=CA_SAVEDATA_STOP_SERVICES,Description=Stopping services,Template=Service: [1])
Action 12:42:40: CA_SAVEDATA_STOP_SERVICES. Stopping services
MSI (s) (74:14) [12:42:40:847]: Executing op: CustomActionSchedule(Action=CA_SAVEDATA_STOP_SERVICES,ActionType=1025,Source=BinaryData,Target=CAQuietExec,CustomActionData="D:\Program Files\Microsoft\Exchange Server\\bin\QuietExe.exe" "C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe"
" -command . 'D:\Program Files\Microsoft\Exchange Server\\bin\servicecontrol.ps1' BeforePatch")
MSI (s) (74:14) [12:42:40:847]: Creating MSIHANDLE (20) of type 790536 for thread 5908
MSI (s) (74:BC) [12:42:40:847]: Invoking remote custom action. DLL: C:\Windows\Installer\MSI1D3D.tmp, Entrypoint: CAQuietExec
MSI (s) (74!44) [12:50:03:781]: Creating MSIHANDLE (21) of type 790531 for thread 5444
CAQuietExec: Error 0x80070001: Command line returned an error.
MSI (s) (74!44) [12:50:03:797]: Closing MSIHANDLE (21) of type 790531 for thread 5444
MSI (s) (74!44) [12:50:03:797]: Creating MSIHANDLE (22) of type 790531 for thread 5444
CAQuietExec: Error 0x80070001: CAQuietExec Failed
MSI (s) (74!44) [12:50:03:797]: Closing MSIHANDLE (22) of type 790531 for thread 5444
MSI (s) (74:BC) [12:50:03:797]: Closing MSIHANDLE (20) of type 790536 for thread 5908
Action ended 12:50:03: InstallExecute. Return value 3.
/r
Joe Hanchey

Hi Joe,
Glad to know that you have solved this issue.
Thanks for your generous sharing.
Have a nice day : )
Thanks
Mavis
Mavis Huang
TechNet Community Support

Similar Messages

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,
Sid

You 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

Exchange 2007 SP3 Rollup 2 installed - OWA stopped working!

After running this update on our Exchange server, everything seemed fine. Then a few days later, someone said they can't access /owa. At first I wasn't able to recreate the problem in IE8 but on other browsers I was getting the 403 access denied
error. Then playing around with the HTTP redirects I was able to get the same error. Now i can't get OWA working at all. I have this article settings which worked before
http://technet.microsoft.com/en-us/library/aa998359(EXCHG.80).aspx . Now no go. Also, can't get to owa from IIS 7 directly anymore. My domain admin credentials don't take
so not sure if the virtual directory is missing somehow or what's causing this. Also, my iPhone still receiving email so not sure why owa isn't working.

Yeah, I did the kb/941201 but that didn't help either (the other link appears to be broken). Microsoft was kind enough to help me without charge. Here's the correct IIS 7 settings that got it working again for me.
Default Web Site - Authentication = Anonymous + Windows, SSL = unchecked + igonore, HTTP Redirect = Check Redirect (entery your
https://URL), Check "Only redirect" box and Status code Found 302.
owa - Authentication = Basic, SSL = Check Require SSL + 128-bit SSL + Ignore radio button, HTTP Redirect = Unchecked
I already had this in EMC but just in case - expand Server Configuration>Client Access>r-click owa under Outlook Web Access tab>Properties Authentication tab and check the USE forms-based authentication button Logon Format: Domain\user name.
And not sure how the service pack messed up those IIS settings. They say not to play with the IIS settings, but hope this helps someone.

Cannot connect to OWA after Exchange 2007 SP3 and Rollup 13 install.

Hi,
Our OWA website isn't accessible after we installed SP3 and rollup update 13 for Exchange 2007. When we attempt to visit the OWA URL, all we receive is HTTP 403.4 SSL is required to view this resource. Doug

Hi,
I recommend you follow the steps below for troubleshooting:
1. Open IIS Manager, click Default Web Site -> Authentication, make sure that Anonymous Authentication and Windows Authentication are enabled.
2. Click Default Web Site -> SSL Settings, check "Require SSL" and click Ignore.
3. Click Default Web Site -> HTTP Redirect, check Redirect (enter your
https://URL), check "Only redirect" box and Status code Found 302.
4. Expand Server Configuration -> Client Access ->double click owa ->Authentication tab. Check the Basic Authentication and check the Use forms-based authentication button Logon Format: Domain\user name.
What's more, here is a thread for your reference.
Exchange 2007 SP3 Rollup 2 installed - OWA stopped working
http://social.technet.microsoft.com/Forums/en-US/8481eb3d-a6ab-42fc-b7ea-fa9a9a625e48/exchange-2007-sp3-rollup-2-installed-owa-stopped-working?forum=exchangesvrdeploylegacy
Hope it helps.
Best regards,
Amy
Amy Wang
TechNet Community Support

Applying OS SP2 to existing Windows Srv 2008 SP1 w/ Exchange 2007 SP3 w/RU 5, before installing RU13

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 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

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 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!
Ian

After 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

Upgrade to Exchange 2007 SP3 from SP2

Need Advice for Upgrade Exchange Server 2007 SP2 to SP3. My Existing environment is 4 AD. All are run in windows server 2003 and 3 Exchange Server 2007 that are run OS 2003 64 bit one SP1 and another two is SP2. and My next plan is Migration Exchange 2007
to 2013 and AD 2003 to 2012 R2. Please explain me any body for this matter as per as soon.
Md. Ramin Hossain

Hi Md,
Thank you for your question.
In addition, when Exchange 2007 and Exchange 2013 are co-existed in organization, and we want to create an EdgeSync Subscription between an Exchange 2007 Hub Transport server and an Exchange 2013 SP1 Edge Transport server, you need to install Exchange 2007
SP3 Update Rollup 13 or later on the Exchange 2007 Hub Transport server.
Exchange 2013 is Exchange 2013 Cumulative Update 2 (CU2) or later on all Exchange 2013 servers in the organization.
We could refer to the following link:
https://technet.microsoft.com/en-us/library/jj898581(v=exchg.150).aspx
We could refer to the following steps to migrate Exchange 2007 to Exchange 2013:
http://blogs.technet.com/b/meamcs/archive/2013/07/25/part-1-step-by-step-exchange-2007-to-2013-migration.aspx
We could ask to our Window Forum for Window 2003 migration.
If there are any questions regarding this issue, please be free to let me know.
Best Regard,
Jim
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]
Jim Xu
TechNet Community Support

OWA Page breaks after Installing the Rollup 11 on Exchange 2007 SP3

I have applied the Update Rollup 11 on my Exchange 2007 SP3 and after updating the Rollup I am able to login to OWA but the it has broken the graphics and all the folders with X icon and cant get inside the folder/mail.
We use RSA token for the sign in
I had tried replacing the OWA folder from the backup and it did not helped.
Any suggestions will be really appreciated.
Regards,
Sudheesh Rajan

Hi,
If the problem happens after installing rollup, please uninstall it and then reinstall.
Most of these problem happen if certian dll files reatling to OWA are not registered or missing. To quickly resolve this problem, you can try to apply the latest SP or reinstall CAS server.
Thanks
Mavis
Mavis Huang
TechNet Community Support

Exchange 2007 SP3 latest update rollup

I would like to install the latest update rollup for Exchange 2007 SP3. I was reading and found Update Rollup 12, is this the latest version? No other update rollups are installed.
I did the SP3 update by installing on the hub transport first, then the 2 mailbox stores.

Hi,
Update Rollup 13 for Exchange 2007 SP3 has been released on 25th February 2014.
Rollup 13 for Microsoft Exchange 2007 SP3 can be downloaded here:
Update Rollup 13 for Exchange Server 2007 Service Pack 3 (KB2917522)
Informations about changes you can find here:
Description of Update Rollup 13 for Exchange Server 2007 Service Pack 3
One thing we need to take into consideration is the order to apply update on our Exchange servers, it should be the following:
1. CAS (if you have multiple sites, internet facing sites first)
2. Hub
3. MBX
Hope this helps.
Best regards,
Belinda
Belinda Ma
TechNet Community Support

OWA Blank Logon Page After Update Rollup 12 for Exchange 2007 SP3

Hello
After installing Update Rollup 12 for Exchange 2007 SP3, can no longer access OWA - internally or externally through Internet Explorer - I just get a blank page (with IE). If I use Chrome or Firefox, and it uses the basic logon, I get a page with just
text, and am able to logon successfully. I have looked at several related forums, but have not found a fix yet. I've seen several people with similar issue have had success by copying contents from a previous owa folder version to the latest one, then running
Updateowa.ps1 and restarting IIS. This did not resolve the issue for me.
Another forum suggested running remove-owavirtualdirectory and
new-owavirtualdirectory, however I haven't attempted that yet, as I'm unsure how I could reverse the changes that the command runs if things get worse.
Any assistance will be appreciated.

Hi,
I encountered a same situation,after recreating
the virtual directory, the issue was solved.
The following article for you reference:
How To: Recreate OWA Virtual Directory – Exchange 2007
Hope this helps!
Thanks.
Niko Cheng
TechNet Community Support

One user unable to login to OWA - error :" The user name or password that you entered is not valid. Try entering it again." exchange 2007 SP3

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
sandip

Hello 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

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.

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

Unable to install Exchange 2007 SP3 Rollup 13

Similar Messages

Maybe you are looking for