Search

Installer Account Selection crossed up after back/next by SQLCraftsman

Closed
as Not Reproducible Help for as Not Reproducible

1
0
Sign in
to vote
Type: Bug
ID: 765609
Opened: 10/1/2012 1:47:59 PM
Access Restriction: Public
0
Workaround(s)
0
User(s) can reproduce this bug
The list of services and services accounts can become corrupted, leading to a non-completable install experience.
Details (expand)

Product Language

English

Version

SQL Server 2012 - Enterprise Edition

Category

Setup

Operating System

Windows Server 2008 R2 Enterprise (SP1)

Operating System Language

US English

Steps to Reproduce

Run the GUI Installer for a stand-alone SQL Instance

Select SQL Server Engine with Replication and FTS, SSAS, SSRS, SSIS. Other shared tools are optional and do not affect the repro.

Continue with defaults until the Server Configuration - Service Accounts page. Select different accounts for each service.

Click "Back" until the Features Selection page.
Remove Reporting Services.
Advance again until the Server Configuration - Services Accounts page.
The account list is as before, but the services are different. The SQL Full-Text Filter Daemon Service now has the same account (NT Service\MsDtsServer110) as SSIS. Furthermore the account selection is greyed out and cannot be changed. Clicking next gives the error "The credentials you provided for the Full-Text service are invalid. To continue..."

Actual Results

Unable to complete setup without restarting

Expected Results

Services and accounts should line up and be correctable under all sequence conditions

Platform

X64

Virtualization

Hyper-V (On-Premise)
File Attachments
0 attachments
Sign in to post a comment.
Posted by Microsoft on 1/21/2013 at 10:07 AM
Hi SQLCraftsman, we were unable to reproduce this issue. If you can provide setup logs we can reopen the issue.

thanks,
[SQL Server Team]
Posted by Microsoft on 10/29/2012 at 3:31 PM
Hi SQLCraftsman, we were not able to reproduce this issue. In order to facilitate further investigation could you attach full setup logs to the connect item?

thanks,
[SQL Server Team]
Sign in to post a workaround.