sqlmss32.dll Missing: Repair the Legacy BDE Connection

sqlmss32.dll is a 32-bit Borland Database Engine (BDE) SQL Links driver for Microsoft SQL Server. It is an application component, not a Windows system DLL, Visual C++ runtime, DirectX file, or modern SQL Server component.

The safest fix is to identify the program that needs it, then repair or reinstall that program and its BDE or SQL Links components from the original vendor installer. Do not begin by downloading a loose copy of sqlmss32.dll or placing it in System32.

What the sqlmss32.dll error means

Windows may display messages such as:

• “The program can’t start because sqlmss32.dll is missing from your computer.”
• “The code execution cannot proceed because sqlmss32.dll was not found.”
• “The specified module could not be found.”
• “sqlmss32.dll is either not designed to run on Windows or it contains an error.”

A BDE application may instead show:

• “An error occurred while attempting to initialize the Borland Database Engine”
• “Cannot load an IDAPI service library”
• A named missing dependency such as NTWDBLIB.DLL

The wording varies by Windows version and application. “The specified module could not be found” does not always mean sqlmss32.dll itself is absent. Windows may be unable to find a dependency required by the file.

The commonly documented file is version 5.2.0.2, approximately 0.4 MB, and 32-bit. Older Delphi, C++Builder, Paradox, and business applications built with BDE and SQL Links may use it.

Fix 1: Identify and repair the application that owns the file

Time needed: 10–30 minutes

This is the most likely solution because sqlmss32.dll is installed by a specific legacy application or its BDE runtime.

Find the parent program

1. Note the application name shown in the error or the shortcut you were opening.
2. Right-click the shortcut and select Properties.
3. Check the Target field. The executable path often reveals the application folder.
4. Open File Explorer and inspect that folder.
5. Search the application’s installation directory for sqlmss32.dll.
6. If the file exists elsewhere, do not copy it yet. Record its full path.

Also check Settings > Apps > Installed apps for the program name. Older desktop programs may instead appear under Control Panel > Programs > Programs and Features.

Repair it

For a Microsoft Store-style entry or a supported desktop application:

1. Open Settings.
2. Select Apps > Installed apps.
3. Find the affected program.
4. Select the three-dot menu.
5. Choose Advanced options.
6. Select Repair, if available.
7. Start the application again.

For a classic desktop program:

1. Open Control Panel.
2. Select Programs > Programs and Features.
3. Select the affected application.
4. Choose Change, Repair, or Modify.
5. Keep the BDE, SQL Links, Microsoft SQL Server driver, or database connectivity feature selected.
6. Complete the installer and restart Windows.

If there is no repair option, uninstall and reinstall the application using its original trusted installer or installation media. Back up the application’s data and configuration first. Some BDE applications share configuration with other programs, so do not remove a shared BDE installation casually.

How to tell whether it worked

The repair worked if the program opens without the sqlmss32.dll message and reaches its normal login or database screen. If the program opens but fails when connecting to SQL Server, the DLL may be present and the remaining problem may be a missing client library, database alias, server setting, permission, or network configuration.

If repair does not restore the file, repeat the installation using the vendor’s complete installer and explicitly select the BDE or SQL Server connectivity component.

Fix 2: Reinstall the legacy BDE or SQL Links runtime

Time needed: 15–45 minutes

BDE applications do not normally need only one DLL. They may also require BDE registry entries, configuration files, SQL Links files, and an older SQL Server client library.

1. Close the affected program.
2. Check its installation media, archived vendor installer, or the application vendor’s support area.
3. Look for a component named Borland Database Engine, BDE, SQL Links, Microsoft SQL Server driver, or database runtime.
4. Run the installer as an administrator:
5. Right-click the installer.
6. Select Run as administrator.
7. Choose Repair, Modify, or a complete installation.
8. Select the Microsoft SQL Server connectivity feature if the installer offers component choices.
9. Restart Windows.
10. Launch the original application.

