Manual Startup of CMS

Whenever the PC is rebooted (XP sp2), CMS will not automatically startup and we have to manually start it. Is there a setting somewhere for it to start at Windows startup?

That is the problem:
3896 3900 assert failure: (.\ODBCDatabaseSubsystem_impl.cpp:731). (0 : [Microsoft][ODBC SQL Server Driver][SQL Server]Cannot open database "crystal" requested by the login. The login failed.).
3896 3900 assert failure: (\backend\cms\include\DatabaseSubsystem.h:166). (0 : Calling SQLDriverConnect).
And I added the dependency to the CMS service:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\BOBJCentralMS\DependOnService added MSSQL$SQLEXPRESS
MSSQL$SQLEXPRESS is the service name that should start sqlservr.exe
But this is not working

Similar Messages

Manual startup of 8i database

Hi I 've Oracle 8i(8.1.5 release) for NT. I runs it on Windows 2000 professional platform.
When I logon to my machine Oracle Database gets itself startsup automatically,and so it takes too much time to start my machine completely and also acquire too much memory.
Is it possible that I can start Oracle Database mannually as in Oracle 8? So why it will faster starting up of my machine. It shouldn't starts automatically with windows startup..
Thanks Please Reply...
Abhishek

Hi
You can modify the parameter ORA_<SID>_AUTOSTART in the registry. If you set it to FALSE, when the service is started the database is not opened. For more info http://download-uk.oracle.com/docs/cd/A87861_01/NT817EE/win.817/a73008/apc.htm
You can also completely disable the NT service.
Chris

How to customize oracle to manually startup/shutdown in Linux ?

Hello Friends,
I am having Oracle 10g XE installed on Ubuntu 7.10..It is working fine..
I want to make it custom startup and shutdown..(As of now it is starting up when gutsy boots) as it is not required Oracle to run each time...Please suggest the way to do it.
Thanks in Advance

Hi,
For Ubuntu, there has an alternative utility for editing runlevels that can be used just like chkconfig on RedHat.
To install:
# sudo apt-get install sysv-rc-conf
Then,
# sysv-rc-conf oracle-xe off
Cheers
Terry

Manual startup/shutdown of windows services using command prompt or .bat

Hi,
I know that we could shutdown and start of SAP in windows using the following commands in a .bat file.
SAP:
     stopsap name=<SID> nr=<SYSNR> SAPDIAHOST=<host>
     startsap name=<SID> nr=<SYSNR> SAPDIAHOST=<host>
OS Collector:
     saposcol -k
Oracle Listener:
     lsnrctl stop / start
How about the following services:
     SAPDEV_00
     OracleOraHome92Agent
     OracleServiceDEV
How can I stop and start of these services in a batch file?
thanks,
kbas

Try,
net stop <service name>
net start <service name>
Message was edited by:
        Bidwan Baruah

Remotely starting the CMS server using a SSH script in a Unix environment.

Is it possible to remotely start a CMS server using a shell script which starts an SSH session and runs the startservers command asin the command below:
ssh -o ConnectionAttempts=2 -o ConnectTimeout=10 -l boadmin huxd0226 '/opt/BO/boxir2/bobje/startservers'
The command securely logs into the server (huxd0226) and runs the command described in single quotes.
the CMS server actually appears to start but then dies inexplicably and displays no errors in the trace logs. The full log file is displayed below:-
Timestamp ProcessID ThreadID Message
Thu Sep 18 10:59:05 2008 913548 1 (wireobinit.cpp:97): trace messa
ge: Creating the shared CWireObject::PropertyNameMap
Thu Sep 18 10:59:05 2008 913548 1 (wireobinit.cpp:119): trace mess
age: Setting static property map
Thu Sep 18 10:59:05 2008 913548 1 (wireobinit.cpp:126): trace mess
age: CWireObject::InitializeStaticPropertyMap() - reference count: 1
Thu Sep 18 10:59:05 2008 913548 1 Log: level=3 cat=1 msg=35100 p=C
entral Management Server started
Thu Sep 18 10:59:05 2008 913548 1 trace message: SIServerControlle
r::run: Before initialize
Thu Sep 18 10:59:05 2008 913548 1 (sidaemon.cpp:416): trace messag
e: SUNIXDaemon::init: starting
Thu Sep 18 10:59:05 2008 913548 1 trace message: SUNIXDaemon::init
: redirecting stdio to /dev/null
Thu Sep 18 10:59:05 2008 913548 1 (sidaemon.cpp:209): trace messag
e: installing fg terminiation handler
Thu Sep 18 10:59:05 2008 913548 1 (sidaemon.cpp:220): trace messag
e: installing abnormal sys handler
Thu Sep 18 10:59:05 2008 913548 1 (sidaemon.cpp:506): trace messag
e: SUNIXDaemon::init: finished
Thu Sep 18 10:59:12 2008 913548 1 trace message: GetClockSequenceU
pdater: Getting clock sequence updater
Thu Sep 18 10:59:13 2008 913548 1 trace message: SSimpleBuffer::lo
adFromFile: calling mmap(): fileName[/opt/BO/boxir2/bobje/enterprise115/aix_rs60
00/sqlrule.llr], lFileLength47132, fd10
Thu Sep 18 10:59:13 2008 913548 1 trace message: SSimpleBuffer::lo
adFromFile: calling mmap(): fileName[/opt/BO/boxir2/bobje/enterprise115/aix_rs60
00/sqlrule.dfa], lFileLength26824, fd10
Thu Sep 18 10:59:14 2008 913548 1 trace message: Loading: database
subsystem: db2databasesubsystem
This is exactly the same as a normal manual startup of the CMS server except it dies at the loading of the db2databasesubsystem section.
Business Objects is patched to Fix Pack 3.6 and is clustered in a HACMP environment. It is a requirement that when the DB2 database fails, shortly after restarting it can automatically start the Business Objects services remotely.
SSH will work if the command is entered manually from within a secured session, but it is only when automated that the failure occurs. Does anyone have an idea on why this is happening and whether it is in fact possible ?

