Clarity Service Management

Expand all | Collapse all

CDB creation failed

  • 1.  CDB creation failed

    Posted 03-03-2016 09:56 PM

    while installing CASD 14.1 I am getting an error called creation of CDB failed



  • 2.  Re: CDB creation failed

    Posted 03-03-2016 10:05 PM



  • 3.  Re: CDB creation failed

    Posted 03-04-2016 08:21 PM

    Can you check the install_mdb.log the screen print is referring to?  It should have the exact command that failed. 


    I believe that sqlcmd did not run or was not able to connect to your underlying DB server to query if there is a DB called mdb there. That's why the failure 


    _R



  • 4.  Re: CDB creation failed

    Posted 03-05-2016 10:05 AM
    That's good to hear. 


    Are you sure it's load default user ? Or was that load default data ?


    _R




  • 5.  Re: CDB creation failed

    Posted 03-05-2016 10:05 AM

    Wrong post. Ignore above post. 


    _R



  • 6.  Re: CDB creation failed

    Posted 03-06-2016 10:47 AM

    Hi Imayan,

     

    I faced the similar error during the installation of service desk from service management installer. Try to run the setup.exe from the products/SDM folder. It solved my problem earlier.

     

    Regards,

    Balram



  • 7.  Re: CDB creation failed

    Posted 03-07-2016 03:01 PM

    HI Imayan,

    Did the help from Balram fixed your problem?

    let us know if you still suffering issue to install SDM.

    /J



  • 8.  Re: CDB creation failed

    Posted 03-08-2016 09:53 AM

    I've been experiencing a similar problem and have a support ticket open for it.  Our install_mdb.log contains this:

    02-24,16:10:15 INFO - =============================================================

    02-24,16:10:15 INFO - MDBTools Log - Wednesday, February 24, 2016 at 4:10:15 PM CST

    02-24,16:10:15 INFO - JVM Version: 1.7.0_60

    02-24,16:10:15 INFO - MDBTools Version 1.5 SP1 (32-01)

    02-24,16:10:15 INFO - =============================================================

    02-24,16:10:15 INFO - MDBTools_0101I - Command: install database schema from driver file.

    02-24,16:10:15 INFO - MDBTools_0110I - As user: ServiceDesk.

    02-24,16:10:15 INFO - MDBTools_0112I - For vendor: mssql.

    Feb 24, 2016 4:10:15 PM com.microsoft.sqlserver.jdbc.TDSReader readPacket

    WARNING: TDSReader@3634f2 ( ConnectionID:1 TransactionID:0x0000000000000000) Unexpected message type:18 in TDS header; expected type:4

    Feb 24, 2016 4:10:15 PM com.microsoft.sqlserver.jdbc.TDSReader throwInvalidTDS

    SEVERE: TDSReader@3634f2 ( ConnectionID:1 TransactionID:0x0000000000000000) got unexpected value in TDS response at offset:4088

    Feb 24, 2016 4:10:15 PM com.microsoft.sqlserver.jdbc.TDSChannel enableSSL

    WARNING: TDSChannel ( ConnectionID:1 TransactionID:0x0000000000000000) SSL handshake failed: The TDS protocol stream is not valid.

    Feb 24, 2016 4:10:15 PM com.microsoft.sqlserver.jdbc.TDSReader readPacket

    WARNING: TDSReader@e220c4 ( ConnectionID:2 TransactionID:0x0000000000000000) Unexpected message type:18 in TDS header; expected type:4

    Feb 24, 2016 4:10:15 PM com.microsoft.sqlserver.jdbc.TDSReader throwInvalidTDS

    SEVERE: TDSReader@e220c4 ( ConnectionID:2 TransactionID:0x0000000000000000) got unexpected value in TDS response at offset:4088

    Feb 24, 2016 4:10:15 PM com.microsoft.sqlserver.jdbc.TDSChannel enableSSL

    WARNING: TDSChannel ( ConnectionID:2 TransactionID:0x0000000000000000) SSL handshake failed: The TDS protocol stream is not valid.

    02-24,16:10:15 INFO - Url: jdbc:sqlserver://localhost:1433;DatabaseName=mdb

    02-24,16:10:15 INFO - User: ServiceDesk

    02-24,16:10:15 INFO - ErrorCode: 0

    02-24,16:10:15 ERROR - The driver could not establish a secure connection to SQL Server by using Secure Sockets Layer (SSL) encryption. Error: The TDS protocol stream is not valid..

    02-24,16:10:15 INFO - MDBTools_0104I - Total time: 0H:0M:0S.

    02-24,16:10:15 MDBTools install error=3

    02-24,16:10:15 Setupmdb exit /B return code=3

     

    which ultimately results in this in the install.log:

     

     

     

    2016/02/24 16.10.13.974 DEBUG [DeployThread: Configuring CA Service Management common tables] [InstallCDB] 02-24,16:10:13 Checking if mdb already exists...
    2016/02/24 16.10.14.379 DEBUG [DeployThread: Configuring CA Service Management common tables] [InstallCDB] 02-24,16:10:14 Checking existing mdb version...
    2016/02/24 16.10.14.606 DEBUG [DeployThread: Configuring CA Service Management common tables] [InstallCDB] 02-24,16:10:14 Pre-check OKAY ( will upgrade MDB version-1.5 )
    2016/02/24 16.10.14.713 DEBUG [DeployThread: Configuring CA Service Management common tables] [InstallCDB] 02-24,16:10:14 Loading mdb...
    2016/02/24 16.10.14.714 DEBUG [DeployThread: Configuring CA Service Management common tables] [InstallCDB]                        using APM_CDB
    2016/02/24 16.10.15.860 DEBUG [DeployThread: Configuring CA Service Management common tables] [InstallCDB] 02-24,16:10:15 MDBTools install error=3
    2016/02/24 16.10.16.055 DEBUG [DeployThread: Configuring CA Service Management common tables] [InstallCDB] 02-24,16:10:16 Setupmdb exit /B return code=3
    2016/02/24 16.10.16.062 INFO  [DeployThread: Configuring CA Service Management common tables] [ActiveProcessHolder] Exit Monitor. Process ID (PID): 7428
    2016/02/24 16.10.16.062 DEBUG [DeployThread: Configuring CA Service Management common tables] [InstallCDB] Command terminated with error
    2016/02/24 16.10.16.063 DEBUG [DeployThread: Configuring CA Service Management common tables] [InstallCDB] Exit code of CDB script : 3
    2016/02/24 16.10.16.063 DEBUG [DeployThread: Configuring CA Service Management common tables] [ProgressPage] ProgressPage - Task Changed Configuring CA Service Management common tables
    2016/02/24 16.10.16.063 DEBUG [DeployThread: Configuring CA Service Management common tables] [ProgressPage] Task State Changed. TaskID: task.install_CDB,Configuring CA Service Management common tables, Old State: running, New State:failed
    2016/02/24 16.10.16.063 DEBUG [DeployThread: Configuring CA Service Management common tables] [ProgressPage] ProgressPage - Task Error.
    2016/02/24 16.10.16.064 DEBUG [DeployThread: Configuring CA Service Management common tables] [ProgressPage] Task Error. TaskID: task.install_CDB,Configuring CA Service Management common tables

     

     

     

    I'm inclined to believe that it's related to some policy that requires encrypted connections to the DB, but I haven't fully proved that out or determined what the offending policy may be.  What I do know is that installing 14.1 on a base WS2k12R2/SQL2012 configuration works fine for me in our pre-production domain, as does upgrading from 12.7 to 14.1 in our pre-production domain, but when I try upgrading from 12.7 to 14.1 using any server in our production domain, the upgrade fails with the above error.  I have not yet attempted a clean 14.1 install in our production domain, but I hope to do that later today.  I expect that it will fail with the same error.

     

    Also, It has been reported to me that CA is working on a fix for this, but I haven't seen the fix yet, so I'm also continuing to troubleshoot on our side until I have that fix in hand to test.



  • 9.  Re: CDB creation failed

    Posted 03-08-2016 01:25 PM

    So, the clean 14.1 install in our production domain failed with the same error.  After that, I ran the setup.exe from the products/SDM folder as Balram.Deswal recommended, and the install and config completed successfully.  So the bottom line is that while the original install doesn't work for us, there is a workaround that does work.



  • 10.  Re: CDB creation failed

    Posted 09-07-2016 07:34 AM

    In our customer installation we faced the same issue.

    The root cause was, that we used a remote SQL DB server with another previously existing MDB, where the mdb was just renamed within the SQL Management Studio to mdb_old. But it was not renamed in the filesystem!

    After we had renamed the mdb.mdf and the mdb_log.mdf in the filesystem, too (mdb_old.mdf and mdb_log_old.mdf) the error did not appear again.