Could not find any resources appropriate for the specified culture or the neutral culture.

Avatar
Matthew McBride
Follow

When I open my provisioning management site with SharePoint friendly error message turned off I get the following error:

Could not find any resources appropriate for the specified culture or the neutral culture.  Make sure "Resources.prov.resources" was correctly embedded or linked into assembly "App_GlobalResources.uqjgrnu7" at compile time, or that all the satellite assemblies required are loadable and fully signed.
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.

Exception Details: System.Resources.MissingManifestResourceException: Could not find any resources appropriate for the specified culture or the neutral culture.  Make sure "Resources.prov.resources" was correctly embedded or linked into assembly "App_GlobalResources.uqjgrnu7" at compile time, or that all the satellite assemblies required are loadable and fully signed.

Source Error:

An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below. 

Stack Trace:


[MissingManifestResourceException: Could not find any resources appropriate for the specified culture or the neutral culture.  Make sure "Resources.prov.resources" was correctly embedded or linked into assembly "App_GlobalResources.uqjgrnu7" at compile time, or that all the satellite assemblies required are loadable and fully signed.]
   System.Resources.ResourceManager.InternalGetResourceSet(CultureInfo culture, Boolean createIfNotExists, Boolean tryParents) +655
   System.Resources.ResourceManager.InternalGetResourceSet(CultureInfo culture, Boolean createIfNotExists, Boolean tryParents) +681
   System.Resources.ResourceManager.InternalGetResourceSet(CultureInfo culture, Boolean createIfNotExists, Boolean tryParents) +681
   System.Resources.ResourceManager.GetObject(String name, CultureInfo culture, Boolean wrapUnmanagedMemStream) +79
   System.Resources.ResourceManager.GetObject(String name, CultureInfo culture) +11
   System.Web.Compilation.BaseResXResourceProvider.GetObject(String resourceKey, CultureInfo culture) +86
   System.Web.Compilation.ResourceExpressionBuilder.GetResourceObject(IResourceProvider resourceProvider, String resourceKey, CultureInfo culture, Type objType, String propName) +20
   System.Web.HttpContext.GetGlobalResourceObject(String classKey, String resourceKey) +22
   SPSolutions.SharePoint.Provisioning.WebControls.ProvisioningMenuCustomizer.GetGlobalString(String className, String resourceKey) +11
   SPSolutions.SharePoint.Provisioning.WebControls.ProvisioningSiteActionsMenuCustomizer.BuildProvisioningSettingsMenu() +111
   SPSolutions.SharePoint.Provisioning.WebControls.ProvisioningSiteActionsMenuCustomizer.CreateChildControls() +34
   System.Web.UI.Control.EnsureChildControls() +87
   SPSolutions.SharePoint.Provisioning.WebControls.ProvisioningSiteActionsMenuCustomizer.OnLoad(EventArgs e) +15
   System.Web.UI.Control.LoadRecursive() +47
   System.Web.UI.Control.LoadRecursive() +131
   System.Web.UI.Control.LoadRecursive() +131
   System.Web.UI.Control.LoadRecursive() +131
   System.Web.UI.Control.LoadRecursive() +131
   System.Web.UI.Control.LoadRecursive() +131
   System.Web.UI.Control.LoadRecursive() +131
   System.Web.UI.Control.LoadRecursive() +131
   System.Web.UI.Control.LoadRecursive() +131
   System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +1061

Have more questions? Submit a request

1 Comments

Date Votes
  • 0
    Avatar
    Matthew McBride

    This error is caused when one ore more Site Provisioning Assistant resource files do not get properly deployed by the SharePoint. To correct the problem you can manually deploy the resource files to the correct IIS Virtual Directory location. To deploy the resource files manually following the steps below.

    1. On you SharePoint Web-Front-End Server navigate to 'C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\CONFIG\Resources'
    2. Copy the files 'prov.resx' and 'prov.en-US.resx'.
    3. Navigate to the IIS Virtual Directory of your SharePoint website
    4. Paste 'prov.resx' and 'prov.en-US.resx' into the Virtual Directory's App_GlobalResources folder
    5. Perform an IISRESET
    6. Refresh your page.

    Your issue should now be resolved.

    This issue is caused by an error with the SharePoint deployment engine. When SharePoint deploys resources to a Virtual Directory it places them in the .NET 1.1 resource directory and not the .NET 2.0 resource directory. SharePoint does not recognize the .NET 1.1 resource location and therefore presents the missing resource error. We have spoken with Microsoft regarding this issue but they don't seem to think the need to correct this issue is urgent. The Microsoft workaround to this problem is to perform an 'stsadm -o copyappbincontent' which is supposed to redeploy all of the resources to each Virtual Directory. We have experienced that in some situations this command doesn't always work correctly.

    Jeremy Luerkens
    Manager, Software Production
    SharePoint Solutions
Please sign in to leave a comment.