The resource object was not found

Avatar
Matthew McBride
Follow

I have just installed, deployed and configured ExCM per the instructions.  On the final step when I navigate to my external URL I get this error:

 

The resource object with key 'loginPageTitleInTitleArea' was not found.   at System.Web.Compilation.ResourceExpressionBuilder.ParseExpression(String expression, Type propertyType, ExpressionBuilderContext context)
   at System.Web.UI.BoundPropertyEntry.ParseExpression(ExpressionBuilderContext context)
   at System.Web.UI.ControlBuilder.FillUpBoundPropertyEntry(BoundPropertyEntry entry, String name)
   at System.Web.UI.ControlBuilder.AddBoundProperty(String filter, String name, String expressionPrefix, String expression, ExpressionBuilder expressionBuilder, Object parsedExpressionData, Boolean generated, String fieldName, String formatString, Boolean twoWayBound)
   at System.Web.UI.ControlBuilder.PreprocessAttribute(String filter, String attribname, String attribvalue, Boolean mainDirectiveMode)
   at System.Web.UI.ControlBuilder.PreprocessAttributes(ParsedAttributeCollection attribs)
   at System.Web.UI.ControlBuilder.Init(TemplateParser parser, ControlBuilder parentBuilder, Type type, String tagName, String id, IDictionary attribs)
   at System.Web.UI.ControlBuilder.CreateChildBuilder(String filter, String tagName, IDictionary attribs, TemplateParser parser, ControlBuilder parentBuilder, String id, Int32 line, VirtualPath virtualPath, Type& childType, Boolean defaultProperty)
   at System.Web.UI.TemplateParser.ProcessBeginTag(Match match, String inputText)
   at System.Web.UI.TemplateParser.ParseStringInternal(String text, Encoding fileEncoding)

 Any help is greatly appreciated.  My \Inetpub\wwwroot\wss\VirtualDirectories\myApp\App_GlobalResourcesand my C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\CONFIG\Resources directories appear to have the same content in them.

Have more questions? Submit a request

6 Comments

Date Votes
  • 0
    Avatar
    Matthew McBride

    Take a look at the troubleshooting help page at http://help.sharepointsolutions.com/products/excm/Troubleshooting_InvalidResource.html.

    There are 2 files that need to be copied from the 12 hive to the virtual directories - del.resx and deltempmem.resx. You can copy them directly or use the command stsadm -o copyappbincontent to copy all of the resource files out to all virtual directories. If this does not work, try to de-activate, then reactivate the features at the site and site collection levels and then run the stsadm command to make sure you have the latest versions of the resource files installed.

    David Fisher
    Software Engineer
    SharePoint Solutions
  • 0
    Avatar
    Matthew McBride

    I did all the steps that you suggested.  I am still seeing the error.  Anything else I can try?

  • 0
    Avatar
    Matthew McBride

    Unfortunately the resource 'loginPageTitleInTitleArea' is not an ExCM resource. It appears some other resource file is missing in your solution. I'm guess this error is occuring on the login page. Can yo confirm this assumption?

    I don't believe the out-of-the-box login page uses 'loginPageTitleInTitleArea' as a resource either. Is this a publishing site (using a custom login page) or has the login page been altered? I would recommend openning the login page and finding the resource reference to the 'loginPageTitleInTitleArea' resource key. It will look something like this...

    <%$ Resources:xxx,loginPageTitleInTitleArea %>

    The xxx values indicate which resources used to resolve the resource key. ExCM uses del and deltempmem. SharePoint typically uses wss and core. Other components may use other resources files. If you find the resource tag we can probably find isolate your issue.

    Jeremy Luerkens
    Manager, Software Production
    SharePoint Solutions
  • 0
    Avatar
    Matthew McBride

    Okay,getting closer to the problem.  I have the ECTS installed for another site.  The web.config was pointing to the login page that is deployed with that solution.  I repointed it to the login.aspx page at the root of the site, unfortunately I now receive a 401 error when going to the site externally.  I'm still tracking that down, but if you have any suggestions I'm all ears.  I did check all the known places for anonymous access allowed, and it is.

  • 0
    Avatar
    Matthew McBride

    The default login page is '/_layouts/login.aspx'. I'd start by making this page your default login page. This file resides in the layouts directory and is not subject to the same anonymous configuration requirements of a login page uploaded to your site with SharePoint Designer or by the publishing features. Once you get this working you should be able to confirm your anonymous settings from Site Settings -> Advanced Permissions -> Settings -> Anonymous Access. The anonymous access level set by this page will dictate how and where your login page can reside.

    Jeremy Luerkens
    Manager, Software Production
    SharePoint Solutions
  • 0
    Avatar
    Matthew McBride

    And I'm up and running, thanks for all the help :)

Please sign in to leave a comment.