Summary:

Issues with TGlobalLibraryFileList can cause an access violation when users attempt to log on. Existing user sessions are unaffected.

Symptoms:

Calls to ChecForandSendFile in TGolablLibraryFileList result in an exception being thrown. The following is from the ewaresystem.log:

Aug 30 2012 10:24:57.046 18148 24612 1 Exception caught and logged. Exception ID:2027342596
Aug 30 2012 10:24:57.046 18148 24612 1 Stack for exception:

------------------------------------------------------------------------------------------
|Address |Module |Unit |Class |Procedure/Method |Line |
------------------------------------------------------------------------------------------
|1A791913|eware.dll|HTTPUtils.pas |TGlobalLibraryFileList|CheckForandSendFile|885[13] |
|1A791870|eware.dll|HTTPUtils.pas |TGlobalLibraryFileList|CheckForandSendFile|872[0] |
|1A936D05|eware.dll|ISAPIDispatch.pas|TISAPIEntry |ISAPIEntryLogin |218[37] |
|1A8F0F07|eware.dll|HTTPApp.pas |TWebActionItem |DispatchAction |1106[18]|
|1A8F0E14|eware.dll|HTTPApp.pas |TWebActionItem |DispatchAction |1088[0] |
|1A8F1BE0|eware.dll|HTTPApp.pas |TCustomWebDispatcher |DispatchAction |1503[32]|
|1A8F1ACC|eware.dll|HTTPApp.pas |TCustomWebDispatcher |DispatchAction |1471[0] |
|1A8F1D92|eware.dll|HTTPApp.pas |TCustomWebDispatcher |HandleRequest |1541[3] |
|1A8F338D|eware.dll|HTTPApp.pas |TDefaultWebAppServices|InvokeDispatcher |2217[3] |
|1A8F3350|eware.dll|HTTPApp.pas |TDefaultWebAppServices|InvokeDispatcher |2214[0] |
|1A8F3330|eware.dll|HTTPApp.pas |TDefaultWebAppServices|HandleRequest |2198[1] |
|1A150F75|eware.dll|WebReq.pas |TWebRequestHandler |HandleRequest |368[25] |
|1A150E44|eware.dll|WebReq.pas |TWebRequestHandler |HandleRequest |343[0] |
|1A151E9A|eware.dll|ISAPIApp.pas |TISAPIApplication |HttpExtensionProc |100[6] |
|1A151E40|eware.dll|ISAPIApp.pas |TISAPIApplication |HttpExtensionProc |94[0] |
|1A151F9D|eware.dll|ISAPIApp.pas | |HttpExtensionProc |147[10] |
------------------------------------------------------------------------------------------

Status:

This issue has been resolved in Sage CRM version 7.1i Hotfix 3.