AyaNovaWBI encountered an unexpected problem

What happened

• There was an unexpected error in the AyaNovaWBI web site.  This may be due to a programming bug or installation / configuration problem.

How this will effect you

• The current page will not load or continue processing the last operation.

What you can do about it

• Close this page and try repeating your last action.  Try alternative methods of performing the same action.  If problems persist contact AyaNova support via the AyaNova technical support forum.  Be sure to provide a copy of the support information below in your support request and a detailed description of the scope of the problem and what steps led to it.

Support information

And I just tried again less than a minute and is working the same workorder I am able to view it. That is exactly what is doing, sometimes you cannot access it, and few minutes later or hours later you are able to view the work order or add work order. Should I change to SQL?

I would suggest checking the following:

1. From your other topic posting, the database is located on an E:\ - is this a different harddrive from where the Firebird Server is installed to?
2. I would recommend checking the server where the database, IIS / WBI is running on - check what is happening such as is it overloaded, low on memory, etc
3. If Firebird is too slow, than yes, moving to SQL would increase speed - but do note that SQL requires a higher end server due to the processing / memory requirements of SQL

- Joyce

AyaNova Sales & Technical Support

http://www.ayanova.com

2. I just chekced the event viewer and this is what I found, exactly at the same time my client tried to access the web and a few minutes ago when I tried.

Event Type: Warning
Event Source: ASP.NET 2.0.50727.0
Event Category: Web Event
Event ID: 1309
Date:  6/18/2007
Time:  12:15 PM
User:  N/A
Computer: NOVASVR
Description:
Event code: 3003
Event message: A validation error has occurred.
Event time: 6/18/2007 12:15:44 PM
Event time (UTC): 6/18/2007 4:15:44 PM
Event ID: 6c70123cd8c14ffa891c252dc2c0e8d1
Event sequence: 15
Event occurrence: 1
Event detail code: 0
 
Application information:
    Application domain: /LM/W3SVC/1/ROOT/NovaWebService-2-128266438322812500
    Trust level: Full
    Application Virtual Path: /NovaWebService
    Application Path: C:\inetpub\wwwroot\NovaWebService\
    Machine name: NOVASVR
 
Process information:
    Process ID: 2308
    Process name: w3wp.exe
    Account name: NT AUTHORITY\NETWORK SERVICE
 
Exception information:
    Exception type: HttpRequestValidationException
    Exception message: A potentially dangerous Request.Form value was detected from the client (edDetails="...          <comehomeorlando.com...").
 
Request information:
    Request URL: http://67.78.169.34/novawebservice/ClientServiceRequestEdit.aspx?clientid=5318515f-7436-490c-bc92-95e015e21e9f
    Request path: /novawebservice/ClientServiceRequestEdit.aspx
    User host address: 71.41.113.254
    User: Vilma Sosa
    Is authenticated: True
    Authentication Type: CSLA
    Thread account name: NT AUTHORITY\NETWORK SERVICE
 
Thread information:
    Thread ID: 1
    Thread account name: NT AUTHORITY\NETWORK SERVICE
    Is impersonating: False
    Stack trace:    at System.Web.HttpRequest.ValidateString(String s, String valueName, String collectionName)
   at System.Web.HttpRequest.ValidateNameValueCollection(NameValueCollection nvc, String collectionName)
   at System.Web.HttpRequest.get_Form()
   at System.Web.HttpRequest.get_HasForm()
   at System.Web.UI.Page.GetCollectionBasedOnMethod(Boolean dontReturnNull)
   at System.Web.UI.Page.DeterminePostBackMode()
   at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)
   at System.Web.UI.Page.ProcessRequest(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)
   at System.Web.UI.Page.ProcessRequest()
   at System.Web.UI.Page.ProcessRequestWithNoAssert(HttpContext context)
   at System.Web.UI.Page.ProcessRequest(HttpContext context)
   at ASP.clientservicerequestedit_aspx.ProcessRequest(HttpContext context)
   at System.Web.HttpApplication.CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute()
   at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously)
 
 
Custom event details:

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

3. My Server Specifications are as follow:

Intel Pentium 4 2.4Ghz

1Gb Memory

160Gb Hard Drive (C and D Drive)

Windows Small Business Server 2003

Could you send the following information directly to support@ayanova.com and we will take a look and get back to you as soon as possible.

URL to your WBI

Client username and password to log in

