Home
%3CLINGO-SUB%20id%3D%22lingo-sub-584521%22%20slang%3D%22en-US%22%3EINFO%3A%20Update%20Rollup%204%20for%20Exchange%20Server%202007%20Service%20Pack%201%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-584521%22%20slang%3D%22en-US%22%3E%3CP%3E%3C%2FP%3E%3CP%3E%3CFONT%20size%3D%222%22%3EFor%20a%20brief%20period%20of%20time%20on%20August%209%2C%202008%2C%20a%20pre-release%20version%20of%20%3CSTRONG%3EUpdate%20Rollup%204%20for%20Exchange%20Server%202007%20Service%20Pack%201%20(KB952580)%3C%2FSTRONG%3E%20was%20inadvertently%20made%20available%20to%20%3CSTRONG%3EMicrosoft%20Update%3C%2FSTRONG%3E%2C%20the%20%3CSTRONG%3EMicrosoft%20Update%20Catalog%3C%2FSTRONG%3E%2C%20and%20%3CSTRONG%3EWindows%20Software%20Update%20Services%20(WSUS)%3C%2FSTRONG%3E%20servers%20for%20download.%20While%20we%20quickly%20removed%20the%20update%20from%20Microsoft%20Update%20within%20a%20short%20period%20of%20time%2C%20some%20servers%20using%20these%20distribution%20methods%20might%20have%20detected%2C%20downloaded%20and%2For%20installed%20this%20version%20of%20the%20update.%3C%2FFONT%3E%3C%2FP%3E%3CP%3E%3CFONT%20size%3D%222%22%3EKnown%20issues%20exist%20with%20this%20pre-release%20version%20of%20Update%20Rollup%204%2C%20including%20issues%20with%20Exchange%20Web%20Services%20(EWS)%20that%20creates%20the%20potential%20for%20a%20continuous%20crashing%20cycle%2C%20an%20uninstall%20issue%20where%20the%20EWS%20web.config%20is%20reset%2C%20and%20an%20issue%20with%20backup%20validation.%20The%20final%20release%20version%20of%20Update%20Rollup%204%20will%20be%20released%20in%20the%20upcoming%20weeks%2C%20and%20until%20then%2C%20we%20recommend%20that%20customers%20who%20have%20not%20already%20installed%20Update%20Rollup%204%20wait%20to%20do%20so.%20If%20you%20have%20already%20installed%20Update%20Rollup%204%2C%20%3CSTRONG%3E%3CU%3Ewe%20recommend%20uninstalling%20it%3C%2FU%3E%3C%2FSTRONG%3E.%3C%2FFONT%3E%3C%2FP%3E%3CP%3E%3CFONT%20size%3D%222%22%3EThe%20following%20known%20issues%20exist%20in%20the%20pre-release%20(version%20%3CSTRONG%3E8.1.311.1%3C%2FSTRONG%3E)%20of%20Update%20Rollup%204%20for%20Exchange%20server%202007%20Service%20Pack%201%20(KB952580).%20Also%20included%20are%20recommended%20steps%20to%20resolve%20this%20for%20customers%20who%20encounter%20any%20of%20the%20issues.%3CBR%20%2F%3E%3CBR%20%2F%3E%3C%2FFONT%3E%3C%2FP%3E%0A%3CTABLE%20cellspacing%3D%220%22%20cellpadding%3D%220%22%20width%3D%22695%22%20border%3D%221%22%3E%0A%3CTBODY%3E%0A%3CTR%3E%0A%3CTD%20align%3D%22middle%22%20width%3D%22199%22%3E%3CFONT%20size%3D%223%22%3E%3CSTRONG%3ESymptom%3C%2FSTRONG%3E%3C%2FFONT%3E%3C%2FTD%3E%0A%3CTD%20align%3D%22middle%22%20width%3D%22154%22%3E%3CFONT%20size%3D%223%22%3E%3CSTRONG%3EValidation%3C%2FSTRONG%3E%3C%2FFONT%3E%3C%2FTD%3E%0A%3CTD%20align%3D%22middle%22%20width%3D%22133%22%3E%3CFONT%20size%3D%223%22%3E%3CSTRONG%3EWorkaround%3C%2FSTRONG%3E%3C%2FFONT%3E%3C%2FTD%3E%0A%3CTD%20align%3D%22middle%22%20width%3D%22207%22%3E%3CFONT%20size%3D%223%22%3E%3CSTRONG%3EResolution%3C%2FSTRONG%3E%3C%2FFONT%3E%3C%2FTD%3E%3C%2FTR%3E%0A%3CTR%3E%0A%3CTD%20valign%3D%22top%22%20width%3D%22199%22%3E%3CP%3E%3CFONT%20size%3D%221%22%3EFailure%20observed%20in%20backup%20applications%20which%20result%20in%20the%20following%20events%20(or%20similar%20ones%20in%20the%20event%20log).%20The%20E00%20in%20event%20ID%20305%20is%20the%20current%20log%20file%20for%20the%20storage%20group%20where%20the%20backup%20is%20performed.%20So%20it%20can%20be%20E0n%20if%20the%20backup%20is%20being%20performed%20against%20a%20different%20storage%20group.%20%3C%2FFONT%3E%3C%2FP%3E%3CP%3E%3CFONT%20size%3D%221%22%3EEvent%20Type%3A%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%20Error%3CBR%20%2F%3EEvent%20Source%3A%26nbsp%3B%26nbsp%3B%26nbsp%3B%20Storage%20Group%20Consistency%20Check%3CBR%20%2F%3EEvent%20Category%3A%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%20Termination%3CBR%20%2F%3EEvent%20ID%3A%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%20401%3CBR%20%2F%3EDescription%3A%20Instance%201%3A%20The%20physical%20consistency%20check%20has%20completed%2C%20but%20one%20or%20more%20errors%20were%20detected.%20The%20consistency%20check%20has%20terminated%20with%20error%20code%20of%20-106%20(0xffffff96).%20%3C%2FFONT%3E%3C%2FP%3E%3CP%3E%3CFONT%20size%3D%221%22%3EEvent%20Type%3A%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%20Error%3CBR%20%2F%3EEvent%20Source%3A%26nbsp%3B%26nbsp%3B%26nbsp%3B%20Storage%20Group%20Consistency%20Check%3CBR%20%2F%3EEvent%20Category%3A%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%20Log%20File%20Validation%3CBR%20%2F%3EEvent%20ID%3A%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%20305%3CBR%20%2F%3EDescription%3A%20Instance%201%3A%20One%20or%20more%20errors%20were%20detected%20while%20validating%20the%20transaction%20log%20files%20in%20'd%3A%5Cdatabase%5C'%20with%20a%20base%20name%20of%20'E00'.%20Transaction%20log%20file%20validation%20failed%20with%20error%20code%20-1811%20(0xfffff8ed).%3C%2FFONT%3E%3C%2FP%3E%3C%2FTD%3E%0A%3CTD%20valign%3D%22top%22%20width%3D%22154%22%3E%3CFONT%20size%3D%221%22%3ECheck%20if%20the%20server%20has%20Update%20Rollup%204%20for%20Exchange%20server%202007%20Service%20Pack%201%20(KB952580)%20v1%20installed.%20(See%20instructions%20below.)%3C%2FFONT%3E%3C%2FTD%3E%0A%3CTD%20valign%3D%22top%22%20width%3D%22133%22%3E%3CFONT%20size%3D%221%22%3ENone%3C%2FFONT%3E%3C%2FTD%3E%0A%3CTD%20valign%3D%22top%22%20width%3D%22207%22%3E%3CP%3E%3CFONT%20size%3D%221%22%3E1)%20Uninstall%20the%20rollup%20from%20%22View%20Installed%20Updates%22%20in%20Windows%20Server%202008%20or%20%22Add%2FRemove%20programs%22%20in%20Windows%20Server%202003.%20%3C%2FFONT%3E%3C%2FP%3E%3CP%3E%3CFONT%20size%3D%221%22%3E2)%20If%20the%20server%20also%20has%20the%20CAS%20role%2C%20open%20the%20web.config%20file%20located%20at%20%3CEXCHANGE%20install%3D%22%22%20folder%3D%22%22%3E%5CClient%20Access%5Cexchweb%5Cews%20using%20an%20editor%20like%20Notepad.exe.%20%3C%2FEXCHANGE%3E%3C%2FFONT%3E%3C%2FP%3E%3CP%3E%3CFONT%20size%3D%221%22%3E3)%20Replace%20all%20instances%20of%20%3CB%3E%25ExchangeInstallDir%25%3C%2FB%3E%20with%20the%20actual%20path%20of%20the%20Exchange%20installation%20folder.%20E.g.%20If%20you%20have%20installed%20Exchange%20in%20D%3A%5CProgram%20Files%5CMicrosoft%5CExchange%20Server%20replace%20%3CB%3E%25ExchangeInstallDir%25%3C%2FB%3E%20with%20%3CB%3ED%3A%5CProgram%20Files%5CMicrosoft%5CExchange%20Server%5C%3C%2FB%3E.%20%3C%2FFONT%3E%3C%2FP%3E%3CP%3E%3CFONT%20size%3D%221%22%3EHere%20is%20a%20line%20in%20the%20web.config%20file.%20%3C%2FFONT%3E%3C%2FP%3E%3CP%3E%3CFONT%20size%3D%221%22%3EBefore%20%3C%2FFONT%3E%3C%2FP%3E%3CP%3E%3CFONT%20size%3D%221%22%3E%3CCODEBASE%20version%3D%22%26quot%3B0.0.0.0%26quot%3B%22%20href%3D%22%26quot%3B%26lt%3B%2FFONT%22%3E%3CA%3E%3CFONT%20size%3D%221%22%3Efile%3A%2F%2F%2F%3CB%3E%25ExchangeInstallDir%25%3C%2FB%3Ebin%5CMicrosoft.Exchange.Common.IL.dll%3C%2FFONT%3E%3C%2FA%3E%3CFONT%20size%3D%221%22%3E%22%2F%26gt%3B%3C%2FFONT%3E%3C%2FCODEBASE%3E%3C%2FFONT%3E%3C%2FP%3E%3CP%3E%3CFONT%20size%3D%221%22%3EAfter%20%3C%2FFONT%3E%3C%2FP%3E%3CP%3E%3CFONT%20size%3D%221%22%3E%3CCODEBASE%20version%3D%22%26quot%3B0.0.0.0%26quot%3B%22%20href%3D%22%26quot%3B%26lt%3B%2FFONT%22%3E%3CA%3E%3CFONT%20size%3D%221%22%3Efile%3A%2F%2F%2F%3CB%3ED%3A%5CProgram%20Files%5CMicrosoft%5CExchange%20Server%5C%3C%2FB%3Ebin%5CMicrosoft.Exchange.Common.IL.dll%3C%2FFONT%3E%3C%2FA%3E%3CFONT%20size%3D%221%22%3E%22%2F%26gt%3B%3C%2FFONT%3E%3C%2FCODEBASE%3E%3C%2FFONT%3E%3C%2FP%3E%3CP%3E%3CFONT%20size%3D%221%22%3ERestart%20W3SVC%20service%3C%2FFONT%3E%3C%2FP%3E%3C%2FTD%3E%3C%2FTR%3E%0A%3CTR%3E%0A%3CTD%20valign%3D%22top%22%20width%3D%22199%22%3E%3CP%3E%3CFONT%20size%3D%221%22%3EIntermittent%20crashes%20in%20w3wp%20process%20on%20the%20CAS%20servers%20when%20Exchange%20Web%20Services%20(EWS)%20GetItem%20operations%20are%20processed.%20The%20following%20event%20is%20also%20logged%20in%20the%20event%20log.%20%3C%2FFONT%3E%3C%2FP%3E%3CP%3E%3CFONT%20size%3D%221%22%3ELog%20Name%3A%20Application%3CBR%20%2F%3ESource%3A%20MSExchange%20Common%3CBR%20%2F%3EEvent%20ID%3A%204999%3CBR%20%2F%3ETask%20Category%3A%20General%3CBR%20%2F%3ELevel%3A%20Error%3CBR%20%2F%3EKeywords%3A%20Classic%3CBR%20%2F%3EDescription%3A%20Watson%20report%20about%20to%20be%20sent%20to%20dw20.exe%20for%20process%20id%3A%209364%2C%20with%20parameters%3A%20E12IIS%2C%20RTL-AMD64%2C%2008.01.0240.006%2C%20WS%2C%20M.E.Services%2C%20M.E.S.C.PerfCounterReader.GetCPUPercent%2C%20System.InvalidOperationException%2C%20d177%2C%2008.01.0311.001.%20ErrorReportingEnabled%3A%20True%20%3C%2FFONT%3E%3C%2FP%3E%3CP%3E%3CFONT%20size%3D%221%22%3EEvent%20Xml%3A%3CBR%20%2F%3E%3CEVENT%20xmlns%3D%22%26quot%3B%26lt%3B%2FFONT%22%3E%3CA%20href%3D%22http%3A%2F%2Fschemas.microsoft.com%2Fwin%2F2004%2F08%2Fevents%2Fevent%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%20target%3D%22_blank%22%3E%3CFONT%20size%3D%221%22%3Ehttp%3A%2F%2Fschemas.microsoft.com%2Fwin%2F2004%2F08%2Fevents%2Fevent%3C%2FFONT%3E%3C%2FA%3E%3CFONT%20size%3D%221%22%3E%22%26gt%3B%3CBR%20%2F%3E%3CSYSTEM%3E%3CBR%20%2F%3E%3CPROVIDER%20name%3D%22%26quot%3BMSExchange%22%20common%3D%22%22%3E%3C%2FPROVIDER%3E%26nbsp%3B%20%3CEVENTID%20qualifiers%3D%22%26quot%3B16388%26quot%3B%22%3E4999%3C%2FEVENTID%3E%3CBR%20%2F%3E%3CLEVEL%3E2%3C%2FLEVEL%3E%3CBR%20%2F%3E%3CTASK%3E1%3C%2FTASK%3E%3CBR%20%2F%3E%3CKEYWORDS%3E0x80000000000000%3C%2FKEYWORDS%3E%26nbsp%3B%20%3CTIMECREATED%20systemtime%3D%22%26quot%3B2008-09-11T00%3A49%3A11.000Z%26quot%3B%22%3E%3C%2FTIMECREATED%3E%20%3CEVENTRECORDID%3E1262%3C%2FEVENTRECORDID%3E%26nbsp%3B%20%3CCHANNEL%3EApplication%3C%2FCHANNEL%3E%26nbsp%3B%20%3CCOMPUTER%3Etest.contoso.com%3C%2FCOMPUTER%3E%26nbsp%3B%20%3CSECURITY%3E%3C%2FSECURITY%3E%3CBR%20%2F%3E%3C%2FSYSTEM%3E%3CBR%20%2F%3E%3CEVENTDATA%3E%3CBR%20%2F%3E%3CDATA%3E9364%3C%2FDATA%3E%3CBR%20%2F%3E%3CDATA%3EE12IIS%3C%2FDATA%3E%3CBR%20%2F%3E%3CDATA%3ERTL-AMD64%3C%2FDATA%3E%20%3CDATA%3E08.01.0240.006%3C%2FDATA%3E%26nbsp%3B%20%3CDATA%3EWS%3C%2FDATA%3E%26nbsp%3B%20%3CDATA%3EM.E.Services%3C%2FDATA%3E%26nbsp%3B%20%3CDATA%3EM.E.S.C.PerfCounterReader.GetCPUPercent%3C%2FDATA%3E%26nbsp%3B%20%3CDATA%3ESystem.InvalidOperationException%3C%2FDATA%3E%3CBR%20%2F%3E%3CDATA%3Ed177%3C%2FDATA%3E%26nbsp%3B%20%3CDATA%3E08.01.0311.001%3C%2FDATA%3E%26nbsp%3B%20%3CDATA%3ETrue%3C%2FDATA%3E%3CBR%20%2F%3E%3C%2FEVENTDATA%3E%3CBR%20%2F%3E%3C%2FFONT%3E%3C%2FEVENT%3E%3C%2FFONT%3E%3C%2FP%3E%3C%2FTD%3E%0A%3CTD%20valign%3D%22top%22%20width%3D%22154%22%3E%3CP%3E%3CFONT%20size%3D%221%22%3ECheck%20if%20the%20server%20has%20Update%20Rollup%204%20for%20Exchange%20server%202007%20Service%20Pack%201%20(KB952580)%20v1%20installed.%20(See%20instructions%20below.)%3C%2FFONT%3E%3C%2FP%3E%3C%2FTD%3E%0A%3CTD%20valign%3D%22top%22%20width%3D%22133%22%3E%3CP%3E%3CFONT%20size%3D%221%22%3E1)%20Restart%20the%20W3SVC%20service.%20%3C%2FFONT%3E%3C%2FP%3E%3CP%3E%3CFONT%20size%3D%221%22%3E2)%20Run%20your%20EWS%20application%20immediately%20to%20ensure%20that%20EWS%20is%20the%20first%20instance%20of%20w3wp%20process.%20%3C%2FFONT%3E%3C%2FP%3E%3CP%3E%3CFONT%20size%3D%221%22%3EUse%20Task%20Manager%20to%20double%20check%20that%20only%201%20w3wp%20process%20is%20present.%20If%20there%20are%20more%20than%201%20w3wp%20process%2C%20then%20redo%20the%20steps%20from%20the%20beginning.%20If%20there%20is%20only%201%20EWS%20is%20being%20serviced%20by%20the%20first%20w3wp%20process.%20As%20long%20this%20w3wp%20process%20does%20not%20crash%20the%20CAS%20server%20will%20not%20run%20into%20this%20issue.%20are%20more%26nbsp%3B%20(which%20may%20be%20launched%20from%20a%20connection%20like%20OWA%20or%20ActiveSync).%3C%2FFONT%3E%3C%2FP%3E%3C%2FTD%3E%0A%3CTD%20valign%3D%22top%22%20width%3D%22207%22%3E%3CP%3E%3CFONT%20size%3D%221%22%3E1)%20Uninstall%20the%20rollup%20from%20%22View%20Installed%20Updates%22%20in%20Windows%20Server%202008%20or%20%22Add%2FRemove%20programs%22%20in%20Windows%20Server%202003.%20%3C%2FFONT%3E%3C%2FP%3E%3CP%3E%3CFONT%20size%3D%221%22%3E2)%20Open%20the%20web.config%20file%20located%20at%20%3CEXCHANGE%20install%3D%22%22%20folder%3D%22%22%3E%5CClient%20Access%5Cexchweb%5Cews%20using%20an%20editor%20like%20Notepad.exe.%20%3C%2FEXCHANGE%3E%3C%2FFONT%3E%3C%2FP%3E%3CP%3E%3CFONT%20size%3D%221%22%3E3)%20Replace%20all%20instances%20of%20%3CB%3E%25ExchangeInstallDir%25%3C%2FB%3E%20with%20the%20actual%20path%20of%20the%20Exchange%20installation%20folder.%20E.g.%20If%20you%20have%20installed%20Exchange%20in%20D%3A%5CProgram%20Files%5CMicrosoft%5CExchange%20Server%20replace%20%3CB%3E%25ExchangeInstallDir%25%3C%2FB%3E%20with%20%3CB%3ED%3A%5CProgram%20Files%5CMicrosoft%5CExchange%20Server%5C%3C%2FB%3E.%20%3C%2FFONT%3E%3C%2FP%3E%3CP%3E%3CFONT%20size%3D%221%22%3EHere%20is%20a%20line%20in%20the%20web.config%20file.%20%3C%2FFONT%3E%3C%2FP%3E%3CP%3E%3CFONT%20size%3D%221%22%3EBefore%20%3C%2FFONT%3E%3C%2FP%3E%3CP%3E%3CFONT%20size%3D%221%22%3E%3CCODEBASE%20version%3D%22%26quot%3B0.0.0.0%26quot%3B%22%20href%3D%22%26quot%3B%26lt%3B%2FFONT%22%3E%3CA%3E%3CFONT%20size%3D%221%22%3Efile%3A%2F%2F%2F%3CB%3E%25ExchangeInstallDir%25%3C%2FB%3Ebin%5CMicrosoft.Exchange.Common.IL.dll%3C%2FFONT%3E%3C%2FA%3E%3CFONT%20size%3D%221%22%3E%22%2F%26gt%3B%3C%2FFONT%3E%3C%2FCODEBASE%3E%3C%2FFONT%3E%3C%2FP%3E%3CP%3E%3CFONT%20size%3D%221%22%3EAfter%20%3C%2FFONT%3E%3C%2FP%3E%3CP%3E%3CFONT%20size%3D%221%22%3E%3CCODEBASE%20version%3D%22%26quot%3B0.0.0.0%26quot%3B%22%20href%3D%22%26quot%3B%26lt%3B%2FFONT%22%3E%3CA%3E%3CFONT%20size%3D%221%22%3Efile%3A%2F%2F%2F%3CB%3ED%3A%5CProgram%20Files%5CMicrosoft%5CExchange%20Server%5C%3C%2FB%3Ebin%5CMicrosoft.Exchange.Common.IL.dll%3C%2FFONT%3E%3C%2FA%3E%3CFONT%20size%3D%221%22%3E%22%2F%26gt%3B%3C%2FFONT%3E%3C%2FCODEBASE%3E%3C%2FFONT%3E%3C%2FP%3E%3CP%3E%3CFONT%20size%3D%221%22%3E4)%20Restart%20W3SVC%20service%3C%2FFONT%3E%3C%2FP%3E%3C%2FTD%3E%3C%2FTR%3E%0A%3CTR%3E%0A%3CTD%20valign%3D%22top%22%20width%3D%22199%22%3E%3CP%3E%3CFONT%20size%3D%221%22%3EExchange%20Web%20Services%20(EWS)%20operations%20fail%20with%20the%20following%20response.%20%3C%2FFONT%3E%3C%2FP%3E%3CP%3E%3CFONT%20size%3D%221%22%3EHTTP%2F1.1%20302%20Found%3CBR%20%2F%3ECache-Control%3A%20private%3CBR%20%2F%3EContent-Length%3A%20175%3CBR%20%2F%3EContent-Type%3A%20text%2Fhtml%3B%20charset%3Dutf-8%3CBR%20%2F%3ELocation%3A%20%2Fews%2FGenericErrorPage.htm%3Faspxerrorpath%3D%2Fews%2FExchange.asmx%3CBR%20%2F%3EServer%3A%20Microsoft-IIS%2F7.0%3CBR%20%2F%3EX-AspNet-Version%3A%202.0.50727%3CBR%20%2F%3EX-Powered-By%3A%20ASP.NET%3CBR%20%2F%3EDate%3A%20Fri%2C%2012%20Sep%202008%2001%3A00%3A02%20GMT%3CBR%20%2F%3E%3CBR%20%2F%3E%3CBR%20%2F%3E%26nbsp%3B%26nbsp%3B%20%3CTITLE%3EObject%20moved%3C%2FTITLE%3E%3CBR%20%2F%3E%3CBR%20%2F%3E%3CBR%20%2F%3E%3C%2FFONT%3E%3C%2FP%3E%3CH2%20id%3D%22toc-hId-1760053241%22%3EObject%20moved%20to%20%3CA%20href%3D%22%26quot%3B%2Fews%2FGenericErrorPage.htm%3Faspxerrorpath%3D%2Fews%2FExchange.asmx%26quot%3B%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%22%3Ehere%3C%2FA%3E.%3C%2FH2%3E%3CBR%20%2F%3E%3CBR%20%2F%3E%3CP%3E%3C%2FP%3E%3C%2FTD%3E%0A%3CTD%20valign%3D%22top%22%20width%3D%22154%22%3E%3CP%3E%3CFONT%20size%3D%221%22%3E1)%20On%20the%20CAS%20server%2C%20open%20the%20web.config%20file%20located%20at%20%3CEXCHANGE%20install%3D%22%22%20folder%3D%22%22%3E%5CClient%20Access%5Cexchweb%5Cews%20using%20an%20editor%20like%20Notepad.exe.%20%3C%2FEXCHANGE%3E%3C%2FFONT%3E%3C%2FP%3E%3CP%3E%3CFONT%20size%3D%221%22%3E2)%20Look%20for%20the%20presence%20of%20the%20text%20%3CB%3E%25ExchangeInstallDir%25%3C%2FB%3E%20in%20the%20file.%20E.g.%20%3C%2FFONT%3E%3C%2FP%3E%3CP%3E%3CFONT%20size%3D%221%22%3E%3CCODEBASE%20version%3D%22%26quot%3B0.0.0.0%26quot%3B%22%20href%3D%22%26quot%3B%26lt%3B%2FFONT%22%3E%3CA%3E%3CFONT%20size%3D%221%22%3Efile%3A%2F%2F%2F%3CB%3E%25ExchangeInstallDir%25%3C%2FB%3Ebin%5CMicrosoft.Exchange.Common.IL.dll%3C%2FFONT%3E%3C%2FA%3E%3CFONT%20size%3D%221%22%3E%22%2F%26gt%3B%3C%2FFONT%3E%3C%2FCODEBASE%3E%3C%2FFONT%3E%3C%2FP%3E%3C%2FTD%3E%0A%3CTD%20valign%3D%22top%22%20width%3D%22133%22%3E%3CFONT%20size%3D%221%22%3ENone%3C%2FFONT%3E%3C%2FTD%3E%0A%3CTD%20valign%3D%22top%22%20width%3D%22207%22%3E%3CP%3E%3CFONT%20size%3D%221%22%3E1)%20Open%20the%20web.config%20file%20located%20at%20%3CEXCHANGE%20install%3D%22%22%20folder%3D%22%22%3E%5CClient%20Access%5Cexchweb%5Cews%20using%20an%20editor%20like%20Notepad.exe.%20%3C%2FEXCHANGE%3E%3C%2FFONT%3E%3C%2FP%3E%3CP%3E%3CFONT%20size%3D%221%22%3E2)%20Replace%20all%20instances%20of%20%3CB%3E%25ExchangeInstallDir%25%3C%2FB%3E%20with%20the%20actual%20path%20of%20the%20Exchange%20installation%20folder.%20E.g.%20If%20you%20have%20installed%20Exchange%20in%20D%3A%5CProgram%20Files%5CMicrosoft%5CExchange%20Server%20replace%20%3CB%3E%25ExchangeInstallDir%25%3C%2FB%3E%20with%20%3CB%3ED%3A%5CProgram%20Files%5CMicrosoft%5CExchange%20Server%5C%3C%2FB%3E.%20%3C%2FFONT%3E%3C%2FP%3E%3CP%3E%3CFONT%20size%3D%221%22%3EHere%20is%20a%20line%20in%20the%20web.config%20file.%20%3C%2FFONT%3E%3C%2FP%3E%3CP%3E%3CFONT%20size%3D%221%22%3EBefore%20%3C%2FFONT%3E%3C%2FP%3E%3CP%3E%3CFONT%20size%3D%221%22%3E%3CCODEBASE%20version%3D%22%26quot%3B0.0.0.0%26quot%3B%22%20href%3D%22%26quot%3B%26lt%3B%2FFONT%22%3E%3CA%3E%3CFONT%20size%3D%221%22%3Efile%3A%2F%2F%2F%3CB%3E%25ExchangeInstallDir%25%3C%2FB%3Ebin%5CMicrosoft.Exchange.Common.IL.dll%3C%2FFONT%3E%3C%2FA%3E%3CFONT%20size%3D%221%22%3E%22%2F%26gt%3B%3C%2FFONT%3E%3C%2FCODEBASE%3E%3C%2FFONT%3E%3C%2FP%3E%3CP%3E%3CFONT%20size%3D%221%22%3EAfter%20%3C%2FFONT%3E%3C%2FP%3E%3CP%3E%3CFONT%20size%3D%221%22%3E%3CCODEBASE%20version%3D%22%26quot%3B0.0.0.0%26quot%3B%22%20href%3D%22%26quot%3B%26lt%3B%2FFONT%22%3E%3CA%3E%3CFONT%20size%3D%221%22%3Efile%3A%2F%2F%2F%3CB%3ED%3A%5CProgram%20Files%5CMicrosoft%5CExchange%20Server%5C%3C%2FB%3Ebin%5CMicrosoft.Exchange.Common.IL.dll%3C%2FFONT%3E%3C%2FA%3E%3CFONT%20size%3D%221%22%3E%22%2F%26gt%3B%3C%2FFONT%3E%3C%2FCODEBASE%3E%3C%2FFONT%3E%3C%2FP%3E%3CP%3E%3CFONT%20size%3D%221%22%3E3)%20Restart%20W3SVC%20service%3C%2FFONT%3E%3C%2FP%3E%3C%2FTD%3E%3C%2FTR%3E%0A%3CTR%3E%0A%3CTD%20valign%3D%22top%22%20width%3D%22199%22%3E%3CP%3E%3CFONT%20size%3D%221%22%3EDuring%20uninstall%20of%20Rollup%204%2C%20the%20admin%20is%20prompted%20for%20a%20request%20for%20Source.%3C%2FFONT%3E%3C%2FP%3E%3C%2FTD%3E%0A%3CTD%20valign%3D%22top%22%20width%3D%22154%22%3E%3CFONT%20size%3D%221%22%3ERollup%204%20is%20being%20uninstalled%20via%20'Add%2FRemove%20Programs'%20and%20there%20is%20a%20UI%20requesting%20the%20original%20source%20media.%3C%2FFONT%3E%3C%2FTD%3E%0A%3CTD%20valign%3D%22top%22%20width%3D%22133%22%3E%3CFONT%20size%3D%221%22%3EStill%20being%20looked%20at.%20Looks%20to%20be%20an%20MSI%20Installer%20bug%20that%20has%20been%20fixed%20in%20a%20future%20version%20of%20MSI%20that%20we%20hit%20when%20changing%20resetsearchindex.ps1.%3C%2FFONT%3E%3C%2FTD%3E%0A%3CTD%20valign%3D%22top%22%20width%3D%22207%22%3E%3CFONT%20size%3D%221%22%3EWhen%20prompted%20for%20the%20source%2C%20point%20to%20the%20original%20ExchangeServer.MSI%20that%20came%20with%20media%20that%20you%20installed%20with.%20This%20will%20allow%20you%20to%20continue%20with%20the%20uninstall.%3C%2FFONT%3E%3C%2FTD%3E%3C%2FTR%3E%3C%2FTBODY%3E%3C%2FTABLE%3E%0A%3CP%3E%3CB%3E%3CFONT%20color%3D%22%230000ff%22%20size%3D%222%22%3EIdentification%20of%20Rollup%20version%20via%20Add%2FRemove%20Programs%3A%3C%2FFONT%3E%3C%2FB%3E%3C%2FP%3E%0A%3CP%3E%3CFONT%20size%3D%222%22%3ETo%20identify%20the%20version%20of%20the%20Rollup%20that%20you%20have%20installed%2C%20press%20the%20%22%3CSTRONG%3EClick%20here%20for%20support%20information%3C%2FSTRONG%3E%22%20link%20for%20the%20update%2C%20under%20Add%20or%20Remove%20Programs%20(or%20Programs%20and%20Features)%20applet%20in%20Control%20Panel%3A%3C%2FFONT%3E%3C%2FP%3E%0A%3CP%3E%3CFONT%20size%3D%222%22%3E%3CIMG%20src%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Flegacyfs%2Fonline%2Fmedia%2Fthemes%2Fexchange%2Fimages%2F449786_E2007SP1RU4v1.jpg%22%20original-url%3D%22%2Fthemes%2Fexchange%2Fimages%2F449786_E2007SP1RU4v1.jpg%22%20%2F%3E%20%3C%2FFONT%3E%3C%2FP%3E%0A%3CP%3E%3CB%3E%3CFONT%20color%3D%22%230000ff%22%20size%3D%222%22%3EIdentification%20of%20the%20rollup%20version%20via%20the%20Registry%3A%3C%2FFONT%3E%3C%2FB%3E%3C%2FP%3E%0A%3CP%3E%3CFONT%20size%3D%222%22%3ETo%20identify%20if%20the%20rollup%20is%20installed%20via%20the%20registry%2C%20the%20%22DisplayVersion%22%20value%20shown%20below%20will%20be%201.%20The%20final%20release%20version%20of%20the%20rollup%20will%20have%20a%20value%20data%20of%202%20or%20higher.%3C%2FFONT%3E%3C%2FP%3E%0A%3CP%3E%3CFONT%20face%3D%22Courier%20New%22%20size%3D%222%22%3EHKEY_LOCAL_MACHINE%5CSOFTWARE%5CMicrosoft%5CWindows%5CCurrentVersion%5CUninstall%5CKB952580%26nbsp%3B%3CBR%20%2F%3E%3C%2FFONT%3E%3CFONT%20face%3D%22Courier%20New%22%20size%3D%222%22%3E%26nbsp%3B%20Name%3A%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%20DisplayVersion%20%3CBR%20%2F%3E%3C%2FFONT%3E%3CFONT%20face%3D%22Courier%20New%22%20size%3D%222%22%3E%26nbsp%3B%20Type%3A%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%20REG_SZ%20%3CBR%20%2F%3E%3C%2FFONT%3E%3CFONT%20face%3D%22Courier%20New%22%20size%3D%222%22%3E%26nbsp%3B%20Data%3A%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%201%3C%2FFONT%3E%3C%2FP%3E%0A%3CP%3E%3CFONT%20size%3D%222%22%3EWe%20apologize%20for%20any%20inconvenience%20this%20may%20have%20caused%20and%20we%20are%20working%20to%20make%20sure%20this%20does%20not%20happen%20again.%3C%2FFONT%3E%3C%2FP%3E%0A%3CP%3E%3CFONT%20size%3D%222%22%3E-%20%3C%2FFONT%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Farchive%2F2006%2F04%2F03%2F424115.aspx%22%20target%3D%22_blank%22%3E%3CFONT%20size%3D%222%22%3EScott%20Roberts%3C%2FFONT%3E%3C%2FA%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E

