SQL Server OLEDB Provider Support Error - XL Reporter
Hi forum,
When i m trying to run the XL Reporter, It gives below given error.
"Unable to Load SQL Server OLEDB Provider Resource DLL. The Application Can Not continue."
I have remove Add-on folder, .sbo files and re-install too.
Can any body guide the solution.
With Regards,
Chintesh Soni
Hi Jim,
Thnx for reply,
We are using Windows XP Proff. SP2 on the machine. The machine is using as workstation.
Warm Regards,
Chintesh
Edited by: Chintesh Soni on Dec 17, 2008 9:20 AM
Similar Messages
-
Hi All,
I applied SQL server 2008 R2 SP3 recently but report builder doesn't work since then
When click on report builder gives error like 'Application validation did not succeed. Unable to continue.
and when I try to see details the error summary like following:
+File, Microsfot.ReportingServices.ComponentLibrary.Controls.dll, has a different computed hash than specified in manifest.
this is urgent.
Please reply me asap.
thanks a lot in advance.
Regards,
Nik
Regards, NamanHi nikp11,
According to your description, you recently updated SQL Server 2008 R2 to SP3, Report Builder doesn’t work since then the error occurs: "Application validation did not succeed. Unable to continue".
This is an known issue in SSRS 2008 R2 SP3 that Microsoft has published an article addressing this issue. It is not planning to release a fix for this issue. But we could implement one of the following workarounds:
Install and run Report Builder 3.0 of SQL Server 2008 R2 RTM.
Install and run Report Builder of SQL Server 2014.
Uninstall Service Pack 3 then uninstall Service Pack 2 and then reinstall Service Pack 3.
Reference:
Report Builder of SQL Server 2008 R2 Service Pack 3 does not launch
Thank you for your understanding.
Best Regards,
Wendy Fu -
I have problem with login in sql Server give me support .pre login handshake
I have problem with login in sql Server give me support .pre login handshake
The following threads are on the same topic:
http://www.sql-server-performance.com/forum/threads/pre-login-handshake-error-when-connecting-to-db.687/
http://stackoverflow.com/questions/12308340/sql-server-2000-connection-error-pre-login-handshake
http://dbaspot.com/sqlserver-server/458011-error-occurred-during-pre-login-handshake-microsoft-sql-server-error-10054-a.html
Kalman Toth Database & OLAP Architect
IPAD SELECT Query Video Tutorial 3.5 Hours
New Book / Kindle: Exam 70-461 Bootcamp: Querying Microsoft SQL Server 2012 -
SQL Server 2008 R2 { An Error occured when attaching database(s) }
Hello Guys!
I just installed SQL Server 2008 R2 a couple of days ago, on the first day use i can attach database(.mdf) with out any problem.
on the day 2, i keep getting this error:
http://img515.imageshack.us/img515/14/1212i.png
TITLE: Microsoft SQL Server Management Studio
An error occurred when attaching the database(s). Click the hyperlink in the Message column for details.
BUTTONS:
OK
after clicking the Hyperlink this window open:
http://img34.imageshack.us/img34/8766/hyperg.png
TITLE: Microsoft SQL Server Management Studio
Attach database failed for Server 'STARGAZER-PC\SQLSTARMAX'. (Microsoft.SqlServer.Smo)
For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=10.50.1600.1+((KJ_RTM).100402-1539+)&EvtSrc=Microsoft.SqlServer.Management.Smo.ExceptionTemplates.FailedOperationExceptionText&EvtID=Attach+database+Server&LinkId=20476
ADDITIONAL INFORMATION:
An exception occurred while executing a Transact-SQL statement or batch. (Microsoft.SqlServer.ConnectionInfo)
Unable to open the physical file "E:\New folder\DataBase.MDF". Operating system error 5: "5(Access is denied.)". (Microsoft SQL Server, Error: 5120)
For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=10.50.1600&EvtSrc=MSSQLServer&EvtID=5120&LinkId=20476
BUTTONS:
OK
in that day i reinstall SQL Server 2008 R2, because I'm so confused. after that i try to attach i still got the same error, what i did is i share the folder where the database is.
i open SSMS and try to attach and i attached without any error...
i think this is the 4rth day, untill now everytime i want to attach a database i got this error, and even i try to share the folder where the database is i still got that error.
any advice guys?
Thanks a lot
jhules
if you want to be happy, find something you love to do and do it for free, then find someone to to you for it.The Error clearly shows that MDF files and LDF files are not matching or LDF file is corrupted.
You can follow either of the one option below
1. Restore a recent backup rather attaching the MDF file
2. Attach single MDF file without LOG File( Warning: All the log transactions will be gone and new log file will be created)
EXEC sp_attach_single_file_db @dbname = 'AdventureWorks2008R2',
@physname = N'C:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\Data\AdventureWorks2008R2_Data.mdf';
Thanks, Aditya Badramraju, _______________________________________________________ Please mark answered if your question is completely answered; vote it as helpful to help others find a solution quicker. This posting is provided AS IS with no warranties
and confers no rights. _______________________________________________________ -
SQL Server 2012 installation problem (error server didn't respond in timely fashion ....)
Hi everyone,
I am new to SQL server....I am learning C# programming using visual studio 2013 . And I want to learn SQL database language to create and practice C# database project....My computer meets all the hardware requirement for SQL installation (i.e. My computer
has window 7 OS , 80 GB freen HD and 6 GB RAM. ) Therefore I download Microsoft SQL server express 2012 try to install it in my computer (which already has visual studio).
But during installation of SQL server I have problem ...it says
the server doesn't respond in timely fashion. When I research about it everyone were saying uninstall sql and reinstall again. I uninstall and re install but still having same problem...
The database engine also not installed displaying same error.
I don't know how can i install sql server 2012 to use with visual studio in same computer.
Can somebody please help with SQL installation please ?
It will be great help.
Many thanks in advance
regards
rashHi
my summary file is :
Overall summary:
Final result: Failed: see details below
Exit code (Decimal): -2146232832
Start time: 2015-04-06 11:34:18
End time: 2015-04-06 19:04:46
Requested action: Install
Setup completed with required actions for features.
Troubleshooting information for those features:
Next step for SQLEngine: Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
Next step for DQ: Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
Next step for FullText: Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
Next step for Replication: Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
Next step for IS: Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
Next step for RS: Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
Next step for AS: Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
Machine Properties:
Machine name: RASHA-VAIO
Machine processor count: 4
OS version: Windows 7
OS service pack: Service Pack 1
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
SQL Server 2008 SQLEXPRESS MSSQL10.SQLEXPRESS Database Engine Services 1033
Express Edition 10.1.2531.0 No
SQL Server 2008 SQLEXPRESS MSSQL10.SQLEXPRESS SQL Server Replication 1033
Express Edition 10.1.2531.0 No
Package properties:
Description: Microsoft SQL Server 2012 Service Pack 1
ProductName: SQL Server 2012
Type: RTM
Version: 11
SPLevel: 0
Installation location: E:\x64\setup\
Installation edition: Enterprise
Product Update Status:
None discovered.
User Input Settings:
ACTION: Install
ADDCURRENTUSERASSQLADMIN: false
AGTSVCACCOUNT: NT Service\SQLSERVERAGENT
AGTSVCPASSWORD: *****
AGTSVCSTARTUPTYPE: Manual
ASBACKUPDIR: C:\Program Files\Microsoft SQL Server\MSAS11.MSSQLSERVER\OLAP\Backup
ASCOLLATION: Latin1_General_CI_AS
ASCONFIGDIR: C:\Program Files\Microsoft SQL Server\MSAS11.MSSQLSERVER\OLAP\Config
ASDATADIR: C:\Program Files\Microsoft SQL Server\MSAS11.MSSQLSERVER\OLAP\Data
ASLOGDIR: C:\Program Files\Microsoft SQL Server\MSAS11.MSSQLSERVER\OLAP\Log
ASPROVIDERMSOLAP: 1
ASSERVERMODE: TABULAR
ASSVCACCOUNT: NT Service\MSSQLServerOLAPService
ASSVCPASSWORD: <empty>
ASSVCSTARTUPTYPE: Automatic
ASSYSADMINACCOUNTS: RASHA-VAIO\RASHA
ASTEMPDIR: C:\Program Files\Microsoft SQL Server\MSAS11.MSSQLSERVER\OLAP\Temp
BROWSERSVCSTARTUPTYPE: Disabled
CLTCTLRNAME: MAIN
CLTRESULTDIR: C:\Program Files (x86)\Microsoft SQL Server\DReplayClient\ResultDir\
CLTSTARTUPTYPE: Manual
CLTSVCACCOUNT: NT Service\SQL Server Distributed Replay Client
CLTSVCPASSWORD: <empty>
CLTWORKINGDIR: C:\Program Files (x86)\Microsoft SQL Server\DReplayClient\WorkingDir\
COMMFABRICENCRYPTION: 0
COMMFABRICNETWORKLEVEL: 0
COMMFABRICPORT: 0
CONFIGURATIONFILE: C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log\20150406_112342\ConfigurationFile.ini
CTLRSTARTUPTYPE: Manual
CTLRSVCACCOUNT: NT Service\SQL Server Distributed Replay Controller
CTLRSVCPASSWORD: <empty>
CTLRUSERS: RASHA-VAIO\RASHA
ENABLERANU: false
ENU: true
ERRORREPORTING: false
FEATURES: SQLENGINE, REPLICATION, FULLTEXT, DQ, AS, RS, RS_SHP, RS_SHPWFE, DQC, BIDS, CONN, IS, BC, SDK, BOL, SSMS, ADV_SSMS, DREPLAY_CTLR, DREPLAY_CLT, SNAC_SDK, MDS
FILESTREAMLEVEL: 0
FILESTREAMSHARENAME: <empty>
FTSVCACCOUNT: NT Service\MSSQLFDLauncher
FTSVCPASSWORD: <empty>
HELP: false
IACCEPTSQLSERVERLICENSETERMS: 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 Service\MsDtsServer110
ISSVCPASSWORD: <empty>
ISSVCSTARTUPTYPE: Automatic
MATRIXCMBRICKCOMMPORT: 0
MATRIXCMSERVERNAME: <empty>
MATRIXNAME: <empty>
NPENABLED: 0
PID: *****
QUIET: false
QUIETSIMPLE: false
ROLE: <empty>
RSINSTALLMODE: FilesOnlyMode
RSSHPINSTALLMODE: SharePointFilesOnlyMode
RSSVCACCOUNT: NT Service\ReportServer
RSSVCPASSWORD: <empty>
RSSVCSTARTUPTYPE: Automatic
SAPWD: *****
SECURITYMODE: SQL
SQLBACKUPDIR: <empty>
SQLCOLLATION: Latin1_General_CI_AS
SQLSVCACCOUNT: NT Service\MSSQLSERVER
SQLSVCPASSWORD: <empty>
SQLSVCSTARTUPTYPE: Automatic
SQLSYSADMINACCOUNTS: RASHA-VAIO\RASHA
SQLTEMPDBDIR: <empty>
SQLTEMPDBLOGDIR: <empty>
SQLUSERDBDIR: <empty>
SQLUSERDBLOGDIR: <empty>
SQMREPORTING: false
TCPENABLED: 1
UIMODE: Normal
UpdateEnabled: true
UpdateSource: MU
X86: false
Configuration file: C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log\20150406_112342\ConfigurationFile.ini
Detailed results:
Feature: Management Tools - Complete
Status: Passed
Feature: Client Tools Connectivity
Status: Passed
Feature: Client Tools SDK
Status: Passed
Feature: Client Tools Backwards Compatibility
Status: Passed
Feature: Management Tools - Basic
Status: Passed
Feature: SQL Server Data Tools
Status: Passed
Feature: Database Engine Services
Status: Failed: see logs for details
Reason for failure: An error occurred during the setup process of the feature.
Next Step: Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
Component name: SQL Server Database Engine Services Instance Features
Component error code: 0x80004005
Error description: The service did not respond to the start or control request in a timely fashion.
Error help link: http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=11.0.3128.0&EvtType=0xDC112D1C%400xDC80C325&EvtType=0xDC112D1C%400xDC80C325
Feature: Data Quality Services
Status: Failed: see logs for details
Reason for failure: An error occurred for a dependency of the feature causing the setup process for the feature to fail.
Next Step: Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
Component name: SQL Server Database Engine Services Instance Features
Component error code: 0x80004005
Error description: The service did not respond to the start or control request in a timely fashion.
Error help link: http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=11.0.3128.0&EvtType=0xDC112D1C%400xDC80C325&EvtType=0xDC112D1C%400xDC80C325
Feature: Full-Text and Semantic Extractions for Search
Status: Failed: see logs for details
Reason for failure: An error occurred for a dependency of the feature causing the setup process for the feature to fail.
Next Step: Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
Component name: SQL Server Database Engine Services Instance Features
Component error code: 0x80004005
Error description: The service did not respond to the start or control request in a timely fashion.
Error help link: http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=11.0.3128.0&EvtType=0xDC112D1C%400xDC80C325&EvtType=0xDC112D1C%400xDC80C325
Feature: SQL Server Replication
Status: Failed: see logs for details
Reason for failure: An error occurred for a dependency of the feature causing the setup process for the feature to fail.
Next Step: Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
Component name: SQL Server Database Engine Services Instance Features
Component error code: 0x80004005
Error description: The service did not respond to the start or control request in a timely fashion.
Error help link: http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=11.0.3128.0&EvtType=0xDC112D1C%400xDC80C325&EvtType=0xDC112D1C%400xDC80C325
Feature: Master Data Services
Status: Passed
Feature: Distributed Replay Client
Status: Passed
Feature: Distributed Replay Controller
Status: Passed
Feature: Integration Services
Status: Failed: see logs for details
Reason for failure: An error occurred during the setup process of the feature.
Next Step: Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
Component name: SQL Server Integration Services
Component error code: 0x84BB0001
Error description: The service did not respond to the start or control request in a timely fashion.
Error help link: http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=11.0.3128.0&EvtType=0xDC112D1C%400xDC80C325&EvtType=0xDC112D1C%400xDC80C325
Feature: Data Quality Client
Status: Passed
Feature: Reporting Services - Native
Status: Failed: see logs for details
Reason for failure: An error occurred during the setup process of the feature.
Next Step: Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
Component name: SQL Server Reporting Services
Component error code: 0x84BB0001
Error description: The service did not respond to the start or control request in a timely fashion.
Error help link: http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=11.0.3128.0&EvtType=0xDC112D1C%400xDC80C325&EvtType=0xDC112D1C%400xDC80C325
Feature: Analysis Services
Status: Failed: see logs for details
Reason for failure: An error occurred during the setup process of the feature.
Next Step: Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
Component name: SQL Server Analysis Services
Component error code: 0x80131600
Error description: The service could not be started. Reason: The service did not respond to the start or control request in a timely fashion.
Error help link: http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=11.0.3128.0&EvtType=0x88A466B0%400x857354B0&EvtType=0x88A466B0%400x857354B0
Feature: Reporting Services - SharePoint
Status: Passed
Feature: Reporting Services Add-in for SharePoint Products
Status: Passed
Feature: SQL Browser
Status: Passed
Feature: Documentation Components
Status: Passed
Feature: SQL Writer
Status: Passed
Feature: SQL Client Connectivity
Status: Passed
Feature: SQL Client Connectivity SDK
Status: Passed
Rules with failures:
Global rules:
Scenario specific rules:
Rules report file: C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log\20150406_112342\SystemConfigurationCheck_Report.htm
I hope it will help you to figure out ...i dont know how to solve this issue ..i have un install and re install more than 5 times.
thank you -
Hello,
Am trying to upgrade a SCOM SP1 environment to SCOM R2( 3 MGT servers, 1 GW and 2 Web console boxes )
The prerequisites are failing and it is stating the following ;
Operational Database SQL Version Check - The installed Version of SQL Server is not supported for the operational database
Data Warehouse SQL Version Check - The installed Version of SQL Server is not supported for the data warehouse
The SQL servers are running SQL 2012 SP1 64 Enterprise, which is compatible.
All other pre-upgrade tasks have been done.
Help appreciated!I'm having the exact same issue, I believe. I think that Tubble has problem with SCOM 2012. Not 2007.
I've checked the compatibility list for both SCOM 2012 SP1 and R2. All newer Windows Server and SQL versions are supported. We're running the SQL 2012 SP1 x64 Standard edition on a Windows Server 2012 Standard.
I even tried to move the database from SQL 2012 to an older SQL 2008 R2, but that's not supported either. Only upgrading. Not downgrading.
So, I started checking the opsMgrSetupWizard.log file for clues. And the error message was there as well. But the reason why it says not supported is that it can't get the info about the OS version, so I guess it assumes the OS version is to low. The RPC
service can not be reached.
[10:29:11]: Error: :GetRemoteOSVersion(): Threw Exception.Type: System.Runtime.InteropServices.COMException, Exception Error Code: 0x800706BA, Exception.Message: The RPC server is unavailable. (Exception from HRESULT: 0x800706BA)
[10:29:11]: Error: :StackTrace: at System.Runtime.InteropServices.Marshal.ThrowExceptionForHRInternal(Int32 errorCode, IntPtr errorInfo)
at System.Management.ManagementScope.InitializeGuts(Object o)
at System.Management.ManagementScope.Initialize()
at System.Management.ManagementObjectSearcher.Initialize()
at System.Management.ManagementObjectSearcher.Get()
at Microsoft.EnterpriseManagement.OperationsManager.Setup.Common.SetupValidationHelpers.GetRemoteOSVersion(String remoteComputer)
[10:29:11]: Debug: :IsSQLOnAValidComputer: remote OS version string was null or empty.
[10:29:11]: Error: :Error:IsValidSQLVersionCheck: SqlServer OS version is too low.
[10:29:11]: Debug: :**************************************************
[10:29:11]: Error: :<![CDATA[CheckPrerequisites: Logic Type:and IsValidOMDBSQLVersionCheck: 2]]>
[10:29:11]: Error: :
[10:29:11]: Error: :CheckPrerequisites: OMDBSqlVersionCheckTitle: Failed
[10:29:11]: Error: :
[10:29:11]: Debug: :**************************************************
[10:29:33]: Error: :GetRemoteOSVersion(): Threw Exception.Type: System.Runtime.InteropServices.COMException, Exception Error Code: 0x800706BA, Exception.Message: The RPC server is unavailable. (Exception from HRESULT: 0x800706BA)
[10:29:33]: Error: :StackTrace: at System.Runtime.InteropServices.Marshal.ThrowExceptionForHRInternal(Int32 errorCode, IntPtr errorInfo)
at System.Management.ManagementScope.InitializeGuts(Object o)
at System.Management.ManagementScope.Initialize()
at System.Management.ManagementObjectSearcher.Initialize()
at System.Management.ManagementObjectSearcher.Get()
at Microsoft.EnterpriseManagement.OperationsManager.Setup.Common.SetupValidationHelpers.GetRemoteOSVersion(String remoteComputer)
[10:29:33]: Debug: :IsSQLOnAValidComputer: remote OS version string was null or empty.
[10:29:33]: Error: :Error:IsValidSQLVersionCheck: SqlServer OS version is too low.
[10:29:33]: Debug: :**************************************************
So, in our case this was just a FW that was blocking some high ports between management server and SQL. I believe TCP port 135 also needs to be open.
Let's hope this fixes your issue as well, Tubble.
Have a great day! -
Hi All,
I have started receiving this error in the logs for the last 10 days and the Schedules Jobs for the database have stopped running. My MS CRM application is working fine.
Can anyone guide me what could be the problem.
Date 17/4/2014 2:04:20 PM
Log SQL Server Agent (Current - 17/4/2014 2:01:00 PM)
Message
[298] SQLServer Error: 10061,
A network-related or instance-specific error has occurred while establishing a connection to SQL Server. Server is not found or not accessible. Check if instance name is correct
and if SQL Server is configured to allow remote connections. For more information see SQL Server Books Online. [SQLSTATE 08001]
Date 17/4/2014 2:11:55 PM
Log SQL Server Agent (Current - 17/4/2014 2:01:00 PM)
Message
[298] SQLServer Error: 10061,
A network-related or instance-specific error
has occurred while establishing a connection to SQL Server. Server is not found or not accessible. Check if instance name is correct and if SQL Server is configured to allow remote connections. For more information
see SQL Server Books Online. [SQLSTATE 08001]
Date 7/4/2014 11:00:31 AM
Log SQL Server Agent (Current - 17/4/2014 2:01:00 PM)
Message
[298] SQLServer Error: 10061,
A network-related or instance-specific error
has occurred while establishing a connection to SQL Server. Server is not found or not accessible. Check if instance name is correct and if SQL Server is configured to allow remote connections. For more information
see SQL Server Books Online. [SQLSTATE 08001]Check this link
http://social.msdn.microsoft.com/Forums/en-US/906da9b5-2482-468c-a424-ae099da2d96b/sql-server-agent-service-account-error?forum=sqlsetupandupgrade
Regards, RSingh -
Failed to set security on SQL Server registry key. Error: 2
Hi,
I have a Primary site (mixed mode) running SCCM 2007 SP1 for many months now with no issues.
This site is made up of two Win 2008 sp2 servers sharing the SCCM roles:-
SCCM01 - Site server, DP, RP, PXE and SQL2005 hosting the SCCM database
SCCM02 – SUP, MP, FSP, SLP
The SQL2005 on SCCM01 is running under a domain service account called
domain\service_sccm which is also a sysadmin in SQL as is the SCCM02 server.
In an effort to resolve the isse I have made this account a Domain Admin.
I have also used this account to log onto SEC01 to run the Secondary Site installation and to be the SQL Service account.
I'm now trying to add a Secondary Site on a Domain Controller called SEC01 (also Win2008 sp2) and on the same LAN as the SCCM01/02.
This is where I get problems.
I run the installation locally on the Sec Site server (DC) as a Domain Admin and the installation completes OK (all green ticks),
the ComponentSetup.log and Pre-Reqs are all good as well however when I check the ConfigMgrSetup.log I see the below -
Failed to set security on SQL Server registry key. Error: 2.
<11-09-2010 22:46:59> SMS Setup full version is 4.00.6221.1000
<11-09-2010 22:46:59> Successfully set security on Setup registry key.
<11-09-2010 22:46:59> Failed to set security on SQL Server registry key. Error: 2
<11-09-2010 22:46:59> Successfully set security on Identification registry key.
<11-09-2010 22:46:59> Creating SMS Inbox Source registry key ...
<11-09-2010 22:46:59> Installing SMS Site Component Manager ...
<11-09-2010 22:46:59> Installing Site Component Manager under acct <NT AUTHORITY\SYSTEM> path <C:\Program Files (x86)\Microsoft
Configuration Manager\bin\i386\sitecomp.exe>
<11-09-2010 22:47:01> Started Site Component Manager service
<11-09-2010 22:47:01> SMS Site Component Manager installation completed.
<11-09-2010 22:47:01> Done with service installation
Adding the PMP role to SEC01 also fails to install and no MPSetup or MPControl logs are created.
WebDav and win2008 roles, features all added and server fully patched.
Despooler.log on SCCM01 seems good and passing keys.
Tried installing to default path and to shortened path such as C:\SCCM
The new secondary site is listed in the console and an address can be added for the Secondary Site
BITS Server Extensions and Remote Differential Compression Features are enabled.
The Group memberships all appear ok:-
SCCM01
Local Admins
contains the sec site server SEC01, SCCM01, installation accounts
SMS_SiteToSiteConnection_001
SEC01 (the sec site server)
SMS_SiteSystemToSiteServerConnection_001
SCCM02
SEC01
No Local Admins as a DC
SMS_SiteToSiteConnection_002
SCCM01
SMS_SiteSystemToSiteServerConnection_002
empty
SQL 2005
This has the account logged in during installation as a sysadmin
SCCM02 is also sysadmin
The fundamental issue appears to be that the SEC01$ server account is not being added to SQL Logins (and therefore SCCM database Roles)
therefore the installation cannot complete.
I have tried to manually add the SEC01 account to SQL Logins before installation of Sec Site but this did not work.
Not sure if the fact that SEC01 is a DC may be a factor.
Appreciate any help if anyone has seen this before or can suggest a resolution.
ThanksAfter a lot of digging around and head scratching I eventually found the resolution.
The original thread title Error turned out to be a bit of a red herring in that my failure to deploy Sec Sites came down to two separate issues seemingly unrelated to the error message of the thread title.
The first part of the resolution was to manually create the SQL Server accounts for the Sec Site Servers and assign them to the smsdbrole_MP DB role to
let the SQL side of the SCCM install complete a s these were not being created automatically.
This then left the fact that that the installation of the Sec Site completed successfully according to the install logs in C:\ however the DP and MP would
never install.
The big clue was eventually contained in the mpfdm.log errors relating to
**ERROR: Cannot find path for destination inbox SMS_AMT_PROXY_COMPONENT on server REGISTRY SMS_MP_FILE_DISPATCH_MANAGER
and
**ERROR: Cannot find path for destination inbox Asset Intelligence KB Manager on server REGISTRY SMS_MP_FILE_DISPATCH_MANAGER
Thankfully the errors led me to these two blogs:
http://myitforum.com/cs2/blogs/scassells/archive/2009/07/20/error-cannot-find-path-for-destination-inbox-sms-amt-proxy-component-on-server-registry.aspx
and
http://social.technet.microsoft.com/Forums/en-US/configmgrsetup/thread/5fcc53d4-8629-4b34-9eaa-6cb020eedc13/
As it turned out the SCCM installation registry and folder creation does not complete and I had to manually enter the reg settings as detailed in the
links above to complete the installation. Once I did as described everything worked a treat – all my MPs and DPs are 100% now.
Solutions
Add the following reg keys to each of your effected secondary sites.
Inbox Fix
Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SMS\MPFDM\Inboxes]
"Asset Intelligence KB Manager"="E:\\Program Files\\Microsoft Configuration Manager\\inboxes\\AIKbMgr.box"
"SMS_AMT_PROXY_COMPONENT"="E:\\Program Files\\Microsoft Configuration Manager\\inboxes\\amtproxy.box"
Asset Intelligence fix:
Note: you will need to identify the next largest key value.
In my example it was key 49
Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SMS\Inbox Source\Inbox Definitions\49]
"Inbox Name"="Asset Intelligence KB Manager"
"Relative Path"="inboxes\\AIKbMgr.box"
"NAL Path"=""
"User Rights"=dword:00000000
"Service Rights"=dword:00000004
"Monitoring Enabled"=dword:00000001
"Location Type"=dword:00000001
"Guest Rights"=dword:00000001
AMT registry Fix.
Note: you will need to identify the next largest key value.
In my example it was key 50
Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SMS\Inbox Source\Inbox Definitions\50]
"Inbox Name"="SMS_AMT_PROXY_COMPONENT"
"Relative Path"="inboxes\\amtproxy.box"
"NAL Path"=""
"User Rights"=dword:00000000
"Service Rights"=dword:00000004
"Monitoring Enabled"=dword:00000001
"Location Type"=dword:00000001
"Guest Rights"=dword:00000001
Big thanks to Shaun Cassells and John Marcum for these blogs -
I have a problem with a DB call. I have two sql delete statements embedded
in Forte Begin End Transaction block. The second statement fails with the
ODBC error. The first Delete causes a DB level Trigger to happen that also
has a Transaction with a Insert into another table. The triggered insert
also has a Transaction and insert. Any Ideas?
I am getting the following error:
ODBC SQLExecute failed.
[Microsoft][ODBC SQL Server Driver]Connection is busy with results for
another hstmt
Eric Rasmussen
Online Resources &
Communications Corporation
(703) 394-5128
[email protected]
To unsubscribe, email '[email protected]' with
'unsubscribe forte-users' as the body of the message.
Searchable thread archive <URL:http://pinehurst.sageit.com/listarchive/>Hi Eric,
This seems to do the trick. My DBA had suggested that I use that to >help
with performance. Any explanation as to why this causes the error?
Thanks!
I am not too sure, probably, the version!! I am running 2.65 (ODBC Driver
for SQL Server) and I faced with similar problem sometime back.
Regards,
V Muthuramalingam (Muthu)
Catapult Technology, Inc.
[email protected]
[email protected]
http://www.catapultt.com
-----Original Message-----
From: Muthuramalingam Venkataraman [SMTP:[email protected]]
Sent: Thursday, June 17, 1999 4:52 PM
To: [email protected]
Cc: [email protected]
Subject: Re: SQL Server 6.5 ODBC Error
You might probably want to uncheck the Generate Stored Procedure for
Prepared Statement in your ODBC configuration setting!
Hope this helps
V Muthuramalingam (Muthu)
Catapult Technology, Inc.
[email protected]
[email protected]
http://www.catapultt.com
Eric wrote :
I have a problem with a DB call. I have two sql delete statementsembedded
in Forte Begin End Transaction block. The second statement fails withthe
ODBC error. The first Delete causes a DB level Trigger to happen thatalso
has a Transaction with a Insert into another table. The triggered
insert
also has a Transaction and insert. Any Ideas?
I am getting the following error:
ODBC SQLExecute failed.
[Microsoft][ODBC SQL Server Driver]Connection is busy with results for
another hstmt
Get Your Private, Free Email at http://www.hotmail.com
Get Your Private, Free Email at http://www.hotmail.com
To unsubscribe, email '[email protected]' with
'unsubscribe forte-users' as the body of the message.
Searchable thread archive <URL:http://pinehurst.sageit.com/listarchive/> -
Microsoft OLE DB Provider for SQL Server 2012 Analysis Services Error Code = 0x80040E05
I've been running a package for 6 months without any issues that pulls data from a cube via MDX and moves it to a database.
We've recently moved to a new server x64 and the connections all succeed but at runtime (in 64 = T&F) I get the following error:
[SRC AdExchange [87]] Error: SSIS Error Code DTS_E_OLEDBERROR. An OLE DB error has occurred. Error code: 0x80040E05.
An OLE DB record is available. Source: "Microsoft OLE DB Provider for SQL Server 2012 Analysis Services." Hresult: 0x00000001 Description: "Error Code = 0x80040E05, External Code = 0x00000000:.".
[SSIS.Pipeline] Error: SRC AdExchange failed the pre-execute phase and returned error code 0xC0202009.
I've installed SQL_AS_OLEDB, SQL_AS_ADOMD from Microsoft® SQL Server® 2012 SP1 Feature Pack
Why is my connection failing?The server has a 10Gbps network connection.
I've installed CU6 for SQL Server 2012 SP1
http://support.microsoft.com/kb/2874879/en-us#hfi
I'm still getting the same error at runtime in BIDS:
[SRC AdExchange [87]] Error: SSIS Error Code DTS_E_OLEDBERROR. An OLE DB error has occurred. Error code: 0x80040E05.
An OLE DB record is available. Source: "Microsoft OLE DB Provider for SQL Server 2012 Analysis Services." Hresult: 0x00000001 Description: "Error Code = 0x80040E05, External Code = 0x00000000:.".
[SSIS.Pipeline] Error: SRC AdExchange failed the pre-execute phase and returned error code 0xC0202009.
Looking at the errorlog, everything looks normal until:
Launched startup procedure 'sp_ssis_startup'.
Attempting to load library 'xpsqlbot.dll' into memory. This is an informational message only. No user action is required.
Using 'xpsqlbot.dll' version '2011.110.2100' to execute extended stored procedure 'xp_qv'. This is an informational message only; no user action is required.
Attempting to load library 'xpstar.dll' into memory. This is an informational message only. No user action is required.
Using 'xpstar.dll' version '2011.110.3000' to execute extended stored procedure 'xp_instance_regread'. This is an informational message only; no user action is required.
Attempting to load library 'xplog70.dll' into memory. This is an informational message only. No user action is required.
Using 'xplog70.dll' version '2011.110.2100' to execute extended stored procedure 'xp_msver'. This is an informational message only; no user action is required.
AppDomain 2 (SSISDB.dbo[runtime].1) created.
Unsafe assembly 'microsoft.sqlserver.integrationservices.server, version=11.0.0.0, culture=neutral, publickeytoken=89845dcd8080cc91, processorarchitecture=msil' loaded into appdomain 2 (SSISDB.dbo[runtime].1).
Unsafe assembly 'microsoft.sqlserver.integrationservices.server, version=11.0.0.0, culture=neutral, publickeytoken=89845dcd8080cc91, processorarchitecture=msil' loaded into appdomain 2 (SSISDB.dbo[runtime].1).
AppDomain 3 (master.sys[runtime].2) created.
Software Usage Metrics is enabled.
SQL Server is terminating because of a system shutdown. This is an informational message only. No user action is required.
Service Broker manager has shut down.
Error: 17054, Severity: 16, State: 1.
The current event was not reported to the Windows Events log. Operating system error = (null). You may need to clear the Windows Events log if it is full.
.NET Framework runtime has been stopped.
SQL Trace was stopped due to server shutdown. Trace ID = '1'. This is an informational message only; no user action is required.
The SQL Server Network Interface library could not deregister the Service Principal Name (SPN) [ MSSQLSvc/XXXXXXXXXX.com ] for the SQL Server service. Error: 0xffffffff, state: 63. Administrator should deregister this SPN manually to avoid client authentication
errors.
The SQL Server Network Interface library could not deregister the Service Principal Name (SPN) [ MSSQLSvc/XXXXXXXXXX.com:1433 ] for the SQL Server service. Error: 0xffffffff, state: 63. Administrator should deregister this SPN manually to avoid client authentication
errors.
Wondering about the unsafe assembly in SSIS and deregistering the SPN..
Anyone have any ideas on how to resolve this?
Thanks! -
Hi,
I keep receiving the error below in the SQL Server Agent Error Log;
[165] ODBC Error: 0, Named Pipes Provider: Could not open a connection to SQL Server [2]. [SQLSTATE 08001]
It is occurring approximately 20 times an hour and i cannot link it to any job failures. All jobs on the same SQL instance are working.
The server is a clustered server and there are no errors occuring in the SQL Server error log at the same time. I have attempted to trace using profiler looking for errors and warnings but anything that does occur doesn't seem to correspond to the reported
times of the errors within the sql agent error log.
Please could someone point me where to look next?
Many thanks.Please may I add that this is on a SQL Server 2008 R2 Enterprise edition patched to 10.50.1600.
Nah, that server is not patched at all, because 10.50.1600 is the RTM version. Find Service Pack 2 and install at the next maintenance window, after having performed tests according to your local policy.
It is not going to resolve your particular problem though.
It seems like you have a job that attempts to a connect to s server that is down or non-existing. The job may be configured to return success also on failures. I would check if there are jobs that target other servers.
Erland Sommarskog, SQL Server MVP, [email protected] -
SQL Server 2012 SP2 support for installation of OM 2012 R2
Hello everyone,
according to
http://technet.microsoft.com/en-us/library/dn281933.aspx SQL Server 2012 SP2 is a supported configuration for SCOM 2012 R2.
Now I've just happily set up an SQL 2012 R2 Instance with SP1 on Windows Server 2012 R2, applied the SP2 and made the Installation a Windows Server Core. Which worked just great but when I started the Setup for SCOM2012 R2 the installer says my SQL Server
Version is not supported and will not allow the Setup to continue. I've also upgraded the Reporting Services Database to 2012 SP2 aswell, I guess that would appear on the next page on the installer and cause similar issues.
I guess it's a configuration value that needs to be changed on the install media to add the SQL Server Version of SP2 as an allowed one.
Can anyone clarify my theory? If it's not that, is there an updated Media somewhere accessible?Hi,
Please check install logs for further information:
OpsMgr 2012: My installation failed. What log files do I read and where can I find them?
http://www.systemcentercentral.com/opsmgr-2012-my-installation-failed-what-log-files-do-i-read-and-where-can-i-find-them/
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
alright, next smartass here's the logfile stating the same thing as I do:
<Quote>
[2014-11-07T08:44:33.0634360+01:00]: Always: Trace Session Started
[08:44:33]: Always: :
[08:44:33]: Always: :
Application Started
[08:44:33]: Always: :Machine on which Operations Manager is being installed: SCOM01
[08:44:33]: Always: :Current setup user: domain\Administrator
[08:44:33]: Always: :Current setup version: 7.1.10226.0
[08:44:33]: Always: :Begin: Parse command line.
[08:44:33]: Debug: :Collected a path value of: C:\SC2012 R2 SCOM\Setup\AMD64\
[08:44:33]: Always: :Begin: Parse command line.
[08:44:33]: Always: :End: Parse reporting command line switches.
[08:44:33]: Always: :End: Parse data reader account command line switches.
[08:44:33]: Always: :End: Parse command line.
[08:44:33]: Always: :Begin: System State detection.
[08:44:33]: Info: :Info:CheckIfOpsMgrComponentsInstalled: component - OMCONSOLE
[08:44:33]: Info: :Info:Component OMCONSOLE is not installed
[08:44:33]: Info: :Info:CheckIfOpsMgrComponentsInstalled: component - OMSERVER
[08:44:33]: Info: :Info:Component OMSERVER is not installed
[08:44:33]: Info: :Info:CheckIfOpsMgrComponentsInstalled: component - OMWEBCONSOLE
[08:44:33]: Info: :Info:Component OMWEBCONSOLE is not installed
[08:44:33]: Info: :Info:CheckIfOpsMgrComponentsInstalled: component - OMREPORTING
[08:44:33]: Info: :Info:Component OMREPORTING is not installed
[08:44:33]: Always: :End: System State detection.
[08:44:33]: Info: :Beginning evaluation of rule 'Upgrade rules for SCOM setup.'
[08:44:33]: Debug: :Condition wasnt defined for rule 'Upgrade rules for SCOM setup.'.
[08:44:33]: Info: :Beginning evaluation of rule 'UpgradeRulesForAllSKUs'
[08:44:33]: Debug: :Condition wasnt defined for rule 'UpgradeRulesForAllSKUs'.
[08:44:33]: Info: :Beginning evaluation of rule 'BlueUpgradeRules'
[08:44:33]: Debug: :Condition wasnt defined for rule 'BlueUpgradeRules'.
[08:44:33]: Info: :Info:OM12RTMServer is installed: False
[08:44:33]: Info: :Info:Product check for OM12RTMServer failed.
[08:44:33]: Info: :Info:OM12RTMConsole is installed: False
[08:44:33]: Info: :Info:Product check for OM12RTMConsole failed.
[08:44:33]: Info: :Info:OM12RTMWebConsole is installed: False
[08:44:33]: Info: :Info:Product check for OM12RTMWebConsole failed.
[08:44:33]: Info: :Info:OM12RTMReporting is installed: False
[08:44:33]: Info: :Info:Product check for OM12RTMReporting failed.
[08:44:33]: Info: :Info:OM12RTMServer is installed: False
[08:44:33]: Info: :Info:Product check for OM12RTMServer failed.
[08:44:33]: Info: :Info:OM12RTMConsole is installed: False
[08:44:33]: Info: :Info:Product check for OM12RTMConsole failed.
[08:44:33]: Info: :Info:OM12RTMWebConsole is installed: False
[08:44:33]: Info: :Info:Product check for OM12RTMWebConsole failed.
[08:44:33]: Info: :Info:OM12RTMReporting is installed: False
[08:44:33]: Info: :Info:Product check for OM12RTMReporting failed.
[08:44:33]: Info: :Finished evaluation of rule 'BlueUpgradeRules'
[08:44:33]: Info: :Finished evaluation of rule 'UpgradeRulesForAllSKUs'
[08:44:33]: Info: :Finished evaluation of rule 'Upgrade rules for SCOM setup.'
[08:44:33]: Always: :This is not an upgrade
[08:44:33]: Always: :No OM component is installed on this machine and it's interactive run.
[08:44:33]: Error: :Error:User did not accept EULA.
[08:44:33]: Always: :We don't have a path entry in the registry or from command line so using default install path as C:\Program Files\Microsoft System Center 2012 R2\Operations Manager
[08:44:33]: Info: :SetInstallPath: installpath has a value of C:\Program Files\Microsoft System Center 2012 R2\Operations Manager
[08:44:33]: Info: :Info:SetComponentSwitches: component list not specified
[08:44:33]: Always: :Begin: Rationalize components.
[08:44:33]: Always: :Begin: Rationalize command line arguments (first run).
[08:44:33]: Always: :RationalizeCommandLineArguments succeeded.
[08:44:33]: Always: :End: Rationalize command line arguments (first run).
[08:44:33]: Always: :Begin: Rationalize final steps.
[08:44:33]: Info: :Beginning evaluation of rule 'Block Unsupported MOM versions.'
[08:44:33]: Debug: :Condition wasnt defined for rule 'Block Unsupported MOM versions.'.
[08:44:33]: Info: :Beginning evaluation of rule 'PreOM12RTMRulesGroup'
[08:44:33]: Debug: :Condition wasnt defined for rule 'PreOM12RTMRulesGroup'.
[08:44:33]: Info: :Info:MOMSelect is installed: False
[08:44:33]: Info: :Info:MOMAEM is installed: False
[08:44:33]: Info: :Info:MOMEval is installed: False
[08:44:33]: Info: :Info:MOMOEM is installed: False
[08:44:33]: Info: :Info:MOMAgent is installed: False
[08:44:33]: Info: :Info:MOMGW is installed: False
[08:44:33]: Info: :Info:MOMReporting is installed: False
[08:44:33]: Info: :Finished evaluation of rule 'PreOM12RTMRulesGroup'
[08:44:33]: Info: :Beginning evaluation of rule 'BlockPre2012SP1'
[08:44:33]: Debug: :Condition wasnt defined for rule 'BlockPre2012SP1'.
[08:44:33]: Info: :Info:OMServer is installed: False
[08:44:33]: Info: :Info:OMConsole is installed: False
[08:44:33]: Info: :Info:OMReporting is installed: False
[08:44:33]: Info: :Info:OMWebConsole is installed: False
[08:44:33]: Info: :Finished evaluation of rule 'BlockPre2012SP1'
[08:44:33]: Info: :Finished evaluation of rule 'Block Unsupported MOM versions.'
[08:44:33]: Info: :Beginning evaluation of rule 'Check that Unsupported SKU does not exist for SCOM setup.'
[08:44:33]: Debug: :Condition wasnt defined for rule 'Check that Unsupported SKU does not exist for SCOM setup.'.
[08:44:33]: Info: :Info:MOMAEM is installed: False
[08:44:33]: Info: :Info:MOMEval is installed: False
[08:44:33]: Info: :Finished evaluation of rule 'Check that Unsupported SKU does not exist for SCOM setup.'
[08:44:33]: Always: :End: Rationalize final steps.
[08:44:33]: Always: :End: Rationalize components.
[08:44:33]: Error: :Error:IsReportingValidToInstall failed SRS instance not provided
[08:44:33]: Info: :Start adding DataItems
[08:44:33]: Info: :Initial Configuration
[08:44:33]: Info: :Database Configuration
[08:44:33]: Info: :Data Warehouse Configuration
[08:44:33]: Info: :Management Server
[08:44:33]: Info: :Operations console
[08:44:33]: Info: :Web Console Server
[08:44:33]: Info: :Reporting Server
[08:44:33]: Info: :Final Configuration
[08:44:33]: Info: :Done adding DataItems
[08:44:33]: Info: :Adding Page StartPageTrack
[08:44:33]: Info: :Adding Page UpgradeInvalidStartPage
[08:44:33]: Info: :Adding Page UpgradeInvalidRootPage
[08:44:33]: Info: :Adding Page ARPStartPageSwitch
[08:44:33]: Info: :Adding Page ARPAddRemovePage
[08:44:34]: Info: :Adding Page UpgradePageSwitch
[08:44:34]: Info: :Adding Page UpgradePage
[08:44:34]: Info: :Adding Page UpgradeManagementGroupPageSwitch
[08:44:34]: Info: :Adding Page UpgradeManagementGroupPage
[08:44:34]: Info: :Adding Page UpgradeEulaPage
[08:44:34]: Info: :Adding Page RegularStartPageSwitch
[08:44:34]: Info: :Adding Page ComponentsPageCleanInstall
[08:44:34]: Info: :Adding Page ComponentsPage
[08:44:34]: Info: :Adding Page InstallationLocationPage
[08:44:34]: Info: :Adding Page PrerequisitesProgressPage
[08:44:34]: Info: :Adding Page AdditionalPrerequisitesPage
[08:44:34]: Info: :Adding Page InstallScenario
[08:44:34]: Info: :Adding Page ShortEulaPage
[08:44:34]: Info: :Adding Page SecondServerOperationalDb
[08:44:34]: Info: :Adding Page EulaPageCleanInstall
[08:44:34]: Info: :Adding Page FirstServerOperationalDb
[08:44:34]: Info: :Adding Page DbPageDataWarehouse
[08:44:34]: Info: :Adding Page SelectManagementServerForReporting
[08:44:34]: Info: :Adding Page SelectReportingInstance
[08:44:34]: Info: :Adding Page SelectManagementServerForWebConsole
[08:44:34]: Info: :Adding Page WebConsoleSitePage
[08:44:34]: Info: :Adding Page WebConsoleAuthorizationMode
[08:44:34]: Info: :Adding Page AccountsInformationPage
[08:44:34]: Info: :Adding Page ImproveUserExperiencePage
[08:44:34]: Info: :Adding Page MSFTUpdatePage
[08:44:34]: Info: :Adding Page ConfigurationSummaryPage
[08:44:34]: Info: :Adding Page ProgressPage
[08:44:34]: Info: :Adding Page BlockPage
[08:44:34]: Info: :Adding Page FinishPage
[08:44:34]: Info: :Beginning evaluation of rule 'Block Unsupported MOM versions.'
[08:44:34]: Debug: :Condition wasnt defined for rule 'Block Unsupported MOM versions.'.
[08:44:34]: Info: :Beginning evaluation of rule 'PreOM12RTMRulesGroup'
[08:44:34]: Debug: :Condition wasnt defined for rule 'PreOM12RTMRulesGroup'.
[08:44:34]: Info: :Info:MOMSelect is installed: False
[08:44:34]: Info: :Info:MOMAEM is installed: False
[08:44:34]: Info: :Info:MOMEval is installed: False
[08:44:34]: Info: :Info:MOMOEM is installed: False
[08:44:34]: Info: :Info:MOMAgent is installed: False
[08:44:34]: Info: :Info:MOMGW is installed: False
[08:44:34]: Info: :Info:MOMReporting is installed: False
[08:44:34]: Info: :Finished evaluation of rule 'PreOM12RTMRulesGroup'
[08:44:34]: Info: :Beginning evaluation of rule 'BlockPre2012SP1'
[08:44:34]: Debug: :Condition wasnt defined for rule 'BlockPre2012SP1'.
[08:44:34]: Info: :Info:OMServer is installed: False
[08:44:34]: Info: :Info:OMConsole is installed: False
[08:44:34]: Info: :Info:OMReporting is installed: False
[08:44:34]: Info: :Info:OMWebConsole is installed: False
[08:44:34]: Info: :Finished evaluation of rule 'BlockPre2012SP1'
[08:44:34]: Info: :Finished evaluation of rule 'Block Unsupported MOM versions.'
[08:44:34]: Info: :Beginning evaluation of rule 'Check that Unsupported SKU does not exist for SCOM setup.'
[08:44:34]: Debug: :Condition wasnt defined for rule 'Check that Unsupported SKU does not exist for SCOM setup.'.
[08:44:34]: Info: :Info:MOMAEM is installed: False
[08:44:34]: Info: :Info:MOMEval is installed: False
[08:44:34]: Info: :Finished evaluation of rule 'Check that Unsupported SKU does not exist for SCOM setup.'
[08:44:34]: Debug: :OMForwardToStartPageTrackPageHandler: Moving to page RegularStartPageSwitch
[08:44:34]: Always: :Entering Page: ComponentsPageCleanInstall
[08:44:34]: Info: :Server Installed:False InstallingNow:False
[08:44:34]: Error: :No Management Server property was provided and Setup could not find a valid Management Server. Please rerun setup with a valid management server.
[08:44:34]: Error: :The management server specified would lead to an invalid scenario. Setup will attempt to find a valid scenario mgt server.
[08:44:34]: Info: :Server Installed:False InstallingNow:False
[08:44:34]: Error: :No Management Server property was provided and Setup could not find a valid Management Server. Please rerun setup with a valid management server.
[08:44:37]: Info: :Server Installed:False InstallingNow:False
[08:44:37]: Error: :No Management Server property was provided and Setup could not find a valid Management Server. Please rerun setup with a valid management server.
[08:44:37]: Error: :The management server specified would lead to an invalid scenario. Setup will attempt to find a valid scenario mgt server.
[08:44:37]: Info: :Server Installed:False InstallingNow:False
[08:44:37]: Error: :No Management Server property was provided and Setup could not find a valid Management Server. Please rerun setup with a valid management server.
[08:44:38]: Info: :Server Installed:False InstallingNow:False
[08:44:38]: Error: :No Management Server property was provided and Setup could not find a valid Management Server. Please rerun setup with a valid management server.
[08:44:38]: Error: :The management server specified would lead to an invalid scenario. Setup will attempt to find a valid scenario mgt server.
[08:44:38]: Info: :Server Installed:False InstallingNow:False
[08:44:38]: Error: :No Management Server property was provided and Setup could not find a valid Management Server. Please rerun setup with a valid management server.
[08:44:39]: Info: :Server Installed:False InstallingNow:False
[08:44:39]: Error: :No Management Server property was provided and Setup could not find a valid Management Server. Please rerun setup with a valid management server.
[08:44:39]: Error: :The management server specified would lead to an invalid scenario. Setup will attempt to find a valid scenario mgt server.
[08:44:39]: Info: :Server Installed:False InstallingNow:False
[08:44:39]: Error: :No Management Server property was provided and Setup could not find a valid Management Server. Please rerun setup with a valid management server.
[08:44:41]: Info: :Server Installed:False InstallingNow:True
[08:44:42]: Info: :Server Installed:False InstallingNow:True
[08:44:42]: Always: :Entering Page: InstallationLocationPage
[08:44:44]: Info: :Info:User specified valid installation path of: C:\Program Files\Microsoft System Center 2012 R2\Operations Manager
[08:44:44]: Always: :Entering Page: PrerequisitesProgressPage
[08:44:44]: Debug: :LoadPrerequisites: Start adding ComponentTitles
[08:44:44]: Always: :LoadPrerequisites: Start adding DataItems
[08:44:44]: Always: :memoryCheckTitle
[08:44:44]: Always: :memoryCheckTitle
[08:44:44]: Always: :ntfsCheckTitle
[08:44:44]: Always: :DriveSpaceCheckTitle
[08:44:44]: Always: :DriveSpaceCheckTitle
[08:44:44]: Always: :OSVersionCheckTitle
[08:44:44]: Always: :OSVersionCheckTitle
[08:44:44]: Always: :PowershellCheckTitle
[08:44:44]: Always: :DomainControllerCheckTitle
[08:44:44]: Always: :WindowsInstallerCheckTitle
[08:44:44]: Always: :PendingRebootCheckTitle
[08:44:44]: Always: :WinRMCheckTitle
[08:44:44]: Always: :RemoteRegistryCheckTitle
[08:44:44]: Always: :ReportViewerCheckTitle
[08:44:44]: Always: :ClusteredServerCheckTitle
[08:44:44]: Always: :ActiveDirectoryCheckTitle
[08:44:44]: Always: :IsComputerNameValidTitle
[08:44:44]: Always: :SEViewerInstalledCheck
[08:44:44]: Always: :AVIcodeAgentCheck
[08:44:44]: Always: :MOMASPAgentInstalledCheck
[08:44:44]: Always: :IISCheckTitle
[08:44:44]: Always: :IISMetabaseCheckTitle
[08:44:44]: Always: :AspNetCheckTitle
[08:44:44]: Always: :WindowsAuthRoleCheckTitle
[08:44:44]: Always: :StaticContentRoleCheckTitle
[08:44:44]: Always: :DefaultDocumentRoleCheckTitle
[08:44:44]: Always: :DirectoryBrowsingRoleCheckTitle
[08:44:44]: Always: :HttpErrorsRoleCheckTitle
[08:44:44]: Always: :HttpLoggingRoleCheckTitle
[08:44:44]: Always: :RequestMonitorRoleCheckTitle
[08:44:44]: Always: :RequestFilterRoleCheckTitle
[08:44:44]: Always: :StaticContentCheckTitle
[08:44:44]: Always: :IISConsoleCheckTitle
[08:44:44]: Always: :IsapiAllowedCheckTitle
[08:44:44]: Always: :IsAspNetIntegratedHandlerInstalledTitle
[08:44:44]: Always: :HttpActivationCheckTitle
[08:44:44]: Always: :HttpActivationCheckTitle
[08:44:44]: Always: :LoadPrerequisites: Done adding prerequisites checks
[08:44:45]: Info: :Approximated Memory = 16384
[08:44:45]: Info: :Approximated Memory = 16384
[08:44:45]: Debug: :**************************************************
[08:44:45]: Debug: :<![CDATA[CheckPrerequisites: Logic Type:and MemoryCheck-2gbFail: 0CheckPrerequisites: Logic Type:and MemoryCheck-4gbWarn: 0]]>
[08:44:45]: Debug: :
[08:44:45]: Debug: :CheckPrerequisites: memoryCheckTitle: Passed
[08:44:45]: Debug: :
[08:44:45]: Debug: :**************************************************
[08:44:46]: Info: :Approximated Memory = 16384
[08:44:46]: Info: :Approximated Memory = 16384
[08:44:46]: Debug: :**************************************************
[08:44:46]: Debug: :<![CDATA[CheckPrerequisites: Logic Type:and MemoryCheck-1gbFail: 0CheckPrerequisites: Logic Type:and MemoryCheck-2gbWarn: 0]]>
[08:44:46]: Debug: :
[08:44:46]: Debug: :CheckPrerequisites: memoryCheckTitle: Passed
[08:44:46]: Debug: :
[08:44:46]: Debug: :**************************************************
[08:44:46]: Debug: :**************************************************
[08:44:46]: Debug: :<![CDATA[CheckPrerequisites: Logic Type:and NTFSDrive-Fail: 0]]>
[08:44:46]: Debug: :
[08:44:46]: Debug: :CheckPrerequisites: ntfsCheckTitle: Passed
[08:44:46]: Debug: :
[08:44:46]: Debug: :**************************************************
[08:44:46]: Debug: :**************************************************
[08:44:46]: Debug: :<![CDATA[CheckPrerequisites: Logic Type:and UIDriveSpaceCheck-Fail: 0]]>
[08:44:46]: Debug: :
[08:44:46]: Debug: :CheckPrerequisites: DriveSpaceCheckTitle: Passed
[08:44:46]: Debug: :
[08:44:46]: Debug: :**************************************************
[08:44:46]: Debug: :**************************************************
[08:44:46]: Debug: :<![CDATA[CheckPrerequisites: Logic Type:and DriveSpaceCheck-Fail: 0]]>
[08:44:46]: Debug: :
[08:44:46]: Debug: :CheckPrerequisites: DriveSpaceCheckTitle: Passed
[08:44:46]: Debug: :
[08:44:46]: Debug: :**************************************************
[08:44:46]: Debug: :**************************************************
[08:44:46]: Debug: :<![CDATA[CheckPrerequisites: Logic Type:or OSVersion-w2k8-Fail: 0]]>
[08:44:46]: Debug: :
[08:44:46]: Debug: :CheckPrerequisites: OSVersionCheckTitle: Passed
[08:44:46]: Debug: :
[08:44:46]: Debug: :**************************************************
[08:44:46]: Debug: :**************************************************
[08:44:46]: Debug: :<![CDATA[CheckPrerequisites: ProductType was not a match. Looking for: LanmanNT Found: ServerNTCheckPrerequisites: Logic Type:or OSVersion-w2k8R2-Fail: 2CheckPrerequisites: Logic Type:or OSVersion-w2k8R2-Fail: 0CheckPrerequisites:
Logic Type:and ArchitectureIs64Check-Fail: 0]]>
[08:44:46]: Debug: :
[08:44:46]: Debug: :CheckPrerequisites: OSVersionCheckTitle: Passed
[08:44:46]: Debug: :
[08:44:46]: Debug: :**************************************************
[08:44:46]: Debug: :**************************************************
[08:44:46]: Debug: :<![CDATA[CheckPrerequisites: Logic Type:and PowerShell2-Fail: 0]]>
[08:44:46]: Debug: :
[08:44:46]: Debug: :CheckPrerequisites: PowershellCheckTitle: Passed
[08:44:46]: Debug: :
[08:44:46]: Debug: :**************************************************
[08:44:46]: Debug: :**************************************************
[08:44:46]: Debug: :<![CDATA[CheckPrerequisites: ProductType was not a match. Looking for: WinNT Found: ServerNTCheckPrerequisites: Logic Type:or OSVersion-notWorkstation-warn: 1CheckPrerequisites: Logic Type:or OSVersion-notServer-warn: 0]]>
[08:44:46]: Debug: :
[08:44:46]: Debug: :CheckPrerequisites: DomainControllerCheckTitle: Passed
[08:44:46]: Debug: :
[08:44:46]: Debug: :**************************************************
[08:44:46]: Debug: :**************************************************
[08:44:46]: Debug: :<![CDATA[Successfully parsed version numbers. Required: 3.1 Actual: 5.0CheckPrerequisites: Logic Type:and WindowsInstallerVersionCheckDelegate-v31: 0]]>
[08:44:46]: Debug: :
[08:44:46]: Debug: :CheckPrerequisites: WindowsInstallerCheckTitle: Passed
[08:44:46]: Debug: :
[08:44:46]: Debug: :**************************************************
[08:44:46]: Debug: :**************************************************
[08:44:46]: Debug: :<![CDATA[CheckPrerequisites: Logic Type:and PendingReboot-Fail: 0]]>
[08:44:46]: Debug: :
[08:44:46]: Debug: :CheckPrerequisites: PendingRebootCheckTitle: Passed
[08:44:46]: Debug: :
[08:44:46]: Debug: :**************************************************
[08:44:46]: Debug: :ServiceControlFunctions.IsEnabledAndRunning(): Starting...
[08:44:46]: Debug: :IsServiceInstalled: WinRM? True.
[08:44:46]: Debug: :**************************************************
[08:44:46]: Debug: :<![CDATA[CheckPrerequisites: Logic Type:and ServiceCheck-WinRM: 0]]>
[08:44:46]: Debug: :
[08:44:46]: Debug: :CheckPrerequisites: WinRMCheckTitle: Passed
[08:44:46]: Debug: :
[08:44:46]: Debug: :**************************************************
[08:44:46]: Debug: :IsServiceInstalled: RemoteRegistry? True.
[08:44:46]: Debug: :ServiceControlFunctions.IsEnabledAndRunning(): Starting...
[08:44:46]: Debug: :IsServiceInstalled: RemoteRegistry? True.
[08:44:46]: Debug: :ServiceControlFunctions.IsEnabledAndRunning(): Checking second time because first time result was False.
[08:44:46]: Debug: :IsServiceInstalled: RemoteRegistry? True.
[08:44:46]: Debug: :**************************************************
[08:44:46]: Debug: :<![CDATA[CheckPrerequisites: Logic Type:and PassIfWin8Anything: 0CheckPrerequisites: Logic Type:and ServiceCheck-WinRM-enabled: 0CheckPrerequisites: Logic Type:or ServiceCheck-WinRM-running: 2]]>
[08:44:46]: Debug: :
[08:44:46]: Debug: :CheckPrerequisites: RemoteRegistryCheckTitle: Passed
[08:44:46]: Debug: :
[08:44:46]: Debug: :**************************************************
[08:44:46]: Info: :Version Installed=11.1.3452.0
[08:44:46]: Debug: :**************************************************
[08:44:46]: Debug: :<![CDATA[CheckPrerequisites: Logic Type:and ReportViewer: 0]]>
[08:44:46]: Debug: :
[08:44:46]: Debug: :CheckPrerequisites: ReportViewerCheckTitle: Passed
[08:44:46]: Debug: :
[08:44:46]: Debug: :**************************************************
[08:44:46]: Debug: :**************************************************
[08:44:46]: Debug: :<![CDATA[CheckPrerequisites: Logic Type:and ClusteredMachineCheck: 0]]>
[08:44:46]: Debug: :
[08:44:46]: Debug: :CheckPrerequisites: ClusteredServerCheckTitle: Passed
[08:44:46]: Debug: :
[08:44:46]: Debug: :**************************************************
[08:44:46]: Debug: :**************************************************
[08:44:46]: Debug: :<![CDATA[CheckPrerequisites: Logic Type:and ADCheck-Fail: 0]]>
[08:44:46]: Debug: :
[08:44:46]: Debug: :CheckPrerequisites: ActiveDirectoryCheckTitle: Passed
[08:44:46]: Debug: :
[08:44:46]: Debug: :**************************************************
[08:44:46]: Debug: :**************************************************
[08:44:46]: Debug: :<![CDATA[IsComputerNameValid: Hostname: SCOM01 Len: 6CheckPrerequisites: Logic Type:and IsComputerNameValid: 0]]>
[08:44:46]: Debug: :
[08:44:46]: Debug: :CheckPrerequisites: IsComputerNameValidTitle: Passed
[08:44:46]: Debug: :
[08:44:46]: Debug: :**************************************************
[08:44:46]: Debug: :**************************************************
[08:44:46]: Debug: :<![CDATA[CheckPrerequisites: Logic Type:and Se-ViewerInstalled-x86: 0CheckPrerequisites: Logic Type:and Se-ViewerInstalled-x64: 0]]>
[08:44:46]: Debug: :
[08:44:46]: Debug: :CheckPrerequisites: SEViewerInstalledCheck: Passed
[08:44:46]: Debug: :
[08:44:46]: Debug: :**************************************************
[08:44:46]: Debug: :**************************************************
[08:44:46]: Debug: :<![CDATA[CheckPrerequisites: Logic Type:and AvicodeAgentInstalled-x86: 0CheckPrerequisites: Logic Type:and AvicodeAgentInstalled-x64: 0]]>
[08:44:46]: Debug: :
[08:44:46]: Debug: :CheckPrerequisites: AVIcodeAgentCheck: Passed
[08:44:46]: Debug: :
[08:44:46]: Debug: :**************************************************
[08:44:46]: Debug: :**************************************************
[08:44:46]: Debug: :<![CDATA[CheckPrerequisites: Logic Type:and W3SVC: 0]]>
[08:44:46]: Debug: :
[08:44:46]: Debug: :CheckPrerequisites: IISCheckTitle: Passed
[08:44:46]: Debug: :
[08:44:46]: Debug: :**************************************************
[08:44:46]: Debug: :**************************************************
[08:44:46]: Debug: :<![CDATA[CheckPrerequisites: Logic Type:and Metabase: 0]]>
[08:44:46]: Debug: :
[08:44:46]: Debug: :CheckPrerequisites: IISMetabaseCheckTitle: Passed
[08:44:46]: Debug: :
[08:44:46]: Debug: :**************************************************
[08:44:46]: Debug: :**************************************************
[08:44:46]: Debug: :<![CDATA[CheckPrerequisites: Logic Type:and ASPNET: 0]]>
[08:44:46]: Debug: :
[08:44:46]: Debug: :CheckPrerequisites: AspNetCheckTitle: Passed
[08:44:46]: Debug: :
[08:44:46]: Debug: :**************************************************
[08:44:46]: Debug: :**************************************************
[08:44:46]: Debug: :<![CDATA[CheckPrerequisites: Logic Type:and WindowsAuthentication: 0]]>
[08:44:46]: Debug: :
[08:44:46]: Debug: :CheckPrerequisites: WindowsAuthRoleCheckTitle: Passed
[08:44:46]: Debug: :
[08:44:46]: Debug: :**************************************************
[08:44:46]: Debug: :**************************************************
[08:44:46]: Debug: :<![CDATA[CheckPrerequisites: Logic Type:and StaticContent: 0]]>
[08:44:46]: Debug: :
[08:44:46]: Debug: :CheckPrerequisites: StaticContentRoleCheckTitle: Passed
[08:44:46]: Debug: :
[08:44:46]: Debug: :**************************************************
[08:44:46]: Debug: :**************************************************
[08:44:46]: Debug: :<![CDATA[CheckPrerequisites: Logic Type:and DefaultDocument: 0]]>
[08:44:46]: Debug: :
[08:44:46]: Debug: :CheckPrerequisites: DefaultDocumentRoleCheckTitle: Passed
[08:44:46]: Debug: :
[08:44:46]: Debug: :**************************************************
[08:44:46]: Debug: :**************************************************
[08:44:46]: Debug: :<![CDATA[CheckPrerequisites: Logic Type:and DirectoryBrowse: 0]]>
[08:44:46]: Debug: :
[08:44:46]: Debug: :CheckPrerequisites: DirectoryBrowsingRoleCheckTitle: Passed
[08:44:46]: Debug: :
[08:44:46]: Debug: :**************************************************
[08:44:46]: Debug: :**************************************************
[08:44:46]: Debug: :<![CDATA[CheckPrerequisites: Logic Type:and HttpErrors: 0]]>
[08:44:46]: Debug: :
[08:44:46]: Debug: :CheckPrerequisites: HttpErrorsRoleCheckTitle: Passed
[08:44:46]: Debug: :
[08:44:46]: Debug: :**************************************************
[08:44:46]: Debug: :**************************************************
[08:44:46]: Debug: :<![CDATA[CheckPrerequisites: Logic Type:and HttpLogging: 0]]>
[08:44:46]: Debug: :
[08:44:46]: Debug: :CheckPrerequisites: HttpLoggingRoleCheckTitle: Passed
[08:44:46]: Debug: :
[08:44:46]: Debug: :**************************************************
[08:44:46]: Debug: :**************************************************
[08:44:46]: Debug: :<![CDATA[CheckPrerequisites: Logic Type:and RequestMonitor: 0]]>
[08:44:46]: Debug: :
[08:44:46]: Debug: :CheckPrerequisites: RequestMonitorRoleCheckTitle: Passed
[08:44:46]: Debug: :
[08:44:46]: Debug: :**************************************************
[08:44:46]: Debug: :**************************************************
[08:44:46]: Debug: :<![CDATA[CheckPrerequisites: Logic Type:and RequestFiltering: 0]]>
[08:44:46]: Debug: :
[08:44:46]: Debug: :CheckPrerequisites: RequestFilterRoleCheckTitle: Passed
[08:44:46]: Debug: :
[08:44:46]: Debug: :**************************************************
[08:44:46]: Debug: :**************************************************
[08:44:46]: Debug: :<![CDATA[CheckPrerequisites: Logic Type:and HttpCompressionStatic: 0]]>
[08:44:46]: Debug: :
[08:44:46]: Debug: :CheckPrerequisites: StaticContentCheckTitle: Passed
[08:44:46]: Debug: :
[08:44:46]: Debug: :**************************************************
[08:44:46]: Debug: :**************************************************
[08:44:46]: Debug: :<![CDATA[CheckPrerequisites: Logic Type:and ManagementConsole: 0]]>
[08:44:46]: Debug: :
[08:44:46]: Debug: :CheckPrerequisites: IISConsoleCheckTitle: Passed
[08:44:46]: Debug: :
[08:44:46]: Debug: :**************************************************
[08:44:47]: Debug: :**************************************************
[08:44:47]: Debug: :<![CDATA[CheckPrerequisites: Logic Type:and IsapiCgiAllowed: 0]]>
[08:44:47]: Debug: :
[08:44:47]: Debug: :CheckPrerequisites: IsapiAllowedCheckTitle: Passed
[08:44:47]: Debug: :
[08:44:47]: Debug: :**************************************************
[08:44:47]: Debug: :**************************************************
[08:44:47]: Debug: :<![CDATA[Found the ASP.NET PageHandler Factory for v4CheckPrerequisites: Logic Type:and IsAspNetIntegratedHandlerInstalled: 0]]>
[08:44:47]: Debug: :
[08:44:47]: Debug: :CheckPrerequisites: IsAspNetIntegratedHandlerInstalledTitle: Passed
[08:44:47]: Debug: :
[08:44:47]: Debug: :**************************************************
[08:44:47]: Debug: :**************************************************
[08:44:47]: Debug: :<![CDATA[CheckPrerequisites: Logic Type:or HttpAuthorizationCheck: 2CheckPrerequisites: Logic Type:or OSVersion-NewerThan2k8R2: 0]]>
[08:44:47]: Debug: :
[08:44:47]: Debug: :CheckPrerequisites: HttpActivationCheckTitle: Passed
[08:44:47]: Debug: :
[08:44:47]: Debug: :**************************************************
[08:44:47]: Debug: :**************************************************
[08:44:47]: Debug: :<![CDATA[CheckPrerequisites: Logic Type:or HttpAuthorizationCheck: 0CheckPrerequisites: The value 6.2.9200.0 was not within the range 0.0.0.0 to 6.2.0.0.CheckPrerequisites: Logic Type:or OSVersion-w2k12-Fail: 2]]>
[08:44:47]: Debug: :
[08:44:47]: Debug: :CheckPrerequisites: HttpActivationCheckTitle: Passed
[08:44:47]: Debug: :
[08:44:47]: Debug: :**************************************************
[08:44:47]: Info: :Beginning evaluation of rule 'Block installation of SCOM.'
[08:44:47]: Debug: :Condition wasnt defined for rule 'Block installation of SCOM.'.
[08:44:47]: Info: :Beginning evaluation of rule 'SCOMSetupRulesGroup'
[08:44:47]: Debug: :Condition wasnt defined for rule 'SCOMSetupRulesGroup'.
[08:44:47]: Info: :Info:MOMASPAgent is installed: False
[08:44:47]: Info: :Finished evaluation of rule 'SCOMSetupRulesGroup'
[08:44:47]: Info: :Finished evaluation of rule 'Block installation of SCOM.'
[08:44:47]: Debug: :**************************************************
[08:44:47]: Debug: :<![CDATA[CheckPrerequisites: Logic Type:and MOMASPAgent: 0]]>
[08:44:47]: Debug: :
[08:44:47]: Debug: :CheckPrerequisites: MOMASPAgentInstalledCheck: Passed
[08:44:47]: Debug: :
[08:44:47]: Debug: :**************************************************
[08:44:47]: Always: :CheckPrerequisites: Return Value 0
[08:44:47]: Always: :Entering Page: AdditionalPrerequisitesPage
[08:44:49]: Always: :Entering Page: InstallScenario
[08:45:00]: Always: :Entering Page: EulaPageCleanInstall
[08:45:00]: Always: :Displaying localized EULA for localization: en
[08:45:00]: Always: :Displaying Eula: C:\Users\Administrator.domain\AppData\Local\SCOM\Setup\en\eula_en_eval.rtf
[08:45:03]: Info: :Info:User has agreed to EULA.
[08:45:04]: Info: :Not all of the information on the screen is valid, so we're not going to check disk space.
[08:45:04]: Info: :Not all of the information on the screen is valid, so we're not going to check disk space.
[08:45:04]: Always: :Entering Page: FirstServerOperationalDb
[08:45:04]: Info: :Not all of the information on the screen is valid, so we're not going to check disk space.
[08:45:04]: Info: :Not all of the information on the screen is valid, so we're not going to check disk space.
[08:45:11]: Always: :DatabaseConfigurationPage: Attempting to connect to database using server\instance SCOMDB01\SCOMDB01. If we need it, the port is 1433
[08:45:11]: Debug: :MSSQL$SCOMDB01 on server SCOMDB01 is in a running state
[08:45:11]: Info: :Info:Opening/Testing Sql Connection on SCOMDB01\SCOMDB01, port:
[08:45:11]: Debug: :Connection was not open. We will try to open it.
[08:45:12]: Debug: :SqlConnectionReady returned True.
[08:45:12]: Debug: :MSSQL$SCOMDB01 on server SCOMDB01 is in a running state
[08:45:12]: Debug: :Connection was not open. We will try to open it.
[08:45:12]: Debug: :SqlConnectionReady returned True.
[08:45:12]: Info: :Info:Using DB command timeout = 1800 seconds.
[08:45:12]: Info: :SQL Product Level: SP2
[08:45:12]: Info: :SQL Edition: Business Intelligence Edition (64-bit)
[08:45:12]: Info: :SQL Version: 11.0.5058.0
[08:45:12]: Always: :Could not find a match for Business Intelligence Edition (64-bit) edition of SQL.
[08:45:12]: Always: :Current Version of SQL=11.0.5058.0 Required Version=10.50.2500.0
[08:45:12]: Always: :Entering GetRemoteOSVersion.
[08:45:12]: Info: :Info: remoteOS = 6.3.9600
[08:45:12]: Info: :Info:Using DB command timeout = 1800 seconds.
[08:45:12]: Info: :Info:Using DB command timeout = 1800 seconds.
[08:45:12]: Info: :The SQL Collation is valid.
[08:45:12]: Info: :Info:Using DB command timeout = 1800 seconds.
[08:45:12]: Debug: :MSSQL$SCOMDB01 on server SCOMDB01 is in a running state
[08:45:12]: Debug: :Connection was not open. We will try to open it.
[08:45:12]: Debug: :SqlConnectionReady returned True.
[08:45:12]: Info: :Info:DatabaseConfigurationPage: DB connection attempt completed.
[08:45:12]: Info: :Info:DatabaseConfigurationPage: DB connection attempt completed.
[08:45:12]: Debug: :MSSQL$SCOMDB01 on server SCOMDB01 is in a running state
[08:45:12]: Debug: :Connection was not open. We will try to open it.
[08:45:12]: Debug: :SqlConnectionReady returned True.
[08:45:12]: Info: :Info:Using DB command timeout = 1800 seconds.
[08:45:12]: Info: :Not all of the information on the screen is valid, so we're not going to check disk space.
[08:45:12]: Info: :Not all of the information on the screen is valid, so we're not going to check disk space.
[08:45:12]: Debug: :MSSQL$SCOMDB01 on server SCOMDB01 is in a running state
[08:45:12]: Debug: :Connection was not open. We will try to open it.
[08:45:12]: Debug: :SqlConnectionReady returned True.
[08:45:12]: Info: :Info:Using DB command timeout = 1800 seconds.
[08:45:12]: Info: :Info:Using DB command timeout = 1800 seconds.
[08:45:12]: Info: :Checking freespace for: SCOMDB01,D:\
[08:45:12]: Always: :CheckUsedSpaceOnDrive: Checking for space on drive SCOMDB01,D:\
[08:45:12]: Info: :CheckUsedSpaceOnDrive succeeded.
[08:45:12]: Info: :Checking freespace for: SCOMDB01,E:\
[08:45:12]: Always: :CheckUsedSpaceOnDrive: Checking for space on drive SCOMDB01,E:\
[08:45:12]: Info: :CheckUsedSpaceOnDrive succeeded.
[08:45:12]: Info: :Checking freespace for: SCOMDB01,D:\
[08:45:12]: Always: :CheckUsedSpaceOnDrive: Checking for space on drive SCOMDB01,D:\
[08:45:12]: Info: :CheckUsedSpaceOnDrive succeeded.
[08:45:12]: Info: :Checking freespace for: SCOMDB01,E:\
[08:45:12]: Always: :CheckUsedSpaceOnDrive: Checking for space on drive SCOMDB01,E:\
[08:45:12]: Info: :CheckUsedSpaceOnDrive succeeded.
[08:45:12]: Info: :Checking freespace for: SCOMDB01,D:\
[08:45:12]: Always: :CheckUsedSpaceOnDrive: Checking for space on drive SCOMDB01,D:\
[08:45:12]: Info: :CheckUsedSpaceOnDrive succeeded.
[08:45:12]: Info: :Checking freespace for: SCOMDB01,E:\
[08:45:12]: Always: :CheckUsedSpaceOnDrive: Checking for space on drive SCOMDB01,E:\
[08:45:12]: Info: :CheckUsedSpaceOnDrive succeeded.
[08:45:12]: Info: :Checking freespace for: SCOMDB01,D:\
[08:45:12]: Always: :CheckUsedSpaceOnDrive: Checking for space on drive SCOMDB01,D:\
[08:45:12]: Info: :CheckUsedSpaceOnDrive succeeded.
[08:45:12]: Info: :Checking freespace for: SCOMDB01,E:\
[08:45:12]: Always: :CheckUsedSpaceOnDrive: Checking for space on drive SCOMDB01,E:\
[08:45:12]: Info: :CheckUsedSpaceOnDrive succeeded.
[08:45:13]: Info: :Checking freespace for: SCOMDB01,D:\
[08:45:13]: Always: :CheckUsedSpaceOnDrive: Checking for space on drive SCOMDB01,D:\
[08:45:13]: Info: :CheckUsedSpaceOnDrive succeeded.
[08:45:13]: Info: :Checking freespace for: SCOMDB01,E:\
[08:45:13]: Always: :CheckUsedSpaceOnDrive: Checking for space on drive SCOMDB01,E:\
[08:45:13]: Info: :CheckUsedSpaceOnDrive succeeded.
[08:45:13]: Info: :Checking freespace for: SCOMDB01,D:\
[08:45:13]: Always: :CheckUsedSpaceOnDrive: Checking for space on drive SCOMDB01,D:\
[08:45:13]: Info: :CheckUsedSpaceOnDrive succeeded.
[08:45:13]: Info: :Checking freespace for: SCOMDB01,E:\
[08:45:13]: Always: :CheckUsedSpaceOnDrive: Checking for space on drive SCOMDB01,E:\
[08:45:13]: Info: :CheckUsedSpaceOnDrive succeeded.
[08:45:15]: Info: :Checking freespace for: SCOMDB01,D:\
[08:45:15]: Always: :CheckUsedSpaceOnDrive: Checking for space on drive SCOMDB01,D:\
[08:45:15]: Info: :CheckUsedSpaceOnDrive succeeded.
[08:45:15]: Info: :Checking freespace for: SCOMDB01,E:\
[08:45:15]: Always: :CheckUsedSpaceOnDrive: Checking for space on drive SCOMDB01,E:\
[08:45:15]: Info: :CheckUsedSpaceOnDrive succeeded.
[08:45:15]: Always: :Connected to SCOMDB01\SCOMDB01 without using the port number.
[08:45:15]: Info: :Info:DatabaseConfigurationPage: Attempting to connect to database using server\instance SCOMDB01\SCOMDB01 and port 1433
[08:45:15]: Info: :Info:Opening/Testing Sql Connection on SCOMDB01\SCOMDB01, port:
[08:45:15]: Debug: :Connection was not open. We will try to open it.
[08:45:15]: Debug: :SqlConnectionReady returned True.
[08:45:15]: Debug: :MSSQL$SCOMDB01 on server SCOMDB01 is in a running state
[08:45:15]: Debug: :Connection was not open. We will try to open it.
[08:45:15]: Debug: :SqlConnectionReady returned True.
[08:45:15]: Info: :Info:Using DB command timeout = 1800 seconds.
[08:45:15]: Info: :SQL Product Level: SP2
[08:45:15]: Info: :SQL Edition: Business Intelligence Edition (64-bit)
[08:45:15]: Info: :SQL Version: 11.0.5058.0
[08:45:15]: Always: :Could not find a match for Business Intelligence Edition (64-bit) edition of SQL.
[08:45:15]: Always: :Current Version of SQL=11.0.5058.0 Required Version=10.50.2500.0
[08:45:15]: Debug: :MSSQL$SCOMDB01 on server SCOMDB01 is in a running state
[08:45:15]: Debug: :Connection was not open. We will try to open it.
[08:45:15]: Debug: :SqlConnectionReady returned True.
[08:45:15]: Info: :Info:Using DB command timeout = 1800 seconds.
[08:45:15]: Info: :SQL Product Level: SP2
[08:45:15]: Info: :SQL Edition: Business Intelligence Edition (64-bit)
[08:45:15]: Info: :SQL Version: 11.0.5058.0
[08:45:15]: Always: :Could not find a match for Business Intelligence Edition (64-bit) edition of SQL.
[08:45:15]: Error: :IsValidSQLInstance: Sql None edition is not supported.
[08:45:15]: Error: :Error:DB Config Page: Invalid Sql Instance.
[08:45:15]: Info: :Info:DatabaseConfigurationPage: DB connection attempt completed.
[08:45:15]: Info: :Info:DatabaseConfigurationPage: DB connection attempt completed.
[08:45:22]: Info: :The user canceled setup
[08:45:22]: Always: :Begin: Property bag dump.
[08:45:22]: Always: :SetupStartTime = 07.11.2014 08:44:33
[08:45:22]: Always: :Collection ProtectedProperties (System.Collections.ArrayList):
[08:45:22]: Always: : [0] = ActionAccountPassword
[08:45:22]: Always: : [1] = DASAccountPassword
[08:45:22]: Always: :DefaultLogName = C:\Users\Administrator.domain\AppData\Local\SCOM\Logs\OpsMgrSetupWizard.log
[08:45:22]: Always: :DefaultLogPath = C:\Users\Administrator.domain\AppData\Local\SCOM\Logs
[08:45:22]: Always: :path = C:\SC2012 R2 SCOM\Setup\AMD64\
[08:45:22]: Always: :setupexepath = C:\Users\Administrator.domain\AppData\Local\SCOM\Setup
[08:45:22]: Always: :ArchitectureIs64Check = True
[08:45:22]: Always: :Collection ListOfSupportedComponents (System.Collections.ArrayList):
[08:45:22]: Always: : [0] = OMCONSOLE
[08:45:22]: Always: : [1] = OMSERVER
[08:45:22]: Always: : [2] = OMWEBCONSOLE
[08:45:22]: Always: : [3] = OMREPORTING
[08:45:22]: Always: :install = 1
[08:45:22]: Always: :installpath = C:\Program Files\Microsoft System Center 2012 R2\Operations Manager
[08:45:22]: Always: :EulaFilesPath = C:\Users\Administrator.domain\AppData\Local\SCOM\Setup
[08:45:22]: Always: :HealthServiceTypeId = AB4C891F-3359-3FB6-0704-075FBFE36710
[08:45:22]: Always: :hsPort = C51B7833-DA54-1653-D8FD-1A738EF8DED5
[08:45:22]: Always: :ScreensLoaded = 1
[08:45:22]: Always: :Collection ListOfSelectedComponents (System.Collections.ArrayList):
[08:45:22]: Always: : [0] = OMREPORTING
[08:45:22]: Always: : [1] = OMWEBCONSOLE
[08:45:22]: Always: : [2] = OMCONSOLE
[08:45:22]: Always: : [3] = OMSERVER
[08:45:22]: Always: :OMREPORTING = 1
[08:45:22]: Always: :OMWEBCONSOLE = 1
[08:45:22]: Always: :OMCONSOLE = 1
[08:45:22]: Always: :OMSERVER = 1
[08:45:22]: Always: :ManagementServer = SCOM01.domain.local
[08:45:22]: Always: :SelectDatabaseInstanceReloadScreenInformation = 1
[08:45:22]: Always: :ReloadPrerequisitesPageChoice = PrerequisitesProgressPage
[08:45:22]: Always: :LoadedPrerequisiteXmlFile = True
[08:45:22]: Always: :PrerequisitesCheckXMLLoaded = True
[08:45:22]: Always: :CountFilteredPrerequisites_Failed = 0
[08:45:22]: Always: :CountFilteredPrerequisites_Warning = 0
[08:45:22]: Always: :CountFilteredPrerequisites_PassedWithChoices = 0
[08:45:22]: Always: :CountFilteredPrerequisites_Passed = 37
[08:45:22]: Always: :PrerequisiteState = Passed
[08:45:22]: Always: :XmlFilteredPrerequisites_Passed : Begin XML property
[08:45:22]: Always: :<?xml version="1.0" encoding="utf-8"?><Root><Title TitleText="OMSERVER"><Detail state="Passed" image="pack://application:,,,/SetupChainerUI;component/GreenCheck.png"
name="memoryCheckTitle" descriptionBody="" descriptionTitle="serverMemCheckPassed" resolution="serverMemCheckResolution" /><Detail state="Passed" image="pack://application:,,,/SetupChainerUI;component/GreenCheck.png"
name="ntfsCheckTitle" descriptionBody="" descriptionTitle="ntfsCheckPassed" resolution="ntfsCheckResolution" /><Detail state="Passed" image="pack://application:,,,/SetupChainerUI;component/GreenCheck.png"
name="DriveSpaceCheckTitle" descriptionBody="" descriptionTitle="ServerDriveSpaceCheckPassed" resolution="ServerDriveSpaceCheckResolution" /><Detail state="Passed" image="pack://application:,,,/SetupChainerUI;component/GreenCheck.png"
name="OSVersionCheckTitle" descriptionBody="" descriptionTitle="OSVersionCheckPassed" resolution="OSVersionCheckResolution" /><Detail state="Passed" image="pack://application:,,,/SetupChainerUI;component/GreenCheck.png"
name="PowershellCheckTitle" descriptionBody="" descriptionTitle="PowershellCheckPassed" resolution="PowerShellCheckResolution" /><Detail state="Passed" image="pack://application:,,,/SetupChainerUI;component/GreenCheck.png"
name="DomainControllerCheckTitle" descriptionBody="" descriptionTitle="DomainControllerCheckPassed" resolution="DomainControllerCheckResolution" /><Detail state="Passed" image="pack://application:,,,/SetupChainerUI;component/GreenCheck.png"
name="WindowsInstallerCheckTitle" descriptionBody="" descriptionTitle="WindowsInstallerCheckPassed" resolution="WindowsInstallerCheckResolution" /><Detail state="Passed" image="pack://application:,,,/SetupChainerUI;component/GreenCheck.png"
name="PendingRebootCheckTitle" descriptionBody="" descriptionTitle="PendingRebootCheckPassed" resolution="PendingRebootCheckResolution" /><Detail state="Passed" image="pack://application:,,,/SetupChainerUI;component/GreenCheck.png"
name="WinRMCheckTitle" descriptionBody="" descriptionTitle="WinRMCheckPassed" resolution="WinRMCheckResolution" /><Detail state="Passed" image="pack://application:,,,/SetupChainerUI;component/GreenCheck.png"
name="RemoteRegistryCheckTitle" descriptionBody="" descriptionTitle="RemoteRegistryCheckPassed" resolution="RemoteRegistryCheckResolution" /><Detail state="Passed" image="pack://application:,,,/SetupChainerUI;component/GreenCheck.png"
name="ClusteredServerCheckTitle" descriptionBody="" descriptionTitle="ClusteredServerCheckPassed" resolution="ClusteredServerCheckResolution" /><Detail state="Passed" image="pack://application:,,,/SetupChainerUI;component/GreenCheck.png"
name="ActiveDirectoryCheckTitle" descriptionBody="" descriptionTitle="ActiveDirectoryCheckPassed" resolution="ActiveDirectoryCheckResolution" /><Detail state="Passed" image="pack://application:,,,/SetupChainerUI;component/GreenCheck.png"
name="IsComputerNameValidTitle" descriptionBody="" descriptionTitle="IsComputerNameValidPassed" resolution="IsComputerNameValidResolution" /><Detail state="Passed" image="pack://application:,,,/SetupChainerUI;component/GreenCheck.png"
name="AVIcodeAgentCheck" descriptionBody="" descriptionTitle="AVICodeAgentCheckPassed" resolution="AVICodeAgentCheckResolution" /><Detail state="Passed" image="pack://application:,,,/SetupChainerUI;component/GreenCheck.png"
name="MOMASPAgentInstalledCheck" descriptionBody="" descriptionTitle="MOMASPAgentCheckPassed" resolution="MOMASPAgentResolution" /></Title><Title TitleText="OMCONSOLE"><Detail state="Passed"
image="pack://application:,,,/SetupChainerUI;component/GreenCheck.png" name="DriveSpaceCheckTitle" descriptionBody="" descriptionTitle="ConsoleDriveSpaceCheckPassed" resolution="ConsoleDriveSpaceCheckResolution"
/><Detail state="Passed" image="pack://application:,,,/SetupChainerUI;component/GreenCheck.png" name="OSVersionCheckTitle" descriptionBody="" descriptionTitle="OSVersionCheckPassed" resolution="OSVersionCheckResolution"
/><Detail state="Passed" image="pack://application:,,,/SetupChainerUI;component/GreenCheck.png" name="ReportViewerCheckTitle" descriptionBody="" descriptionTitle="ReportViewerCheckPassed" resolution="ReportViewerCheckResolution"
/></Title><Title TitleText="OMWEBCONSOLE"><Detail state="Passed" image="pack://application:,,,/SetupChainerUI;component/GreenCheck.png" name="SEViewerInstalledCheck" descriptionBody="" descriptionTitle="SeViewerInstalledCheckPassed"
resolution="SeViewerInstalledCheckResolution" /><Detail state="Passed" image="pack://application:,,,/SetupChainerUI;component/GreenCheck.png" name="IISCheckTitle" descriptionBody="" descriptionTitle="IISCheckPassed"
resolution="IISCheckResolution" /><Detail state="Passed" image="pack://application:,,,/SetupChainerUI;component/GreenCheck.png" name="IISMetabaseCheckTitle" descriptionBody="" descriptionTitle="IISMetabaseCheckPassed"
resolution="IISMetabaseCheckResolution" /><Detail state="Passed" image="pack://application:,,,/SetupChainerUI;component/GreenCheck.png" name="AspNetCheckTitle" descriptionBody="" descriptionTitle="AspNetCheckPassed"
resolution="AspNetCheckResolution" /><Detail state="Passed" image="pack://application:,,,/SetupChainerUI;component/GreenCheck.png" name="WindowsAuthRoleCheckTitle" descriptionBody="" descriptionTitle="WindowsAuthRoleCheckPassed"
resolution="WindowsAuthRoleCheckResolution" /><Detail state="Passed" image="pack://application:,,,/SetupChainerUI;component/GreenCheck.png" name="StaticContentRoleCheckTitle" descriptionBody="" descriptionTitle="StaticContentRoleCheckPassed"
resolution="StaticContentRoleCheckResolution" /><Detail state="Passed" image="pack://application:,,,/SetupChainerUI;component/GreenCheck.png" name="DefaultDocumentRoleCheckTitle" descriptionBody="" descriptionTitle="DefaultDocumentRoleCheckPassed"
resolution="DefaultDocumentRoleCheckResolution" /><Detail state="Passed" image="pack://application:,,,/SetupChainerUI;component/GreenCheck.png" name="DirectoryBrowsingRoleCheckTitle" descriptionBody=""
descriptionTitle="DirectoryBrowsingRoleCheckPassed" resolution="DirectoryBrowsingRoleCheckResolution" /><Detail state="Passed" image="pack://application:,,,/SetupChainerUI;component/GreenCheck.png" name="HttpErrorsRoleCheckTitle"
descriptionBody="" descriptionTitle="HttpErrorsRoleCheckPassed" resolution="HttpErrorsRoleCheckResolution" /><Detail state="Passed" image="pack://application:,,,/SetupChainerUI;component/GreenCheck.png"
name="HttpLoggingRoleCheckTitle" descriptionBody="" descriptionTitle="HttpLoggingRoleCheckPassed" resolution="HttpLoggingRoleCheckResolution" /><Detail state="Passed" image="pack://application:,,,/SetupChainerUI;component/GreenCheck.png"
name="RequestMonitorRoleCheckTitle" descriptionBody="" descriptionTitle="RequestMonitorRoleCheckPassed" resolution="RequestMonitorRoleCheckResolution" /><Detail state="Passed" image="pack://application:,,,/SetupChainerUI;component/GreenCheck.png"
name="RequestFilterRoleCheckTitle" descriptionBody="" descriptionTitle="RequestFilterRoleCheckPassed" resolution="RequestFilterRoleCheckResolution" /><Detail state="Passed" image="pack://application:,,,/SetupChainerUI;component/GreenCheck.png"
name="StaticContentCheckTitle" descriptionBody="" descriptionTitle="StaticContentCheckPassed" resolution="StaticContentCheckResolution" /><Detail state="Passed" image="pack://application:,,,/SetupChainerUI;component/GreenCheck.png"
name="IISConsoleCheckTitle" descriptionBody="" descriptionTitle="IISConsoleCheckPassed" resolution="IISConsoleCheckResolution" /><Detail state="Passed" image="pack://application:,,,/SetupChainerUI;component/GreenCheck.png"
name="IsapiAllowedCheckTitle" descriptionBody="" descriptionTitle="IsapiAllowedCheckPassed" resolution="IsapiAllowedCheckResolution" /><Detail state="Passed" image="pack://application:,,,/SetupChainerUI;component/GreenCheck.png"
name="IsAspNetIntegratedHandlerInstalledTitle" descriptionBody="" descriptionTitle="IsAspNetIntegratedHandlerInstalledPassed" resolution="IsAspNetIntegratedHandlerInstalledResolution" /><Detail state="Passed"
image="pack://application:,,,/SetupChainerUI;component/GreenCheck.png" name="HttpActivationCheckTitle" descriptionBody="" descriptionTitle="HttpActivationCheckPassed" resolution="HttpActivationCheckResolution"
/><Detail state="Passed" image="pack://application:,,,/SetupChainerUI;component/GreenCheck.png" name="HttpActivationCheckTitle" descriptionBody="" descriptionTitle="HttpActivation45RoleCheckPassed" resolution="HttpActivation45RoleCheckResolution"
/></Title><Title TitleText="OMREPORTING"><Detail state="Passed" image="pack://application:,,,/SetupChainerUI;component/GreenCheck.png" name="memoryCheckTitle" descriptionBody="" descriptionTitle="ReportingMemCheckPassed"
resolution="ReportingMemCheckResolution" /></Title></Root>
[08:45:22]: Always: :End XML property
[08:45:22]: Always: :UserSelectedInstallType = FirstServer
[08:45:22]: Always: :ManagementGroupName = domain Management Group
[08:45:22]: Always: :SqlServerInstance = SCOMDB01\SCOMDB01
[08:45:22]: Always: :DatabaseName = OperationsManager
[08:45:22]: Always: :DatabaseSize = 1000
[08:45:22]: Always: :DatabaseLogPath = E:\Program Files\Microsoft SQL Server\MSSQL11.SCOMDB01\MSSQL\Data
[08:45:22]: Always: :DatabasePath = D:\Program Files\Microsoft SQL Server\MSSQL11.SCOMDB01\MSSQL\DATA\
[08:45:22]: Always: :DbMode = New
[08:45:22]: Always: :InvalidSQLReason = SQL Server None edition cannot be used.
[08:45:22]: Always: :UserCanceledInstall = 1
[08:45:22]: Always: :InstallSuccess = 1
[08:45:22]: Always: :End: Property bag dump.
[08:45:22]: Debug: :CEIP disabled. CEIP data will NOT be sent.
[08:45:22]: Always: :Application Ended: Successful
[08:45:22]: Always: :
[2014-11-07T08:45:22.6484495+01:00]: Always: Trace Session Ended
</Quote>
I've even highlighted in Bold what it's moaning about so can we please for gods sake cut it down already? I do know SQL Server, I've been working with OM for years I don't need to be told to disable the Firewall, I can read and think through Errors so how about
going back to my second post on this thread: Either fix that XML file or get me some proper install media? -
Unable to install SQL Server Express 2008 R2 - Errors "Failed to retrieve data for this request"
As domain admin I am attempting to install "SQL Server 2008 R2 with SP2" but it keeps failing with "Failed to retrieve data for this request".
The installation never actually starts, it errors before then.
It displays the same error even if I run the System Configuration Checker.
The summary.txt for the install displays the following text:
Overall summary:
Final result: Failed: see details below
Exit code (Decimal): -1554760125
Exit facility code: 852
Exit error code: 15939
Exit message: Failed to retrieve data for this request.
Start time: 2014-08-15 16:49:52
End time: 2014-08-15 16:50:06
Requested action: RunRules
Machine Properties:
Machine name: servername
Machine processor count: 8
OS version: Windows Server 2008 R2
OS service pack: Service Pack 1
OS region: United States
OS language: English (United States)
OS architecture: x64
Process architecture: 64 Bit
OS clustered: Yes
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: c:\84122ef5b6d9cdcd3b2ac48cec\x64\setup\
Installation edition: EXPRESS
User Input Settings:
ACTION: RunRules
CONFIGURATIONFILE:
ENU: True
FARMACCOUNT: <empty>
FARMADMINPORT: 0
FARMPASSWORD: *****
FEATURES:
HELP: False
INDICATEPROGRESS: False
INSTANCENAME: <empty>
PASSPHRASE: *****
QUIET: False
QUIETSIMPLE: False
RULES: GLOBALRULES,SqlUnsupportedProductBlocker,PerfMonCounterNotCorruptedCheck,Bids2008InstalledCheck,BlockInstallSxS,AclPermissionsFacet,FacetDomainControllerCheck,SSMS_IsInternetConnected,FacetWOW64PlatformCheck,FacetPowerShellCheck
UIMODE: AutoAdvance
X86: False
Configuration file: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20140815_164944\ConfigurationFile.ini
Detailed results:
Rules with failures:
Global rules:
There are no scenario-specific rules.
Rules report file: The rule result report file is not available.
Exception summary:
The following is an exception stack listing the exceptions in outermost to innermost order
Inner exceptions are being indented
Exception type: Microsoft.SqlServer.Management.Sdk.Sfc.EnumeratorException
Message:
Failed to retrieve data for this request.
Data:
HelpLink.ProdName = Microsoft SQL Server
HelpLink.BaseHelpUrl = http://go.microsoft.com/fwlink
HelpLink.LinkId = 20476
DisableWatson = true
Stack:
at Microsoft.SqlServer.Management.Sdk.Sfc.Enumerator.Process(Object connectionInfo, Request request)
at Microsoft.SqlServer.Chainer.Infrastructure.SqlDiscoveryDatastoreInterface.ProcessDTbl(DataTable dt, Int32 level)
at Microsoft.SqlServer.Chainer.Infrastructure.SqlDiscoveryDatastoreInterface.CollectSqlDiscoveryData(String machineName)
at Microsoft.SqlServer.Chainer.Infrastructure.SqlDiscoveryDatastoreInterface.LoadData(IEnumerable`1 machineNames, String discoveryDocRootPath, String clusterDiscoveryDocRootPath)
at Microsoft.SqlServer.Configuration.SetupExtension.RunDiscoveryAction.ExecuteAction(String actionId)
at Microsoft.SqlServer.Chainer.Infrastructure.Action.Execute(String actionId, TextWriter errorStream)
at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.ExecuteActionHelper(TextWriter statusStream, ISequencedAction actionToRun)
Inner exception type: Microsoft.SqlServer.Configuration.Sco.SqlRegistryException
Message:
The network path was not found.
Data:
WatsonData = [email protected]rror
Stack:
at Microsoft.SqlServer.Configuration.Sco.SqlRegistry.CreateBaseKey(ServiceContainer ctx, String machineName, IntPtr hKey, String keyName, RegistryAccess access, RegistryView
view)
at Microsoft.SqlServer.Configuration.Sco.SqlRegistry.GetLocalMachine(ServiceContainer ctx, String machineName, RegistryAccess access, RegistryView view)
at Microsoft.SqlServer.Discovery.DiscoveryEnumObject.GetSql2kMsiInstanceListInHive(String machineName, RegistryView regView)
at Microsoft.SqlServer.Discovery.DiscoveryEnumObject.LoadSql2kInstanceList(String machineName)
at Microsoft.SqlServer.Discovery.Product.GetData(EnumResult erParent)
at Microsoft.SqlServer.Management.Sdk.Sfc.Environment.GetData()
at Microsoft.SqlServer.Management.Sdk.Sfc.Enumerator.GetData(Object connectionInfo, Request request)
at Microsoft.SqlServer.Management.Sdk.Sfc.Enumerator.Process(Object connectionInfo, Request request)Inner exception type: Microsoft.SqlServer.Configuration.Sco.SqlRegistryException
Message:
The network path was not found.
Data:
WatsonData = [email protected]rror
Above message says that your registry is not consistent and some of the parameters are missing from registry.Or
Account installing SQL server does not have permission to access this. I think case can be here that account with which you logged into your system to install SQL Server might not have certain privileges. Can you take help
of domain admin account add it as a local administrator in this machine always right click on setup file and select run as administrator. Before this make sure you remove all SQL Server components from add remove program
I strongly recommend you to have a good look at below thread
http://support.microsoft.com/kb/2000257/en-us
Please mark this reply as answer if it solved your issue or vote as helpful if it helped so that other forum members can benefit from it.
My TechNet Wiki Articles -
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 -
[Error] Microsoft SQL Server 2008 Setup. Error reading from file msdbdata.mdf
Hi all
I'm trying to install SQL 2008 Express on my Computer: Hp compact DX7300 Slim tower.
and get this error:
TITLE: Microsoft SQL Server 2008 Setup
The following error has occurred:Error reading from file d:\8268cd7b247d294de359c9\x86\setup\sql_engine_core_inst_msi\PFiles\SqlServr\MSSQL.X\MSSQL\Binn\Template\msdbdata.mdf. Verify that the file exists and that you can access it.
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.0.1823.0&EvtType=0xF45F6601%25401201%25401
Log file
Overall summary:
Final result: SQL Server installation failed. To continue, investigate the reason for the failure, correct the problem, uninstall SQL Server, and then rerun SQL Server Setup.
Exit code (Decimal): -2068643839
Exit facility code: 1203
Exit error code: 1
Exit message: SQL Server installation failed. To continue, investigate the reason for the failure, correct the problem, uninstall SQL Server, and then rerun SQL Server Setup.
Start time: 2014-12-09 23:22:03
End time: 2014-12-09 23:40:28
Requested action: Install
Log with failure: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20141209_232121\sql_engine_core_inst_Cpu32_1.log
Exception help link: http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=10.0.1823.0
Machine Properties:
Machine name: VISTA-PC
Machine processor count: 2
OS version: Windows Vista
OS service pack: Service Pack 1
OS region: United States
OS language: English (United States)
OS architecture: x86
Process architecture: 32 Bit
OS clustered: No
Product features discovered:
Product Instance Instance ID Feature
Language Edition Version Clustered
Package properties:
Description: SQL Server Database Services 2008
SQLProductFamilyCode: {628F8F38-600E-493D-9946-F4178F20A8A9}
ProductName: SQL2008
Type: RTM
Version: 10
SPLevel: 0
Installation location: d:\8268cd7b247d294de359c9\x86\setup\
Installation edition: EXPRESS
User Input Settings:
ACTION: Install
ADDCURRENTUSERASSQLADMIN: False
AGTSVCACCOUNT: NT AUTHORITY\NETWORK SERVICE
AGTSVCPASSWORD: *****
AGTSVCSTARTUPTYPE: Disabled
ASBACKUPDIR: Backup
ASCOLLATION: Latin1_General_CI_AS
ASCONFIGDIR: Config
ASDATADIR: Data
ASDOMAINGROUP: <empty>
ASLOGDIR: Log
ASPROVIDERMSOLAP: 1
ASSVCACCOUNT: <empty>
ASSVCPASSWORD: *****
ASSVCSTARTUPTYPE: Automatic
ASSYSADMINACCOUNTS: <empty>
ASTEMPDIR: Temp
BROWSERSVCSTARTUPTYPE: Disabled
CONFIGURATIONFILE: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20141209_232121\ConfigurationFile.ini
ENABLERANU: True
ERRORREPORTING: False
FEATURES: SQLENGINE,REPLICATION
FILESTREAMLEVEL: 0
FILESTREAMSHARENAME: <empty>
FTSVCACCOUNT: <empty>
FTSVCPASSWORD: *****
HELP: False
INDICATEPROGRESS: False
INSTALLSHAREDDIR: C:\Program Files\Microsoft SQL Server\
INSTALLSHAREDWOWDIR: C:\Program Files\Microsoft SQL Server\
INSTALLSQLDATADIR: <empty>
INSTANCEDIR: C:\Program Files\Microsoft SQL Server\
INSTANCEID: SQLExpress
INSTANCENAME: SQLEXPRESS
ISSVCACCOUNT: NT AUTHORITY\NetworkService
ISSVCPASSWORD: *****
ISSVCSTARTUPTYPE: Automatic
MEDIASOURCE: d:\8268cd7b247d294de359c9\
NPENABLED: 0
PID: *****
QUIET: False
QUIETSIMPLE: False
RSINSTALLMODE: FilesOnlyMode
RSSVCACCOUNT: <empty>
RSSVCPASSWORD: *****
RSSVCSTARTUPTYPE: Automatic
SAPWD: *****
SECURITYMODE: <empty>
SQLBACKUPDIR: <empty>
SQLCOLLATION: SQL_Latin1_General_CP1_CI_AS
SQLSVCACCOUNT: NT AUTHORITY\NETWORK SERVICE
SQLSVCPASSWORD: *****
SQLSVCSTARTUPTYPE: Automatic
SQLSYSADMINACCOUNTS: VISTA-PC\VISTA
SQLTEMPDBDIR: <empty>
SQLTEMPDBLOGDIR: <empty>
SQLUSERDBDIR: <empty>
SQLUSERDBLOGDIR: <empty>
SQMREPORTING: False
TCPENABLED: 0
X86: False
Configuration file: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20141209_232121\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
Rules with failures:
Global rules:
Scenario specific rules:
Rules report file: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20141209_232121\SystemConfigurationCheck_Report.htm
I will very appriciate if someone can help me solve it. I was trying to set Full control for my account in Properties/Security of root folder and try again but error is still.
Many thanksHi Foreverduy,
Before you run SQL Server 2008 express setup, make sure that you have installed Windows installer 4.5 and.NET Framework 3.5 SP1 manually. For more information about the process, please refer to the article:
http://msdn.microsoft.com/en-us/library/ms143506(v=sql.100).aspx. Moreover, please turn off all the third-party softwares which could prohibit the installation process.
According to your error message, the issue could be due to that your account has no rights to install SQL Server, or the corruption on the media.
Firstly, please ensure that your account has admin rights. Also make sure that you right-click the setup.exe and choose “Run as administrator” to complete the installation.
Secondly, please check if "msdbdata.mdf" file exists at d:\8268cd7b247d294de359c9\x86\setup\sql_engine_core_inst_msi\PFiles\SqlServr\MSSQL.X\MSSQL\Binn\Template. If it exists, please make sure that your account has read permission to the extracted
folder.
However, if the file doesn't exist in the extraction, the media could be corrupt. Please download the
media
again and check if the issue still occurs.
Regards,
Michelle Li
Maybe you are looking for
-
HR Logical database PNP. OO to fill table dynamic table from PNP ?
Hi all I want to get some stuff from the HR logical database into a dynamic table Here's a real simple example that writes info out to a normal list. (report is based on using Logical DB PNP) tables: pernr. INFOTYPES: 0001, "Organ
-
Airport disk not visible in windows (XP)
I have 3 computes 2x imac + one PC under Windows XP I use time capsule (7.4.2) for the network + file sharing. Almost everything works ok. Only issue is that I do not have airport disk access from the PC/Windows. On the PC I have Airport Utility 5.4.
-
How to delete duplicate photos on iPad4?
How can I find and delete duplicate photos from iPad4?
-
Hi, I have a Pl/Sql query which when run is taking a long time to execute. When i put a trace on it, i found that it is waiting for 2 objects and as soon as the wait is over the query produces the output immediately. I tried puuting index on tables w
-
Re-installing original OS on G3
My old iBook (c2001)came with OS 9 and the original OS X (10.1). At one stage I upgraded it to OS X (10.3)with a disc from my iMac. Didn't cope with the upgrade too well (a bit slow) and I'm now also thinking of passing the machine on. I'd like to re