Cannot edit GPO server 2008

Dear All
I use windows server 2008 in branch have active directory join to Primary domain in data-center domain.co.cc
 i need to edit group on the this server but show error
Please help to advise
Run command dcdiag /fix
[QUOTE]Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Windows\system32>dcdiag /fix
Directory Server Diagnosis
Performing initial setup:
Trying to find home server...
Home Server = aaa-CM-DC
* Identified AD Forest.
Done gathering initial info.
Doing initial required tests
Testing server: CHIANGMAI\aaa-CM-DC
Starting test: Connectivity
......................... aaa-CM-DC passed test Connectivity
Doing primary tests
Testing server: CHIANGMAI\aaa-CM-DC
Starting test: Advertising
......................... aaa-CM-DC passed test Advertising
Starting test: FrsEvent
There are warning or error events within the last 24 hours after the
SYSVOL has been shared. Failing SYSVOL replication problems may cause
Group Policy problems.
......................... aaa-CM-DC failed test FrsEvent
Starting test: DFSREvent
......................... aaa-CM-DC passed test DFSREvent
Starting test: SysVolCheck
......................... aaa-CM-DC passed test SysVolCheck
Starting test: KccEvent
......................... aaa-CM-DC passed test KccEvent
Starting test: KnowsOfRoleHolders
......................... aaa-CM-DC passed test KnowsOfRoleHolders
Starting test: MachineAccount
......................... aaa-CM-DC passed test MachineAccount
Starting test: NCSecDesc
......................... aaa-CM-DC passed test NCSecDesc
Starting test: NetLogons
......................... aaa-CM-DC passed test NetLogons
Starting test: ObjectsReplicated
......................... aaa-CM-DC passed test ObjectsReplicated
Starting test: Replications
......................... aaa-CM-DC passed test Replications
Starting test: RidManager
......................... aaa-CM-DC passed test RidManager
Starting test: Services
......................... aaa-CM-DC passed test Services
Starting test: SystemLog
An error event occurred. EventID: 0x00000422
Time Generated: 11/19/2014 11:05:09
Event String:
The processing of Group Policy failed. Windows attempted to read the
file \\domain.co.cc\SysVol\domain.co.cc\Policies\{B6AEC142-9EBB-417C-8080-A6E4713790D
9}\gpt.ini from a domain controller and was not successful. Group Policy setting
s may not be applied until this event is resolved. This issue may be transient a
nd could be caused by one or more of the following:
An error event occurred. EventID: 0x00000422
Time Generated: 11/19/2014 11:10:10
Event String:
The processing of Group Policy failed. Windows attempted to read the
file \\domain.co.cc\SysVol\domain.co.cc\Policies\{B6AEC142-9EBB-417C-8080-A6E4713790D
9}\gpt.ini from a domain controller and was not successful. Group Policy setting
s may not be applied until this event is resolved. This issue may be transient a
nd could be caused by one or more of the following:
A warning event occurred. EventID: 0x00000427
Time Generated: 11/19/2014 11:14:30
Event String:
There are no IP addresses available for lease in the scope or supers
cope "DHCP-CM".
A warning event occurred. EventID: 0x000003FC
Time Generated: 11/19/2014 11:14:48
Event String:
Scope, 192.168.10.0, is 100 percent full with only 0 IP addresses re
maining.
An error event occurred. EventID: 0x00000422
Time Generated: 11/19/2014 11:15:10
Event String:
The processing of Group Policy failed. Windows attempted to read the
file \\domain.co.cc\SysVol\domain.co.cc\Policies\{B6AEC142-9EBB-417C-8080-A6E4713790D
9}\gpt.ini from a domain controller and was not successful. Group Policy setting
s may not be applied until this event is resolved. This issue may be transient a
nd could be caused by one or more of the following:
An error event occurred. EventID: 0x00000422
Time Generated: 11/19/2014 11:20:11
Event String:
The processing of Group Policy failed. Windows attempted to read the
file \\domain.co.cc\SysVol\domain.co.cc\Policies\{B6AEC142-9EBB-417C-8080-A6E4713790D
9}\gpt.ini from a domain controller and was not successful. Group Policy setting
s may not be applied until this event is resolved. This issue may be transient a
nd could be caused by one or more of the following:
An error event occurred. EventID: 0x00000422
Time Generated: 11/19/2014 11:25:11
Event String:
The processing of Group Policy failed. Windows attempted to read the
file \\domain.co.cc\SysVol\domain.co.cc\Policies\{B6AEC 142-9EBB-417C-8080-A6E4713790D
9}\gpt.ini from a domain controller and was not successful. Group Policy setting
s may not be applied until this event is resolved. This issue may be transient a
nd could be caused by one or more of the following:
An error event occurred. EventID: 0x00000422
Time Generated: 11/19/2014 11:30:12
Event String:
The processing of Group Policy failed. Windows attempted to read the
file \\domain.co.cc\SysVol\domain.co.cc\Policies\{B6AEC 142-9EBB-417C-8080-A6E4713790D
9}\gpt.ini from a domain controller and was not successful. Group Policy setting
s may not be applied until this event is resolved. This issue may be transient a
nd could be caused by one or more of the following:
An error event occurred. EventID: 0xC00A0038
Time Generated: 11/19/2014 11:32:53
Event String:
The Terminal Server security layer detected an error in the protocol
stream and has disconnected the client. Client IP: 192.168.0.212.
A warning event occurred. EventID: 0x000003FC
Time Generated: 11/19/2014 11:34:49
Event String:
Scope, 192.168.10.0, is 100 percent full with only 0 IP addresses re
maining.
A warning event occurred. EventID: 0x000003FC
Time Generated: 11/19/2014 11:34:49
Event String:
Scope, 192.168.10.0, is 100 percent full with only 0 IP addresses re
maining.
An error event occurred. EventID: 0x00000422
Time Generated: 11/19/2014 11:35:13
Event String:
The processing of Group Policy failed. Windows attempted to read the
file \\domain.co.cc\SysVol\domain.co.cc\Policies\{B6AEC 142-9EBB-417C-8080-A6E4713790D
9}\gpt.ini from a domain controller and was not successful. Group Policy setting
s may not be applied until this event is resolved. This issue may be transient a
nd could be caused by one or more of the following:
An error event occurred. EventID: 0x00000422
Time Generated: 11/19/2014 11:40:13
Event String:
The processing of Group Policy failed. Windows attempted to read the
file \\domain.co.cc\SysVol\domain.co.cc\Policies\{B6AEC 142-9EBB-417C-8080-A6E4713790D
9}\gpt.ini from a domain controller and was not successful. Group Policy setting
s may not be applied until this event is resolved. This issue may be transient a
nd could be caused by one or more of the following:
An error event occurred. EventID: 0x00000422
Time Generated: 11/19/2014 11:45:14
Event String:
The processing of Group Policy failed. Windows attempted to read the
file \\domain.co.cc\SysVol\domain.co.cc\Policies\{B6AEC 142-9EBB-417C-8080-A6E4713790D
9}\gpt.ini from a domain controller and was not successful. Group Policy setting
s may not be applied until this event is resolved. This issue may be transient a
nd could be caused by one or more of the following:
An error event occurred. EventID: 0x00000457
Time Generated: 11/19/2014 11:45:19
Event String:
Driver RICOH Aficio MP C4502 PCL 5c required for printer RICOH Afici
o MP C4502 PCL 5c is unknown. Contact the administrator to install the driver be
fore you log in again.
An error event occurred. EventID: 0x00000457
Time Generated: 11/19/2014 11:45:22
Event String:
Driver Send To Microsoft OneNote 2010 Driver required for printer Se
nd To OneNote 2010 is unknown. Contact the administrator to install the driver b
efore you log in again.
An error event occurred. EventID: 0x00000457
Time Generated: 11/19/2014 11:45:23
Event String:
Driver Microsoft XPS Document Writer v4 required for printer Microso
ft XPS Document Writer is unknown. Contact the administrator to install the driv
er before you log in again.
An error event occurred. EventID: 0x00000457
Time Generated: 11/19/2014 11:45:23
Event String:
Driver SnagIt 8 Printer required for printer SnagIt 8 is unknown. Co
ntact the administrator to install the driver before you log in again.
An error event occurred. EventID: 0x00000457
Time Generated: 11/19/2014 11:45:24
Event String:
Driver WebEx Document Loader required for printer WebEx Document Loa
der is unknown. Contact the administrator to install the driver before you log i
n again.
An error event occurred. EventID: 0x00000422
Time Generated: 11/19/2014 11:50:17
Event String:
The processing of Group Policy failed. Windows attempted to read the
file \\domain.co.cc\SysVol\domain.co.cc\Policies\{B6AEC 142-9EBB-417C-8080-A6E4713790D
9}\gpt.ini from a domain controller and was not successful. Group Policy setting
s may not be applied until this event is resolved. This issue may be transient a
nd could be caused by one or more of the following:
An error event occurred. EventID: 0x00000422
Time Generated: 11/19/2014 11:55:17
Event String:
The processing of Group Policy failed. Windows attempted to read the
file \\domain.co.cc\SysVol\domain.co.cc\Policies\{B6AEC 142-9EBB-417C-8080-A6E4713790D
9}\gpt.ini from a domain controller and was not successful. Group Policy setting
s may not be applied until this event is resolved. This issue may be transient a
nd could be caused by one or more of the following:
An error event occurred. EventID: 0x00000457
Time Generated: 11/19/2014 11:58:36
Event String:
Driver RICOH Aficio MP C4502 PCL 5c required for printer RICOH Afici
o MP C4502 PCL 5c is unknown. Contact the administrator to install the driver before you log in again.
An error event occurred. EventID: 0x00000457
Time Generated: 11/19/2014 11:58:39
Event String:
Driver Microsoft XPS Document Writer v4 required for printer Microso
ft XPS Document Writer is unknown. Contact the administrator to install the driv
er before you log in again.
An error event occurred. EventID: 0x00000457
Time Generated: 11/19/2014 11:58:40
Event String:
Driver WebEx Document Loader required for printer WebEx Document Loa
der is unknown. Contact the administrator to install the driver before you log i
n again.
An error event occurred. EventID: 0x00000457
Time Generated: 11/19/2014 11:58:41
Event String:
Driver Send To Microsoft OneNote 2010 Driver required for printer Se
nd To OneNote 2010 is unknown. Contact the administrator to install the driver b
efore you log in again.
An error event occurred. EventID: 0x00000457
Time Generated: 11/19/2014 11:58:42
Event String:
Driver SnagIt 8 Printer required for printer SnagIt 8 is unknown. Co
ntact the administrator to install the driver before you log in again.
An error event occurred. EventID: 0x00000422
Time Generated: 11/19/2014 12:00:18
Event String:
The processing of Group Policy failed. Windows attempted to read the
file \\domain.co.cc\SysVol\domain.co.cc\Policies\{B6AEC 142-9EBB-417C-8080-A6E4713790D
9}\gpt.ini from a domain controller and was not successful. Group Policy setting
s may not be applied until this event is resolved. This issue may be transient a
nd could be caused by one or more of the following:
......................... aaa-CM-DC failed test SystemLog
Starting test: VerifyReferences
......................... aaa-CM-DC passed test VerifyReferences
Running partition tests on : DomainDnsZones
Starting test: CheckSDRefDom
......................... DomainDnsZones passed test CheckSDRefDom
Starting test: CrossRefValidation
......................... DomainDnsZones passed test
CrossRefValidation
Running partition tests on : ForestDnsZones
Starting test: CheckSDRefDom
......................... ForestDnsZones passed test CheckSDRefDom
Starting test: CrossRefValidation
......................... ForestDnsZones passed test
CrossRefValidation
Running partition tests on : Schema
Starting test: CheckSDRefDom
......................... Schema passed test CheckSDRefDom
Starting test: CrossRefValidation
......................... Schema passed test CrossRefValidation
Running partition tests on : Configuration
Starting test: CheckSDRefDom
......................... Configuration passed test CheckSDRefDom
Starting test: CrossRefValidation
......................... Configuration passed test CrossRefValidation
Running partition tests on : aaa
Starting test: CheckSDRefDom
......................... aaa passed test CheckSDRefDom
Starting test: CrossRefValidation
......................... aaa passed test CrossRefValidation
Running enterprise tests on : domain.co.cc
Starting test: LocatorCheck
......................... domain.co.cc passed test LocatorCheck
Starting test: Intersite
......................... domain.co.cc passed test Intersite

