Software Updates failed to installed on Server 2008 R2

Hello All,
I have performed deployment of around 89 software updates on Windows Server 2008 Citrix Terminal Server. However, out of them only 1 of them got installed .  8 updates got downloaded in ccmcache.
The updates were installing manually if we try to install them.
I do not understand why this happened.
I have checked the "States 3 - States for a deployment and computer" and appears that Software updates are not required. Also, i of list of few updates which listed
as "is installed", but actually does not appears to be installed.
Please share your valuable inputs.

software updates were targetting using single deployment & is there any deadline configured for the same?
someone might have uninstalled previously installed updates, please run software update scan cycle to see latest results. also check event viewer logs & updatestore.log & windowupdate.log for more information.
Prashant Patil

Similar Messages

  • The unattended installation failed while installing SQL Server 2008 R2 ????

    Hi gurus,
    I got an error while installing SQL Server 2008 R2 in Windows 2008 R2 standard 64 bit operating system.
    LOG file*
    Customized installation of SQL Server 2008R2 for SAP *
    Detailed results:
      Feature:                       Database Engine Services
      Status:                        Failed: see logs for details
      MSI status:                    Failed: see details below
      MSI error code:                0x1639
      MSI log file location:         C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20120116_221104\SqlBrowser_Cpu32_1.log
      MSI error description:        
      MSI status:                    Failed: see details below
      MSI error code:                0x1639
      MSI log file location:         C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20120116_221104\sql_common_core_Cpu64_1.log
      MSI error description:        
      MSI status:                    Failed: see details below
      MSI error code:                0x1639
      MSI log file location:         C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20120116_221104\SqlWriter_Cpu64_1.log
      MSI error description:        
      MSI status:                    Failed: see details below
      MSI error code:                0x1639
      MSI log file location:         C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20120116_221104\sql_tools_Cpu64_1.log
      MSI error description:        
      Configuration status:          Passed
      Feature:                       Full-Text Search
      Status:                        Failed: see logs for details
      MSI status:                    Failed: see details below
      MSI error code:                0x1639
      MSI log file location:         C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20120116_221104\SqlBrowser_Cpu32_1.log
      MSI error description:        
      MSI status:                    Failed: see details below
      MSI error code:                0x1639
      MSI log file location:         C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20120116_221104\sql_common_core_Cpu64_1.log
      MSI error description:        
      Configuration status:          Passed
      Feature:                       Client Tools Connectivity
      Status:                        Failed: see logs for details
      MSI status:                    Failed: see details below
      MSI error code:                0x1639
      MSI log file location:         C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20120116_221104\sql_common_core_Cpu64_1.log
      MSI error description:        
      MSI status:                    Failed: see details below
      MSI error code:                0x1639
      MSI log file location:         C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20120116_221104\sql_tools_Cpu64_1.log
      MSI error description:        
      MSI status:                    Failed: see details below
      MSI error code:                0x1639
      MSI log file location:         C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20120116_221104\SqlBrowser_Cpu32_1.log
      MSI error description:        
      Configuration status:          Passed
      Feature:                       Management Tools - Complete
      Status:                        Failed: see logs for details
      MSI status:                    Failed: see details below
      MSI error code:                0x1639
      MSI log file location:         C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20120116_221104\sql_common_core_Cpu64_1.log
      MSI error description:        
      MSI status:                    Failed: see details below
      MSI error code:                0x1639
      MSI log file location:         C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20120116_221104\sql_tools_Cpu64_1.log
      MSI error description:        
      MSI status:                    Failed: see details below
      MSI error code:                0x1639
      MSI log file location:         C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20120116_221104\SqlBrowser_Cpu32_1.log
      MSI error description:        
      Configuration status:          Passed
      Feature:                       Management Tools - Basic
      Status:                        Failed: see logs for details
      MSI status:                    Failed: see details below
      MSI error code:                0x1639
      MSI log file location:         C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20120116_221104\sql_common_core_Cpu64_1.log
      MSI error description:        
      MSI status:                    Failed: see details below
      MSI error code:                0x1639
      MSI log file location:         C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20120116_221104\SqlBrowser_Cpu32_1.log
      MSI error description:        
      MSI status:                    Failed: see details below
      MSI error code:                0x1639
      MSI log file location:         C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20120116_221104\sql_tools_Cpu64_1.log
      MSI error description:        
      Configuration status:          Passed
      Feature:                       Client Tools SDK
      Status:                        Failed: see logs for details
      MSI status:                    Failed: see details below
      MSI error code:                0x1639
      MSI log file location:         C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20120116_221104\sql_tools_Cpu64_1.log
      MSI error description:        
      MSI status:                    Failed: see details below
      MSI error code:                0x1639
      MSI log file location:         C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20120116_221104\SqlBrowser_Cpu32_1.log
      MSI error description:        
      MSI status:                    Failed: see details below
      MSI error code:                0x1639
      MSI log file location:         C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20120116_221104\sql_common_core_Cpu64_1.log
      MSI error description:        
      Configuration status:          Passed
      Feature:                       Client Tools Backwards Compatibility
      Status:                        Failed: see logs for details
      MSI status:                    Failed: see details below
      MSI error code:                0x1639
      MSI log file location:         C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20120116_221104\sql_common_core_Cpu64_1.log
      MSI error description:        
      MSI status:                    Failed: see details below
      MSI error code:                0x1639
      MSI log file location:         C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20120116_221104\sql_tools_Cpu64_1.log
      MSI error description:        
      MSI status:                    Failed: see details below
      MSI error code:                0x1639
      MSI log file location:         C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20120116_221104\SqlBrowser_Cpu32_1.log
      MSI error description:        
      Configuration status:          Passed
      Feature:                       Business Intelligence Development Studio
      Status:                        Failed: see logs for details
      MSI status:                    Failed: see details below
      MSI error code:                0x1639
      MSI log file location:         C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20120116_221104\sql_common_core_Cpu64_1.log
      MSI error description:        
      MSI status:                    Failed: see details below
      MSI error code:                0x1639
      MSI log file location:         C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20120116_221104\SqlBrowser_Cpu32_1.log
      MSI error description:        
      MSI status:                    Failed: see details below
      MSI error code:                0x1639
      MSI log file location:         C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20120116_221104\sql_tools_Cpu64_1.log
      MSI error description:        
      Configuration status:          Passed
    Rules with failures:
    Global rules:
    Scenario specific rules:
    Rules report file:               C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20120116_221104\SystemConfigurationCheck_Report.htm
    1/16/2012 10:13:34 PM
    Message Box "Installation failed"
    The unattended installation failed.
      Installation Step: The unattended installation failed.
      Return Code:       -2068052377
      Log File:          C:\Windows\SQL4SAP.log
    Check the log file above.
    See SAP note 1144459 for known issues.
    Result: vbOK
    Registry settings (2/2):
    HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\AppCompatFlags\{3d06c673-5e8a-41c0-b47f-3c3ca0a22e67}
    WRITE(REG_DWORD): 4
    HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\AppCompatFlags\{2b9034f3-b661-4d36-a5ef-60ab5a711ace}
    WRITE(REG_DWORD): 4
    1/16/2012 10:37:32 PM
    Quit script with return code 1
    Please help me out with this issue.
    REGARDS,
    Raj

    Hello Raj,
    MS SQL DB installation specific steps for SAP system is clearly documented in SAP Installation guide. Please download from SMP, read it carefully and install as mentioned in the guide.
    Hope it helps.
    Thanks,
    Siva Kumar

  • Software updater fails to connect to server. How can I fix?

    Software updater fails tp connect with the server. I have tried a restart and checked network connections and internet access. I have no problems connecting to internet, App Store and iTunes Store. Help!

    If you know what downloads to look for you get them from support.apple.com.  For example the 10.6.8 combo update v1.1 can be found here.
    The probelm is knowing what to look for and that's why softwere update comes in handy even if you don't want to have it do the downloads.  What's probably going on was that the servers looked by software update were either temporarily down, or as mentioned above, overloaded.  Wait a while and try it again.

  • Software updates fail to install...

    Howdy...
    Trying to test a couple updates deployed to 5 computers and 4 of them fail with the following error:
    Error Code:  0X87D00664
    Error Description:  Updates handler job was cancelled.
    Any thoughts???
    The log file says in RED:  Execution cancelled by job.  Update will not be monitored.
    Here's the Updateshandler.log file
    ContentAvailable notification received from CAS.
    UpdatesHandler 11/7/2013 2:56:53 PM
    4880 (0x1310)
    Contents downloaded successfully for Update (45dd224d-d9fc-421d-a885-1788fd05f92a).
    UpdatesHandler 11/7/2013 2:56:53 PM
    4880 (0x1310)
    ContentAvailable notification received from CAS.
    UpdatesHandler 11/7/2013 2:56:53 PM
    1392 (0x0570)
    Contents downloaded successfully for Update (e0ed4bab-1c29-4e00-8a22-4502d10810f9).
    UpdatesHandler 11/7/2013 2:56:53 PM
    1392 (0x0570)
    Download completed for the job ({2D60929F-765F-4BC9-BDE2-047BAEFE045D}).
    UpdatesHandler 11/7/2013 2:56:53 PM
    4880 (0x1310)
    Successfully sent job ({2D60929F-765F-4BC9-BDE2-047BAEFE045D}) success completion to the SdmAgent
    UpdatesHandler 11/7/2013 2:56:53 PM
    1392 (0x0570)
    CompleteJob received from SDM. UpdatesHandler
    11/7/2013 2:56:53 PM 4880 (0x1310)
    Complete - Job ({2D60929F-765F-4BC9-BDE2-047BAEFE045D}) Cleanup.
    UpdatesHandler 11/7/2013 2:56:53 PM
    4880 (0x1310)
    CompleteJob - Job ({2D60929F-765F-4BC9-BDE2-047BAEFE045D}) removed from job manager list.
    UpdatesHandler 11/7/2013 2:56:53 PM
    4880 (0x1310)
    Initiating updates scan for checking applicability.
    UpdatesHandler 11/7/2013 2:56:54 PM
    4196 (0x1064)
    Successfully initiated scan. UpdatesHandler
    11/7/2013 2:56:54 PM 4196 (0x1064)
    Updates scan completion received, result = 0x0.
    UpdatesHandler 11/7/2013 2:56:54 PM
    4880 (0x1310)
    Method (Apply) called from SDM. UpdatesHandler
    11/7/2013 2:56:54 PM 4880 (0x1310)
    Starting job with id = {59209229-A0D3-49F9-A01C-78DA0F259F04}
    UpdatesHandler 11/7/2013 2:56:54 PM
    4880 (0x1310)
    Initiating Scan. Forced = (0) UpdatesHandler
    11/7/2013 2:56:54 PM 4880 (0x1310)
    Successfully initiated scan for job ({59209229-A0D3-49F9-A01C-78DA0F259F04}).
    UpdatesHandler 11/7/2013 2:56:54 PM
    4880 (0x1310)
    Scan completion received for job ({59209229-A0D3-49F9-A01C-78DA0F259F04}).
    UpdatesHandler 11/7/2013 2:56:54 PM
    4880 (0x1310)
    Evaluating status of the updates for the job ({59209229-A0D3-49F9-A01C-78DA0F259F04}).
    UpdatesHandler 11/7/2013 2:56:54 PM
    4880 (0x1310)
    Initiating download for the job ({59209229-A0D3-49F9-A01C-78DA0F259F04}).
    UpdatesHandler 11/7/2013 2:56:54 PM
    4880 (0x1310)
    Starting download on action (INSTALL) for Update (45dd224d-d9fc-421d-a885-1788fd05f92a)
    UpdatesHandler 11/7/2013 2:56:54 PM
    4880 (0x1310)
    Ignoring update state (DOWNLOAD_READY) change in job state (2)
    UpdatesHandler 11/7/2013 2:56:54 PM
    4196 (0x1064)
    Contents already available. UpdatesHandler
    11/7/2013 2:56:54 PM 4880 (0x1310)
    Starting download on action (INSTALL) for Update (e0ed4bab-1c29-4e00-8a22-4502d10810f9)
    UpdatesHandler 11/7/2013 2:56:54 PM
    4880 (0x1310)
    Contents already available. UpdatesHandler
    11/7/2013 2:56:54 PM 4880 (0x1310)
    Download completed for the job ({59209229-A0D3-49F9-A01C-78DA0F259F04}).
    UpdatesHandler 11/7/2013 2:56:54 PM
    4880 (0x1310)
    Job in ready state. Triggering software update policy.
    UpdatesHandler 11/7/2013 2:56:54 PM
    4880 (0x1310)
    IMaintenanceCoordinator::GetTaskState failed because MTC job has not been created yet.
    UpdatesHandler 11/7/2013 2:56:54 PM
    4880 (0x1310)
    Request a MTC task for execution request request id: {37CBE4F6-C75C-489A-9F95-4123BFF99C92}
    UpdatesHandler 11/7/2013 2:56:54 PM
    4880 (0x1310)
    MTC task with id {37CBE4F6-C75C-489A-9F95-4123BFF99C92}, changed state from 0 to 4
    UpdatesHandler 11/7/2013 2:56:54 PM
    4348 (0x10FC)
    Job {59209229-A0D3-49F9-A01C-78DA0F259F04} is starting execution
    UpdatesHandler 11/7/2013 2:56:54 PM
    4348 (0x10FC)
    Sending ack to MTC for task with id: {37CBE4F6-C75C-489A-9F95-4123BFF99C92}
    UpdatesHandler 11/7/2013 2:56:54 PM
    4348 (0x10FC)
    Job ({59209229-A0D3-49F9-A01C-78DA0F259F04}) already connected, start processing
    UpdatesHandler 11/7/2013 2:56:54 PM
    4348 (0x10FC)
    Initiating Scan. Forced = (0) UpdatesHandler
    11/7/2013 2:56:54 PM 4348 (0x10FC)
    Successfully initiated scan for job ({59209229-A0D3-49F9-A01C-78DA0F259F04}).
    UpdatesHandler 11/7/2013 2:56:54 PM
    4348 (0x10FC)
    MTC task with id {37CBE4F6-C75C-489A-9F95-4123BFF99C92}, changed state from 4 to 5
    UpdatesHandler 11/7/2013 2:56:54 PM
    4348 (0x10FC)
    No change in the handle state. Ignoring. UpdatesHandler
    11/7/2013 2:56:54 PM 4348 (0x10FC)
    Scan completion received for job ({59209229-A0D3-49F9-A01C-78DA0F259F04}).
    UpdatesHandler 11/7/2013 2:56:54 PM
    4880 (0x1310)
    Evaluating status of the updates for the job ({59209229-A0D3-49F9-A01C-78DA0F259F04}).
    UpdatesHandler 11/7/2013 2:56:54 PM
    4880 (0x1310)
    CDeploymentJob::InstallUpdatesInBatch - Batch or non-batch install is not in progress for the job ({59209229-A0D3-49F9-A01C-78DA0F259F04}). So allowing install..
    UpdatesHandler 11/7/2013 2:56:54 PM
    4880 (0x1310)
    CDeploymentJob::InstallUpdatesInBatch - Resetting install flag to false as method is complete
    UpdatesHandler 11/7/2013 2:57:21 PM
    4880 (0x1310)
    Job {59209229-A0D3-49F9-A01C-78DA0F259F04} is cancelling execution
    UpdatesHandler 11/7/2013 3:12:54 PM
    6540 (0x198C)
    CancelProcessing for job ({59209229-A0D3-49F9-A01C-78DA0F259F04}) - Finishing the updates processing.
    UpdatesHandler 11/7/2013 3:12:54 PM
    6540 (0x198C)
    Execution cancelled by job. Update will not be monitored
    UpdatesHandler 11/7/2013 3:12:54 PM
    6540 (0x198C)
    Raising event:
    [SMS_CodePage(437), SMS_LocaleID(1033)]
    instance of SMS_SUMAgentUpdateError_Internal_Mom
    ClientID = "GUID:57638E3E-A16A-4A7B-8311-DD83D1147B33";
    DateTime = "20131107211254.488000+000";
    MachineName = "LAB-APPSENSE";
    ModelName = "Site_720F847F-DBAB-43FE-BC06-ABA85246D7E5/SUM_45dd224d-d9fc-421d-a885-1788fd05f92a";
    ProcessID = 3996;
    SdmPackageVersion = "1";
    SiteCode = "CHI";
    ThreadID = 6540;
    UpdateId = "45dd224d-d9fc-421d-a885-1788fd05f92a";
    Win32ErrorCode = 2278557284;
    UpdatesHandler
    11/7/2013 3:12:54 PM 6540 (0x198C)
    Execution cancelled by job. Update will not be monitored
    UpdatesHandler 11/7/2013 3:12:54 PM
    6540 (0x198C)
    Raising event:
    [SMS_CodePage(437), SMS_LocaleID(1033)]
    instance of SMS_SUMAgentUpdateError_Internal_Mom
    ClientID = "GUID:57638E3E-A16A-4A7B-8311-DD83D1147B33";
    DateTime = "20131107211254.550000+000";
    MachineName = "LAB-APPSENSE";
    ModelName = "Site_720F847F-DBAB-43FE-BC06-ABA85246D7E5/SUM_e0ed4bab-1c29-4e00-8a22-4502d10810f9";
    ProcessID = 3996;
    SdmPackageVersion = "1";
    SiteCode = "CHI";
    ThreadID = 6540;
    UpdateId = "e0ed4bab-1c29-4e00-8a22-4502d10810f9";
    Win32ErrorCode = 2278557284;
    UpdatesHandler
    11/7/2013 3:12:54 PM 6540 (0x198C)
    Execution completed for the job ({59209229-A0D3-49F9-A01C-78DA0F259F04}).
    UpdatesHandler 11/7/2013 3:12:54 PM
    6540 (0x198C)
    Successfully sent job ({59209229-A0D3-49F9-A01C-78DA0F259F04}) success completion to the SdmAgent
    UpdatesHandler 11/7/2013 3:12:54 PM
    4872 (0x1308)
    CompleteJob received from SDM. UpdatesHandler
    11/7/2013 3:12:54 PM 4040 (0x0FC8)
    Complete - Job ({59209229-A0D3-49F9-A01C-78DA0F259F04}) Cleanup.
    UpdatesHandler 11/7/2013 3:12:54 PM
    4040 (0x0FC8)
    CompleteJob - Job ({59209229-A0D3-49F9-A01C-78DA0F259F04}) removed from job manager list.
    UpdatesHandler 11/7/2013 3:12:54 PM
    4040 (0x0FC8)

    Hi,
    “Win32ErrorCode = 2278557284”
    The reason is the updates fail to finish installation before the defined “Max Run Time” by Configuration Manager, aka it times out. So Configuration Manager Client agent killed the installation process.
    Please refer to the following blog.
    Configuration Manager May Fail to
    Install Exchange Rollup (KB2706990, KB2734323) because of Timeout
    Best Regards,
    Joyce Li
    We
    are trying to better understand customer views on social support experience, so your participation in this
    interview project would be greatly appreciated if you have time.
    Thanks for helping make community forums a great place.

  • Software updates fail to install so does office for mac 2011

    When I check for software updates it says I have 5:
    MacBook Pro EFI Firware Update v 2.3
    Itunes v 10.5.1
    Digital Camera Raw Compatability Update v 3.9
    Java for Mac OS X 10.6 Update 6 v 6.0
    MacBook Pro SMC Firware Update v 1.5
    When I try to install these items it seems to work fine. It downloads them and prompts me to restart. But when I do, it fails to install any of them ( I have also tried them all one at a time to make sure it's not just one of them messing it up). Then my computer freezes.
    ANY HELP PLEASE??
    Also.. I recently downloaded Microsoft for Mac Home and Student 2011. This downloads fine but when i try to install it gets to the end and says that it encountered a problem. Things I've found online and support from both microsoft and apple have told me do not work. I created another account and tried to open office from my share drive--NOPE. I disabled my antivirus--NOPE. I rebooted in safe mode--NOPE. i fixed my permissions--NOPE. I downloaded the trail version which is supposed to be "error free"--NOPE
    ANY HELP PLEASE??
    Thank you

    The EFI update should be installed all by itself.
    The directions are a bit wacky, and what happens is a bit wacky. If you get that one in, the rest may unclog.

  • All my software update fail after installing Lion

    i was running a software update after Lion was installed and it would get all the way to the end and fail with an unknown error message. i tried updating things individually to see if it was an isolated problem but eery one failed at the end of the update. Please help!

    Depends on what you mean by lost?
    Have they just disappeared from sight, ie can you toggle the little triangle before the Inbox and they come back?
    Or are all you emails totally vanished so you have none in the right hand window?

  • Software Update Fails to Install iLife 09 Updates...

    I have a Macbook with all the most recent updates installed, and computer otherwise running smoothly.
    I had purchased iLife 11 (and since gave it away to a friend) but was very disappointed with the upgrade, and for various reasons decided to go back to the original iLife 09 that my computer came with.
    I had already successfully made the downgrade on my Macbook Pro, by deleting the apps, all its related preference files etc I found by searching my computer. When I went to do the same on my Macbook, I was also able to delete and reinstall iLife 09 without a hitch, but when I got to the point where I ran Software Update is where I ran into some issues...
    Software Update recognizes that I have iLife 09 installed, and tells me there are updates to iDVD, iWeb, iMovie and iPhoto totalling some 272MB. Everything downloads fine, starts to install but hangs for a few minutes on "Validating Packages" and soon after I get an error message that "None of the updates were installed" citing an "Unexpected Error". What gives?
    I have tried the update a few times, after restarts, fixing permissions from Disk Utility, and searched the web for an answer, and come up empty...
    Any help in getting this issue resolved would be appreciated. Thanks!

    Start by bypassing Software update and downloading the updates directly from Apple Support;
    http://support.apple.com/kb/DL803
    http://support.apple.com/kb/DL842
    http://support.apple.com/kb/DL1009
    http://support.apple.com/kb/DL1355
    Install one at a time, repair permissions when all done.

  • Software Updater failed to install

    Hi
    I recently purchased an N82, I installed the Nokia PC suite and as part of the installation it checked for any updates. A few updates were found one of which was the NSU itself (v1.4). All the other updates installed perfectly but the NSU update downloaded and then afetr the download said 'Installation Failed'. No other message. Any help to solve this problem greatly appreciated.
    I am running Windows XP home. I have also tried to download and install from the Nokia web site with the same result.
    Thanks.
    Message Edited by n82boy on 22-Jul-2008 08:08 AM

    Hi,
    retry to download the latest version of NSU here:
    http://europe.nokia.com/softwareupdate
    if you cant complete doenload,i think your os has problem and you should reinstall it.
    NOKIA means:Night Of King In Alone

  • Software Updates Failing - Group Policy Overwritten - Server and Policy NOT CONFIGURED

    I have seen a few posts about this issue and group policy overwriting the settings needed by SCCM with the wrong WSUS server. I checked the wuahandlerlog and found this error but it didnt have the server information.
    "Group policy settings were overwritten by a higher authority (Domain Controller) to: Server  and Policy NOT CONFIGURED"
    The only coputer policy that applies to this system does not have WSUS entries in it.  Windows update runs ok, and I deleted the WSUS registry keys that were set by a script and reinstall the client still getting the same error. I dont see any GPO local or domain, or reg keys that are setting anything. I have 10 other servers is the same AD container that this is working perfecly on.......
    Suggestions????

    Check out this GPO:
    Computer Configuration -> Administrative Templates -> System -> Group Policy: 
    "Turn off Local Group Policy Objects processing"
    The help text:
    "This policy setting prevents Local Group Policy Objects (Local GPOs) from being applied.
    By default, the policy settings in Local GPOs are applied before any domain-based GPO policy settings. These policy settings can apply to both users and the local computer. You can disable the processing and application of all Local GPOs to ensure that only
    domain-based GPOs are applied.
    If you enable this policy setting, the system does not process and apply any Local GPOs.
    If you disable or do not configure this policy setting, Local GPOs continue to be applied.
    Note: For computers joined to a domain, it is strongly recommended that you only configure this policy setting  in domain-based GPOs. This policy setting will be ignored on computers that are joined to a workgroup."
    Rolf Lidvall, Swedish Radio (Ltd)

  • An error occurred attempting to install SQL Server 2008 Express Service Pack 1

    i have Setup application with complete prerequisite requirement package create from Visual Studio 2010 setup application.And yes this setup working fine in windows 7 and windows vista but not working in windows xp service pack 3.and getting error when install "An error occurred attempting to install SQL Server 2008 Express Service Pack 1"Give me solution as soon as possible.I have listed summery.txt and log.txt. please refer it.Summery.txt
    ===============================================================Component SQL Server 2008 Express has failed to install with the
    following error message:
    "An error occurred attempting to install SQL Server
    2008 Express Service Pack 1."
    The following components were successfully
    installed:
    - Microsoft .NET Framework 4 Client Profile (x86 and
    x64)
    The following components failed to install:
    - SQL Server 2008
    Express
    See the setup log file located at
    'C:\DOCUME~1\BS\LOCALS~1\Temp\VSD8C9.tmp\install.log' for more
    information.Install.log
    ==========================================================================The following properties have been set:
    Property: [AdminUser]
    = true {boolean}
    Property: [InstallMode] = HomeSite {string}
    Property:
    [ProcessorArchitecture] = Intel {string}
    Property: [VersionNT] = 5.1.3
    {version}
    Running checks for package 'Windows Installer 3.1', phase
    BuildList
    The following properties have been set for package 'Windows
    Installer 3.1':
    Running checks for command
    'WindowsInstaller3_1\WindowsInstaller-KB893803-v2-x86.exe'
    Result of running
    operator 'VersionGreaterThanOrEqualTo' on property 'VersionMsi' and value '3.1':
    true
    Result of checks for command
    'WindowsInstaller3_1\WindowsInstaller-KB893803-v2-x86.exe' is
    'Bypass'
    'Windows Installer 3.1' RunCheck result: No Install
    Needed
    Running checks for package 'Microsoft .NET Framework 4 Client Profile
    (x86 and x64)', phase BuildList
    Reading value 'Version' of registry key
    'HKLM\Software\Microsoft\NET Framework Setup\NDP\v4\Client'
    Unable to read
    registry value
    Not setting value for property
    'DotNet40Client_TargetVersion'
    The following properties have been set for
    package 'Microsoft .NET Framework 4 Client Profile (x86 and x64)':
    Running
    checks for command 'DotNetFX40Client\dotNetFx40_Client_x86_x64.exe'
    Result of
    running operator 'ValueEqualTo' on property 'InstallMode' and value 'HomeSite':
    true
    Result of checks for command
    'DotNetFX40Client\dotNetFx40_Client_x86_x64.exe' is 'Bypass'
    Running checks
    for command 'DotNetFX40Client\dotNetFx40_Client_setup.exe'
    Result of running
    operator 'ValueNotEqualTo' on property 'InstallMode' and value 'HomeSite':
    false
    Skipping ByPassIf because Property 'DotNet40Client_TargetVersion' was
    not defined
    Result of running operator 'ValueEqualTo' on property 'AdminUser'
    and value 'false': false
    Result of running operator 'VersionLessThan' on
    property 'VersionNT' and value '5.1.2': false
    Result of running operator
    'ValueEqualTo' on property 'ProcessorArchitecture' and value 'IA64':
    false
    Result of checks for command
    'DotNetFX40Client\dotNetFx40_Client_setup.exe' is 'Install'
    'Microsoft .NET
    Framework 4 Client Profile (x86 and x64)' RunCheck result: Install
    Needed
    Running checks for package 'SQL Server 2008 Express', phase
    BuildList
    Running external check with command
    'C:\DOCUME~1\BS\LOCALS~1\Temp\VSD8C9.tmp\SqlExpress2008\SqlExpressChk.exe' and
    parameters '10.0.1600 1033'
    Process exited with code 2
    Setting value '2
    {int}' for property 'SQLExpressChk'
    The following properties have been set
    for package 'SQL Server 2008 Express':
    Property: [SQLExpressChk] = 2
    {int}
    Running checks for command
    'SqlExpress2008\SQLEXPR32_x86_ENU.EXE'
    Result of running operator
    'ValueNotExists' on property 'VersionNT': false
    Result of running operator
    'VersionLessThan' on property 'VersionNT' and value '5.1.2': false
    Result of
    running operator 'VersionEqualTo' on property 'VersionNT' and value '5.2.0':
    false
    Result of running operator 'VersionEqualTo' on property 'VersionNT' and
    value '5.2.1': false
    Result of running operator 'ValueEqualTo' on property
    'AdminUser' and value 'false': false
    Result of running operator
    'ValueEqualTo' on property 'SQLExpressChk' and value '-1': false
    Result of
    running operator 'ValueEqualTo' on property 'SQLExpressChk' and value '-2':
    false
    Result of running operator 'ValueEqualTo' on property 'SQLExpressChk'
    and value '-3': false
    Result of running operator 'ValueEqualTo' on property
    'SQLExpressChk' and value '-4': false
    Result of running operator
    'ValueLessThan' on property 'SQLExpressChk' and value '-4': false
    Result of
    running operator 'ValueNotEqualTo' on property 'ProcessorArchitecture' and value
    'Intel': false
    Result of running operator 'ValueNotEqualTo' on property
    'SQLExpressChk' and value '1': true
    Result of checks for command
    'SqlExpress2008\SQLEXPR32_x86_ENU.EXE' is 'Bypass'
    Running checks for command
    'SqlExpress2008\SQLEXPR32_x86_ENU.EXE'
    Result of running operator
    'ValueNotEqualTo' on property 'ProcessorArchitecture' and value 'Intel':
    false
    Result of running operator 'ValueNotEqualTo' on property
    'SQLExpressChk' and value '2': false
    Result of checks for command
    'SqlExpress2008\SQLEXPR32_x86_ENU.EXE' is 'Install'
    Running checks for
    command 'SqlExpress2008\SQLEXPR_x64_ENU.EXE'
    Result of running operator
    'ValueNotEqualTo' on property 'ProcessorArchitecture' and value 'amd64':
    true
    Result of checks for command 'SqlExpress2008\SQLEXPR_x64_ENU.EXE' is
    'Bypass'
    Running checks for command
    'SqlExpress2008\SQLEXPR_x64_ENU.EXE'
    Result of running operator
    'ValueNotEqualTo' on property 'ProcessorArchitecture' and value 'amd64':
    true
    Result of checks for command 'SqlExpress2008\SQLEXPR_x64_ENU.EXE' is
    'Bypass'
    'SQL Server 2008 Express' RunCheck result: Install Needed
    EULA
    for components 'Microsoft .NET Framework 4 Client Profile (x86 and x64)' was
    accepted.
    EULA for components 'SQL Server 2008 Express' was
    accepted.
    Copying files to temporary directory
    "C:\DOCUME~1\BS\LOCALS~1\Temp\VSD8C9.tmp\"
    Downloading files to
    "C:\DOCUME~1\BS\LOCALS~1\Temp\VSD8C9.tmp\"
    (11/15/2014 3:59:51 PM)
    Downloading 'DotNetFX40Client\dotNetFx40_Client_setup.exe' from 'http://go.microsoft.com/fwlink/?linkid=182804'
    to 'C:\DOCUME~1\BS\LOCALS~1\Temp\VSD8C9.tmp\'
    Download completed at
    11/15/2014 3:59:53 PM
    Verifying file integrity of
    C:\DOCUME~1\BS\LOCALS~1\Temp\VSD8C9.tmp\DotNetFX40Client\dotNetFx40_Client_setup.exe
    WinVerifyTrust
    returned 0
    File trusted
    (11/15/2014 3:59:53 PM) Downloading
    'SqlExpress2008\SQLEXPR32_x86_ENU.EXE' from 'http://go.microsoft.com/fwlink/?LinkID=153228&clcid=0x409'
    to 'C:\DOCUME~1\BS\LOCALS~1\Temp\VSD8C9.tmp\'
    Download completed at
    11/15/2014 4:00:22 PM
    Verifying file integrity of
    C:\DOCUME~1\BS\LOCALS~1\Temp\VSD8C9.tmp\SqlExpress2008\SQLEXPR32_x86_ENU.EXE
    WinVerifyTrust
    returned 0
    File trusted
    Running checks for package 'Microsoft .NET
    Framework 4 Client Profile (x86 and x64)', phase BeforePackage
    Reading value
    'Version' of registry key 'HKLM\Software\Microsoft\NET Framework
    Setup\NDP\v4\Client'
    Unable to read registry value
    Not setting value for
    property 'DotNet40Client_TargetVersion'
    The following properties have been
    set for package 'Microsoft .NET Framework 4 Client Profile (x86 and
    x64)':
    Running checks for command
    'DotNetFX40Client\dotNetFx40_Client_setup.exe'
    Result of running operator
    'ValueNotEqualTo' on property 'InstallMode' and value 'HomeSite':
    false
    Skipping ByPassIf because Property 'DotNet40Client_TargetVersion' was
    not defined
    Result of running operator 'ValueEqualTo' on property 'AdminUser'
    and value 'false': false
    Result of running operator 'VersionLessThan' on
    property 'VersionNT' and value '5.1.2': false
    Result of running operator
    'ValueEqualTo' on property 'ProcessorArchitecture' and value 'IA64':
    false
    Result of checks for command
    'DotNetFX40Client\dotNetFx40_Client_setup.exe' is 'Install'
    'Microsoft .NET
    Framework 4 Client Profile (x86 and x64)' RunCheck result: Install
    Needed
    Verifying file integrity of
    C:\DOCUME~1\BS\LOCALS~1\Temp\VSD8C9.tmp\DotNetFX40Client\dotNetFx40_Client_setup.exe
    WinVerifyTrust
    returned 0
    File trusted
    Installing using command
    'C:\DOCUME~1\BS\LOCALS~1\Temp\VSD8C9.tmp\DotNetFX40Client\dotNetFx40_Client_setup.exe'
    and parameters ' /q /norestart /ChainingPackage ClientX64ClickOnce /lcid
    1033'
    Process exited with code 0
    Running checks for package 'Microsoft
    .NET Framework 4 Client Profile (x86 and x64)', phase AfterPackage
    Reading
    value 'Version' of registry key 'HKLM\Software\Microsoft\NET Framework
    Setup\NDP\v4\Client'
    Read string value '4.0.30319'
    Setting value
    '4.0.30319 {string}' for property 'DotNet40Client_TargetVersion'
    The
    following properties have been set for package 'Microsoft .NET Framework 4
    Client Profile (x86 and x64)':
    Property: [DotNet40Client_TargetVersion] =
    4.0.30319 {string}
    Running checks for command
    'DotNetFX40Client\dotNetFx40_Client_setup.exe'
    Result of running operator
    'ValueNotEqualTo' on property 'InstallMode' and value 'HomeSite':
    false
    Result of running operator 'VersionGreaterThanOrEqualTo' on property
    'DotNet40Client_TargetVersion' and value '4.0.30129': true
    Result of checks
    for command 'DotNetFX40Client\dotNetFx40_Client_setup.exe' is
    'Bypass'
    'Microsoft .NET Framework 4 Client Profile (x86 and x64)' RunCheck
    result: Install Succeeded
    Running checks for package 'SQL Server 2008
    Express', phase BeforePackage
    Running external check with command
    'C:\DOCUME~1\BS\LOCALS~1\Temp\VSD8C9.tmp\SqlExpress2008\SqlExpressChk.exe' and
    parameters '10.0.1600 1033'
    Process exited with code 2
    Setting value '2
    {int}' for property 'SQLExpressChk'
    The following properties have been set
    for package 'SQL Server 2008 Express':
    Property: [SQLExpressChk] = 2
    {int}
    Running checks for command
    'SqlExpress2008\SQLEXPR32_x86_ENU.EXE'
    Result of running operator
    'ValueNotEqualTo' on property 'ProcessorArchitecture' and value 'Intel':
    false
    Result of running operator 'ValueNotEqualTo' on property
    'SQLExpressChk' and value '2': false
    Result of checks for command
    'SqlExpress2008\SQLEXPR32_x86_ENU.EXE' is 'Install'
    'SQL Server 2008 Express'
    RunCheck result: Install Needed
    Verifying file integrity of
    C:\DOCUME~1\BS\LOCALS~1\Temp\VSD8C9.tmp\SqlExpress2008\SQLEXPR32_x86_ENU.EXE
    WinVerifyTrust
    returned 0
    File trusted
    Installing using command
    'C:\DOCUME~1\BS\LOCALS~1\Temp\VSD8C9.tmp\SqlExpress2008\SQLEXPR32_x86_ENU.EXE'
    and parameters '/q /hideconsole /action=Upgrade /instancename=SQLEXPRESS
    /skiprules=RebootRequiredCheck'
    Process exited with code
    -2068578302
    Status of package 'Microsoft .NET Framework 4 Client Profile (x86
    and x64)' after install is 'InstallSucceeded'
    Status of package 'SQL Server
    2008 Express' after install is 'InstallFailed'
    S S Manne

    Hi Manne,
    As your description, you come across an error when trying to install SQL Server 2008 express Service Pack 1 on windows XP Service Pack 3 machine. From your error log, I get the error(unable to read registry value). As my analysis, the issue could be due
    to that your account doesn't have access to registry. Below are the recommendations for troubleshooting the issue.
    1. Make sure that you log in as an administrator of the machine.
    2. Please follow the steps below to make sure that you have granted the right permission to registry.
    a. Located HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server in registry.
    b. Right click and go to Permission, then you could see user accounts or groups. If your user account is not in the list, you could click Add to add your account there.
    c. Select your account and Click on Advance.
    d. Check on both check box ('Include inheritable permissions from this object's parent'.
    and 'Replace all child object permissions with inheritable permissions from this object'), click OK.
    e. Click OK again.
    Regards,
    Michelle Li

  • Cannot Install Sql Server 2008, Gives The Error "Database Engine Services Failed"

    I cannot install Sql Server 2008 R2 on Windows 8. Tried many times but failed because it gives the error "Database
    Engine Services Failed". Sql files cannot be corrupted because i can install the same setup on Windows 7 and i can connect to databases.
    I tried all the things below;
    * I'm uninstalling everything related with Sql Server from Control Panel/Programs And Features.
    * I'm deleting all the keys related with Sql Server from Regedit.
    * Later i'm restarting windows, and trying to install again. But during the install it gives the error "Database
    Engine Services Failed", install is finishing but when i opened the Management Studio i cannot connect to Database Engine with Sa naturally.
    * My firewall is already closed. And i have not any antivirus software.
    * I gave the permission for port 1433 on firewall.
    Please help me. Why i always take "Database Engine Services Failed" error? I will get crazy cause of that for many days.

    Here's the ERRORLOG file which i found under the folder;
    Microsoft SQL Server/MSSQL10_50.MSSQLSERVER/MSSQL/Log.
    2014-09-27 03:39:40.15 Server      Microsoft SQL Server 2008 R2 (RTM) - 10.50.1600.1 (X64) 
    Apr  2 2010 15:48:46 
    Copyright (c) Microsoft Corporation
    Developer Edition (64-bit) on Windows NT 6.2 <X64> (Build 9200: )
    2014-09-27 03:39:40.15 Server      (c) Microsoft Corporation.
    2014-09-27 03:39:40.15 Server      All rights reserved.
    2014-09-27 03:39:40.15 Server      Server process ID is 5768.
    2014-09-27 03:39:40.15 Server      System Manufacturer: 'SAMSUNG ELECTRONICS CO., LTD.', System Model: '350V5C/350V5X/350V4C/350V4X/351V5C/351V5X/351V4C/351V4X/3540VC/3540VX/3440VC/3440VX'.
    2014-09-27 03:39:40.15 Server      Authentication mode is MIXED.
    2014-09-27 03:39:40.15 Server      Logging SQL Server messages in file 'C:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\Log\ERRORLOG'.
    2014-09-27 03:39:40.15 Server      Registry startup parameters: 
    -d C:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\DATA\master.mdf
    -e C:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\Log\ERRORLOG
    -l C:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\DATA\mastlog.ldf
    2014-09-27 03:39:40.15 Server      Command Line Startup Parameters:
    -m SqlSetup
    -f
    -Q
    -q Turkish_CI_AS
    -T 4022
    -T 4010
    -T 3659
    -T 3610
    2014-09-27 03:39:40.18 Server      Warning: The server instance was started using minimal configuration startup option (-f). Starting an instance of SQL Server with minimal configuration places the server in single-user mode automatically.  After
    the server has been started with minimal configuration, you should change the appropriate server option value or values, stop, and then restart the server.
    2014-09-27 03:39:40.18 Server      SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
    2014-09-27 03:39:40.18 Server      Detected 4 CPUs. This is an informational message; no user action is required.
    2014-09-27 03:39:40.31 Server      Perfmon counters for resource governor pools and groups failed to initialize and are disabled.
    2014-09-27 03:39:40.32 Server      Using dynamic lock allocation.  Initial allocation of 2500 Lock blocks and 5000 Lock Owner blocks per node.  This is an informational message only.  No user action is required.
    2014-09-27 03:39:40.43 Server      Node configuration: node 0: CPU mask: 0x000000000000000f:0 Active CPU mask: 0x000000000000000f:0. This message provides a description of the NUMA configuration for this computer. This is an informational message
    only. No user action is required.
    2014-09-27 03:39:40.45 Server      Support for distributed transactions was not enabled for this instance of the Database Engine because it was started using the minimal configuration option. This is an informational message only. No user action
    is required.
    2014-09-27 03:39:40.45 spid7s      Warning ******************
    2014-09-27 03:39:40.45 spid7s      SQL Server started in single-user mode. This an informational message only. No user action is required.
    2014-09-27 03:39:40.46 spid7s      Starting up database 'master'.
    2014-09-27 03:39:40.52 spid7s      Recovery is writing a checkpoint in database 'master' (1). This is an informational message only. No user action is required.
    2014-09-27 03:39:40.58 spid7s      SQL Server was started using the -f flag. SQL Server Audit is disabled. This is an informational message. No user action is required.
    2014-09-27 03:39:40.59 spid7s      FILESTREAM: effective level = 0, configured level = 0, file system access share name = 'MSSQLSERVER'.
    2014-09-27 03:39:40.59 spid7s      Server started with '-f' option. Auditing will not be started. This is an informational message only; no user action is required.
    2014-09-27 03:39:40.59 spid7s      Starting up database 'mssqlsystemresource'.
    2014-09-27 03:39:40.61 spid7s      The resource database build version is 10.50.1600. This is an informational message only. No user action is required.
    2014-09-27 03:39:40.94 spid7s      Password policy update was successful.
    2014-09-27 03:39:40.94 spid8s      Starting up database 'model'.
    2014-09-27 03:39:40.95 spid7s      Server name is 'CAGATAY'. This is an informational message only. No user action is required.
    2014-09-27 03:39:41.21 spid8s      Clearing tempdb database.
    2014-09-27 03:39:41.21 spid10s     A new instance of the full-text filter daemon host process has been successfully started.
    2014-09-27 03:39:41.24 Server      A self-generated certificate was successfully loaded for encryption.
    2014-09-27 03:39:41.24 Server      Server local connection provider is ready to accept connection on [ \\.\pipe\SQLLocal\MSSQLSERVER ].
    2014-09-27 03:39:41.24 Server      Dedicated administrator connection support was not started because it is disabled on this edition of SQL Server. If you want to use a dedicated administrator connection, restart SQL Server using the trace flag
    7806. This is an informational message only. No user action is required.
    2014-09-27 03:39:41.28 Server      The SQL Server Network Interface library could not register the Service Principal Name (SPN) for the SQL Server service. Error: 0x54b, state: 3. Failure to register an SPN may cause integrated authentication
    to fall back to NTLM instead of Kerberos. This is an informational message. Further action is only required if Kerberos authentication is required by authentication policies.
    2014-09-27 03:39:41.28 Server      SQL Server is now ready for client connections. This is an informational message; no user action is required.
    2014-09-27 03:39:41.70 spid8s      Starting up database 'tempdb'.
    2014-09-27 03:39:41.86 spid7s      Warning ******************
    2014-09-27 03:39:41.86 spid7s      Attempting to change default collation to Turkish_CI_AS.
    2014-09-27 03:39:41.92 spid7s       index restored for master.syspriorities.
    2014-09-27 03:39:41.95 spid7s       index restored for master.sysbrickfiles.
    2014-09-27 03:39:41.96 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:41.96 spid7s       index restored for master.sysowners.
    2014-09-27 03:39:42.13 spid7s       index restored for master.sysdbreg.
    2014-09-27 03:39:42.16 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:42.16 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:42.16 spid7s       index restored for master.sysschobjs.
    2014-09-27 03:39:42.17 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:42.17 spid7s       index restored for master.syscolpars.
    2014-09-27 03:39:42.17 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:42.18 spid7s       index restored for master.sysxlgns.
    2014-09-27 03:39:42.18 spid7s       index restored for master.sysxsrvs.
    2014-09-27 03:39:42.18 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:42.18 spid7s       index restored for master.sysnsobjs.
    2014-09-27 03:39:42.18 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:42.18 spid7s       index restored for master.syscerts.
    2014-09-27 03:39:42.19 spid7s       index restored for master.sysrmtlgns.
    2014-09-27 03:39:42.19 spid7s       index restored for master.sysxprops.
    2014-09-27 03:39:42.19 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:42.19 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:42.31 spid7s       index restored for master.sysscalartypes.
    2014-09-27 03:39:42.31 spid7s       index restored for master.sysidxstats.
    2014-09-27 03:39:42.31 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:42.32 spid7s       index restored for master.sysendpts.
    2014-09-27 03:39:42.32 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:42.32 spid7s       index restored for master.sysclsobjs.
    2014-09-27 03:39:42.32 spid7s       index restored for master.sysremsvcbinds.
    2014-09-27 03:39:42.32 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:42.32 spid7s       index restored for master.sysrts.
    2014-09-27 03:39:42.33 spid7s       index restored for master.sysasymkeys.
    2014-09-27 03:39:42.33 spid7s       index restored for master.syssqlguides.
    2014-09-27 03:39:42.44 spid7s       index restored for master.syssoftobjrefs.
    2014-09-27 03:39:42.47 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:42.48 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:42.49 spid7s       index restored for master.spt_values.
    2014-09-27 03:39:42.49 spid7s       index restored for master.MSreplication_options.
    2014-09-27 03:39:42.56 spid7s       index restored for tempdb.syspriorities.
    2014-09-27 03:39:42.56 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:42.57 spid7s       index restored for tempdb.sysowners.
    2014-09-27 03:39:42.57 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:42.57 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:42.57 spid7s       index restored for tempdb.sysschobjs.
    2014-09-27 03:39:42.57 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:42.59 spid7s       index restored for tempdb.syscolpars.
    2014-09-27 03:39:42.60 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:42.60 spid7s       index restored for tempdb.sysnsobjs.
    2014-09-27 03:39:42.60 spid7s       index restored for tempdb.syscerts.
    2014-09-27 03:39:42.60 spid7s       index restored for tempdb.sysxprops.
    2014-09-27 03:39:42.60 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:42.60 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:42.60 spid7s       index restored for tempdb.sysscalartypes.
    2014-09-27 03:39:42.61 spid7s       index restored for tempdb.sysidxstats.
    2014-09-27 03:39:42.61 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:42.61 spid7s       index restored for tempdb.sysclsobjs.
    2014-09-27 03:39:42.61 spid7s       index restored for tempdb.sysremsvcbinds.
    2014-09-27 03:39:42.61 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:42.61 spid7s       index restored for tempdb.sysrts.
    2014-09-27 03:39:42.62 spid7s       index restored for tempdb.sysasymkeys.
    2014-09-27 03:39:42.69 spid7s       index restored for tempdb.syssqlguides.
    2014-09-27 03:39:42.69 spid7s       index restored for tempdb.syssoftobjrefs.
    2014-09-27 03:39:42.75 spid7s       index restored for model.syspriorities.
    2014-09-27 03:39:42.75 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:42.75 spid7s       index restored for model.sysowners.
    2014-09-27 03:39:42.76 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:42.76 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:42.76 spid7s       index restored for model.sysschobjs.
    2014-09-27 03:39:42.76 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:43.00 spid7s       index restored for model.syscolpars.
    2014-09-27 03:39:43.00 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:43.00 spid7s       index restored for model.sysnsobjs.
    2014-09-27 03:39:43.00 spid7s       index restored for model.syscerts.
    2014-09-27 03:39:43.00 spid7s       index restored for model.sysxprops.
    2014-09-27 03:39:43.00 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:43.00 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:43.00 spid7s       index restored for model.sysscalartypes.
    2014-09-27 03:39:43.00 spid7s       index restored for model.sysidxstats.
    2014-09-27 03:39:43.01 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:43.01 spid7s       index restored for model.sysclsobjs.
    2014-09-27 03:39:43.01 spid7s       index restored for model.sysremsvcbinds.
    2014-09-27 03:39:43.01 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:43.01 spid7s       index restored for model.sysrts.
    2014-09-27 03:39:43.01 spid7s       index restored for model.sysasymkeys.
    2014-09-27 03:39:43.01 spid7s       index restored for model.syssqlguides.
    2014-09-27 03:39:43.01 spid7s       index restored for model.syssoftobjrefs.
    2014-09-27 03:39:43.02 spid7s      Starting up database 'msdb'.
    2014-09-27 03:39:43.82 spid7s       index restored for msdb.syspriorities.
    2014-09-27 03:39:43.85 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:43.93 spid7s       index restored for msdb.sysowners.
    2014-09-27 03:39:43.99 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:44.00 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:44.09 spid7s       index restored for msdb.sysschobjs.
    2014-09-27 03:39:44.12 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:44.20 spid7s       index restored for msdb.syscolpars.
    2014-09-27 03:39:44.20 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:44.20 spid7s       index restored for msdb.sysnsobjs.
    2014-09-27 03:39:44.20 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:44.25 spid7s       index restored for msdb.syscerts.
    2014-09-27 03:39:44.25 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:44.26 spid7s       index restored for msdb.sysxprops.
    2014-09-27 03:39:44.26 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:44.26 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:44.27 spid7s       index restored for msdb.sysscalartypes.
    2014-09-27 03:39:44.37 spid7s       index restored for msdb.sysidxstats.
    2014-09-27 03:39:44.41 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:44.42 spid7s       index restored for msdb.sysclsobjs.
    2014-09-27 03:39:44.42 spid7s       index restored for msdb.sysremsvcbinds.
    2014-09-27 03:39:44.42 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:44.42 spid7s       index restored for msdb.sysrts.
    2014-09-27 03:39:44.54 spid7s       index restored for msdb.sysasymkeys.
    2014-09-27 03:39:44.54 spid7s       index restored for msdb.syssqlguides.
    2014-09-27 03:39:44.59 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:44.74 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:44.85 spid7s       index restored for msdb.syssoftobjrefs.
    2014-09-27 03:39:44.89 spid7s       index restored for msdb.syspolicy_policies_internal.
    2014-09-27 03:39:44.90 spid7s       index restored for msdb.sysproxies.
    2014-09-27 03:39:44.90 spid7s       index restored for msdb.syscollector_execution_stats_internal.
    2014-09-27 03:39:44.90 spid7s       index restored for msdb.syssubsystems.
    2014-09-27 03:39:44.91 spid7s       index restored for msdb.log_shipping_primary_secondaries.
    2014-09-27 03:39:44.91 spid7s       index restored for msdb.sysdownloadlist.
    2014-09-27 03:39:44.91 spid7s       index restored for msdb.log_shipping_monitor_primary.
    2014-09-27 03:39:44.92 spid7s       index restored for msdb.sysoriginatingservers.
    2014-09-27 03:39:44.93 spid7s       index restored for msdb.log_shipping_monitor_history_detail.
    2014-09-27 03:39:44.95 spid7s       index restored for msdb.log_shipping_monitor_error_detail.
    2014-09-27 03:39:44.95 spid7s       index restored for msdb.log_shipping_secondary.
    2014-09-27 03:39:44.97 spid7s       index restored for msdb.log_shipping_secondary_databases.
    2014-09-27 03:39:45.10 spid7s       index restored for msdb.log_shipping_monitor_secondary.
    2014-09-27 03:39:45.10 spid7s       index restored for msdb.sysjobs.
    2014-09-27 03:39:45.10 spid7s       index restored for msdb.sysutility_ucp_mi_file_space_health_internal.
    2014-09-27 03:39:45.10 spid7s       index restored for msdb.sysutility_ucp_mi_database_health_internal.
    2014-09-27 03:39:45.10 spid7s       index restored for msdb.syscollector_blobs_internal.
    2014-09-27 03:39:45.11 spid7s       index restored for msdb.sysutility_mi_dac_execution_statistics_internal.
    2014-09-27 03:39:45.11 spid7s       index restored for msdb.sysjobsteps.
    2014-09-27 03:39:45.11 spid7s       index restored for msdb.sysutility_ucp_dac_file_space_health_internal.
    2014-09-27 03:39:45.11 spid7s       index restored for msdb.logmarkhistory.
    2014-09-27 03:39:45.11 spid7s       index restored for msdb.sysutility_mi_session_statistics_internal.
    2014-09-27 03:39:45.12 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:45.12 spid7s       index restored for msdb.sysdtscategories.
    2014-09-27 03:39:45.33 spid7s       index restored for msdb.syspolicy_target_sets_internal.
    2014-09-27 03:39:45.33 spid7s       index restored for msdb.sysutility_ucp_mi_volume_space_health_internal.
    2014-09-27 03:39:45.33 spid7s       index restored for msdb.sysschedules.
    2014-09-27 03:39:45.33 spid7s       index restored for msdb.sysdac_instances_internal.
    2014-09-27 03:39:45.33 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:45.50 spid7s       index restored for msdb.sysssispackages.
    2014-09-27 03:39:45.51 spid7s       index restored for msdb.sysutility_ucp_computer_cpu_health_internal.
    2014-09-27 03:39:45.51 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:45.52 spid7s       index restored for msdb.sysssispackagefolders.
    2014-09-27 03:39:45.52 spid7s       index restored for msdb.sysdac_history_internal.
    2014-09-27 03:39:45.53 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:45.62 spid7s       index restored for msdb.syscategories.
    2014-09-27 03:39:45.62 spid7s       index restored for msdb.systargetservers.
    2014-09-27 03:39:45.62 spid7s       index restored for msdb.systargetservergroups.
    2014-09-27 03:39:45.62 spid7s       index restored for msdb.syspolicy_policy_category_subscriptions_internal.
    2014-09-27 03:39:45.62 spid7s       index restored for msdb.sysalerts.
    2014-09-27 03:39:45.62 spid7s       index restored for msdb.sysoperators.
    2014-09-27 03:39:45.63 spid7s       index restored for msdb.syspolicy_system_health_state_internal.
    2014-09-27 03:39:45.63 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:45.63 spid7s       index restored for msdb.syscollector_config_store_internal.
    2014-09-27 03:39:45.65 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:45.65 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:45.65 spid7s       index restored for msdb.sysmanagement_shared_server_groups_internal.
    2014-09-27 03:39:45.66 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:45.66 spid7s       index restored for msdb.sysutility_mi_smo_properties_to_collect_internal.
    2014-09-27 03:39:45.66 spid7s       index restored for msdb.sysmanagement_shared_registered_servers_internal.
    2014-09-27 03:39:45.66 spid7s       index restored for msdb.syscachedcredentials.
    2014-09-27 03:39:45.79 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:45.79 spid7s       index restored for msdb.syscollector_collection_sets_internal.
    2014-09-27 03:39:45.79 spid7s       index restored for msdb.sysutility_ucp_dac_health_internal.
    2014-09-27 03:39:45.80 spid7s       index restored for msdb.MSdbms.
    2014-09-27 03:39:45.80 spid7s       index restored for msdb.MSdbms_datatype.
    2014-09-27 03:39:45.80 spid7s       index restored for msdb.sysmail_profile.
    2014-09-27 03:39:45.80 spid7s       index restored for msdb.sysutility_ucp_managed_instances_internal.
    2014-09-27 03:39:45.83 spid7s       index restored for msdb.syspolicy_management_facets.
    2014-09-27 03:39:45.84 spid7s       index restored for msdb.sysutility_ucp_mi_health_internal.
    2014-09-27 03:39:45.86 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:45.86 spid7s       index restored for msdb.syscollector_collector_types_internal.
    2014-09-27 03:39:45.86 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:45.86 spid7s       index restored for msdb.syspolicy_configuration_internal.
    2014-09-27 03:39:45.87 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:45.87 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:45.87 spid7s       index restored for msdb.syspolicy_facet_events.
    2014-09-27 03:39:45.87 spid7s       index restored for msdb.sysmail_account.
    2014-09-27 03:39:45.87 spid7s       index restored for msdb.syspolicy_conditions_internal.
    2014-09-27 03:39:45.88 spid7s       index restored for msdb.sysutility_ucp_health_policies_internal.
    2014-09-27 03:39:45.88 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:45.88 spid7s       index restored for msdb.syscollector_collection_items_internal.
    2014-09-27 03:39:45.90 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:46.00 spid7s       index restored for msdb.sysmail_servertype.
    2014-09-27 03:39:46.00 spid7s       index restored for msdb.sysutility_ucp_filegroups_with_policy_violations_internal.
    2014-09-27 03:39:46.02 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:46.03 spid7s       index restored for msdb.sysutility_ucp_policy_check_conditions_internal.
    2014-09-27 03:39:46.03 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:46.03 spid7s       index restored for msdb.sysutility_ucp_configuration_internal.
    2014-09-27 03:39:46.03 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:46.03 spid7s       index restored for msdb.sysutility_ucp_policy_target_conditions_internal.
    2014-09-27 03:39:46.04 spid7s       index restored for msdb.sysmail_server.
    2014-09-27 03:39:46.04 spid7s       index restored for msdb.syspolicy_policy_categories_internal.
    2014-09-27 03:39:46.04 spid7s       index restored for msdb.syspolicy_object_sets_internal.
    2014-09-27 03:39:46.04 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:46.05 spid7s       index restored for msdb.sysmail_configuration.
    2014-09-27 03:39:46.05 spid7s       index restored for msdb.sysdbmaintplan_databases.
    2014-09-27 03:39:46.05 spid7s       index restored for msdb.log_shipping_primary_databases.
    2014-09-27 03:39:46.39 spid7s      The default collation was successfully changed.
    2014-09-27 03:39:46.39 spid7s      Recovery is complete. This is an informational message only. No user action is required.
    2014-09-27 03:39:47.17 spid51      Changed database context to 'master'.
    2014-09-27 03:39:47.18 spid51      Changed language setting to us_english.
    2014-09-27 03:39:47.72 spid51      Setting database option RECOVERY to FULL for database model.
    2014-09-27 03:39:47.84 spid51      Configuration option 'show advanced options' changed from 0 to 1. Run the RECONFIGURE statement to install.
    2014-09-27 03:39:47.84 spid51      FILESTREAM: effective level = 0, configured level = 0, file system access share name = 'MSSQLSERVER'.
    2014-09-27 03:39:47.98 spid51      Configuration option 'default language' changed from 0 to 0. Run the RECONFIGURE statement to install.
    2014-09-27 03:39:47.98 spid51      Configuration option 'default full-text language' changed from 1033 to 1033. Run the RECONFIGURE statement to install.
    2014-09-27 03:39:47.98 spid51      FILESTREAM: effective level = 0, configured level = 0, file system access share name = 'MSSQLSERVER'.
    2014-09-27 03:39:47.98 spid51      Configuration option 'show advanced options' changed from 1 to 0. Run the RECONFIGURE statement to install.
    2014-09-27 03:39:47.98 spid51      FILESTREAM: effective level = 0, configured level = 0, file system access share name = 'MSSQLSERVER'.
    2014-09-27 03:39:48.27 spid51      Error: 15007, Severity: 16, State: 1.
    2014-09-27 03:39:48.27 spid51      '' is not a valid login or you do not have permission.
    2014-09-27 03:51:25.13 Logon       Error: 18456, Severity: 14, State: 8.
    2014-09-27 03:51:25.13 Logon       Login failed for user 'sa'. Reason: Password did not match that for the login provided. [CLIENT: <local machine>]
    2014-09-27 03:51:32.67 Logon       Error: 18456, Severity: 14, State: 8.
    2014-09-27 03:51:32.67 Logon       Login failed for user 'sa'. Reason: Password did not match that for the login provided. [CLIENT: <local machine>]
    2014-09-27 03:51:42.11 Logon       Error: 18456, Severity: 14, State: 5.
    2014-09-27 03:51:42.11 Logon       Login failed for user 'CAGATAY\cagatay (cagatay)'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
    2014-09-27 03:52:42.07 Logon       Error: 18456, Severity: 14, State: 5.
    2014-09-27 03:52:42.07 Logon       Login failed for user 'CAGATAY\cagatay (cagatay)'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
    2014-09-27 03:53:01.23 Logon       Error: 18461, Severity: 14, State: 1.
    2014-09-27 03:53:01.23 Logon       Login failed for user 'CAGATAY\cagatay'. Reason: Server is in single user mode. Only one administrator can connect at this time. [CLIENT: <local machine>]
    2014-09-27 03:53:17.57 Logon       Error: 18456, Severity: 14, State: 8.
    2014-09-27 03:53:17.57 Logon       Login failed for user 'sa'. Reason: Password did not match that for the login provided. [CLIENT: <local machine>]
    2014-09-27 03:53:32.54 Logon       Error: 18456, Severity: 14, State: 5.
    2014-09-27 03:53:32.54 Logon       Login failed for user 'CAGATAY\cagatay (cagatay)'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
    2014-09-27 03:54:04.29 Logon       Error: 18456, Severity: 14, State: 5.
    2014-09-27 03:54:04.29 Logon       Login failed for user 'CAGATAY\cagatay (cagatay)'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
    2014-09-27 03:54:10.36 Logon       Error: 18456, Severity: 14, State: 5.
    2014-09-27 03:54:10.36 Logon       Login failed for user 'CAGATAY\cagatay'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
    2014-09-27 03:54:47.18 Logon       Error: 18456, Severity: 14, State: 8.
    2014-09-27 03:54:47.18 Logon       Login failed for user 'sa'. Reason: Password did not match that for the login provided. [CLIENT: <local machine>]
    Resolve the error, please refer to the following links.
    Enable DAC:http://www.mssqltips.com/sqlservertip/2538/enabling-dedicated-administrator-connection-in-sql-server-2008-express-edition/
    could not register the SPN Kerberos:
    http://saveadba.blogspot.com/2012/03/could-not-register-spn-kerberos.html  
    Make sure the password of sa is correct,and the login 'CAGATAY\cagatay' has been created in SQL Server

  • When I click on Firefox it opens with a box that says "Foxfire is installing your updates and will start in a few moments-. " then it says "Software Update Failed (in blue) with an exclamation mark inside a yellow triangle) The update could not be install

    When I click on Firefox the first time it says "Foxfire is installing your updates and will start in a few moments…. (with a green bar)" then it says "Software Update Failed (in blue) with an exclamation mark inside a yellow triangle)
    The update could not be installed. Please make sure there are no other copies of Firefox running on your computer, and then restart Firefox to try again." When I click the ok, Firefox opens up. If I open another Firefox window with the previous one still running, it doesn't give me any of these messages, it just opens normally.
    == This happened ==
    Every time Firefox opened

    If you can't install on top of the current installation then you need to delete or rename the current Firefox program folder to do a clean install.
    It is possible that your security software is using or locking files, so you can try to temporarily disable that software during the installation.

  • Bought a new iMac 27" yesterday.  Attempting to download Adobe Creative Suite 5 Design Premium. Loaded software from discs. When I check for updates they fail to install. A window comes up saying "Some updates failed to install." Then under each applicati

    I bought a new iMac 27" yesterday, running with Mavericks OS.  Attempting to download Adobe Creative Suite 5 Design Premium. Loaded software from discs. When I check for updates they fail to install. A window comes up saying "Some updates failed to install." Then under each applications it says "There was an error downloading this update. Please quit and try again later." Have done this several times. Suggestions?

    update manually,:  http://www.adobe.com/downloads/updates/

  • Software Update wants to install Pro Apps Update 2008-05...

    I've been running Final Cut Studio 3 on this machine for a long time.  Suddenly Software update wants to install the Pro Applications Update 2008-05. The only thing I can think of that might have caused that is that I dragged over a copy of LiveType from an older PPC G5 that was still running FCS2.  Not sure if I should allow it or not. If I allow it, will it be smart enough to see that I have more recent versions of all of the apps?  Any suggestions?
    Thanks,
    CJ

    Nothing newer will be replaced.

  • HT4623 I am getting a messages saying "Software Update Failed An error occurred downloading iOS 6.1.3" everytime I try and install the update.

    I am getting a messages saying "Software Update Failed An error occurred downloading iOS 6.1.3" everytime I try and install the update. Any suggestions?

    dkmusic89 wrote:
    I am also having same issue. Why Apple people is not replying here with the correct steps to resolve this?
    Because Apple does not participate in these forums. These are user-to-user forums.

Maybe you are looking for

  • PO Accruals and closing Purchasing periods

    Hi, can anybody confirm how many purchasing periods should be open at any one time. We are having a problem with the accruals and I am trying to understand the correct procedure for re-setting the purchasing accruals. I am aware that by closing the p

  • Schedule Background jobs automatically -

    Hello Guys, I have the following requirement. I have a copy program in BPS-SEM(ABAP program). Users have to run the copy program for different combinations like variant:1 costcenetr 100-200 valuetype - 10 user 1 variant:2 costcenetr 400-500 valuetype

  • Info required for any email adapter

    Hi I have a requirement to send email from different applications for different purposes. So instead of using email facility of each individual application, it is designed to use some common service to send & monitor emails. So it is planned to devel

  • Viewing songs in Ipod from ITunes screen

    Hi. I have never had a problem viewing the songs on my Ipod after plugging it in...it just came right up...until now when I updated my iTunes and Ipod from a version 1.1.1 to a 1.3. Now when I try and view what's on my Ipod from my ITunes screen: I c

  • Document types for invoice docements

    Dear Experts, whenever I am printing Invoices and subsequent debit documents  it is showing the heading as Credit Memo . My user wants that when he will print normal invoice it should show Invoice and should show Credit Memo  when he posts subsequent