we're going to run into deep offtopic if we continue that line ))
But I believe there is a big push to get the forum format actualy working this time.

Setup problem - sql server 2014 - "could not find the database engine startup handle" - 0x851a0019

I tried to install ,deleted and re-installed several times and no help at all.
visual studio 2013 with update 2 rc and adk installed in my computer.
error code: 0x851a0019
error messege in setup: could not find the database engine startup handle
edition: Microsoft SQL Server 2014 Enterprise (Evaluation)
logs:
Overall summary:
Final result: Failed: see details below
Exit code (Decimal): -2061893607
Start time: 2014-04-03 13:53:29
End time: 2014-04-03 14:47:48
Requested action: Install
Setup completed with required actions for features.
Troubleshooting information for those features:
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 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.
Machine Properties:
Machine name: ARIELUBA-PC
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 2012 SQLEXPRESS MSSQL11.SQLEXPRESS Database Engine Services 1033
Express Edition 11.1.3128.0 No Yes
SQL Server 2012 SQLEXPRESS MSSQL11.SQLEXPRESS SQL Server Replication 1033
Express Edition 11.1.3128.0 No Yes
SQL Server 2012 ADK MSSQL11.ADK Database Engine Services
1033 Express Edition 11.0.2100.60 No Yes
SQL Server 2012 ADK MSSQL11.ADK SQL Server Replication
1033 Express Edition 11.0.2100.60 No Yes
SQL Server 2012 LocalDB
1033 Express Edition 11.1.3412.0 No Yes
Package properties:
Description: Microsoft SQL Server 2014
ProductName: SQL Server 2014
Type: RTM
Version: 12
SPLevel: 0
Installation location: C:\Users\Arie Luba\Downloads\WS2012R2DC\SQLServer2014-x64-ENU\x64\setup\
Installation edition: Evaluation
Product Update Status:
None discovered.
User Input Settings:
ACTION: Install
ADDCURRENTUSERASSQLADMIN: true
AGTSVCACCOUNT: NT Service\SQLSERVERAGENT
AGTSVCPASSWORD: *****
AGTSVCSTARTUPTYPE: Manual
ASBACKUPDIR: C:\Program Files\Microsoft SQL Server\MSAS12.MSSQLSERVER\OLAP\Backup
ASCOLLATION: Hebrew_CI_AS
ASCONFIGDIR: C:\Program Files\Microsoft SQL Server\MSAS12.MSSQLSERVER\OLAP\Config
ASDATADIR: C:\Program Files\Microsoft SQL Server\MSAS12.MSSQLSERVER\OLAP\Data
ASLOGDIR: C:\Program Files\Microsoft SQL Server\MSAS12.MSSQLSERVER\OLAP\Log
ASPROVIDERMSOLAP: 1
ASSERVERMODE: MULTIDIMENSIONAL
ASSVCACCOUNT: NT Service\MSSQLServerOLAPService
ASSVCPASSWORD: <empty>
ASSVCSTARTUPTYPE: Automatic
ASSYSADMINACCOUNTS: ARIELUBA-PC\Arie Luba
ASTEMPDIR: C:\Program Files\Microsoft SQL Server\MSAS12.MSSQLSERVER\OLAP\Temp
BROWSERSVCSTARTUPTYPE: Automatic
CLTCTLRNAME:
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\120\Setup Bootstrap\Log\20140403_135327\ConfigurationFile.ini
CTLRSTARTUPTYPE: Manual
CTLRSVCACCOUNT: NT Service\SQL Server Distributed Replay Controller
CTLRSVCPASSWORD: <empty>
CTLRUSERS: ARIELUBA-PC\Arie Luba
ENABLERANU: false
ENU: true
ERRORREPORTING: false
FEATURES: SQLENGINE, REPLICATION, FULLTEXT, DQ, AS, RS, RS_SHP, RS_SHPWFE, DQC, CONN, IS, BC, SDK, BOL, SSMS, ADV_SSMS, DREPLAY_CTLR, DREPLAY_CLT, MDS
FILESTREAMLEVEL: 0
FILESTREAMSHARENAME: <empty>
FTSVCACCOUNT: NT Service\MSSQLFDLauncher
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: MSSQLSERVER
INSTANCENAME: MSSQLSERVER
ISSVCACCOUNT: NT Service\MsDtsServer120
ISSVCPASSWORD: <empty>
ISSVCSTARTUPTYPE: Automatic
MATRIXCMBRICKCOMMPORT: 0
MATRIXCMSERVERNAME: <empty>
MATRIXNAME: <empty>
NPENABLED: 0
PID: *****
QUIET: false
QUIETSIMPLE: false
ROLE: AllFeatures_WithDefaults
RSINSTALLMODE: DefaultNativeMode
RSSHPINSTALLMODE: SharePointFilesOnlyMode
RSSVCACCOUNT: NT Service\ReportServer
RSSVCPASSWORD: <empty>
RSSVCSTARTUPTYPE: Automatic
SAPWD: <empty>
SECURITYMODE: <empty>
SQLBACKUPDIR: <empty>
SQLCOLLATION: Hebrew_CI_AS
SQLSVCACCOUNT: NT Service\MSSQLSERVER
SQLSVCPASSWORD: <empty>
SQLSVCSTARTUPTYPE: Automatic
SQLSYSADMINACCOUNTS: ARIELUBA-PC\Arie Luba
SQLTEMPDBDIR: <empty>
SQLTEMPDBLOGDIR: <empty>
SQLUSERDBDIR: <empty>
SQLUSERDBLOGDIR: <empty>
SQMREPORTING: false
TCPENABLED: 1
UIMODE: Normal
UpdateEnabled: true
UpdateSource: MU
USEMICROSOFTUPDATE: false
X86: false
Configuration file: C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20140403_135327\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: 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 Database Engine Services Instance Features
Component error code: 0x851A0019
Error description: Could not find the Database Engine startup handle.
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=0xD15B4EB2%400x4BDAF9BA%401306%4025&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4025
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: 0x851A0019
Error description: Could not find the Database Engine startup handle.
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=0xD15B4EB2%400x4BDAF9BA%401306%4025&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4025
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: 0x851A0019
Error description: Could not find the Database Engine startup handle.
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=0xD15B4EB2%400x4BDAF9BA%401306%4025&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4025
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: 0x851A0019
Error description: Could not find the Database Engine startup handle.
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=0xD15B4EB2%400x4BDAF9BA%401306%4025&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4025
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: 0x851A0019
Error description: Could not find the Database Engine startup handle.
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=0xD15B4EB2%400x4BDAF9BA%401306%4025&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4025
Feature: Master Data Services
Status: Passed
Feature: Distributed Replay Client
Status: Passed
Feature: Distributed Replay Controller
Status: Passed
Feature: Integration Services
Status: Passed
Feature: Data Quality Client
Status: Passed
Feature: Analysis Services
Status: Passed
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: Setup Support Files
Status: Passed
Rules with failures:
Global rules:
Scenario specific rules:
Rules report file: C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20140403_135327\SystemConfigurationCheck_Report.htm
2014-04-03 14:14:28.01 Server Microsoft SQL Server 2014 - 12.0.2000.8 (X64)
Feb 20 2014 20:04:26
Copyright (c) Microsoft Corporation
Enterprise Evaluation Edition (64-bit) on Windows NT 6.3 <X64> (Build 9600: ) (Hypervisor)
2014-04-03 14:14:28.01 Server UTC adjustment: 3:00
2014-04-03 14:14:28.01 Server (c) Microsoft Corporation.
2014-04-03 14:14:28.01 Server All rights reserved.
2014-04-03 14:14:28.01 Server Server process ID is 7148.
2014-04-03 14:14:28.01 Server System Manufacturer: 'Dell Inc.', System Model: 'Inspiron N5110'.
2014-04-03 14:14:28.01 Server Authentication mode is WINDOWS-ONLY.
2014-04-03 14:14:28.01 Server Logging SQL Server messages in file 'C:\Program Files\Microsoft SQL Server\MSSQL12.MSSQLSERVER\MSSQL\Log\ERRORLOG'.
2014-04-03 14:14:28.01 Server The service account is 'NT Service\MSSQLSERVER'. This is an informational message; no user action is required.
2014-04-03 14:14:28.01 Server Registry startup parameters:
-d C:\Program Files\Microsoft SQL Server\MSSQL12.MSSQLSERVER\MSSQL\DATA\master.mdf
-e C:\Program Files\Microsoft SQL Server\MSSQL12.MSSQLSERVER\MSSQL\Log\ERRORLOG
-l C:\Program Files\Microsoft SQL Server\MSSQL12.MSSQLSERVER\MSSQL\DATA\mastlog.ldf
2014-04-03 14:14:28.01 Server Command Line Startup Parameters:
-s "MSSQLSERVER"
-m "SqlSetup"
-Q
-q "Hebrew_CI_AS"
-T 4022
-T 4010
-T 3659
-T 3610
-T 8015
2014-04-03 14:14:28.28 Server SQL Server detected 1 sockets with 4 cores per socket and 8 logical processors per socket, 8 total logical processors; using 8 logical processors based on SQL Server licensing. This is an informational message;
no user action is required.
2014-04-03 14:14:28.28 Server SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
2014-04-03 14:14:28.28 Server Detected 8099 MB of RAM. This is an informational message; no user action is required.
2014-04-03 14:14:28.28 Server Using conventional memory in the memory manager.
2014-04-03 14:14:28.31 Server Default collation: SQL_Latin1_General_CP1_CI_AS (us_english 1033)
2014-04-03 14:14:28.34 Server Perfmon counters for resource governor pools and groups failed to initialize and are disabled.
2014-04-03 14:14:28.36 Server Query Store settings initialized with enabled = 1,
2014-04-03 14:14:28.36 Server The maximum number of dedicated administrator connections for this instance is '1'
2014-04-03 14:14:28.36 Server Node configuration: node 0: CPU mask: 0x00000000000000ff:0 Active CPU mask: 0x00000000000000ff: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-04-03 14:14:28.38 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-04-03 14:14:28.39 Server Database Mirroring Transport is disabled in the endpoint configuration.
2014-04-03 14:14:28.39 spid8s Warning ******************
2014-04-03 14:14:28.39 spid8s SQL Server started in single-user mode. This an informational message only. No user action is required.
2014-04-03 14:14:28.40 spid8s Starting up database 'master'.
2014-04-03 14:14:28.42 Server Software Usage Metrics is disabled.
2014-04-03 14:14:28.48 Server CLR version v4.0.30319 loaded.
2014-04-03 14:14:28.56 Server Common language runtime (CLR) functionality initialized using CLR version v4.0.30319 from C:\Windows\Microsoft.NET\Framework64\v4.0.30319\.
2014-04-03 14:14:28.62 spid8s SQL Server Audit is starting the audits. This is an informational message. No user action is required.
2014-04-03 14:14:28.63 spid8s SQL Server Audit has started the audits. This is an informational message. No user action is required.
2014-04-03 14:14:28.64 spid8s SQL Trace ID 1 was started by login "sa".
2014-04-03 14:14:28.64 spid8s Server name is 'ARIELUBA-PC'. This is an informational message only. No user action is required.
2014-04-03 14:14:28.65 spid16s Password policy update was successful.
2014-04-03 14:14:28.66 spid16s Error: 17190, Severity: 16, State: 1.
2014-04-03 14:14:28.66 spid16s Initializing the FallBack certificate failed with error code: 1, state: 20, error number: 0.
2014-04-03 14:14:28.66 spid16s Unable to initialize SSL encryption because a valid certificate could not be found, and it is not possible to create a self-signed certificate.
2014-04-03 14:14:28.66 spid16s Error: 17182, Severity: 16, State: 1.
2014-04-03 14:14:28.66 spid16s TDSSNIClient initialization failed with error 0x80092004, status code 0x80. Reason: Unable to initialize SSL support. Cannot find object or property.
2014-04-03 14:14:28.66 spid16s Error: 17182, Severity: 16, State: 1.
2014-04-03 14:14:28.66 spid16s TDSSNIClient initialization failed with error 0x80092004, status code 0x1. Reason: Initialization failed with an infrastructure error. Check for previous errors. Cannot find object or property.
2014-04-03 14:14:28.66 spid16s Error: 17826, Severity: 18, State: 3.
2014-04-03 14:14:28.66 spid16s Could not start the network library because of an internal error in the network library. To determine the cause, review the errors immediately preceding this one in the error log.
2014-04-03 14:14:28.67 spid16s Error: 17120, Severity: 16, State: 1.
2014-04-03 14:14:28.67 spid16s SQL Server could not spawn FRunCommunicationsManager thread. Check the SQL Server error log and the Windows event logs for information about possible related problems.
________________________________________________________________________________________________

