Exchange 2010 Sp3

I have 4 exchange 2010 SP3 RU mailbox servers. I continue to fail getting them updated to SP3 RU11. the question is do I have to install all the previous Rollups before I can Rollup to RU11 from RU7. that is the only thing I can think of now at this point. I don't recall.having to do that in the past but I wanted to a least check. UAC is disabled, all virus scanning software is also disabled. it does have some type of netbackup software that the storage team uses and I'm not sure if that is the issue but I stopped those services with no success. the OS is windows server 2012 DATACENTER. any suggestions would be great.
LVL 30
timgreen7077Exchange EngineerAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

R--RCommented:
You can upgrade RU 11 directly. Please provide us the failed error message occur during the installation.
timgreen7077Exchange EngineerAuthor Commented:
There is no error, it starts the process of stopping the services and then it starts rolling back and says not changes were performed to the system. It nevers goes pass stopping services before it instantly starts the roll back. See attached Exchange Setup logs.
ServiceControl.log
ServiceStartupMode.xml
ServiceState.xml
Davis McCarnOwnerCommented:
Numerous hits say to turn UAC back on and to install it from an elevated command prompt: http://www.msdigest.net/2014/03/setup-wizard-for-exchange-update-rollup-ended-prematurely/
Your Guide to Achieving IT Business Success

The IT Service Excellence Tool Kit has best practices to keep your clients happy and business booming. Inside, you’ll find everything you need to increase client satisfaction and retention, become more competitive, and increase your overall success.

techbnjcompCommented:
Also it could be waiting for reboot from another update.   As Mr. McCarn said try UAC on and from elevated but after that reboot system properly and try update again.
timgreen7077Exchange EngineerAuthor Commented:
I have rebooted multiple times, and tried again. I have attempted to install with UAC on from and elevated account and that failed also.  I found the following link and i will try this and see what happens and I will update.

https://support.microsoft.com/en-us/kb/2784788#/en-us/kb/2784788
timgreen7077Exchange EngineerAuthor Commented:
I have attempted the fix on the link but still no luck. See the attached rollup log, maybe there is something there that one of you have seen before that may help.
rollup.txt
Davis McCarnOwnerCommented:
Yes; about 95% of the way down your log is CAQuietExec:  Error 0x80070001

According to this, its a machine or user policy which needs to be set to "not configured":
https://support.microsoft.com/en-us/kb/981474
timgreen7077Exchange EngineerAuthor Commented:
Davis I will try this and update.
timgreen7077Exchange EngineerAuthor Commented:
Those polices were set to unrestricted but I have made the changes on the GPO, and verified that those userpolicy and machinepolicy are now undefined. I still get the exact same result. I forced the gpupdate and the applied the new undefined policy. I didn't reboot the server though, but I still get the same issue when trying to update. See new log.
rollup3.log
Davis McCarnOwnerCommented:
Is this a server that's a member of a database availability group (DAG)?
If it is:
https://technet.microsoft.com/en-gb/library/ee861125(v=exchg.141).aspx
timgreen7077Exchange EngineerAuthor Commented:
Yes it is a member of the DAG, but the DAG maintenance script doesn't even run, it gives an error. Anytime I update, I manually move the active DB copy to a different DAG member. They had a contractor working on Exchange before I came aboard and he also installed Windows Server 2012 DataCenter on the Exchange Servers along with WMF 4.0, so I have also removed WMF 4.0 from the servers, but the DAG maintenance script has never worked.
Davis McCarnOwnerCommented:
Are you a member of the domain admin's group?
timgreen7077Exchange EngineerAuthor Commented:
Yes I am a member of that group.
Davis McCarnOwnerCommented:
"but the DAG maintenance script doesn't even run, it gives an error"  What, EXACTLY, is the error?
timgreen7077Exchange EngineerAuthor Commented:
Not sure, I haven't run it in about 3 weeks. I would have to try that again later but that script definitely fails.
Davis McCarnOwnerCommented:
Then we're stuck until you have that error.
timgreen7077Exchange EngineerAuthor Commented:
This is the error from DAG maintenance script:

