FIX: The SQL Server 2005 Setup program may take a very long time to be completed (910070)
The information in this article applies to:
- Microsoft SQL Server 2005 Developer Edition
- Microsoft SQL Server 2005 Enterprise Edition
- Microsoft SQL Server 2005 Enterprise Edition for Itanium Based Systems
- Microsoft SQL Server 2005 Enterprise X64 Edition
- Microsoft SQL Server 2005 Express Edition
- Microsoft SQL Server 2005 Standard Edition
- Microsoft SQL Server 2005 Standard X64 Edition
- Microsoft SQL Server 2005 Workgroup
- SQL Server 2005 Standard Edition for Itanium-based Systems
Bug #: 20011453 (SQLBUDT)
SUMMARYThis article describes the following about this hotfix release: - The issues that are fixed by this hotfix package
- The prerequisites for installing the hotfix package
- Whether you must restart your computer after you install the hotfix package
- Whether you must make any registry changes
SYMPTOMSThe Microsoft SQL Server 2005 Setup program may take a very long time to be completed. Sometimes this time will be more than 24 hours. You may see in the detailed SQL Server Windows Installer log that most of the execution time occurs in the Write_sql XXX custom actions. These custom actions may include the following actions: - Write_sqlFileSDDL
- Write_sqlRegSDDL
- Write_sqlGroupMember
CAUSEWhen the primary domain has many external trust relationships with other domains or many lookups are performed at the same time, the time that is required to look up domain group names may increase significantly. Therefore, the time that is required to install SQL Server 2005 may increase.RESOLUTIONA supported hotfix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Only apply it to systems that are experiencing this specific problem. This hotfix may receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next version of SQL Server 2005 Service Pack that contains this hotfix. To resolve this problem immediately, contact Microsoft Product Support Services to obtain the hotfix. For a complete list of Microsoft Product Support Services telephone numbers and information about support costs, visit the following Microsoft Web site: Note In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question. Hotfix informationPrerequisitesThere are no prerequisites for this hotfix. Restart requirement
You do not have to restart the computer after you apply this hotfix.
Registry information
You do not have to change the registry after you apply this hotfix. WORKAROUNDTo work around this issue, you can use one of the following methods: Method 1Temporarily disable the network on the computer on which the SQL Server 2005 Setup program is running. To do this, either disconnect the network cable or type the following command at a command prompt: Note This workaround will not suceed when you are installing a SQL Server failover cluster.
Method 2Follow the steps that are listed in the following Microsoft Knowledge base article to restrict the lookup of isolated names in external trusted domains: 818024 How to restrict the lookup of isolated names in external trusted domains by using the LsaLookupRestrictIsolatedNameLevel registry entry
STATUSMicrosoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
Modification Type: | Major | Last Reviewed: | 6/6/2006 |
---|
Keywords: | kbsql2005sp1fix kbHotfixServer kbQFE kbsql2005setup kbtshoot kbprb KB910070 kbAudDeveloper kbAudITPRO |
---|
|