I do follow with step below as link http://support.microsoft.com/kb/290762, It's work fine
Note You can configure the FRS logs to record detailed debugging entries. For more information about how to configure FRS logging, click the following article number to view the article in the Microsoft Knowledge Base:
221111 Description of FRS entries in the registry
To perform a nonauthoritative restore, stop the FRS service, configure the
BurFlags
registry key, and then restart the FRS service. To do so:
Click Start, and then click Run.
In the Open box, type cmd and then press ENTER.
In the Command box, type net stop ntfrs.
Click Start, and then click Run.
In the Open box, type regedit and then press ENTER.
Locate the following subkey in the registry:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\NtFrs\Parameters\Backup/Restore\Process at Startup
In the right pane, double-click BurFlags.
In the Edit DWORD Value dialog box, type D2 and then click
OK.
Quit Registry Editor, and then switch to the Command box.
In the Command box, type net start ntfrs.
Quit the Command box.
When the FRS service restarts, the following actions occur:
The value for BurFlags registry key returns to 0.
Files in the reinitialized FRS folders are moved to a <var>Pre-existing</var> folder.
An event 13565 is logged to signal that a nonauthoritative restore is started.
The FRS database is rebuilt.
The member performs an initial join of the replica set from an upstream partner or from the computer that is specified in the Replica Set Parent registry key if a parent has been specified for SYSVOL replica sets.
The reinitialized computer runs a full replication of the affected replica sets when the relevant replication schedule begins.
When the process is complete, an event 13516 is logged to signal that FRS is operational. If the event is not logged, there is a problem with the FRS configuration.

