[SOLVED]Mismatched tag 'style' at login with admin user

[guillo]

I created a new agent with full admin permissions. But every time the agent tries to log in this error appears. If I remove the admin permits everything works fine.

It happens with the root user now

There are other agents with admin permissions and they log in with no problems.
Any ideas???

[guillo]

So the problem persits, I just gave up trying to log with the user. But now I can't seem to acces with the user ROOT.

Code: Select all

[Mon Sep 24 15:19:23 2012] -e: Use of uninitialized value in string eq at F:/PROGRA~1/OTRS/OTRS//Kernel/Modules/AgentTicketWatcher.pm line 58.
[Mon Sep 24 15:19:23 2012] -e: Use of uninitialized value in string eq at F:/PROGRA~1/OTRS/OTRS//Kernel/Modules/AgentTicketWatcher.pm line 58.
ERROR: OTRS-CGI-21 Perl: 5.12.3 OS: MSWin32 Time: Mon Sep 24 15:20:29 2012

 Message: C-Parser: 
not well-formed (invalid token) at line 904, column 36, byte 33146 at F:/Program Files/OTRS/StrawberryPerl/perl/vendor/lib/XML/Parser.pm line 187
!

 Traceback (4948): 
   Module: Kernel::System::XML::XMLParse (v1.105) Line: 755
   Module: Kernel::System::XML::XMLParse2XMLHash (v1.105) Line: 604
   Module: Kernel::Output::HTML::DashboardProductNotify::Run (v1.11) Line: 86
   Module: Kernel::Modules::AgentDashboard::_Element (v1.24) Line: 458
   Module: Kernel::Modules::AgentDashboard::Run (v1.24) Line: 307
   Module: Kernel::System::Web::InterfaceAgent::Run (v1.58.2.1) Line: 853
   Module: ModPerl::ROOT::ModPerl::Registry::F_3a_Program_20Files_OTRS_OTRS_bin_cgi_2dbin_index_2epl::handler (unknown version) Line: 49
   Module: (eval) (v1.89.2.1) Line: 204
   Module: ModPerl::RegistryCooker::run (v1.89.2.1) Line: 204
   Module: ModPerl::RegistryCooker::default_handler (v1.89.2.1) Line: 170
   Module: ModPerl::Registry::handler (v1.99) Line: 31

ERROR: OTRS-CGI-21 Perl: 5.12.3 OS: MSWin32 Time: Mon Sep 24 15:20:29 2012

 Message: XML::Parser produced errors. I use XML::Parser::Lite as fallback!

 Traceback (4948): 
   Module: Kernel::System::XML::XMLParse (v1.105) Line: 756
   Module: Kernel::System::XML::XMLParse2XMLHash (v1.105) Line: 604
   Module: Kernel::Output::HTML::DashboardProductNotify::Run (v1.11) Line: 86
   Module: Kernel::Modules::AgentDashboard::_Element (v1.24) Line: 458
   Module: Kernel::Modules::AgentDashboard::Run (v1.24) Line: 307
   Module: Kernel::System::Web::InterfaceAgent::Run (v1.58.2.1) Line: 853
   Module: ModPerl::ROOT::ModPerl::Registry::F_3a_Program_20Files_OTRS_OTRS_bin_cgi_2dbin_index_2epl::handler (unknown version) Line: 49
   Module: (eval) (v1.89.2.1) Line: 204
   Module: ModPerl::RegistryCooker::run (v1.89.2.1) Line: 204
   Module: ModPerl::RegistryCooker::default_handler (v1.89.2.1) Line: 170
   Module: ModPerl::Registry::handler (v1.99) Line: 31

[Mon Sep 24 15:20:29 2012] [error] [Mon Sep 24 15:20:29 2012] Lite.pm: mismatched tag 'style'\n

This is from the Apache log. I'm using IE8 (company policies) could this be a bug? since a nother user managed to log into the OTRS using OPERA, but after a couple of errors.

[crythias]

Are you certain this isn't a theme issue?

[guillo]

Are you certain this isn't a theme issue?

A theme Issue?? Can you explain a little bit more?

I just checked all my theme configurations and all are set to Default (standard), but I'm not sure if this is what you mean.

[crythias]

a theme ... as in the user's preferences are looking for a theme that is invalid.

[guillo]

a theme ... as in the user's preferences are looking for a theme that is invalid.

I double checked and all the agents have the same theme on their user preferences, including the root user.

I found a walkaround to log into the OTRS when the Mismatched Tag error appears:

1. After the error appears, I write the URL http://serveripaddress/otrs/index.pl and add ?Action=Admin next to the index.pl. This allows me to log onto the OTRS (it does not ask for password, like if it was already logged on), check configurations, create tickets, look for tickets etc, BUT I cannot check the dashboard or the Mismatched Tag 'style' error appears immediately. Weird huh?

[guillo]

As a side note, I' don't know if it has anything to do with this, but everytime I create a new agent, user root and root@localhost appears as default email

[jojo]

the prepopulation is a browser issue.

The mismatched tag comes from either the rss feed or the version check via http request. (I asume that you have a proxy in place which sends some error...)

[guillo]

If enter directly trough the server (localhost), where there is no proxy, the 'tag style error' still appears.

Is there any other reason?? I was wondering if this is an Apache error or a pearl error

[jojo]

OTRS (Server) tries to fetch some data from the internet. This data is changed byyour proxy

[guillo]

One last question, any idea why this happens only with the root and andmin users?

[jojo]

the dashlet checking for new OTRS versions is only configured for admin users

[guillo]

the dashlet checking for new OTRS versions is only configured for admin users

Thanks jojo for your help and time.

.. but, let me get this straight. From what you said: I understand there is a dashlet that checks for new OTRS versions, and this dashlet only works with admin users. So when a 'standard' user logs in, the dashlet does not run, therefore, the 'tag style error' does not appear.

In other words, what you are telling me is that the dashlet is the one that has a problem with the admin user. Did I understand you correctly? If so, what is this dashlet you are talking about? Where can I find it and check for configurations or errors.

[crythias]

The dashlets apparently are the OTRS news and OTRS releases.

[jojo]

You'll find it in Frontend:.Agent::Dashboard in Framework.

But the Dashlet is not the issue, the issue is the Proxy which changes data instead of giving the requested xml file

[guillo]

Ok thanks a lot to both of you.

It's fixed now, I went into the framework and deactivated the DashboardBackend###0000-ProductNotify, wich was configured for the admins only.

We've never used this and as I can see it is calling an XML file, just like you said: http://otrs.org/product.xml

We will definitely check why the proxy is blocking this.

Thanks JOJO, thanks Crythias.