Namespace Core.Agent could not be initialized

Moderator: crythias

Post Reply
User avatar
StefanP
OTRS newbie
Posts: 43
Joined: 14 Jan 2010, 18:16
OTRS Version?: 6.0.16
Real Name: Stefan
Company: Pachlina

Namespace Core.Agent could not be initialized

Post by StefanP » 13 Nov 2013, 12:51

Hello,

i tried to upgrade my OTRS 3.2.6 installation on an Windows 2003 R2 x32 Server with the paket otrs-3.3.1-win-installer-3.0.3.exe

The installation process works fine, but at the login window at OTRS following error occurs:
Namespace Core.Agent could not be initialized, because Core.UI.TreeSelection could not be found

Error details:
Core.Agent.Init is not a function

(?)()@http://ticket/otrs/index.pl:289
Core.App</TargetNS.Ready/<@http://ticket/otrs-web/js/js-cache/Comm ... 6a9.js:301
._Deferred/e.resolveWith@http://ticket/otrs-web/js/js-cache/Comm ... f6a9.js:33
f</<.ready@http://ticket/otrs-web/js/js-cache/Comm ... f6a9.js:33
f</C@http://ticket/otrs-web/js/js-cache/Comm ... f6a9.js:33

I can't login .... :(

In the past i deinstalled otrs completly and installed it again with restore of the database and config-file.
but with win-installer 3.0.3 a upgrade should work, right ?
Can someone help me out of that ?

thx
Stefan

badwurzach
OTRS newbie
Posts: 42
Joined: 07 Jan 2013, 21:02
OTRS Version?: 4.0.8

Re: Namespace Core.Agent could not be initialized

Post by badwurzach » 13 Nov 2013, 13:57

I have the same problem from 3.2.12 to 3.3.1. I used the installer, too.
Aktuell: OTRS6 CE (GIT), Ubuntu 18.04 LTS (with KeyHelp)

User avatar
StefanP
OTRS newbie
Posts: 43
Joined: 14 Jan 2010, 18:16
OTRS Version?: 6.0.16
Real Name: Stefan
Company: Pachlina

Re: Namespace Core.Agent could not be initialized

Post by StefanP » 13 Nov 2013, 14:00

a forgot to say that the web installer didnt start ... maybe thats ok, cause of upgrade.

btw: i'm wondering about this "Windows Upgrade" entry in OTRS 3.3 documentation.

Panter
OTRS newbie
Posts: 9
Joined: 12 Sep 2013, 14:39
OTRS Version?: 3.2.10
Real Name: sven

Re: Namespace Core.Agent could not be initialized

Post by Panter » 14 Nov 2013, 12:57

Bei mir auch das gleiche ..... ich gehe wieder auf die 3.2.11 :(

Mike_B
Moderator
Posts: 266
Joined: 12 Jan 2010, 18:16
OTRS Version?: CVS HEAD

Re: Namespace Core.Agent could not be initialized

Post by Mike_B » 27 Nov 2013, 21:24

Hi, please try again with the OTRS 3.3.2 / installer 3.0.4 release that has been made available earlier this week.
It fixes a LOT of issues related to upgrade:

Code: Select all

3.0.4 2013-11-26
- Extended upgrading proccess for minor and patch level upgrades.
    Including:
      database upgrades
      rebuild of otrs config
      deleting of otrs cache
      reinstallation of packages on patch level upgrades
      restarting micrsoft iis server (optional)
      removal of old framework files
- Removed short links.
- Fixed installer warnings.
- Fixed removing of services after uninstalling.
- Added workaround for Bug#10004 Can't connect to LDAP using StrawberryPerl on 3.3.1 to installer.
huntingbears.nl - @michielbeijen on Twitter

tomcek
OTRS newbie
Posts: 6
Joined: 19 Jun 2013, 17:10
OTRS Version?: 3.2.8

Re: Namespace Core.Agent could not be initialized

Post by tomcek » 28 Nov 2013, 12:34

Same error message if I try to install version 3.2.10 from source (Ubuntu 12.04 LTS).

Starting the webinstaller says:

Namespace Core.Agent could not be initialized, because Core.UI.TreeSelection could not be found

and more detailed:

Core.Agent is undefined

(?)()@http://mydomain/otrs/installer.pl:338
Core.App</TargetNS.Ready/<@http://mydomain/otrs-web/js/Core.App.js:72
._Deferred/e.resolveWith@http://mydomain/otrs-web/js/thirdparty/ ... query.js:2
f</<.ready@http://mydomain/otrs-web/js/thirdparty/ ... query.js:2
f</C@http://mydomain/otrs-web/js/thirdparty/ ... query.js:2


Has anybody an idea?

reneeb
OTRS guru
Posts: 4795
Joined: 13 Mar 2011, 09:54
OTRS Version?: 3.3.x
Company: Perl-Services.de
Contact:

Re: Namespace Core.Agent could not be initialized

Post by reneeb » 28 Nov 2013, 12:45

Anywhere in ZZZAuto.pm mentioned the old path to jquery or any other JS library? Then you have to update those paths...
Perl / OTRS development: http://perl-services.de
Free OTRS add ons from the community: http://opar.perl-services.de
Commercial add ons: http://feature-addons.de

tomcek
OTRS newbie
Posts: 6
Joined: 19 Jun 2013, 17:10
OTRS Version?: 3.2.8

Re: Namespace Core.Agent could not be initialized

Post by tomcek » 28 Nov 2013, 13:03

reneeb wrote:Anywhere in ZZZAuto.pm mentioned the old path to jquery or any other JS library? Then you have to update those paths...
Hi!

What do you mean exactly?

I do a fresh new install, I haven´t done any modification. The server is brand new too.

reneeb
OTRS guru
Posts: 4795
Joined: 13 Mar 2011, 09:54
OTRS Version?: 3.3.x
Company: Perl-Services.de
Contact:

Re: Namespace Core.Agent could not be initialized

Post by reneeb » 28 Nov 2013, 13:15

You said, you upgraded OTRS. Part of the upgrade process is to copy Kernel/Config/ZZZAuto.pm. If you have changed a setting like "Loader::Agent::CommonJS###000-Framework" the changed setting is stored in that ZZZAuto.pm. This config option contains paths to JavaScript libraries (e.g. "thirdparty/jquery-1.10.0/jquery.js") in your old OTRS version those paths were different. The setting in ZZZAuto.pm overrides the original 3.3.1 default values, so OTRS uses paths that doesn't exist anymore.

So you have to change that setting in ZZZAuto.pm to use the new paths...

If you haven't copied the old ZZZAuto.pm and/or you didn't change those settings I don't know why the error messages references to those outdated JavaScript libraries.
Perl / OTRS development: http://perl-services.de
Free OTRS add ons from the community: http://opar.perl-services.de
Commercial add ons: http://feature-addons.de

tomcek
OTRS newbie
Posts: 6
Joined: 19 Jun 2013, 17:10
OTRS Version?: 3.2.8

Re: Namespace Core.Agent could not be initialized

Post by tomcek » 28 Nov 2013, 14:36

reneeb wrote:You said, you upgraded OTRS.
No, I did a fresh install.

But problem solved ... restarting Apache :D

Post Reply