install problems

Post here for help with installing or upgrading mojoPortal pre-compiled release packages. When posting in this forum, please provide all relevant details. You may also want to review the installation or upgrading documentation.

If you have questions about using the source code or working with mojoPortal in Visual Studio, please post in the Developer forum.

Post here for help with installation of mojoPortal pre-compiled release packages

When posting in this forum, please try to provide as many relevant details as possible. Particularly the following:

  • What operating system were you running when the bug appeared?
  • What database platform is your site using?
  • What version of mojoPortal are you running?
  • What version of .NET do you use?
  • What steps are necessary to reproduce the issue? Compare expected results vs actual results.

You may also want to review the installation or upgrading documentation.

If you have questions about using the source code or working with mojoPortal in Visual Studio, please post in the Developer forum.

This thread is closed to new posts. You must sign in to post in the forums.
11/30/2006 5:23:51 AM
Gravatar
Total Posts 10

Re: install problems

here's what i did i've uploaded all of the files under the root folder to a subdomain, next i made sure that all files and folders have the 777 permissions.

Under the other subdomain for the mssql i do have that file, while for the mysql one that file does not exist. what do you mean by type a space in web.config.

i'll try to set the port and see what happens.

Thanks, Al
11/30/2006 5:34:17 AM
Gravatar
Total Posts 18439

Re: install problems

Are you hosted on linux or windows? mojoportal 2.x only works on windows
I ask because of the way you describe the folder permissions as 777 which seems more linux way of doing things than windows.

What I mean about type a space in web.config is in asp.net you can force the application to recycle by modifiying the web.config file, it just needs the timestamp modified so adding a space and re-upload web.config will do this.

When you have an error and you make a configuration change to fix the error (ie fix the folder permissions), you need to recycle the app to  clear the cache and make sure it starts up correctly

Hope it helps,

Joe

ps, I am about to go to a meeting in an hour and after that I'm on the road for 8 hours so may not be able to help much more today
11/30/2006 5:37:13 AM
Gravatar
Total Posts 10

Re: install problems

its alright i'm doing something else anyway, we are hosted on a windows, well that's what the host said anyway, i'll have my bro fix this he's the dotnet guru in the family i'm more of a designer

thanks, al
12/1/2006 4:27:54 AM
Gravatar
Total Posts 10

Re: install problems

i was trying to add the store procedures throuh ASP.NET Enterprise Manager and while i was doing so i got this error:


Server Error in '/MSSQL' Application.
A potentially dangerous Request.Form value was detected from the client (sqlstmt="... Author: <Author,,Name>
-- C...").
Description: Request Validation has detected a potentially dangerous client input value, and processing of the request has been aborted. This value may indicate an attempt to compromise the security of your application, such as a cross-site scripting attack. You can disable request validation by setting validateRequest=false in the Page directive or in the configuration section. However, it is strongly recommended that your application explicitly check all inputs in this case.

Exception Details: System.Web.HttpRequestValidationException: A potentially dangerous Request.Form value was detected from the client (sqlstmt="... Author: <Author,,Name>
-- C...").

Source Error:

The source code that generated this unhandled exception can only be shown when compiled in debug mode. To enable this, please follow one of the below steps, then request the URL:

1. Add a "Debug=true" directive at the top of the file that generated the error. Example:

<%@ Page Language="C#" Debug="true" %>

or:

2) Add the following section to the configuration file of your application:

<configuration>
<system.web>
<compilation debug="true"/>
</system.web>
</configuration>

Note that this second technique will cause all files within a given application to be compiled in debug mode. The first technique will cause only that particular file to be compiled in debug mode.

Important: Running applications in debug mode does incur a memory/performance overhead. You should make sure that an application has debugging disabled before deploying into production scenario.

Stack Trace:

[HttpRequestValidationException (0x80004005): A potentially dangerous Request.Form value was detected from the client (sqlstmt="... Author: <Author,,Name>
-- C...").]
System.Web.HttpRequest.ValidateString(String s, String valueName, String collectionName) +3219534
System.Web.HttpRequest.ValidateNameValueCollection(NameValueCollection nvc, String collectionName) +108
System.Web.HttpRequest.get_Form() +119
System.Web.HttpRequest.get_HasForm() +57
System.Web.UI.Page.GetCollectionBasedOnMethod(Boolean dontReturnNull) +2025185
System.Web.UI.Page.DeterminePostBackMode() +60
System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +6953
System.Web.UI.Page.ProcessRequest(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +154
System.Web.UI.Page.ProcessRequest() +86
System.Web.UI.Page.ProcessRequestWithNoAssert(HttpContext context) +18
System.Web.UI.Page.ProcessRequest(HttpContext context) +49
ASP.app_query_aspx.ProcessRequest(HttpContext context) +29
System.Web.CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() +154
System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously) +64


Version Information: Microsoft .NET Framework Version:2.0.50727.42; ASP.NET Version:2.0.50727.210




Thanks, Al
12/1/2006 5:13:51 AM
Gravatar
Total Posts 18439

Re: install problems

Hi Al,

This error is happening in the ASP.NET Enterprise Manager at your host, it has nothing to do with mojoPortal or the mojoportal sql script so I'm not really the support person for that. However, it is a common error in general in ASP.NET applications. The answer to fix it is right in the message:

"Description: Request Validation has detected a potentially dangerous client input value, and processing of the request has been aborted. This value may indicate an attempt to compromise the security of your application, such as a cross-site scripting attack. You can disable request validation by setting validateRequest=false in the Page directive or in the configuration section. However, it is strongly recommended that your application explicitly check all inputs in this case."

You have to modify either the web.config or the page directive in your ASP.NET Enterprise Manager to get it to work.

More info here:
http://www.asp.net/faq/requestvalidation.aspx

Or just google for asp.net requestvalidation

Hope it helps,

Joe
12/1/2006 5:19:07 AM
Gravatar
Total Posts 10

Re: install problems

Thanks Joe,

I really needed you opinion first before i start talking to them.

Al
You must sign in to post in the forums. This thread is closed to new posts.