SQL Server 7.0 Acmsetup.exe setup application fails (305680)
The information in this article applies to:
This article was previously published under Q305680 SYMPTOMS
When the Configuring Server portion of a SQL Server 7.0 installation is in progress, this series of error messages may appear:
{acmsetup.EXE - Application Error
The application failed to initialize properly (0xc0000006). Click on OK to terminate the application.}
Followed by:
sqlservr.exe - Unable To Locate DLL
The dynamic link library MSWSTR10.DLL could not be found in the specified path:
d:\MSSQL7\binn;C:\WINNT;C:\WINNT\system32
Followed by:
Setup
Setup failed to configure the server. Refer to the server error logs and cnfgsvr.out for more information.
If you run just the Mdac_typ.exe executable file that is located in the x86\Other folder of the SQL Server 7.0 CD, you may see:
- This error message:
acmsetup.EXE - Application Error
The application failed to initialize properly (0xc0000006). Click on OK to terminate the application.
- An entry similar to this in the Cnfgsvr.out file:
Starting Service...
An error occurred while attempting to start the service (1053)
SQL Server Configuration failed.
- An entry similar to this in the Sqlstp.log file:
08:56:46 Path successfully updated.
08:56:46 %SystemRoot%\system32;%SystemRoot%;D:\MSSQL7\BINN 08:56:46 D:\MSSQL7\binn\cnfgsvr.exe -Silent 2 -NoSampleDB 0 -SQLPath
"D:\MSSQL7\" -SQLDataPath "E:\MSSQL7\" -SortID 52 -LCIDCompStyle "1033-196609" -HWND 27001094 -User sa -Pwd
08:58:58 Process Exit Code: (-1)
08:59:00 Setup failed to configure the server. Refer to the server error logs and cnfgsvr.out for more information.
08:59:00 Action CleanUpInstall:
08:59:00 C:\TEMP\_ISTMP10.DIR\scm.exe -Silent 1 -Action 4 -Service SQLServerAgent
08:59:00 Process Exit Code: (1060) The specified service does not exist as an installed service.
08:59:00 C:\TEMP\_ISTMP10.DIR\scm.exe -Silent 1 -Action 4 -Service MSSQLServer
08:59:05 Process Exit Code: (0)
08:59:05 Installation Failed.
CAUSE
An 0xc000006 exception error occurs when the system attempts to retrieve a swapped-out page and fails.
WORKAROUND
To work around the problem, use the methods that follow.
- If you suspect that the problem is with the CD-ROM disk drive unit, copy the contents of the SQL Server 7.0 CD-ROM disk to a local directory on the local hard drive and include these directories:
Then, retry the installation.
- If you suspect that the local CD-ROM disk drive unit is damaged and the computer is on a network, copy the CD-ROM disk to the local hard drive from another CD-ROM disk drive that you have shared on another computer.
- Make sure that the CD-ROM disk that you are using to install SQL Server is not scratched or otherwise damaged. To test the condition of the CD-ROM disk, temporarily install SQL Server to another computer. If the CD-ROM disk is bad this installation attempt is likely to fail.
- After you rule out difficulties with the CD-ROM disk and drive, devote your attention to the local hard drive. Monitor page file usage on the system. Systems with page file usage that average about 30% and peak out at about 70%, or higher, are likely to cause the errors shown in the "Symptoms" section. If this is the case, increase the amount of RAM to improve the disk drive and related controller measurements.
Modification Type: | Major | Last Reviewed: | 12/17/2004 |
---|
Keywords: | kbprb KB305680 |
---|
|