For a brief period of time on August 9, 2008, a pre-release version of Update Rollup 4 for Exchange Server 2007 Service Pack 1 (KB952580) was inadvertently made available to Microsoft Update, the Microsoft Update Catalog, and Windows Software Update Services (WSUS) servers for download. While we quickly removed the update from Microsoft Update within a short period of time, some servers using these distribution methods might have detected, downloaded and/or installed this version of the update.

Known issues exist with this pre-release version of Update Rollup 4, including issues with Exchange Web Services (EWS) that creates the potential for a continuous crashing cycle, an uninstall issue where the EWS web.config is reset, and an issue with backup validation. The final release version of Update Rollup 4 will be released in the upcoming weeks, and until then, we recommend that customers who have not already installed Update Rollup 4 wait to do so. If you have already installed Update Rollup 4, we recommend uninstalling it.

The following known issues exist in the pre-release (version 8.1.311.1) of Update Rollup 4 for Exchange server 2007 Service Pack 1 (KB952580). Also included are recommended steps to resolve this for customers who encounter any of the issues.

Symptom Validation Workaround Resolution

Failure observed in backup applications which result in the following events (or similar ones in the event log). The E00 in event ID 305 is the current log file for the storage group where the backup is performed. So it can be E0n if the backup is being performed against a different storage group.

