FIXED: Error during ajax communication

Moderator: crythias

Locked
MWMeads
Znuny newbie
Posts: 24
Joined: 09 Mar 2012, 22:27
Znuny Version: 31000
Real Name: Tim
Company: Mountain West Telephone

FIXED: Error during ajax communication

Post by MWMeads »

When turning on the delete and reset change order links, I would get an error during ajax communication.

Looking in the apache logs, I see this:

[Mon Apr 30 16:02:19 2012] [error] [client 10.32.1.25] Module: /opt/otrs/bin/cgi-bin/index.pl (v1.90) Line: 46, referer: http://support1.*****/otrs/index.pl?Action=AgentITSMChangeZoom;ChangeID=2
[Mon Apr 30 16:02:19 2012] [error] [client 10.32.1.25] , referer: http://support1.*****/otrs/index.pl?Action=AgentITSMChangeZoom;ChangeID=2
[Mon Apr 30 16:32:05 2012] [error] [client 10.32.1.25] ERROR: OTRS-CGI-10 Perl: 5.12.4 OS: linux Time: Mon Apr 30 16:32:05 2012, referer: http://support1.*****/otrs/index.pl?Action=AgentITSMChangeZoom;ChangeID=2
[Mon Apr 30 16:32:05 2012] [error] [client 10.32.1.25] , referer: http://support1.*****/otrs/index.pl?Action=AgentITSMChangeZoom;ChangeID=2
[Mon Apr 30 16:32:05 2012] [error] [client 10.32.1.25] Message: Module Kernel::Modules::AgentITSMChangeDelete not registered in Kernel/Config.pm!, referer: http://support1.*****/otrs/index.pl?Action=AgentITSMChangeZoom;ChangeID=2
[Mon Apr 30 16:32:05 2012] [error] [client 10.32.1.25] , referer: http://support1.*****/otrs/index.pl?Action=AgentITSMChangeZoom;ChangeID=2
[Mon Apr 30 16:32:05 2012] [error] [client 10.32.1.25] Traceback (5025): , referer: http://support1.*****/otrs/index.pl?Action=AgentITSMChangeZoom;ChangeID=2
[Mon Apr 30 16:32:05 2012] [error] [client 10.32.1.25] Module: Kernel::System::Web::InterfaceAgent::Run (v1.64) Line: 731, referer: http://support1.*****/otrs/index.pl?Action=AgentITSMChangeZoom;ChangeID=2


The important error was:

Message: Module Kernel::Modules::AgentITSMChangeDelete not registered in Kernel/Config.pm!


I fixed this by going in and looking at the module registration inside the admin:SysConfig:ITSM Change Management:Frontend::Agent::ModuleRegistration

In this area, you have the additional options to load the modules.


This will work for an error pertaining to Module Kernel::Modules:: not registered in Kernel/Config.pm!
Locked