SQL Server Installation - All Features
Hi,
I'm literally fighting with one of my colleague. He is installing all features that are available during the installation and also configuring with defaults. For example, Reporting Services with Default configuration & SSRS with Sharepoint
integration, Distributed Replay, Analysis Services, Integrating Services, Replication etc etc.... He is litereally selecting every checkbox that is available on the features selection screen and installing them with defaults. I'm fed up with the
argument and finally approaching you.
There is no such requirement from the client. Application owner wants us to install only SQL Server and host their databases, that's it.
How can I convince him that installing all features is not a good idea? Can I really convince him?
If you feel that I have answered your question then please "Mark as Answer".
Hello,
Installing more features may require more resources from the server. Features like Analysis Services and Reporting Services require
many computer resources like RAM and disk space.
Just one example: SQL Server has a minimum requirement of 1 GB of RAM (apart from the RAM requirements of the operating system). If
you decide to add the Data Quality Services feature only, then the minimum requirement for installation is now 2 GB.
Additionally, by installing less features you are reducing the surface area and improving security. The less features the computer have
installed then less roads to potential attacks.
Hope this helps.
Regards,
Alberto Morillo
SQLCoffee.com
Similar Messages
-
hi,
I installed visual studio 2010 in my windows 8.1 system.during the installation sql server 2008 r2 features were installed.so which version of sql server i need to install(2008 or 2008 r2)?
regards,
harsha.My guess is SQL Server 2008 R2.
Check the following KB article for details:
http://support.microsoft.com/kb/2681562
Kalman Toth Database & OLAP Architect
SELECT Video Tutorials 4 Hours
New Book / Kindle: Exam 70-461 Bootcamp: Querying Microsoft SQL Server 2012 -
Overall summary:
Final result: Failed: see details below
Exit code (Decimal): -2147467259
Start time: 2015-02-16 10:35:41
End time: 2015-02-16 11:15:03
Requested action: Install
Setup completed with required actions for features.
Troubleshooting information for those features:
Next step for SSMS: Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
Next step for BIDS: 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 SQLEngine: 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.
Machine Properties:
Machine name: ABHI
Machine processor count: 4
OS version: Future Windows Version
OS service pack:
OS region: United States
OS language: English (United States)
OS architecture: x64
Process architecture: 64 Bit
OS clustered: No
Product features discovered:
Product Instance Instance ID Feature
Language Edition Version Clustered
Package properties:
Description: Microsoft SQL Server 2012 Service Pack 1
ProductName: SQL Server 2012
Type: RTM
Version: 11
SPLevel: 0
Installation location: f:\33ee254b43729031825c982f\x64\setup\
Installation edition: Express
Product Update Status:
None discovered.
User Input Settings:
ACTION: Install
ADDCURRENTUSERASSQLADMIN: true
AGTSVCACCOUNT: NT AUTHORITY\NETWORK SERVICE
AGTSVCPASSWORD: *****
AGTSVCSTARTUPTYPE: Disabled
ASBACKUPDIR: Backup
ASCOLLATION: Latin1_General_CI_AS
ASCONFIGDIR: Config
ASDATADIR: Data
ASLOGDIR: Log
ASPROVIDERMSOLAP: 1
ASSERVERMODE: MULTIDIMENSIONAL
ASSVCACCOUNT: <empty>
ASSVCPASSWORD: <empty>
ASSVCSTARTUPTYPE: Automatic
ASSYSADMINACCOUNTS: <empty>
ASTEMPDIR: Temp
BROWSERSVCSTARTUPTYPE: Disabled
CLTCTLRNAME: <empty>
CLTRESULTDIR: <empty>
CLTSTARTUPTYPE: 0
CLTSVCACCOUNT: <empty>
CLTSVCPASSWORD: <empty>
CLTWORKINGDIR: <empty>
COMMFABRICENCRYPTION: 0
COMMFABRICNETWORKLEVEL: 0
COMMFABRICPORT: 0
CONFIGURATIONFILE:
CTLRSTARTUPTYPE: 0
CTLRSVCACCOUNT: <empty>
CTLRSVCPASSWORD: <empty>
CTLRUSERS: <empty>
ENABLERANU: true
ENU: true
ERRORREPORTING: true
FEATURES: SQLENGINE, REPLICATION, FULLTEXT, RS, BIDS, BOL, SSMS, SNAC_SDK, LOCALDB
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 AUTHORITY\Network Service
ISSVCPASSWORD: <empty>
ISSVCSTARTUPTYPE: Automatic
MATRIXCMBRICKCOMMPORT: 0
MATRIXCMSERVERNAME: <empty>
MATRIXNAME: <empty>
NPENABLED: 0
PID: *****
QUIET: false
QUIETSIMPLE: false
ROLE: AllFeatures_WithDefaults
RSINSTALLMODE: DefaultNativeMode
RSSHPINSTALLMODE: DefaultSharePointMode
RSSVCACCOUNT: NT Service\ReportServer
RSSVCPASSWORD: <empty>
RSSVCSTARTUPTYPE: Automatic
SAPWD: *****
SECURITYMODE: SQL
SQLBACKUPDIR: <empty>
SQLCOLLATION: SQL_Latin1_General_CP1_CI_AS
SQLSVCACCOUNT: NT Service\MSSQLSERVER
SQLSVCPASSWORD: <empty>
SQLSVCSTARTUPTYPE: Automatic
SQLSYSADMINACCOUNTS: ABHI\abhi24
SQLTEMPDBDIR: <empty>
SQLTEMPDBLOGDIR: <empty>
SQLUSERDBDIR: <empty>
SQLUSERDBLOGDIR: <empty>
SQMREPORTING: true
TCPENABLED: 0
UIMODE: AutoAdvance
UpdateEnabled: true
UpdateSource: MU
X86: false
Configuration file: C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log\20150216_102728\ConfigurationFile.ini
Detailed results:
Feature: Management Tools - Basic
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 Common Files
Component error code: 0x84BB0001
Error description: The MOF compiler could not connect with the WMI server. This is either because of a semantic error such as an incompatibility with the existing WMI repository or an actual error such as the
failure of the WMI server to start.
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=0xA60E3551%400xD3BEBD98%401211%401&EvtType=0xA60E3551%400xD3BEBD98%401211%401
Feature: SQL Server Data Tools
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 Common Files
Component error code: 0x84BB0001
Error description: The MOF compiler could not connect with the WMI server. This is either because of a semantic error such as an incompatibility with the existing WMI repository or an actual error such as the
failure of the WMI server to start.
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=0xA60E3551%400xD3BEBD98%401211%401&EvtType=0xA60E3551%400xD3BEBD98%401211%401
Feature: Reporting Services - Native
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 Common Files
Component error code: 0x84BB0001
Error description: The MOF compiler could not connect with the WMI server. This is either because of a semantic error such as an incompatibility with the existing WMI repository or an actual error such as the
failure of the WMI server to start.
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=0xA60E3551%400xD3BEBD98%401211%401&EvtType=0xA60E3551%400xD3BEBD98%401211%401
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 system cannot find the path specified
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=0xF57C3D6F%400xDC80C325&EvtType=0xF57C3D6F%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 system cannot find the path specified
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=0xF57C3D6F%400xDC80C325&EvtType=0xF57C3D6F%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 system cannot find the path specified
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=0xF57C3D6F%400xDC80C325&EvtType=0xF57C3D6F%400xDC80C325
Feature: SQL Browser
Status: Passed
Feature: Documentation Components
Status: Passed
Feature: SQL Writer
Status: Passed
Feature: LocalDB
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\20150216_102728\SystemConfigurationCheck_Report.htmHi,
It seems to me like you have
1. Previous failed instance of SQL Server installation which subsequently caused further SQL Server installations to fail
2. The windows account with which you logged into machine to install SQL Server is corrupt
You can, If possible create a new windows account give it admin privileges and then log into machine using this account
After you login follow below method to remove failed SQL Server installation
Uninstall
Uninstall SQL Server completely from add remove program. Make sure no previous failed installation fragments are present on your system. Please use this
link for uninstalling existing instance of SQL Server
. If you have SQL Server 2005
use this link .
If you are unable to uninstall SQL Server completely because you deleted SQL Server files and un-installation is giving error please follow below method. This method is tested and suggested on
this thread and
Forum .
Below Solution (about removing reg keys) will work correctly for SQL Server having Just one instance.
If you have multiple instances and you have messed up SQL Server installation please contact Microsoft Support personal to get better guidance on removal of SQL Server. Please DONT use this method if you are new to SQL Server take help of experienced
DBA to locate proper registry keys and remove them if you are not confident at all it would be better calling Microsoft Support.
Note: Removing necessary registry entries might cause SQL Server instance to crash so backup registry before doing changes.
1. Uninstall the existing SQL Server and all the components from the add remove program.
2.
Backup the registry .
3. Delete the following keys using regedit:
--HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server
--HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer
4. Go to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall and delete all the sub-keys referencing SQL Server.
5. Go to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services and delete all the keys referencing SQL Server.
6. Rename all the SQL Server folders in the computer.
7. Reboot the machine.
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 Article
MVP -
SQL Server installation failed with Exit code (Decimal): -2068643839
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: 2009-10-20 23:58:46
End time: 2009-10-21 00:56:30
Requested action: Install
Log with failure: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20091020_235135\Detail.txt
Exception help link: http%3a%2f%2fgo.microsoft.com%2ffwlink%3fLinkId%3d20476%26ProdName%3dMicrosoft%2bSQL%2bServer%26EvtSrc%3dsetup.rll%26EvtID%3d50000%26ProdVer%3d10.0.1600.22%26EvtType%3d0xBE029E38%400x12C2466D
Machine Properties:
Machine name: ADI
Machine processor count: 2
OS version: Windows XP
OS service pack: Service Pack 3
OS region: România
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:\e9d5147ebef49a28bb15\x86\setup\
Installation edition: EXPRESS_ADVANCED
User Input Settings:
ACTION: Install
ADDCURRENTUSERASSQLADMIN: True
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\20091020_235135\ConfigurationFile.ini
ENABLERANU: True
ERRORREPORTING: False
FEATURES: SQLENGINE,REPLICATION,SSMS
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:\e9d5147ebef49a28bb15\
NPENABLED: 0
PID: *****
QUIET: False
QUIETSIMPLE: True
RSINSTALLMODE: FilesOnlyMode
RSSVCACCOUNT: <empty>
RSSVCPASSWORD: *****
RSSVCSTARTUPTYPE: Automatic
SAPWD: *****
SECURITYMODE: SQL
SQLBACKUPDIR: <empty>
SQLCOLLATION: Romanian_CI_AS
SQLSVCACCOUNT: NT AUTHORITY\Network Service
SQLSVCPASSWORD: *****
SQLSVCSTARTUPTYPE: Automatic
SQLSYSADMINACCOUNTS: <empty>
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\20091020_235135\ConfigurationFile.ini
Detailed results:
Feature: Database Engine Services
Status: Failed: see logs for details
MSI status: Passed
Configuration status: Failed: see details below
Configuration error code: 0x12C2466D
Configuration error description: '' is not a valid login or you do not have permission.
Configuration log: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20091020_235135\Detail.txt
Feature: SQL Server Replication
Status: Failed: see logs for details
MSI status: Passed
Configuration status: Failed: see details below
Configuration error code: 0x12C2466D
Configuration error description: '' is not a valid login or you do not have permission.
Configuration log: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20091020_235135\Detail.txt
Feature: Management Tools - Basic
Status: Passed
MSI status: Passed
Configuration status: Passed
Rules with failures:
Global rules:
Scenario specific rules:
Rules report file: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20091020_235135\SystemConfigurationCheck_Report.htmHi All,
I am also having same issue:-
long time back i installed default sql 2008 with sp1 in win2008 R2 server in drive(system data files) M:\, but some time back windows team deleted all the system datafiles from drive, now when i am trying to uninstall\install default sql 2008
getting below error. manually i have removed all the mssqlserver,version entry from registry and deleted all the remaining folder from drive C:\, but still error is comming.
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: 2011-06-12 23:14:10
End time: 2011-06-12 23:20:59
Requested action: Install
Log with failure: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20110612_230738\Detail.txt
Exception help link: http%3a%2f%2fgo.microsoft.com%2ffwlink%3fLinkId%3d20476%26ProdName%3dMicrosoft%2bSQL%2bServer%26EvtSrc%3dsetup.rll%26EvtID%3d50000%26ProdVer%3d10.0.1600.22%26EvtType%3d0xF57C3D6F%400xFB92A9BB
Machine Properties:
Machine name: XXXXXXXXX
Machine processor count: 8
OS version: Windows Server 2008
OS service pack:
OS region: United States
OS language: English (United States)
OS architecture: x64
Process architecture: 64 Bit
OS clustered: No
Product features discovered:
Product Instance Instance ID
Feature Language
Edition Version Clustered
Package properties:
Description: SQL Server Database Services 2008
SQLProductFamilyCode: {628F8F38-600E-493D-9946-F4178F20A8A9}
ProductName: SQL2008
Type: RTM
Version: 10
SPLevel: 0
Installation location: D:\sql dump\SQL 2008 EE 64 Bit\x64\setup\
Installation edition: ENTERPRISE
User Input Settings:
ACTION: Install
ADDCURRENTUSERASXXXXXXXXX: False
AGTSVCACCOUNT: XXXXXXXXX\XXXXXX
AGTSVCPASSWORD: *****
AGTSVCSTARTUPTYPE: Manual
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\20110612_230738\ConfigurationFile.ini
ENABLERANU: False
ERRORREPORTING: False
FEATURES: SQLENGINE,REPLICATION,FULLTEXT
FILESTREAMLEVEL: 0
FILESTREAMSHARENAME: <empty>
FTSVCACCOUNT: NT AUTHORITY\LOCAL SERVICE
FTSVCPASSWORD: *****
HELP: False
INDICATEPROGRESS: False
INSTALLSHAREDDIR: C:\Program Files\Microsoft SQL Server\
INSTALLSHAREDWOWDIR: C:\Program Files (x86)\Microsoft SQL Server\
INSTALLSQLDATADIR: <empty>
INSTANCEDIR: D:\Program Files\Microsoft SQL Server\
INSTANCEID: MSSQLSERVER
INSTANCENAME: MSSQLSERVER
ISSVCACCOUNT: NT AUTHORITY\NetworkService
ISSVCPASSWORD: *****
ISSVCSTARTUPTYPE: Automatic
MEDIASOURCE: D:\sql dump\SQL 2008 EE 64 Bit\
NPENABLED: 0
PID: *****
QUIET: False
QUIETSIMPLE: False
RSINSTALLMODE: FilesOnlyMode
RSSVCACCOUNT: <empty>
RSSVCPASSWORD: *****
RSSVCSTARTUPTYPE: Automatic
SAPWD: *****
SECURITYMODE: SQL
SQLBACKUPDIR: <empty>
SQLCOLLATION: SQL_Latin1_General_CP850_BIN2
SQLSVCACCOUNT: xxxxxxx\xxxxxxxx
SQLSVCPASSWORD: *****
SQLSVCSTARTUPTYPE: Automatic
SQLSYSADMINACCOUNTS: xxxxxxx\xxxxxxxx
SQLTEMPDBDIR: <empty>
SQLTEMPDBLOGDIR: <empty>
SQLUSERDBDIR: <empty>
SQLUSERDBLOGDIR: <empty>
SQMREPORTING: False
TCPENABLED: 1
X86: False
Configuration file: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20110612_230738\ConfigurationFile.ini
Detailed results:
Feature: Database Engine Services
Status: Failed: see logs for details
MSI status: Passed
Configuration status: Failed: see details below
Configuration error code: 0xFB92A9BB
Configuration error description: The system cannot find the path specified
Configuration log: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20110612_230738\Detail.txt
Feature: SQL Server Replication
Status: Failed: see logs for details
MSI status: Passed
Configuration status: Failed: see details below
Configuration error code: 0xFB92A9BB
Configuration error description: The system cannot find the path specified
Configuration log: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20110612_230738\Detail.txt
Feature: Full-Text Search
Status: Failed: see logs for details
MSI status: Passed
Configuration status: Failed: see details below
Configuration error code: 0xFB92A9BB
Configuration error description: The system cannot find the path specified
Configuration log: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20110612_230738\Detail.txt
Rules with failures:
Global rules:
Scenario specific rules:
Rules report file: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20110612_230738\SystemConfigurationCheck_Report.htm
india -
Problem installing SQL Server 2012 SP1: "managed sql server installer has stopped working"
Hello,
I have a big problem.
I just downloaded SQL Server 2012 SP1 and I only want to install SSMS. The installer always crashes with an error message "managed sql server installer has stopped working".
I already tried all solutions from Google for this problem but nothing works.
Can someone help me plase?
My System: Window 8 Pro with Visual Studio 2012.
Thanks
SvenWould you please uplaod/share SQL Server setup logs
C:\Program
Files\Microsoft
SQL Server\110\Setup
Bootstrap\Log\20130125_133342
to file sharing service like SkyDrive.com
FAQ
Regards,
Ahmed Ibrahim
SQL Server Setup Team
My Blog
This posting is provided "AS IS" with no warranties, and confers no rights. Please remember to click
"Mark as Answer" and "Vote as Helpful"
on posts that help you.
This can be beneficial to other community members reading the thread. -
SQl Server Installation failing for Database Engine and Its Services
Hi,
I was trying to install SQL SERVER 2008 R2 on VM having 500 GB hard disk and 16 GB RAM.
OS is Windows Server 2008
But it fails for Database Engine.
Installation Details are as Below.
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): -2068119551
Exit facility code: 1211
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-10-13 18:41:01
End time: 2014-10-13 19:26:32
Requested action: Install
Log with failure: C:Program FilesMicrosoft SQL Server100Setup BootstrapLog20141013_183354Detail.txt
Exception help link: http%3a%2f%2fgo.microsoft.com%2ffwlink%3fLinkId%3d20476%26ProdName%3dMicrosoft%2bSQL%2bServer%26EvtSrc%3dsetup.rll%26EvtID%3d50000%26ProdVer%3d10.50.1600.1%26EvtType%3d0x476BF04A%400xBB814387
Machine Properties:
Machine name: KVS-IN-WFAN092
Machine processor count: 4
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: No
Product features discovered:
Product Instance Instance ID Feature
Language Edition Version Clustered
Package properties:
Description: SQL Server Database Services 2008 R2
ProductName: SQL Server 2008 R2
Type: RTM
Version: 10
SPLevel: 0
Installation location: di-softwareSoftwaresSQLSQL_2008_R2_Enterprisex64setup
Installation edition: ENTERPRISE
User Input Settings:
ACTION: Install
ADDCURRENTUSERASSQLADMIN: False
AGTSVCACCOUNT: NT AUTHORITYNETWORK SERVICE
AGTSVCPASSWORD: *****
AGTSVCSTARTUPTYPE: Manual
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: Automatic
CONFIGURATIONFILE: C:Program FilesMicrosoft SQL Server100Setup BootstrapLog20141013_183354ConfigurationFile.ini
CUSOURCE:
ENABLERANU: False
ENU: True
ERRORREPORTING: False
FARMACCOUNT: <empty>
FARMADMINPORT: 0
FARMPASSWORD: *****
FEATURES: SQLENGINE,REPLICATION,FULLTEXT,SSMS,ADV_SSMS
FILESTREAMLEVEL: 0
FILESTREAMSHARENAME: <empty>
FTSVCACCOUNT: NT AUTHORITYLOCAL SERVICE
FTSVCPASSWORD: *****
HELP: False
IACCEPTSQLSERVERLICENSETERMS: False
INDICATEPROGRESS: False
INSTALLSHAREDDIR: C:Program FilesMicrosoft SQL Server
INSTALLSHAREDWOWDIR: C:Program Files (x86)Microsoft SQL Server
INSTALLSQLDATADIR: <empty>
INSTANCEDIR: C:Program FilesMicrosoft SQL Server
INSTANCEID: SQLServer
INSTANCENAME: SQLSERVER
ISSVCACCOUNT: NT AUTHORITYNetworkService
ISSVCPASSWORD: *****
ISSVCSTARTUPTYPE: Automatic
NPENABLED: 0
PASSPHRASE: *****
PCUSOURCE:
PID: *****
QUIET: False
QUIETSIMPLE: False
ROLE: <empty>
RSINSTALLMODE: FilesOnlyMode
RSSVCACCOUNT: <empty>
RSSVCPASSWORD: *****
RSSVCSTARTUPTYPE: Automatic
SAPWD: *****
SECURITYMODE: SQL
SQLBACKUPDIR: <empty>
SQLCOLLATION: SQL_Latin1_General_CP1_CI_AS
SQLSVCACCOUNT: NT AUTHORITYNETWORK SERVICE
SQLSVCPASSWORD: *****
SQLSVCSTARTUPTYPE: Automatic
SQLSYSADMINACCOUNTS: KRONOSENGsuperuser
SQLTEMPDBDIR: <empty>
SQLTEMPDBLOGDIR: <empty>
SQLUSERDBDIR: <empty>
SQLUSERDBLOGDIR: <empty>
SQMREPORTING: False
TCPENABLED: 1
UIMODE: Normal
X86: False
Configuration file: C:Program FilesMicrosoft SQL Server100Setup BootstrapLog20141013_183354ConfigurationFile.ini
Detailed results:
Feature: Database Engine Services
Status: Failed: see logs for details
MSI status: Passed
Configuration status: Passed
Feature: SQL Server Replication
Status: Failed: see logs for details
MSI status: Passed
Configuration status: Passed
Feature: Full-Text Search
Status: Failed: see logs for details
MSI status: Passed
Configuration status: Passed
Feature: Management Tools - Complete
Status: Passed
MSI status: Passed
Configuration status: Passed
Feature: Management Tools - Basic
Status: Passed
MSI status: Passed
Configuration status: Passed
Rules with failures:
Global rules:
Scenario specific rules:
Rules report file: C:Program FilesMicrosoft SQL Server100Setup BootstrapLog20141013_183354SystemConfigurationCheck_Report.htm
And Error in log file are maily as below.
2014-10-13 19:26:27 Slp: Completed Action: SqlBrowserConfigAction_install_Startup_Cpu32, returned True
2014-10-13 19:26:27 Slp: Action "ConfigEvent_SQL_Engine_Core_Inst_sql_engine_core_inst_Cpu64_Install_Startup_postmsi" will return false due to the following conditions:
2014-10-13 19:26:27 Slp: Condition "Feature dependency condition for action: ConfigEvent_SQL_Engine_Core_Inst_sql_engine_core_inst_Cpu64_Install_Startup_postmsi The condition tests feature: SQL_Engine_Core_Inst_sql_engine_core_inst_Cpu64. There are 11
dependant features. The feature is tested for results: ValidateResult, Result." did not pass as it returned false and true was expected.
2014-10-13 19:26:27 Slp: Condition is false because the required feature SQL_Engine_Core_Inst_sql_engine_core_inst_Cpu64 failed in result Result
2014-10-13 19:26:27 Slp: Action "SqlBrowserConfigEngAction_install_Startup_Cpu64" will return false due to the following conditions:
2014-10-13 19:26:27 Slp: Condition "Feature dependency condition for action: SqlBrowserConfigEngAction_install_Startup_Cpu64 The condition tests feature: SQL_Engine_Core_Inst_sql_engine_core_inst_Cpu64. There are 11 dependant features. The feature is tested
for results: ValidateResult, Result." did not pass as it returned false and true was expected.
2014-10-13 19:26:27 Slp: Condition is false because the required feature SQL_Engine_Core_Inst_sql_engine_core_inst_Cpu64 failed in result Result
2014-10-13 19:26:27 Slp: Action "SqlEngineConfigAction_install_startup_Cpu64" will return false due to the following conditions:
2014-10-13 19:26:27 Slp: Condition "Feature dependency condition for action: SqlEngineConfigAction_install_startup_Cpu64 The condition tests feature: SQL_Engine_Core_Inst_sql_engine_core_inst_Cpu64. There are 11 dependant features. The feature is tested
for results: ValidateResult, Result." did not pass as it returned false and true was expected.
2014-10-13 19:26:27 Slp: Condition is false because the required feature SQL_Engine_Core_Inst_sql_engine_core_inst_Cpu64 failed in result Result
2014-10-13 19:26:27 Slp: Action "ConfigEvent_MPT_AGENT_CORE_CNI_sql_engine_core_inst_Cpu64_Install_Startup_postmsi" will return false due to the following conditions:
2014-10-13 19:26:27 Slp: Condition "Feature dependency condition for action: ConfigEvent_MPT_AGENT_CORE_CNI_sql_engine_core_inst_Cpu64_Install_Startup_postmsi The condition tests feature: MPT_AGENT_CORE_CNI_sql_engine_core_inst_Cpu64. There are 2 dependant
features. The feature is tested for results: ValidateResult, Result." did not pass as it returned false and true was expected.
2014-10-13 19:26:27 Slp: Condition is false because the required feature SQL_Engine_Core_Inst_sql_engine_core_inst_Cpu64 failed in result Result
2014-10-13 19:26:27 Slp: Action "AgentInstall_AgentInstallStartup_Cpu64" will return false due to the following conditions:
2014-10-13 19:26:27 Slp: Condition "Feature dependency condition for action: AgentInstall_AgentInstallStartup_Cpu64 The condition tests feature: MPT_AGENT_CORE_CNI_sql_engine_core_inst_Cpu64. There are 2 dependant features. The feature is tested for results:
ValidateResult, Result." did not pass as it returned false and true was expected.
2014-10-13 19:26:27 Slp: Condition is false because the required feature SQL_Engine_Core_Inst_sql_engine_core_inst_Cpu64 failed in result Result
2014-10-13 19:26:27 Slp: Action "ConfigEvent_SQL_Replication_Core_Inst_sql_engine_core_inst_Cpu64_Install_Startup_postmsi" will return false due to the following conditions:
2014-10-13 19:26:27 Slp: Condition "Feature dependency condition for action: ConfigEvent_SQL_Replication_Core_Inst_sql_engine_core_inst_Cpu64_Install_Startup_postmsi The condition tests feature: SQL_Replication_Core_Inst_sql_engine_core_inst_Cpu64. There
are 3 dependant features. The feature is tested for results: ValidateResult, Result." did not pass as it returned false and true was expected.
2014-10-13 19:26:27 Slp: Condition is false because the required feature SQL_Engine_Core_Inst_sql_engine_core_inst_Cpu64 failed in result Result
2014-10-13 19:26:27 Slp: Action "ConfigEvent_SQL_FullText_Adv_sql_fulltext_Cpu64_Install_Startup_postmsi" will return false due to the following conditions:
2014-10-13 19:26:27 Slp: Condition "Feature dependency condition for action: ConfigEvent_SQL_FullText_Adv_sql_fulltext_Cpu64_Install_Startup_postmsi The condition tests feature: SQL_FullText_Adv_sql_fulltext_Cpu64. There are 3 dependant features. The feature
is tested for results: ValidateResult, Result." did not pass as it returned false and true was expected.
2014-10-13 19:26:27 Slp: Condition is false because the required feature SQL_Engine_Core_Inst_sql_engine_core_inst_Cpu64 failed in result Result
2014-10-13 19:26:27 Slp: Action "FulltextConfigAction_install_startup_Cpu64" will return false due to the following conditions:
2014-10-13 19:26:27 Slp: Condition "Feature dependency condition for action: FulltextConfigAction_install_startup_Cpu64 The condition tests feature: SQL_FullText_Adv_sql_fulltext_Cpu64. There are 3 dependant features. The feature is tested for results:
ValidateResult, Result." did not pass as it returned false and true was expected.
2014-10-13 19:26:27 Slp: Condition is false because the required feature SQL_Engine_Core_Inst_sql_engine_core_inst_Cpu64 failed in result Result
2014-10-13 19:26:27 Slp: Action "ConfigEvent_SQL_Engine_Core_Inst_sql_engine_core_inst_Cpu64_Install_StartupFinalize_postmsi" will return false due to the following conditions:
2014-10-13 19:26:27 Slp: Condition "Feature dependency condition for action: ConfigEvent_SQL_Engine_Core_Inst_sql_engine_core_inst_Cpu64_Install_StartupFinalize_postmsi The condition tests feature: SQL_Engine_Core_Inst_sql_engine_core_inst_Cpu64. There
are 11 dependant features. The feature is tested for results: ValidateResult, Result." did not pass as it returned false and true was expected.
2014-10-13 19:26:27 Slp: Condition is false because the required feature SQL_Engine_Core_Inst_sql_engine_core_inst_Cpu64 failed in result Result
2014-10-13 19:26:27 Slp: Action "ConfigEvent_MPT_AGENT_CORE_CNI_sql_engine_core_inst_Cpu64_Install_StartupFinalize_postmsi" will return false due to the following conditions:
2014-10-13 19:26:27 Slp: Condition "Feature dependency condition for action: ConfigEvent_MPT_AGENT_CORE_CNI_sql_engine_core_inst_Cpu64_Install_StartupFinalize_postmsi The condition tests feature: MPT_AGENT_CORE_CNI_sql_engine_core_inst_Cpu64. There are
2 dependant features. The feature is tested for results: ValidateResult, Result." did not pass as it returned false and true was expected.
2014-10-13 19:26:27 Slp: Condition is false because the required feature SQL_Engine_Core_Inst_sql_engine_core_inst_Cpu64 failed in result Result
2014-10-13 19:26:27 Slp: Action "ConfigEvent_SQL_Replication_Core_Inst_sql_engine_core_inst_Cpu64_Install_StartupFinalize_postmsi" will return false due to the following conditions:
2014-10-13 19:26:27 Slp: Condition "Feature dependency condition for action: ConfigEvent_SQL_Replication_Core_Inst_sql_engine_core_inst_Cpu64_Install_StartupFinalize_postmsi The condition tests feature: SQL_Replication_Core_Inst_sql_engine_core_inst_Cpu64.
There are 3 dependant features. The feature is tested for results: ValidateResult, Result." did not pass as it returned false and true was expected.
2014-10-13 19:26:27 Slp: Condition is false because the required feature SQL_Engine_Core_Inst_sql_engine_core_inst_Cpu64 failed in result Result
2014-10-13 19:26:27 Slp: Action "ConfigEvent_SQL_FullText_Adv_sql_fulltext_Cpu64_Install_StartupFinalize_postmsi" will return false due to the following conditions:
2014-10-13 19:26:27 Slp: Condition "Feature dependency condition for action: ConfigEvent_SQL_FullText_Adv_sql_fulltext_Cpu64_Install_StartupFinalize_postmsi The condition tests feature: SQL_FullText_Adv_sql_fulltext_Cpu64. There are 3 dependant features.
The feature is tested for results: ValidateResult, Result." did not pass as it returned false and true was expected.
2014-10-13 19:26:27 Slp: Condition is false because the required feature SQL_Engine_Core_Inst_sql_engine_core_inst_Cpu64 failed in result Result
2014-10-13 19:26:27 Slp: Completed Action: PostMsiTimingConfigAction, returned True
2014-10-13 19:26:27 Slp: Completed Action: ExecuteStandardTimingsWorkflow, returned True
2014-10-13 19:26:27 Slp: ----------------------------------------------------------------------
2014-10-13 19:26:27 Slp: Running Action: ExecuteExtendedTimingsWorkflow
Thanks,
MaheshI have uploaded detail.txt at below url.
http://m.uploadedit.com/b041/1413264342685.txt
Hi Mahesh,
According to log file, I find the message ‘The setup100.exe.config file was not found, therefore the DTSWizard and SQLWatson app config files were not replaced’. It seems that the SQL Server setup file is not complete. Please check that if the SQL Server
setup file is corrupted, if it is corrupted, please download it again and reinstall SQL Server 2008 R2.
However, if there’s no problem with the setup file, please check that if there is third-party software such as anti-virus software on your computer blocking the process of SQL Server installation. In addition, make sure that you choose ‘Run as administrator’
to launch the setup and configure SQL Server service accounts appropriately with administrator permission during the installation.
For more details about this error, please review the following similar thread.
http://answers.flyppdevportal.com/categories/sqlserver/sqlsetupandupgrade.aspx?ID=ad794a97-09ae-4aae-9d68-0b06f9af3e16
Thanks,
Lydia Zhang -
Managed sql server installer has stopped working sql 2008 r2
I tried to installed sql 2008 r2 on my windows 7 but unfortunately I got message "managed sql server installer has stopped working"
1. I tried to program feature on and off feature
2. I checked setup file is corrupted or not setup file is well in condition
3. I turn on firewall too.
then again I tried to installed again same problem I faced.
please any different way to overcome from this problem!
regard Bishnu Khaling!Hi Bishnu,
As Shanky’s post, you can post the SQL Server setup log files for analysis.
According to the error message, it is usually a problem with the installation of .NET Framework on the machine. However, from your description, you try to turn on the Microsoft .NET Framework 3.5 feature and still fail to install SQL Server 2008 R2.
Do you reboot your computer after enabling .NET Framework 3.5?
To further troubleshoot this issue, I recommend you perform the following steps.
1. Run the below tool to verify the state of one or more versions of the .NET Framework on the computer .
http://blogs.msdn.com/b/astebner/archive/2008/10/13/8999004.aspx
2. If .Net Frameworks 3.5 cannot be verified in step1, please use the
.NET Framework Repair Tool to repair it.
3. If there’s no problem with .Net Frameworks 3.5, and you also have .NET Framework 4.0 or 4.5 installed on the computer, please uninstall .NET Framework 4.0 or 4.5 completely. Then reinstall SQL Server and check if it is successful.
4. In addition, please make sure that the Windows 7 system is not damaged.
For more details about the error, you can also review the following blog.
Fix: Managed SQL Server installer has stopped working on Windows 7 | 8:
http://www.thewindowsclub.com/managed-sql-server-installer-has-stopped-working
Thanks,
Lydia Zhang -
Getting [Microsoft][ODBC SQL Server Driver] Optional feature not implemented
I am using below mentioned code to insert values in MSAccess 2000 which having table structure as mentioned below:-
Field Name Data Type
TodaysDate Date/Time
Cart ID Number
Client Name Text
Campaign Text
Team & Segment Text
Duration Number
Tape ID Text
Start Date Date/Time
End Date Date/Time
Station Text
Code:-
private boolean enterDataIntoMSAccessDatabaseusingPreparedStatement()
try {
ps = connection.prepareStatement("INSERT INTO Cart ID Details VALUES (?,?,?,?,?,?,?,?,?)");
System.out.println("After Query");
catch (SQLException se) {
generateErrorMessage("Error in Prepared Statement \n " + se.getMessage() );
return false;
catch (Exception e)
generateErrorMessage("Unexpected Error Occured \n " + e.getMessage());
String todaysDate = cartIDApplicationAddCartIDDatejTextField.getText().trim();
String cartID = cartIDApplicationAddCartIDCartIDjTextField.getText().trim();
String clientName = cartIDApplicationAddCartIDClientNamejTextField.getText().trim();
String campaign = cartIDApplicationAddCartIDCampaignjTextField.getText().trim();
String teamSegment = cartIDApplicationAddCartIDTeamAndSegmentjTextField.getText().trim();
String duration = cartIDApplicationAddCartIDDurationjTextField.getText().trim();
String tapeID = cartIDApplicationAddCartIDTapeIDjTextField.getText().trim();
String startDate = cartIDApplicationAddCartIDStartDatejTextField.getText().trim();
String endDate = cartIDApplicationAddCartIDEndDatejTextField.getText().trim();
String station = cartIDApplicationAddCartIDDELjCheckBox.getText().substring(0, 3);
System.out.println(station);
try {
System.out.println("Before ps.setString()");
SimpleDateFormat simpleDateFormat = new SimpleDateFormat("yyyy-mm-dd", Locale.ENGLISH);
System.out.println("Simple Date Format");
/*ps.setString(1, todaysDate);
ps.setString(2, cartID );
ps.setString(3, clientName);
ps.setString(4, teamSegment);
ps.setString(5, duration);
ps.setString(6, tapeID);
ps.setString(7, startDate);
ps.setString(8, endDate);*/
System.out.println("1");
ps.setDate(1, new java.sql.Date(simpleDateFormat.parse(todaysDate).getTime()));
ps.setString(2, cartID);
ps.setString(3, clientName);
ps.setString(4, campaign);
ps.setString(5, teamSegment);
ps.setString(6, duration);
ps.setString(7, tapeID);
ps.setDate(8, new java.sql.Date(simpleDateFormat.parse(startDate).getTime()));
ps.setDate(9, new java.sql.Date(simpleDateFormat.parse(endDate).getTime()));
ps.setString(10, station);
System.out.println("After ps.setString()");
ps.executeUpdate();
catch (SQLException se) {
generateErrorMessage("Error while inserting data in database \n " + se.getMessage());
return false;
catch (Exception e)
generateErrorMessage("Unexpected Error Occured \n" + e.getMessage() );
return true;
I got below error after implementing the above code:-
[Microsoft][ODBC SQL Server Driver]Optional feature not implemented.
Kindly help me for the same.>> [Microsoft][ODBC SQL Server Driver]
I don't see anything Oracle in your question. It looks like you're getting an error using Microsoft's SQL Server driver, did you mean to post this to a forum on Microsoft's site perhaps? -
Microsoft][ODBC SQL Server Driver]Optional feature not implemented
this is my program code for java jdbc:odbc SQL connectivity
but iam getting the error as
*java.sql.SQLException: [Microsoft][ODBC SQL Server Driver]Optional feature not implemented*
package desktopapplication2;
import java.sql.*;
* @author Bharat Raj Verma
public class db {
void get(String gr,String fn,String ln,String job ,Integer rate,Integer ot,String att,long amt,String cmt)
try
Connection con=null,con1=null;
Statement stmt2;
String query = "Update dbo.attend SET Gr = ? , fn = ? ,ln = ?, job = ? , rate = ? , ot = ? , att = ? ,amt = ? , comment = ?";
// String query1 = "Select accnum rom dbo.newacc where accnum= ?";
String url = "jdbc:odbc:bharat";
Class.forName("sun.jdbc.odbc.JdbcOdbcDriver");
con = DriverManager.getConnection(url,"","");
con1 = DriverManager.getConnection(url,"","");
System.out.println("connection Established");
stmt2 = con.createStatement();
Statement stmt = con1.createStatement();
ResultSet rs;
rs=stmt.executeQuery("select * from dbo.attend");
while(rs.next())
String cmp1= rs.getString("gr");
if(cmp1.equalsIgnoreCase(gr))
PreparedStatement ps1 = con.prepareStatement(query);
System.out.println("Insisde RS");
ps1.setString(1,gr);
ps1.setString(2,fn);
ps1.setString(3,ln);
ps1.setString(4,job);
ps1.setInt(5,rate);
ps1.setInt(6,ot);
ps1.setString(7,att);
ps1.setLong(8,amt);
ps1.setString(9,cmt);
System.out.println("SSS");
// ps1.setString(1,gr);
ps1.executeUpdate();
System.out.println("Success");
catch(Exception e1)
System.err.println(e1);
}This is the SQL table in which iam trying to insert the value
SET ANSI_PADDING OFF
create table attend
Gr VARCHAR(20) primary key,
fn VARCHAR (25),
ln VARCHAR(25),
job VARCHAR(25),
rate integer,
ot integer,
att varchar(10),
amt varchar (10),
comment varchar(70)
)the complete output is
init:
deps-jar:
Compiling 1 source file to C:\Documents and Settings\Bharat Raj Verma\My Documents\NetBeansProjects\DesktopApplication2\build\classes
compile:
run:
connection Established
Insisde RS
java.sql.SQLException: [Microsoft][ODBC SQL Server Driver]Optional feature not implemented
BUILD SUCCESSFUL (total time: 29 seconds)
here is the stack trace
java.sql.SQLException: [Microsoft][ODBC SQL Server Driver]Optional feature not implemented
at sun.jdbc.odbc.JdbcOdbc.createSQLException(JdbcOdbc.java:6958)
at sun.jdbc.odbc.JdbcOdbc.standardError(JdbcOdbc.java:7115)
at sun.jdbc.odbc.JdbcOdbc.SQLBindInParameterBigint(JdbcOdbc.java:1225)
at sun.jdbc.odbc.JdbcOdbcPreparedStatement.setLong(JdbcOdbcPreparedStatement.java:592)
at desktopapplication2.db.get(db.java:47)
at desktopapplication2.DesktopApplication2View.jButton1ActionPerformed(DesktopApplication2View.java:394)
at desktopapplication2.DesktopApplication2View.access$800(DesktopApplication2View.java:22)
at desktopapplication2.DesktopApplication2View$4.actionPerformed(DesktopApplication2View.java:183)
at javax.swing.AbstractButton.fireActionPerformed(AbstractButton.java:1849)
at javax.swing.AbstractButton$Handler.actionPerformed(AbstractButton.java:2169)
at javax.swing.DefaultButtonModel.fireActionPerformed(DefaultButtonModel.java:420)
at javax.swing.DefaultButtonModel.setPressed(DefaultButtonModel.java:258)
at javax.swing.plaf.basic.BasicButtonListener.mouseReleased(BasicButtonListener.java:236)
at java.awt.Component.processMouseEvent(Component.java:5517)
at javax.swing.JComponent.processMouseEvent(JComponent.java:3135)
at java.awt.Component.processEvent(Component.java:5282)
at java.awt.Container.processEvent(Container.java:1966)
at java.awt.Component.dispatchEventImpl(Component.java:3984)
at java.awt.Container.dispatchEventImpl(Container.java:2024)
at java.awt.Component.dispatchEvent(Component.java:3819)
at java.awt.LightweightDispatcher.retargetMouseEvent(Container.java:4212)
at java.awt.LightweightDispatcher.processMouseEvent(Container.java:3892)
at java.awt.LightweightDispatcher.dispatchEvent(Container.java:3822)
at java.awt.Container.dispatchEventImpl(Container.java:2010)
at java.awt.Window.dispatchEventImpl(Window.java:1791)
at java.awt.Component.dispatchEvent(Component.java:3819)
at java.awt.EventQueue.dispatchEvent(EventQueue.java:463)
at java.awt.EventDispatchThread.pumpOneEventForHierarchy(EventDispatchThread.java:242)
at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:163)
at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:157)
at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:149)
at java.awt.EventDispatchThread.run(EventDispatchThread.java:110)
Plz can anyone help ???and what was the solution?
thanks in advance
brindy -
[ODBC SQL Server Driver]Optional feature not implemented
Hi,
Has anyone faced such error @ analysis,
Error Codes: OPR4ONWY:U9IM8TAC:OI2DL65P
State: HY000. Code: 10058. [NQODBC] [SQL_STATE: HY000] [nQSError: 10058] A general error has occurred. [nQSError: 43113] Message returned from OBIS. [nQSError: 43119] Query Failed: [nQSError: 16001] ODBC error state: S1C00 code: 0 message: [Microsoft][ODBC SQL Server Driver]Optional feature not implemented. [nQSError: 16012] ODBC error occurred while binding the parameters of a SQL statement. (HY000)
we are having some issue on DBfeature check box issue.
Thanks
DevaHi,
Yes. after that only i am getting error. if i enabled Query DBMS then report is working with out error (we don't want to use query dbms option that's i just query dbms off option by Reset to default) then its thoewing error.
Thanks
Deva -
Does SQL Server have a feature simiar to RMAN Duplicate
I have a production server and a test server (SQL Server) I am familiar with backup database and restore database and know that this can be automated. However, I was wondering if SQL Server had any feature similar to Oracle RMAN duplicate?
Thanks! OrcldudeHello,
If you are looking for a tool to copy or clone a database like RMAN does, then look at the following
resources:
http://msdn.microsoft.com/en-us/library/ms188664.aspx
(Copy Database Wizard)
http://msdn.microsoft.com/en-us/library/ee210545.aspx
(Publish a database)
http://msdn.microsoft.com/en-us/library/ee210754.aspx
(Clone a server)
Hope this helps.
Regards,
Alberto Morillo
SQLCoffee.com -
SQL Server installation paths best practices
In my company we're planning to setup a new (consolidated) SQL Server 2012 server (on Windows 2012 R2, VMWare). Current situation is there is a SQL Server 2000, a few SQL Server 2008 Express and a lot of Access databases. For the installation I'm wondering
what the best selections for the various installation paths are. Our infra colleagues (offshore) have the following standard partition setup for SQL Server servers:
C:\ OS
E:\ Application
L:\ Logs
S:\ DB
T:\ TEMPDB
And during the installation I have to make a choice for the following
Shared feature directory: x:\Program Files\Microsoft SQL Server\
Shared feature directory (x86): x:\Program Files\Microsoft SQL Server\
Instance root directory (SQL Server, Analysis Services, Reporting Services): x:\Program Files\Microsoft SQL Server\
Database Engine Configuration Data Directories:
Data root directory: x:\Program Files\Microsoft SQL Server\
User database directory: x:\Program Files\Microsoft SQL Server\MSSQL11.x\MSSQL\...
User database log directory: x:\Program Files\Microsoft SQL Server\MSSQL11.x\MSSQL\...
Temp DB directory: x:\Program Files\Microsoft SQL Server\MSSQL11.x\MSSQL\...
Temp DB log directory: x:\Program Files\Microsoft SQL Server\MSSQL11.x\MSSQL\...
Backup directory: x:\Program Files\Microsoft SQL Server\MSSQL11.x\MSSQL\...
Analysis Services Configuration Data Directories:
User database directory: x:\Program Files\Microsoft SQL Server\MSSQL11.x\MSSQL\...
User database log directory: x:\Program Files\Microsoft SQL Server\MSSQL11.x\MSSQL\...
Temp DB directory: x:\Program Files\Microsoft SQL Server\MSSQL11.x\MSSQL\...
Temp DB log directory: x:\Program Files\Microsoft SQL Server\MSSQL11.x\MSSQL\...
Backup directory: x:\Program Files\Microsoft SQL Server\MSSQL11.x\MSSQL\...
Distributed Replay Client:
Working Directory: x:\Program Files (x86)\Microsoft SQL Server\DReplayClient\WorkingDir\
Result Directory: x:\Program Files (86)\Microsoft SQL Server\DReplayClient\ResultDir\
So I'd like some on assistance on the filling in the x drive letters. I understand it's best practice to seperate the data files and the logs files. But should that also be the case for TempDB? And should both the database and tempdb log files go to the
same log paritition then? What about the backup directories? Any input is very much appreciated!
Btw, I followed the http://www.sqlservercentral.com/blogs/basits-sql-server-tips/2012/06/23/sql-server-2012-installation-guide/ guide for the installation (Test server now).You can place all installation libraries on E:\ Drive.
>>So I'd like some on assistance on the filling in the x drive letters. I understand it's best practice
to seperate the data files and the logs files. But should that also be the case for TempDB? And should both the database and tempdb log files go to the same log paritition then? What about the backup directories? Any input is very much appreciated!
You can place tempdb data files on T drive and I prefer to place tempdb log and user database log file
on the same drive i.e is L:\ Drive.
>>Backup directories
If you are not using any third party tool then i would prefer to create separate drive for backup.
Refer the below link for further reading
http://www.brentozar.com/archive/2009/02/when-should-you-put-data-and-logs-on-the-same-drive/
--Prashanth -
How to test a new SQL Server installation
Hi,
We are in the process of consolidating several database on a single SQL Server instance.
We first installed a test server and we want to use this installation as the base for our production server.
I checked:
- the server collation is the one required SQL_Latin1_General_CP1_CI_AI
- services are running: SQL Server Database engine, Analysis services, Report Services, Integration Services are running
I identified the following problems:
- SQL Server Agent is not running and I can not start it from the services panes of the computer management
- When I want to connect to SQL Server Integeration Services from SQL Server Management Studio I get a pop up error message:
failed to retrieve data for this request (Microsoft.SqlServer.Management.Sdk.Sfc)
acces is denied
What else should I check?
We are a small team and I am new to database administration, every advice is appreciated.And make sure to configure all the basic configuration as per the requirment... few of them is below... there might be many but its all upto you and your business requirments...
Memory
Backup compression
Error Log
Securit, logins, aduiting ( Minimum failed and successful logins )
Ports ( Static or dynamic -- Named Instance )
Default location of the data,log(ldf),backup -- If you have missed this at the time of installation.
authentication mode
disable or change the SA password ( Enforce password policy )
Service packs and hot fixes, CU's
Configure all the required basic maintenance jobs
SQL Service accounts or MSA in case of standalone hosts Windows 7, Windows Server 2008 R2 or later ..
http://technet.microsoft.com/en-us/library/dd560633%28v=ws.10%29.aspx
Monitoring if required
Move all the required configuration details from your existing servers using --- sp_configure
Move all the logins and jobs..
https://support.microsoft.com/kb/918992?wa=wsignin1.0
Change the databases compatibility level after restoring in new server
rebuild the index and update the stats once after restoring it in new server.
Most importantaly review the setup log once after the complete installation.. and sql error log, eventlog..
DAC --- http://technet.microsoft.com/en-us/library/ms178068%28v=sql.105%29.aspx
In case if you use policy based management please check that as well..
http://msdn.microsoft.com/en-us/library/bb510667.aspx
Raju Rasagounder Sr MSSQL DBA -
SQL Server Installation on Windows 7 Professional sp 1
Hi Everyone,
I have windows 7 professional sp1 installed on my pc.
I am planning to install SQL server 2008 on my pc.
As I am using sp1 os, I have to install SQL server 2008 sp1 also.
I have enabled .net framework 3.5, installed sql server 2008, and sql server 2008 sp1.
But when I tried to connect to server I am getting the below error.
The below is services state information.
Thanks and Regards, Readers please vote for my posts if the questions i asked are helpful.I am getting an error like "this is used by another application" when I tried to delete the entries starting with "Microsoft.SqlServer".
Can you please help me on this.
Hi G Srikar Reddy,
Please ensure that you have uninstalled SQL Server 2008 instance and other SQL Server 2008 R2 components completely, and restart the computer.
Besides using the Windows Installer cleanup tool , you can also perform the following steps to uninstall
SQL Server 2008 manually.
a. Uninstall all SQL Server 2008 components ( including the entry "Support for SQL Server Setup") from the control panel.
b. Backup the registry.
c. Delete the following keys in regedit:
--HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server
--HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer
d. Go to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall and delete all the sub-keys referencing SQL Server.
e. Go to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services and delete all the keys referencing SQL Server.
f. Rename all the SQL Server folders in the computer.
g. Reboot the machine.
Thanks,
Lydia Zhang -
Error 1406 : could not write value to key \software sql server installation
I've problems installins SQL Server with management studio
I tried different steps starting from
Changing permissions of the local user while running both registry editor and installer with adminstrator
i've checked most similar posts here in the forums and followed their steps but no progress ,
this is the error message
i couldn't resolve it till now , i'm in this problem for 4 days till now tried different suggestions but no progress , i'm in a hurry , so please help me
Regards,
OmarOverall summary:
Final result: Failed: see details below
Exit code (Decimal): -2068052610
Start time: 2014-08-05 23:21:36
End time: 2014-08-05 23:29:12
Requested action: Install
Setup completed with required actions for features.
Troubleshooting information for those features:
Next step for Adv_SSMS: Use the following information to resolve the error, and then try the setup process again.
Next step for SSMS: Use the following information to resolve the error, and then try the setup process again.
Machine Properties:
Machine name: OMAR
Machine processor count: 8
OS version: Windows 8
OS service pack:
OS region: United States
OS language: English (United States)
OS architecture: x64
Process architecture: 64 Bit
OS clustered: No
Product features discovered:
Product Instance Instance ID Feature
Language Edition Version Clustered Configured
SQL Server 2014 Client Tools Connectivity
1033 12.0.2000.8 No Yes
SQL Server 2014 Client Tools Backwards Compatibility
1033 12.0.2000.8 No Yes
SQL Server 2014 Client Tools SDK
1033 12.0.2000.8 No
Yes
Package properties:
Description: Microsoft SQL Server 2014
ProductName: SQL Server 2014
Type: RTM
Version: 12
SPLevel: 0
Installation location: E:\Sources\SQL Server with management studio\SQLManagementStudio_x64_ENU\x64\setup\
Installation edition: Express
Product Update Status:
None discovered.
User Input Settings:
ACTION: Install
ADDCURRENTUSERASSQLADMIN: true
AGTSVCACCOUNT: <empty>
AGTSVCPASSWORD: <empty>
AGTSVCSTARTUPTYPE: Manual
ASBACKUPDIR: Backup
ASCOLLATION: Latin1_General_CI_AS
ASCONFIGDIR: Config
ASDATADIR: Data
ASLOGDIR: Log
ASPROVIDERMSOLAP: 1
ASSERVERMODE: MULTIDIMENSIONAL
ASSVCACCOUNT: <empty>
ASSVCPASSWORD: <empty>
ASSVCSTARTUPTYPE: Automatic
ASSYSADMINACCOUNTS: <empty>
ASTEMPDIR: Temp
BROWSERSVCSTARTUPTYPE: Disabled
CLTCTLRNAME: <empty>
CLTRESULTDIR: <empty>
CLTSTARTUPTYPE: 0
CLTSVCACCOUNT: <empty>
CLTSVCPASSWORD: <empty>
CLTWORKINGDIR: <empty>
COMMFABRICENCRYPTION: 0
COMMFABRICNETWORKLEVEL: 0
COMMFABRICPORT: 0
CONFIGURATIONFILE:
CTLRSTARTUPTYPE: 0
CTLRSVCACCOUNT: <empty>
CTLRSVCPASSWORD: <empty>
CTLRUSERS: <empty>
ENABLERANU: false
ENU: true
ERRORREPORTING: false
FEATURES: SSMS, ADV_SSMS
FILESTREAMLEVEL: 0
FILESTREAMSHARENAME: <empty>
FTSVCACCOUNT: <empty>
FTSVCPASSWORD: <empty>
HELP: false
IACCEPTSQLSERVERLICENSETERMS: true
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: <empty>
INSTANCENAME: <empty>
ISSVCACCOUNT: NT AUTHORITY\Network Service
ISSVCPASSWORD: <empty>
ISSVCSTARTUPTYPE: Automatic
MATRIXCMBRICKCOMMPORT: 0
MATRIXCMSERVERNAME: <empty>
MATRIXNAME: <empty>
NPENABLED: 0
PID: *****
QUIET: false
QUIETSIMPLE: false
ROLE: AllFeatures_WithDefaults
RSINSTALLMODE: DefaultNativeMode
RSSHPINSTALLMODE: DefaultSharePointMode
RSSVCACCOUNT: <empty>
RSSVCPASSWORD: <empty>
RSSVCSTARTUPTYPE: Automatic
SAPWD: <empty>
SECURITYMODE: <empty>
SQLBACKUPDIR: <empty>
SQLCOLLATION: SQL_Latin1_General_CP1_CI_AS
SQLSVCACCOUNT: <empty>
SQLSVCPASSWORD: <empty>
SQLSVCSTARTUPTYPE: Automatic
SQLSYSADMINACCOUNTS: <empty>
SQLTEMPDBDIR: <empty>
SQLTEMPDBLOGDIR: <empty>
SQLUSERDBDIR: <empty>
SQLUSERDBLOGDIR: <empty>
SQMREPORTING: false
TCPENABLED: 0
UIMODE: AutoAdvance
UpdateEnabled: true
UpdateSource: MU
USEMICROSOFTUPDATE: false
X86: false
Configuration file: C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20140805_232135\ConfigurationFile.ini
Detailed results:
Feature: Management Tools - Complete
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, and then try the setup process again.
Component name: SQL Server Management Services
Component error code: 1406
Component log file: C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20140805_232135\sql_ssms_Cpu64_1.log
Error description: Could not write value to key \SOFTWARE. Verify that you have sufficient access to that key, or contact your support personnel.
Error help link: http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=12.0.2000.8&EvtType=sql_ssms.msi%40WriteRegistryValues%401406
Feature: Management Tools - Basic
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, and then try the setup process again.
Component name: SQL Server Management Services
Component error code: 1406
Component log file: C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20140805_232135\sql_ssms_Cpu64_1.log
Error description: Could not write value to key \SOFTWARE. Verify that you have sufficient access to that key, or contact your support personnel.
Error help link: http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=12.0.2000.8&EvtType=sql_ssms.msi%40WriteRegistryValues%401406
Rules with failures:
Global rules:
Scenario specific rules:
Rules report file: C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20140805_232135\SystemConfigurationCheck_Report.htm
Maybe you are looking for
-
Hi All, i am trying to create material stock using MB1c T code and movement type 561. I entered plant and storage location , doc date and posting date. when i try to execute the transaction after giving material and quantity , i am getting an error
-
Restriction to component selection in Service Order
Hi, Scenario is a Repair Technician selects a Fault Code in the Notification. Component entry (Part consumption) in the Service Order is allowed only if the selected Fault Code requires a Part replacement. Is it possible to restrict component selecti
-
My macbook air is very slow to inciate
My macbook air is taking too long time to iniciate. It is relatively new (got it in october/11) . How can I fix this?
-
Check authrozation problems in WebDynpro
Hello, In SAPGUI there exists a tool for analysing authorization errors (go in a SAPGUI menu to System->Utilities->Display Authorization Checks or start transaction code SU53). The tool display which authorization check has failed and displays the cu
-
Hello folks, We are using both Self Service timecards and TK but usage is restricted to certain scenarios. TK, based time entry done by HR, is used when employees default timecards. HR enters the time. The problem is when HR enters the timecard, it s