Event Type:        Error
Event Source:    Storage Group Consistency Check
Event Category:                Termination
Event ID:              401
Description: Instance 1: The physical consistency check has completed, but one or more errors were detected. The consistency check has terminated with error code of -106 (0xffffff96).

Event Type:        Error
Event Source:    Storage Group Consistency Check
Event Category:                Log File Validation
Event ID:              305
Description: Instance 1: One or more errors were detected while validating the transaction log files in 'd:\database\' with a base name of 'E00'. Transaction log file validation failed with error code -1811 (0xfffff8ed).

Check if the server has Update Rollup 4 for Exchange server 2007 Service Pack 1 (KB952580) v1 installed. (See instructions below.) None

1) Uninstall the rollup from "View Installed Updates" in Windows Server 2008 or "Add/Remove programs" in Windows Server 2003.

2) If the server also has the CAS role, open the web.config file located at <Exchange Install folder>\Client Access\exchweb\ews using an editor like Notepad.exe.

3) Replace all instances of %ExchangeInstallDir% with the actual path of the Exchange installation folder. E.g. If you have installed Exchange in D:\Program Files\Microsoft\Exchange Server replace %ExchangeInstallDir% with D:\Program Files\Microsoft\Exchange Server\.

Here is a line in the web.config file.

Before

