An exception occurred while initializing module 'Site'
So have a 3.8/1.5 configuration running under the identity Network Service (as we utilise LDAP security config).
I have a number of sites which were migrated successfully from previous versions, can be edited & viewers launched without any issues.
However, while i'm able to create a NEW site & add a viewer I get the following error upon viewer startup:
An exception occurred while initializing module 'Site'.
- The exception message was: Site module Uri configuration is missing.
- The Assembly that the module was trying to be loaded from was:Geocortex.EssentialsSilverlightViewer.CoreModules, Version=1.5.0.743, Culture=neutral, PublicKeyToken=2279c6c155d3316f
Check the InnerException property of the exception for more information. If the exception occurred while creating an object in a DI container, you can exception.GetRootException() to help locate the root cause of the problem.
Microsoft.Practices.Prism.Modularity.ModuleInitializeException: An exception occurred while initializing module 'Site'.
- The exception message was: Site module Uri configuration is missing.
- The Assembly that the module was trying to be loaded from was:Geocortex.EssentialsSilverlightViewer.CoreModules, Version=1.5.0.743, Culture=neutral, PublicKeyToken=2279c6c155d3316f
Check the InnerException property of the exception for more information. If the exception occurred while creating an object in a DI container, you can exception.GetRootException() to help locate the root cause of the problem.
---> System.InvalidOperationException: Site module Uri configuration is missing.
at Geocortex.EssentialsSilverlightViewer.CoreModules.Site.SiteModule.Initialize(ModuleConfiguration moduleConfiguration)
at Geocortex.EssentialsSilverlightViewer.Infrastructure.Modularity.ViewerModule.Initialize()
at Microsoft.Practices.Prism.Modularity.ModuleInitializer.Initialize(ModuleInfo moduleInfo)
--- End of inner exception stack trace ---
at Microsoft.Practices.Prism.Modularity.ModuleInitializer.HandleModuleInitializationError(ModuleInfo moduleInfo, String assemblyName, Exception exception)
at Microsoft.Practices.Prism.Modularity.ModuleInitializer.Initialize(ModuleInfo moduleInfo)
at Microsoft.Practices.Prism.Modularity.ModuleManager.LoadModulesThatAreReadyForLoad()
at Microsoft.Practices.Prism.Modularity.ModuleManager.IModuleTypeLoader_LoadModuleCompleted(Object sender, LoadModuleCompletedEventArgs e)
at Microsoft.Practices.Prism.MefExtensions.Modularity.MefXapModuleTypeLoader.RaiseLoadModuleCompleted(LoadModuleCompletedEventArgs e)
at Microsoft.Practices.Prism.MefExtensions.Modularity.MefXapModuleTypeLoader.HandleDownloadCompleted(DeploymentCatalog deploymentCatalog, AsyncCompletedEventArgs e)
at Microsoft.Practices.Prism.MefExtensions.Modularity.MefXapModuleTypeLoader.DeploymentCatalog_DownloadCompleted(Object sender, AsyncCompletedEventArgs e)
at System.ComponentModel.Composition.Hosting.DeploymentCatalog.OnDownloadCompleted(AsyncCompletedEventArgs e)
at System.ComponentModel.Composition.Hosting.DeploymentCatalog.HandleOpenReadCompleted(Object sender, OpenReadCompletedEventArgs e)
at System.Net.WebClient.OnOpenReadCompleted(OpenReadCompletedEventArgs e)
at System.Net.WebClient.OpenReadOperationCompleted(Object arg)
I also notice my map services (secured) are randomly loosing there configuration (password) details for the site.
Any suggestions what is going on here as this is a simple test site.
Brad
-
I am also noticing that my map connection details are dropping randomly on a working (migrated) site?? The issue is resolved by re-entering security details (my map services are secured) but this is worrying that they are loosing them in the first place?
Brad
0 -
Brad,
Part of the error message "Site module Uri configuration is missing." indicates that the Viewer.xml that was created for your viewer was not saved correctly. Have a look at the Viewer.xml file and you'll probably see that the <SiteUri> element is empty. This is normally set by Manager when you save. It sounds like the Manager application has permission to create files in the Sites directory, but is perhaps not able to modify certain existing files. You may see a message to that effect in the Manager Logs.
--Ryan
0 -
Ryan,
Thanks for tip, i was under the impression this was a permissions issue.
So, increasing the permissions for the Network Service user for the sites folder to include 'write' has addressed the issue.
HOWEVER what has changed between 3.5 & 3.8 to make this a requirement (I have both 3.5 & 3.8 running on my test server & I do not get this issue on the 3.5 installation).
I'm intrigued as to why the network service user requires this permission since isn't it the identity of the manager (App Pool: EssentialsAdministrationAppPool4 (Identity: EssentialsAdmin)) making the changes on the config files (site.xml/viewer.xml)). Appreciate the REST sites are running under NetworkService identity (in my case).
Are able to join the dots of the above process to help me better understand what is happening in the background.
I've also just discovered this post in the knowledge base (presumably relatively new as I've not seen it before): http://support.geocortex.com/file-permissions-for-geocortex-essentials-rest-elements. I however am querying the permissions outlined based on my experience above (e.g. I've had to permit the identity that the sites are running under (Network Service) to include the 'write' permissions; My EssentialsAdmin identity remains as-is from a default installation & thus has default settings (full control for sites folder). OR should i be considering changing the identity upon which manager is running under (I don't see any justification why i should do this)?
Appreciate if you are able to clarify the queries above (I do appreciate permissions can be a tricky topic given the dependencies on your setup) as i don't like having to second guess when it comes to production deployments which i will need to be doing shortly.
Brad
0 -
Hi Brad,
We haven't made any permissions changes to the installer between 3.5 and 3.8.
From what you described it sounds as if your RestManager application is running under EssentialsAppPool4 rather than EssentialsAdministrationAppPool4. That would explain why the change to the NetworkService permissions suddenly made RestManager work.
We generally don't recommend that you change the identity used by RestManager unless there is some very specific network or security issue that requires it.
--Ryan
0 -
Ryan,
I won't push this too far via a forum thread (can escalate to support call if necessary), but i wish to confirm (as indicated below), the RestManager site is running under the EssentialsAdminstrationAppPool4. This is (without repeating the install) is default configuration as i understand. I run the REST site under a custom AppPool under Nework Service identify.
My queries below are therefore still valid. Intrigued as to what is going on to cause the anomaly.
Brad
0
Du måste logga in om du vill lämna en kommentar.
Kommentarer
5 kommentarer