Unrecognised configuration section
Parser Error Message: Unrecognised configuration section 'connectionStrings',
The ASP.NET application may be an early .NET version, not version 4.6.
To correct this problem, use the Windows IIS Manager tool to check the site/virtual directory/application properties, and change the ASP.NET version to 4.6 (the exact method for choosing the ASP.NET version varies according to the version of IIS being used).
During set web.config file, the following error appears:
Error message: Extracting Themes on Website, This could take several minutes. A WebException occurred.
This means it is not possible to connect to the remote server.
Please check the web server is running.
Please check the URL is correct. An error occurred extracting themes.
Please check ASP.NET access rights with the internet service provider.
This means that the ASP.NET user account does not have full access rights to the web directory.
a)If the company is using a hosting provider, this means the account has not been set up correctly. Please contact them and advise that the ASP.NET user account needs write/delete access to the full website directory.
b)If hosting internally, please ask the web server administrator to set up the ASP.NET user account with write/delete access to the full website directory.
Cannot log on with users' web logons
There is a way to see if the users have been sent to the website via the eBusiness Transactions tab from within Jim2:
On the ribbon, go to eBusiness > eBusiness Transactions > Outbound Queue.
Select Include Processed Requests. Check the Last Processed date in the grid to see if anything has been published.
|
Generally speaking, when customers experience problems with the web based portal, the issue is often due to an upgrade of Jim2 having been performed but the Web Framework Installer has not been run after the upgrade.
Ensure the Jim2 Framework Installer is run after every Jim2 Server Upgrade. |
Further Information
Diagnosing Incoming Email Issues
Diagnosing Outgoing Email Issues
Jim2 Server Scheduled Backup Fails