QESTNET Internal:Developer Setup QESTField: Difference between revisions

Latest revision as of 01:26, 8 February 2016

QESTField

Open ~\qestnet\QESTField MVC\QESTField.sln
- If the solution does not load, check that .NET Framework 4.5 and ASP.NET MVC 4 are installed on your local machine. Use the Visual Studio 2012 CD to repair the installation.
Build the solution. There should not be any errors
Go to Debug > Exceptions
- Find System.ServiceModel.FaultException`1
- Uncheck User-unhandled.
  This will stop the debugger breaking on a fault exception catch every time you login. It is on a "to do" list somewhere to fix... really I (DL) promise.
Start Debugging (F5).
This will launch a web browser. The choice of web browser is configured in Visual Studio where Start Debugging is.
Google Chrome is the recommended choice for QESTField development. The browser will take you to the web address of a local ASP.NET Development Server which Visual Studio has spun up. The login page of QESTField should be displayed.
You can login using any QESTLab login credentials which are available in the database and have permission to use QESTField.

Potential Errors

Error	Solution
Error: "Underlying service failed to Open."	Check the Event Viewer log. It is normally due to the QESTNET service credentials not having permission to access the QESTLab database.
Error: "No connection could be made because the target machine actively refused it 127.0.0.1:52525."	The QESTNET service is not running. Ensure the service is running in Control Panel -> Services.
Error: "A project with an Output Type of Class Library cannot be started directly."	Right-click the project "QESTField" in the Solution Explorer and select "Set as StartUp Project"
When you log into QESTField, an AJAX error message is sent with the title: "The filestore directory does not exist: C:\NEEDSTOEXIST"	This directory is the storage location QESTField will use. To change the directory, edit the following line in the app.config file for the project QESTNET.Service\QESTNET: <add key="fileStorePath" value="C:\NEEDSTOEXIST" /> Then, rebuild QESTNET.Service and restart the QESTNET service.
Cannot log into QESTField, below error message is displayed for any username/password. "An error occurred while preparing the command definition. See the inner exception for details"	QESTLab_Data.Views are no longer up to date if the message says 'model no longer matches'- Generate Data Schema Or, If this does not help, Cleaning the bin folders and rebuilding QESTField fixed the issue. C:\dev\qestnet\QESTNET\bin\Debug C:\dev\qestnet\QESTField MVC\QESTField\bin

@@ Line 7: / Line 7: @@
 **Uncheck '''User-unhandled'''.<BR> This will stop the debugger breaking on a fault exception catch every time you login. It is on a "to do" list somewhere to fix... really I (DL) promise.
 *Start Debugging ('''F5'''). <BR>This will launch a web browser. The choice of web browser is configured in Visual Studio where Start Debugging is. <BR>Google Chrome is the recommended choice for QESTField development. The browser will take you to the web address of a local ASP.NET Development Server which Visual Studio has spun up. The login page of QESTField should be displayed. <BR>You can login using any QESTLab login credentials which are available in the database and have permission to use QESTField.
-**Error: "Underlying service failed to Open." - Check the Event Viewer log. It is normally due to the QESTNET service credentials not having permission to access the QESTLab database.
+====Potential Errors====
+{| class="wikitable"
+!Error
+!Solution
+|-
+|Error: "Underlying service failed to Open."
+|Check the Event Viewer log. It is normally due to the QESTNET service credentials not having permission to access the QESTLab database.
+|-
+|Error: "No connection could be made because the target machine actively refused it 127.0.0.1:52525."
+|The QESTNET service is not running. Ensure the service is running in Control Panel -> Services.
+|-
+|Error: "A project with an Output Type of Class Library cannot be started directly."
+|Right-click the project "QESTField" in the Solution Explorer and select "Set as StartUp Project"
+|-
+|When you log into QESTField, an AJAX error message is sent with the title: "The filestore directory does not exist: C:\NEEDSTOEXIST"
+|This directory is the storage location QESTField will use. To change the directory, edit the following line in the app.config file for the project QESTNET.Service\QESTNET:
+:&lt;add key="fileStorePath" value="<span style="color:#0000FF">C:\NEEDSTOEXIST</span>" /&gt;
+Then, rebuild QESTNET.Service and restart the QESTNET service.
+|
+|-
+|Cannot log into QESTField, below error message is displayed for any username/password.<BR> "An error occurred while preparing the command definition. See the inner exception for details"
+|
+QESTLab_Data.Views are no longer up to date if the message says 'model no longer matches'- Generate Data Schema Or,
+If this does not help,
+Cleaning the bin folders and rebuilding QESTField fixed the issue.
+C:\dev\qestnet\QESTNET\bin\Debug<BR>
+C:\dev\qestnet\QESTField MVC\QESTField\bin
+|}