At C:\Program Files\Microsoft\Exchange Server\V14\Scripts\DagCommonLibrary.ps1:494 char:6
+         return $moveSuccessful
+         ~~~~~~~~~~~~~~~~~~~~~~
Control cannot leave a finally block.
At C:\Program Files\Microsoft\Exchange Server\V14\Scripts\DagCommonLibrary.ps1:926 char:5
+                 return $success
+                 ~~~~~~~~~~~~~~~
Control cannot leave a finally block.
    + CategoryInfo          : ParserError: (:) [], ParseException
    + FullyQualifiedErrorId : ControlLeavingFinally

Test-RsatClusteringInstalled : The term 'Test-RsatClusteringInstalled' is not recognized as the name of a cmdlet,
function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that th
path is correct and try again.
At C:\Program Files\Microsoft\Exchange Server\V14\Scripts\StartDagServerMaintenance.ps1:78 char:2
+     Test-RsatClusteringInstalled
+     ~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : ObjectNotFound: (Test-RsatClusteringInstalled:String) [], CommandNotFoundException
    + FullyQualifiedErrorId : CommandNotFoundException

log-verbose : The term 'log-verbose' is not recognized as the name of a cmdlet, function, script file, or operable
program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again.
At C:\Program Files\Microsoft\Exchange Server\V14\Scripts\StartDagServerMaintenance.ps1:232 char:4
+             log-verbose ($StartDagServerMaintenance_LocalizedStrings.res_0015 )
+             ~~~~~~~~~~~
    + CategoryInfo          : ObjectNotFound: (log-verbose:String) [], CommandNotFoundException
    + FullyQualifiedErrorId : CommandNotFoundException

log-verbose : The term 'log-verbose' is not recognized as the name of a cmdlet, function, script file, or operable
program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again.
At C:\Program Files\Microsoft\Exchange Server\V14\Scripts\StartDagServerMaintenance.ps1:97 char:3
+         log-verbose ($StartDagServerMaintenance_LocalizedStrings.res_0008 -f $shortSer ...
+         ~~~~~~~~~~~
    + CategoryInfo          : ObjectNotFound: (log-verbose:String) [], CommandNotFoundException
Davis McCarnOwnerCommented:
timgreen7077Exchange EngineerAuthor Commented:
We are running PS version 3.0 on window server 2012 but I don't show that the KB is installed.
Davis McCarnOwnerCommented:
PS 3.0 breaks the scripts for the Exchange rollups.  Its in that thread I posted.
timgreen7077Exchange EngineerAuthor Commented:
I agree but that shouldn't have anything to do with the RU 11 installing. This installed successfully on the CAS/Hub servers, and they also have PS 3.0
Davis McCarnOwnerCommented:
https://social.technet.microsoft.com/Forums/exchange/en-US/acc712fd-c4ee-4b56-be55-618990eec9a9/dag-maintenance-scripts-do-not-work-anymore-after-sp2-ur5-upgrade?forum=exchange2010
Sudeep SharmaTechnical DesignerCommented:
Latest roll up is RU12, did you tried that?

KB:
http://support.microsoft.com/kb/3096066

Download:
https://www.microsoft.com/en-us/download/details.aspx?id=50359

Sudeep
timgreen7077Exchange EngineerAuthor Commented:
Please disregard this ticket. I will be contacting Microsoft about this issue.
timgreen7077Exchange EngineerAuthor Commented:
I've requested that this question be deleted for the following reason:

Please disregard this ticket. I will be contacting Microsoft about this issue.
timgreen7077Exchange EngineerAuthor Commented:
This has now been completed. The issue was snap manager was installed and once we uninstalled it from the mailbox servers, all updates were successful.
timgreen7077Exchange EngineerAuthor Commented:
This has now been completed. The issue was snap manager was installed and once we uninstalled it from the mailbox servers, all updates were successful.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
timgreen7077Exchange EngineerAuthor Commented:
This has now been completed. The issue was snap manager was installed and once we uninstalled it from the mailbox servers, all updates were successful.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Exchange

From novice to tech pro — start learning today.