CA Service Management

Expand all | Collapse all

SDM Migration v11.1 to v14.1: SQL migration/pdm cmd/swing box method

  • 1.  SDM Migration v11.1 to v14.1: SQL migration/pdm cmd/swing box method

    Posted Feb 15, 2017 06:52 AM

    Hello,

    We have an old working Unicenter server, version 11.1 and we need to migrate to version 14.1

     

    I installed a fresh v14.1 server, and now in process to migarte old contacts(created manually) and tickets information.

     

    I need your help, wich is best method to migrate old references to the new system:

    SQL migration: backup old database and export contents to the new database

    pdm export: using pdm_extract and load contacts, usp_contact and tickets to the new system

    Swing migration.

     

    Thanks in advance.



  • 2.  Re: SDM Migration v11.1 to v14.1: SQL migration/pdm cmd/swing box method

    Posted Feb 15, 2017 08:17 AM

    Swing migration is far the best method for me

    don't get why you opening a new post for it.

    We may have follow up on your existing one that is still open.... 

     

    my previous answer for swing box:

     

    Here is the link to CA support describing the process for a swing box approach.

    the doc refer to 12.7 but the method apply to higher version too.

    /J



  • 3.  Re: SDM Migration v11.1 to v14.1: SQL migration/pdm cmd/swing box method

    Posted Feb 15, 2017 09:30 AM

    Hello Jerome,

     

    Thank you very much for your feedback.

     

    Yes, I want to know if it's suitable for our case to use SQL export or pdm_extract commands.

     

    Thanks and best regards/



  • 4.  Re: SDM Migration v11.1 to v14.1: SQL migration/pdm cmd/swing box method

    Posted Feb 15, 2017 09:45 AM

    well this is really depend on what data you would like to migrate but knowing all the reference to foreign tables you will have to play with, this is a huge work to extract/load those data with high risk on the data integrity itself

    Therefore swinbox approach will a full upgrade on the mdb before to move to your new box is the less consuming and safer approach.

    my 2 cents

    /J



  • 5.  Re: SDM Migration v11.1 to v14.1: SQL migration/pdm cmd/swing box method

    Posted Feb 15, 2017 09:51 AM

    Hello Jerome,

    Thank you very much.

    I appreciate your feedback.

    Kind regards.



  • 6.  Re: SDM Migration v11.1 to v14.1: SQL migration/pdm cmd/swing box method

    Posted Feb 15, 2017 05:22 PM

    hassan.lagroubi

     

    I agree with jmayer.  The SWING BOX method is the most reliable method.

     

    In any case, be sure to review the Archive and Purge capabilities to trim as much from the MDB as possible.  I've had more issues with unsupported characters in ten year old documents/tickets that anything else.

     

    If you do decide to go with pdm_extract, be aware of the need to convert the exports to UTF-8 before cleaning/uploading the results.

     

    Regards,

     

    J.W.



  • 7.  Re: SDM Migration v11.1 to v14.1: SQL migration/pdm cmd/swing box method

    Broadcom Employee
    Posted Feb 20, 2017 10:48 AM

    Hassan.........

    Do you have any further questions regarding the upgrade process from CA SDM 11.1 to 14.1 using the Swing Box method?



  • 8.  Re: SDM Migration v11.1 to v14.1: SQL migration/pdm cmd/swing box method

    Posted Feb 27, 2017 11:02 AM

    Hello,

    I have an issue when I try to configure mdb SQL Server database, any valuable help:

    Error: the database server node is invalid. Please correct it and continue.

    Thanks in advance.SQL Server 2005 mdb connection error.



  • 9.  Re: SDM Migration v11.1 to v14.1: SQL migration/pdm cmd/swing box method

    Posted Feb 27, 2017 02:14 PM

    From what version of Service Desk is that screen capture and to what version of SQL Server are you trying to connect?



  • 10.  Re: SDM Migration v11.1 to v14.1: SQL migration/pdm cmd/swing box method

    Posted Mar 01, 2017 02:11 PM

    Hello Lindsay,

    Service Desk version is Uni_SD_r11_1

    SQL version is 2005

    regards.



  • 11.  Re: SDM Migration v11.1 to v14.1: SQL migration/pdm cmd/swing box method

    Posted Mar 01, 2017 05:37 PM

    In the r11.0 installer, access to the MSSQL database by the installer is by the Windows user with which you are logged in. That Windows login will need sysadmin right for the install. Only after the install is the MSSQL user "servicedesk" used by the application.



  • 12.  Re: SDM Migration v11.1 to v14.1: SQL migration/pdm cmd/swing box method

    Posted Feb 27, 2017 09:14 PM

    Hi Hassan,

    I presume this screen shot comes from the first stage in your swing box process - setting up a clone of your existing production USD 11.1 instance?  What did you enter as the database server node?  Here are some troubleshooting possibilities:

    • Is SQL 2005 client connectivity installed on your USD host? 
    • Can you ping that database server node from the USD host? 
    • Is port 1433 open between the USD host and the SQL server? 
    • Can you run the SQL command line on the USD host and log on to the SQL 2005 database, using the database server node, port and user credentials that you are specifying for USD? 

     

    If the answer to any of the last 4 questions is no then you need to get it to yes before USD will successfully configure.

    Hope that helps,

    Regards,

    James



  • 13.  Re: SDM Migration v11.1 to v14.1: SQL migration/pdm cmd/swing box method

    Posted Feb 28, 2017 12:28 PM

    Hello James,

    Thank you for your reply.

    I checked, SQL server 1433 is opened, I can access in using "servicedesk" login.

    I added "sqljdbc4" to classpath, but still I receive this error in joined file.

    Kind regards.SQL Server connectivity issue



  • 14.  Re: SDM Migration v11.1 to v14.1: SQL migration/pdm cmd/swing box method

    Posted Feb 28, 2017 08:55 PM

    Hi Hassan,

     

    I'm wondering if the Database Server Node text is correct.  'MSSQLSERVER' is the name usually assigned to the Default instance, but that specification 'SERVICEDESK\MSSQLSERVER' is for a Named instance.  If your MDB really is on the Default instance then you don't need to specify the instance name and just the server hostname (or IP address) should work.  If your MDB is actually on a Named instance called MSSQLSERVER (not a good name to choose as it is likely to cause confusion) then the port is almost certainly wrong as 1433 is usually reserved for the Default instance.  In the latter case you would need to ask your DBA to specify a static port for the Named instance (I'm not sure about SQL 2005 but in more recent versions of SQL the default is to use a dynamic port) and then specify that port instead of 1433.

     

    Hope that helps!

    Regards,

    James



  • 15.  Re: SDM Migration v11.1 to v14.1: SQL migration/pdm cmd/swing box method

    Posted Mar 01, 2017 12:52 PM

    Hi James,

    I have reinstalled SQL Server with a custom instance (because I tested before with default instance name), but I have the same issue.

    I used a DB test tool  to test connection with servicedesk account, I can access sql databse.

    For information, SQL server and Unidesk are installed in the same server.

     

    Regards.sql database test connection



  • 16.  Re: SDM Migration v11.1 to v14.1: SQL migration/pdm cmd/swing box method

    Posted Mar 03, 2017 12:26 PM

    Hello,

    I'm having the same issur, Unicenter Service Desk can't access in to SQL Server.

    This event log in Windows Event log:

    Login failed for user 'ServiceDesk'. [CLIENT: 10.78.78.90]

    Login failed for user 'servicedesksrv\ServiceDesk'. [CLIENT: 10.78.78.90]

     

    For informaiton, SDM and SQL are installed in the same server

     

    You will find after SQL capture logs:

    <Events>
    <Event id="65534" name="Trace Start">
    <Column id="14" name="StartTime">2017-03-03T08:54:45.353-08:00</Column>
    </Event>
    <Event id="17" name="ExistingConnection">
    <Column id="1" name="TextData">-- network protocol: LPC
    set quoted_identifier on
    set arithabort off
    set numeric_roundabort off
    set ansi_warnings on
    set ansi_padding on
    set ansi_nulls on
    set concat_null_yields_null on
    set cursor_close_on_commit off
    set implicit_transactions off
    set language us_english
    set dateformat mdy
    set datefirst 7
    set transaction isolation level read committed
    </Column>
    <Column id="9" name="ClientProcessID">3464</Column>
    <Column id="11" name="LoginName">SERVICEDESKSRV\servicedesk</Column>
    <Column id="6" name="NTUserName">servicedesk</Column>
    <Column id="10" name="ApplicationName">Microsoft SQL Server Management Studio</Column>
    <Column id="12" name="SPID">51</Column>
    <Column id="14" name="StartTime">2017-03-03T08:51:55.733-08:00</Column>
    </Event>
    <Event id="14" name="Audit Login">
    <Column id="1" name="TextData">-- network protocol: LPC
    set quoted_identifier on
    set arithabort off
    set numeric_roundabort off
    set ansi_warnings on
    set ansi_padding on
    set ansi_nulls on
    set concat_null_yields_null on
    set cursor_close_on_commit off
    set implicit_transactions off
    set language us_english
    set dateformat mdy
    set datefirst 7
    set transaction isolation level read committed
    </Column>
    <Column id="9" name="ClientProcessID">2792</Column>
    <Column id="11" name="LoginName">SERVICEDESKSRV\servicedesk</Column>
    <Column id="6" name="NTUserName">servicedesk</Column>
    <Column id="10" name="ApplicationName">OSQL-32</Column>
    <Column id="12" name="SPID">52</Column>
    <Column id="14" name="StartTime">2017-03-03T08:55:53.103-08:00</Column>
    </Event>
    <Event id="13" name="SQL:BatchStarting">
    <Column id="1" name="TextData"> set quoted_identifier off </Column>
    <Column id="9" name="ClientProcessID">2792</Column>
    <Column id="11" name="LoginName">SERVICEDESKSRV\servicedesk</Column>
    <Column id="6" name="NTUserName">servicedesk</Column>
    <Column id="10" name="ApplicationName">OSQL-32</Column>
    <Column id="12" name="SPID">52</Column>
    <Column id="14" name="StartTime">2017-03-03T08:55:53.103-08:00</Column>
    </Event>
    <Event id="12" name="SQL:BatchCompleted">
    <Column id="11" name="LoginName">SERVICEDESKSRV\servicedesk</Column>
    <Column id="15" name="EndTime">2017-03-03T08:55:53.103-08:00</Column>
    <Column id="6" name="NTUserName">servicedesk</Column>
    <Column id="10" name="ApplicationName">OSQL-32</Column>
    <Column id="12" name="SPID">52</Column>
    <Column id="14" name="StartTime">2017-03-03T08:55:53.103-08:00</Column>
    <Column id="16" name="Reads">0</Column>
    <Column id="18" name="CPU">0</Column>
    <Column id="1" name="TextData"> set quoted_identifier off </Column>
    <Column id="9" name="ClientProcessID">2792</Column>
    <Column id="13" name="Duration">148</Column>
    <Column id="17" name="Writes">0</Column>
    </Event>
    <Event id="13" name="SQL:BatchStarting">
    <Column id="1" name="TextData">-------------------------------------------------------------------------------
    -- Copyright (C) 2005 Computer Associates International, Inc
    -- as an unpublished work. This notice does not imply unrestricted or public
    -- access to these materials which are a trade secret of Computer Associates
    -- International or its subsidiaries or affiliates (together referred to as
    -- CA), and which may not be reproduced, used, sold or
    -- transferred to any third party without CA's prior written consent.
    --
    -- All Rights Reserved.
    --
    -- RESTRICTED RIGHTS LEGEND
    -- Use, duplication, or disclosure by the Government is subject to
    -- restrictions as set forth in subparagraph (c)(1)(ii) of the Rights in
    -- Technical Data and Computer Software clause at DFARS 252.227-7013.
    -------------------------------------------------------------------------------
    -- Verifies user has needed authorities
    --
    -- Returns 0 - OK
    -- 1 - One or more errors occurred during grants
    -------------------------------------------------------------------------------
    -- $Header: /base/source/java/configui/resources/LOC/en-US/.RCS/sql_check_user.sql,v 1.2.1.2 2005/12/14 23:41:34 chadu01 Exp $
    -------------------------------------------------------------------------------

    use master
    SET NOCOUNT ON
    </Column>
    <Column id="9" name="ClientProcessID">2792</Column>
    <Column id="11" name="LoginName">SERVICEDESKSRV\servicedesk</Column>
    <Column id="6" name="NTUserName">servicedesk</Column>
    <Column id="10" name="ApplicationName">OSQL-32</Column>
    <Column id="12" name="SPID">52</Column>
    <Column id="14" name="StartTime">2017-03-03T08:55:53.103-08:00</Column>
    </Event>
    <Event id="12" name="SQL:BatchCompleted">
    <Column id="11" name="LoginName">SERVICEDESKSRV\servicedesk</Column>
    <Column id="15" name="EndTime">2017-03-03T08:55:53.103-08:00</Column>
    <Column id="6" name="NTUserName">servicedesk</Column>
    <Column id="10" name="ApplicationName">OSQL-32</Column>
    <Column id="12" name="SPID">52</Column>
    <Column id="14" name="StartTime">2017-03-03T08:55:53.103-08:00</Column>
    <Column id="16" name="Reads">0</Column>
    <Column id="18" name="CPU">0</Column>
    <Column id="1" name="TextData">-------------------------------------------------------------------------------
    -- Copyright (C) 2005 Computer Associates International, Inc
    -- as an unpublished work. This notice does not imply unrestricted or public
    -- access to these materials which are a trade secret of Computer Associates
    -- International or its subsidiaries or affiliates (together referred to as
    -- CA), and which may not be reproduced, used, sold or
    -- transferred to any third party without CA's prior written consent.
    --
    -- All Rights Reserved.
    --
    -- RESTRICTED RIGHTS LEGEND
    -- Use, duplication, or disclosure by the Government is subject to
    -- restrictions as set forth in subparagraph (c)(1)(ii) of the Rights in
    -- Technical Data and Computer Software clause at DFARS 252.227-7013.
    -------------------------------------------------------------------------------
    -- Verifies user has needed authorities
    --
    -- Returns 0 - OK
    -- 1 - One or more errors occurred during grants
    -------------------------------------------------------------------------------
    -- $Header: /base/source/java/configui/resources/LOC/en-US/.RCS/sql_check_user.sql,v 1.2.1.2 2005/12/14 23:41:34 chadu01 Exp $
    -------------------------------------------------------------------------------

    use master
    SET NOCOUNT ON
    </Column>
    <Column id="9" name="ClientProcessID">2792</Column>
    <Column id="13" name="Duration">128</Column>
    <Column id="17" name="Writes">0</Column>
    </Event>
    <Event id="13" name="SQL:BatchStarting">
    <Column id="1" name="TextData">
    declare @retcd int
    set @retcd = 1

    -------------------------------------------------------------------------------
    -- Dump out version information for Support purposes
    -------------------------------------------------------------------------------

    select @@version

    -------------------------------------------------------------------------------
    -- First check to see if in sysadmin group
    -------------------------------------------------------------------------------
    IF IS_SRVROLEMEMBER ('sysadmin') = 1
    begin
    set @retcd = 0
    print 'Current user is a member of the sysadmin role'
    end
    ELSE IF IS_MEMBER ('db_owner') = 1
    begin
    set @retcd = 0
    print 'Current user is a member of the db_owner role'
    end

    -- It is OK to not replace this REPLACE because it is unlikely that
    -- anyone will have a role called No_role_check

    ELSE IF IS_MEMBER ('No_role_check') = 1
    begin
    set @retcd = 0
    print 'Current user is a member of the No_role_check role'
    end
    ELSE
    begin
    set @retcd = 1
    print 'Current user cannot create a database'
    end

    -------------------------------------------------------------------------------
    -- return an error code
    -------------------------------------------------------------------------------
    SELECT @retcd
    </Column>
    <Column id="9" name="ClientProcessID">2792</Column>
    <Column id="11" name="LoginName">SERVICEDESKSRV\servicedesk</Column>
    <Column id="6" name="NTUserName">servicedesk</Column>
    <Column id="10" name="ApplicationName">OSQL-32</Column>
    <Column id="12" name="SPID">52</Column>
    <Column id="14" name="StartTime">2017-03-03T08:55:53.12-08:00</Column>
    </Event>
    <Event id="12" name="SQL:BatchCompleted">
    <Column id="11" name="LoginName">SERVICEDESKSRV\servicedesk</Column>
    <Column id="15" name="EndTime">2017-03-03T08:55:53.12-08:00</Column>
    <Column id="6" name="NTUserName">servicedesk</Column>
    <Column id="10" name="ApplicationName">OSQL-32</Column>
    <Column id="12" name="SPID">52</Column>
    <Column id="14" name="StartTime">2017-03-03T08:55:53.12-08:00</Column>
    <Column id="16" name="Reads">0</Column>
    <Column id="18" name="CPU">0</Column>
    <Column id="1" name="TextData">
    declare @retcd int
    set @retcd = 1

    -------------------------------------------------------------------------------
    -- Dump out version information for Support purposes
    -------------------------------------------------------------------------------

    select @@version

    -------------------------------------------------------------------------------
    -- First check to see if in sysadmin group
    -------------------------------------------------------------------------------
    IF IS_SRVROLEMEMBER ('sysadmin') = 1
    begin
    set @retcd = 0
    print 'Current user is a member of the sysadmin role'
    end
    ELSE IF IS_MEMBER ('db_owner') = 1
    begin
    set @retcd = 0
    print 'Current user is a member of the db_owner role'
    end

    -- It is OK to not replace this REPLACE because it is unlikely that
    -- anyone will have a role called No_role_check

    ELSE IF IS_MEMBER ('No_role_check') = 1
    begin
    set @retcd = 0
    print 'Current user is a member of the No_role_check role'
    end
    ELSE
    begin
    set @retcd = 1
    print 'Current user cannot create a database'
    end

    -------------------------------------------------------------------------------
    -- return an error code
    -------------------------------------------------------------------------------
    SELECT @retcd
    </Column>
    <Column id="9" name="ClientProcessID">2792</Column>
    <Column id="13" name="Duration">1073</Column>
    <Column id="17" name="Writes">0</Column>
    </Event>
    <Event id="15" name="Audit Logout">
    <Column id="11" name="LoginName">SERVICEDESKSRV\servicedesk</Column>
    <Column id="15" name="EndTime">2017-03-03T08:55:53.133-08:00</Column>
    <Column id="6" name="NTUserName">servicedesk</Column>
    <Column id="10" name="ApplicationName">OSQL-32</Column>
    <Column id="12" name="SPID">52</Column>
    <Column id="14" name="StartTime">2017-03-03T08:55:53.103-08:00</Column>
    <Column id="16" name="Reads">0</Column>
    <Column id="18" name="CPU">0</Column>
    <Column id="9" name="ClientProcessID">2792</Column>
    <Column id="13" name="Duration">30000</Column>
    <Column id="17" name="Writes">0</Column>
    </Event>
    <Event id="13" name="SQL:BatchStarting">
    <Column id="1" name="TextData">SELECT
    'Server[@Name=' + quotename(CAST(serverproperty(N'Servername') AS sysname),'''') + ']' + '/Login[@Name=' + quotename(log.name,'''') + ']' AS [Urn],
    log.name AS [Name],
    CASE WHEN N'U' = log.type THEN 0 WHEN N'G' = log.type THEN 1 WHEN N'S' = log.type THEN 2 WHEN N'C' = log.type THEN 3 WHEN N'K' = log.type THEN 4 END AS [LoginType],
    log.is_disabled AS [IsDisabled],
    log.create_date AS [CreateDate]
    FROM
    sys.server_principals AS log
    WHERE
    (log.type in ('U', 'G', 'S', 'C', 'K') AND log.principal_id not between 101 and 255 AND log.name &lt;&gt; N'##MS_AgentSigningCertificate##')
    ORDER BY
    [Name] ASC</Column>
    <Column id="9" name="ClientProcessID">3464</Column>
    <Column id="11" name="LoginName">SERVICEDESKSRV\servicedesk</Column>
    <Column id="6" name="NTUserName">servicedesk</Column>
    <Column id="10" name="ApplicationName">Microsoft SQL Server Management Studio</Column>
    <Column id="12" name="SPID">51</Column>
    <Column id="14" name="StartTime">2017-03-03T08:56:39.92-08:00</Column>
    </Event>
    <Event id="12" name="SQL:BatchCompleted">
    <Column id="11" name="LoginName">SERVICEDESKSRV\servicedesk</Column>
    <Column id="15" name="EndTime">2017-03-03T08:56:39.933-08:00</Column>
    <Column id="6" name="NTUserName">servicedesk</Column>
    <Column id="10" name="ApplicationName">Microsoft SQL Server Management Studio</Column>
    <Column id="12" name="SPID">51</Column>
    <Column id="14" name="StartTime">2017-03-03T08:56:39.92-08:00</Column>
    <Column id="16" name="Reads">45</Column>
    <Column id="18" name="CPU">15</Column>
    <Column id="1" name="TextData">SELECT
    'Server[@Name=' + quotename(CAST(serverproperty(N'Servername') AS sysname),'''') + ']' + '/Login[@Name=' + quotename(log.name,'''') + ']' AS [Urn],
    log.name AS [Name],
    CASE WHEN N'U' = log.type THEN 0 WHEN N'G' = log.type THEN 1 WHEN N'S' = log.type THEN 2 WHEN N'C' = log.type THEN 3 WHEN N'K' = log.type THEN 4 END AS [LoginType],
    log.is_disabled AS [IsDisabled],
    log.create_date AS [CreateDate]
    FROM
    sys.server_principals AS log
    WHERE
    (log.type in ('U', 'G', 'S', 'C', 'K') AND log.principal_id not between 101 and 255 AND log.name &lt;&gt; N'##MS_AgentSigningCertificate##')
    ORDER BY
    [Name] ASC</Column>
    <Column id="9" name="ClientProcessID">3464</Column>
    <Column id="13" name="Duration">11759</Column>
    <Column id="17" name="Writes">0</Column>
    </Event>
    <Event id="13" name="SQL:BatchStarting">
    <Column id="1" name="TextData">use [master]</Column>
    <Column id="9" name="ClientProcessID">3464</Column>
    <Column id="11" name="LoginName">SERVICEDESKSRV\servicedesk</Column>
    <Column id="6" name="NTUserName">servicedesk</Column>
    <Column id="10" name="ApplicationName">Microsoft SQL Server Management Studio</Column>
    <Column id="12" name="SPID">51</Column>
    <Column id="14" name="StartTime">2017-03-03T08:56:39.933-08:00</Column>
    </Event>
    <Event id="12" name="SQL:BatchCompleted">
    <Column id="11" name="LoginName">SERVICEDESKSRV\servicedesk</Column>
    <Column id="15" name="EndTime">2017-03-03T08:56:39.933-08:00</Column>
    <Column id="6" name="NTUserName">servicedesk</Column>
    <Column id="10" name="ApplicationName">Microsoft SQL Server Management Studio</Column>
    <Column id="12" name="SPID">51</Column>
    <Column id="14" name="StartTime">2017-03-03T08:56:39.933-08:00</Column>
    <Column id="16" name="Reads">0</Column>
    <Column id="18" name="CPU">0</Column>
    <Column id="1" name="TextData">use [master]</Column>
    <Column id="9" name="ClientProcessID">3464</Column>
    <Column id="13" name="Duration">217</Column>
    <Column id="17" name="Writes">0</Column>
    </Event>
    <Event id="14" name="Audit Login">
    <Column id="1" name="TextData">-- network protocol: LPC
    set quoted_identifier on
    set arithabort off
    set numeric_roundabort off
    set ansi_warnings on
    set ansi_padding on
    set ansi_nulls on
    set concat_null_yields_null on
    set cursor_close_on_commit off
    set implicit_transactions off
    set language us_english
    set dateformat mdy
    set datefirst 7
    set transaction isolation level read committed
    </Column>
    <Column id="9" name="ClientProcessID">3464</Column>
    <Column id="11" name="LoginName">SERVICEDESKSRV\servicedesk</Column>
    <Column id="6" name="NTUserName">servicedesk</Column>
    <Column id="10" name="ApplicationName">Microsoft SQL Server Management Studio</Column>
    <Column id="12" name="SPID">52</Column>
    <Column id="14" name="StartTime">2017-03-03T08:56:41.527-08:00</Column>
    </Event>
    <Event id="13" name="SQL:BatchStarting">
    <Column id="1" name="TextData">SET LOCK_TIMEOUT 10000</Column>
    <Column id="9" name="ClientProcessID">3464</Column>
    <Column id="11" name="LoginName">SERVICEDESKSRV\servicedesk</Column>
    <Column id="6" name="NTUserName">servicedesk</Column>
    <Column id="10" name="ApplicationName">Microsoft SQL Server Management Studio</Column>
    <Column id="12" name="SPID">52</Column>
    <Column id="14" name="StartTime">2017-03-03T08:56:41.527-08:00</Column>
    </Event>
    <Event id="12" name="SQL:BatchCompleted">
    <Column id="11" name="LoginName">SERVICEDESKSRV\servicedesk</Column>
    <Column id="15" name="EndTime">2017-03-03T08:56:41.527-08:00</Column>
    <Column id="6" name="NTUserName">servicedesk</Column>
    <Column id="10" name="ApplicationName">Microsoft SQL Server Management Studio</Column>
    <Column id="12" name="SPID">52</Column>
    <Column id="14" name="StartTime">2017-03-03T08:56:41.527-08:00</Column>
    <Column id="16" name="Reads">0</Column>
    <Column id="18" name="CPU">0</Column>
    <Column id="1" name="TextData">SET LOCK_TIMEOUT 10000</Column>
    <Column id="9" name="ClientProcessID">3464</Column>
    <Column id="13" name="Duration">75</Column>
    <Column id="17" name="Writes">0</Column>
    </Event>
    <Event id="13" name="SQL:BatchStarting">
    <Column id="1" name="TextData">SELECT
    log.name AS [Name]
    FROM
    sys.server_principals AS log
    WHERE
    (log.type in ('U', 'G', 'S', 'C', 'K') AND log.principal_id not between 101 and 255 AND log.name &lt;&gt; N'##MS_AgentSigningCertificate##')and(log.name=N'SERVICEDESKSRV\servicedesk')</Column>
    <Column id="9" name="ClientProcessID">3464</Column>
    <Column id="11" name="LoginName">SERVICEDESKSRV\servicedesk</Column>
    <Column id="6" name="NTUserName">servicedesk</Column>
    <Column id="10" name="ApplicationName">Microsoft SQL Server Management Studio</Column>
    <Column id="12" name="SPID">52</Column>
    <Column id="14" name="StartTime">2017-03-03T08:56:41.527-08:00</Column>
    </Event>
    <Event id="12" name="SQL:BatchCompleted">
    <Column id="11" name="LoginName">SERVICEDESKSRV\servicedesk</Column>
    <Column id="15" name="EndTime">2017-03-03T08:56:41.527-08:00</Column>
    <Column id="6" name="NTUserName">servicedesk</Column>
    <Column id="10" name="ApplicationName">Microsoft SQL Server Management Studio</Column>
    <Column id="12" name="SPID">52</Column>
    <Column id="14" name="StartTime">2017-03-03T08:56:41.527-08:00</Column>
    <Column id="16" name="Reads">10</Column>
    <Column id="18" name="CPU">0</Column>
    <Column id="1" name="TextData">SELECT
    log.name AS [Name]
    FROM
    sys.server_principals AS log
    WHERE
    (log.type in ('U', 'G', 'S', 'C', 'K') AND log.principal_id not between 101 and 255 AND log.name &lt;&gt; N'##MS_AgentSigningCertificate##')and(log.name=N'SERVICEDESKSRV\servicedesk')</Column>
    <Column id="9" name="ClientProcessID">3464</Column>
    <Column id="13" name="Duration">5969</Column>
    <Column id="17" name="Writes">0</Column>
    </Event>
    <Event id="13" name="SQL:BatchStarting">
    <Column id="1" name="TextData">SELECT
    dtb.collation_name AS [Collation],
    dtb.name AS [DatabaseName2]
    FROM
    master.sys.databases AS dtb
    WHERE
    (dtb.name=N'master')</Column>
    <Column id="9" name="ClientProcessID">3464</Column>
    <Column id="11" name="LoginName">SERVICEDESKSRV\servicedesk</Column>
    <Column id="6" name="NTUserName">servicedesk</Column>
    <Column id="10" name="ApplicationName">Microsoft SQL Server Management Studio</Column>
    <Column id="12" name="SPID">52</Column>
    <Column id="14" name="StartTime">2017-03-03T08:56:41.54-08:00</Column>
    </Event>
    <Event id="12" name="SQL:BatchCompleted">
    <Column id="11" name="LoginName">SERVICEDESKSRV\servicedesk</Column>
    <Column id="15" name="EndTime">2017-03-03T08:56:41.557-08:00</Column>
    <Column id="6" name="NTUserName">servicedesk</Column>
    <Column id="10" name="ApplicationName">Microsoft SQL Server Management Studio</Column>
    <Column id="12" name="SPID">52</Column>
    <Column id="14" name="StartTime">2017-03-03T08:56:41.54-08:00</Column>
    <Column id="16" name="Reads">9</Column>
    <Column id="18" name="CPU">16</Column>
    <Column id="1" name="TextData">SELECT
    dtb.collation_name AS [Collation],
    dtb.name AS [DatabaseName2]
    FROM
    master.sys.databases AS dtb
    WHERE
    (dtb.name=N'master')</Column>
    <Column id="9" name="ClientProcessID">3464</Column>
    <Column id="13" name="Duration">12220</Column>
    <Column id="17" name="Writes">0</Column>
    </Event>
    <Event id="13" name="SQL:BatchStarting">
    <Column id="1" name="TextData">select SERVERPROPERTY(N'servername')</Column>
    <Column id="9" name="ClientProcessID">3464</Column>
    <Column id="11" name="LoginName">SERVICEDESKSRV\servicedesk</Column>
    <Column id="6" name="NTUserName">servicedesk</Column>
    <Column id="10" name="ApplicationName">Microsoft SQL Server Management Studio</Column>
    <Column id="12" name="SPID">52</Column>
    <Column id="14" name="StartTime">2017-03-03T08:56:41.573-08:00</Column>
    </Event>
    <Event id="12" name="SQL:BatchCompleted">
    <Column id="11" name="LoginName">SERVICEDESKSRV\servicedesk</Column>
    <Column id="15" name="EndTime">2017-03-03T08:56:41.573-08:00</Column>
    <Column id="6" name="NTUserName">servicedesk</Column>
    <Column id="10" name="ApplicationName">Microsoft SQL Server Management Studio</Column>
    <Column id="12" name="SPID">52</Column>
    <Column id="14" name="StartTime">2017-03-03T08:56:41.573-08:00</Column>
    <Column id="16" name="Reads">0</Column>
    <Column id="18" name="CPU">0</Column>
    <Column id="1" name="TextData">select SERVERPROPERTY(N'servername')</Column>
    <Column id="9" name="ClientProcessID">3464</Column>
    <Column id="13" name="Duration">259</Column>
    <Column id="17" name="Writes">0</Column>
    </Event>
    <Event id="13" name="SQL:BatchStarting">
    <Column id="1" name="TextData">SELECT

    Thanks for your help.

     

    Regards.



  • 17.  Re: SDM Migration v11.1 to v14.1: SQL migration/pdm cmd/swing box method

    Posted Mar 03, 2017 03:13 PM

    Please answer the following questions:

    1. What is the Windows login ID you are using to run the Installer (in other words who are you logged in as)?
    2. Is that user a member of the local Administrators group on the Windows server?
    3. Have you created a login in the SQL server for that Windows login ID?
    4. Have you given that user sysadmin rights in the SQL server?

    If you would like some assistance getting this done please email me at Lindsay@iteduconsultants.com



  • 18.  Re: SDM Migration v11.1 to v14.1: SQL migration/pdm cmd/swing box method

    Posted Mar 06, 2017 06:07 AM

    Hello Lindsay,

    Thank for your feedback.

    Here after, the answers for your questions:

    • What is the Windows login ID you are using to run the Installer (in other words who are you logged in as)?

    Windows login ID is "servicedesk", this account has admin rights (memebers of local admin administrators group), installation is executed when loggin with this login;

    • Is that user a member of the local Administrators group on the Windows server?

    yes, this account is an admin account

    • Have you created a login in the SQL server for that Windows login ID?

    I created an SQL account for this Windows account, also SQL Auth is mixt (windows+sql)

    • Have you given that user sysadmin rights in the SQL server?

    Yes, the account "servicedesk" is an 'sa' account, having rights sysadmin and dbcreator and all rights.

    Thanks and kind regards.

    Youssef.



  • 19.  Re: SDM Migration v11.1 to v14.1: SQL migration/pdm cmd/swing box method

    Posted Mar 06, 2017 03:17 PM

    Hi Youssef,

     

    Something we are not seeing here but I cannot determine what it is yet. It appears that:

    • You have installed the database (mdb) successfully
    • You have installed the Service Desk application
    • But the configuration is failing when trying to connect to the database.

    If you want, please send me an email with your contact information and I can set up a Webex session to screen share and walk through the issue with you.

     

    Cheers,

    Lindsay



  • 20.  Re: SDM Migration v11.1 to v14.1: SQL migration/pdm cmd/swing box method

    Posted Mar 07, 2017 01:25 PM

    Hi Youssef,

     

    Now that you have r11.1 installed, I think you only have to upgrade to r11.2 before you can upgrade to r14.1. According to the documentation, you can upgrade Service Desk from r11.2 to r14.1 without going to any other intermediate release.

     

    Cheers,

    Lindsay