Symantec Access Management

  • Private Community

  • 1.  MSVCR80.dll error with Exception code: 0xc0000005

    Posted Mar 03, 2017 09:10 AM

    Hi All,

     

    I have setup a new environment of Siteminder and Policy server with SSO for applications.

     

    ISSUE:-


    Only problem is my policy server stops randomly and i could only find out the following error log:-

     

    Faulting application name: smpolicysrv.exe, version: 12.52.100.499, time stamp: 0x53f2882e
    Faulting module name: MSVCR80.dll, version: 8.0.50727.6195, time stamp: 0x4dcddbf3
    Exception code: 0xc0000005
    Fault offset: 0x00014500
    Faulting process id: 0x6c4
    Faulting application start time: 0x01d29421e49ec2f3
    Faulting application path: C:\PROGRA~2\CA\SITEMI~1\bin\smpolicysrv.exe
    Faulting module path: C:\Windows\WinSxS\x86_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.6195_none_d09154e044272b9a\MSVCR80.dll
    Report Id: 2f5e6eb4-0015-11e7-af13-d8d385a739ae

     

     

    My analysis:-

     

    • VC++ version issue.
    • either uninstall or upgrade the dotnet version.

     

    Please help me with this, I have to restart Policy server every time as visible in event viewer.

    Thanks,
    Hridyesh



  • 2.  Re: MSVCR80.dll error with Exception code: 0xc0000005

    Posted Mar 03, 2017 09:48 AM

    Hi Hridyesh,

     

    Please review the below article from Microsoft on the faulting module: MSVCR80.dll

    MSVCR80.dll problem - Microsoft Community 

    If you continue to have issues, please open a case with CA Support as this could be a bug with the version of the policy server and further analysis would be needed.



  • 3.  Re: MSVCR80.dll error with Exception code: 0xc0000005

    Posted Mar 06, 2017 05:18 AM

    Hi blach12,

     

    I did go through the thread error : faulting module MSVCR80.dll , and found the similar results but i suspect this being a bug which is not fixed till date. I'm open to raising a ticket but everything is working as it should except the service going down repeatedly in a pattern, i.e gap of 3 minutes.

    Also tried re-installing the vcredist package from siteminder/bin to avoid any chances of version mismatch. 
    Guys any help on this ? Ujwol emmle02

    Thanks,
    Hridyesh



  • 4.  Re: MSVCR80.dll error with Exception code: 0xc0000005

    Posted Mar 06, 2017 05:48 AM

    Ensure the latest updates for Microsoft Visual C++ 2005,2010,2013 x86  is installed.


    https://communities.ca.com/community/ca-security/ca-single-sign-on/blog/2016/07/12/tech-tip-ca-single-sign-on-policy-serverunsatisfiedlinkerror


    If still having problem, capture IIS debug diag crash dump of smpolicysrve.exe. This needs to be analayzed.


    If you are running Policy server from command line, you might as well get some debug message in the console.



  • 5.  Re: MSVCR80.dll error with Exception code: 0xc0000005

    Posted Mar 06, 2017 06:37 AM

    Re-installed the 2013 x86 version, still facing issue.
    Yes i'm running policy server from command line, without any debug message in the console
    Additionally the Informational log named as Windows Error Reporting which can be seen in the screenshot describes:-

     

    Fault bucket , type 0

    Event Name: APPCRASH

    Response: Not available

    Cab Id: 0

     

    Problem signature:

    P1: smpolicysrv.exe

    P2: 12.52.100.499

    P3: 53f2882e

    P4: MSVCR80.dll

    P5: 8.0.50727.6195

    P6: 4dcddbf3

    P7: c0000005

    P8: 00014500

    P9:

    P10:

     

    Attached files:
    Attaching the fiiles found at the location

     

    These files may be available here:

    C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppCrash_smpolicysrv.exe_1e81e3c6a3cf141d81cba37d3f6ef99622d7e6fa_184fd8e5

     

    Analysis symbol:

    Rechecking for solution: 0

    Report Id: d47d2334-025d-11e7-aa39-d8d385a739ae

    Report Status: 4

    If this can be of some help debugging.



  • 6.  Re: MSVCR80.dll error with Exception code: 0xc0000005

    Posted Mar 08, 2017 06:59 AM

    Not really. We will need to capture the full crash dump and analayze with DebugDiag tool.


    https://blogs.msdn.microsoft.com/cobold/2010/03/01/collecting-crash-dumps/