Re: [otrs] OTRS 3.3 question - How to figure out problem data???

Hi Charles, Please try the following: Make sure you have all the Needed and Proposed perl modules (Specially for YAML) you can use the CheckModules script to know the status (this might change from version to version (mayor) so run it every time you made a mayor version update). Make sure all perl modules are on the latest version. Then open the Dynamic Field configuration for the ones that you use in the Dashboard Calendar (or all if the error still), try to modify a value in the lower part of the screen (Not in the General section), this should force to re-write the YAML content (hopefully with he correct format), you can revert the changes back once it is saved (saving again but with the configuration you had before). If you still have this issue, you might consider to get commercial support, for that you can contact our sales department at sales@otrs.com. Update to OTRS 4 or 5 is strongly recommended as OTRS 3.3 is only supported for security issues. ((enjoy)) Carlos Rodríguez

On Jul 8, 2016, at 4:47 PM, Lambrecht, Charles wrote:

Hello OTRS List,

I just upgraded to OTRS 3.3 and am working on cleaning up any issues before upgrading to 4 and then 5.

Occasionally I see the error message below in the system log and further details are in the apache error log. After searches and reading, I understand I have some data in my config files that didn’t get upgraded properly or converted when upgrading and usually it is related to dynamic fields. Our OTRS instance is pretty generic (no customizations), but has been upgraded over the past ten years through various versions and most recently to 3.3. Everything is working, but the occasional error message *bugs* me.

I’ve reviewed settings, but everything looks good.

I’m looking for pointers on how to identify the problem field!

From the apache error log (and this usually happens when an agent logs in but can happen when changing screens – the user doesn’t get an error message)

ERROR: OTRS-CGI-10 Perl: 5.10.1 OS: linux Time: Fri Jun 24 15:28:55 2016 Message: Data was only readable pure-perl YAML module, please contact the System Administrator to update this record, as the stored data is still in a wrong format!

RemoteAddress: (deleted)

RequestURI: /otrs/index.pl?Action=AgentDashboard

Traceback (24865): Module: Kernel::System::YAML::Load (OTRS 3.3.15) Line: 150 Module: Kernel::System::DynamicField::DynamicFieldGet (OTRS 3.3.15) Line: 311 Module: Kernel::System::DynamicField::DynamicFieldListGet (OTRS 3.3.15) Line: 965 Module: Kernel::Output::HTML::DashboardEventsTicketCalendar::new (OTRS 3.3.15) Line: 43 Module: Kernel::Modules::AgentDashboardCommon::_Element (OTRS 3.3.15) Line: 789 Module: Kernel::Modules::AgentDashboardCommon::Run (OTRS 3.3.15) Line: 569 Module: Kernel::System::Web::InterfaceAgent::Run (OTRS 3.3.15) Line: 915 Module: ModPerl::ROOT::ModPerl::Registry::opt_otrs_bin_cgi_2dbin_index_2epl::handler (unknown version) Line: 41 Module: (eval) (v1.99) Line: 204 Module: ModPerl::RegistryCooker::run (v1.99) Line: 204 Module: ModPerl::RegistryCooker::default_handler (v1.99) Line: 170 Module: ModPerl::Registry::handler (v1.99) Line: 31

Regards, Charles Lambrecht --------------------------------------------------- Charles Lambrecht Computer Operations Manager UT College of Veterinary Medicine cgl@utk.edu mailto:cgl@utk.edu ---------------------------------------------------

--------------------------------------------------------------------- OTRS mailing list: otrs - Webpage: http://otrs.org/ http://otrs.org/ Archive: http://lists.otrs.org/pipermail/otrs http://lists.otrs.org/pipermail/otrs To unsubscribe: http://lists.otrs.org/mailman/listinfo/otrs http://lists.otrs.org/mailman/listinfo/otrs