Similar Messages

  • 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 find SQL Server 2008 instance

    I have installed SQL server 2008 Developer edition on my laptop. When I open SSMS I cannot find the installed instance under the Server Name group and When I choose the Browse More option and go to Database engine, the instance name does not show up. Will
    appreciate any suggestions.
    Thanks
    akoranteng

    >>I see two instances of SQL Server 2008 when i issue the commands you suggested to me
    I don't why you have two instances, may be you installed two different instances.
    I think local servers list is obtained by reading the registry key
    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server \Instance Names\SQL
    Sometimes (don't know why may it is SQL browser service or something else messed up) you don't see a locally installed instance on the drop down list. Just
    type in the instance name manually inside the textbox for server name and you should be able to connect

  • Cannot install SQL Server 2008 R2 on Widows 7 Pro

    I've tried unsuccesfully to install SQL Server 2008 R2 on my laptop running Windows 7 Pro.
    I previously installed Visual Studio 2010 and downloaded the SQL Server 2008 R2 disk image, burned the disk and then tried to install SQL Server.
    I get a "Microsoft .NET Framework" unhandled exception dialog box with the following detail message:
    See the end of this message for details on invoking
    just-in-time (JIT) debugging instead of this dialog box.
    ************** Exception Text **************
    System.Configuration.ConfigurationErrorsException: An error occurred creating the configuration section handler for userSettings/Microsoft.SqlServer.Configuration.LandingPage.Properties.Settings: Could not load file or assembly 'System, Version=4.0.0.0, Culture=neutral,
    PublicKeyToken=b77a5c561934e089' or one of its dependencies. The system cannot find the file specified. (C:\Users\Louis\AppData\Local\Microsoft_Corporation\LandingPage.exe_StrongName_ryspccglaxmt4nhllj5z3thycltsvyyx\10.0.0.0\user.config line 5) ---> System.IO.FileNotFoundException:
    Could not load file or assembly 'System, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089' or one of its dependencies. The system cannot find the file specified.
    File name: 'System, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089'
       at System.Configuration.TypeUtil.GetTypeWithReflectionPermission(IInternalConfigHost host, String typeString, Boolean throwOnError)
       at System.Configuration.RuntimeConfigurationRecord.RuntimeConfigurationFactory.Init(RuntimeConfigurationRecord configRecord, FactoryRecord factoryRecord)
       at System.Configuration.RuntimeConfigurationRecord.RuntimeConfigurationFactory.InitWithRestrictedPermissions(RuntimeConfigurationRecord configRecord, FactoryRecord factoryRecord)
       at System.Configuration.RuntimeConfigurationRecord.RuntimeConfigurationFactory..ctor(RuntimeConfigurationRecord configRecord, FactoryRecord factoryRecord)
       at System.Configuration.RuntimeConfigurationRecord.CreateSectionFactory(FactoryRecord factoryRecord)
       at System.Configuration.BaseConfigurationRecord.FindAndEnsureFactoryRecord(String configKey, Boolean& isRootDeclaredHere)
    WRN: Assembly binding logging is turned OFF.
    To enable assembly bind failure logging, set the registry value [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1.
    Note: There is some performance penalty associated with assembly bind failure logging.
    To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fusion!EnableLog].
       --- End of inner exception stack trace ---
       at System.Configuration.BaseConfigurationRecord.FindAndEnsureFactoryRecord(String configKey, Boolean& isRootDeclaredHere)
       at System.Configuration.BaseConfigurationRecord.GetSectionRecursive(String configKey, Boolean getLkg, Boolean checkPermission, Boolean getRuntimeObject, Boolean requestIsHere, Object& result, Object& resultRuntimeObject)
       at System.Configuration.BaseConfigurationRecord.GetSection(String configKey, Boolean getLkg, Boolean checkPermission)
       at System.Configuration.BaseConfigurationRecord.GetSection(String configKey)
       at System.Configuration.ClientConfigurationSystem.System.Configuration.Internal.IInternalConfigSystem.GetSection(String sectionName)
       at System.Configuration.ConfigurationManager.GetSection(String sectionName)
       at System.Configuration.ClientSettingsStore.ReadSettings(String sectionName, Boolean isUserScoped)
       at System.Configuration.LocalFileSettingsProvider.GetPropertyValues(SettingsContext context, SettingsPropertyCollection properties)
       at System.Configuration.SettingsBase.GetPropertiesFromProvider(SettingsProvider provider)
       at System.Configuration.SettingsBase.GetPropertyValueByName(String propertyName)
       at System.Configuration.SettingsBase.get_Item(String propertyName)
       at System.Configuration.ApplicationSettingsBase.GetPropertyValue(String propertyName)
       at System.Configuration.ApplicationSettingsBase.get_Item(String propertyName)
       at Microsoft.SqlServer.Configuration.LandingPage.Properties.Settings.get_WindowPlacement()
       at Microsoft.SqlServer.Configuration.LandingPage.LandingPageForm.OnLoad(EventArgs e)
       at System.Windows.Forms.Form.OnCreateControl()
       at System.Windows.Forms.Control.CreateControl(Boolean fIgnoreVisible)
       at System.Windows.Forms.Control.CreateControl()
       at System.Windows.Forms.Control.WmShowWindow(Message& m)
       at System.Windows.Forms.Control.WndProc(Message& m)
       at System.Windows.Forms.ScrollableControl.WndProc(Message& m)
       at System.Windows.Forms.ContainerControl.WndProc(Message& m)
       at System.Windows.Forms.Form.WmShowWindow(Message& m)
       at System.Windows.Forms.Form.WndProc(Message& m)
       at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
       at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
       at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
    ************** Loaded Assemblies **************
    mscorlib
        Assembly Version: 2.0.0.0
        Win32 Version: 2.0.50727.4952 (win7RTMGDR.050727-4900)
        CodeBase:
    file:///C:/Windows/Microsoft.NET/Framework/v2.0.50727/mscorlib.dll
    LandingPage
        Assembly Version: 10.0.0.0
        Win32 Version: 10.50.1600.1 ((KJ_RTM).100402-1540 )
        CodeBase: file:///E:/x86/LandingPage.exe
    System.Windows.Forms
        Assembly Version: 2.0.0.0
        Win32 Version: 2.0.50727.4927 (NetFXspW7.050727-4900)
        CodeBase:
    file:///C:/Windows/assembly/GAC_MSIL/System.Windows.Forms/2.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
    System
        Assembly Version: 2.0.0.0
        Win32 Version: 2.0.50727.4927 (NetFXspW7.050727-4900)
        CodeBase:
    file:///C:/Windows/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
    System.Drawing
        Assembly Version: 2.0.0.0
        Win32 Version: 2.0.50727.4927 (NetFXspW7.050727-4900)
        CodeBase:
    file:///C:/Windows/assembly/GAC_MSIL/System.Drawing/2.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
    Microsoft.SqlServer.Configuration.Sco
        Assembly Version: 10.0.0.0
        Win32 Version: 10.50.1600.1 ((KJ_RTM).100402-1540 )
        CodeBase:
    file:///E:/x86/Microsoft.SqlServer.Configuration.Sco.DLL
    Microsoft.SqlServer.Chainer.Infrastructure
        Assembly Version: 10.0.0.0
        Win32 Version: 10.50.1600.1 ((KJ_RTM).100402-1540 )
        CodeBase:
    file:///E:/x86/Microsoft.SqlServer.Chainer.Infrastructure.DLL
    System.Xml
        Assembly Version: 2.0.0.0
        Win32 Version: 2.0.50727.4927 (NetFXspW7.050727-4900)
        CodeBase:
    file:///C:/Windows/assembly/GAC_MSIL/System.Xml/2.0.0.0__b77a5c561934e089/System.Xml.dll
    Accessibility
        Assembly Version: 2.0.0.0
        Win32 Version: 2.0.50727.4927 (NetFXspW7.050727-4900)
        CodeBase:
    file:///C:/Windows/assembly/GAC_MSIL/Accessibility/2.0.0.0__b03f5f7f11d50a3a/Accessibility.dll
    Microsoft.SqlServer.Management.Controls
        Assembly Version: 10.0.0.0
        Win32 Version: 10.50.1600.1 ((KJ_RTM).100402-1540 )
        CodeBase:
    file:///E:/x86/Microsoft.SqlServer.Management.Controls.DLL
    System.Configuration
        Assembly Version: 2.0.0.0
        Win32 Version: 2.0.50727.4927 (NetFXspW7.050727-4900)
        CodeBase:
    file:///C:/Windows/assembly/GAC_MSIL/System.Configuration/2.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll
    ************** JIT Debugging **************
    To enable just-in-time (JIT) debugging, the .config file for this
    application or computer (machine.config) must have the
    jitDebugging value set in the system.windows.forms section.
    The application must also be compiled with debugging
    enabled.
    For example:
    <configuration>
        <system.windows.forms jitDebugging="true" />
    </configuration>
    When JIT debugging is enabled, any unhandled exception
    will be sent to the JIT debugger registered on the computer
    rather than be handled by this dialog box.
    ////  End of message.
    I have all the updates on my laptop per Microsoft Update.
    Any ideas what is wrong?

    Hello,
    Please try the solution posted in the following thread:
    http://social.msdn.microsoft.com/Forums/en/sqlkjsetupandupgrade/thread/35356bf2-6db7-4785-a104-bc62d18913f7
    Hope this helps.
    Regards,
    Alberto Morillo
    SQLCoffee.com

  • Cannot install SQL Server 2008 R2 Developer on Windows 8.1

    I am unable to install SQL Server 2008 R2 Developer edition on Windows 8.1 Enterprise evaluation and about 3/4 of the way through the installation I get this error msg:
    TITLE: SQL Server 2008 R2 Setup
    The following error has occurred:
    Attempted to perform an unauthorized operation.
    Click 'Retry' to retry the failed action, or click 'Cancel' to cancel this action and continue setup.
    For help, click: http://go.microsoft.com/fwlink?LinkID=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=10.50.4000.0&EvtType=0x88792597%25400xBB814387
    This is my log file:
    Overall summary:
    Final result: User cancelled
    Exit code (Decimal): 0
    Exit message: User cancelled
    Start time: 2014-04-23 23:49:10
    End time: 2014-04-24 00:03:44
    Requested action: Install
    Machine Properties:
    Machine name: PC
    Machine processor count: 2
    OS version: Future Windows Version
    OS service pack:
    OS region: United States
    OS language: English (United States)
    OS architecture: x64
    Process architecture: 64 Bit
    OS clustered: No
    Product features discovered:
    Product Instance Instance ID Feature Language Edition Version Clustered
    Package properties:
    Description: SQL Server Database Services 2008 R2
    ProductName: SQL Server 2008 R2
    Type: RTM
    Version: 10
    SPLevel: 1
    Installation location: F:\My Files\My Downloads\EXISTING\SQLServer2008R2Dev\SQLFULL_ENU\x64\setup\
    Installation edition: DEVELOPER
    User Input Settings:
    ACTION: Install
    ADDCURRENTUSERASSQLADMIN: False
    AGTSVCACCOUNT: NT AUTHORITY\SYSTEM
    AGTSVCPASSWORD: *****
    AGTSVCSTARTUPTYPE: Manual
    ASBACKUPDIR: C:\Program Files\Microsoft SQL Server\MSAS10_50.MSSQLSERVER\OLAP\Backup
    ASCOLLATION: Latin1_General_CI_AS
    ASCONFIGDIR: C:\Program Files\Microsoft SQL Server\MSAS10_50.MSSQLSERVER\OLAP\Config
    ASDATADIR: C:\Program Files\Microsoft SQL Server\MSAS10_50.MSSQLSERVER\OLAP\Data
    ASDOMAINGROUP: <empty>
    ASLOGDIR: C:\Program Files\Microsoft SQL Server\MSAS10_50.MSSQLSERVER\OLAP\Log
    ASPROVIDERMSOLAP: 1
    ASSVCACCOUNT: NT AUTHORITY\SYSTEM
    ASSVCPASSWORD: *****
    ASSVCSTARTUPTYPE: Automatic
    ASSYSADMINACCOUNTS: PC\computername
    ASTEMPDIR: C:\Program Files\Microsoft SQL Server\MSAS10_50.MSSQLSERVER\OLAP\Temp
    BROWSERSVCSTARTUPTYPE: Disabled
    CONFIGURATIONFILE: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20140423_234604\ConfigurationFile.ini
    CUSOURCE:
    ENABLERANU: False
    ENU: True
    ERRORREPORTING: False
    FARMACCOUNT: <empty>
    FARMADMINPORT: 0
    FARMPASSWORD: *****
    FEATURES: SQLENGINE,REPLICATION,FULLTEXT,AS,RS,BIDS,CONN,IS,BC,SDK,BOL,SSMS,ADV_SSMS,OCS
    FILESTREAMLEVEL: 2
    FILESTREAMSHARENAME: MSSQLSERVER
    FTSVCACCOUNT: NT AUTHORITY\LOCAL SERVICE
    FTSVCPASSWORD: *****
    HELP: False
    INDICATEPROGRESS: False
    INSTALLSHAREDDIR: C:\Program Files\Microsoft SQL Server\
    INSTALLSHAREDWOWDIR: C:\Program Files (x86)\Microsoft SQL Server\
    INSTALLSQLDATADIR: <empty>
    INSTANCEDIR: C:\Program Files\Microsoft SQL Server\
    INSTANCEID: MSSQLSERVER
    INSTANCENAME: MSSQLSERVER
    ISSVCACCOUNT: NT AUTHORITY\NetworkService
    ISSVCPASSWORD: *****
    ISSVCSTARTUPTYPE: Automatic
    NPENABLED: 0
    PASSPHRASE: *****
    PCUSOURCE:
    PID: *****
    QUIET: False
    QUIETSIMPLE: False
    ROLE: <empty>
    RSINSTALLMODE: DefaultNativeMode
    RSSVCACCOUNT: NT AUTHORITY\SYSTEM
    RSSVCPASSWORD: *****
    RSSVCSTARTUPTYPE: Automatic
    SAPWD: *****
    SECURITYMODE: <empty>
    SQLBACKUPDIR: <empty>
    SQLCOLLATION: SQL_Latin1_General_CP1_CI_AS
    SQLSVCACCOUNT: NT AUTHORITY\SYSTEM
    SQLSVCPASSWORD: *****
    SQLSVCSTARTUPTYPE: Automatic
    SQLSYSADMINACCOUNTS: PC\computername
    SQLTEMPDBDIR: <empty>
    SQLTEMPDBLOGDIR: <empty>
    SQLUSERDBDIR: <empty>
    SQLUSERDBLOGDIR: <empty>
    SQMREPORTING: False
    TCPENABLED: 0
    UIMODE: Normal
    X86: False
    Configuration file: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20140423_234604\ConfigurationFile.ini
    Detailed results:
    Feature: Database Engine Services
    Status: Failed: see logs for details
    MSI status: Passed
    Configuration status: Passed
    Feature: SQL Server Replication
    Status: Failed: see logs for details
    MSI status: Passed
    Configuration status: Passed
    Feature: Full-Text Search
    Status: Failed: see logs for details
    MSI status: Passed
    Configuration status: Passed
    Feature: Analysis Services
    Status: Failed: see logs for details
    MSI status: Passed
    Configuration status: Passed
    Feature: Reporting Services
    Status: Failed: see logs for details
    MSI status: Passed
    Configuration status: Passed
    Feature: Integration Services
    Status: Failed: see logs for details
    MSI status: Passed
    Configuration status: Passed
    Feature: Client Tools Connectivity
    Status: Failed: see logs for details
    MSI status: Passed
    Configuration status: Passed
    Feature: Management Tools - Complete
    Status: Failed: see logs for details
    MSI status: Passed
    Configuration status: Passed
    Feature: Management Tools - Basic
    Status: Failed: see logs for details
    MSI status: Passed
    Configuration status: Passed
    Feature: Client Tools SDK
    Status: Failed: see logs for details
    MSI status: Passed
    Configuration status: Passed
    Feature: Client Tools Backwards Compatibility
    Status: Failed: see logs for details
    MSI status: Passed
    Configuration status: Passed
    Feature: Business Intelligence Development Studio
    Status: Failed: see logs for details
    MSI status: Passed
    Configuration status: Passed
    Feature: SQL Server Books Online
    Status: Failed: see logs for details
    MSI status: Passed
    Configuration status: Passed
    Feature: Microsoft Sync Framework
    Status: Passed
    MSI status: Passed
    Configuration status: Passed
    Rules with failures:
    Global rules:
    Scenario specific rules:
    Rules report file: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20140423_234604\SystemConfigurationCheck_Report.htm
    I tried installing as adminstrator and in compatability mode with Windows 7/Vista but that didn't work. Trying to install from the dvd or from the extracted files in my drive made no difference.
    I am now wondering if there is a download link for SQL Server 2008 R2 Developer edition with SP2 included (i.e. not just SP2 but the whole application (5GB+) otherwise I am not sure how to install this.

    Hello,
    1. Please refer to solution provided in below thread
    http://social.msdn.microsoft.com/Forums/sqlserver/en-US/61d56f64-2575-4a58-9503-84579476afaf/sql-server-2008-setup-error-attempted-to-perform-an-unauthorized-operation?forum=sqlsetupandupgrade
    2. Make sure you stop antivirus services during running the setup.Make sure you Right click on setup.exe file and select run as administrator.
    If above does not works include below as well
    3. Please verify WMI service is started.
    If WMI is started, consider to repair WMI.
    http://windowsxp.mvps.org/repairwmi.htm
    Reference
    Link
    Please mark this reply as the answer or vote as helpful, as appropriate, to make it useful for other readers

  • Cannot install Win Server 2008 x4150

    Title says it all. I've tried the Sun Installation Assistant, I've tried right form the Server 2008 DVD, and Server 2008 R2 DVD, nothing works.
    Most common point of failure: Copying, Expanding and Installing features/updates completes, server restarts, immediately after restart I get the "Clock Interrupt was not received on a secondary processor within the allocated time interval" BSOD.
    Before this error the Server would simply lock up before it finished expanding files so I updated the BIOS and ILOM to the latest versions and now I'm stuck again with the above error.
    Am I missing something? I have tried loading RAID drivers from my updated Tools and Drivers CD and from a floppy even though it only finds the LSI RAID card taht isn't even in use. My RAID config is Adaptec mirrored 2x 73Gb SAS drives. According to all documentation, no drivers are even NEEDED for Server 2008.
    Called Sun support but they can't get back to me until tomorrow morning. I kind of need this fixed now though.
    Thanks in advanced

    Sorry I left that little bit of crucial information out. It was a looooong night.
    I am trying to install 64 bit as per software vendor's requirement. I say software vendor because a third party will be installing software on top of the Datacenter installation.

  • Cannot Edit Duplicate Server Behaviors (bugged?)

    Okay, here's a problem:
    I've got a user login page with two different forms on it -
    one to log in new users, and one to log in existing users. I
    applied a "log in user" server behavior to each of them. Now both
    of these server behaviors are showing up under the Server Behaviors
    menu with the exact same name: "Log In User". When I try to save
    this file I get the following error:
    The Server Behavior panel cannot determine whether "Log In
    User" or "Log In User" is applied to your page. Please select the
    Edit Server Behaviors and change one of the two behaviors to ensure
    that each is uniquely identifiable.
    Clicking on each of them points to the same block of code
    (which logs in the existing user). I cannot delete them using the
    minus sign. When I click on the plus sign and select "Edit Server
    Behaviors" it shows me two other custom behaviors that I'd already
    downloaded (and used on another page) but doesn't show me the "Log
    In User" behavior at all.
    Is there any way to edit these behaviors? Change the name of
    one of them? Right now my page is working perfectly and I wouldn't
    mind the error except for the fact that this page is based on a
    template. Any template changes I make are not updating to this
    page. . . perhaps there's a preference I could change that would
    allow template changes even if an error is encountered?
    Any help is appreciated. Thanks in advance!

    Sylvain; thank you for the reply.  No, this issue impacts entries other than automount as well.
    So far I have observed this with entries consisting of :
    1) top/posixaccount/organizationalPerson/person/inetOrgPerson,
    2) top/groupofuniquenames/posixgroup
    3) top/iphost/nsHost
    4) top/nisNetgroup
    I have double/triple checked the schema and any log files as well to no avail.
    I have opened SR 3-10281206831 related to this issue.

  • Digital Editions & Terminal Server 2008

    I'm checking for a client whether Digital Editions is supported on a Windows 2008 Terminal Server platform.
    Any links/references available?
    Thanks a lot, Arjan.

    No the program does not work in that environment.
    ===============

  • Cannot Restore SQL Server 2008 Server Backup

    PLEASE HELP!!!
    Please I did an Sql database backup for my application server, has some issues with my application data and tried restoring the database but kept getting the error........
    PLEASE MY COMPANY IS HELD TO RANSOM AS WE NEED THE MOST RECENT BACKUP TO WORK!!!

    Thank you Shanky_621 for replying.
    The error is:
    "SQL Server :: Object Cannot Be Cast From DBNull To Other Types"
    Dont use GUI to restore database.This issue can come sometimes when your login is not administrator in SQL Server, instead use below query
    RESTORE FILELISTONLY
    FROM disk= 'AdventureWorks2008R2_Backup'--this would be your backup location
    -- Restore the files for MyAdvWorks.
    RESTORE DATABASE MyAdvWorks--your database name
    FROM AdventureWorks2008R2_Backup
    WITH RECOVERY,
    MOVE 'AdventureWorks2008R2_Data' TO 'D:\MyData\MyAdvWorks_Data.mdf',
    MOVE 'AdventureWorks2008R2_Log' TO 'F:\MyLog\MyAdvWorks_Log.ldf'
    GO
    --specifiy drive where you want to restore database and kjust replace mdf and ndf with name you like in above script
    Please mark this reply as the answer or vote as helpful, as appropriate, to make it useful for other readers

  • RAC on Windows Server 2008 R2 - which edition is necessary

    Hello,
    which Windows Server 2008 R2 edition is required to install RAC - standard or enterprise (NOT database edition - windows server 2008 edition)?
    If we want to implement RAC 11Gr2 Enterprise Edition does the operating system also has to be enterprise edition or is it possible to install RAC 11GR2 Enterprise Edition on Windows Server 2008 Standard Edition?
    What Server Version is more suited for RAC Windows Server 2003 or Windows Server 2008, and why?
    Thanks in advance for any information.
    kind regards
    Monika Anna

    Hi Monika,
    which Windows Server 2008 R2 edition is required to install RAC - standard or enterprise (NOT database edition - windows server 2008 edition)?
    If we want to implement RAC 11Gr2 Enterprise Edition does the operating system also has to be enterprise edition or is it possible to install RAC 11GR2 Enterprise Edition on Windows Server 2008 Standard Edition?All Oracle Database 11g Release 2 is supported on the following Windows Server 2008 R2 editions:
    Windows Web Server 2008 (x64)
    Windows Server 2008 Foundation (x64)
    Windows Server 2008 Standard (x64)
    Windows Server 2008 Enterprise (x64)
    Windows Server 2008 Datacenter (x64)
    What Server Version is more suited for RAC Windows Server 2003 or Windows Server 2008, and why?I recommend Windows 2008, because the system is newer and has a lot of features that do not exist in Windows 2003. Oracle 11.2 is certified in Windows 2008.
    Check this note...
    *Statement of Direction: Oracle Database 11g Release 2 – Microsoft Windows 7 and Windows Server 2008 R2 [ID 867040.1]*
    https://support.oracle.com/CSP/main/article?cmd=show&type=NOT&doctype=ANNOUNCEMENT&id=867040.1
    Regards,
    Levi Pereira

  • Sql server 2008 standard edition verses enterprise edition

    I heard on a call today that microsoft has different logging capture in these two editions. Also because of this difference that at least in the past GG could not support some replication approaches from SQL Server Standard Edition beacuse of this. Can anyone point me to a resource or certification matrix that references standard verses enterprise versions of SQL Server.

    From the SQL Server installation guide:
    ● SQL Server 2000/2005: Enterprise and Standard Edition
    ● SQL Server 2008: Enterprise (capture or delivery) or Standard Edition (delivery only)
    ● SQL Server 2008 R2: Enterprise (capture or delivery) or Standard Edition (delivery only)

  • Has mssql2008r2 got "Cumulative Update Package 6 for SQL Server 2008 Service Pack 1"

    hi,
    I have
    Microsoft SQL Server 2008 R2 (RTM) - 10.50.1600.1 (Intel X86)   Apr  2 2010 15:53:02   Copyright (c) Microsoft Corporation  Express Edition with Advanced Services on Windows NT 5.1 <X86> (Build 2600: Service Pack 3) 
    , i wanted to know has it got
    "Cumulative Update Package 6 for SQL Server 2008 Service Pack 1"
    so that i do not have to install or i have to install
    yours sincerley

    Thank u, please tel me can i instal  sp3.
    I have noticed the link of sp2 (http://www.microsoft.com/en-in/download/details.aspx?id=30437)
     has listed
    (SQL Server 2008 R2 Express Edition)
    SQL Server 2008 R2 Service Pack 2 (SP2) is now available for download. SQL Server 2008 R2 service packs are cumulative and can be used to upgrade all releases of SQL Server 2008 R2 to Service Pack 2. SQL Server 2008 R2 Service Pack 2 contains Cumulative Update
    1 to 5 from SQL Server 2008 R2 SP1. The package can be used to upgrade the following SQL Server 2008 R2 editions: 
    SQL Server 2008 R2 Parallel Computing Edition
    SQL Server 2008 R2 Datacenter Edition
    SQL Server 2008 R2 Enterprise Edition and Developer Edition
    SQL Server 2008 R2 Standard Edition
    SQL Server 2008 R2 Web Edition
    SQL Server 2008 R2 Workgroup Edition
    SQL Server 2008 R2 Express Edition
    where as link of sp3(http://www.microsoft.com/en-us/download/details.aspx?id=44271)
    has not listed express edition but written in general.
    SQL Server 2008 R2 Service Pack 3 (SP3) is now available for download. SQL Server 2008 R2 service packs are cumulative and can be used to upgrade all releases of SQL Server 2008 R2 to Service Pack 3. SQL Server 2008 R2 Service Pack 3 contains
    Cumulative Update 1 to 13 from SQL Server 2008 R2 SP2. The package can be used to upgrade the following SQL Server 2008 R2 editions: 
    SQL Server 2008 R2 Parallel Computing Edition
    SQL Server 2008 R2 Datacenter Edition
    SQL Server 2008 R2 Enterprise Edition and Developer Edition
    SQL Server 2008 R2 Standard Edition
    SQL Server 2008 R2 Web Edition
    SQL Server 2008 R2 Workgroup Edition
    yours sincerley

  • Oracle Database 11g-R2 with Windows Server 2008

    Hi to All Respected Gurus!
    Recently I have downloaded Oracle Database 11g-R2.
    Will it work with Windows Server 2008-R2?
    Please guid eme.
    Thanks in Advance.
    Muhammad Uzair
    Oracle Application Developer
    Oracle APEX Developer
    Pakistan
    +92 (333) 7058754

    uzairmalik wrote:
    Hi to All Respected Gurus!
    Recently I have downloaded Oracle Database 11g-R2.
    Will it work with Windows Server 2008-R2?
    Please guid eme.
    Did you look in the installation guide for the software requirement for 11.2? You could had easily found the answer from there by yourself.
    http://docs.oracle.com/cd/E11882_01/install.112/e24186/reqs.htm#CHDHGGFE
    From the above link,
    >
    Requirement     Value
    Operating System
    Oracle Database for 32-bit Windows is supported on the following operating systems:
    Windows Server 2003 - all editions
    Windows Server 2003 R2 - all editions
    Windows XP Professional
    Windows Vista - Business, Enterprise, and Ultimate editions
    Windows Server 2008 - Standard, Enterprise, Datacenter, Web, and Foundation editions. The Server Core option is not supported.
    Note: Check My Oracle Support (formerly OracleMetaLink) for more information about Hyper-V support.
    Windows 7 - Professional, Enterprise, and Ultimate editions
    Windows Multilingual User Interface Pack is supported.
    >
    Aman....

  • ACS 4.2 Remote Agent on Server 2008 R2

    Hi,
    We are migrating our domain controllers from 2003 to 2008 R2 and would like to know if the remote agents are compatible to run on 2008 R2.  I've seen release notes that the RA's have been tested on 2008 SP1 but not R2.
    Can anyone advise and/or confirm that the RA's are supported on 2008 R2?
    We are currently running Solution Engine 4.2.1.15 as well as the 4.2.1.15-1 fix.  RA's are the same version.
    Thanks in advance for your help.

    Well, this is a known enhancement bug:
    CSCta35271    Support for Windows server 2008 R2
    Acs 4.2.x doesn't support all newer versions of Windows 2008. It only supports the below listed version. You can also check the release notes.
    Supported Operating Systems section
    --Windows Server 2008, Standard Edition
    --Windows Server 2008, Enterprise Edition
    --Japanese Windows Server 2008, Standard Edition, Service Pack 2
    --Japanese Windows Server 2008, Enterprise Edition, Service Pack 2
    This bug might get fixed in upcoming Release\patches. This is in the pipeline/roadmap and the development team is working on it
    Regds,
    JK
    Do rate helpful posts-

  • Error 18452 "Login failed. The login is from an untrusted domain and cannot be used with Windows authentication" on SQL Server 2008 R2 Enterprise Edition 64-bit SP2 clustered instance

    Hi there,
    I have a Windows 2008 R2 Enterprise x64 SP2 cluster which has 2 SQL Server 2008 R2 Enterprise Edition x64 SP2
    instances.
    A domain account "Domain\Login" is administrator on both physcial nodes and "sysadmin" on both SQL Server instances.
    Currently both instances are running on same node.
    While logging on to SQL Server instance 2 thru "Domain\Login" using "IP2,port2", I get error 18452 "Login failed. The login is from an untrusted domain and cannot be used with Windows authentication". This happened in the past
    as well but issue resolved post insatllation of SQL Server 2008R2 SP2. This has re-occurred now. But it connects using 'SQLVirtual2\Instance2' without issue.
    Same login with same rights is able to access Instance 1 on both 'SQLVirtual1\Instance1' and "IP1,port1" without any issue.
    Please help resolve the issue.
    Thanks,
    AY

    Hello,
    I Confirm that I encountred the same problem when the first domain controller was dow !!
    During a restarting of the first domain controller, i tried to failover my SQL Server instance to a second node, after that I will be able to authenticate SQL Server Login but Windows Login returns Error 18452 !
    When the firts DC restart finishied restarting every thing was Ok !
    The Question here : Why the cluster instance does'nt used the second DC ???
    Best Regards     
    J.K

Maybe you are looking for

  • Batch management report

    Hi Experts, Is there any report in batch management  to get a detailed listing of inventory(finished goods) by batch with all characteristic values info included? Best Regards CS

  • ERROR message Final Cut Express HD wont open

    configuration Error this software requires certain hardware or software which is missing AGP graphic card. this is my info on the graphic card GeForce 8600M GT: Chipset Model: GeForce 8600M GT Type: Display Bus: PCIe PCIe Lane Width: x16 VRAM (Total)

  • To Transfer data from internal table to a table control

    Hi All, I have selected some data to be displayed on a screen into an internal table ...............my problem is how to transfer the data from the internal table to this table control so that when screen is displayed the data is also displayed. Rega

  • VBIOS for GTX 970 Gaming 4g

    Hello, can I get latest bios to my graphic card ? Current version NV316MH.186 My S/N: 602-V316-130B1505014241 Thanks

  • Targeting Dynamically Attached MC's (2-3 Levels Deep) From Root????

    I am in the process of building an application where all of the functions will be eventually exported into seperate AS files. I am having issues with a Sub Navigation that is attached and managed dynamically. The Sub Navigation is in an MC which cont