3CX Call Logs error

Discussion in '3CX Phone System - General' started by lneblett, May 5, 2011.

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

    lneblett Well-Known Member

    Joined:
    Sep 7, 2010
    Messages:
    2,061
    Likes Received:
    56
    Have recently been unable to use the call log function. Am unsure how long the situation has existed as the feature is not used very much; only when a specific detail is needed. In any event, any access to any report using the call reporter results in an error message being reported by the 3CX interface. The content of the error message reads:

    3CX Interface
    ---------------------------
    An exception occurred CrystalFilter Error: Unable to read data from the transport connection: An existing connection was forcibly closed by the remote host.
    ---------------------------
    Responding OK to the message then results in a new pop-up with the following:
    ---------------------------

    ---------------------------
    Unable to read data from the transport connection: An existing connection was forcibly closed by the remote host.

    at System.Net.Sockets.NetworkStream.Read(Byte[] buffer, Int32 offset, Int32 size)

    at System.IO.BufferedStream.ReadByte()

    at Npgsql.NpgsqlState.<ProcessBackendResponses_Ver_3>d__a.MoveNext()

    at Npgsql.NpgsqlState.IterateThroughAllResponses(IEnumerable`1 ienum)

    at Npgsql.NpgsqlConnectedState.Startup(NpgsqlConnector context)

    at Npgsql.NpgsqlConnector.Open()

    at Npgsql.NpgsqlConnectorPool.GetPooledConnector(NpgsqlConnection Connection)

    at Npgsql.NpgsqlConnectorPool.RequestPooledConnectorInternal(NpgsqlConnection Connection)

    at Npgsql.NpgsqlConnectorPool.RequestPooledConnector(NpgsqlConnection Connection)

    at Npgsql.NpgsqlConnectorPool.RequestConnector(NpgsqlConnection Connection)

    at Npgsql.NpgsqlConnection.Open()

    at FastReport.Data.DataConnectionBase.OpenConnection(DbConnection connection)

    at FastReport.Data.DataConnectionBase.FillTableData(DataTable table, String selectCommand, CommandParameterCollection parameters)

    at FastReport.Data.DataConnectionBase.X0YmPnYPT(TableDataSource )

    at FastReport.Data.TableDataSource.LoadData(ArrayList rows)

    at FastReport.Data.DataSourceBase.dYtpv1Qtr()

    at FastReport.Data.DataSourceBase.Init(Relation relation, String filter, SortCollection sort)

    at FastReport.Data.DataSourceBase.Init(DataSourceBase parentData, String filter, SortCollection sort)

    at FastReport.DataBand.InitDataSource()

    at FastReport.Engine.ReportEngine.rBd2ZOhjR(DataBand )

    at FastReport.Engine.ReportEngine.M4BDF48yZ4(BandCollection )

    at FastReport.Engine.ReportEngine.8JZDjfY4JV(ReportPage )

    at FastReport.Engine.ReportEngine.qlgD542Zs1()

    at FastReport.Engine.ReportEngine.rmS6MY2xJ(Boolean , Boolean , ReportPage )

    at FastReport.Engine.ReportEngine.sdkrTC5tw(Boolean , Boolean )

    at FastReport.Report.Prepare(Boolean append)

    at FastReport.Report.Show(Boolean modal, Form owner)

    at FastReport.Report.Show()

    at _CXCallLogsReporter.CrystalFilter.printReport()


    The event viewer shows:
    An error occurred while reading the command timeout for fast report from DB. Use default value 120 secs. Error: Unable to read data from the transport connection: An existing connection was forcibly closed by the remote host.

    Version is 9 with all updates installed, all 3CX services show to be started and in the green and verified in Windows services.

    Looking at the 3CX reports file, it appears that the 1st instance of this occuring was on 4/18/2011, but client did not mention at the time.

    Any help appreciated.

    Thanks,

    Larry Neblett
     
  2. lneblett

    lneblett Well-Known Member

    Joined:
    Sep 7, 2010
    Messages:
    2,061
    Likes Received:
    56
    Hmm interesting. A simple reboot of the server seems to have fixed the problem. What is puzzling is that the syetem has been rebooted since April 18, so I now wonder what conditions cause the issue to reoccur? Will monitor and advise should the gremlin reappear.
     
Thread Status:
Not open for further replies.