Is it okay? (see below)
;SQL Server 2014 Configuration File
[OPTIONS]
; Specifies a Setup work flow, like INSTALL, UNINSTALL, or UPGRADE. This is a required parameter.
ACTION="Install"
; Detailed help for command line argument ROLE has not been defined yet.
ROLE="AllFeatures_WithDefaults"
; Use the /ENU parameter to install the English version of SQL Server on your localized Windows operating system.
ENU="True"
; Parameter that controls the user interface behavior. Valid values are Normal for the full UI,AutoAdvance for a simplied UI, and EnableUIOnServerCore for bypassing Server Core setup GUI block.
UIMODE="Normal"
; Setup will not display any user interface.
QUIET="False"
; Setup will display progress only, without any user interaction.
QUIETSIMPLE="False"
; Specify whether SQL Server Setup should discover and include product updates. The valid values are True and False or 1 and 0. By default SQL Server Setup will include updates that are found.
UpdateEnabled="True"
; Specify if errors can be reported to Microsoft to improve future SQL Server releases. Specify 1 or True to enable and 0 or False to disable this feature.
ERRORREPORTING="False"
; If this parameter is provided, then this computer will use Microsoft Update to check for updates.
USEMICROSOFTUPDATE="False"
; Specifies features to install, uninstall, or upgrade. The list of top-level features include SQL, AS, RS, IS, MDS, and Tools. The SQL feature will install the Database Engine, Replication, Full-Text, and Data Quality Services (DQS) server. The Tools feature
will install Management Tools, Books online components, SQL Server Data Tools, and other shared components.
FEATURES=SQLENGINE,REPLICATION,FULLTEXT,DQ,AS,RS,RS_SHP,RS_SHPWFE,DQC,CONN,IS,BC,SDK,BOL,SSMS,ADV_SSMS,DREPLAY_CTLR,DREPLAY_CLT,MDS
; Specify the location where SQL Server Setup will obtain product updates. The valid values are "MU" to search Microsoft Update, a valid folder path, a relative path such as .\MyUpdates or a UNC share. By default SQL Server Setup will search Microsoft Update
or a Windows Update service through the Window Server Update Services.
UpdateSource="MU"
; Displays the command line parameters usage
HELP="False"
; Specifies that the detailed Setup log should be piped to the console.
INDICATEPROGRESS="False"
; Specifies that Setup should install into WOW64. This command line argument is not supported on an IA64 or a 32-bit system.
X86="False"
; Specify the root installation directory for shared components. This directory remains unchanged after shared components are already installed.
INSTALLSHAREDDIR="C:\Program Files\Microsoft SQL Server"
; Specify the root installation directory for the WOW64 shared components. This directory remains unchanged after WOW64 shared components are already installed.
INSTALLSHAREDWOWDIR="C:\Program Files (x86)\Microsoft SQL Server"
; Specify a default or named instance. MSSQLSERVER is the default instance for non-Express editions and SQLExpress for Express editions. This parameter is required when installing the SQL Server Database Engine (SQL), Analysis Services (AS), or Reporting Services
(RS).
INSTANCENAME="MSSQLSERVER"
; Specify that SQL Server feature usage data can be collected and sent to Microsoft. Specify 1 or True to enable and 0 or False to disable this feature.
SQMREPORTING="False"
; Specify the Instance ID for the SQL Server features you have specified. SQL Server directory structure, registry structure, and service names will incorporate the instance ID of the SQL Server instance.
INSTANCEID="MSSQLSERVER"
; The computer name that the client communicates with for the Distributed Replay Controller service.
CLTCTLRNAME="SQLDRC"
; The Windows account(s) used to grant permission to the Distributed Replay Controller service.
CTLRUSERS="ARIELUBA-PC\Arie Luba"
; The account used by the Distributed Replay Controller service.
CTLRSVCACCOUNT="NT Service\SQL Server Distributed Replay Controller"
; The startup type for the Distributed Replay Controller service.
CTLRSTARTUPTYPE="Manual"
; The account used by the Distributed Replay Client service.
CLTSVCACCOUNT="NT Service\SQL Server Distributed Replay Client"
; The startup type for the Distributed Replay Client service.
CLTSTARTUPTYPE="Manual"
; The result directory for the Distributed Replay Client service.
CLTRESULTDIR="C:\Program Files (x86)\Microsoft SQL Server\DReplayClient\ResultDir"
; The working directory for the Distributed Replay Client service.
CLTWORKINGDIR="C:\Program Files (x86)\Microsoft SQL Server\DReplayClient\WorkingDir"
; RSInputSettings_RSInstallMode_Description
RSINSTALLMODE="DefaultNativeMode"
; RSInputSettings_RSInstallMode_Description
RSSHPINSTALLMODE="SharePointFilesOnlyMode"
; Specify the installation directory.
INSTANCEDIR="C:\Program Files\Microsoft SQL Server"
; Agent account name
AGTSVCACCOUNT="NT Service\SQLSERVERAGENT"
; Auto-start service after installation.
AGTSVCSTARTUPTYPE="Manual"
; Startup type for Integration Services.
ISSVCSTARTUPTYPE="Automatic"
; Account for Integration Services: Domain\User or system account.
ISSVCACCOUNT="NT Service\MsDtsServer120"
; The name of the account that the Analysis Services service runs under.
ASSVCACCOUNT="NT Service\MSSQLServerOLAPService"
; Controls the service startup type setting after the service has been created.
ASSVCSTARTUPTYPE="Automatic"
; The collation to be used by Analysis Services.
ASCOLLATION="Hebrew_CI_AS"
; The location for the Analysis Services data files.
ASDATADIR="C:\Program Files\Microsoft SQL Server\MSAS12.MSSQLSERVER\OLAP\Data"
; The location for the Analysis Services log files.
ASLOGDIR="C:\Program Files\Microsoft SQL Server\MSAS12.MSSQLSERVER\OLAP\Log"
; The location for the Analysis Services backup files.
ASBACKUPDIR="C:\Program Files\Microsoft SQL Server\MSAS12.MSSQLSERVER\OLAP\Backup"
; The location for the Analysis Services temporary files.
ASTEMPDIR="C:\Program Files\Microsoft SQL Server\MSAS12.MSSQLSERVER\OLAP\Temp"
; The location for the Analysis Services configuration files.
ASCONFIGDIR="C:\Program Files\Microsoft SQL Server\MSAS12.MSSQLSERVER\OLAP\Config"
; Specifies whether or not the MSOLAP provider is allowed to run in process.
ASPROVIDERMSOLAP="1"
; Specifies the list of administrator accounts that need to be provisioned.
ASSYSADMINACCOUNTS="ARIELUBA-PC\Arie Luba"
; Specifies the server mode of the Analysis Services instance. Valid values are MULTIDIMENSIONAL and TABULAR. The default value is MULTIDIMENSIONAL.
ASSERVERMODE="MULTIDIMENSIONAL"
; CM brick TCP communication port
COMMFABRICPORT="0"
; How matrix will use private networks
COMMFABRICNETWORKLEVEL="0"
; How inter brick communication will be protected
COMMFABRICENCRYPTION="0"
; TCP port used by the CM brick
MATRIXCMBRICKCOMMPORT="0"
; Startup type for the SQL Server service.
SQLSVCSTARTUPTYPE="Automatic"
; Level to enable FILESTREAM feature at (0, 1, 2 or 3).
FILESTREAMLEVEL="0"
; Set to "1" to enable RANU for SQL Server Express.
ENABLERANU="False"
; Specifies a Windows collation or an SQL collation to use for the Database Engine.
SQLCOLLATION="Hebrew_CI_AS"
; Account for SQL Server service: Domain\User or system account.
SQLSVCACCOUNT="NT Service\MSSQLSERVER"
; Windows account(s) to provision as SQL Server system administrators.
SQLSYSADMINACCOUNTS="ARIELUBA-PC\Arie Luba"
; Provision current user as a Database Engine system administrator for %SQL_PRODUCT_SHORT_NAME% Express.
ADDCURRENTUSERASSQLADMIN="True"
; Specify 0 to disable or 1 to enable the TCP/IP protocol.
TCPENABLED="1"
; Specify 0 to disable or 1 to enable the Named Pipes protocol.
NPENABLED="0"
; Startup type for Browser Service.
BROWSERSVCSTARTUPTYPE="Automatic"
; Specifies which account the report server NT service should execute under. When omitted or when the value is empty string, the default built-in account for the current operating system.
; The username part of RSSVCACCOUNT is a maximum of 20 characters long and
; The domain part of RSSVCACCOUNT is a maximum of 254 characters long.
RSSVCACCOUNT="NT Service\ReportServer"
; Specifies how the startup mode of the report server NT service. When
; Manual - Service startup is manual mode (default).
; Automatic - Service startup is automatic mode.
; Disabled - Service is disabled
RSSVCSTARTUPTYPE="Automatic"
; Add description of input argument FTSVCACCOUNT
FTSVCACCOUNT="NT Service\MSSQLFDLauncher"