Exactly what was selected, entered etc to obtain that error above (I realize I may not get that error right now - but it is extremely important that I receive exactly what was done to recreate) - provide the exact workorder, any text entered, etc

Thank you

AyaNova Sales & Technical Support

http://www.ayanova.com

Thank you for sending the informaiton. Such a message usually occurs because text is being entered that IIS (your Microsoft Internet Information Service) is identifying as potentially dangereous - and therefore prevents the text from going through. For example, text entered with < > around it. If you have to enter text that uses the < > symbols, do the following; otherwise refrain from using those symbols:

1. Open up the Web.config using NotePad (do not use any other editor) for WBI, and add the following line

  <pages validateRequest="false" />

between the  <system.web> and </system.web>. For example, add as a line just above </system.web> such as below

 
 <!--/AyaNova specific-->
 
 <system.web>
  <!-- Assembly references, do not modify this section unless directed to do so by technical support -->
  <compilation>
   <assemblies>
    <add assembly="System.Runtime.Remoting, Version=2.0.0.0, Culture=neutral, PublicKeyToken=B77A5C561934E089"/>
    <add assembly="System.Data.OracleClient, Version=2.0.0.0, Culture=neutral, PublicKeyToken=B77A5C561934E089"/>
    <add assembly="System.Windows.Forms, Version=2.0.0.0, Culture=neutral, PublicKeyToken=B77A5C561934E089"/>
    <add assembly="System.Design, Version=2.0.0.0, Culture=neutral, PublicKeyToken=B03F5F7F11D50A3A"/>
    <add assembly="System.Security, Version=2.0.0.0, Culture=neutral, PublicKeyToken=B03F5F7F11D50A3A"/>
    <add assembly="Microsoft.VisualC, Version=8.0.0.0, Culture=neutral, PublicKeyToken=B03F5F7F11D50A3A"/>
    <add assembly="System.Configuration, Version=2.0.0.0, Culture=neutral, PublicKeyToken=B03F5F7F11D50A3A"/>
    <add assembly="System.Data, Version=2.0.0.0, Culture=neutral, PublicKeyToken=B77A5C561934E089"/>
    <add assembly="System, Version=2.0.0.0, Culture=neutral, PublicKeyToken=B77A5C561934E089"/>
    <add assembly="System.Xml, Version=2.0.0.0, Culture=neutral, PublicKeyToken=B77A5C561934E089"/>
    <add assembly="System.Drawing, Version=2.0.0.0, Culture=neutral, PublicKeyToken=B03F5F7F11D50A3A"/>
    <add assembly="System.EnterpriseServices, Version=2.0.0.0, Culture=neutral, PublicKeyToken=B03F5F7F11D50A3A"/>
    <add assembly="System.Runtime.Serialization.Formatters.Soap, Version=2.0.0.0, Culture=neutral, PublicKeyToken=B03F5F7F11D50A3A"/>
    <add assembly="Infragistics2.WebUI.WebSchedule.v6.3, Version=6.3.20063.53, Culture=neutral, PublicKeyToken=7dd5c3163f2cd0cb" />
           <add assembly="Infragistics2.WebUI.Shared.v6.3, Version=6.3.20063.53, Culture=neutral, PublicKeyToken=7dd5c3163f2cd0cb" />
   </assemblies>
  </compilation>
  <!--Compression - Do not modify unless directed to do so by technical support-->
  <httpModules>
   <add name="CompressionModule" type="blowery.Web.HttpCompress.HttpModule, blowery.web.HttpCompress"/>
  </httpModules>
  <!--/Compression-->
  <!--Security and error handling, DO NOT CHANGE-->
  <authentication mode="Forms">
   <forms name="WBILogin" loginUrl="login.aspx" protection="All" timeout="999999" />
  </authentication>
  <authorization>
   <deny users="?"/>
  </authorization>
  <customErrors mode="Off" defaultRedirect="~/HandleError.aspx">
   <error statusCode="404" redirect="~/stub.aspx"/>
  </customErrors>
  <!-- / Security and error handling-->
   <pages validateRequest="false" />
 </system.web>

 <!--

2. Save the Web.config file

3. Restart IIS (or reboot the entire machine)

4. Once rebooted, log into WBI and check out the same workorder where was getting the issue, or create a new service request with the exact same text as previously.

Let me know the result. If you have an issue, do be sure to attach a zipped copy of the edited Web.config as well as details of what is occurring. Thank you

- Joyce

AyaNova Sales & Technical Support

http://www.ayanova.com