Dismiss Notice
We would like to remind you that we’re updating our login process for all 3CX forums whereby you will be able to login with the same credentials you use for the Partner or Customer Portal. Click here to read more.

UltiDevCassinWebServer2a.exe get Windows Platform FIPS...

Discussion in '3CX Phone System - General' started by cmindus, Mar 18, 2010.

Thread Status:
Not open for further replies.
  1. cmindus

    Joined:
    Mar 4, 2010
    Messages:
    3
    Likes Received:
    0
    On Win2003StdServer English, 3CX Phone System8, clean install:

    UltiDevCassinWebServer2a.exe get exception This implementation is not part of the Windows Platform FIPS validated cryptographic algorithms.

    Event code: 3005
    Event message: An unhandled exception has occurred.
    Event time: 2010-03-18 22:42:48
    Event time (UTC): 2010-03-18 21:42:48
    Event ID: a638fea388864caf90607f262b752ed5
    Event sequence: 26
    Event occurrence: 1
    Event detail code: 0

    Application information:
    Application domain: 6e55b32f-2-129134221020625000
    Trust level: Full
    Application Virtual Path: /
    Application Path: C:\Documents and Settings\All Users\Application Data\3CX\Data\Http\Interface\
    Machine name: ONE

    Process information:
    Process ID: 2808
    Process name: UltiDevCassinWebServer2a.exe
    Account name: NT AUTHORITY\SYSTEM

    Exception information:
    Exception type: InvalidOperationException
    Exception message: This implementation is not part of the Windows Platform FIPS validated cryptographic algorithms.

    Request information:
    Request URL: http://localhost:5481/Route/1.92.4/ie/en-US/TcxTheme/Icons.logo.gif.wgx
    Request path: /Route/1.92.4/ie/en-US/TcxTheme/Icons.logo.gif.wgx
    User host address: 127.0.0.1
    User:
    Is authenticated: False
    Authentication Type:
    Thread account name: NT AUTHORITY\SYSTEM

    Thread information:
    Thread ID: 14
    Thread account name: NT AUTHORITY\SYSTEM
    Is impersonating: False
    Stack trace: at System.Security.Cryptography.RijndaelManaged..ctor()
    at System.Web.Configuration.MachineKeySection.ConfigureEncryptionObject()
    at System.Web.Configuration.MachineKeySection.EnsureConfig()
    at System.Web.Configuration.MachineKeySection.HashData(Byte[] buf, Byte[] modifier, Int32 start, Int32 length)
    at System.Web.Configuration.MachineKeySection.HashAndBase64EncodeString(String s)
    at System.Web.HttpCachePolicy.UpdateFromDependencies(HttpResponse response)
    at System.Web.HttpCachePolicy.UpdateCachedHeaders(HttpResponse response)
    at System.Web.HttpCachePolicy.GetCurrentSettings(HttpResponse response)
    at System.Web.Caching.OutputCacheModule.OnLeave(Object source, EventArgs eventArgs)
    at System.Web.HttpApplication.SyncEventExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute()
    at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously)

    Quick resolution:

    Edit registry key to remove FIPS complicancy checking in Windows, not very nice because it affects the entire server.
    Set HKLM\System\CurrentControlSet\Control\Lsa\FIPSAlgorithmPolicy to DWORD=0 instead of 1.

    Of course, with Group Policy turned on, this flag normally gets reset to "1" when the Active Directory is replicated.

    So here is another solution: better one: in the Cassini .config file (normally C:\Program Files\3CX PhoneSystem\Bin\Cassini\UltiDevCassinWebServer2a.exe.config), add the lines in italic-bold below in order to have the entire file look like below:

    <?xml version="1.0" encoding="utf-8" ?>
    <configuration>
    <appSettings>
    <add key="PingKeepRunningEverySoMinutes" value="5"/>
    </appSettings>
    <runtime>
    <enforceFIPSPolicy enabled="0"/>
    </runtime>
    </configuration>
     
  2. nb

    nb Support Team
    Staff Member 3CX Support

    Joined:
    Jun 7, 2007
    Messages:
    2,153
    Likes Received:
    172
    Actually we can't do much

    http://support.microsoft.com/kb/935434
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
Thread Status:
Not open for further replies.