Error 126 loading library sqlcax.dll ???

http://support.microsoft.com/support/kb/articles/q307/1/96.ASP
что-то я не въеду, что это значит???

CAUSE
The problem in this case is the Path statement. The error message can occur if the path statement does not contain the path to the Sqlservr.exe file. For example:

(C:\Windows;C:\Mssql7\Binn;C:\)

Я, конечно, извиняюсь, но я ни чего не понял : (
Вот что ещё нарыл, как обойти на пойму??

Setup with MSDE Merge Modules May Fail During Initialization (SQLCAX.DLL)
Description:
A setup that includes the MSDE merge modules from the may fail during the initialization phase. When you create a log file of the installation you find an entry similar to this:
Action start 11:52:49: GetSqlStates.2D02443E_7002_4C0B_ABC9_EAB2C064397B.
Loading extended custom action library sqlcax.dll
Error 126 loading library sqlcax.dll
Action ended 11:52:49: GetSqlStates.2D02443E_7002_4C0B_ABC9_EAB2C064397B. Return value 3.
1: Failed to launch action 'GetSqlStates.2D02443E_7002_4C0B_ABC9_EAB2C064397B', error is 1603
Cause:
SQLBASE.MSM includes (among others) the following custom actions: StreamSupportFiles and GetSqlStates. StreamSupportFiles is responsible for unpacking sqlcax.dll from the Binary table to a temp directory where custom action GetSqlStates can load it. If GetSqlStates is called before StreamSupportFiles it will fail with error code 126 "Specified module could not be found".
Custom actions in merge modules are sequenced based on standard actions. StreamSupportFiles is called before LaunchConditions and GetSqlStates is called after AppSearch. If you place AppSearch before LaunchConditions in your main setup (which is completely legal) the MSDE custom actions will be called in the wrong order.
Workarounds:
Move AppSearch after LaunchConditions in your main setup. Or open SQLBASE.MSM in Orca and adjust the ModuleInstallUISequence and ModuleInstalLExecuteSequence so that StreamSupportFiles is called before AppSearch. (Remarks: I haven't tested the latter solution but in theory it should work. You should check all other MSDE modules to see if they include similar problems)
Status:
This problem is documented in Microsoft Knowledge Base article 321283.
InstallShield Developer 8 includes a workaround for this problem.
Created: 2002-07-08 Last update: 2003-02-18

http://www.installsite.org/pages/en/bugs_msi.htm