Article ID: 951266 - Last Review: April 3, 2008 - Revision: 1.0
Error 25070 on setup
Source: Microsoft Support
RAPID PUBLISHING
RAPID PUBLISHING ARTICLES PROVIDE INFORMATION DIRECTLY FROM WITHIN THE MICROSOFT SUPPORT ORGANIZATION. THE INFORMATION CONTAINED HEREIN IS CREATED IN RESPONSE TO EMERGING OR UNIQUE TOPICS, OR IS INTENDED SUPPLEMENT OTHER KNOWLEDGE BASE INFORMATION.
Action
When installing an upgrade patch, or running change mode setup from the Control Panel for MIIS or ILM or IIFP, the installation process stops and returns the error:
Error 25070. Error connecting to database. MicrosoftIdentityIntegrationServer.
<hr=0x8000405>
Error 25070. Error connecting to database. MicrosoftIdentityIntegrationServer.
<hr=0x8000405>
Cause
This error occurs when the setup process cannot connect to the MIIS database.
Resolution
To resolve this problem, you must be able to establish connectivity to the MIIS database. A good way of testing this is to create a UDL file (see http://support.microsoft.com/kb/244659
(http://support.microsoft.com/kb/244659)
for details)
The Provider should be the Microsoft OLE DB Provider for SQL Server.
The data for the Server and database fields can be found in the following registry key:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\miiserver\Parameters
If the database is local and the default SQL instance then the server field in the UDL can be left empty.
The Provider should be the Microsoft OLE DB Provider for SQL Server.
The data for the Server and database fields can be found in the following registry key:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\miiserver\Parameters
If the database is local and the default SQL instance then the server field in the UDL can be left empty.
More Information
In one case, this error occured because the user had changed the SQL port after installing the database, but anything that is preventing SQL connectivity can also cause this error.
DISCLAIMER
MICROSOFT AND/OR ITS SUPPLIERS MAKE NO REPRESENTATIONS OR WARRANTIES ABOUT THE SUITABILITY, RELIABILITY OR ACCURACY OF THE INFORMATION CONTAINED IN THE DOCUMENTS AND RELATED GRAPHICS PUBLISHED ON THIS WEBSITE (THE “MATERIALS”) FOR ANY PURPOSE. THE MATERIALS MAY INCLUDE TECHNICAL INACCURACIES OR TYPOGRAPHICAL ERRORS AND MAY BE REVISED AT ANY TIME WITHOUT NOTICE.
TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, MICROSOFT AND/OR ITS SUPPLIERS DISCLAIM AND EXCLUDE ALL REPRESENTATIONS, WARRANTIES, AND CONDITIONS WHETHER EXPRESS, IMPLIED OR STATUTORY, INCLUDING BUT NOT LIMITED TO REPRESENTATIONS, WARRANTIES, OR CONDITIONS OF TITLE, NON INFRINGEMENT, SATISFACTORY CONDITION OR QUALITY, MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE, WITH RESPECT TO THE MATERIALS.
TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, MICROSOFT AND/OR ITS SUPPLIERS DISCLAIM AND EXCLUDE ALL REPRESENTATIONS, WARRANTIES, AND CONDITIONS WHETHER EXPRESS, IMPLIED OR STATUTORY, INCLUDING BUT NOT LIMITED TO REPRESENTATIONS, WARRANTIES, OR CONDITIONS OF TITLE, NON INFRINGEMENT, SATISFACTORY CONDITION OR QUALITY, MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE, WITH RESPECT TO THE MATERIALS.
APPLIES TO
- Identity Integration Feature Pack 1a for Microsoft Windows Server Active Directory
- Identity Integration Feature Pack for Microsoft Windows Server Active Directory
- Identity Integration Feature Pack for Microsoft Windows Server Active Directory with Service Pack 2
- Microsoft Identity Integration Server 2003 Enterprise Edition
- Microsoft Identity Integration Server 2003 Service Pack 2
- Microsoft Identity Lifecycle Manager 2007
Note: This article is from Microsoft Knowledage Base
Related problems posted by other users | |
| more... |

