Antivirus Interference (errors 88319 and 88320)
Security software can stop Speediful in two ways, and each has its own error number:
| Error | When Speediful was stopped | Work done |
|---|---|---|
| 88319 | Before it started | None |
| 88320 | While it was running | Some, possibly |
The exclusions under Temporary fix clear both errors.
Error 88319: Speediful never started
Speediful did not start, so no work was done. The output in the Results pane may provide further details. Antivirus software is a common cause. Refer to Speediful's documentation on antivirus interference for further assistance.
Speediful never started. Nothing was read from Salesforce, nothing was written to SQL
Server, and no rows were changed. The error itself cannot tell why Speediful did not
start, so read the output in the Results pane. Whatever was printed before Speediful
stopped is there, in the output column.
When security software is the cause
This is a common cause. Security software blocked files Speediful needs, and the output in the Results pane names a file that could not be loaded:
Error, load DLL. ([Error 225] Operation did not complete successfully because the file
contains a virus or potentially unwanted software.)
The Messages pane shows the error itself:
Msg 88319, Level 16, State 1 ... Speediful did not start, so no work was done.
The wording of the first line varies. Windows error 225 specifically means security software refused to load the file. The exclusions under Temporary fix clear it.
Other causes
If the output in the Results pane does not name a file that could not be loaded, security software is unlikely to be the cause, and the exclusions will not clear the error. Send that output to Speediful support along with the procedure call.
Error 88319 is raised before Speediful examines the input table, contacts Salesforce, or writes anything. Re-running once the cause is fixed is safe, and no rows were partially processed.
Error 88320: Speediful was stopped while running
Speediful was stopped by Windows before it finished (exit code -1073741819, 0xC0000005). Security software is the most common cause. Some work may have been done. Refer to Speediful's documentation on antivirus interference for further assistance.
Speediful started, then Windows ended the program before it could finish or report an
error of its own. The Results pane usually shows Speediful's version line and little
else: no error text from Speediful and no Support reference #. Speediful's own log is
empty for the same reason.
The error names the exit code, the number Windows reported when it ended the program, first as a decimal and then as a hexadecimal status code. The status code tells you what stopped it:
| Exit code | Status code | Meaning |
|---|---|---|
-1073741819 | 0xC0000005 | Access violation. The program touched memory it was not allowed to. Security software that injects code into running programs is the most common cause. |
-1073741818 | 0xC0000006 | In-page error. Windows could not read part of the program from disk, often because a scanner held the file locked or a network or disk read failed. |
-1073740791 | 0xC0000409 | Stack buffer overrun, also reported for a fail-fast exit. Exploit protection and endpoint security products raise this when they end a program they consider suspicious. |
Any other negative exit code is also a Windows status code. Search for the hexadecimal
form (for example 0xC0000005) to find its meaning.
Unlike error 88319, Speediful may have done part of the work before it was stopped. A
load may have sent some rows to Salesforce; a query may have left a partly written
table. Check the input table's SLAM_message column, or the destination table, before
you re-run.
Temporary fix: exclude Speediful from real-time scanning
Excluding these paths clears the error. Treat it as a temporary measure.
C:\Program Files\Speediful\SLAM\- the
AppData\Local\Tempfolder of the account SQL Server runs as
Speediful runs as the SQL Server service account and unpacks itself into that account's
temporary folder, so the second path depends on the instance. To find it, run this in SQL
Server Management Studio (SSMS) and add \AppData\Local\Temp to the folder it prints:
EXEC xp_cmdshell 'echo %USERPROFILE%';
Unless an administrator changed the account SQL Server runs as, the folder is:
| Instance | Temporary folder |
|---|---|
Default instance (MSSQLSERVER) | C:\Windows\ServiceProfiles\MSSQLSERVER\AppData\Local\Temp |
Named instance, for example PROD | C:\Windows\ServiceProfiles\MSSQL$PROD\AppData\Local\Temp |
For Microsoft Defender, an administrator can add both in PowerShell. Replace the second path with the folder you found:
Add-MpPreference -ExclusionPath 'C:\Program Files\Speediful\SLAM'
Add-MpPreference -ExclusionPath 'C:\Windows\ServiceProfiles\MSSQL$PROD\AppData\Local\Temp'
For other products, add the same two paths as real-time scanning exclusions using that product's management console. In a managed environment these are usually set through group policy rather than on the server itself, so your security team may need to make the change.
If your security policy does not permit these exclusions, contact Speediful support.
Reporting it
If the exclusions are in place and the error continues, send Speediful support the detection record from your antivirus product (the threat name and the full path it names) along with the output in the Results pane and the error from the Messages pane, including the exit code. This is worth reporting even when an exclusion resolves it, so the file can be submitted to the vendor for reclassification.