Calling CoCreateInstance during OS and service startup

I have created 2 COM services ServiceA and SerivceB. ( OS Windows 7)
ServiceA: Automatic startup
ServiceB: Manual Startup
During OS start-up, Calling CoCreateInstance of ServiceB from ServiceA->Run() is delayed almost 100 seconds.
This issue only occurs during OS startup. below link says similar issue. But not applicable to Windows 7.
http://support.microsoft.com/kb/258943
Similar to http://stackoverflow.com/questions/3398105/calling-cocreateinstance-during-service-startup
Thanks, Renjith V R

It seems there is a solution in the second thread on stackoverflow.
I need reason. Not solution. I already have a solution of adding dependency. Also below link says service db is locked during service startup. Then the startup of second service should be failed. But my service is started successfully
but it takes more than 1.5 mins.
https://technet.microsoft.com/en-us/library/aa998749(v=exchg.65).aspx
Thanks, Renjith V R

Install Oracle DB as service that should be started manually

Hi!
I have laptop computer (Windows Business Vista) with small main disk space and I would like to install Oracle DB on removable HDD (I have already many programms installed there; RAM is sufficienly large to accomodate them) and my plan is to install Oracle database 11g on HDD as service that should be started manually. Are there any installation options to do this in the right way or are there any configuration options that should be tuned after installation, is there stardad way recommended by Oracle how to do this?
I know that after installation I can configure any Windows service one by one (including OracleServiceXXX, OracleDBConsoleXXX, ...JobSceduler, ...TNSListener, etc.) that they should be started only manually, but is there any procedure recommded by Oracle how to do this? E.g. maybe I can miss some service that should be configured and so on.
And maybe the similar procedure is available of application servers and services of SOA Suite as well?
And when I will have Oracle installation with manual startup-shutdown configuration - how should I start and shutdown database. I am reading http://download.oracle.com/docs/cd/B19306_01/server.102/b14231/start.htm and it says that I should issue only SQL statements for this - but as I understand - there should be some scripts that should be executed before those statements - at least - for startup of TNSListener. Is there some *.bat file suppled by Oracle for this?
Sorry for such questions, but they are asked by developer not administrator.
Thanks in advance!

