in

Dotnetpanel Forums

Community support forums for DotNetPanel products

The request failed with HTTP status 400: Bad Request.

Last post 07-02-2009 6:22 AM by Michael G. 2 replies.
Page 1 of 1 (3 items)
Sort Posts: Previous Next
  • 07-01-2009 5:30 AM

    The request failed with HTTP status 400: Bad Request.

    Hi I am new to this product so please forgive basic questions. I am testing the trial install of the product on a VMware test environment as I do not want to have any character building events on the production system.

    Aside from a domain controller I have one mailbox server and one client access / hub server in the test setup. I have tried to load the DNP Enterprise server, DNP server and DNP portal server on to the client access / hub server for starters but I get the error below when I try to connect via the portal on the server itself. The machine names are all resolvable locally via AD DNS and I have uninstalled and reinstalled a few times with the same result.

    This install is using SQL 2005 Express on the actual box the production will use and external SQL server. I’ve tried both Windows and SQL authentication.

    I think I have the basics correct re IIS and all the DNP components installed without any error messages. i have not installed any DNP modules on the other boxes yet. 

    The host is 64 bit Windows 2003 server service pack 2 with Exchange 2007 service pack 2

    This is the error message: Server Error in '/' Application. The request failed with HTTP status 400: Bad Request. Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.

    Exception Details: System.Net.WebException: The request failed with HTTP status 400: Bad Request.

    Source Error:

    An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.


    Stack Trace:

     

    [WebException: The request failed with HTTP status 400: Bad Request.]   System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage message, WebResponse response, Stream responseStream, Boolean asyncCall) +1981   System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object[ parameters) +307   DotNetPanel.EnterpriseServer.esAuthentication.IsLicensesAvailable(String[ types) +77   DotNetPanel.Portal.LicensingHelper.IsEnterpriseServerLicensed() +376   DotNetPanel.Portal.LicensesSiteMapFilter.AddPage(PortalPage page) +121   DotNetPanel.WebPortal.PortalConfiguration.ParsePagesRecursively(String path, SiteStructure site, XmlNodeList xmlPages, PortalPage parentPage) +3538   DotNetPanel.WebPortal.PortalConfiguration.LoadPagesFromXml(SiteStructure site, String path) +283   DotNetPanel.WebPortal.PortalConfiguration.get_Site() +297   DotNetPanel.WebPortal.DefaultPage.Page_Init(Object sender, EventArgs e) +102   System.Web.Util.CalliHelper.EventArgFunctionCaller(IntPtr fp, Object o, Object t, EventArgs e) +25   System.Web.Util.CalliEventHandlerDelegateProxy.Callback(Object sender, EventArgs e) +58   System.Web.UI.Control.OnInit(EventArgs e) +127   System.Web.UI.Page.OnInit(EventArgs e) +16   System.Web.UI.Control.InitRecursive(Control namingContainer) +517   System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +1518
     

    Version Information: Microsoft .NET Framework Version:2.0.50727.235; ASP.NET Version:2.0.50727.235

     

  • 07-02-2009 5:59 AM In reply to

    • GrZeCh
    • Top 10 Contributor
    • Joined on 04-25-2007
    • Poland
    • Posts 651

    Re: The request failed with HTTP status 400: Bad Request.

     I think you should check DNP Server configuration (DNP Server configuration IP should be equal to IP which you are using to access DNP Server WebService)

    DotNetPanel 2.8.14
  • 07-02-2009 6:22 AM In reply to

    Re: The request failed with HTTP status 400: Bad Request.

    Thank you for the suggestion. I think you’re on the right track.

    I got it to work late this evening after 2 days of fun by removing the domain definition (left empty) which was pointed to the web server on the same system. I tried playing with host headers which did not fix it but I then found a post suggesting you can install without defining the domain detail. After the panel page came up and let me logon. Smile

    Tomorrow I will try to deploy to the other system and see how this system works.

    I had a side issue of the myLittleAdmin  package also did not work. There are instructions on the DNP site to fix that issue on IIS7 but not IIS6. I found the solution to that one here.  http://forum.mylittleadmin.com/yafnet/Default.aspx?g=posts&t=87 I’ve not tested if that has broken anything on the Exchange side of things yet.

    Thanks again

     

Page 1 of 1 (3 items)
Powered by Community Server (Commercial Edition), by Telligent Systems