Event IDs 2268 and 2274 with a source of W3SVC-WP when installing Symantec Endpoint Protection Manager on a 64-bit server
Last Updated January 19, 2007
After installing the Symantec Endpoint Protection Manager (SEPM) on a 64-bit server, you are unable to login successfully. You look in the Event Logs and notice Event IDs 2268 and 2274 with a source of W3SVC-WP.
Symptoms Your username and password do not allow you to login to the SEPM after install. In the Event Viewer, you have event log errors that look like the examples below:
Event ID: 2268 Raw Event ID : 2268 Record Nr. : 3746 Source: W3SVC-WP Category: None Type : Error Machine : servername Description: Could not load all ISAPI filters for site/service. Therefore startup aborted.
Event ID: 2274 Raw Event ID : 2274 Record Nr. : 3745 Source: W3SVC-WP Category: None Type : Error Machine : servername Description: ISAPI Filter 'C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\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.
Internet Information Service (IIS) 6.0 supports both the 32-bit mode and the 64-bit mode. However, IIS 6.0 does not support running both modes at the same time on a 64-bit version of Windows. ASP.NET 1.1 runs only in 32-bit mode; ASP.NET 2.0 runs in 32-bit mode or in 64-bit mode. Therefore, if you want to run ASP.NET 1.1 and ASP.NET 2.0 at the same time, you must run IIS in 32-bit mode.