The historical BDE runtime is deprecated and is not replaced by a normal Microsoft redistributable package. Installing Visual C++, DirectX, .NET, SQL Server Management Studio, or Windows Update will not normally install sqlmss32.dll.

No current unrestricted standalone Microsoft package for the historical BDE build should be assumed. Use the original application vendor, licensed Borland or Embarcadero product access, or trusted installation media.

Fix 3: Check Windows Security quarantine before restoring anything

Time needed: 5–15 minutes

A cleanup utility, antivirus product, or Microsoft Defender may have removed the file. Restoration must not be automatic because a file that merely resembles a legitimate legacy DLL could also be malicious.

1. Open Windows Security from the Start menu.
2. Select Virus & threat protection.
3. Select Protection history.
4. Review entries around the time the error began.
5. Expand any detection involving sqlmss32.dll or the application folder.
6. Confirm that the file came from the original trusted application installer.
7. If your organization manages security software, ask the administrator to review the detection.
8. Restore or allow the file only after its provenance has been verified.

If the file came from an unknown download, another computer, or a random DLL archive, do not restore it. Remove that copy and reinstall the application from its trusted source instead.

Microsoft’s Protection History guidance explains how quarantined items are reviewed and why restoring a genuine threat can put the device at risk.

Fix 4: Check the missing dependency named by the error

Time needed: 15–45 minutes

A present sqlmss32.dll can still produce “specified module could not be found” if Windows cannot load one of its dependencies.

Look for names such as:

• NTWDBLIB.DLL
• DBNETLIB.DLL
• DBNMPNTW.DLL
• Another SQL Server client library

If one of these is named, reinstall the matching database client components supplied with the application or supported by its vendor. Do not install a random replacement DLL from the internet.

To check the basic situation:

1. Open the application’s installation folder.
2. Confirm whether sqlmss32.dll is present.
3. Read the complete error rather than only the first line.
4. Check whether the error appears at application startup or only when opening a database.
5. Contact the application vendor with the exact dependency name.

If the application starts but cannot connect to the database, the issue may be the SQL Server protocol, server name, alias, credentials, permissions, or network configuration rather than the DLL.

Fix 5: Confirm 32-bit compatibility on 64-bit Windows

Time needed: 5–15 minutes

The identified sqlmss32.dll file is 32-bit. A 32-bit application can run on 64-bit Windows through WOW64, but it must load 32-bit dependencies.