Hi;
You can make installation to on your external HDD. If you want to service should be start manualy than you need to open services.msc and on related service > right click >properties >> startup type "manuel"
Regard
Helios

Oracle 8i Automatic Startup/shutdown on NT

After installing Oracle 8.1.6 on Win NT/2000 and creating a database a new service is created too (OracleServiceSID). My problem is that this new service (which works like oradim starting srvc,inst) does not startup the db when rebooting the machine. I need always manual startup/shutdown with a script that uses svrmgrl while in Oracle guides it seems that would be enough to start the service. Every parameter in the registry is set according to these guides to permit automatic startup/shutdown but only the service, not the db, starts and stops automatically. Where is my error?
Thanks
Alex
null

Dear Alexdelarg,
First launch the "Services" applet from the Windows NT Control Panel. Double-click on the "OracleService<SID>" service and verify that "Startup Type" is set to "Automatic", "Log On As" is set to "System Account", and that the "Allow Service to Interact with Desktop" check box is disabled.
Then launch REGEDIT and check that the Value String ORA_<SID>AUTOSTART within the key My Computer\HKEYLOCAL_MACHINE\SOFTWARE\ORACLE is set to "TRUE".
If the above does not rectify your startup problem, try issuing the following command from the Command Prompt:
<ORACLE_HOME>\bin\oradim -edit -sid <SID> -startmode auto
where <ORACLE_HOME> is the full path of your Oracle8i Server software and <SID> is the Service Identifier of your database.
Hope this helps!

