Server errors (Could not locate & SYS0270)

Hi,


I have a couple of java errors popping up consistently. I am guessing that these mean something fundamental is wrong with the mysource install, it is beyond forum type help, and I will need to talk to Squiz NZ about them. this post is really just confirming that and hoping it is not a big issue.



The first error box pops up whenever I go into simple edit mode. It is a simple three line error box:



Error

Could not locate asset (#<assestid of asset being edited>)

(OK button)



e.g. Screenshot example



This error doesn’t seem to cause any harm and isn’t stopping us doing anything we need to at this point.



The second error we are getting is a little nastier. I only get this error in the admin interface and I have to reload to duplicate it, but it happens every time I repeat these steps.



If I try to open System Managment > Authentiction Systems I get a rather long error message pop up saying that mysource has failed an assert exception (SYS0270)



Screenshot example



It then removes the expansion option next to the Authentication Systems item and doesn’t allow me to try opening it again until I reload the whole admin interface (at which point I get the same error)



This is a fairly major issue as it means I am unable to hook up our ldap bridge as an authentication source.



So I guess my question is are either of these things something that forum help can get fixed up?



Ryan

You need contact Support: Your install is missing the IPB package, but the IPB Authentication asset has been installed. This is the cause of the second problem.


The first error is due to the fact that the asset map is trying to expand to the current asset but is probably being blocked by permissions. Make sure the users have at least read access to any folders or other assets between the root and the site.

That doesn't sound anywhere near as fatal as I was expecting. Am waiting for a call back from Craig about some other things so I will also talk to him about ipb.


As for the simple edit problem, I get the same thing happening if I log in as root. And even if I try to edit the homepage I get the same issue. The homepage is a child of a site asset at the root of the mysource install. Public users have read access to both the homepage and the site asset. Do specific users/groups also need read access or should public read access be enough?

No, that should be enough. We'll have to look elsewhere. I'd resolve your authentication issues first and then see if the other problem persists.

[quote]No, that should be enough. We’ll have to look elsewhere. I’d resolve your authentication issues first and then see if the other problem persists.
[right][post=“15412”]<{POST_SNAPBACK}>[/post][/right][/quote]





I’ve been experiencing this as well - we’ve given read permissions to our master user group which contains all other editor’s user groups at the top level of all of our sites.



Its an annoyance but doesnt block editing - although occasionally we’ve noticed the asset map won’t expand. It is also more prevalent if a root node is specified for a user group, but that is not always the case - some user groups have no root node in their preferences and still get the error.



In our case the ‘cannot locate asset’ error always refers to the Site asset.

[quote]In our case the ‘cannot locate asset’ error always refers to the Site asset.
[right][post=“15415”]<{POST_SNAPBACK}>[/post][/right][/quote]



I’m sure this was an issue in an older version of Matrix that has been since fixed.

[quote]No, that should be enough. We’ll have to look elsewhere. I’d resolve your authentication issues first and then see if the other problem persists.
[right][post=“15412”]<{POST_SNAPBACK}>[/post][/right][/quote]



I have now sorted out the IPB issue.



However the “Could not locate asset” issue is still there.

[quote]However the “Could not locate asset” issue is still there.
[right][post=“15439”]<{POST_SNAPBACK}>[/post][/right][/quote]



Again, I would log this with support so that they can check this.