<codeBase version="0.0.0.0" href="file:///%ExchangeInstallDir%bin\Microsoft.Exchange.Common.IL.dll"/>

After

<codeBase version="0.0.0.0" href="file:///D:\Program Files\Microsoft\Exchange Server\bin\Microsoft.Exchange.Common.IL.dll"/>

Restart W3SVC service

Intermittent crashes in w3wp process on the CAS servers when Exchange Web Services (EWS) GetItem operations are processed. The following event is also logged in the event log.

Log Name: Application
Source: MSExchange Common
Event ID: 4999
Task Category: General
Level: Error
Keywords: Classic
Description: Watson report about to be sent to dw20.exe for process id: 9364, with parameters: E12IIS, RTL-AMD64, 08.01.0240.006, WS, M.E.Services, M.E.S.C.PerfCounterReader.GetCPUPercent, System.InvalidOperationException, d177, 08.01.0311.001. ErrorReportingEnabled: True

Event Xml:
<Event xmlns="
http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="MSExchange Common" />  <EventID Qualifiers="16388">4999</EventID>
<Level>2</Level>
<Task>1</Task>
<Keywords>0x80000000000000</Keywords>  <TimeCreated SystemTime="2008-09-11T00:49:11.000Z" /> <EventRecordID>1262</EventRecordID>  <Channel>Application</Channel>  <Computer>test.contoso.com</Computer>  <Security />
</System>
<EventData>
<Data>9364</Data>
<Data>E12IIS</Data>
<Data>RTL-AMD64</Data> <Data>08.01.0240.006</Data>  <Data>WS</Data>  <Data>M.E.Services</Data>  <Data>M.E.S.C.PerfCounterReader.GetCPUPercent</Data>  <Data>System.InvalidOperationException</Data>
<Data>d177</Data>  <Data>08.01.0311.001</Data>  <Data>True</Data>
</EventData>
</Event>