Since 10.4.9 update: postfix needs to be started manually after reboot

Although mail services are all activated in Server Admin, postfix refuses to start up automatically after a system reboot.
All I need to do, is open a Terminal window and type "postfix start" and all is well.
The problem is, if we have a power outage or something else, then mail reception and sending is off-line until I discover that the server has rebooted itself, and I type in the commands again.
What could prevent postfix from starting up?
Ronald

Hi,
below the output of the commands, only the IP address in the range of the netmask was replaced with 12.34.56 and the domain name was replaced with domain.
The only strange thing is this line:
smtpdclientrestrictions = permit_mynetworks permit
which is the only line in which the parameters are not comma separated.
But why that would stop automatic startup, while manual startup works, is beyond me.
I also should add, I didn't mess with any config files except by proxy of Server Admin, since I'm more than aware of the fragile nature of such software dealing with such alterations.
Thanks for your help.
Ronald
[tigger:~] root# postconf -n
alias_maps = hash:/etc/aliases,hash:/var/mailman/data/aliases
always_bcc =
command_directory = /usr/sbin
config_directory = /etc/postfix
content_filter = smtp-amavis:[127.0.0.1]:10024
daemon_directory = /usr/libexec/postfix
debugpeerlevel = 2
enableserveroptions = yes
inet_interfaces = all
localrecipientmaps = proxy:unix:passwd.byname $alias_maps
luser_relay =
mail_owner = postfix
mailbox_transport = cyrus
mailq_path = /usr/bin/mailq
manpage_directory = /usr/share/man
mapsrbldomains = dun.dnsrbl.net,spam.dnsrbl.net,bl.spamcop.net,dynablock.easynet.nl,proxies.blac kholes.easynet.nl,cbl.abuseat.org,sbl.spamhaus.org,dnsbl.njabl.org,relays.ordb.o rg,opm.blitzed.org
masquerade_domains = domain.com
messagesizelimit = 26214400
mydestination = $myhostname,localhost.$mydomain,smtp,pop,imap,mailhost,domain.com,smtp.domain.c om,pop.domain.com,imap.domain.com,mail.domain.com,mailhost.domain.com,mail,local host,localhost.domain.com,127.0.0.1
mydomain = domain.com
mydomain_fallback = localhost
myhostname = smtp.domain.com
mynetworks = 127.0.0.0/8,12.34.56.96/27,12.34.56.64/27,12.34.56.32/27,12.34.56.192/27,12.34. 56.128/27,12.34.56.0/27,66.92.70.119/32,128.148.0.0/16,212.227.94.95/32,10.0.136 .0/24,207.210.106.210,61.222.108.90,140.211.11.2
mynetworks_style = host
newaliases_path = /usr/bin/newaliases
ownerrequestspecial = no
queue_directory = /private/var/spool/postfix
readme_directory = /usr/share/doc/postfix
recipient_delimiter = +
relayhost =
sample_directory = /usr/share/doc/postfix/examples
sendmail_path = /usr/sbin/sendmail
setgid_group = postdrop
smtpdclientrestrictions = permit_mynetworks permit
smtpdenforcetls = no
smtpdpw_server_securityoptions = plain,login,cram-md5
smtpdrecipientrestrictions = permitsasl_authenticated,permit_mynetworks,reject_unauthdestination,permit
smtpdsasl_authenable = yes
smtpdtls_certfile = /etc/certificates/DomainSSL.crt
smtpdtls_keyfile = /etc/certificates/DomainSSL.key
smtpdtlsloglevel = 0
smtpduse_pwserver = yes
smtpdusetls = yes
unknownlocal_recipient_rejectcode = 550
[tigger:~] root# ps -U clamav
PID TT STAT TIME COMMAND
66 ?? Ss 0:15.81 amavisd (master)
188 ?? Ss 0:00.82 freshclam -d -D -pfreshclam.pid -c 1
9683 ?? S 0:07.97 amavisd (ch8-avail)
9795 ?? S 0:09.19 amavisd (ch7-avail)
[tigger:~] root#

