6.0.0-beta1
7/5/25

[#13335] Active sync administration raising a fatal error
Summary Active sync administration raising a fatal error
Queue Synchronization
Queue Version Git master
Type Bug
State Not A Bug
Priority 1. Low
Owners
Requester jerome (at) catrouillet (dot) net
Created 07/09/2014 (4014 days ago)
Due
Updated 07/09/2014 (4014 days ago)
Assigned
Resolved 07/09/2014 (4014 days ago)
Github Issue Link
Github Pull Request
Milestone 5.2.1
Patch No

History
07/09/2014 03:53:31 PM Michael Rubinsky State ⇒ Not A Bug
Priority ⇒ 1. Low
 
07/09/2014 01:20:01 PM jerome (at) catrouillet (dot) net Comment #5 Reply to this comment
Claiming the user for a poor error message seems not to be the best 
user-friendly approach...
07/09/2014 01:13:15 PM arjen+horde (at) de-korte (dot) org Comment #4 Reply to this comment
The UPGRADING document quite explicitly states that

     "The ActiveSync configuration section should be revisited."

If you decide to just go ahead and ignore this, the problem is all 
yours. As an administrator you should know better.
07/09/2014 12:36:57 PM jerome (at) catrouillet (dot) net Comment #3 Reply to this comment
In this case, the error message generated when trying to update the 
horde config file should be way better than the current one. It's just 
stating that it cannot update the config file... The best would be to 
state that new parameters are not set and open the config to the tab 
where are the missing parameters.
Straight from the annoucement message:

For upgrading instructions, please see
http://www.horde.org/apps/horde/docs/UPGRADING

You'll find that quite a few changes are listed for ActiveSync. Go 
to the ActiveSync tab in the horde configuration and fill in the 
missing parameters.
07/09/2014 10:41:54 AM arjen+horde (at) de-korte (dot) org Comment #2 Reply to this comment
Straight from the annoucement message:

For upgrading instructions, please see
http://www.horde.org/apps/horde/docs/UPGRADING

You'll find that quite a few changes are listed for ActiveSync. Go to 
the ActiveSync tab in the horde configuration and fill in the missing 
parameters.
07/09/2014 10:32:59 AM jerome (at) catrouillet (dot) net Comment #1
Priority ⇒ 2. Medium
Type ⇒ Bug
Summary ⇒ Active sync administration raising a fatal error
Queue ⇒ Synchronization
Milestone ⇒ 5.2.1
Patch ⇒ No
State ⇒ Unconfirmed
Reply to this comment
Hi,

Just upgraded my Horde 5.1.7 to Horde 5.2 final and during the upgrade 
through pear, I got this syslog message:
Message from syslogd@box1 at Jul  9 12:11:57 ...
  HORDE: [horde] Missing required state object [pid 29235 on line 122 
of "/usr/share/php/Horde/ActiveSync/Driver/Base.php"]
I updated the DB and config files expecting to fix the issue.

But I still got the syslog message happening again and again.

So I tried to clear all the active sync devices to start fresh but 
once I click on ActiveSync Devices I got this fatal error:
A fatal error has occurred

Call to a member function setLogger() on a non-object

1. Horde_ErrorHandler::catchFatalError()
Details

The full error message is logged in Horde's log file, and is shown 
below only to administrators. Non-administrative users will not see 
error details.

ErrorException Object
(
     [message:protected] => Call to a member function setLogger() on a 
non-object
     [string:Exception:private] =>
     [code:protected] => 0
     [file:protected] => /.../horde/admin/activesync.php
     [line:protected] => 25
     [trace:Exception:private] => Array
         (
             [0] => Array
                 (
                     [function] => catchFatalError
                     [class] => Horde_ErrorHandler
                     [type] => ::
                     [args] => Array
                         (
                         )

                 )

         )

     [previous:Exception:private] =>
     [severity:protected] => 1
     [logged] => 1
)

Saved Queries