Microsoft KB Archive/305680

= SQL Server 7.0 Acmsetup.exe setup application fails =

Article ID: 305680

Article Last Modified on 12/17/2004

-

APPLIES TO


 * Microsoft SQL Server 7.0 Standard Edition

-



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 &quot;D:\MSSQL7\&quot; -SQLDataPath &quot;E:\MSSQL7\&quot; -SortID 52 -LCIDCompStyle &quot;1033-196609&quot; -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:  x86</li> Install</li> Html</li> Devtools</li></ul>

Then, retry the installation.

</li> 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.</li> 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.</li> 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 &quot;Symptoms&quot; section. If this is the case, increase the amount of RAM to improve the disk drive and related controller measurements.</li></ul>

<div class="moreinformation_section">

MORE INFORMATION
The text for the 0xc000006 exception error is:

&quot;I/O Error in Paging&quot; (STATUS_IN_PAGE_ERROR).

The 0xc000006 exception error is indicative of a low-level I/O problem. If you are performing the installation over a network (from a central installation server or a shared CD-ROM drive), network issues can cause the error messages.

The 0xc000006 exception error may also occur with remote program execution. A portion of the executable is on the remote disk and when the program goes to read the page, for some reason (usually network related) the page fetch fails. The page fetch fails because of the heavy demand on RAM, causing page file usage. The installation routine requests a page from Windows, the request fails and as a result the process terminates. A failure to satisfy a page request is a good indication of hardware related problems.

Problems with either the CD-ROM disk drive unit or the CD-ROM disk itself can also cause similar I/O behavior.

Additional Troubleshooting Steps
You can also use the methods that follow to troubleshoot the problem:  Increase the paging file size so that it is at least as large as the amount of RAM + 12 MB.</li> Run the Check Disk utility on the computer's disks to check for hardware problems.</li> Examine the Event Viewer's System Log for errors.</li> Make sure that the latest drivers are installed for the computer's SCSI controller card.</li> Make sure that the latest BIOS for the computer's mother board is installed.</li> Consider reinstalling the Microsoft NT Windows Service Pack that is currently in place, or apply the next version. Also reapply the same version, or a later version, of Microsoft Internet Explorer and Microsoft Data Access Components (MDAC). Newer versions of Internet Explorer and MDAC have resolved the problem in some cases.</li> Make sure that the person who runs the installation is logged on with administrator authority for the local computer.</li> <li>Check the NTFS permissions of the drive where SQL Server is being installed, make sure that Administrators and Local System have full control, and that those permissions apply to all sub-directories and files.</li> <li>Select the Local System account for the SQL Server service to start.</li> <li>Navigate to Control Panel and double-click the Services folder. Search for the services in the following list. Stop any service that is not in the list until the SQL Server 7.0 installation completes: Windows NT 4.0 Services

<ul> <li>Alerter</li> <li>ClipBook Server</li> <li>Computer Browser</li> <li>Directory Replicator</li> <li>Event Log</li> <li>License Logging</li> <li>Messenger</li> <li>Net Logon</li> <li>Network DDE</li> <li>Network DDE DSDM</li> <li>NT LM Security Support Provider</li> <li>Remote Procedure Call (RPC) Locator</li> <li>Remote Procedure Call (RPC) Service</li> <li>Schedule</li> <li>Server</li> <li>Spooler</li> <li>UPS</li> <li>Workstation</li></ul>

Windows 2000 Services

<ul> <li>Alerter</li> <li>Computer Browser</li> <li>Distributed File System</li> <li>Distributed Link Tracking Client</li> <li>Distributed Link Tracking Server</li> <li>DNS Client</li> <li>Event Log</li> <li>IPSEC Policy Agent</li> <li>License Logging Service</li> <li>Logical Disk Manager</li> <li>Messenger</li> <li>Net Logon</li> <li>NT LM Security Support Provider</li> <li>Network Connectors</li> <li>Plug and Play</li> <li>Process Control</li> <li>Remote Procedure Call (RPC) Locator</li> <li>Remote Procedure Call (RPC) Service</li> <li>Remote Registry Service</li> <li>Removable Storage</li> <li>RunAs Service</li> <li>Security Accounts Manager</li> <li>Server</li> <li>Spooler</li> <li>TCP/IP NetBIOS Helper</li> <li>Time Service</li> <li>Windows Management Instrumentation Driver Extensions</li> <li>Windows Time</li> <li>Workstation</li></ul>

Now that you have stopped all the non-essential services, open Task Manager and stop any program that is not in this list:

<ul> <li>Csrss.exe</li> <li>Explorer.exe</li> <li>Llssrv.exe</li> <li>Loadwc.exe</li> <li>Lsass.exe</li> <li>Nddeagnt.exe</li> <li>Pstores.exe</li> <li>RpcSs.exe</li> <li>Services.exe</li> <li>Smss.exe</li> <li>Spools.exe</li> <li>System.exe</li> <li>System Idle Process</li> <li>Taskmgr.exe</li> <li>Winlogon.exe</li></ul>

</li> <li>Install MDAC 2.1 for SQL Server 7.0 or MDAC 2.5 for SQL Server 2000 separate from the SQL Server installation.

To install MDAC 2.1 for SQL Server 7.0, the file is located on the CD-ROM disk at: x86\Other\Mmdac_typ.exesqlredis.exe</li></ul>