| Previous | Next |
| ERROR_INVALID_DLL | ERROR_DDE_FAIL |
ERROR_NO_ASSOCIATION
No registered application can perform the requested shell operation.
ERROR_NO_ASSOCIATION has value 1155 (0x483). It is commonly returned by shell activation such as ShellExecuteEx when Windows cannot resolve the supplied file name or URI and verb to an installed handler. The target file may exist and be readable; the missing piece is the association needed to decide which application should receive it.
Interpret the complete activation request
- the extension or URI scheme, including its original spelling
- the verb, such as
open,edit,print, or a product-specific action - the caller's user account, session, integrity level, and desktop context
- whether the launch used a path, URL, shell item, or document object
- the selected default application and its registration scope
An extension can have a valid open handler but no print handler, so reporting only “.pdf is associated” may miss the actual failure. Per-user defaults also mean that an interactive user and a service account can see different registration state.
Typical causes
- the required application was never installed or was removed incompletely
- a portable application was deleted without removing its registration
- an installer registered the handler for one user but automation runs under another account
- the program supports the file type but did not register the requested verb
- policy or image maintenance reset default-app registration
- the caller supplied an extensionless temporary file or an unregistered custom protocol
Diagnostic steps
- log the unmodified target, verb, parameters, working directory, and show flags
- call the activation path once and preserve
GetLastErrorbefore any fallback - test the same operation interactively under the same account
- inspect the application's supported registration rather than creating an arbitrary command line by hand
- verify that the handler executable still exists and that its registration points to the correct installation
Do not repair this condition by assigning a random executable to the extension. File associations are an activation and security boundary: the handler must understand the data format, quote arguments safely, and support the selected verb.
Application behavior
A desktop program can offer the user a choice of installed applications or direct the user to install the required product. A background service should normally avoid shell associations and invoke a documented executable or API explicitly, because services do not share the interactive user's default-app experience.
When a product owns a custom file type or protocol, its installer should register it transactionally and remove only registrations belonging to that installation. Startup self-repair should not silently overwrite a user's chosen default application.
Distinguishing related results
ERROR_FILE_NOT_FOUND concerns the target or handler path. ERROR_DDE_FAIL indicates that a handler was selected but command delivery failed. ERROR_DLL_NOT_FOUND can be returned if the chosen application lacks a required library. Error 1155 occurs earlier in the shell decision: no suitable association exists for the requested operation.
Example
A service generates a report with a proprietary extension and calls ShellExecuteEx using the print verb. The report viewer is installed only for the logged-on user, while the service account has no corresponding association. Recording account and verb exposes the mismatch; the robust solution is to use the viewer's documented command-line or printing API instead of relying on shell defaults.
References
- Microsoft: System Error Codes (1000–1299)
- Microsoft: ShellExecuteExW function
- Microsoft: Application registration
Looking for a different code? Search another status or error code.