Possible solution if receive ISAPI Filter could not be loaded


#1

A service company using AyaNova received the following error message when logged in via WBI or via RI:

SAPI Filter ?C:\Windows\Microsoft.NET\Framework\v4.0.30319\aspnet_filter.dll? could not be loaded due to a configuration problem. The current configuration only supports loading images built for a AMD64 processor architecture. The data field contains the error number. To learn more about this issue, including how to troubleshooting this kind of processor architecture mismatch error, see http://go.microsoft.com/fwlink/?LinkId=29349.

You may receive similar error with slightly different path (depending on your version of Framework, bit version etc).

Solution:

Same as per this site, issue was due to two backslashes in folder path that once edited and saved, now able to log in again successfully.
[ul]
[li]Opened IIS Manager and selected the IIS web server node
[/li][li]In the middle pane, browse to the IIS section and select ISAPI Filters
[/li][li]Expand the columns as required, looking for an Executable path with \ in it, then click Edit
[/li][li]From the above screenshot, change the \ to \ so the path reads: C:\Windows\Microsoft.NET\Framework\v4.0.30319\aspnet_filter.dll
[/li][li]Keep in mind that the folders Framework and Framework64 or the .NET version may change depending on your implementation.
[/li][/ul]