Exadata startup after power outage

Hi,
Recently we had a power cycle on one of our Exadata machines resulting in a partly running server.
After checking with:
dcli -l root -g all_group 'ipmitool sunoem cli "show /SP/policy" | grep abled'it seems some components do an autoboot and some don't.
When I checked another Exadata it showed the configuration was for a total autoboot.
Do you have any view what would be preferrable a manual startup or an autoboot?
Or maybe assess this setting for each Exadata individually?
Regards,
Tycho

Hi andy.colvin,
Can you give some more information on what didn't start up?The 4 db nodes didn't boot up on this half rack Exadata but the 7 cells did.
Support pointed me to 1470536.1 about the issue.
It could be in firmware (Active image version: 11.2.3.1.0.120304) or ACS changed the standards for the policy in the ILOM.
I have a second half rack (Active image version: 11.2.2.4.2.111221) which is configured to do a full autoboot (eg HOST_LAST_POWER_STATE = enabled) after a power outage. For now I have changed the ILOM setting to enabled and I will wait for a final answer from support.
Regards,
Tycho

Reg: Automatic Database Startup

Sir,
I would like to get my datbase Open automatically when the Machine where the database resides get restarted.
Now , What happens is that , I need to manually startup the database in the machine where database resides. I would like this to be automatic (i.e) the database should go up when the machine is restarted.
Kindly do provide me the solution for the same.
Regards,
Santhosh

