This stack trace is a bit unusual. Have you performed any customisations on your MantisBT instance, e.g. removed the default filter?

No, I have a standard installation of Mantis and have not done any customizations.

The database has been updated several times, since the instance was setup in 2008.

I'm very unhappy with this Stacktrace since it gives me no clue where to point the problem ...

The stack trace ends at http://git.mantisbt.org/?p=mantisbt.git;a=blob;f=api/soap/mc_filter_api.php;h=a265e981830049558089e113e5ca97d481f3adb6;hb=162c0d27022a889ad92a6354fbeac35b2ffc2761#l26

I can see that it calls mci_filter_db_get_available_queries and by examining the function I guess that $t_filter_detail is not properly formed ( http://git.mantisbt.org/?p=mantisbt.git;a=blob;f=api/soap/mc_api.php;h=b84de9dfd5fcf356cf32f7286ee7c0613d0250cc;hb=162c0d27022a889ad92a6354fbeac35b2ffc2761#l268 ) . Can you provide some more details about this filter?

I hope I unstand you corretly: You guess the Filter-String ist not "wellformed"!?

The defined Filers used have standard-strings as names. To ensure this is not the Problem I deleted all Filters and got the same Error.

Yes, that was my intuition. What interests me is the filter_string column.

I have printed all the filter-strings into stderr. To me they dont look unusual.

Example: v8#a:41:{s:8:"_version";s:2:"v8";s:10:"_view_type";s:6:"simple";s:8:"per_page";i:50;s:17:"highlight_changed";i:6;s:13:"sticky_issues";b:1;s:4:"sort";s:12:"last_updated";s:3:"dir";s:4:"DESC";s:8:"platform";a:
1:{i:0;i:0;}s:2:"os";a:1:{i:0;i:0;}s:8:"os_build";a:1:{i:0;i:0;}s:10:"project_id";a:1:{i:0;i:-3;}s:11:"start_month";s:2:"06";s:9:"start_day";i:1;s:10:"start_year";s:4:"2011";s:9:"end_month";s:2:"06";s:7:"end
_day";s:2:"28";s:8:"end_year";s:4:"2011";s:6:"search";s:0:"";s:16:"and_not_assigned";b:0;s:17:"do_filter_by_date";b:0;s:10:"view_state";s:0:"";s:17:"relationship_type";i:-1;s:16:"relationship_bug";i:0;s:14:"
target_version";a:1:{i:0;s:1:"0";}s:10:"tag_string";s:0:"";s:10:"tag_select";s:0:"";s:13:"show_category";a:1:{i:0;i:0;}s:13:"show_severity";a:1:{i:0;i:0;}s:11:"show_status";a:1:{i:0;i:0;}s:11:"reporter_id";a
:1:{i:0;i:0;}s:10:"handler_id";a:1:{i:0;i:0;}s:12:"note_user_id";a:1:{i:0;i:0;}s:15:"show_resolution";a:1:{i:0;i:0;}s:13:"show_priority";a:1:{i:0;i:0;}s:10:"show_build";a:1:{i:0;i:0;}s:12:"show_version";a:1:
{i:0;i:0;}s:11:"hide_status";a:1:{i:0;i:90;}s:16:"fixed_in_version";a:1:{i:0;i:0;}s:12:"user_monitor";a:1:{i:0;i:0;}s:12:"show_profile";a:1:{i:0;i:0;}s:13:"custom_fields";a:1:{i:1;a:1:{i:0;i:0;}}}

Yes, that one looks fine. Can you single out the row which causes the error?

I'm not a PHP-Coder ... can you give me a Hint how to singe it out? Is there an Exception I my catch or is it simply the last line?

Just before

$t_filter_detail = explode( '#', $row['filter_string'], 2 );

add something like

file_put_contents("/tmp/debug.log", "Read filter with id ".$row['id']);

Thnx to your Help I was able to find and solve the Problem.

One of the Filters had no filter_string. I don't know why but deleting this filter solved the Problem-

Thank you very much for your Help.

OK, thanks for confirming. I will still need to handle this in the SOAP API though, so I'll keep the task open.

Marking as 'acknowledged' not resolved/closed to track that change gets ported to master-2.0.x branch