Check if the server has Update Rollup 4 for Exchange server 2007 Service Pack 1 (KB952580) v1 installed. (See instructions below.)

1) Restart the W3SVC service.

2) Run your EWS application immediately to ensure that EWS is the first instance of w3wp process.

Use Task Manager to double check that only 1 w3wp process is present. If there are more than 1 w3wp process, then redo the steps from the beginning. If there is only 1 EWS is being serviced by the first w3wp process. As long this w3wp process does not crash the CAS server will not run into this issue. are more  (which may be launched from a connection like OWA or ActiveSync).

1) Uninstall the rollup from "View Installed Updates" in Windows Server 2008 or "Add/Remove programs" in Windows Server 2003.

2) Open the web.config file located at <Exchange Install folder>\Client Access\exchweb\ews using an editor like Notepad.exe.

3) Replace all instances of %ExchangeInstallDir% with the actual path of the Exchange installation folder. E.g. If you have installed Exchange in D:\Program Files\Microsoft\Exchange Server replace %ExchangeInstallDir% with D:\Program Files\Microsoft\Exchange Server\.

Here is a line in the web.config file.

Before

<codeBase version="0.0.0.0" href="file:///%ExchangeInstallDir%bin\Microsoft.Exchange.Common.IL.dll"/>

After

<codeBase version="0.0.0.0" href="file:///D:\Program Files\Microsoft\Exchange Server\bin\Microsoft.Exchange.Common.IL.dll"/>

