This Package applies to these issues:
• Disabling the ISAPI service and resetting IIS caused the XSISAPI.dll file not to load. The Event log reported the following message: "The HTTP Filter DLL C:\Windows\system32\inetsrv\XSISAPI.DLL failed to load. The data is the error. Could not load all ISAPI filters for site 'DEFAULT WEB SITE'. Therefore site startup aborted." 
• For unknown devices (i.e. devices which are not enrolled or devices in which the ActiveSync ID is not present in Afaria or the devices.xml file), the ISAPI pipe server must scan the devices.xml file for the user in order to determine if the device is allowed or blocked. This activity consumes significant CPU cycles. If many unknown devices are syncing, the pipe server will exhibit heavy CPU utilization. 
• Corrected issues in which multiple entries were added to the devices.xml file. 
• Access Control (ISAPI filter) improved performance and stability. 
• Improved performance of device.xml creation process.
• Improved performance of device lookup process when ActiveSync ID is present for a device.
• Added a check to ensure that the devices.xml file exists before accessing the file. This prevents an exception error from occurring while the devices.xml file is being updated.
• For any existing iOS devices which do not have an ActiveSync ID, the ActiveSync ID will be generated using the format "APPL<DeviceSerialNumber>" in the devices.xml file.
- SAP Afaria 7 Service Pack 3
- SAP Afaria ISAPI Filter
release notes. , KBA , MOB-AFA , Afaria , Problem
About this pageThis is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP ONE Support launchpad (Login required).
Search for additional results
Visit SAP Support Portal's SAP Notes and KBA Search.