Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

ADFS 2.1 SQL farm deployment fails if you do not have SQL permissions


View products that this article applies to.

Symptoms

Consider the following scenario:
  • You deploy an ADFS 2.1 SQL farm in which there is a role separation between the domain admin and the ADFS admin.
  • You run fsconfig GenerateSQLScripts by using the SQL admin account to give the ADFS service account permission to change the database.
  • You perform CreateSQLFarm actions on the ADFS server by using the domain admin account.
In this situation, configuration of the AD FS VSS Express Writer fails. Therefore, the deployment of the SQL farm fails when the domain admin has no access to the SQL server.

↑ Back to the top


Cause

This issue occurs because the domain admin account is used to perform database query instead of the ADFS admin account.

↑ Back to the top


Resolution

Hotfix information

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem.

If the hotfix is available for download, there is a "Hotfix Download Available" section at the top of this Knowledge Base article. If this section does not appear, submit a request to Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft website: Note The "Hotfix Download Available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.

Prerequisites

To apply this hotfix, you must be running Windows Server 2012.

Registry information

To use the hotfix in this package, you do not have to make any changes to the registry.

Restart requirement

You must restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace a previously released hotfix.
File information
The global version of this hotfix installs files that have the attributes that are listed in the following tables. The dates and the times for these files are listed in Coordinated Universal Time (UTC). The dates and the times for these files on your local computer are displayed in your local time together with your current daylight saving time (DST) bias. Additionally, the dates and the times may change when you perform certain operations on the files.





Windows Server 2012 file information notes
  • The files that apply to a specific product, milestone (RTM, SPn), and service branch (LDR, GDR) can be identified by examining the file version numbers as shown in the following table:

    VersionProductMilestoneService branch
    6.2.920 0.20xxxWindows Server 2012RTMLDR
  • The MANIFEST files (.manifest) and the MUM files (.mum) that are installed for each environment are listed separately in the "Additional file information for Windows Server 2012" section. MUM, MANIFEST, and the associated security catalog (.cat) files, are very important to maintain the state of the updated components. The security catalog files, for which the attributes are not listed, are signed with a Microsoft digital signature.
For all supported x64-based versions of Windows Server 2012
File nameFile versionFile sizeDateTimePlatform
Microsoft.identityserver.ui.shared.dll6.2.9200.209211,638,91217-Jan-201402:44x86

↑ Back to the top


Workaround

To work around this issue, you can grant ADFS admin with SQL admin permission.

↑ Back to the top


Status

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

↑ Back to the top


More Information

For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:
824684 Description of the standard terminology that is used to describe Microsoft software updates
Additional file information

Additional file information for Windows Server 2012

Additional files for all supported x64-based versions of Windows Server 2012
File propertyValue
File nameAmd64_e7d27a7d4829506bd0dfefa008f78980_31bf3856ad364e35_6.2.9200.20921_none_bb5600a0363ae129.manifest
File versionNot applicable
File size707
Date (UTC)17-Jan-2014
Time (UTC)16:35
PlatformNot applicable
File nameMsil_microsoft.identityserver.ui.shared_31bf3856ad364e35_6.2.9200.20921_none_e624fbd3e68f653b.manifest
File versionNot applicable
File size3,341
Date (UTC)17-Jan-2014
Time (UTC)02:51
PlatformNot applicable
File namePackage_1_for_kb2926658~31bf3856ad364e35~amd64~~6.2.1.0.mum
File versionNot applicable
File size2,037
Date (UTC)17-Jan-2014
Time (UTC)16:35
PlatformNot applicable
File namePackage_for_kb2926658_rtm~31bf3856ad364e35~amd64~~6.2.1.0.mum
File versionNot applicable
File size1,668
Date (UTC)17-Jan-2014
Time (UTC)16:35
PlatformNot applicable

↑ Back to the top


Keywords: kb, kbautohotfix, kbqfe, kbhotfixserver, kbfix, kbsurveynew, kbexpertiseadvanced

↑ Back to the top

Article Info
Article ID : 2926658
Revision : 1
Created on : 1/7/2017
Published on : 10/24/2014
Exists online : False
Views : 140