4) Restart W3SVC service

Exchange Web Services (EWS) operations fail with the following response.

HTTP/1.1 302 Found
Cache-Control: private
Content-Length: 175
Content-Type: text/html; charset=utf-8
Location: /ews/GenericErrorPage.htm?aspxerrorpath=/ews/Exchange.asmx
Server: Microsoft-IIS/7.0
X-AspNet-Version: 2.0.50727
X-Powered-By: ASP.NET
Date: Fri, 12 Sep 2008 01:00:02 GMT
<html>
<head>
   <title>Object moved</title>
</head>
<body>
<h2>Object moved to <a href="/ews/GenericErrorPage.htm?aspxerrorpath=/ews/Exchange.asmx">here</a>.</h2>
</body>
</html>

1) On the CAS server, open the web.config file located at <Exchange Install folder>\Client Access\exchweb\ews using an editor like Notepad.exe.

2) Look for the presence of the text %ExchangeInstallDir% in the file. E.g.

<codeBase version="0.0.0.0" href="file:///%ExchangeInstallDir%bin\Microsoft.Exchange.Common.IL.dll"/>

None

1) Open the web.config file located at <Exchange Install folder>\Client Access\exchweb\ews using an editor like Notepad.exe.

2) Replace all instances of %ExchangeInstallDir% with the actual path of the Exchange installation folder. E.g. If you have installed Exchange in D:\Program Files\Microsoft\Exchange Server replace %ExchangeInstallDir% with D:\Program Files\Microsoft\Exchange Server\.

Here is a line in the web.config file.

Before

<codeBase version="0.0.0.0" href="file:///%ExchangeInstallDir%bin\Microsoft.Exchange.Common.IL.dll"/>

After

<codeBase version="0.0.0.0" href="file:///D:\Program Files\Microsoft\Exchange Server\bin\Microsoft.Exchange.Common.IL.dll"/>

3) Restart W3SVC service

During uninstall of Rollup 4, the admin is prompted for a request for Source.

Rollup 4 is being uninstalled via 'Add/Remove Programs' and there is a UI requesting the original source media. Still being looked at. Looks to be an MSI Installer bug that has been fixed in a future version of MSI that we hit when changing resetsearchindex.ps1. When prompted for the source, point to the original ExchangeServer.MSI that came with media that you installed with. This will allow you to continue with the uninstall.

Identification of Rollup version via Add/Remove Programs:

To identify the version of the Rollup that you have installed, press the "Click here for support information" link for the update, under Add or Remove Programs (or Programs and Features) applet in Control Panel:

Identification of the rollup version via the Registry:

To identify if the rollup is installed via the registry, the "DisplayVersion" value shown below will be 1. The final release version of the rollup will have a value data of 2 or higher.

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\KB952580 
  Name:            DisplayVersion
  Type:            REG_SZ
  Data:            1

We apologize for any inconvenience this may have caused and we are working to make sure this does not happen again.

- Scott Roberts

102 Comments
Not applicable
I am sorry but this is absolutely unacceptable.  

1. Rollups should not be automatically installed, they should be optional.
2. If a prerelease patch can get into Microsoft update, you leave me no choice but to disable automatic updates.
Not applicable
It is always recommended on servers to configure the Microsoft Update Agent to automatically download, but never to automatically install.  I would suggest this approach in conjunction with proper testing procedures in a lab environment instead of disabling automatic updates altogether.  :)
Not applicable
Glad it was caught. LIke Chris, I only have my servers set to download but not install automatically. Patches only get installed once I've reviewed, or at least scanned, the information on the patch. I doubt there would have been an MS08-xx for this out yet and that alone would have prevented me from installing it until I knew more.
Not applicable
This didn't happen to us, but what happens if the client downloaded it already even if it wasn't applied? When you release the new one, will the client download that one and override the pre-release one?
Not applicable
BDAY-

If your client only downloaded it and is online to the internet, wait 24 hours and the client will force a rescan. Offline clients will be able to install it. I am understanding the meaning of offline as those clients that cannot fully connect to Microsoft Update at the the time of the next scan. In most cases, the 24 hours has already passed.

FYI - Rollup 4 isn't not classified as a Security Update.

Moving forward, Exchange Rollups will be released on the second and fourth Tuesday of the month due to 'may cause a reboot'.

Not applicable
The screenshots and registry don't seem to apply to Vista (using Exch Mgmt Console)

The version i see in the console is 08.01.0311.001. What will the new version be?
Not applicable
Also, the download of the wrong verion is still available via the download link in an MBSA scan.
Not applicable
So you are saying I should not trust any update released by Microsoft until I test it?  This is a great way for full time Exchange Admins to spend their time, but my customers are not going to pay me to do Microsoft’s job.  
I go into small businesses and setup an Exchange server.  During the configuration I set Microsoft update to automatically install patches.  You are saying I should charge my customers to test each patch released by Microsoft then manually install the patch on each server I have setup.  Talk about job security.
Not applicable
Thanks GeeB -
1. We will update the blog with the text of what you will see in Vista and Windows 2008. The new version when released will be 08.01.0311.0xx where xx will be higher than 01. I will probably update this blog once we know the official build number

2. The MBSA Scan is probably due to the MU process that uses it. I beleive the link will not work. MBSA, if I remember correctly uses Microsoft Update regluarly to determine if a Security Update should be offered. It should now offer Rollup 3. I will get back to you on this one

Scott (Exchange)
Not applicable
Andy -

It sounds like what Scott is saying is that it is always a good idea to test  something before installing it (and this doesn't just apply to Microsoft code, either, but to any code that you EVER install).

Although I'm pretty sure that Microsoft tests everything they put out, I doubt that they have the time or resources to test it with every single configuration known to man.  Just because it works with (let's say) the 99% of hardware/software configurations they DO test -- it is not a good idea for you to be that 1% that they don't test AND which crashes the system.

Change Control Processes are ALWAYS a good idea -- even in smaller businesses.
Not applicable
I've already installed the patch on my management workstation.  If I leave it alone, will it upgrade to the new version (via WU) when it's released?
Not applicable
Steve - yes... if you have the machine set to get the MU updates automagically, it will. If you installed it manually, you can just install it on top of what you have now.
Not applicable

