Overview
When creating new sites in a DNN environment, you may encounter issues where the PortalLanguages table does not populate, leading to incomplete site settings. This can be caused by misconfigurations, missing database triggers, or incomplete installation processes. Additionally, file crawler failures can contribute to broader functionality problems. This article provides steps to troubleshoot and resolve these issues, including checking localization settings, updating the DNN environment, and ensuring proper file permissions.
Information
To resolve issues with the PortalLanguages table not populating during site creation in DNN, follow these steps:
-
Verify Localization Settings:
- Ensure that the default language is properly configured in the
Languagestable. - Run the following SQL query to check the default language:
SELECT * FROM Languages WHERE IsDefault = 1; - If no default language is set, update it with:
UPDATE Languages SET IsDefault = 1 WHERE CultureCode = 'en-US'; -- Replace 'en-US' with your desired default language
- Ensure that the default language is properly configured in the
-
Check File Crawler Functionality:
- Access the Event Viewer in the DNN Persona Bar to check for error logs related to the file crawler.
- Ensure that file permissions for DNN directories are correctly configured, with the application pool identity in IIS having read/write access.
- Restart the application pool and clear the DNN cache.
-
Database Comparison:
- Use a database comparison tool to compare key tables (
PortalSettings,Tabs,PortalAlias,Modules,PortalLocalization) between production and non-production environments to identify discrepancies.
- Use a database comparison tool to compare key tables (
-
Update or Reinstall DNN:
- Consider updating DNN to the latest version or reinstalling the current version to ensure all components are correctly configured.
- Backup your database and files before proceeding with an update or reinstallation.
-
Manual Table Update:
- If necessary, manually insert missing entries into the
PortalLanguagestable using SQL queries, ensuring thePortalIDmatches the site in question.
- If necessary, manually insert missing entries into the
By following these steps, you can address the issues with site creation and ensure proper functionality within your DNN environment.
Frequently Asked Questions
- What causes the
PortalLanguagestable not to populate during site creation? - This issue can be caused by misconfigurations, missing database triggers, or incomplete installation processes. Ensuring proper localization settings and default language configurations can help resolve it.
- How can I check if the default language is set in DNN?
- Run the SQL query
SELECT * FROM Languages WHERE IsDefault = 1;to check the default language. If not set, update it usingUPDATE Languages SET IsDefault = 1 WHERE CultureCode = 'en-US';. - What should I do if the file crawler is not running successfully?
- Check the Event Viewer for error logs, ensure correct file permissions, restart the application pool, and clear the DNN cache. These steps can help resolve file crawler issues.
Priyanka Bhotika
Comments