Having an issue with getting web access config page to come out keep getting errors I was just wondering if the customer is going to need to have a 2012 server
Question
Question
is web access 10.2 compatible with windows server 2016
Replies
Supposedly Web Access 10 is verified to be working with 2016, were you able to get it working with an earlier dot version?
I did get it to pass the prereqs after I did a complete uninstall of IIS and web access. But when I launch the web access config page I get the following error.
HTTP Error 500.19 - Internal Server Error
The requested page cannot be accessed because the related configuration data for the page is invalid.
Detailed Error Information:
Module IIS Web Core
Notification BeginRequest
Handler Not yet determined
Error Code 0x8007000d
Config Error
Config File \\?\C:\Program Files\Laserfiche\Web Access\Web Files\web.config
Requested URL http://localhost:80/laserfiche/configuration/configuration.aspx
Physical Path C:\Program Files\Laserfiche\Web Access\Web Files\configuration\configuration.aspx
Logon Method Not yet determined
Logon User Not yet determined
Config Source:
-1:
0:
More Information:
This error occurs when there is a problem reading the configuration file for the Web server or Web application. In some cases, the event logs may contain more information about what caused this error.
View more information »
Hi James,
I'm sorry to hear you're having issues. I can confirm that Web Client 10.2+ supports Server 2016. We've tested on Server 2016 extensively and works for us, so OS version probably isn't the root cause here.
Have you tried repairing the install? The error you mentions invalid data in the config file stored here:
C:\Program Files\Laserfiche\Web Access\Web Files\web.config
Have you manually altered this file for some customization? You might want to try opening it in a text editor that supports color coding XML syntax, such as Notepad++ and Visual Studio, and see if you can spot any obvious invalid XML syntax.
Outside of that, I'd recommend opening a case with our support team. Please link to this thread and attach a copy of the faulty web.config file.