Ok folks,

I want to point out that there is an uninstall case that we just uncovered that people may hit. Although the cases where customers have had to uninstall this particular version of Rollup 4 is low, I want to share this with everyone.

- On install, the EWS Web.config file is installed with 'placeholder' information that is modified outside of the MSI (installer) while Exchange Setup is running.
- When we uninstall Rollup 4, the EWS web.config (example: D:Program FilesMicrosoftExchange ServerClientAccessexchwebewsweb.config) file is restored to the RTM version without the post-processing.
- On startup, EWS tries to read it and does not function properly.

For those who encounter this condition, the fix is to open the web.config file manually and Find + Replace the information it needs. I should have the blog updated with the official info shortly with ways to detect this and the steps to fix this.

I will have more later this evening as I write up the official blog post.

Scott

Not applicable
Andy,

I wouldn't say you shouldn't trust the updates, but as an experienced administrator, you should know never allow your servers to install patches automatically. You should be scheduling routine maintenance cycles for your systems. I would say this about ANY server environment-- Windows, Linux, Mac, or otherwise. This is especially true if you're doing work as a consultant... what would be worse for your customers-- paying you for an hour of routine maintenance, or paying you for several hours of troubleshooting a botched patch update?

In any case, what would you prefer Microsoft do here? Not even admit the problem exists, leave the updated posted, and then silently replace it with the correct version?
Not applicable
<i>In any case, what would you prefer Microsoft do here? Not even admit the problem exists, leave the updated posted, and then silently replace it with the correct version?</i>

I would rather Microsoft have a little better QC in place than to get pre-releases rolled out to the auto-update system. This is why you'll never see Microsoft Life Support 1.0 - who can afford the risk?

And I concur - auto-updating is a recipe for disaster. The history of Microsoft and patches has notable problems (service pack 6a, anyone?), and having your system download and install a leap of faith patch from Microsoft is an activity that will, eventually, cost you.  
Not applicable
MEC2

Service Pack 6a?  what is this, 1996?
Not applicable
As I write this I'm on the phone with Microsoft for the 8th Hour trying to fix 2 production servers that downloaded this Patch and installed it via WSUS.   It has been a nightmare.   And the fix?   Wipe and reload the servers.
Not applicable
Dr4g0nfly,

What are your symptoms?

An update to the Uninstall web.config issue is:

Symptom:
Exchange Web Services (EWS) operations fail with the following response.
HTTP/1.1 302 Found
Cache-Control: private
Content-Length: 175
Content-Type: text/html; charset=utf-8
Location: /ews/GenericErrorPage.htm?aspxerrorpath=/ews/Exchange.asmx
Server: Microsoft-IIS/7.0
X-AspNet-Version: 2.0.50727
X-Powered-By: ASP.NET
Date: Fri, 12 Sep 2008 01:00:02 GMT

<html>
 <head>
   <title>Object moved</title>
 </head>
 <body>
   <h2>Object moved to <a href="/ews/GenericErrorPage.htm?aspxerrorpath=/ews/Exchange.asmx">here</a>.</h2>
 </body>
</html>

Troubleshooting steps to validate root cause:
1) On the CAS server, open the web.config file located at <Exchange Install folder>Client Accessexchwebews using an editor like Notepad.exe.
2) Look for the presence of the text %ExchangeInstallDir% in the file. E.g.
<codeBase version="0.0.0.0" href="file:///%ExchangeInstallDir%binMicrosoft.Exchange.Common.IL.dll"/>

Issue:
The issue happened because Update Rollup 4 for Exchange server 2007 Service Pack 1 (KB952580) v1 was previously installed on the server and subsequently uninstalled

Workaround (if the rollup cannot be uninstalled immediately): None

Resolution:
1) Open the web.config file located at <Exchange Install folder>Client Accessexchwebews using an editor like Notepad.exe.
2) Replace all instances of %ExchangeInstallDir% with the actual path of the Exchange installation folder. E.g. If you have installed Exchange in D:Program FilesMicrosoftExchange Server replace %ExchangeInstallDir% with D:Program FilesMicrosoftExchange Server.
Here is a line in the web.config file.
Before
<codeBase version="0.0.0.0" href="file:///%ExchangeInstallDir%binMicrosoft.Exchange.Common.IL.dll"/>
After
<codeBase version="0.0.0.0" href="file:///D:Program FilesMicrosoftExchange ServerbinMicrosoft.Exchange.Common.IL.dll"/>
3) Restart W3SVC service


Not applicable
Re: SP6a and 1996

No, it's 2007, but what's changed, other than an automated way to distribute updates that break your system? My point... thanks for making it. The fact they had to actually add a revision increment to a service pack just drives it home.

If you want something more recent, look up the XP SP3 auto update on AMD systems with OEM XP - I had to deal with this zero-hour and it was pretty damn aggravating. Others abound, in fact had one today, computer displays no fonts or text after autoupdates - restore to prior day - fine. The point is, auto updating makes you the beta tester. Wait, and download after the patch has matured, and let the pioneers take the arrows...

MEC2
Not applicable
Many Thanks to Scott Roberts! We had the same problem. Thx.
Not applicable
the fault lies with the WSUS Team - automatic deployment of applications and patches occurs because some items are bulk classified and the wsus team refuses to change their architecture to accomodate more classification to prevent autoinstalls.
we had the same type of problems with FCS deploying to clients - on top of symantec AV.
Not applicable
After uninstalling Rollup 4 I have a lot of Event ID 1309 and noone has access to Out Of Office Assistant. I tried to change the  %ExchangeInstallDir% to the actual install dir and restart W3SVC service - but it doesnt seem to help. What to do now?
Not applicable
Forget what I just wrote :) Forgot a in the end of the path to the exchangedir. Tried again with notepad (replace all) and then it worked.

Thanks for the quick help.
Not applicable
To Scott Roberts (Exchange),



fyi...MBSA scan now no longer detects the need of UR4 as of this morning, however, on any previous reports the download link still works to the bad version:


http://www.download.windowsupdate.com/msdownload/update/software/uprl/2008/08/exchange2007-kb952580-...




Not applicable
"Not aware of many customers being affected" - let's consider who was most likely to be affected: first, the timing of the patch on automatic update meant that it was night or evening in Europe and the Middle East, but still day in North America. Since most would have automatic updates set to go off outside business hours, not so many will have caught the patch in America, but more in time zones east of the Atlantic, and they're less likely to have reached the attention of the Exchange team in the USA. Second the sort of customer using automatic update is likely to be the small to medium size, with a small IT staff or IT contacted out. These people are less likely to have support contracts and less likely to be able to reach the right people at Microsoft. Are you sure it was "not many customers"?
Not applicable
The patch pointed to a KB which wasn't available, so I was wary of it and didn't install it on any of our management boxes--which patch automatically. I patch all our servers manually.

1. Yes. It was unacceptable that this was released, but sometimes planes crash and bridges fail. They'll fix it.

2. KB should be live and say: "This is in testing. Do not install in a production environment". Pull the trigger on the KB at the same time you do the update.

3. I run clean, pristine, simple boxes with grown-up *current* hardware and software: Dell 2950/MD1000, the surprisingly superb Trend ScanMail (and therefore unfortunately: Java), Symantec SEP, BESR, RAWS. And that's it. I do this so that I can rely on the multibillion dollar corporation to adequately test against a standard configuration, because it's going to do it better than I am.
Not applicable
After uninstalling rollup 4 on my cas/hub server, owa login screen (form based) does not display properly, with red x for the images.  Can someone please help?  Thanks.
Not applicable
I could swear my updates are set to download and not install and it still installed the freaking update.  

