Article ID: 936892 - View products that this article applies to.
On a server that is running Windows Server 2003, you upgrade from Microsoft SQL Server 2000 to Microsoft SQL Server 2005. However, an access violation occurs during the startup of the SQL Server service. Additionally, the following error message is logged in the SQL Server Errorlog file:
Messages that resemble the following are logged in the SQLSetup0005_ServerName_SQL.log file:
DateTime spid4s * Exception Address = 78144D3A Module(MSVCR80+00014D3A)
DateTime spid4s * Exception Code = c0000005 EXCEPTION_ACCESS_VIOLATION
DateTime spid4s * Access Violation occurred reading address 00000006
Unable to update password policy
This problem occurs when SQL Server 2005 is trying to recover the resource database.
Service MSSQL$InstanceName with parameters '-m SqlSetup -r -T4022 -T4010' is being started at DateTime
MSI (s) (80:A4) [12:46:36:153]: Running as a service.
Failed to start service MSSQL$InstanceName. Error code 17185
Service failed unexpectedly (17185)
Error Code: 0x80074321 (17185)
Windows Error Text: Source File Name: sqlsetuplib\service.cpp
Compiler Timestamp: DateTime
Function Name: sqls::Service::Start
Source Line Number: 301
This problem occurs if the following conditions are true:
To work around this problem, use one of the following methods.
Note We recommend that you use Method 1. Use Method 2 only as a temporary workaround for migration purposes.
Method 1: Update the password of the SQL Server login to comply with the password policy in Windows Server 2003Note You may not know the specific SQL Server login whose password does not comply with the password policy. In this case, you must repeat step 1 through step 4 to examine each SQL Server login until you find the problematic SQL Server login.
Method 2: Disable the password policy enforcement feature for the SQL Server loginNote Use Method 2 only as a temporary workaround for migration purposes until you update the password.
Important These steps may increase your security risk. These steps may also make the computer or the network more vulnerable to attack by malicious users or by malicious software such as viruses. We recommend the process that this article describes to enable programs to operate as they are designed to or to implement specific program capabilities. Before you make these changes, we recommend that you evaluate the risks that are associated with implementing this process in your particular environment. If you decide to implement this process, take any appropriate additional steps to help protect the system. We recommend that you use this process only if you really require this process.
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
Article ID: 936892 - Last Review: October 26, 2007 - Revision: 1.1