Error when opening the "Catalog" addon in CMS

Erik Täck

Vote:

So we have two machines, both running the same code, and they uses the same database(s) and they both point to the same appdata folder.

On one machine (my own computer), the Catalog in CMS works fine, but on our test machine, we get a script error when starting it, so it will not work at all, this happens on the URL '/episerver/Commerce/Catalog' line 67, where the function parser.parse() is called. What can possibly be wrong here cause I am sure there is some error somewhere on the server or related, but there is nothing apart from this crypptic dojo error. So everything else works perfectly fine, even using catalog items (ex. products) as blocks and editing them after they have been placed, tis just the "Catalog" (that has the link above) that throws this error.

dojo/parser::parse() error Error {stack: "Error: Could not resolve dependency "epi.storeregi…ll/3.0.1209/ClientResources/dojo/parser.js:2:8935", message: "Could not resolve dependency "epi.storeregistry" (epi.dependency)"} parser.js:2

(anonymous function)parser.js:2
_2e9dojo.js:3661
then._2f6.thendojo.js:3776
lang.extend.otherwisedojo.js:3873
_1b.parseparser.js:2
(anonymous function)Catalog:67
_c6dojo.js:608
_36dojo.js:689
(anonymous function)dojo.js:713
_37dojo.js:697
_7bdojo.js:708
_e8dojo.js:746
_11css.js:2
_2fload-css.js:2
_27load-css.js:2
_1a._1c.(anonymous function)._1c.(anonymous function)load-css.js:2

#81566

Feb 19, 2014 14:58

Erik Täck

Vote:

Forgot version numbers, everything installed from the latest version available in nuget feed, there are no updates available for any of the relevant addons either:

#81568

Feb 19, 2014 15:08

Thomas Hjorth

Vote:

I'm experiencing the exact same thing here on one of our development machines :(

#81697

Feb 24, 2014 12:50

Erik Täck

Vote:

I manged to solve it (sort of), by completely wiping the site root of the dev machine and deploying everything again. Only thing I can think of is that there was a wrong version of a dll in the "modulesbin" folder, but I am not 100% sure what exactly solved the problem (or what the problem even was in the first place).

#81698

Feb 24, 2014 12:59

Mads Storm Hansen

Vote:

We saw the same issue on a developer machine that did not have EPiServer installed in "C:\Program Files\..."

http://world.episerver.com/Modules/Forum/Pages/Thread.aspx?id=78804&epslanguage=en

#81702

Feb 24, 2014 14:59

Erik Täck

Vote:

Hmm, that might be related. The machine did indeed lack the Episerver commerce module installation in program files at one point (it had episerver installed). Though it still showed the same error after installing the commerce module installer, might have been a combination of issues.

#81704

Feb 24, 2014 15:13