Namespace Core.Agent could not be initialized
Moderator: crythias
-
- Znuny newbie
- Posts: 46
- Joined: 14 Jan 2010, 18:16
- Znuny Version: 6.0.30
- Real Name: Stefan
- Company: Pachlina
Namespace Core.Agent could not be initialized
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
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
-
- Znuny newbie
- Posts: 45
- Joined: 07 Jan 2013, 21:02
- Znuny Version: 6.x
- Real Name: DW
Re: Namespace Core.Agent could not be initialized
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)
-
- Znuny newbie
- Posts: 46
- Joined: 14 Jan 2010, 18:16
- Znuny Version: 6.0.30
- Real Name: Stefan
- Company: Pachlina
Re: Namespace Core.Agent could not be initialized
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.
btw: i'm wondering about this "Windows Upgrade" entry in OTRS 3.3 documentation.
Re: Namespace Core.Agent could not be initialized
Bei mir auch das gleiche ..... ich gehe wieder auf die 3.2.11
Re: Namespace Core.Agent could not be initialized
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:
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
Re: Namespace Core.Agent could not be initialized
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?
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?
-
- Znuny guru
- Posts: 5018
- Joined: 13 Mar 2011, 09:54
- Znuny Version: 6.0.x
- Real Name: Renée Bäcker
- Company: Perl-Services.de
- Contact:
Re: Namespace Core.Agent could not be initialized
Anywhere in ZZZAuto.pm mentioned the old path to jquery or any other JS library? Then you have to update those paths...
Perl / Znuny development: http://perl-services.de
Free Znuny add ons from the community: http://opar.perl-services.de
Commercial add ons: http://feature-addons.de
Free Znuny add ons from the community: http://opar.perl-services.de
Commercial add ons: http://feature-addons.de
Re: Namespace Core.Agent could not be initialized
Hi!reneeb wrote:Anywhere in ZZZAuto.pm mentioned the old path to jquery or any other JS library? Then you have to update those paths...
What do you mean exactly?
I do a fresh new install, I haven´t done any modification. The server is brand new too.
-
- Znuny guru
- Posts: 5018
- Joined: 13 Mar 2011, 09:54
- Znuny Version: 6.0.x
- Real Name: Renée Bäcker
- Company: Perl-Services.de
- Contact:
Re: Namespace Core.Agent could not be initialized
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.
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 / Znuny development: http://perl-services.de
Free Znuny add ons from the community: http://opar.perl-services.de
Commercial add ons: http://feature-addons.de
Free Znuny add ons from the community: http://opar.perl-services.de
Commercial add ons: http://feature-addons.de
Re: Namespace Core.Agent could not be initialized
No, I did a fresh install.reneeb wrote:You said, you upgraded OTRS.
But problem solved ... restarting Apache