Settings on my server:
Web root:
C:\inetpub\gspanel
Access to the entire deployment folder:
C:\Program Files\Gspanel
Error:
Could not load file or assembly 'System.Data.SQLite' or one of its dependencies. An attempt was made to load a program with an incorrect format.
Config file:
Code: Select all
<?xml version="1.0"?>
<!--
Note: As an alternative to hand editing this file you can use the
web admin tool to configure settings for your application. Use
the Website->Asp.Net Configuration option in Visual Studio.
A full list of settings and comments can be found in
machine.config.comments usually located in
\Windows\Microsoft.Net\Framework\v2.x\Config
-->
<configuration>
<appSettings>
<!--Do not remove any of these setting entries, even if they don't apply -->
<!--This setting defines where the logs, license requests, and the license for UGCC is stored -->
<add key="log" value="C:\inetpub\gspanel"/>
<!--dbtype can be mysql for a mysql backend or sqlite for sqlite backend. Use oledb (depreciated-not recommended/supported)
for oledb/mdb support -->
<add key="dbtype" value="mysql"/>
<!--If using sqlite, where can UGCC find the DB File-->
<add key="sqlitelocation" value="C:\program files\Gspanel\DB"/>
<!--If using oledb, where can UGCC find the DB File-->
<add key="mdblocation" value="C:\Program Files\Gspanel\DB"/>
<!--Following settings apply for mysql server only-->
<add key="sqlsrvr" value="localhost"/>
<add key="user" value="gsp"/>
<add key="password" value="**"/>
<add key="dbname" value="gspanel"/>
</appSettings>
<connectionStrings/>
<system.web>
<!--
Set compilation debug="true" to insert debugging
symbols into the compiled page. Because this
affects performance, set this value to true only
during development.
-->
<compilation debug="false"/>
<!--
The <authentication> section enables configuration
of the security authentication mode used by
ASP.NET to identify an incoming user.
-->
<authentication mode="Windows"/>
<!--
The <customErrors> section enables configuration
of what to do if/when an unhandled error occurs
during the execution of a request. Specifically,
it enables developers to configure html error pages
to be displayed in place of a error stack trace.
<customErrors mode="RemoteOnly" defaultRedirect="GenericErrorPage.htm">
<error statusCode="403" redirect="NoAccess.htm" />
<error statusCode="404" redirect="FileNotFound.htm" />
</customErrors>
-->
<customErrors mode="RemoteOnly"/>
</system.web>
</configuration>