Sir,
I would like to get my datbase Open automatically when the Machine where the database resides get restarted.
Now , What happens is that , I need to manually startup the database in the machine where database resides. I would like this to be automatic (i.e) the database should go up when the machine is restarted.
Kindly do provide me the solution for the same.
Regards,
Santhosh

Startup & shutdown database when reboot server

Dear Oracle guru
We have Digital Unix (True64) v.5.0, and Oracle v.81.5 on top, these days we need to manually startup and shutdown database when we need to maintain its server.
Wondering if you could suggest me for the startup and shutdown scripts to put at /sbin/rc*.d, so that when the server reboots, it will startup database automatically and vice versa for shutting down the server.
Would be very appreciated for your prompt help.

The instance is not going to start automatically when you reboot the server.
1.- Shutdown all instances with immediate, transactional or normal option.
2.- stop the listener services
3.- Stop all rest of Oracle services
4.- Reboot the server
5.- start the listener
6.- start the instance
7.- start all rest of Oracle services
Joel Pérez

Oracle automatic startup

Hi,
I have Oracle 10g installed on Windows 2000 SP4. Oracle automatically starts up... is there any way to change this so that I can manually startup Oracle every time?
Thanks
Mark

In Configuration Panel\Administration Tools\Services windows, Configure the service OracleService<SID> as manually.
Nicolas.

Oracle startup guidence reqd

I am running Oracle 11g on 64 Windows platform.
1 . I shutdown the database with the shutdown immediate. And i hadn't stopped the Oracle services .
2. Then is stopped server.
3. When I restarted the server , databases were up is tht due to not stopping Oracle services. I want to conform it.

to change the service stop/start and automatic/manual startup of services, follow the steps
1. Logon to Windows with Administrator rights.
2 Click Start > Control Panel.
3 Double-click Administrative Tools.
4 Double-click the Services icon.
5 Double-click the service that you want to stop or start.
6 When the Service Properties window appears, do one of the following:
* If the service is running, click Stop the service.
* If the service is not running, click Start the service.
Change the startup type which includes Automatic, Manual and Disabled:
* Automatic starts the services at system logon,
* Manual starts a service as required or when called from an application (according to definition, but only some of the time in practice, depending on the service),
* Disabled completely disables the service and prevents it and its dependencies from running.
7 Click OK.

Manual Startup of CMS

Similar Messages

Maybe you are looking for