"Time out has expired ..." exception

This site uses cookies. By continuing to browse this site, you are agreeing to our Cookie Policy.

  • "Time out has expired ..." exception

    When I try to start the server manager (by selecting the Start button on the Palo Server Manager), there is a few second pause and then I get a Palo Server Manager pop-up error saying:
    _________
    An unhandled exception has occured in your application. If you click Continue, the application will ignore this error and attempt to continue. If you click Quit, the application will be shut down immediately.

    Time out has expired and the operation has not been completed.
    __________
    The server doesn't start up.

    Hitting details yields the additional info at the end of this msg.

    Running on Windows XP Pro, .NET Framework 1.1

    Thanks in advance... Larry

    -----------------------
    from Details window:

    See the end of this message for details on invoking
    just-in-time (JIT) debugging instead of this dialog box.

    ************** Exception Text **************
    System.ServiceProcess.TimeoutException: Time out has expired and the operation has not been completed.
    at System.ServiceProcess.ServiceController.WaitForStatus(ServiceControllerStatus desiredStatus, TimeSpan timeout)
    at PaloInfoPanel.ControllerForm.button1_Click(Object sender, EventArgs e)
    at System.Windows.Forms.Control.OnClick(EventArgs e)
    at System.Windows.Forms.Button.OnClick(EventArgs e)
    at System.Windows.Forms.Button.OnMouseUp(MouseEventArgs mevent)
    at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
    at System.Windows.Forms.Control.WndProc(Message& m)
    at System.Windows.Forms.ButtonBase.WndProc(Message& m)
    at System.Windows.Forms.Button.WndProc(Message& m)
    at System.Windows.Forms.ControlNativeWindow.OnMessage(Message& m)
    at System.Windows.Forms.ControlNativeWindow.WndProc(Message& m)
    at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)


    ************** Loaded Assemblies **************
    mscorlib
    Assembly Version: 1.0.5000.0
    Win32 Version: 1.1.4322.2032
    CodeBase: file:///c:/windows/microsoft.net/framework/v1.1.4322/mscorlib.dll
    ----------------------------------------
    PaloInfoPanel
    Assembly Version: 1.0.2326.18762
    Win32 Version: 1.0.2326.18762
    CodeBase: file:///C:/Program%20Files/Jedox/Palo/PaloInfoPanel.exe
    ----------------------------------------
    System.Windows.Forms
    Assembly Version: 1.0.5000.0
    Win32 Version: 1.1.4322.2032
    CodeBase: file:///c:/windows/assembly/gac/system.windows.forms/1.0.5000.0__b77a5c561934e089/system.windows.forms.dll
    ----------------------------------------
    System
    Assembly Version: 1.0.5000.0
    Win32 Version: 1.1.4322.2032
    CodeBase: file:///c:/windows/assembly/gac/system/1.0.5000.0__b77a5c561934e089/system.dll
    ----------------------------------------
    System.ServiceProcess
    Assembly Version: 1.0.5000.0
    Win32 Version: 1.1.4322.2032
    CodeBase: file:///c:/windows/assembly/gac/system.serviceprocess/1.0.5000.0__b03f5f7f11d50a3a/system.serviceprocess.dll
    ----------------------------------------
    System.Drawing
    Assembly Version: 1.0.5000.0
    Win32 Version: 1.1.4322.2032
    CodeBase: file:///c:/windows/assembly/gac/system.drawing/1.0.5000.0__b03f5f7f11d50a3a/system.drawing.dll
    ----------------------------------------
    System.Data
    Assembly Version: 1.0.5000.0
    Win32 Version: 1.1.4322.2032
    CodeBase: file:///c:/windows/assembly/gac/system.data/1.0.5000.0__b77a5c561934e089/system.data.dll
    ----------------------------------------
    System.Xml
    Assembly Version: 1.0.5000.0
    Win32 Version: 1.1.4322.2032
    CodeBase: file:///c:/windows/assembly/gac/system.xml/1.0.5000.0__b77a5c561934e089/system.xml.dll
    ----------------------------------------

    ************** JIT Debugging **************
    To enable just in time (JIT) debugging, the config file for this
    application or machine (machine.config) must have the
    jitDebugging value set in the system.windows.forms section.
    The application must also be compiled with debugging
    enabled.

    For example:

    <configuration>
    <system.windows.forms jitDebugging="true" />
    </configuration>

    When JIT debugging is enabled, any unhandled exception
    will be sent to the JIT debugger registered on the machine
    rather than being handled by this dialog.
  • RE: "Time out has expired ..." exception

    Hi!
    Manager application is probably unable to start the PALOServerService … there is some problem with Server or you don’t have enough privileges to start the service. Did this happen right after you installed Palo on your PC for the first time? Could you try to start PALOServerService from Server Manager Applet in Control Panel? Could you please post your palo.log?
    Mit freundlichen Gruessen/ With kind Regards / Meilleures salutations

    Vladislav Malicevic
    VP Development & Support
    Jedox AG
  • RE: "Time out has expired ..." exception

    Thanks for the suggestions. When I try starting the "PALO Server Service" from the Windows control panel, I get the following message:
    "The PALO Server Service service on Local Computer startred and then stopped. Some services stop automatically if they have no work to do, for example, the Performance Logs and Alerts service."

    Yes, I've had this problem since loading PALO on this machine (though have used it successfully on others).
  • RE: "Time out has expired ..." exception

    Oh, and today.s PALO log....

    __________
    06.07.2006 09:15:54 INFO: LOG: changed log file to "palo.log"
    06.07.2006 09:15:54 INFO: loading authentication configuration: ".\auth.xml"
    06.07.2006 09:15:54 INFO: loading root: ".\root.xml"
    06.07.2006 09:15:54 INFO: loading root: configuration file not present - loading any available databases
    06.07.2006 09:15:54 INFO: loading database: ".\Demo\Demo.xml"
    06.07.2006 09:15:54 INFO: loading database: configuration file not present - loading any available dimensions and cubes
    06.07.2006 09:15:54 INFO: processing dimension: "Datatypes"
    06.07.2006 09:15:54 INFO: loading dimension: ".\Demo\RGF0YXR5cGVz.dimension.xml"
    06.07.2006 09:15:54 INFO: using dimension log file: ".\Demo\RGF0YXR5cGVz.dimension.log"
    06.07.2006 09:15:54 INFO: processing dimension: "Employees"
    06.07.2006 09:15:54 INFO: loading dimension: ".\Demo\RW1wbG95ZWVz.dimension.xml"
    06.07.2006 09:15:54 INFO: using dimension log file: ".\Demo\RW1wbG95ZWVz.dimension.log"
    06.07.2006 09:15:54 INFO: processing dimension: "Months"
    06.07.2006 09:15:54 INFO: loading dimension: ".\Demo\TW9udGhz.dimension.xml"
    06.07.2006 09:15:54 INFO: using dimension log file: ".\Demo\TW9udGhz.dimension.log"
    06.07.2006 09:15:54 INFO: processing dimension: "Measures"
    06.07.2006 09:15:54 INFO: loading dimension: ".\Demo\TWVhc3VyZXM=.dimension.xml"
    06.07.2006 09:15:54 INFO: using dimension log file: ".\Demo\TWVhc3VyZXM=.dimension.log"
    06.07.2006 09:15:54 INFO: processing dimension: "Projects"
    06.07.2006 09:15:54 INFO: loading dimension: ".\Demo\UHJvamVjdHM=.dimension.xml"
    06.07.2006 09:15:54 INFO: using dimension log file: ".\Demo\UHJvamVjdHM=.dimension.log"
    06.07.2006 09:15:54 INFO: processing dimension: "Products"
    06.07.2006 09:15:54 INFO: loading dimension: ".\Demo\UHJvZHVjdHM=.dimension.xml"
    06.07.2006 09:15:54 INFO: using dimension log file: ".\Demo\UHJvZHVjdHM=.dimension.log"
    06.07.2006 09:15:54 INFO: processing dimension: "Regions"
    06.07.2006 09:15:54 INFO: loading dimension: ".\Demo\UmVnaW9ucw==.dimension.xml"
    06.07.2006 09:15:54 INFO: using dimension log file: ".\Demo\UmVnaW9ucw==.dimension.log"
    06.07.2006 09:15:54 INFO: processing dimension: "Years"
    06.07.2006 09:15:54 INFO: loading dimension: ".\Demo\WWVhcnM=.dimension.xml"
    06.07.2006 09:15:54 INFO: using dimension log file: ".\Demo\WWVhcnM=.dimension.log"
    06.07.2006 09:15:54 INFO: loading cube: ".\Demo\QnVyblJhdGVz.cube.xml"
    06.07.2006 09:15:54 INFO: loading cube data file: ".\Demo\QnVyblJhdGVz.cube.data"
    06.07.2006 09:15:54 INFO: using cube log file: ".\Demo\QnVyblJhdGVz.cube.log"
    06.07.2006 09:15:54 INFO: using dimension log file: ".\Demo\WWVhcnM=.dimension.log"
    06.07.2006 09:15:54 INFO: using dimension log file: ".\Demo\TW9udGhz.dimension.log"
    06.07.2006 09:15:54 INFO: using dimension log file: ".\Demo\UHJvamVjdHM=.dimension.log"
    06.07.2006 09:15:54 INFO: using dimension log file: ".\Demo\TWVhc3VyZXM=.dimension.log"
    06.07.2006 09:15:54 INFO: synchronizing storage ids
    06.07.2006 09:15:54 ERROR: SERVER MAIN: error loading data:
    Error code: -25
    0 id_maps_generate() [ id_map.c:0139]: element "FTEs" not found in dimension "Measures"
    1 cube_restore_data() [olap_cube_data.c:0598]: -
    2 load_cube() [ load.c:0466]: -
    3 load_database_simple() [ load.c:0240]: -
    4 load_database() [ load.c:0398]: -
    5 load_root_simple() [ load.c:0149]: -
    6 load_root() [ load.c:0189]: -
    7 load_data() [ main.c:0118]: -
    8 servermain() [ main.c:0282]: -

    06.07.2006 09:15:54 ERROR: SERVICE MAIN: server main failed!
    06.07.2006 09:15:54 INFO: MAIN: done - exiting...
  • RE: "Time out has expired ..." exception

    Hi!
    According to log there is a something wrong with the Demo database … you could try to backup and then delete complete <PALO_DIR>\data\Demo directory, then try again to start the service … Did you make any changes to the Demo DB and if so can you remember which?
    If the problem persists, then please post new palo.log.
    Mit freundlichen Gruessen/ With kind Regards / Meilleures salutations

    Vladislav Malicevic
    VP Development & Support
    Jedox AG
  • RE: "Time out has expired ..." exception

    Hello,
    we have with an installation the same problem. Time out has expired and not possibilty to start the service manually.
    I Tried to delete the Demo database but the service will not start. Also a repair and a reinstall of Palo don't fix the problem.
    I don't find continuative information to this Problem.
    I checked the palo.log but there are no entrees from today, only from yesterday where we tried to append a database.

    Thanks for your help.
    with kind regards
    Jochen