Lenovo Service Bridge cannot install

Hi, Trying to install the Lenovo Service Bridge app, the installer downloads the application but then returns an error saying "Cannot retrieve application. Authentication failure." and closes on me. Cheers,Callum EDIT: Here is the 'details' it gives me - http://pastebin.com/AKsMpvg3

I ran into another, but different problem when I installed it on July 8, 2015. It wanted to install Adobe AIR to run (can't we keep things simple Lenovo?) and it did so. But then nothing after that. No error. No progress. It installed AIR then acted as if done.
Luckily, running it again worked so I could install the diagnostic Lenovo Service Center (LSC). When re-running LSC, it said my AIR was in need of update. C'mon Lenovo.
Long story short it all worked in the end, if lacking in the beta-tested area.
Sadly, the diagnostic program LSC is useless. It detect my Network port, but not the problem with it.
LSC also gives out "Warnings" but never gives a *%@!%# specific message. My ATI/AMD grapphics chip had a "stress test" (what is that even?) and it said "Warning". Wow, that was informative.
Back to the drawing board Lenovo.

Similar Messages

  • SCS Service Error - Cannot install CE

    hi all,
    I'm trying to install CE on windows and following is the error log.
    Sep 18, 2007 6:19:39 PM [Info  ]: Arg[0]: D:/usr/sap/CE2/SYS/exe/uc/NTI386/sapstartsrv
    Sep 18, 2007 6:19:39 PM [Info  ]: Arg[1]: -q
    Sep 18, 2007 6:19:39 PM [Info  ]: Arg[2]: -r
    Sep 18, 2007 6:19:39 PM [Info  ]: Arg[3]: -s
    Sep 18, 2007 6:19:39 PM [Info  ]: Arg[4]: CE2
    Sep 18, 2007 6:19:39 PM [Info  ]: Arg[5]: -p
    Sep 18, 2007 6:19:39 PM [Info  ]: Arg[6]: D:/usr/sap/CE2/SYS/profile/CE2_SCS01_LOCALHOST
    Sep 18, 2007 6:19:39 PM [Info  ]: Arg[7]: -n
    Sep 18, 2007 6:19:39 PM [Info  ]: Arg[8]: 01
    Sep 18, 2007 6:19:39 PM [Info  ]: Arg[9]: -U
    Sep 18, 2007 6:19:39 PM [Info  ]: Arg[10]: NT AUTHORITY\LocalService
    Sep 18, 2007 6:19:39 PM [Info  ]: Arg[11]: -P
    Sep 18, 2007 6:19:39 PM [Info  ]: Arg[12]: ""
    Sep 18, 2007 6:19:40 PM [Info  ]: Process started. Try to get Streams..
    Sep 18, 2007 6:19:40 PM [Info  ]: Got Streams. Try to read them...
    Sep 18, 2007 6:20:25 PM [Info  ]: Service not started within 40 seconds.
    Sep 18, 2007 6:20:25 PM [Info  ]: Process exited with rc: -1
    Sep 18, 2007 6:20:25 PM [Error ]: excpetion in step:
    Sep 18, 2007 6:20:25 PM [Error ]:      name: CREATE_SCS_SERVICE [com.sap.xpf.controller.TaskExecutionStep]
    Sep 18, 2007 6:20:25 PM [Fatal ]: com.sap.xpf.tasklib.TaskLibraryException: cannot start serice. rc was: -1
           at com.sap.instancemgt.win.SAPServiceCreateDEV.execute(SAPServiceCreateDEV.java:80)
           at com.sap.xpf.tasklib.execution.TaskExecutionObjectJava.execute(TaskExecutionObjectJava.java:54)
           at com.sap.xpf.tasklib.TaskLibraryEngine.executeTask(TaskLibraryEngine.java:256)
           at com.sap.xpf.tasklib.TaskLibraryEngine.executeTask(TaskLibraryEngine.java:264)
           at com.sap.xpf.controller.TaskExecutionStep.execute(TaskExecutionStep.java:115)
           at com.sap.xpf.controller.Controller.execute(Controller.java:506)
           at com.sap.xpf.controller.Controller.start(Controller.java:292)
           at com.sap.inst.engine.customactions.CallController.install(CallController.java:93)
           at com.zerog.ia.installer.actions.CustomAction.installSelf(DashoA8113:-1)
           at com.zerog.ia.installer.Action.install(DashoA8113:-1)
           at com.zerog.ia.installer.Action.install(DashoA8113:-1)
           at com.zerog.ia.installer.GhostDirectory.install(DashoA8113:-1)
           at com.zerog.ia.installer.Installer.install(DashoA8113:-1)
           at com.zerog.ia.installer.actions.InstallProgressAction.m(DashoA8113:-1)
           at com.zerog.ia.installer.actions.ProgressPanelAction$1.run(DashoA8113:-1)
    Sep 18, 2007 6:20:25 PM [Info  ]: End CREATE_SCS_SERVICE [com.sap.xpf.controller.TaskExecutionStep]
    Sep 18, 2007 6:20:25 PM [Info  ]: rc:   1
    Sep 18, 2007 6:20:25 PM [Info  ]: at:   2007.09.18 - 18.20.25[yyyy.MM.dd - HH.mm.ss]
    Sep 18, 2007 6:20:25 PM [Info  ]: duration:   00:00:45[HH:mm:ss]
    Sep 18, 2007 6:20:25 PM [Info  ]:
    Sep 18, 2007 6:20:25 PM [Info  ]: Error during executing
    Sep 18, 2007 6:20:25 PM [Info  ]: End Controller
    Sep 18, 2007 6:20:25 PM [Info  ]:   at          : 2007.09.18 - 18.20.25[yyyy.MM.dd - HH.mm.ss]
    Sep 18, 2007 6:20:25 PM [Info  ]:   durationt   : 00:23:39[HH:mm:ss]
    Sep 18, 2007 6:20:25 PM [Info  ]:   status   : ERROR
    Any help is highly appreciated.
    Thanks.
    Best Regards,
    Shiva

    Hi,
    I solved the problem by making this step as ok in steps.xml as the SCS service is installed successfully but taking more than 40 secs to start.
    --Shiva

  • I am trying to now install a free trial of indesign because despite paying $50+ a month for this supposed service I cannot open an indesign file I've been sent and need to do work on it urgently. I have now signed in again for a free one month trial and i

    i am trying to now install a free trial of indesign because despite paying $50+ a month for this supposed service I cannot open an indesign file I've been sent and need to do work on it urgently. I have now signed in again for a free one month trial and it claims to be downloading but this is not happening at all. I am on a Macbook Air and Abobe for my $600 a year membership you have totally ruined by Friday night. If there's a human being out there at Abode please respond now

    Hi,
    If you have already subscribed to the membership, please follow the help document below:
    https://helpx.adobe.com/creative-suite/kb/trial--1-launch.html
    Regards,
    Sheena

  • Cannot install itunes  I get a message that apple mobile device failed to start..  verify that you have sufficient priveliges to start system services

    cannot install itunes  I get a message that apple mobile device failed to start..  verify that you have sufficient priveliges to start system services

    Hello, Edward. 
    Thank you for visiting Apple Support Communities.
    I think the best option would be to completely uninstall all components of iTunes in the order specified of the article below.  Once this is done attempt to install iTunes again.
    Removing and reinstalling iTunes and other software components for Windows Vista, Windows 7, or Windows 8
    http://support.apple.com/kb/ht1923
    If the issue persists, try the steps in the article below.
    How to restart the Apple Mobile Device Service (AMDS) on Windows
    http://support.apple.com/kb/ts1567
    Cheers,
    Jason H.

  • I cannot install Creative Suite 5.5 on my Windows 7 Professional. I keep getting error message: "Exit Code: 15 - Media DB sync failed". I have disabled UAC and Startup items and Services with no luck. Can you please help?

    I cannot install Creative Suite 5.5 on my Windows 7 Professional. I keep getting error message: "Exit Code: 15 - Media DB sync failed". I have disabled UAC and Startup items and Services with no luck. Can you please help?

    I am sorry Erickkasner but there is no longer direct support provided for Creative Suite 5.5 installation issues.
    You are welcome to post any specific errors you are able to discover within your installation log to this discussion.  Since you are using Windows then Exit Code 15 could mean one of the following:
    Installer database is corrupted
    Update pending to your operating system
    Improper permissions set for the Media.db
    The installation log file should provide additional insight into the exact error you are experiencing.  Please make sure to use the find command to look for the words 'ERROR' and 'FATAL' to locate the relevant error messages.

  • [Forum FAQ] Reporting Service Point cannot be installed on a Site System Server running SQL Server 2012 SP1

    Symptom: When you install Reporting Service Point role on a Site System Server running SQL Server
    2012 SP1, you may encounter an issue that the Reporting Service Point role cannot be installed. The error log “srsrpMSI.log” and “srsrpsetup.log” may throw the error as shown in Figure 1 and Figure 2.
    03:32:03:764]:
    MainEngineThread is returning 1618
    Figure 1: Error -1
    <03/03/14 03:32:03>
    srsrp.msi exited with return code: 1618
    Figure 2: Error -2
    Reason: All the two logs indicate an error return code 1618. From the KB below you may know what
    the return code means.
    ERROR_INSTALL_ALREADY RUNNING 
    1618
    Another installation is already in progress. Complete that installation before proceeding with this install.
    KB link:
    http://support.microsoft.com/kb/290158 “it is related to an Office Suite KB, anyway, the MSI return code is the same meaning”
    You can look into Resource Manager and Event Viewer to find the other currently running MSI installation. You may get a warning in Event Log that means the MSI wants to install a SQL Server
    related Component (Figure 3). The Resource Manager confirms this (Figure 4).
    Event Log:
    Event ID: 1004
    Source: Msinstaller
    Level: Warning
    Detection of product '{A7037EB2-F953-4B12-B843-195F4D988DA1}',
    feature 'SQL_Tools_ANS', component '{0CECE655-2A0F-4593-AF4B-EFC31D622982}' failed.  The resource '' does not exist.
    Figure 3: Event Log
    Figure 4: Resource Manager
    Resolution: the error is exactly what the following KB describes.
    KB Link:
    http://support.microsoft.com/kb/2793634
    After we resolve the SQL Server 2012 issue, the Reporting Service Role is installed successfully.
    Please click to vote if the post helps you. This can be beneficial to other community members reading the thread.

    This implies that ODP.NET does NOT need to be installed on a client. However, I cannot find OraOPs9.dll on a machine with Client Release 9.2 installed. Should OraOps?.dll automatically come with a Client installation of 9.2 or higher?
    ODP.NET needs to be installed on the client. OraOps9.dll is part of ODP.NET, not the Oracle Client.
    Also, if an application is built with the 10g ODP.NET, can it be run from a machine with OraOps9.dll?
    If an application is built with 10g ODP.NET, it can be run with 9.2 ODP.NET as long as you do not use any 10g APIs. The new features in 10g ODP.NET are included in the doc and the ODP.NET FAQ for your reference.

  • Cannot install itunes 7.7 with Vista due to bonjour service issues

    (I do have itunes version 7.6.2.9 working fine with no issues on vista)Cannot install itunes 7.7 becoz vista doesnt let bonjour service to run, While trying to start the Bonjour service from the Windows Services console gives an other error: "Windows could not start the Bonjour service on Local Computer. For more information, review the System Event Log. If this is a non-Microsoft service, contact the service vendor, and refer to service-specific error code -65549." Is there any way I can get Bonjour to install and run as a service? tried switching off windows defender and Norton Internet security along with norton firewall too, still it doesnt let me install ,even tried downloading the windows version of bonjour but it too doesnt get installed as the service cannot start
    Event report:
    - <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
    - <System>
    <Provider Name="MsiInstaller" />
    <EventID Qualifiers="0">1013</EventID>
    <Level>2</Level>
    <Task>0</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2008-07-11T12:32:31.000Z" />
    <EventRecordID>69102</EventRecordID>
    <Channel>Application</Channel>
    <Computer>Revelations</Computer>
    <Security UserID="S-1-5-21-216963075-3724653442-2767649758-1000" />
    </System>
    - <EventData>
    <Data>Product: iTunes -- Service 'Bonjour Service' (Bonjour Service) failed to start. Verify that you have sufficient privileges to start system services.</Data>
    <Data>(NULL)</Data>
    <Data>(NULL)</Data>
    <Data>(NULL)</Data>
    <Data>(NULL)</Data>
    <Data />
    <Data /> <Binary>7B45463643343630302D333036442D344636412D413131392D433241383737443235423 4417D</Binary>
    </EventData>
    </Event>
    The Bonjour Service service terminated with service-specific error 4294901747 (0xFFFEFFF3).
    Any comments and advice would be higly appreciated
    regards
    Message was edited by: Vistacrap
    Message was edited by: Vistacrap
    Message was edited by: Vistacrap
    null

    Apple offer this advice which I guess is not much help to you as you have Norton:
    http://support.apple.com/kb/TS1609?viewlocale=en_US
    I wonder if it is worth looking in the your firewall configuration>>Programs and deleting any entry for Bonjour - in the hope that you will be prompted to allow it or not when you do the install, or maybe adding it back with permit all.
    But someone came up with another possible solution at the end of this thread:
    http://discussions.apple.com/thread.jspa?threadID=1540617&tstart=0

  • I have win xp version 202 service pack 3 had printer laserjet1010 installed but cannot install it an

    i have win xp version 202 service pack 3 had printer laserjet1010 installed but cannot install it again as error message is
    the installation file for this device is missing anecessary entry.this may be because the INF file was written for win95 or later

    helhaj,
    I am sorry, but to get your issue more exposure I would suggest posting it in the commercial forums since this is a commercial printer. You can do this at http://h30499.www3.hp.com/hpeb/ .
    I hope this helps.
    ↙-----------How do I give Kudos?| How do I mark a post as Solved? ----------------↓

  • 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

  • Cannot install latest updates for Bridge and Photoshop CC. Get the following message: Update Failed. The download appears corrupted.  U43M1D207.

    Cannot install latest updates for Bridge and Photoshop CC. I get the following message: "Update Failed. The download appears corrupted.  U43M1D207."
    I have tried to install at different times over three different days with the same result each time. My version of Bridge now no longer shows DNG files except as an icon. The update is supposed to install Camera Raw version 9.

    I had the 204 version of your error using the direct download links proved on this thread solved my problem.. hope you have same success... had to log off/in cloud manager before it showed all apps updated
    https://forums.adobe.com/thread/1825014

  • Cannot install Photoshop or Bridge from CC. Get message 'close bridge.exe', but it is not open.

    Cannot install Photoshop or Bridge from CC. Get message 'close bridge.exe', but it is not open. I have CS5 installed on my PC. Help!

    Terminate the process in task manager.
    Mylenium

  • JavaService - can install java program into win2k service, but cannot run

    i have a JavaService problem: i can install java program into win2k service, but cannot run
    the version of javaservice is 2.0.7.0
    the following is the message:
    C:\DailyUpdate\dist>JavaService.exe -install DailyUpdate C:\Program Files\Java\j
    dk1.5.0_05\jre\bin\client\jvm.dll -Djava.class.path=C:\DailyUpdate\dist\ftpbean.
    jar;C:\DailyUpdate\dist\mysql-connector-java-3.0.10-stable-bin.jar;C:\DailyUpdat
    e\dist\DailyUpdater.jar -Xms16M -Xmx64M -start DailyUpdateHandler -params C:\Dai
    lyUpdate\dist -out C:\DailyUpdate\dist\logs\out.log -err C:\DailyUpdate\dist\lo
    gs\err.log
    The DailyUpdate automatic service was successfully installed
    The DailyUpdate service is starting.
    The DailyUpdate service could not be started.
    The service did not report an error.
    More help is available by typing NET HELPMSG 3534.

    I might be doing some programming for my company soon
    which will require a program to monitor a database
    and whenever there is a change to certain fields, it
    must copy certain fields into another database. When I see "whenever thiere is a change to certain fields" I tend to think "triggers" - but maybe this won't work for you 'cause of the "another database" part. And the fact that triggers are inherently evil.
    [snip]
    Is it possible to run a Java program as a windows
    service? And if so then how would you go about it? I'd hit Google - there're a couple ways to do this.
    [snip]
    Also,...if I were to use one of those programs which
    can make an .exe of a Java program, then do you still
    require the JRE to be on the machine? It depends on how you did the conversion. If you compile to native then no, if you just wrap up a JRE then yes.
    Why I ask is
    that I occasionally get asked to do small development
    projects for my company, but we are a microsoft
    partner and therefore do all the development in C#
    and the like. So I would like to just implement as
    many things in Java as I can, just to show everyone
    that Java can do exactly what C# can do. But its
    difficult to convince people of this since I always
    require the JRE and they dont. Of course, they require the .NET framework and you don't. And last I looked that thing was around 23 Meg.

  • I cannot install ICS update(All the available updates @ Lenovo)

    Hey guys I was using CM7 for a while , then i had frequent reboot problem with the CM7 ROM. Then i tried installing the ICS update version A107I0_A404_001_014_0116_US.zip
    that was available at http://download.lenovo.com/slates/a1/ICS_OTA/ 
    I couldnt install it after 75% of the installation i get a warning sign and the installation is aborted and i am taken to the recovery screen where the below options are available
    Reboo now
    Wipe data
    Factory reset
    Touch calibration.
    I used the below method suggested at xda dev. Remove CWM > Flash stock recovery > Install ICS update > Flash CWM again > Wipe/Factory reset > Reboot.
    But i cannot install the update as stated above. I am stuck at ICS update. Since the install failed i just see the Android boot logo after rebooting . What did i do wrong and why am i unable to install ICS update ?
    I used different updates of CM7 ROMs , i get frequent reboots after a while. Please Help me out . I taut this update would fix all the pre-existing problem.

    i installed ICS 1.2 like you said and it is fully working and i tired installing the update but i am not sure whether i got it to install the update when i click install now it reboots and goes in to the update android logo after few minutes the logo disappears and the tablet is switched off
    I tried to Install CWM by putting in the internal sd card as update.zip and booted into recovery and still i get the same anrdoid logo and now CWM install . I am unable to root the tab using Superoneclick . Rooter zip doesnt work get the same prob as the above
    Please help me out guys

  • Cannot install windows 7 service pack 1 on my HPE-400z desktop

    I have an HP  hpe-400z desktop pc.  It is running windows 7 home premium operating system.   Ever since Windows 7 SP1 came out, my pc has been trying to install it.  Every time it tries to install, during the boot process the install fails and the system reverts back to original settings.  I get the error message E_FAIL  (0x80004005).  I have tried letting the automatic updater install this sp1 and I have also downloaded it, running the update, and then the same thing happens.  I have tried it without my security software running and get the same result.   This has been going on for so long now that I do not even bother to watch my machine boot up,- I know it is going to boot twice due to the failure of installing sp1.  Please help!

    I would suggest you download the Win 7 Readiness Tool (see list of OS versions) located here
    The System Update Readiness Tool can help fix problems that might prevent Windows updates and service packs from installing. For example, an update might not install if a damaged system file prevents the update from recognizing the version of Windows that's running on your computer.
    If your computer is having problems installing an update or a service pack, download and install the tool, which runs automatically. Then, try installing the update or service pack again.
    I am a volunteer. I am not an HP employee.
    To say THANK YOU, press the "thumbs up symbol" to render a KUDO. Please click Accept as Solution, if your problem is solved. You can render both Solution and KUDO.
    The Law of Effect states that positive reinforcement increases the probability of a behavior being repeated. (B.F.Skinner). You toss me KUDO and/or Solution, and I perform better.
    (2) HP DV7t i7 3160QM 2.3Ghz 8GB
    HP m9200t E8400,Win7 Pro 32 bit. 4GB RAM, ASUS 550Ti 2GB, Rosewill 630W. 1T HD SATA 3Gb/s
    Custom Asus P8P67, I7-2600k, 16GB RAM, WIN7 Pro 64bit, EVGA GTX660 2GB, 750W OCZ, 1T HD SATA 6Gb/s
    Custom Asus P8Z77, I7-3770k, 16GB RAM, WIN7 Pro 64bit, EVGA GTX670 2GB, 750W OCZ, 1T HD SATA 6Gb/s
    Both Customs use Rosewill Blackhawk case.
    Printer -- HP OfficeJet Pro 8600 Plus

  • Cannot Install CS5 trial version on Vista 64 bit...been weeks..please help..!

    I've been trying to install the CS5 for a couple of week now but cannot get it to install. I've tried lots of things I've seen in the forums but I still cannot get it to install. I'd appreciate it if someone could offer some help and direction to step me through the possible issues. I've tried uninstalling, using the cs5 cleanup utility, changing permissions on the entire Adobe folder, completely uninstalling any Adobe product, deleting all reference folders, running as administrator, etc etc but nothing works. I've turned off firewall and antivirus, closed all applications including start-up items, and still nothing.
    I'll start again and list my issues and perhaps someone can help..
    This is the error:
    Exit Code: 6
    -------------------------------------- Summary --------------------------------------
    - 0 fatal error(s), 52 error(s), 50 warning(s)
    WARNING: Payload cannot be installed due to dependent operation failure
    WARNING: Payload cannot be installed due to dependent operation failure
    WARNING: Payload cannot be installed due to dependent operation failure
    WARNING: Payload cannot be installed due to dependent operation failure
    WARNING: Payload cannot be installed due to dependent operation failure
    WARNING: Payload cannot be installed due to dependent operation failure
    WARNING: Payload cannot be installed due to dependent operation failure
    WARNING: Payload cannot be installed due to dependent operation failure
    WARNING: Payload cannot be installed due to dependent operation failure
    WARNING: Payload cannot be installed due to dependent operation failure
    WARNING: Payload cannot be installed due to dependent operation failure
    WARNING: Payload cannot be installed due to dependent operation failure
    WARNING: Payload cannot be installed due to dependent operation failure
    WARNING: Payload cannot be installed due to dependent operation failure
    WARNING: Payload cannot be installed due to dependent operation failure
    WARNING: Payload cannot be installed due to dependent operation failure
    WARNING: Payload cannot be installed due to dependent operation failure
    WARNING: Payload cannot be installed due to dependent operation failure
    WARNING: Payload cannot be installed due to dependent operation failure
    WARNING: Payload cannot be installed due to dependent operation failure
    WARNING: Payload cannot be installed due to dependent operation failure
    WARNING: Payload cannot be installed due to dependent operation failure
    WARNING: Payload cannot be installed due to dependent operation failure
    WARNING: Payload cannot be installed due to dependent operation failure
    WARNING: Payload cannot be installed due to dependent operation failure
    WARNING: Payload cannot be installed due to dependent operation failure
    WARNING: Payload cannot be installed due to dependent operation failure
    WARNING: Payload cannot be installed due to dependent operation failure
    WARNING: Payload cannot be installed due to dependent operation failure
    WARNING: Payload cannot be installed due to dependent operation failure
    WARNING: Payload cannot be installed due to dependent operation failure
    WARNING: Payload cannot be installed due to dependent operation failure
    WARNING: Payload cannot be installed due to dependent operation failure
    WARNING: Payload cannot be installed due to dependent operation failure
    WARNING: Payload cannot be installed due to dependent operation failure
    WARNING: Payload cannot be installed due to dependent operation failure
    WARNING: Payload cannot be installed due to dependent operation failure
    WARNING: Payload cannot be installed due to dependent operation failure
    WARNING: Payload cannot be installed due to dependent operation failure
    WARNING: Payload cannot be installed due to dependent operation failure
    WARNING: Payload cannot be installed due to dependent operation failure
    WARNING: Payload cannot be installed due to dependent operation failure
    WARNING: Payload cannot be installed due to dependent operation failure
    WARNING: Payload cannot be installed due to dependent operation failure
    WARNING: Payload cannot be installed due to dependent operation failure
    WARNING: Payload cannot be installed due to dependent operation failure
    WARNING: Payload cannot be installed due to dependent operation failure
    WARNING: Payload cannot be installed due to dependent operation failure
    WARNING: Payload cannot be installed due to dependent operation failure
    WARNING: Payload cannot be installed due to dependent operation failure
    ERROR: The following payload errors were found during install:
    ERROR:  - Adobe CSXS Infrastructure CS5: Install failed
    ERROR:  - Microsoft_VC90_ATL_x86: Install failed
    ERROR:  - Adobe Media Player: Install failed
    ERROR:  - Adobe Linguistics CS5 x64: Install failed
    ERROR:  - Microsoft_VC90_CRT_x86: Install failed
    ERROR:  - Adobe Photoshop CS5 Support: Install failed
    ERROR:  - Adobe Bridge CS5: Install failed
    ERROR:  - Recommended Common Fonts Installation x64: Install failed
    ERROR:  - AdobePDFL x64 CS5: Install failed
    ERROR:  - DeviceCentral_DeviceCentral3LP-en_GB: Install failed
    ERROR:  - Microsoft_VC80_MFCLOC_x86_x64: Install failed
    ERROR:  - Adobe XMP Panels CS5: Install failed
    ERROR:  - Photoshop Camera Raw: Install failed
    ERROR:  - AdobeColorCommonSetCMYK: Install failed
    ERROR:  - Adobe Mini Bridge CS5: Install failed
    ERROR:  - Microsoft_VC80_CRT_x86_x64: Install failed
    ERROR:  - AdobeColorJA CS5: Install failed
    ERROR:  - Adobe ReviewPanel CS5: Install failed
    ERROR:  - Photoshop Camera Raw (64 bit): Install failed
    ERROR:  - Microsoft_VC90_MFC_x86: Install failed
    ERROR:  - Adobe Photoshop CS5 Core_x64: Failed due to Language Pack installation failure
    ERROR:  - Suite Shared Configuration CS5: Install failed
    ERROR:  - PDF Settings CS5: Install failed
    ERROR:  - DeviceCentral: Failed due to Language Pack installation failure
    ERROR:  - AdobeTypeSupport CS5: Install failed
    ERROR:  - AdobeColorVideoProfilesCS CS5: Install failed
    ERROR:  - AdobeColorCommonSetRGB: Install failed
    ERROR:  - Adobe Player for Embedding x64: Install failed
    ERROR:  - Required Common Fonts Installation x64: Install failed
    ERROR:  - Microsoft_VC90_ATL_x86_x64: Install failed
    ERROR:  - Adobe CSXS Extensions CS5: Install failed
    ERROR:  - Microsoft_VC80_ATL_x86_x64: Install failed
    ERROR:  - AdobeOutputModule: Install failed
    ERROR:  - Microsoft_VC80_CRT_x86: Install failed
    ERROR:  - AdobeCMaps x64 CS5: Install failed
    ERROR:  - AdobeTypeSupport x64 CS5: Install failed
    ERROR:  - Microsoft_VC90_MFC_x86_x64: Install failed
    ERROR:  - Adobe Photoshop CS5 International English Language Pack_x64_AdobePhotoshop12-en_GB_x64: Install failed
    ERROR:  - Adobe WinSoft Linguistics Plugin CS5 x64: Install failed
    ERROR:  - AdobeColorEU CS5: Install failed
    ERROR:  - AdobePDFL CS5: Install failed
    ERROR:  - AdobeCMaps CS5: Install failed
    ERROR:  - AdobeColorNA CS5: Install failed
    ERROR:  - Microsoft_VC80_MFC_x86_x64: Install failed
    ERROR:  - Adobe SwitchBoard 2.0: Install failed
    ERROR:  - Microsoft_VC80_MFC_x86: Install failed
    ERROR:  - AdobeColorPhotoshop CS5: Install failed
    ERROR:  - Microsoft_VC80_MFCLOC_x86: Install failed
    ERROR:  - Adobe Extension Manager CS5: Install failed
    ERROR:  - Adobe ExtendScript Toolkit CS5: Install failed
    ERROR:  - Adobe AIR: Install failed
    Can anyone help please..?

    Try this microsoft solution, it worked for me on Vista with SP2, 32 bit. Even though you have a 64bit system, I think this solution might well work.  I spent 9 days with Adobe trying to install $1,700 software, and still they haven't given me a solution.  Opened Microsoft tech support case today, and everything is now installed, CS5 and Acrobat 9 professional.  Installed Acrobat 9 the same was as CS5, and installed it using the new Admintrator account.
    Here is a summary from Microsoft of what the did to fix the issue:  Good luck!
    Subject: SRX1134614654ID - Unable to install Adobe CS5\Exit Code 7
    It was my pleasure to work with you on your Windows Support Request 1134614654.
    I am glad to hear that the issue is resolved. We appreciate your time and patience in going through the troubleshooting steps performed.
    The following is the summary of the troubleshooting steps performed that resolved the issue.
    ACTION: Tried to install Adobe CS5.
    RESULT: Unable to install Adobe CS5 getting error Exit Code 7.
    CAUSE: Conflict with Administrator rights.
    RESOLUTION: Enabled Default Admin Account and  able to install Adobe CS5 and Acrobat Reader in default admin account.
    Steps to enable Default Administrator Account:
    1.       First you’ll need to open a command prompt in administrator mode by right-clicking and choosing “Run as administrator” (or use the Ctrl+Shift+Enter shortcut from the search box).
    2.       Now type the following command:
    net user administrator /active:yes
    3.       You should see a message that the command completed successfully. Log out, and you’ll now see the Administrator account as a choice.
    Steps to disable Default Administrator Account:
    1.       Make sure you are logged on as your regular user account, and then open an administrator mode command prompt as above. Type the following command: net user administrator /active:no
    2.       The administrator account will now be disabled, and shouldn’t show up on the login screen anymore.
    For future support please go through the support options:
    Support Options:
    Chat Support: http://support.microsoft.com/oas/default.aspx?ln=en-us&prid=11274&gprid=500921
    Phone Support:  1-800-936-5700
    Support working hours:
    Monday - Friday: 5:00 A.M. - 9:00 P.M. PST
    Saturday - Sunday: 6:00 A.M. - 3:00 P.M. PST
    Microsoft recommends installing:” Microsoft Essentials”- provides real-time protection for your home PC that guards against viruses, spyware, and other malicious software.
    http://www.microsoft.com/Security_Essentials/
    Our goal is to make sure you are happy with Microsoft Products, Support & Services.  If the issue reoccurs or there is any questions regarding this issue, please reply to this email with a brief note. It would also be helpful if you can provide your convenient date and time for us to contact you.

Maybe you are looking for