Everything is working fine but I am getting event id 401 on storage group 1

Instance 1: The physical consistency check has completed, but one or more errors were detected. The consistency check has terminated with error code of -106 (0xffffff96).

My backup has stopped because of this but the server is still running.  I think I am going to leave it alone.  
Not applicable
Holy crap you guys cannot be serious.  I just tried to uninstall rollup 4 and it wouldn't let me because it needed the files from rollup 3.  I have applied all updates via WSUS and have no idea where to go about getting thos files.  This totally sucks.  
Not applicable
Jason,

Install Rollup 3 ontop of Rollup 4. While I don't know exactly what is happening for you, this should restore the cached files to the box for Rollup 3 and then you can try to uninstall Rollup 4. If that fails, let me know and I will get you the command line command to do the uninstall with MSI verbose logging turned on.

I think that I might have someone with a local repro of the problem and hopefully can look at it today.

Thanks
Scott
Not applicable
Jason,

While I don't know your specific scenario, reinstall Rollup 3 which should put locally the MSP in your installer cache. Then you should be able to uninstall rollup 4.

If this doesn't work for you please let me know here. I can give you the uninstall string so that you can turn on verbose MSI logging and I will need that.

Thanks
Scott
Not applicable
What happens if I leave it alone?  I mean everything is workign fine now?

thanks
Not applicable
Scott, thanks for your help on this ... however, should I leave it alone for now or remove it?  The server is runing fine I am only getting event id 401 and 305  Consistency check
Not applicable
The update is still there to download...


http://www.microsoft.com/downloads/details.aspx?familyid=E56FC52A-216E-4225-BF2F-F082C20B7B21&displa...



I thought they removed it right???

Not applicable
I've resolve my issue.  I re-installed rollup 3 again, this time running the msp file manually instead of using Windows update.  I'm not sure why there's a difference.
Not applicable
I was one of the unfortunate who happened to install the update Tuesday night. I followed Scott Roberts' instructions for fixing the EWS web.config, but I had an additional anomaly. Throughout the entire web.config were randomly scattered NULL characters which had replaced valid characters. So for some people, a find and replace on %ExchangeInstallDir% might not completely solve the issue. Try opening the web.config up in a better text editor that is capable of displaying non-text ASCII characters. I used Notepad++ for this. You will still have to find and fix the NULL characters by hand.

Jamie Schwinn
www.systmsny.net
Not applicable
One of or CAS servers got the update...we happened to be patching/updating  the server for the Scheduled Microsoft Tuesday patches.

I uninstalled Rollup4.
I manually edited the web.config file as seen above.
I rebooted.

So far, no errors!  I looks OK.
Not applicable
Jamie,

Thanks for poining out the whitespace issue.

Tak, I am thinking that you might have hit the MAX Disk limit for the MSI Installer cache. I don't know yet the side effects of hitting this so I am checking on it. It is 10% of the current system drive I believe.

Not applicable
so an answer ? should I leave it alone since my exchange si working fine?

Thanks
Not applicable
We were also hit by the automatic update.  (Exchange 2007)

We found all Exchange services were disabled.  By checking another Exchange 2007 system we changed all matching services to Automatic and restarted.  Now we have Exchange running but OWA is dead!  Not a severe limitation (iow, we can get by for a short term albeit with some inconvenience to me personally!).

I tried to uninstall the rollup but it required the original Exchange 2007 CD which I couldn't find readily.  In the meantime I will download another copy off Technet.

I've elected to do nothing further pending Microsoft giving me a reliable method of repair.  From what I read in the blog - that degree e of reliability has not been reached yet.

Can I suggest to Scott, that the revised update install over the top of Rollup 4 and fix it automatically for us???
Not applicable
Why most of you are uninstalling Rollup 4? What problems are you guys facing? Is it complete email failure?
Not applicable
Michael,

I don't know what is happening with your OWA based on the available information. I believe that reinstalling Rollup 3 will rerun the OWA VDIR powershell and set up OWA Properly for you. It runs for every rollup. If that doesn’t solve the problem, we should escalate the issue and get you support.

We have also reproduced the issue with the uninstall that requires the original Exchange 2007 MSI but I don't know exactly why yet. Should know soon. I have the MSI log file and currently reading it. Pointing the uninstall UI to the original MSI will get you around this.

You will be able to install the newer rollup on top of the older Rollup 4. It will solve most of the uninstall issues. If you uninstall the newer Rollup 4 and then uninstall the older Rollup 4, you will still get into the same situation as described above.

M, I would uninstall the rollup. I am researching your problem and should have an answer. You do not have to do what I recommend of course. It just might save you some trouble later on if you have to handle an issue where you need to uninstall the rollup.
Not applicable
M,

Ultimately - if you are not experiencing any of the issues mentioned in our blog post or this comment thread - I'd leave the patch in place. The server works fine, so why not. You will be offered the updated version of this Rollup when it releases and then apply that, and it should be business as usual.
Not applicable
Scott to help you out, here are the 2 errors


Errors as follows


Event ID 305


Instance 1: One or more errors were detected while validating the transaction log files in '\?GLOBALROOTDeviceHarddiskVolumeShadowCopy6EisnerMstorage2log' with a base name of 'E01'. The operation failed with error code -1811 (0xfffff8ed).



For more information, see Help and Support Center at

http://go.microsoft.com/fwlink/events.asp.


Then I got event ID 401


Instance 1: The physical consistency check has completed, but one or more errors were detected. The consistency check has terminated with error code of -106 (0xffffff96).



For more information, see Help and Support Center at

http://go.microsoft.com/fwlink/events.asp.


Yes it sux.. however, I ran an NTbackup on my exchange and it went through no issues.. I believe my database is fine and that this is a bug on Microsoft end.  However I found this article  



http://msexchangeteam.com/archive/2008/09/11/449787.aspx?CommentPosted=true#commentmessage



I am honestly very worried about uninstalling rollup4 as this is a production environment and I am worried it will crash my server.  It’s working now so I am leaving it alone and crossing my fingers it will be okay.  However, if you tell me that this will cause

me serious issues very soon then I will take my chances and try to remove it then install roll up 3 to fix OWA.



Thanks

Not applicable
I reviewd my log againa nd found this event from WED only

Watson report about to be sent to dw20.exe for process id: 5516, with parameters: E12, c-RTL-AMD64, 08.01.0291.001, edgetransport, unknown, M.E.D.S.U.StreamHandler.CopyStreamData, System.OutOfMemoryException, 164e, unknown.  ErrorReportingEnabled: False

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

event id 4999
Not applicable
I to have attempted to uninstall Rollup 4 and had the uninstall fail out needing files from the Rollup 3.  I then tried to reinstall Rollup 3 by doing a manual download of the patch from the Microsoft.Com web site.  That install also failed out and now all of my exchange services are set to disabled.  Can someone provide me with the a list of the services that I need to set back to automatic.  I do remember that several of them were not automatic but I do not know which ones they were.
Not applicable
see thats why I did not want to remove mine.  I thought today will be a slow day for me and I get to relax after I have been working on their network for 4 months anyways... life= Microsoft :)

here is what you need to have started

ME active directory topology
ME any spam update
edgesync
information store
mail submission
mailbox assitants
pop3
replication service
search indexer
service host
system attendant
transport
log search
ME Exchange


good luck

Not applicable
Gary did it work?
Not applicable
Ended up calling Microsoft and worked with tech there to further resolve issues.  To make a long story short we ended up manually removing the Parch 4 and then reapplied patch 3.  Everything is now working but my suggestion to everyone is if your not having serious issues with the defective patch 4 I would wait for Microsoft to release a fix.  Three hours on the phone makes my head hurt.
Gary
Not applicable
Glad to hear that things worked for you...

Do we know when this fix will be released?  Rollup4 V2?

Thanks