How can we help you today? How can we help you today?

SQL Change Automation Tool Upgrade errors

Hi Team,

 

I have recently upgraded the ReadyRoll Projects in my VS2017 solution to SQL Change Automation. I’m facing below issues.

 Visual Studio Version : Microsoft Professional VS 2017 15.8.7

Upgraded ReadyRoll Version : SQL Change Automation 3  version: 3.0.18291.2122

  After updating the ReadyRoll Version we are unable to connect to servers (localdb)\ProjectsV13 or (localdb)\MSSQLLocalDB  in SQL Change Automation window.

 Sqlcmd: Error: Microsoft ODBC Driver 13 for SQL Server : Login timeout expired. Sqlcmd: Error: Microsoft ODBC Driver 13 for SQL Server : A network-related or instance-specific error has occurred while establishing a connection to SQL Server. Server is not found or not accessible. Check if instance name is correct and if SQL Server is configured to allow remote connections. For more information see SQL Server Books Online.. Done building project "ProTransact.SQLAutomation.sqlproj" -- FAILED.

 But when I connected to <Machine>/SQLEXPRESS2012 its working fine.

 As all our developers are using localdb)\ProjectsV13 for development  purpose I need to resolve this as early as possible. Tried multiple options but no luck.

 

Can anyone please reply us why I’m getting this error even though I upgraded to new ReadyRoll version.

 

Sai
0

Comments

7 comments

Sort by
  • PeterG
    Hi Sai,

    There shouldn't be a problem with connecting to localdb, to help diagnose further could you contact support@red-gate.com with following information:

    Version you upgraded from: 
    Version you upgraded to: 3.0.18291.2122
    Visual Studio version:     15.8.7
    SQLCmd version:

    And the logs from     %LOCALAPPDATA%\Red Gate\Logs\SQL Change Automation\VS

    Also are you able to connect to (localdb)\ProjectsV13 from the visual studio server explorer?
    PeterG
    0
  • Sai

    Hi Peter,

    To my surprise I'm not able to connect to (localdb)\ProjectsV13 from the visual studio server explorer. Is that some issue..please let me know.

    thanks,

    Archana

    Sai
    0
  • PeterG
    Probably means the instance is corrupt or something. You might want to recreate it using the command line: https://docs.microsoft.com/en-us/sql/relational-databases/express-localdb-instance-apis/command-line-management-tool-sqllocaldb-exe?view=sql-server-2017

    sqllocaldb.exe stop ProjectsV13
sqllocaldb.exe delete ProjectsV13
sqllocaldb.exe create ProjectsV13<br>sqllocaldb.exe start ProjectsV13

    This will force recreate the ProjectsV13 instance on localdb
    PeterG
    0
  • Sai

    Hi Peter,

    Thanks for your instant replies. Really appreciate it.

    I tried the above option of recreating the ProjectsV13 instance, but still its not working. :(

    Please let me know what could be the root cause.


    Thanks,

    Sai
    0
  • Sai
    Please find my SQL Change Automation-VS.log file attached
    Sai
    0
  • PeterG
    Can you try running
    sqlcmd -S "(localdb)\mssqllocaldb"
    and if that fails you can try the fix in https://stackoverflow.com/a/44640176
    PeterG
    0
  • Sai

    Thank you so much for your responses...It helped me a lot.. After downloading the ODBC Driver 13.1 for SQL Server the issue got resolved....Thanks a lot Peter :)

    Sai
    0

Add comment

Please sign in to leave a comment.