Database Service Fail

I have installed Oracle 8i personal ediation on windows XP Professional.. after the installatoin, oracle successfully gets connected to the database. But when I restart the system , the oracle database servie fails to start . I have tried it many times on XP Professional.
What is the reason....Send me the solution,,,,

Hi jj_the_Skeptic,
in my opinion, there was a performance issue, so perhaps by taking the memory dump, it will help a lot to debug the process, to know why from the web02 become unresponsive.
my colleague said that, if there is alot of users that access the database in the same time, there may issue also here, because access database is not that powerful as sql, that will turn out slow process-time out-failed process
if you need the services at the web server, then you may try to create a webserver+application server together as your testing environment.
if you need direct assistance to capture the memory dump and analysis, please open a ticket to
http://support.microsoft.com.
Regards,
Aries
Microsoft Online Community Support
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

Similar Messages

  • Database Services Engine Failed, SQL Server Replication Failed, Full Text Search Failed, Reporting Services Failed

    Hello,
    I am trying to install Microsoft SQL Server 2008 R2. I get the error bellow (Database Services Engine Failed, SQL Server Replication Failed, Full Text Search Failed, Reporting Services Failed). I already have a copy of SQL Server 2008 R2 on the machine.
    I want to create a new named instance of SQL Server for some software I'm installing.
    The error is below.
    Any help would be much appreciated, thanks!
    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):           -595541211
      Exit facility code:            1152
      Exit error code:               49957
      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-02-06 09:14:09
      End time:                      2014-02-06 11:18:16
      Requested action:              Install
      Log with failure:              C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20140206_091302\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.50.2500.0%26EvtType%3d0x44D4F75E%400xDC80C325
    Machine Properties:
      Machine name:                  BAHPBZ52TY
      Machine processor count:       4
      OS version:                    Windows 7
      OS service pack:               Service Pack 1
      OS region:                     United States
      OS language:                   English (United States)
      OS architecture:               x64
      Process architecture:          64 Bit
      OS clustered:                  No
    Product features discovered:
      Product              Instance             Instance ID                   
    Feature                                  Language            
    Edition              Version         Clustered
      Sql Server 2008 R2   SQLEXPRESS           MSSQL10_50.SQLEXPRESS          Database Engine Services                
    1033                 Express Edition      10.50.1600.1    No        
      Sql Server 2008 R2                                                      
    Management Tools - Basic                 1033                 Express Edition     
    10.50.1600.1    No        
    Package properties:
      Description:                   SQL Server Database Services 2008 R2
      ProductName:                   SQL Server 2008 R2
      Type:                          RTM
      Version:                       10
      Installation location:         c:\c7ced2c86d6b9813b28186cc831c2054\x64\setup\
      Installation edition:          EXPRESS_ADVANCED
      Slipstream:                    True
      SP Level                       1
    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:             
      CUSOURCE:                      
      ENABLERANU:                    True
      ENU:                           True
      ERRORREPORTING:                False
      FARMACCOUNT:                   <empty>
      FARMADMINPORT:                 0
      FARMPASSWORD:                  *****
      FEATURES:                      SQLENGINE,REPLICATION,FULLTEXT,RS,SSMS,SNAC_SDK,OCS
      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:                   C:\Program Files\Microsoft SQL Server\
      INSTANCEID:                    aedt2bSQL
      INSTANCENAME:                  AEDT2BSQL
      ISSVCACCOUNT:                  NT AUTHORITY\NetworkService
      ISSVCPASSWORD:                 *****
      ISSVCSTARTUPTYPE:              Automatic
      NPENABLED:                     0
      PASSPHRASE:                    *****
      PCUSOURCE:                     c:\c7ced2c86d6b9813b28186cc831c2054\PCUSOURCE
      PID:                           *****
      QUIET:                         False
      QUIETSIMPLE:                   False
      ROLE:                          AllFeatures_WithDefaults
      RSINSTALLMODE:                 DefaultNativeMode
      RSSVCACCOUNT:                  NT AUTHORITY\NETWORK SERVICE
      RSSVCPASSWORD:                 *****
      RSSVCSTARTUPTYPE:              Automatic
      SAPWD:                         *****
      SECURITYMODE:                  SQL
      SQLBACKUPDIR:                  <empty>
      SQLCOLLATION:                  SQL_Latin1_General_CP1_CI_AS
      SQLSVCACCOUNT:                 NT AUTHORITY\NETWORK SERVICE
      SQLSVCPASSWORD:                *****
      SQLSVCSTARTUPTYPE:             Automatic
      SQLSYSADMINACCOUNTS:           BAH\568385
      SQLTEMPDBDIR:                  <empty>
      SQLTEMPDBLOGDIR:               <empty>
      SQLUSERDBDIR:                  <empty>
      SQLUSERDBLOGDIR:               <empty>
      SQMREPORTING:                  False
      TCPENABLED:                    0
      UIMODE:                        AutoAdvance
      X86:                           False
      Configuration file:            C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20140206_091302\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:      0xDC80C325
      Configuration error description: Access is denied
      Configuration log:             C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20140206_091302\Detail.txt
      Feature:                       SQL Client Connectivity SDK
      Status:                        Passed
      MSI status:                    Passed
      Configuration status:          Passed
      Feature:                       SQL Server Replication
      Status:                        Failed: see logs for details
      MSI status:                    Passed
      Configuration status:          Failed: see details below
      Configuration error code:      0xDC80C325
      Configuration error description: Access is denied
      Configuration log:             C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20140206_091302\Detail.txt
      Feature:                       Full-Text Search
      Status:                        Failed: see logs for details
      MSI status:                    Passed
      Configuration status:          Failed: see details below
      Configuration error code:      0xDC80C325
      Configuration error description: Access is denied
      Configuration log:             C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20140206_091302\Detail.txt
      Feature:                       Reporting Services
      Status:                        Failed: see logs for details
      MSI status:                    Passed
      Configuration status:          Failed: see details below
      Configuration error code:      0xDC80C325
      Configuration error description: Access is denied
      Configuration log:             C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20140206_091302\Detail.txt
      Feature:                       Management Tools - Basic
      Status:                        Passed
      MSI status:                    Passed
      Configuration status:          Passed
      Feature:                       Microsoft Sync Framework
      Status:                        Passed
      MSI status:                    Passed
      Configuration status:          Passed
    Rules with failures:
    Global rules:
    Scenario specific rules:
    Rules report file:               C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20140206_091302\SystemConfigurationCheck_Report.htm

    Hello,
    If you see error descriptioon it gives access denied so basically it is because of some access issue.I guess You must be using some domin account for installation make sure it is  added as local administrator also instead of using NT Authority network
    service  as SQL server service account use local system account .
    Below link would help
    http://serverfault.com/questions/212135/access-is-denied-error-installing-sql-server-2008-on-windows-7
    You can also browse to setup.exe file and RK on it and select run as administrator
    Please mark this reply as the answer or vote as helpful, as appropriate, to make it useful for other readers

  • Cannot Install Sql Server 2008, Gives The Error "Database Engine Services Failed"

    I cannot install Sql Server 2008 R2 on Windows 8. Tried many times but failed because it gives the error "Database
    Engine Services Failed". Sql files cannot be corrupted because i can install the same setup on Windows 7 and i can connect to databases.
    I tried all the things below;
    * I'm uninstalling everything related with Sql Server from Control Panel/Programs And Features.
    * I'm deleting all the keys related with Sql Server from Regedit.
    * Later i'm restarting windows, and trying to install again. But during the install it gives the error "Database
    Engine Services Failed", install is finishing but when i opened the Management Studio i cannot connect to Database Engine with Sa naturally.
    * My firewall is already closed. And i have not any antivirus software.
    * I gave the permission for port 1433 on firewall.
    Please help me. Why i always take "Database Engine Services Failed" error? I will get crazy cause of that for many days.

    Here's the ERRORLOG file which i found under the folder;
    Microsoft SQL Server/MSSQL10_50.MSSQLSERVER/MSSQL/Log.
    2014-09-27 03:39:40.15 Server      Microsoft SQL Server 2008 R2 (RTM) - 10.50.1600.1 (X64) 
    Apr  2 2010 15:48:46 
    Copyright (c) Microsoft Corporation
    Developer Edition (64-bit) on Windows NT 6.2 <X64> (Build 9200: )
    2014-09-27 03:39:40.15 Server      (c) Microsoft Corporation.
    2014-09-27 03:39:40.15 Server      All rights reserved.
    2014-09-27 03:39:40.15 Server      Server process ID is 5768.
    2014-09-27 03:39:40.15 Server      System Manufacturer: 'SAMSUNG ELECTRONICS CO., LTD.', System Model: '350V5C/350V5X/350V4C/350V4X/351V5C/351V5X/351V4C/351V4X/3540VC/3540VX/3440VC/3440VX'.
    2014-09-27 03:39:40.15 Server      Authentication mode is MIXED.
    2014-09-27 03:39:40.15 Server      Logging SQL Server messages in file 'C:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\Log\ERRORLOG'.
    2014-09-27 03:39:40.15 Server      Registry startup parameters: 
    -d C:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\DATA\master.mdf
    -e C:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\Log\ERRORLOG
    -l C:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\DATA\mastlog.ldf
    2014-09-27 03:39:40.15 Server      Command Line Startup Parameters:
    -m SqlSetup
    -f
    -Q
    -q Turkish_CI_AS
    -T 4022
    -T 4010
    -T 3659
    -T 3610
    2014-09-27 03:39:40.18 Server      Warning: The server instance was started using minimal configuration startup option (-f). Starting an instance of SQL Server with minimal configuration places the server in single-user mode automatically.  After
    the server has been started with minimal configuration, you should change the appropriate server option value or values, stop, and then restart the server.
    2014-09-27 03:39:40.18 Server      SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
    2014-09-27 03:39:40.18 Server      Detected 4 CPUs. This is an informational message; no user action is required.
    2014-09-27 03:39:40.31 Server      Perfmon counters for resource governor pools and groups failed to initialize and are disabled.
    2014-09-27 03:39:40.32 Server      Using dynamic lock allocation.  Initial allocation of 2500 Lock blocks and 5000 Lock Owner blocks per node.  This is an informational message only.  No user action is required.
    2014-09-27 03:39:40.43 Server      Node configuration: node 0: CPU mask: 0x000000000000000f:0 Active CPU mask: 0x000000000000000f:0. This message provides a description of the NUMA configuration for this computer. This is an informational message
    only. No user action is required.
    2014-09-27 03:39:40.45 Server      Support for distributed transactions was not enabled for this instance of the Database Engine because it was started using the minimal configuration option. This is an informational message only. No user action
    is required.
    2014-09-27 03:39:40.45 spid7s      Warning ******************
    2014-09-27 03:39:40.45 spid7s      SQL Server started in single-user mode. This an informational message only. No user action is required.
    2014-09-27 03:39:40.46 spid7s      Starting up database 'master'.
    2014-09-27 03:39:40.52 spid7s      Recovery is writing a checkpoint in database 'master' (1). This is an informational message only. No user action is required.
    2014-09-27 03:39:40.58 spid7s      SQL Server was started using the -f flag. SQL Server Audit is disabled. This is an informational message. No user action is required.
    2014-09-27 03:39:40.59 spid7s      FILESTREAM: effective level = 0, configured level = 0, file system access share name = 'MSSQLSERVER'.
    2014-09-27 03:39:40.59 spid7s      Server started with '-f' option. Auditing will not be started. This is an informational message only; no user action is required.
    2014-09-27 03:39:40.59 spid7s      Starting up database 'mssqlsystemresource'.
    2014-09-27 03:39:40.61 spid7s      The resource database build version is 10.50.1600. This is an informational message only. No user action is required.
    2014-09-27 03:39:40.94 spid7s      Password policy update was successful.
    2014-09-27 03:39:40.94 spid8s      Starting up database 'model'.
    2014-09-27 03:39:40.95 spid7s      Server name is 'CAGATAY'. This is an informational message only. No user action is required.
    2014-09-27 03:39:41.21 spid8s      Clearing tempdb database.
    2014-09-27 03:39:41.21 spid10s     A new instance of the full-text filter daemon host process has been successfully started.
    2014-09-27 03:39:41.24 Server      A self-generated certificate was successfully loaded for encryption.
    2014-09-27 03:39:41.24 Server      Server local connection provider is ready to accept connection on [ \\.\pipe\SQLLocal\MSSQLSERVER ].
    2014-09-27 03:39:41.24 Server      Dedicated administrator connection support was not started because it is disabled on this edition of SQL Server. If you want to use a dedicated administrator connection, restart SQL Server using the trace flag
    7806. This is an informational message only. No user action is required.
    2014-09-27 03:39:41.28 Server      The SQL Server Network Interface library could not register the Service Principal Name (SPN) for the SQL Server service. Error: 0x54b, state: 3. Failure to register an SPN may cause integrated authentication
    to fall back to NTLM instead of Kerberos. This is an informational message. Further action is only required if Kerberos authentication is required by authentication policies.
    2014-09-27 03:39:41.28 Server      SQL Server is now ready for client connections. This is an informational message; no user action is required.
    2014-09-27 03:39:41.70 spid8s      Starting up database 'tempdb'.
    2014-09-27 03:39:41.86 spid7s      Warning ******************
    2014-09-27 03:39:41.86 spid7s      Attempting to change default collation to Turkish_CI_AS.
    2014-09-27 03:39:41.92 spid7s       index restored for master.syspriorities.
    2014-09-27 03:39:41.95 spid7s       index restored for master.sysbrickfiles.
    2014-09-27 03:39:41.96 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:41.96 spid7s       index restored for master.sysowners.
    2014-09-27 03:39:42.13 spid7s       index restored for master.sysdbreg.
    2014-09-27 03:39:42.16 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:42.16 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:42.16 spid7s       index restored for master.sysschobjs.
    2014-09-27 03:39:42.17 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:42.17 spid7s       index restored for master.syscolpars.
    2014-09-27 03:39:42.17 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:42.18 spid7s       index restored for master.sysxlgns.
    2014-09-27 03:39:42.18 spid7s       index restored for master.sysxsrvs.
    2014-09-27 03:39:42.18 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:42.18 spid7s       index restored for master.sysnsobjs.
    2014-09-27 03:39:42.18 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:42.18 spid7s       index restored for master.syscerts.
    2014-09-27 03:39:42.19 spid7s       index restored for master.sysrmtlgns.
    2014-09-27 03:39:42.19 spid7s       index restored for master.sysxprops.
    2014-09-27 03:39:42.19 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:42.19 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:42.31 spid7s       index restored for master.sysscalartypes.
    2014-09-27 03:39:42.31 spid7s       index restored for master.sysidxstats.
    2014-09-27 03:39:42.31 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:42.32 spid7s       index restored for master.sysendpts.
    2014-09-27 03:39:42.32 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:42.32 spid7s       index restored for master.sysclsobjs.
    2014-09-27 03:39:42.32 spid7s       index restored for master.sysremsvcbinds.
    2014-09-27 03:39:42.32 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:42.32 spid7s       index restored for master.sysrts.
    2014-09-27 03:39:42.33 spid7s       index restored for master.sysasymkeys.
    2014-09-27 03:39:42.33 spid7s       index restored for master.syssqlguides.
    2014-09-27 03:39:42.44 spid7s       index restored for master.syssoftobjrefs.
    2014-09-27 03:39:42.47 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:42.48 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:42.49 spid7s       index restored for master.spt_values.
    2014-09-27 03:39:42.49 spid7s       index restored for master.MSreplication_options.
    2014-09-27 03:39:42.56 spid7s       index restored for tempdb.syspriorities.
    2014-09-27 03:39:42.56 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:42.57 spid7s       index restored for tempdb.sysowners.
    2014-09-27 03:39:42.57 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:42.57 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:42.57 spid7s       index restored for tempdb.sysschobjs.
    2014-09-27 03:39:42.57 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:42.59 spid7s       index restored for tempdb.syscolpars.
    2014-09-27 03:39:42.60 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:42.60 spid7s       index restored for tempdb.sysnsobjs.
    2014-09-27 03:39:42.60 spid7s       index restored for tempdb.syscerts.
    2014-09-27 03:39:42.60 spid7s       index restored for tempdb.sysxprops.
    2014-09-27 03:39:42.60 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:42.60 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:42.60 spid7s       index restored for tempdb.sysscalartypes.
    2014-09-27 03:39:42.61 spid7s       index restored for tempdb.sysidxstats.
    2014-09-27 03:39:42.61 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:42.61 spid7s       index restored for tempdb.sysclsobjs.
    2014-09-27 03:39:42.61 spid7s       index restored for tempdb.sysremsvcbinds.
    2014-09-27 03:39:42.61 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:42.61 spid7s       index restored for tempdb.sysrts.
    2014-09-27 03:39:42.62 spid7s       index restored for tempdb.sysasymkeys.
    2014-09-27 03:39:42.69 spid7s       index restored for tempdb.syssqlguides.
    2014-09-27 03:39:42.69 spid7s       index restored for tempdb.syssoftobjrefs.
    2014-09-27 03:39:42.75 spid7s       index restored for model.syspriorities.
    2014-09-27 03:39:42.75 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:42.75 spid7s       index restored for model.sysowners.
    2014-09-27 03:39:42.76 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:42.76 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:42.76 spid7s       index restored for model.sysschobjs.
    2014-09-27 03:39:42.76 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:43.00 spid7s       index restored for model.syscolpars.
    2014-09-27 03:39:43.00 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:43.00 spid7s       index restored for model.sysnsobjs.
    2014-09-27 03:39:43.00 spid7s       index restored for model.syscerts.
    2014-09-27 03:39:43.00 spid7s       index restored for model.sysxprops.
    2014-09-27 03:39:43.00 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:43.00 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:43.00 spid7s       index restored for model.sysscalartypes.
    2014-09-27 03:39:43.00 spid7s       index restored for model.sysidxstats.
    2014-09-27 03:39:43.01 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:43.01 spid7s       index restored for model.sysclsobjs.
    2014-09-27 03:39:43.01 spid7s       index restored for model.sysremsvcbinds.
    2014-09-27 03:39:43.01 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:43.01 spid7s       index restored for model.sysrts.
    2014-09-27 03:39:43.01 spid7s       index restored for model.sysasymkeys.
    2014-09-27 03:39:43.01 spid7s       index restored for model.syssqlguides.
    2014-09-27 03:39:43.01 spid7s       index restored for model.syssoftobjrefs.
    2014-09-27 03:39:43.02 spid7s      Starting up database 'msdb'.
    2014-09-27 03:39:43.82 spid7s       index restored for msdb.syspriorities.
    2014-09-27 03:39:43.85 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:43.93 spid7s       index restored for msdb.sysowners.
    2014-09-27 03:39:43.99 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:44.00 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:44.09 spid7s       index restored for msdb.sysschobjs.
    2014-09-27 03:39:44.12 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:44.20 spid7s       index restored for msdb.syscolpars.
    2014-09-27 03:39:44.20 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:44.20 spid7s       index restored for msdb.sysnsobjs.
    2014-09-27 03:39:44.20 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:44.25 spid7s       index restored for msdb.syscerts.
    2014-09-27 03:39:44.25 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:44.26 spid7s       index restored for msdb.sysxprops.
    2014-09-27 03:39:44.26 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:44.26 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:44.27 spid7s       index restored for msdb.sysscalartypes.
    2014-09-27 03:39:44.37 spid7s       index restored for msdb.sysidxstats.
    2014-09-27 03:39:44.41 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:44.42 spid7s       index restored for msdb.sysclsobjs.
    2014-09-27 03:39:44.42 spid7s       index restored for msdb.sysremsvcbinds.
    2014-09-27 03:39:44.42 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:44.42 spid7s       index restored for msdb.sysrts.
    2014-09-27 03:39:44.54 spid7s       index restored for msdb.sysasymkeys.
    2014-09-27 03:39:44.54 spid7s       index restored for msdb.syssqlguides.
    2014-09-27 03:39:44.59 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:44.74 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:44.85 spid7s       index restored for msdb.syssoftobjrefs.
    2014-09-27 03:39:44.89 spid7s       index restored for msdb.syspolicy_policies_internal.
    2014-09-27 03:39:44.90 spid7s       index restored for msdb.sysproxies.
    2014-09-27 03:39:44.90 spid7s       index restored for msdb.syscollector_execution_stats_internal.
    2014-09-27 03:39:44.90 spid7s       index restored for msdb.syssubsystems.
    2014-09-27 03:39:44.91 spid7s       index restored for msdb.log_shipping_primary_secondaries.
    2014-09-27 03:39:44.91 spid7s       index restored for msdb.sysdownloadlist.
    2014-09-27 03:39:44.91 spid7s       index restored for msdb.log_shipping_monitor_primary.
    2014-09-27 03:39:44.92 spid7s       index restored for msdb.sysoriginatingservers.
    2014-09-27 03:39:44.93 spid7s       index restored for msdb.log_shipping_monitor_history_detail.
    2014-09-27 03:39:44.95 spid7s       index restored for msdb.log_shipping_monitor_error_detail.
    2014-09-27 03:39:44.95 spid7s       index restored for msdb.log_shipping_secondary.
    2014-09-27 03:39:44.97 spid7s       index restored for msdb.log_shipping_secondary_databases.
    2014-09-27 03:39:45.10 spid7s       index restored for msdb.log_shipping_monitor_secondary.
    2014-09-27 03:39:45.10 spid7s       index restored for msdb.sysjobs.
    2014-09-27 03:39:45.10 spid7s       index restored for msdb.sysutility_ucp_mi_file_space_health_internal.
    2014-09-27 03:39:45.10 spid7s       index restored for msdb.sysutility_ucp_mi_database_health_internal.
    2014-09-27 03:39:45.10 spid7s       index restored for msdb.syscollector_blobs_internal.
    2014-09-27 03:39:45.11 spid7s       index restored for msdb.sysutility_mi_dac_execution_statistics_internal.
    2014-09-27 03:39:45.11 spid7s       index restored for msdb.sysjobsteps.
    2014-09-27 03:39:45.11 spid7s       index restored for msdb.sysutility_ucp_dac_file_space_health_internal.
    2014-09-27 03:39:45.11 spid7s       index restored for msdb.logmarkhistory.
    2014-09-27 03:39:45.11 spid7s       index restored for msdb.sysutility_mi_session_statistics_internal.
    2014-09-27 03:39:45.12 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:45.12 spid7s       index restored for msdb.sysdtscategories.
    2014-09-27 03:39:45.33 spid7s       index restored for msdb.syspolicy_target_sets_internal.
    2014-09-27 03:39:45.33 spid7s       index restored for msdb.sysutility_ucp_mi_volume_space_health_internal.
    2014-09-27 03:39:45.33 spid7s       index restored for msdb.sysschedules.
    2014-09-27 03:39:45.33 spid7s       index restored for msdb.sysdac_instances_internal.
    2014-09-27 03:39:45.33 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:45.50 spid7s       index restored for msdb.sysssispackages.
    2014-09-27 03:39:45.51 spid7s       index restored for msdb.sysutility_ucp_computer_cpu_health_internal.
    2014-09-27 03:39:45.51 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:45.52 spid7s       index restored for msdb.sysssispackagefolders.
    2014-09-27 03:39:45.52 spid7s       index restored for msdb.sysdac_history_internal.
    2014-09-27 03:39:45.53 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:45.62 spid7s       index restored for msdb.syscategories.
    2014-09-27 03:39:45.62 spid7s       index restored for msdb.systargetservers.
    2014-09-27 03:39:45.62 spid7s       index restored for msdb.systargetservergroups.
    2014-09-27 03:39:45.62 spid7s       index restored for msdb.syspolicy_policy_category_subscriptions_internal.
    2014-09-27 03:39:45.62 spid7s       index restored for msdb.sysalerts.
    2014-09-27 03:39:45.62 spid7s       index restored for msdb.sysoperators.
    2014-09-27 03:39:45.63 spid7s       index restored for msdb.syspolicy_system_health_state_internal.
    2014-09-27 03:39:45.63 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:45.63 spid7s       index restored for msdb.syscollector_config_store_internal.
    2014-09-27 03:39:45.65 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:45.65 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:45.65 spid7s       index restored for msdb.sysmanagement_shared_server_groups_internal.
    2014-09-27 03:39:45.66 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:45.66 spid7s       index restored for msdb.sysutility_mi_smo_properties_to_collect_internal.
    2014-09-27 03:39:45.66 spid7s       index restored for msdb.sysmanagement_shared_registered_servers_internal.
    2014-09-27 03:39:45.66 spid7s       index restored for msdb.syscachedcredentials.
    2014-09-27 03:39:45.79 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:45.79 spid7s       index restored for msdb.syscollector_collection_sets_internal.
    2014-09-27 03:39:45.79 spid7s       index restored for msdb.sysutility_ucp_dac_health_internal.
    2014-09-27 03:39:45.80 spid7s       index restored for msdb.MSdbms.
    2014-09-27 03:39:45.80 spid7s       index restored for msdb.MSdbms_datatype.
    2014-09-27 03:39:45.80 spid7s       index restored for msdb.sysmail_profile.
    2014-09-27 03:39:45.80 spid7s       index restored for msdb.sysutility_ucp_managed_instances_internal.
    2014-09-27 03:39:45.83 spid7s       index restored for msdb.syspolicy_management_facets.
    2014-09-27 03:39:45.84 spid7s       index restored for msdb.sysutility_ucp_mi_health_internal.
    2014-09-27 03:39:45.86 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:45.86 spid7s       index restored for msdb.syscollector_collector_types_internal.
    2014-09-27 03:39:45.86 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:45.86 spid7s       index restored for msdb.syspolicy_configuration_internal.
    2014-09-27 03:39:45.87 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:45.87 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:45.87 spid7s       index restored for msdb.syspolicy_facet_events.
    2014-09-27 03:39:45.87 spid7s       index restored for msdb.sysmail_account.
    2014-09-27 03:39:45.87 spid7s       index restored for msdb.syspolicy_conditions_internal.
    2014-09-27 03:39:45.88 spid7s       index restored for msdb.sysutility_ucp_health_policies_internal.
    2014-09-27 03:39:45.88 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:45.88 spid7s       index restored for msdb.syscollector_collection_items_internal.
    2014-09-27 03:39:45.90 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:46.00 spid7s       index restored for msdb.sysmail_servertype.
    2014-09-27 03:39:46.00 spid7s       index restored for msdb.sysutility_ucp_filegroups_with_policy_violations_internal.
    2014-09-27 03:39:46.02 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:46.03 spid7s       index restored for msdb.sysutility_ucp_policy_check_conditions_internal.
    2014-09-27 03:39:46.03 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:46.03 spid7s       index restored for msdb.sysutility_ucp_configuration_internal.
    2014-09-27 03:39:46.03 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:46.03 spid7s       index restored for msdb.sysutility_ucp_policy_target_conditions_internal.
    2014-09-27 03:39:46.04 spid7s       index restored for msdb.sysmail_server.
    2014-09-27 03:39:46.04 spid7s       index restored for msdb.syspolicy_policy_categories_internal.
    2014-09-27 03:39:46.04 spid7s       index restored for msdb.syspolicy_object_sets_internal.
    2014-09-27 03:39:46.04 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:46.05 spid7s       index restored for msdb.sysmail_configuration.
    2014-09-27 03:39:46.05 spid7s       index restored for msdb.sysdbmaintplan_databases.
    2014-09-27 03:39:46.05 spid7s       index restored for msdb.log_shipping_primary_databases.
    2014-09-27 03:39:46.39 spid7s      The default collation was successfully changed.
    2014-09-27 03:39:46.39 spid7s      Recovery is complete. This is an informational message only. No user action is required.
    2014-09-27 03:39:47.17 spid51      Changed database context to 'master'.
    2014-09-27 03:39:47.18 spid51      Changed language setting to us_english.
    2014-09-27 03:39:47.72 spid51      Setting database option RECOVERY to FULL for database model.
    2014-09-27 03:39:47.84 spid51      Configuration option 'show advanced options' changed from 0 to 1. Run the RECONFIGURE statement to install.
    2014-09-27 03:39:47.84 spid51      FILESTREAM: effective level = 0, configured level = 0, file system access share name = 'MSSQLSERVER'.
    2014-09-27 03:39:47.98 spid51      Configuration option 'default language' changed from 0 to 0. Run the RECONFIGURE statement to install.
    2014-09-27 03:39:47.98 spid51      Configuration option 'default full-text language' changed from 1033 to 1033. Run the RECONFIGURE statement to install.
    2014-09-27 03:39:47.98 spid51      FILESTREAM: effective level = 0, configured level = 0, file system access share name = 'MSSQLSERVER'.
    2014-09-27 03:39:47.98 spid51      Configuration option 'show advanced options' changed from 1 to 0. Run the RECONFIGURE statement to install.
    2014-09-27 03:39:47.98 spid51      FILESTREAM: effective level = 0, configured level = 0, file system access share name = 'MSSQLSERVER'.
    2014-09-27 03:39:48.27 spid51      Error: 15007, Severity: 16, State: 1.
    2014-09-27 03:39:48.27 spid51      '' is not a valid login or you do not have permission.
    2014-09-27 03:51:25.13 Logon       Error: 18456, Severity: 14, State: 8.
    2014-09-27 03:51:25.13 Logon       Login failed for user 'sa'. Reason: Password did not match that for the login provided. [CLIENT: <local machine>]
    2014-09-27 03:51:32.67 Logon       Error: 18456, Severity: 14, State: 8.
    2014-09-27 03:51:32.67 Logon       Login failed for user 'sa'. Reason: Password did not match that for the login provided. [CLIENT: <local machine>]
    2014-09-27 03:51:42.11 Logon       Error: 18456, Severity: 14, State: 5.
    2014-09-27 03:51:42.11 Logon       Login failed for user 'CAGATAY\cagatay (cagatay)'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
    2014-09-27 03:52:42.07 Logon       Error: 18456, Severity: 14, State: 5.
    2014-09-27 03:52:42.07 Logon       Login failed for user 'CAGATAY\cagatay (cagatay)'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
    2014-09-27 03:53:01.23 Logon       Error: 18461, Severity: 14, State: 1.
    2014-09-27 03:53:01.23 Logon       Login failed for user 'CAGATAY\cagatay'. Reason: Server is in single user mode. Only one administrator can connect at this time. [CLIENT: <local machine>]
    2014-09-27 03:53:17.57 Logon       Error: 18456, Severity: 14, State: 8.
    2014-09-27 03:53:17.57 Logon       Login failed for user 'sa'. Reason: Password did not match that for the login provided. [CLIENT: <local machine>]
    2014-09-27 03:53:32.54 Logon       Error: 18456, Severity: 14, State: 5.
    2014-09-27 03:53:32.54 Logon       Login failed for user 'CAGATAY\cagatay (cagatay)'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
    2014-09-27 03:54:04.29 Logon       Error: 18456, Severity: 14, State: 5.
    2014-09-27 03:54:04.29 Logon       Login failed for user 'CAGATAY\cagatay (cagatay)'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
    2014-09-27 03:54:10.36 Logon       Error: 18456, Severity: 14, State: 5.
    2014-09-27 03:54:10.36 Logon       Login failed for user 'CAGATAY\cagatay'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
    2014-09-27 03:54:47.18 Logon       Error: 18456, Severity: 14, State: 8.
    2014-09-27 03:54:47.18 Logon       Login failed for user 'sa'. Reason: Password did not match that for the login provided. [CLIENT: <local machine>]
    Resolve the error, please refer to the following links.
    Enable DAC:http://www.mssqltips.com/sqlservertip/2538/enabling-dedicated-administrator-connection-in-sql-server-2008-express-edition/
    could not register the SPN Kerberos:
    http://saveadba.blogspot.com/2012/03/could-not-register-spn-kerberos.html  
    Make sure the password of sa is correct,and the login 'CAGATAY\cagatay' has been created in SQL Server

  • Net8 database service test failed

    Can someone suggest what Am I doing wrong?
    I need to configure the ODBC to work with an application and the first step (according to my reading) is to configure the Net8 Database Services. Well, every time I test the service I have created it give me this error: ORA-12560:TNS:Protocol adapter error. I have check my listener. It has 3 addresses on it and one of them is exacly the same protocol and key from the service that I am trying. Both my database service and the application are on the same machine. So the protocol I am using is IPC (local database) with the key= ORCL. My database have no domain so the global_name is only, ORACLE. Could that be creating any problem?
    Please, I really need help.
    Thanks,
    cip

    Thanks akhil for replying. The application that I am trying to connect to is FrontPage. And yes I can work on my sql*plus shell with no problem. If the database is up and running the Listener is too? Should I use TCP/IP even though I don't need to connect any where because my database is local? My Oracle and software application are on the same machine. which host should I use if I don't need to coneect out of my machine?
    Now that I tried with the TCP/IP I got the error ora 12541: TNS:no listener. What now? I even started the listener with the lstnctr utility.
    I certainly appreciate any suggestions.
    Thanks,
    Carmen
    null

  • Creating new Data Source Error - Database connection Failed

    Successfully installed and configured 11.1.1.3.0. Planning and Essbase dev.
    Went to Workspace > Administer > Classing Planning Administration > Manage Data Sources > Create Data Source.
    Entered all info about the application database , etc. Getting error "The database connection failed" (I was able to connect with no problem during the install)
    SQL server 2005 is on the same physical server.
    The diagnostic tool shows database connection passed for planning. A new database was created for the new application.
    The server event viewer shows these errors.
    "Login failed for user 'xxx-hyperion'. The user is not associated with a trusted SQL Server connection."
    Group Policy Error "The client-side extension could not apply computer policy settings for 'Default Domain Policy {xxx}' because it failed with error code '0x80070003 The system cannot find the path specified.' See trace file for more details. "
    The Group Policy client-side extension Group Policy Services failed to execute. Please look for any errors reported earlier by that extension.
    Any help is appreciated.

    Datasource for the application.
    I have created a sql db for this planning application (my datasource). See my first message for more details.
    When you create a new planning application, you need to associate it with a data source. Since this is a new install, I don't have any data sources available yet.
    So, "To create, edit or delete data sources, click Manage Data Source."
    This page lets you validate your connection to the database and essbase server. My essbase server connection validates! The database connection does not validate after I enter all the relevant information.
    SCREEN INFO BELOW
    Fields displayed with an asterisk (*) are mandatory.
    Data Source Name *:
    Data Source Description:
    Select Database Platform
    Microsoft SQL Server
    Application Database
    Server * :
    Port * :
    Database *:
    User *:
    Password *:
    Click "Validate Database Connection"
    ERROR ---> Database connection failed.
    So it does not let me create a data source for my new planning application, so I cannot create a new planning application.
    Thanks in advance.

  • Com.sap.security.core.ume.service failed. J2EE Engine cannot be started

    Hi,
    I have configured SNC on NetWeaver 7.0 (ABAP+JAVA) System on Windows 2003 Server with MS-SQL 2005 Database.
    After the SNC configuration restarted the Server but the JAVA Server process is going down with EXIT Code -11113. The SNC Configuration is working fine but JAVA is not running. SDM and dispatcher are in green but server process is going gray.
    I have checked the log files under C:\usr\sap\SID\DVEBMGS00\j2ee\cluster\server0\log
    The following is the part of log file.
    #1.5#005056BA6C3F001D0000000F000008D8000489ACAFC86070#1277274683393#com.sap.engine.core.service630.container.ServiceRunner##com.sap.engine.core.service630.container.ServiceRunner#######SAPEngine_System_Thread[impl:5]_71##0#0#Error#1#/System/Server#Java###Core service com.sap.security.core.ume.service failed. J2EE Engine cannot be started.
    [EXCEPTION]
    #1#com.sap.engine.frame.ServiceException: <Localization failed: ResourceBundle='com.sap.engine.frame.KernelResourceBundle', ID='UME initialization failed.', Arguments: []> : Can't find resource for bundle java.util.PropertyResourceBundle, key UME initialization failed.
         at com.sap.security.core.server.ume.service.UMEServiceFrame.start(UMEServiceFrame.java:372)
         at com.sap.engine.frame.ApplicationFrameAdaptor.start(ApplicationFrameAdaptor.java:31)
         at com.sap.engine.core.service630.container.ServiceRunner.startApplicationServiceFrame(ServiceRunner.java:214)
         at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:144)
         at com.sap.engine.frame.core.thread.Task.run(Task.java:64)
         at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:79)
         at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:105)
    Caused by: com.sap.security.core.persistence.datasource.PersistenceException: SNC required for this connection
         at com.sap.security.core.persistence.datasource.imp.R3PersistenceBase.newPersistenceException(R3PersistenceBase.java:178)
         at com.sap.security.core.persistence.datasource.imp.R3PersistenceBase.init(R3PersistenceBase.java:446)
         at com.sap.security.core.persistence.imp.PrincipalDatabagFactoryInstance.<init>(PrincipalDatabagFactoryInstance.java:356)
         at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.newInstance(PrincipalDatabagFactory.java:156)
         at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.getInstance(PrincipalDatabagFactory.java:109)
         at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.getInstance(PrincipalDatabagFactory.java:56)
         at com.sap.security.core.InternalUMFactory.initializeUME(InternalUMFactory.java:266)
         at com.sap.security.core.server.ume.service.UMEServiceFrame.start(UMEServiceFrame.java:279)
         ... 6 more
    #1.5#005056BA6C3F001D00000011000008D8000489ACAFC8628E#1277274683393#com.sap.engine.core.Framework##com.sap.engine.core.Framework#######SAPEngine_System_Thread[impl:5]_71##0#0#Fatal#1#/System/Server#Plain###Critical shutdown was invoked. Reason is: Core service com.sap.security.core.ume.service failed. J2EE Engine cannot be started.#
    Please help me to solve the issue.
    Thanks,
    Ajay.

    Hi Tim,
    I have configured using Kerberos library for 32 bit on Net Weaver 7.0 with MS SQL 2005 Server on Windows 2003 Server. I didnt change any thing on JAVA side. I have configured as per the Kerberos configuration steps  as per below URL
    http://help.sap.com/saphelp_nw70ehp2/helpdata/en/44/0ebf6c9b2b0d1ae10000000a114a6b/frameset.htm
    The configuration was successful and I am able to login with out asking password, but After the configuration when I have restarted every thing on ABAP side works well but JAVA server process going down with EXIT code -11113. One of the log file contains follows error message.
    com.sap.engine.frame.ServiceException: <Localization failed: ResourceBundle='com.sap.engine.frame.KernelResourceBundle', ID='UME initialization failed.', Arguments: []> : Can't find resource for bundle java.util.PropertyResourceBundle, key UME initialization failed.
         at com.sap.security.core.server.ume.service.UMEServiceFrame.start(UMEServiceFrame.java:372)
         at com.sap.engine.frame.ApplicationFrameAdaptor.start(ApplicationFrameAdaptor.java:31)
         at com.sap.engine.core.service630.container.ServiceRunner.startApplicationServiceFrame(ServiceRunner.java:214)
         at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:144)
         at com.sap.engine.frame.core.thread.Task.run(Task.java:64)
         at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:79)
         at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:105)
    Caused by: com.sap.security.core.persistence.datasource.PersistenceException: SNC required for this connection
         at com.sap.security.core.persistence.datasource.imp.R3PersistenceBase.newPersistenceException(R3PersistenceBase.java:178)
         at com.sap.security.core.persistence.datasource.imp.R3PersistenceBase.init(R3PersistenceBase.java:446)
         at com.sap.security.core.persistence.imp.PrincipalDatabagFactoryInstance.<init>(PrincipalDatabagFactoryInstance.java:356)
         at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.newInstance(PrincipalDatabagFactory.java:156)
         at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.getInstance(PrincipalDatabagFactory.java:109)
         at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.getInstance(PrincipalDatabagFactory.java:56)
         at com.sap.security.core.InternalUMFactory.initializeUME(InternalUMFactory.java:266)
         at com.sap.security.core.server.ume.service.UMEServiceFrame.start(UMEServiceFrame.java:279)
         ... 6 more
    [Framework -> criticalShutdown] Core service com.sap.security.core.ume.service failed. J2EE Engine cannot be started.
    Jun 25, 2010 3:05:24 AM             com.sap.engine.core.Framework [SAPEngine_System_Thread[impl:5]_69] Fatal: Critical shutdown was invoked. Reason is: Core service com.sap.security.core.ume.service failed. J2EE Engine cannot be started.
    One of the line says "SNC required for this connection". What does this mean? What else need to be done for JAVA to communicate with ABAP?
    Thanks,
    Ajay.

  • 11gR2 Install Error, Listener is not up or database service is not registered with it

    Hi all,
    I'm currently studying towards my OCA, I've passed 1z0-051 (SQL Fundementals I), and now I'm moving onto 1z0-052 (Admin 1).
    Im really having trouble creating a database in Oracle 11g R2 Enterprise Edition. I install the software no problem. Then I create a database, and during the creation I have to createsa listener which uses TCP (default port:1521) and IPC. whilst creating the database I get the following error
    'Listener is not up or database service is not registered with it. Start the Listener and register database service and run EM configuration Assistant again.'
    Now, before you lynch me, I have searched this forum for answer to this for a day and a half. I've also tried google, i just can't find a answer that sorts out my problem. please assist me.
    I'm running on Windows 7 Professional (32bit) (I have previously tried on the 64 bit version with teh same results).
    Here's teh contents of my listener.ora file:
    # listener.ora Network Configuration File: C:\app\Damien\product\11.2.0\dbhome_1\network\admin\listener.ora
    # Generated by Oracle configuration tools.
    SID_LIST_LISTENER =
    (SID_LIST =
    (SID_DESC =
    (SID_NAME = CLRExtProc)
    (ORACLE_HOME = C:\app\Damien\product\11.2.0\dbhome_1)
    (PROGRAM = extproc)
    (ENVS = "EXTPROC_DLLS=ONLY:C:\app\Damien\product\11.2.0\dbhome_1\bin\oraclr11.dll")
    LISTENER =
    (DESCRIPTION_LIST =
    (DESCRIPTION =
    (ADDRESS = (PROTOCOL = IPC)(KEY = ipc))
    (ADDRESS = (PROTOCOL = TCP)(HOST = 192.168.10.4)(PORT = 1521))
    (ADDRESS = (PROTOCOL = IPC)(KEY = EXTPROC1521))
    ADR_BASE_LISTENER = C:\app\Damien
    Here's the contents of my tsnames.ora:
    # tnsnames.ora Network Configuration File: C:\app\Damien\product\11.2.0\dbhome_1\network\admin\tnsnames.ora
    # Generated by Oracle configuration tools.
    ORACLR_CONNECTION_DATA =
    (DESCRIPTION =
    (ADDRESS_LIST =
    (ADDRESS = (PROTOCOL = IPC)(KEY = EXTPROC1521))
    (CONNECT_DATA =
    (SID = CLRExtProc)
    (PRESENTATION = RO)
    Here is the last fe lines of my emConfig.log:
    Jan 18, 2014 9:38:22 AM oracle.sysman.emcp.util.GeneralUtil isLocalConnectionRequired
    CONFIG: isLocalConnectionRequired: true
    Jan 18, 2014 9:38:22 AM oracle.sysman.emcp.util.GeneralUtil initSQLEngine
    CONFIG: isLocalConnectionRequired: true. Connecting to database instance locally.
    Jan 18, 2014 9:38:22 AM oracle.sysman.emcp.util.GeneralUtil initSQLEngineLoacly
    CONFIG: SQLEngine connecting with SID: orcl, oracleHome: C:\app\Damien\product\11.2.0\dbhome_1, and user: SYSMAN
    Jan 18, 2014 9:38:22 AM oracle.sysman.emcp.util.GeneralUtil initSQLEngineLoacly
    CONFIG: SQLEngine created successfully and connected
    Jan 18, 2014 9:38:23 AM oracle.sysman.emcp.ParamsManager checkListenerStatusForDBControl
    CONFIG: ORA-12514: TNS:listener does not currently know of service requested in connect descriptor
    oracle.sysman.assistants.util.sqlEngine.SQLFatalErrorException: ORA-12514: TNS:listener does not currently know of service requested in connect descriptor
    at oracle.sysman.assistants.util.sqlEngine.SQLEngine.executeImpl(SQLEngine.java:1655)
    at oracle.sysman.assistants.util.sqlEngine.SQLEngine.executeSql(SQLEngine.java:1903)
    at oracle.sysman.emcp.ParamsManager.checkListenerStatusForDBControl(ParamsManager.java:3230)
    at oracle.sysman.emcp.EMReposConfig.unlockMGMTAccount(EMReposConfig.java:1001)
    at oracle.sysman.emcp.EMReposConfig.invoke(EMReposConfig.java:346)
    at oracle.sysman.emcp.EMReposConfig.invoke(EMReposConfig.java:158)
    at oracle.sysman.emcp.EMConfig.perform(EMConfig.java:253)
    at oracle.sysman.assistants.util.em.EMConfiguration.run(EMConfiguration.java:583)
    at oracle.sysman.assistants.dbca.backend.PostDBCreationStep.executeImpl(PostDBCreationStep.java:968)
    at oracle.sysman.assistants.util.step.BasicStep.execute(BasicStep.java:210)
    at oracle.sysman.assistants.util.step.Step.execute(Step.java:140)
    at oracle.sysman.assistants.util.step.StepContext$ModeRunner.run(StepContext.java:2667)
    at java.lang.Thread.run(Thread.java:595)
    Jan 18, 2014 9:38:23 AM oracle.sysman.emcp.EMConfig perform
    SEVERE: Listener is not up or database service is not registered with it. Start the Listener and register database service and run EM Configuration Assistant again .
    Refer to the log file at C:\app\Damien\cfgtoollogs\dbca\orcl\emConfig.log for more details.
    Jan 18, 2014 9:38:23 AM oracle.sysman.emcp.EMConfig perform
    CONFIG: Stack Trace:
    oracle.sysman.emcp.exception.EMConfigException: Listener is not up or database service is not registered with it. Start the Listener and register database service and run EM Configuration Assistant again .
    at oracle.sysman.emcp.ParamsManager.checkListenerStatusForDBControl(ParamsManager.java:3245)
    at oracle.sysman.emcp.EMReposConfig.unlockMGMTAccount(EMReposConfig.java:1001)
    at oracle.sysman.emcp.EMReposConfig.invoke(EMReposConfig.java:346)
    at oracle.sysman.emcp.EMReposConfig.invoke(EMReposConfig.java:158)
    at oracle.sysman.emcp.EMConfig.perform(EMConfig.java:253)
    at oracle.sysman.assistants.util.em.EMConfiguration.run(EMConfiguration.java:583)
    at oracle.sysman.assistants.dbca.backend.PostDBCreationStep.executeImpl(PostDBCreationStep.java:968)
    at oracle.sysman.assistants.util.step.BasicStep.execute(BasicStep.java:210)
    at oracle.sysman.assistants.util.step.Step.execute(Step.java:140)
    at oracle.sysman.assistants.util.step.StepContext$ModeRunner.run(StepContext.java:2667)
    at java.lang.Thread.run(Thread.java:595)
    Jan 18, 2014 9:38:23 AM oracle.sysman.emcp.EMConfig restoreOuiLoc
    CONFIG: Restoring oracle.installer.oui_loc to C:\app\Damien\product\11.2.0\dbhome_1\oui
    My Listner status output is here:
    LSNRCTL for 32-bit Windows: Version 11.2.0.1.0 - Production on 18-JAN-2014 10:14:39
    Copyright (c) 1991, 2010, Oracle.  All rights reserved.
    Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=IPC)(KEY=ipc)))
    STATUS of the LISTENER
    Alias                     LISTENER
    Version                   TNSLSNR for 32-bit Windows: Version 11.2.0.1.0 - Production
    Start Date                18-JAN-2014 09:27:34
    Uptime                    0 days 0 hr. 47 min. 6 sec
    Trace Level               off
    Security                  ON: Local OS Authentication
    SNMP                      OFF
    Listener Parameter File   C:\app\Damien\product\11.2.0\dbhome_1\network\admin\listener.ora
    Listener Log File         c:\app\damien\diag\tnslsnr\LONDON\listener\alert\log.xml
    Listening Endpoints Summary...
      (DESCRIPTION=(ADDRESS=(PROTOCOL=ipc)(PIPENAME=\\.\pipe\ipcipc)))
      (DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=192.168.10.4)(PORT=1521)))
      (DESCRIPTION=(ADDRESS=(PROTOCOL=ipc)(PIPENAME=\\.\pipe\EXTPROC1521ipc)))
    Services Summary...
    Service "CLRExtProc" has 1 instance(s).
      Instance "CLRExtProc", status UNKNOWN, has 1 handler(s) for this service...
    The command completed successfully
    I can login as sys into my database through sqlplus, so it seems the database is up and running, it just seems to be a listener problem maybe??
    Many thanks for any assistance that you give. I'm learning so be gentle...
    Damien

    SOLVED!
    OK all solved now, thanks to the link to Ed Stevens website that Baris posted (mucho respect )
    Seems that like Barus said I was not using Dynamic Registration, which means that I would need to manua
    ly update the listerner.ora file. On top of that it seems that for some my tnsnames.ora wasn't resolving mt database name so the tnsping wasfailing.
    What I did to solve the name resolution problem
    1. Opened the
    Network Configuration Assistant and saw that my listener didnt have my DB registered with it. So I added it. What this horrible GUI tool does is update the tnsnames and listener.ora files for you. So once that was done I went to the command prompt and did ;'tnsping <dn name> and hey presto it was getting a nice response.
    Then I re-ran my DB Configuration Assistant and tried to reconfigure my database. However it aing failed and gave me the same message that I was originally getting about the DB Service not being registered etc..the lister status still said that same thing:
    Services Summary...
    Service "CLRExtProc" has 1 instance(s).
      Instance "CLRExtProc", status UNKNOWN, has 1 handler(s) for this service...
    the 'unknown' means that the DB  didnt tell the listener that it was there but instead the listener is in manual mode and will just use the configuration in the listener.ora to know where the DB is.
    So then I followed the steps on the ED Stevens website (follow the link). He has steps which show how to enable Dynanmic registration so that your DB regusters itself with the listener. In a nutshell, he states that he listener actually doesnt need the listerner.ora if using dynamic registration. I shutdown the DB, stopped the listener then I renamed the lsitener.ora to listerner.old, then started the lietener and checked the status and it said 'the listener supports no service' I then started the DB and, then resched teh listener status, it then read 'status: READY'... hooray!, the DB had dynamically registered itself with the listener. I then was able to successfully start up and run Enterprise Manager.
    Thanks for all your help Baris, and Ed Steven website.
    I know more now than when I started so I'm happy.
    Thanks.

  • Issue while installing WCS using omii.ini: Database ping failed

    Hi,
    I am trying to install WCS on local linux VM. I am following the document 'Oracle WebCenter Sites: Installing on Oracle WebLogic Application Server".
    Following are the things I have been able to do successfully:
    Install Oracle DB, create a database and then create a user for this database
    Install WebLogic server, create domain, create admin server, managed server, and finally create a datasource. THe datasource connection to the DB created in step 1 above is successfull.
    I downloaded the WCS installer from Oracle Website 'WebCenterSites_11.1.1.6_bp1'. I am installing using silent installer using omii.ini file.
    During installation, on receiving the prompt to install CS and CAS applications, I installed them successfully via WebLogic console.
    I tested the URL 'http://localhost:7001/cs/HelloCS' and it showed me the Oracle WCS 11g page.
    Now, when I go back to the wcs installation terminal and hit Enter, it gives following error:
    [2013-07-11 01:32:21.861][CS.INSTALL][INFO] 1. If your platform requires you to manually deploy the Sites application, deploy Sites now. Otherwise, continue with step 2 2. Restart your application server. 3. Test the URL http:////HelloCS to see if application is deployed successfully 4. If the test is successful, press ENTER. URL http://localhost:7001/cs/HelloCS [2013-07-11 01:41:16.841][CS.INSTALL][INFO] CSSetupEngine.testConnectionAction:  Testing user configuration and database connectivity. [2013-07-11 01:41:17.118][CS.INSTALL][INFO] CSSetupEngine.postURL:  PostURL success for http://localhost:7001/cs/HelloCS [2013-07-11 01:41:17.118][CS.INSTALL][INFO] CSSetupEngine.testConnectionAction:  Web Server and Application Server Configuration test finished successfully. [2013-07-11 01:41:17.118][CS.INSTALL][INFO] CSSetupEngine.testConnectionAction:  Attempting to Ping the Database. [2013-07-11 01:41:17.459][CS.INSTALL][ERROR] CSSetupEngine.doPing:  Database Ping Failed. Make sure your application server and web server are running. Response received = HTTP/1.1 200 OK HOST_SERVICE: FutureTenseContentServer:11.1.1.6.1 Transfer-Encoding: chunked Date: Wed, 10 Jul 2013 20:11:17 GMT Set-Cookie: JSESSIONID=vpMNRd1Fwb1NJyb5NH1pXx5dfmPhzzyJL2S3yYry3FwQqL8hFVJ6!1994306862; path=/; HttpOnly Content-Type: text/html; charset=UTF-8 X-Powered-By: Servlet/2.5 JSP/2.1 [2013-07-11 01:41:17.459][CS.INSTALL][ERROR] CSSetupEngine.doPing:  Database Ping Failed. Make sure your application server and web server are running. Response received = HTTP/1.1 200 OK HOST_SERVICE: FutureTenseContentServer:11.1.1.6.1 Transfer-Encoding: chunked Date: Wed, 10 Jul 2013 20:11:17 GMT Set-Cookie: JSESSIONID=vpMNRd1Fwb1NJyb5NH1pXx5dfmPhzzyJL2S3yYry3FwQqL8hFVJ6!1994306862; path=/; HttpOnly Content-Type: text/html; charset=UTF-8 X-Powered-By: Servlet/2.5 JSP/2.1 [2013-07-11 01:41:17.460][CS.INSTALL][ERROR] CSSetupEngine.testConnectionAction: Database Ping was attempted with WCSDataSource as the DSN. The URL that was passed in = http://localhost:7001/cs/CatalogManager. Please Check your connection and property files settings. [2013-07-11 01:41:17.460][CS.INSTALL][ERROR] CSSetupEngine.testConnectionAction:  Install was unable to ping the database. Installation has halted. [2013-07-11 01:41:17.461][CS.INSTALL][ERROR] Worker.run. Install failed.                Please check log file.                          Click Yes to modify your install choices      and re-try install.                             Click No to terminate application. 
    It looks like DB ping is getting failed.
    But I am not sure how to resolve this error.
    Please help. I am pasting the content of my bea_omii.ini file that I have used. (Please view as HTML, as formatting is getting lost on this page.)
    Do let me know if any other information is required from my end.
    bea_omii.ini:
    #ContentServer install properties #Thu Apr 17 12:03:27 IST 2008 # Content Server Information # Specify the directory where you want to install Content Server i.e on windows C\:/csinstall on unix /opt/csinstall CSInstallDirectory=/home/oracle/WCS # Path to the Shared Directory i.e on windows C\:/csinstall/Shared on unix /opt/csinstall/Shared CSInstallSharedDirectory=/home/oracle/WCS/Shared # For delivery installation set Development to false Development=true # CSInstallType single/upgrade/cluster default is single only needed for upgrade or cluster #CSInstallType=single # This is to select APPSERVER Note: PORTALSERVER is not supported CSInstallPlatformType=APPSERVER # Set the application/portal server you want to install # Possible options are: wls92 for ( weblogic server), websphere60 (for webshpere), tomcat5 (for tomcat) CSInstallAppServerType=wls92 # Set the path to the server directory ex. For weblogic, on windows CSInstallAppServerPath=C\:\\bea\\wlserver_10.3 # on unix CSInstallAppServerPath=/u01/software/bea/wlserver_10.3 CSInstallAppServerPath=/home/oracle/Oracle/Middleware/wlserver_10.3 # [WEBLOGIC ONLY] Set the path to the weblogic domain i.e. on windows CSInstallWLDomainPath=C\:/bea/user_projects/domains/base_domain # on unix CSInstallWLDomainPath=/u01/software/bea/user_projects/domains/base_domain CSInstallWLDomainPath=/home/oracle/Oracle/Middleware/user_projects/domains/WCSDomain # [WEBLOGIC ONLY] Set the weblogic domain name i.e. base_domain name from path C\:/bea/user_projects/domains/base_domain CSInstallAdminDomainName=WCSDomain # Option for manual deployment (Should always be set to true) CSInstallbManual=true #Manual deployment needs to set the path where installer has to explode the war CSManualDeployPath=/home/oracle/WCS/deployment # Set the context path for your web application for example /cs/ sCgiPath=/cs/ # Set the database type Possible options #CSInstallDatabaseType=  [SQL Server, DB2, Oracle10]  CSInstallDatabaseType=Oracle10 # Set the data source name CSInstallDBDSN=WCSDataSource # By default it is installed as a primary cluster member. To install as cluster member make CSInstallType=cluster. CSInstallType=single #WEM installation IsWEMInstall=TRUE #hostname where cs is installed CASHostName=localhost # port number of cs installation CASPortNumber=7003 #Server HostName of internally accessible CAS CASHostNameLocal=localhost #Server PortNumber of internally accessible CAS CASPortNumberLocal=7003 #Server HostName where CAS is actually deployed CASHostNameActual=localhost # Select the default logger name (possible values com.fatwire.cs.core.logging.StandardLog, com.fatwire.cs.core.logging.TraditionalLog # com.fatwire.cs.core.logging.StandardTraditionalLog , org.apache.commons.logging.impl.Log4JLogger LoggerName=org.apache.commons.logging.impl.Log4JLogger # Set the host name where the application will be running CSInstallWebServerAddress=localhost # Set the port number where the application will be running CSInstallWebServerPort=7001 # Set this property to true if you are installing Spark CSInstallSpark=false # Sample Sites Information # Set this true if you want to install Avisports sample site. Avisports=true # CS-Direct and CS-Direct Advantage properties. Please don't touch them ContentCentre=true CatalogCentre=true # Set this true if you want to install CS Engage otherwise false MarketingStudio=true # Set this to true if you want to install Commerce Connectors CommerceConnector=true # Set this to true to install Structure and Navigation for FS2 this is only installed if this is development mode FSCore=true # Set this to true to install Engage Extensions for Structure and Navigation. This depends on Development and FSCore FSEngageCore=true # Set this to true to install Store Schema. This depends on Development and FSCore FSStoreSchema=true # Set this to true to install Engage Extensions for Store Schema. This depends on Development, CommereceConnector and FSEngageCore FSEngageStoreSchema=true # Set this to true to install Document Schema. This depends on Development and FSCore FSDocSchema=true # Set this to true to install Sample Visitors. This depends on Development and FSCore FSLocalUser=true # Set this to true to install Pretty URL Package. This depends on Development and FSCore FSPrettyURL=true # Set this to true to install Store Demo Data. This depends on Development and FSStoreSchema FSStoreDemoData=true # Set this to true to install Document Demo Data. This depends on Development and FSDocSchema FSDocDemoData=true # Set this to true to install Engage Store Data. This depends on Development,FSStoreDemoData,FSEngageStoreSchema and FSStoreSchema FSEngageStoreDemoData=true # If you want to install First Site II Site View set it true otherwise false. This depends on Development and FSStoreSchema FSSiteView=true # Set this to true to install Analytics. This depends on Development,FSCore,FSEngageCore,FSStoreSchema,CommerceConnector and CatalogCentre FSAnalytics=true # Set this to true to install Legacy (core) asset types (Article, Linkset). This depends on Development and ContentCentre CCSampleAssets=true # Set this to true to install Burlington Financial asset types. This depends on Development and ContentCentre CCSampleAssetsBF=true # Set this to true to install Engage and Analytics extensions for Burlington Financial. This depends on Development,MarketingStudio and ContentCentre MSSampleAssetsBF=true # Set this to true to install HelloAssetWorld asset types. This depends on Development and ContentCentre CCSampleAssetsHW=true # Set this to true to install GE Lighting asset types. This depends on Development and ContentCentre CatCSampleAssets=true # Set this to true to install Hello World sample site.  This depends on Development and ContentCentre CCSampleSiteHW=true # Set this to true to install Burlington Financial sample site. This depends on CCSampleAssets and CCSampleAssetsBF CCSampleSiteBF=true # Set this to true to install Burlington Financial Extensions sample site. MSSampleSiteBF=true # Set this to true to install GE Lighting sample site. MSSampleSiteGE=true # Spark sample site components # Set this to true to install Document Management sample asset types DMSampleAssets=false # Set this to true to install Content Management sample asset types WCMSampleAssets=false # Set this to true to install Base Components SparkSampleSite=false # Set this to true to install Sample Data SparkSampleData=false # Set this to true to install Sample Portlets. Set this true if this is a portal server SparkSamplePortlets=false

    Thanks for your reply Yct.
    I got the ping issue resolved today, there was an issue in the data source. Finally I was able to complete the installation successfully.
    But there is one more issue now. After completing the installation, I am trying to access the URL to get to the WCS login page, but with no success.
    Below, I am mentioning few URLs that I tried, and the outcome:
    http://localhost:7001/cs/HelloCS ,           This URL gives me a page with some static content messages like 'Welcome to Oracle WebCenter Sites 11gR1'. Then there are some text lines in blue color. I think this page is working as expected.
    http://localhost:7001/cs/login , this URL automatically gets redirected to the URL 'http://localhost:7003/cas/login?service=http%3A%2F%2Flocalhost%3A7001%2Fcs%2Fwem%2Ffatwire%2Fwem%2FWelcome' and I get an error message 'Firefox can't establish a connection to the server at localhost:7003.'
    http://localhost:7001/cas/login, this takes me to login page, where when I enter fwadmin@xceladmin credentials, I am taken to JASIG Central Authentication Service page, which is again static, and I can't do anything on this page
    http://localhost:7001/cs/Satellite?c=Page&cid=1327351719456&pagename=avisports%2FPage%2FHomeLayout1 , this takes me to the Avisports site, which is functional
    http://localhost:7001/cs/Satellite?c=Page&childpagename=FirstSiteII%2FFSIILayout&cid=1124747609916&pagename=FSIIWrapper, this takes me to he FirstSit page, which is again functional
    Issue: I am not getting the main login page, where I would get 3 sites(Avisports/FirstsiteII) in the dropdown.
    Looks like there is something wrong going on.
    Following I am pasting my omii.ini file, if it helps:
    #ContentServer install properties
    #Thu Apr 17 12:03:27 IST 2008
    # Content Server Information
    # Specify the directory where you want to install Content Server i.e on windows C\:/csinstall on unix /opt/csinstall
    CSInstallDirectory=/home/oracle/WCS
    # Path to the Shared Directory i.e on windows C\:/csinstall/Shared on unix /opt/csinstall/Shared
    CSInstallSharedDirectory=/home/oracle/WCS/Shared
    # For delivery installation set Development to false
    Development=true
    # CSInstallType single/upgrade/cluster default is single only needed for upgrade or cluster
    #CSInstallType=single
    # This is to select APPSERVER Note: PORTALSERVER is not supported
    CSInstallPlatformType=APPSERVER
    # Set the application/portal server you want to install
    # Possible options are: wls92 for ( weblogic server), websphere60 (for webshpere), tomcat5 (for tomcat)
    CSInstallAppServerType=wls92
    # Set the path to the server directory ex. For weblogic, on windows CSInstallAppServerPath=C\:\\bea\\wlserver_10.3
    # on unix CSInstallAppServerPath=/u01/software/bea/wlserver_10.3
    CSInstallAppServerPath=/home/oracle/Oracle/Middleware/wlserver_10.3
    # [WEBLOGIC ONLY] Set the path to the weblogic domain i.e. on windows CSInstallWLDomainPath=C\:/bea/user_projects/domains/base_domain
    # on unix CSInstallWLDomainPath=/u01/software/bea/user_projects/domains/base_domain
    CSInstallWLDomainPath=/home/oracle/Oracle/Middleware/user_projects/domains/WCSDomain
    # [WEBLOGIC ONLY] Set the weblogic domain name i.e. base_domain name from path C\:/bea/user_projects/domains/base_domain
    CSInstallAdminDomainName=WCSDomain
    # Option for manual deployment (Should always be set to true)
    CSInstallbManual=true
    #Manual deployment needs to set the path where installer has to explode the war
    CSManualDeployPath=/home/oracle/WCS/deployment
    # Set the context path for your web application for example /cs/
    sCgiPath=/cs/
    # Set the database type Possible options
    #CSInstallDatabaseType=  [SQL Server, DB2, Oracle10] 
    CSInstallDatabaseType=Oracle10
    # Set the data source name
    CSInstallDBDSN=WCSDataSource
    # By default it is installed as a primary cluster member. To install as cluster member make CSInstallType=cluster.
    CSInstallType=single
    #WEM installation
    IsWEMInstall=TRUE
    #hostname where cs is installed
    CASHostName=localhost
    # port number of cs installation
    CASPortNumber=7003
    #Server HostName of internally accessible CAS
    CASHostNameLocal=localhost
    #Server PortNumber of internally accessible CAS
    CASPortNumberLocal=7003
    #Server HostName where CAS is actually deployed
    CASHostNameActual=localhost
    # Select the default logger name (possible values com.fatwire.cs.core.logging.StandardLog, com.fatwire.cs.core.logging.TraditionalLog
    # com.fatwire.cs.core.logging.StandardTraditionalLog , org.apache.commons.logging.impl.Log4JLogger
    LoggerName=org.apache.commons.logging.impl.Log4JLogger
    # Set the host name where the application will be running
    CSInstallWebServerAddress=localhost
    # Set the port number where the application will be running
    CSInstallWebServerPort=7001
    # Set this property to true if you are installing Spark
    CSInstallSpark=false
    # Sample Sites Information
    # Set this true if you want to install Avisports sample site.
    Avisports=true
    # CS-Direct and CS-Direct Advantage properties. Please don't touch them
    ContentCentre=true
    CatalogCentre=true
    # Set this true if you want to install CS Engage otherwise false
    MarketingStudio=true
    # Set this to true if you want to install Commerce Connectors
    CommerceConnector=true
    # Set this to true to install Structure and Navigation for FS2 this is only installed if this is development mode
    FSCore=true
    # Set this to true to install Engage Extensions for Structure and Navigation. This depends on Development and FSCore
    FSEngageCore=true
    # Set this to true to install Store Schema. This depends on Development and FSCore
    FSStoreSchema=true
    # Set this to true to install Engage Extensions for Store Schema. This depends on Development, CommereceConnector and FSEngageCore
    FSEngageStoreSchema=true
    # Set this to true to install Document Schema. This depends on Development and FSCore
    FSDocSchema=true
    # Set this to true to install Sample Visitors. This depends on Development and FSCore
    FSLocalUser=true
    # Set this to true to install Pretty URL Package. This depends on Development and FSCore
    FSPrettyURL=true
    # Set this to true to install Store Demo Data. This depends on Development and FSStoreSchema
    FSStoreDemoData=true
    # Set this to true to install Document Demo Data. This depends on Development and FSDocSchema
    FSDocDemoData=true
    # Set this to true to install Engage Store Data. This depends on Development,FSStoreDemoData,FSEngageStoreSchema and FSStoreSchema
    FSEngageStoreDemoData=true
    # If you want to install First Site II Site View set it true otherwise false. This depends on Development and FSStoreSchema
    FSSiteView=true
    # Set this to true to install Analytics. This depends on Development,FSCore,FSEngageCore,FSStoreSchema,CommerceConnector and CatalogCentre
    FSAnalytics=true
    # Set this to true to install Legacy (core) asset types (Article, Linkset). This depends on Development and ContentCentre
    CCSampleAssets=true
    # Set this to true to install Burlington Financial asset types. This depends on Development and ContentCentre
    CCSampleAssetsBF=true
    # Set this to true to install Engage and Analytics extensions for Burlington Financial. This depends on Development,MarketingStudio and ContentCentre
    MSSampleAssetsBF=true
    # Set this to true to install HelloAssetWorld asset types. This depends on Development and ContentCentre
    CCSampleAssetsHW=true
    # Set this to true to install GE Lighting asset types. This depends on Development and ContentCentre
    CatCSampleAssets=true
    # Set this to true to install Hello World sample site.  This depends on Development and ContentCentre
    CCSampleSiteHW=true
    # Set this to true to install Burlington Financial sample site. This depends on CCSampleAssets and CCSampleAssetsBF
    CCSampleSiteBF=true
    # Set this to true to install Burlington Financial Extensions sample site.
    MSSampleSiteBF=true
    # Set this to true to install GE Lighting sample site.
    MSSampleSiteGE=true
    # Spark sample site components
    # Set this to true to install Document Management sample asset types
    DMSampleAssets=false
    # Set this to true to install Content Management sample asset types
    WCMSampleAssets=false
    # Set this to true to install Base Components
    SparkSampleSite=false
    # Set this to true to install Sample Data
    SparkSampleData=false
    # Set this to true to install Sample Portlets. Set this true if this is a portal server
    SparkSamplePortlets=false

  • Database Logon Failed which created by Crystal Report 2008

    this time i meet the famous error again which is database logon failed.
    i created a crystal report 2008 starting from blank report, then connect with odbc
    i use 2008 method
    objRpt.SetDatabaseLogon(db_username, db_password, odbc_name, database_name);
    2008 method will get database logon failed even set database location and verify database again
    then i use 8.5 method and try again for 2008 report. it said field name is unknown for one of formula
    then i drag field again for formula and set database location and verify database again
    it said the same error.
    then i uninstall 8.5 crytal report software in window 7 deployment machine, and do above again, it said the same error
    //'Create a new Stored Procedure Table to replace the reports current table.
            CrystalDecisions.ReportAppServer.DataDefModel.Procedure boTable = new CrystalDecisions.ReportAppServer.DataDefModel.Procedure();
            //'boMainPropertyBag: These hold the attributes of the tables ConnectionInfo object
            PropertyBag boMainPropertyBag = new PropertyBag();
            //'boInnerPropertyBag: These hold the attributes for the QE_LogonProperties
            //'In the main property bag (boMainPropertyBag)
            PropertyBag boInnerPropertyBag = new PropertyBag();
            //'Set the attributes for the boInnerPropertyBag
            boInnerPropertyBag.Add("Connect Timeout", "15");
            //boInnerPropertyBag.Add("Data Source", "MyDataSource");
            boInnerPropertyBag.Add("Data Source", "10.1.1.191");
            boInnerPropertyBag.Add("DataTypeCompatibility", "0");
            boInnerPropertyBag.Add("General Timeout", "0");
            //boInnerPropertyBag.Add("Initial Catalog", "MyCatalog");
            boInnerPropertyBag.Add("Initial Catalog", database_name);
            boInnerPropertyBag.Add("Integrated Security", "False");
            boInnerPropertyBag.Add("Locale Identifier", "1033");
            boInnerPropertyBag.Add("MARS Connection", "0");
            //boInnerPropertyBag.Add("OLE DB Services", "-5");
            //boInnerPropertyBag.Add("ODBC", "-5");
            boInnerPropertyBag.Add("ODBC", "Cheque");
            boInnerPropertyBag.Add("Provider", "SQLNCLI");
            boInnerPropertyBag.Add("Tag with column collation when possible", "0");
            boInnerPropertyBag.Add("Trust Server Certificate", "0");
            boInnerPropertyBag.Add("Use Encryption for Data", "0");
            //'Set the attributes for the boMainPropertyBag
            boMainPropertyBag.Add("Database DLL", "crdb_ado.dll");
            //boMainPropertyBag.Add("Database DLL", "p2sodbc.dll");
            //boMainPropertyBag.Add("QE_DatabaseName", "VEPILOT");
            boMainPropertyBag.Add("QE_DatabaseName", database_name);
            //boMainPropertyBag.Add("QE_DatabaseType", "OLE DB (ADO)");
            boMainPropertyBag.Add("QE_DatabaseType", "ODBC");
            //'Add the QE_LogonProperties we set in the boInnerPropertyBag Object
            boMainPropertyBag.Add("QE_LogonProperties", boInnerPropertyBag);
            boMainPropertyBag.Add("QE_ServerDescription", "MyServer");
            boMainPropertyBag.Add("QE_SQLDB", "True");
            boMainPropertyBag.Add("SSO Enabled", "False");
            //'Create a new ConnectionInfo object
            CrystalDecisions.ReportAppServer.DataDefModel.ConnectionInfo boConnectionInfo = new CrystalDecisions.ReportAppServer.DataDefModel.ConnectionInfo();
            //'Pass the database properties to a connection info object
            boConnectionInfo.Attributes = boMainPropertyBag;
            //'Set the connection kind
            boConnectionInfo.Kind = CrConnectionInfoKindEnum.crConnectionInfoKindCRQE;
            //'*EDIT* Set the User Name and Password if required.
            boConnectionInfo.UserName = db_username;
            boConnectionInfo.Password = db_password;
            //'Pass the connection information to the table
            boTable.ConnectionInfo = boConnectionInfo;
    CrystalDecisions.ReportAppServer.DataDefModel.Tables boTables = objRpt.ReportClientDocument.DatabaseController.Database.Tables;
                CrystalDecisions.CrystalReports.Engine.Tables tables = objRpt.Database.Tables;
                foreach (CrystalDecisions.CrystalReports.Engine.Table table in tables)
                    if (!string.IsNullOrEmpty(table.Name))
                        //boTable.Name = table.Name;
                        //boTable.QualifiedName = database_name + ".dbo." + table.Name;
                        //boTable.Alias = table.Name;
                        boTable.Name = "sp_ChequeIssueDetRpt";
                        boTable.QualifiedName = database_name + ".dbo.sp_ChequeIssueDetRpt";
                        boTable.Alias = "sp_ChequeIssueDetRpt";
                        objRpt.ReportClientDocument.DatabaseController.SetTableLocation(boTables[0], boTable);
                objRpt.VerifyDatabase();
    http://sourceforge.net/projects/aspchequesprint/files/ChequeIssueDet.rpt/download

    No subreport, only a stored procedure with final two lines are
    print @m_sql
    exec (@m_sql)
    After use generated code in the link above
    Error at boReportDocument.VerifyDatabase();
    Inner Exception : no error
    Message "Logon failed"
    ErrorID : CrystalDecisions.CrystalReports.Engine.EngineExceptionErrorID.LogOnFailed
    HelpLink : null
    stacktrace :  CrystalDecisions.CrystalReports.Engine.ReportDocument.VerifyDatabase()\r\n   at viewReport.Page_Load(Object sender, EventArgs e) 於 d:
    Data
    My Documents
    Visual Studio 2008
    WebSites
    Cheques
    viewReport.aspx.cs: row 1302\r\n   at System.Web.Util.CalliHelper.EventArgFunctionCaller(IntPtr fp, Object o, Object t, EventArgs e)\r\n   at System.Web.Util.CalliEventHandlerDelegateProxy.Callback(Object sender, EventArgs e)\r\n   at System.Web.UI.Control.OnLoad(EventArgs e)\r\n   at System.Web.UI.Control.LoadRecursive()\r\n   於 System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)
    TargetSite : {Void VerifyDatabase()}
    string reportPath = report_path + "ChequeIssueDet.rpt";
                boReportDocument = new ReportDocument();
                //**EDIT** Change the path and report name to the report you want to change.
                boReportDocument.Load(reportPath, OpenReportMethod.OpenReportByTempCopy);
                //Create a new Stored Procedure Table to replace the reports current table.
                CrystalDecisions.ReportAppServer.DataDefModel.Procedure boTable =
                new CrystalDecisions.ReportAppServer.DataDefModel.Procedure();
                //boMainPropertyBag: These hold the attributes of the tables ConnectionInfo object
                PropertyBag boMainPropertyBag = new PropertyBag();
                //boInnerPropertyBag: These hold the attributes for the QE_LogonProperties
                //In the main property bag (boMainPropertyBag)
                PropertyBag boInnerPropertyBag = new PropertyBag();
                //Set the attributes for the boInnerPropertyBag
                boInnerPropertyBag.Add("Database", database_name);
                boInnerPropertyBag.Add("DSN", "Cheque");
                boInnerPropertyBag.Add("UseDSNProperties", "False");
                //Set the attributes for the boMainPropertyBag
                boMainPropertyBag.Add("Database DLL", "crdb_odbc.dll");
                boMainPropertyBag.Add("QE_DatabaseName", database_name);
                boMainPropertyBag.Add("QE_DatabaseType", "ODBC (RDO)");
                //Add the QE_LogonProperties we set in the boInnerPropertyBag Object
                boMainPropertyBag.Add("QE_LogonProperties", boInnerPropertyBag);
                boMainPropertyBag.Add("QE_ServerDescription", "Cheque");
                boMainPropertyBag.Add("QE_SQLDB", "True");
                boMainPropertyBag.Add("SSO Enabled", "False");
                //Create a new ConnectionInfo object
                CrystalDecisions.ReportAppServer.DataDefModel.ConnectionInfo boConnectionInfo =
                new CrystalDecisions.ReportAppServer.DataDefModel.ConnectionInfo();
                //Pass the database properties to a connection info object
                boConnectionInfo.Attributes = boMainPropertyBag;
                //Set the connection kind
                boConnectionInfo.Kind = CrConnectionInfoKindEnum.crConnectionInfoKindCRQE;
                //**EDIT** Set the User Name and Password if required.
                boConnectionInfo.UserName = db_username;
                boConnectionInfo.Password = db_password;
                //Pass the connection information to the table
                boTable.ConnectionInfo = boConnectionInfo;
                //Get the Database Tables Collection for your report
                CrystalDecisions.ReportAppServer.DataDefModel.Tables boTables;
                boTables = boReportDocument.ReportClientDocument.DatabaseController.Database.Tables;
                //For each table in the report:
                // - Set the Table Name properties.
                // - Set the table location in the report to use the new modified table
                boTable.Name = "sp_ChequeIssueDetRpt;1";
                boTable.QualifiedName = database_name+".dbo.sp_ChequeIssueDetRpt;1";
                boTable.Alias = "sp_ChequeIssueDetRpt;1";
                boReportDocument.ReportClientDocument.DatabaseController.SetTableLocation(boTables[0], boTable);
                //Verify the database after adding substituting the new table.
                //To ensure that the table updates properly when adding Command tables or Stored Procedures.
                boReportDocument.VerifyDatabase();
                //**EDIT** Set the value for the Stored Procedure parameters.
                string m_curUser = "";
                int spid = Convert.ToInt32(Request.Cookies["login_cookie"]["spid"]);
                queryString = "select * from v_All_Session where SPID=" + spid.ToString();
                //string _connectionString = ConfigurationManager.ConnectionStrings["ChequeConnectionString"].ConnectionString;
                using (SqlConnection connection = new SqlConnection(_connectionString))
                    SqlCommand command = connection.CreateCommand();
                    command.CommandText = queryString;
                    connection.Open();
                    using (SqlDataReader datareader = command.ExecuteReader())
                        if (datareader.HasRows == true)
                            while (datareader.Read())
                                if (datareader["UserID"] != System.DBNull.Value)
                                    m_curUser = datareader["UserID"].ToString();
                        datareader.Close();
                    connection.Close();
                boReportDocument.SetParameterValue("@UserID", m_curUser);
                if (string.IsNullOrEmpty(Session["fm_CoCode"].ToString()))
                    boReportDocument.SetParameterValue("@fm_CoCode", Session["fm_CoCode"].ToString());
                if (string.IsNullOrEmpty(Session["to_CoCode"].ToString()))
                    boReportDocument.SetParameterValue("@to_CoCode", Session["to_CoCode"].ToString());
                if (string.IsNullOrEmpty(Session["fm_BankACNo"].ToString()))
                    boReportDocument.SetParameterValue("@fm_BankACNo", Session["fm_BankACNo"].ToString());
                if (string.IsNullOrEmpty(Session["to_BankACNo"].ToString()))
                    boReportDocument.SetParameterValue("@to_BankACNo", Session["to_BankACNo"].ToString());
                if (string.IsNullOrEmpty(Session["fm_BatchNo"].ToString()))
                    boReportDocument.SetParameterValue("@fm_BatchNo", Session["fm_BatchNo"].ToString());
                if (string.IsNullOrEmpty(Session["to_BatchNo"].ToString()))
                    boReportDocument.SetParameterValue("@to_BatchNo", Session["to_BatchNo"].ToString());
    Edited by: Mathew_666 on Jul 19, 2011 4:27 AM
    Edited by: Mathew_666 on Jul 19, 2011 4:28 AM

  • Installation issue : sql server 2008 r2 some services failed to installed on windows 7

    I have been facing this problem while installing sql server 2008 r2.. i tried so many times but same result .. it shows sql server installed with some errors
    database engine service : failed
    SQL Server Replication : failed
    Full-Text Search : failed
    Analysis Services : failed
    Reporting Services : failed
    And my Log file (or) summary file is (it is in C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log):
    Overall summary:
      Final result:                  User cancelled
      Exit code (Decimal):           -2068380094
      Exit facility code:            1207
      Exit error code:               1602
      Exit message:                  User has cancelled.
      Start time:                    2014-08-14 21:15:26
      End time:                      2014-08-14 21:23:58
      Requested action:              AddNode
    Machine Properties:
      Machine name:                  MANJU-PC
      Machine processor count:       4
      OS version:                    Windows Vista
      OS service pack:               
      OS region:                     United States
      OS language:                   English (United States)
      OS architecture:               x86
      Process architecture:          32 Bit
      OS clustered:                  No
    Product features discovered:
      Product              Instance             Instance ID                   
    Feature                                  Language            
    Edition              Version         Clustered
      Sql Server 2008      MSSQLSERVER          MSSQL10.MSSQLSERVER            Database Engine Services                
    1033                                      10.0.1600.22   
    No        
      Sql Server 2008      MSSQLSERVER          MSSQL10.MSSQLSERVER            SQL Server Replication                  
    1033                                      10.0.1600.22   
    No        
      Sql Server 2008      MSSQLSERVER          MSSQL10.MSSQLSERVER            Full-Text Search                        
    1033                                      10.0.1600.22   
    No        
      Sql Server 2008      MSSQLSERVER          MSAS10.MSSQLSERVER             Analysis Services                       
    1033                                      10.0.1600.22   
    No        
      Sql Server 2008      MSSQLSERVER          MSRS10.MSSQLSERVER             Reporting Services                      
    1033                                      10.0.1600.22   
    No        
      Sql Server 2008                                                         
    Management Tools - Basic                 1033                 Developer Edition   
    10.0.1600.22    No        
      Sql Server 2008                                                         
    Management Tools - Complete              1033                 Developer Edition    10.0.1600.22   
    No        
      Sql Server 2008                                                         
    Client Tools Connectivity                1033                 Developer Edition    10.0.1600.22   
    No        
      Sql Server 2008                                                         
    Client Tools Backwards Compatibility     1033                 Developer Edition    10.0.1600.22    No      
      Sql Server 2008                                                         
    Client Tools SDK                         1033                
    Developer Edition    10.0.1600.22    No        
      Sql Server 2008                                                         
    Integration Services                     1033                 Developer Edition   
    10.0.1600.22    No        
    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:\Softwares\JAVA & .NET SW\SQL Server 2008\SQL Server 2008\x86\setup\
      Installation edition:          DEVELOPER
    User Input Settings:
      ACTION:                        AddNode
      AGTSVCACCOUNT:                 <empty>
      AGTSVCPASSWORD:                *****
      ASSVCACCOUNT:                  <empty>
      ASSVCPASSWORD:                 *****
      CONFIGURATIONFILE:             
      FAILOVERCLUSTERGROUP:          
      FAILOVERCLUSTERNETWORKNAME:    <empty>
      FTSVCACCOUNT:                  <empty>
      FTSVCPASSWORD:                 *****
      HELP:                          False
      INDICATEPROGRESS:              False
      INSTANCENAME:                  <empty>
      MEDIASOURCE:                   D:\Softwares\JAVA & .NET SW\SQL Server 2008\SQL Server 2008\
      PID:                           *****
      QUIET:                         False
      QUIETSIMPLE:                   False
      SQLSVCACCOUNT:                 <empty>
      SQLSVCPASSWORD:                *****
      X86:                           False
      Configuration file:            C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20140814_210558\ConfigurationFile.ini
    Detailed results:
      Feature:                       Integration Services
      Status:                        Failed: see logs for details
      MSI status:                    Passed
      Configuration status:          Passed
      Feature:                       Client Tools Connectivity
      Status:                        Failed: see logs for details
      MSI status:                    Passed
      Configuration status:          Passed
      Feature:                       Management Tools - Complete
      Status:                        Failed: see logs for details
      MSI status:                    Passed
      Configuration status:          Passed
      Feature:                       Management Tools - Basic
      Status:                        Failed: see logs for details
      MSI status:                    Passed
      Configuration status:          Passed
      Feature:                       Client Tools SDK
      Status:                        Failed: see logs for details
      MSI status:                    Passed
      Configuration status:          Passed
      Feature:                       Client Tools Backwards Compatibility
      Status:                        Failed: see logs for details
      MSI status:                    Passed
      Configuration status:          Passed
      Feature:                       Business Intelligence Development Studio
      Status:                        Failed: see logs for details
      MSI status:                    Passed
      Configuration status:          Passed
    Rules with failures:
    Global rules:
    There are no scenario-specific rules.
    Rules report file:               C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20140814_210558\SystemConfigurationCheck_Report.htm
    Exception summary:
    The following is an exception stack listing the exceptions in outermost to innermost order
    Inner exceptions are being indented
    Exception type: Microsoft.SqlServer.Chainer.Infrastructure.CancelException
        Message:
            User has cancelled.
        Stack:
            at Microsoft.SqlServer.Configuration.UIExtension.Request.Wait()
            at Microsoft.SqlServer.Configuration.UIExtension.UserInterfaceProxy.SubmitAndWait(Request request)
            at Microsoft.SqlServer.Configuration.UIExtension.UserInterfaceProxy.NavigateToWaypoint(String moniker)
            at Microsoft.SqlServer.Configuration.UIExtension.UserInterfaceService.Waypoint(String moniker)
            at Microsoft.SqlServer.Configuration.UIExtension.WaypointAction.ExecuteAction(String actionId)
            at Microsoft.SqlServer.Chainer.Infrastructure.Action.Execute(String actionId, TextWriter errorStream)
            at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.InvokeAction(WorkflowObject metabase, TextWriter statusStream)
            at Microsoft.SqlServer.Setup.Chainer.Workflow.PendingActions.InvokeActions(WorkflowObject metaDb, TextWriter loggingStream)

      Requested action:              AddNode
      OS architecture:               x86
      Process architecture:          32 Bit
      OS clustered:                  No
    Product features discovered:
      Product              Instance             Instance ID                   
    Feature                                  Language            
    Edition              Version         Clustered
      Sql Server 2008      MSSQLSERVER          MSSQL10.MSSQLSERVER            Database Engine Services                
    1033                                      10.0.1600.22   
    No        
      Sql Server 2008      MSSQLSERVER          MSSQL10.MSSQLSERVER            SQL Server Replication                  
    1033                                      10.0.1600.22   
    No        
      Sql Server 2008      MSSQLSERVER          MSSQL10.MSSQLSERVER            Full-Text Search                        
    1033                                      10.0.1600.22   
    No        
      Sql Server 2008      MSSQLSERVER          MSAS10.MSSQLSERVER             Analysis Services                       
    1033                                      10.0.1600.22   
    No        
      Sql Server 2008      MSSQLSERVER          MSRS10.MSSQLSERVER             Reporting Services                      
    1033                                      10.0.1600.22   
    No        
      Sql Server 2008                                                         
    Management Tools - Basic                 1033                 Developer Edition   
    10.0.1600.22    No        
      Sql Server 2008                                                         
    Management Tools - Complete              1033                 Developer Edition    10.0.1600.22   
    No        
      Sql Server 2008                                                         
    Client Tools Connectivity                1033                 Developer Edition    10.0.1600.22   
    No        
      Sql Server 2008                                                         
    Client Tools Backwards Compatibility     1033                 Developer Edition    10.0.1600.22    No      
      Sql Server 2008                                                         
    Client Tools SDK                         1033                
    Developer Edition    10.0.1600.22    No        
      Sql Server 2008                                                         
    Integration Services                     1033                 Developer Edition   
    10.0.1600.22    No        
    Instead of installing SQL server instance you selected add node which is to be selected when SQL server installation is to be made on Node which is being added to cluster. Since your OS is not clustered I am sure you selected worng option.
    Please right click on setup file and select run as administrator. Now installation window which pops up on that on left hand side select
    installation and then on page that appears select 'New server standalone installation or add feature to existing installation'.
    You already have SQL server 2008 installed on your machine as per feature discovery report
    Please mark this reply as answer if it solved your issue or vote as helpful if it helped so that other forum members can benefit from it.
    My TechNet Wiki Articles

  • How to "roll back" the model if a database update fails

    I'd like to know if there's a way to "roll back" the model (the values in the managed beans) if a service call to a database fails during the Invoke Application phase. My understanding of the JSF lifecycle is that the values in the model are updated before a service call to a database would happen. If the database update operation fails, it seems to me that the data in the model and the database would be inconsistent.
    For example, say I have a ridiculously simple application that updates a names database. The fields are id, last name, first name. The application has a simple view that allows the user to update a name in the database. The user updates the last name field for a particular record from "Doe" to "Smith" and clicks "submit". The request goes through the lifecycle, the model values are updated from the web form during the Update Model Values phase, then the call to update the database fails during the Invoke Applications phase (the database connection failed). When the Render Response phase completes, the UI would display an error message where I put <h:messages> but the last name value in the UI would show "Smith" instead of "Doe". Is there something I can do to roll the model value back to "Doe" if the database call fails?
    I know that I could redirect to a technical error page, but I'd like to avoid it unless it is the best thing to do.
    I'd appreciate any advice you can offer.
    Thanks.
    - Luke

    I'd like to know if there's a way to "roll back" the model (the values in the managed beans) if a service call to a database fails during the Invoke Application phase. My understanding of the JSF lifecycle is that the values in the model are updated before a service call to a database would happen. If the database update operation fails, it seems to me that the data in the model and the database would be inconsistent.
    For example, say I have a ridiculously simple application that updates a names database. The fields are id, last name, first name. The application has a simple view that allows the user to update a name in the database. The user updates the last name field for a particular record from "Doe" to "Smith" and clicks "submit". The request goes through the lifecycle, the model values are updated from the web form during the Update Model Values phase, then the call to update the database fails during the Invoke Applications phase (the database connection failed). When the Render Response phase completes, the UI would display an error message where I put <h:messages> but the last name value in the UI would show "Smith" instead of "Doe". Is there something I can do to roll the model value back to "Doe" if the database call fails?
    I know that I could redirect to a technical error page, but I'd like to avoid it unless it is the best thing to do.
    I'd appreciate any advice you can offer.
    Thanks.
    - Luke

  • Essbase Registration With Shared Services Fails...

    Hi all,
    I have three system A, B, C in a distributive manner. A has only Oracle 11g and Essbase Server. B has Shared Services, Planning, Essbase Essbase Components, Workspace. C has EPMA, Calc Manager, Reporting Analysis. I created separate database for each components. While configuring I do the following-
    -> First on B I configured Shared Services/Common Settings with its database(1st Time). I could see the green tick.
    -> On A I configured Shared Services/Common Settings with previously configured database. I could see green tick.
    -> On A configure Essbase Server, here I get the error which shows Register with Shared Services failed.
    Examining the configtool_err.log navigate to D:\Hyperion\logs\config folder I see the following message-
    (Jun 10, 2009, 01:13:32 PM), com.hyperion.cis.config.wizard.RunAllTasksWizardAction, ERROR, Shared Services Registration task can not be executed because Shared Services instance is not available in Registry
    (Jun 10, 2009, 01:13:42 PM), com.hyperion.essbase.config.EssbaseAgentTaskProcessor, ERROR, Error in executing the script to register Essbase as a service: exitCode = 1
    I am using v11.1.1.1 on Win 2003.
    Can anyone pls help me how to solve this??
    Thanks.
    Edited by: Sap B on Jun 10, 2009 12:52 AM
    Edited by: Sap B on Jun 10, 2009 1:14 AM
    Edited by: Sap B on Jun 10, 2009 1:15 AM
    Edited by: Sap B on Jun 10, 2009 1:48 AM

    Thanks John. I was so anxious to get a response from you. See, on the machine where only Essbase Server is installed( and 11g as well), on configuration page I get two options- Hyperion Foundation and Essbase. Now Hyperion Foundation( Configure Database and Common Settings) configuration is done properly with previously configured database.
    Now in Essbase node there is Essbase and under it is Essbase Custom Configuration. when I try to configure it I get the error that Register to Shared Services failed. I could see green tick on Essbase Custom Configuration, but a red cross on Essbase.
    What needs to be done John?? Please help.
    Edited by: Sap B on Jun 10, 2009 2:06 AM
    Edited by: Sap B on Jun 10, 2009 6:22 AM

  • Live Office: Database logon failed error

    Please help...Live Office problem...
    Am working in Xcelsius 2008.
    Here's what I'm trying to do:
    1. I set up a Crystal Report using a Stored Procedure as the data provider.
    2. The Stored Procedure has a parameter built into it.
    3. When the report is refreshed within Crystal, the prompt dialog box is displayed; I fill in the desired value, and run. Everything comes back fine.
    4. Crystal Report is exported to the repository.
    5. In Excel, I inserted the Crystal Report using Live Office. It shows up as a Live Office object just fine.
    6. I bound an Excel cell to the prompt; when you change the value in the bound cell, the Live Office object refreshes and displays the correct results.
    7. In Xcelsius, I imported the Excel spreadsheet.
    8. I set up a Text component that is bound to the cell containing the parameter value. Also set up a Grid to display the results, and a Connection Refresh button to call the refresh. Added a Live Office Data Connection pointing to the Web Service URL for the report. 
    Note: When in Designer mode, if the value of the bound cell is changed, the results in the grid change accordingly.
    9.  When in Preview mode (or generated swf), if the Refresh button is pressed, a "User Identification" dialog box appears asking me to log on. The values it asks for are: System, User Name, Password, and Authentication.  I enter the same credentials as are within the Live Office settings in Excel, (which are working correctly), but receive an error "soapenv:Server.generalException: Database logon failed.".
    Note - all the id's are synced up - Business Objects, Database, etc.
    I've tried all kinds of combinations, but nothing gets me past this error. If I use any other server than the system one, the error message is "soapenv:Server.generalException: Server XXXXX not found or server may be down".
    I've noticed that in Excel directly, when I open the spreadsheet and refresh the Live Office object, I am prompted to log on to the database where the stored procedure is being executed. This dialog box does not appear once the Excel sheet has been imported into Xcelsius. One of the combinations I tried in the "User Identification" dialog box was the name of the database server, that didn't work either.
    I also tried creating the Live Office object directly within the Excel spreadsheet in Xcelsius, but then I was unable to bind the prompt value. Could never get the Live Office/Properties menu to appear.
    Ideas? Thoughts?
    Thanks in advance!
    Stephanie

    Got it!
    Here's what I had to do...
    In the CMC, under Object/Process/Database for the Crystal Report -
    which says...
    "Set the default information for logging onto the data source(s) automatically whenever the report is run."
    The Database Connection option had to be set to "Use custom database logon information specified here" and
    the When Viewing Report option set to "Use same database logon as when report is run".
    Then everything works fine - prompts appear, and Xcelsius passes the log on information to the database correctly. Stored procedure executes and returns the correct results.
    Thanks to everyone for their help!
    Stephanie

  • Database logon failed.Database Vendor Error Code:1005(ReportSDKLogonExcep.)

    Hi all,
               I have suffering this error, when I am running my application in IBM Application Server 6. Basically this errors are throughing, when I running the report(which is contains some sub report). But non-sub reports are running fine.  Kindly requested to all, plz help me.
    my documentation...
    1. WASD 5.1.1
    2. Oracle 9i
    3. CR XI R 2
    4. Application connected with Crystal Report by JDBC-JNDI.
    5. My all reports  developed  with CR 10.
    com.crystaldecisions.sdk.occa.report.lib.ReportSDKLogonException: Database logon failed. Database Vendor Error Code: 1005---- Error code:-2147467259 Error code name:failed
         at com.crystaldecisions.sdk.occa.report.lib.ReportSDKLogonException.throwReportSDKLogonException(Unknown Source)
         at com.businessobjects.reports.sdk.b.i.if(Unknown Source)
         at com.businessobjects.reports.sdk.b.i.a(Unknown Source)
         at com.businessobjects.reports.sdk.b.i.byte(Unknown Source)
         at com.businessobjects.reports.sdk.JRCCommunicationAdapter.request(Unknown Source)
    Thanks & Regards,
    Sanjay Biswal

    Hi Ted Ueda,
           In my application, I have connected with Crystal report by JDBC/JNDI.
    now, I give all information about my application. plz follws.
    First :
    Database Type: JDBC(JNDI)
    JDBC Connection : True
    Connection URL : jdbc:oracle:oci8:@<service name>
    Database Classname : oracle.jdbc.driver.OracleDriver
    Service : <service name>
    OS Authentication : False
    JDBC Connection String : !oracle.jdbc.driver.OracleDriver!jdbc:oracle:oci8:/@<service name>
    User ID : <user name>
    Second :
          Some coding are giving, by which Crystal Report accessing Login information from JSP page.
    ConnectionInfos oConnectionInfos= new ConnectionInfos();
    ConnectionInfo oConnectionInfo = new ConnectionInfo();
    oConnectionInfos.setUserName(<user name>);
    oConnectionInfos.setPassword(<password>);
    oConnectionInfo .add(oConnectionInfos);
    CrystalReportViewer oCrystalReportViewer= new CrystalReportViewer();
    oCrystalReportViewer.setReportSource(reportSource);
    oCrystalReportViewer.setDatabaseLogonInfos(connInfos);
    Third :
               ojdbc14.jar files haveing in lib floder.
    This login information in my application. PLz give suggection.
    Thanks & Regards,
    Sanjay Biswal
    Edited by: Sanjay Biswal on Oct 31, 2008 9:56 AM

  • Analytical Services failed to get user's parent group tree with Error

    Hi,
    We have a frequent errror during our weekly batch for an application.
    The context:
    - Essbase Administration Services we are using is version is 9.3.1.
    - 8 applications are calculated during the week-end. The scripts executed are exactly the same for the 8 applications.
    - For example let's say that 5 scripts are launched during the night in the batch for each application (script 1, script 2 ... script 5)
    - App1 and App2 are launched alone and before the 6 others applications as these applications database are 3 x bigger (App1 is calculated alone, then app2 is calculated alone, then app3 to app8 scripts are launched in the same time).
    The issue :
    - We don't see any issue for app3 to app8, the calculation are executed without any problem from script1 to script5.
    - But we have an error in App1 and App2 log when the bath execute script 4 and we see the following error in the server log **
    "Analytical Services failed to get user's parent group tree with Error".
    (** : we don't see any log for script 4 in the application log - it's like the server bypass script 4 to go directly from script 3 to script 5 )
    Nothing special is done in script 4 but just an aggregation of the Year dimension (using a @SUM(@RELATIVE(Year,0)) calculation.
    I think that there is may be a synchronization error with Shared Services but what is strange is that it's always for the same script 4 and the batch is launched at different time every week-end.
    Can the issue be linked to the size of the database of applications (8 Gb) and difficulties for the processor to executes aggregation in a large database volume ?

    Hi,
    According to your description, my understanding is that the error occurred when sending an email to the user in workflow.
    Did you delete the existing Connections before setting NetBiosDomainNamesEnabled?
    If not, I recommend to delete and recreate your AD connections, then set NetBiosDomainNamesEnabled to true.
    Or you can delete the original User Profile Service Application and create a new one, then set the NetBiosDomainNamesEnabled to true and start the User Profile Service Application
     synchronization.
    More reference:
    http://social.technet.microsoft.com/wiki/contents/articles/18060.sharepoint-20xx-what-if-the-domain-netbios-name-is-different-than-the-fqdn-of-the-domain-with-user-profile.aspx
    Best regards.
    Thanks
    Victoria Xia
    TechNet Community Support

Maybe you are looking for

  • Why is Compressor 4 so darned slow?

    Hello all, Using Compressor 4.0.6 and FCX 10.0.7.  Have a few iMac's, all core i7's, 2011 or later, all with a minimum 8GB Ram.  The projects I create are on average 2 hours long, and I produce about 160 of them a year. I've exhausted trying to find

  • Problem under Mac OS X with very long commands

    Hi, in one app. I have very long commands, this make problems under mac os x (sdk 1.4.2) it works under Lin and Win, only under Mac OS X it wont work like it shoud. is there a possibility of arise this "max length" ? sample: http://matrix.phileon.de/

  • Change color on mouse over

    Hi, how can i change the color of column heading during mouse over a particular column.? Does anyone know any html code for this?

  • Best way for exporting a final cut file

    Hi, I'm exporting a final cut project so i can use it in dvd studio pro 4. But it's over two hours. does anybody know the best way to compress it?

  • Dynamic Image From Network Path

    I am trying to setup dynamic student photos onto a report, we are lucky enough to know the photo filenames as they are the same as our student_id's so I setup in a formula: Spot\Image_Bank\QLSPhotographs\Images\" + {Photo_List_By_Course;1.student_id}