Copied to clipboard

Flag this post as spam?

This post will be reported to the moderators as potential spam to be looked at


  • Paul de Quant 403 posts 1521 karma points
    Aug 01, 2016 @ 16:06
    Paul de Quant
    0

    Installing Umbraco to specific SQL Server Instance

    Hello,

    I'm trying to install a clean Umbraco install to a specific instance on SQL Server - i.e. SERVERNAME\INSTANCE

    No matter what options I select in the Configure your database section of the install - it always states that it 'Could not connect to database'

    The strange thing is, I've got SQL Server Management Studio installed on the same server as the website and using the exact same connection details and it works fine.

    Does Umbraco have a problem installing to specific SQL instances (rather that the default one).

    Can anyone help me?

    Cheers

    Paul

  • Carson Brown 15 posts 85 karma points
    Aug 01, 2016 @ 18:29
    Carson Brown
    0

    Hello Paul, I found useful this link useful. Hopefully it helps

  • Paul de Quant 403 posts 1521 karma points
    Aug 03, 2016 @ 07:52
    Paul de Quant
    0

    Hi,

    Thanks for the reply, I'm afraid this didn't work for me. I'm not sure if it's because it's a SQL instance other than the default one and SQL has had it's default port 1433 changed to something else.

    I wish there was a log I could look at to find out the reason as to why it can't connect.

    Thanks

    Paul

  • Amir Khan 1289 posts 2746 karma points
    Aug 03, 2016 @ 18:56
    Amir Khan
    0

    Hi Paul, have you tried connecting to the DB from Management Studio from a different machine than the one the database is installed on?

    -Amir

  • Josh Yates 6 posts 86 karma points
    Aug 03, 2016 @ 19:49
    Josh Yates
    0

    Make sure your SQLSERVERAGENT service is started.

    Are you using Windows Authentication?

    Double check your instance name.

  • Paul de Quant 403 posts 1521 karma points
    Aug 04, 2016 @ 06:49
    Paul de Quant
    100

    I finally worked out what it was - turns out the password had a semi-colon in it, which I completely missed. Wrapping the password in quotes and specifying it as a custom connection string did the trick.

    Thanks for the suggestions though.

    Cheers

    Paul

  • This forum is in read-only mode while we transition to the new forum.

    You can continue this topic on the new forum by tapping the "Continue discussion" link below.

Please Sign in or register to post replies