Install 2nd instance of SQL Server 2005 on Windows Server 2008 cluster

  • Hi,

    I'm having trouble installing a second named instance of SQL Server 2005 on a 5 node Windows Server 2008 failover cluster. For some reason my installation account doesn't have permissions to start the setup on the remote nodes.

    I get the error "Setup failed to start on the remote machine. Check the Task Scheduler event log on the remote machine. "

    I already found an article to make sure my Task Scheduler is started and all my RDP sessions are removed from all my nodes. I even restarted the servers several times. But I keep getting the same error.

    The installation account is not a domain administrator, but local administrator on all nodes (I'm not in control of the account I install with).

    Anybody an idea in which direction I should search next?

    Cheers,

    Peter

  • you are using a windows domain account, right ?

    Johan

    Learn to play, play to learn !

    Dont drive faster than your guardian angel can fly ...
    but keeping both feet on the ground wont get you anywhere :w00t:

    - How to post Performance Problems
    - How to post data/code to get the best help[/url]

    - How to prevent a sore throat after hours of presenting ppt

    press F1 for solution, press shift+F1 for urgent solution 😀

    Need a bit of Powershell? How about this

    Who am I ? Sometimes this is me but most of the time this is me

  • Peter,

    is this policy setting disabled: Network access: Do not allow storage of credentials or .NET Passports for network authentication

    KEY: HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Lsa

    VALUE: disabledomaincreds

    SETTING: 1

    This should be: “0”

    HTH

    Robbert 😉

  • Thx for your reply...

    I'm using a domain user account to install the 2nd named instance.

    The security setting Robbert mentioned is set to disabled (we encountered that setting in an earlier attempt to install SQL Server 2005 on a Windows Server 2008 failover cluster).

  • It turns out that the installation account needed extra user rights permissions on top of the local administrators permissions:

    The extra permissions are:

    * Act as part of the operating system

    * Replace a process-level token

    After this the issue was resolved.

  • Thank you for the feedback.

    It does indeed ring a bell, but far far away 😉

    Johan

    Learn to play, play to learn !

    Dont drive faster than your guardian angel can fly ...
    but keeping both feet on the ground wont get you anywhere :w00t:

    - How to post Performance Problems
    - How to post data/code to get the best help[/url]

    - How to prevent a sore throat after hours of presenting ppt

    press F1 for solution, press shift+F1 for urgent solution 😀

    Need a bit of Powershell? How about this

    Who am I ? Sometimes this is me but most of the time this is me

Viewing 6 posts - 1 through 5 (of 5 total)

You must be logged in to reply to this topic. Login to reply