[SOLVED] Namespace Core.Customer could not be initialized.

Moderator: crythias

Post Reply
DenisBY
Moderator
Posts: 54
Joined: 19 Aug 2010, 08:33
Znuny Version: 3.0 CVS
Location: Minsk, Belarus

[SOLVED] Namespace Core.Customer could not be initialized.

Post by DenisBY »

I'm using latest 3.0 CVS. after today's update in the middle of day (I have GMT +2) I'm start to receive errors like this in dialog box:
In CI:

Code: Select all

Namespace Core.Customer could not be initialized, because Core.UI could not be found.

or in AI:

Code: Select all

Namespace Core.Form.Validate could not be initialized, because Core.UI.Dialog could not be found.
how to fix it? is it a bug in my installation or in general?
Last edited by DenisBY on 24 Aug 2010, 09:32, edited 1 time in total.
OTRS 3.0 SVN, CentOS, MySQL, Lotus LDAP for Agents and Customers. Production (Yes, I'm crazy).
Orson
Znuny newbie
Posts: 11
Joined: 21 Feb 2008, 10:10
Znuny Version: 2.4.6

Re: Namespace Core.Customer could not be initialized.

Post by Orson »

Same Problem after Installing OTRS 3.0.0 beta 2.
otrs 2.4.6 auf debian lenny 5.0.4
otrs 3.0.0 beta 2 auf debian lenny 5.0.4 (testsystem)
Orson
Znuny newbie
Posts: 11
Joined: 21 Feb 2008, 10:10
Znuny Version: 2.4.6

Re: Namespace Core.Customer could not be initialized.

Post by Orson »

Seam to be a problem with access-rights. Files exists in folder otrs/var/httpd/htdocs/js .
otrs 2.4.6 auf debian lenny 5.0.4
otrs 3.0.0 beta 2 auf debian lenny 5.0.4 (testsystem)
Orson
Znuny newbie
Posts: 11
Joined: 21 Feb 2008, 10:10
Znuny Version: 2.4.6

Re: Namespace Core.Customer could not be initialized.

Post by Orson »

On the OTRS-Site is the solution.

run ./bin/otrsRebuildConfig.pl

is the solution
otrs 2.4.6 auf debian lenny 5.0.4
otrs 3.0.0 beta 2 auf debian lenny 5.0.4 (testsystem)
hughkelley
Znuny newbie
Posts: 3
Joined: 23 Aug 2010, 21:20
Znuny Version: 3.0

Re: [SOLVED] Namespace Core.Customer could not be initialize

Post by hughkelley »

I encountered this issue when I tried to cheat and carry over a ZZZAuto.pm module from Beta1 to Beta2 (skipping the export/import). Using a proper SysConfig export and import worked fine.

See http://lists.otrs.org/pipermail/otrs/20 ... 33212.html for details
Post Reply