1. Home
  2. Knowledge Base
  3. On-premise/Customer-Hosted Server
  4. Customer-Hosted FAQ
  5. How To Fix Web Sign-In Not Working After a Server OS Upgrade.

How To Fix Web Sign-In Not Working After a Server OS Upgrade.

Update .NET Version

After performing an OS upgrade from 2012 R2 -> 2019 or similar, you may get the following error when trying to access the website afterward:

Server Error in ‘/’ Application. Configuration Error Description: An error occurred during the processing of a configuration file required to service this request. Please review the specific error details below and modify your configuration file appropriately.

Parser Error Message: The ‘targetFramework’ attribute in the element of the Web.config file is used only to target version 4.0 and later of the .NET Framework (for example, ”). The ‘targetFramework’ attribute currently references a version that is later than the installed version of the .NET Framework. Specify a valid target version of the .NET Framework, or install the required version of the .NET Framework.


This can happen because the version of .NET that came with the OS changed so that the prerequisite .NET framework for EIOBoard is no longer met by the Server. You can fix this by downloading the .NET 4.8 framework here:



If any other prerequisites are missing, you can find the whole list for the server prerequisites at this Knowledgebase article:

Minimum Requirements: What are the System Requirements and Server Specifications for the EIOBoard Server?


Active Directory

If you use Active Directory for login, make sure the Active Directory Settings are still the same or that the connection still works. There was a change in authentication with update 10.3.47 so if your upgrade goes past that point you may need to re-set it up

Active Directory login not working after a server upgrade

Active Directory Changes after version 10.3.47+


Database Version

If you receive the error message:

Error contacting Server. Please check your server settings and try again. @IPv4Address is not a parameter for procedure LoginCheck.

That error means the Database isn’t on the same version as the Server. You can check the dbo.versions table to check the Database version and upgrade it manually if it doesn’t match here:

Was this article helpful?

Related Articles

Need Support?

Can't find the answer you're looking for?
Contact Support