Do not replace it with a 64-bit DLL. Do not install a second copy in System32 or `SysWOW64 as a general fix.

Windows uses System32 for native system components and SysWOW64 for 32-bit system components on 64-bit Windows. That naming is confusing, but neither folder is the correct home for an application-specific BDE driver.

The correct location is the application or BDE directory selected by the installer, often under a Borland or shared application folder. Windows commonly searches the executable’s folder before system directories, so placing files in the wrong directory can prevent the application from finding the expected build.

Microsoft explains the compatibility rules for 32-bit applications, file-system redirection, and DLL search order.

Fix 6: Do not use regsvr32 for this driver

Time needed: 2 minutes

regsvr32 is not a general-purpose DLL repair command. BDE SQL Links drivers are normally installed and configured by the BDE installer, not registered like an ActiveX or COM component.

Do not run:

regsvr32 sqlmss32.dll

If you already did and received “DllRegisterServer was not found,” that is expected evidence that registration is not the right repair. Reinstall the application or BDE runtime instead.

Microsoft documents regsvr32 for DLLs that provide a registration entry point such as DllRegisterServer.

Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Support on Ko-Fi

Fix 7: Repair Windows components only if other programs are failing

Time needed: 10–30 minutes

Because sqlmss32.dll is not a Windows system DLL, SFC and DISM will not normally recreate it. Use them when Windows itself has broader corruption symptoms, such as several built-in applications failing or repeated system-component errors.

1. Save your work.
2. Open Start and type Command Prompt.
3. Right-click Command Prompt.
4. Select Run as administrator.
5. Run DISM first:

DISM /Online /Cleanup-Image /RestoreHealth

1. Wait for it to finish.
2. Run System File Checker:

sfc /scannow

1. Restart Windows.
2. Test the application again.

Microsoft’s System File Checker instructions cover this sequence.

When manually hunting through Windows components or repeating repair commands makes it difficult to see what changed, Outbyte PC Repair can scan for system problems and show what it found; repairs are performed by the full version. It is not required, and reinstalling the application remains the definitive fix when the missing file belongs to that application.

Fix 8: Roll back a recent change with System Restore

Time needed: 15–30 minutes

Use System Restore if the error began immediately after a cleanup, driver installation, Windows change, or application update and a suitable restore point exists.

1. Press Windows key + R.
2. Type:

rstrui.exe

1. Press Enter.
2. Select Next.
3. Choose a restore point from before the error began.
4. Select Scan for affected programs if available.
5. Review the result.
6. Select Next > Finish.
7. Allow Windows to restart.

System Restore rolls back system settings, installed programs, and drivers without normally affecting personal files. It may restore the application’s files or configuration, but it is not a substitute for a clean vendor reinstall.

Fix 9: Update related drivers only when the application vendor requires it

Time needed: 15–30 minutes

Device Manager is relevant only if the application depends on a hardware or system driver that is also failing. It does not install sqlmss32.dll.

1. Right-click Start.
2. Select Device Manager.
3. Expand the relevant category, such as Network adapters, Storage controllers, or System devices.
4. Right-click the suspected device.
5. Select Update driver.
6. Choose Search automatically for drivers.
7. Restart Windows if prompted.

Do not remove an unknown device or install a modern driver package merely because the DLL error mentions SQL Server. Ask the application vendor which driver version is supported.

If identifying the correct device and matching driver is the difficult part, Outbyte Driver Updater can scan for outdated drivers and identify what needs attention; driver installation is performed by the full version. It is optional, and it will not replace the BDE runtime required by the owning application.

Why this error appears after a reinstall or PC move

Common causes include:

• Windows was reinstalled without reinstalling the legacy application’s BDE component.
• The application was copied rather than installed, leaving out registry configuration and companion files.
• A PC migration moved the executable but not its shared BDE directory.
• A cleanup tool deleted an old DLL it considered unused.
• Antivirus quarantined the file.
• A 64-bit replacement was used for a 32-bit application.
• The BDE configuration or SQL Links files were damaged.
• An old SQL Server client dependency is missing.
• A different BDE build was installed and is incompatible with the application.

FAQ

Is sqlmss32.dll a Windows file?

No. It is an application component associated with the legacy 32-bit Borland Database Engine SQL Links driver for Microsoft SQL Server.

Should I download sqlmss32.dll from a DLL website?

No. Random copies may contain malware, the wrong architecture, the wrong build, or missing companion files. They often leave the BDE configuration and SQL Server client dependency problem unresolved.

Should I copy it to System32 or SysWOW64?

No. Install it through the owning application or BDE installer in the directory expected by that application.

Should I install Visual C++, DirectX, or .NET?

Usually no. Those packages do not normally provide this BDE driver.

Can a 32-bit application run on 64-bit Windows?

Yes, through WOW64, provided the application, sqlmss32.dll, BDE components, and required database client libraries are compatible 32-bit files.

What if the original application is unavailable?

First identify the executable, vendor, installer media, and licensing information. Contact the vendor or obtain a licensed copy of the product installer. The DLL alone cannot establish the correct BDE configuration, companion files, SQL Server client version, or registry settings.

What should I give technical support?

Provide the application name and version, exact error text, full path shown in the error, Windows version, whether the file was quarantined, whether the program is 32-bit, and whether the error occurs at startup or only during database connection.

Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.