Exchange 2013 CU7 OWA 400 Bad Request after successful login

Scenario:
Exchange 2007/2013 Migration
One
Exchange 2007 Server [removed]
One
Exchange 2013 Server Std, Windows 2012
All mailboxes moved to 2013
- November 27-30 2014
All public folders moved to
2013 - December 2, 2014
Exchange
2007 is still running and has not been removed from the domain, yet. [update]
Exchange
2007 removed from domain - 12-13-14
SSL
Certs are current for: Autodiscover.ExtDom.com, ex13.ExtDom.com, ex13.IntDom.com
Applied
CU6 (Dec 3, 2014) to fix Mobile access issues. Since applying CU6, OWA does not work with the exception of mobile browsers (Chrome - Nexus 7) or Safari 5.1.7 on Windows 7. These browsers get the OWA 2010 theme (Yellow).
User
logs into OWA with Domain\UserName and PWD(IE). After clicking Sign In, page returns Bad Request. No errors logged in w3scv logs.
[update]
CU7 applied 12-11-2014
All
users can connect using Outlook 2013 or Mobile (iPhone & Android)
Exchange
Admin Center (ECP) still works!
Browsers
tested: IE10 (windows 7 x64),Chrome 39.0.2171.71m, Opera 26.0, FireFox 34.0.5, Safari 5.1.7
Attempted:
https://ex13.ExtDom.com/owa
https://ex13.IntDom.com/owa
https://ex13.ExtDom.com/owa?ExchClientVer=15
https://ex13.IntDom.com/owa?ExchClientVer=15
https://localhost/owa
(on Ex 2013 server)
https://localhost/owa?ExchClientVer=15
(on Ex 2013 Server)
Fixes
attempted:
remove
| create Virtual Directories for OWA
Change
authentication through Exchange PowerShell - Integrated/Basic from FBA/Basic
reverted
since change didn’t work.
Run
UpdateCas.ps1
Run
UpdateConfigFiles.ps1
IISReset
(iisReset /NoForce fails)
OWA
(Default Web Site) displays as Version 15.0 (Build 995.29) in EAC. [update] Build 1044.25 (CU7)
Links
used for troubleshooting:
http://community.spiceworks.com/topic/514617-exchange-2013-unable-to-login-to-owa-ecp
https://social.technet.microsoft.com/Forums/ie/en-US/f8aa95d4-19e4-483c-8c4b-b039ab0d0127/400-bad-request-when-logging-in-to-owa-exchange-2013?forum=exchangesvrclients
http://tecfused.com/2013/09/23/exchange-2013-ecp-double-login-error-400/
https://social.technet.microsoft.com/Forums/lync/en-US/c25ce81c-76ea-471a-93ae-eeaf9e5015ac/exchange-2013-owa-error-400-bad-request?forum=exchangesvradmin
http://support.microsoft.com/kb/2871485/en-gb

Hi,
Does it work if you disable the FBA and only use the basic authentication?
Please also let us know the authentication settings on the Default Web site.
Thanks,
Simon Wu
TechNet Community Support

Similar Messages

400 bad request error after Firefox 4.0.1 update

After the latest Firefox update, the browser no longer works. When I try to go to a web site, Firefox sends the URL incorrectly by repeating the url. For example: if I type the url http://my.yahoo.com/, I get the following error:
400 Bad Request
Your browser sent a request that this server could not understand:
my.yahoo.comhttp://my.yahoo.com/ (port 80)

Thank you again for your help. After clearing the cache and cookies, and still having the problem, I uninstalled/reinstalled firefox. I had tried this before, but allowed it to keep my bookmarks, etc.. This time I had it remove everything (this is a check-box when doing the uninstall).
After reinstalling Firefox this time, the problem went away. Thank you for your help. Your comment about the cache and cookies, made me think that removing all information during the uninstall would help, and it did.
I don't know if your second suggestion would have helped, because it is now fixed.
But I believe it was a possibility.

Test-ActiveSyncConnectivity fails with The remote server returned an error: (400) Bad Request.

Hi all,
I'm on the process of transition from Exchange 2003 to 2010, everything is going perfectly alright however ActiveSync is bugging me!
when I try to test activesync I get the following error:
[PS] C:\>Test-ActiveSyncConnectivity -MailboxCredential $user -TrustAnySSLCertificate |FL
RunspaceId : 136b8f68-26ec-4e29-a5bb-cf5ee816e04b
LocalSite : SITE
SecureAccess : True
VirtualDirectoryName :
Url :
UrlType : Unknown
Port : 0
ConnectionType : Plaintext
ClientAccessServerShortName : cas01
LocalSiteShortName : SITE
ClientAccessServer : CASSERVERNAME
Scenario : Options
ScenarioDescription : Issue an HTTP OPTIONS command to retrieve the Exchange ActiveSync protocol version.
PerformanceCounterName :
Result : Success
Error :
UserName : user1
StartTime : 12/12/2012 1:02:23 PM
Latency : 00:00:00.0312496
EventType : Success
LatencyInMillisecondsString : 31.25
Identity :
IsValid : True
RunspaceId : 136b8f68-26ec-4e29-a5bb-cf5ee816e04b
LocalSite : Reckon_NS
SecureAccess : True
VirtualDirectoryName :
Url :
UrlType : Unknown
Port : 0
ConnectionType : Plaintext
ClientAccessServerShortName : CASSERVERNAME
LocalSiteShortName : SITE
ClientAccessServer : CASSERVERNAME
Scenario : FolderSync
ScenarioDescription : Issue a FolderSync command to retrieve the folder hierarchy.
PerformanceCounterName : DirectPush Latency
Result : Failure
Error : [System.Net.WebException]: The remote server returned an error: (400) Bad Request.
HTTP response headers:
MS-Server-ActiveSync: 6.5.7638.1
Content-Length: 46
Cache-Control: private
Content-Type: text/html
Date: Wed, 12 Dec 2012 02:02:23 GMT
Server: Microsoft-IIS/7.5
X-AspNet-Version: 2.0.50727
X-Powered-By: ASP.NET
UserName : user1
StartTime : 12/12/2012 1:02:23 PM
Latency : -00:00:01
EventType : Error
LatencyInMillisecondsString :
Identity :
IsValid : True
environment:
Ex 2003 'Exchange' virtual directory permission: Integrated Windows Authentication, Basic
Ex 2003 'OMA' permission: Basic Authentication
Ex 2003 'ActiveSync' permission: Integrated, Basic
Ex 2010 successfully redirects users from 2010 to 2003 webmail if you login to OWA with a mailbox on 2003

Yes Martina,
It has been done through ESM
I cannot test using testexchangeconnectivity.com since I cannot put the 2010 one into production, I will get into trouble if I change the DNS record to the new mail server!
Yes, EAS works perfectly fine with 2010 mailboxes.
OK.
It might be that it's not possible to run Test-ActiveSyncConnectivity against a mailbox stored in Exchange 2003.
Installing KB937031 and enabling Windows Authentication is really all that needs to be done in EX03, in order for Exchange 2010 to proxy the EAS requests.
Martina Miskovic

Internal Autodiscover - 400 Bad Request

I am having an issue with our internal autodiscover.
At the moment we have 2010 and 2013 in coexistance. Our autodiscover record in DNS points to the CAS array of Exchange 2010. If I do a test-webservicesconnectivity for a user in Exchange 2013, I get an Error 400 Bad Request reply.
How can I fix this?

Hi snorri788,
Exchange 2013 doesn't use CAS Arrays as there is no MAPI support except via RPC/HTTP which doesn't use the CAS Array object in 2010 either.
Besides, Outlook client finds AutoDiscover also by using SCP first for internal access. If it not success, then turn to DNS.
For your question, please run following command to double check the result of Test-WebServicesConnectivity:
Test-WebServicesConnectivity -ClientAccessServer CAS01 –AutoDiscoverServer CAS01
Note: please try to add a DNS record and point Autodiscover record to Exchange 2013 CAS.
Additional, please pay attention to below article about Step-by-Step Exchange 2007 to 2013 Migration, for your reference:
http://blogs.technet.com/b/meamcs/archive/2013/07/25/part-2-step-by-step-exchange-2007-to-2013-migration.aspx
Best Regards,
Allen Wang

Workflow manager IIS site throws a 403 Forbidden error and published workflows throw an error 400 bad request

Hello All , Request your help on the below issue ,
We have a single server farm SP 2013 where workflow was working as expected but its broken now , Not sure
what caused this. Workflow manager is installed alongside Service Bus. Workflow Manager client is installed on the same SP server.
We are able to create and publish the workflows from SP Designer without errors but when we start the workflow from SharePoint list we get an error " Sorry something went wrong". We have tried creating new workflows but the same problem.
We receive the below error in event viewer.
Error processing management request. Method: PUT, RequestUri: http://server URL:12291/$Workflows/89c767d2-82d2-4bd9-8e5e-dcace81d844f, Error: System.ArgumentException: The remote server returned an error: (400) Bad Request. ---> System.Net.WebException:
The remote server returned an error: (400) Bad Request.
at System.Net.HttpWebRequest.EndGetResponse(IAsyncResult asyncResult)
at Microsoft.ServiceBus.Messaging.ServiceBusResourceOperations.GetAsyncResult`1.EndGetResponse(GetAsyncResult`1 thisPtr, IAsyncResult ar)
at Microsoft.ServiceBus.Messaging.IteratorAsyncResult`1.StepCallback(IAsyncResult result)
--- End of inner exception stack trace ---
Server stack trace:
Exception rethrown at [0]:
at Microsoft.Workflow.Common.AsyncResult.End[TAsyncResult](IAsyncResult result)
at Microsoft.Workflow.Gateway.HttpAsyncResult.End[TAsyncResult](IAsyncResult result)
at Microsoft.Workflow.Gateway.WorkflowServiceGateway.<>c__DisplayClass6a.<EndCreateOrUpdateWorkflow>b__69()
at Microsoft.Workflow.Gateway.WorkflowServiceGateway.ExceptionFilter[T](Func`1 body)
at System.Threading.Tasks.TaskFactory`1.FromAsyncCoreLogic(IAsyncResult iar, Func`2 endFunction, Action`1 endAction, Task`1 promise, Boolean requiresSynchronization)
ULS logs give below error
Error 1 - Microsoft.Workflow.Client.InternalServerException: An internal error occured. For more details, please see the server logs. HTTP headers received from the server - ActivityId: ba6e77cb-aaae-41a0-9cc8-1ea817d0045e. NodeId: Servername.
Scope: /SharePoint/default/bc694777-7bbb-473e-ab2d-20087221a97a/5229793b-31a1-44b1-9b0b-374f38b762fd. Client ActivityId : a6daec9c-7139-7034-b4ee-edeb1f96ec2a. ---> System.Net.WebException: The remote server returned an error: (500) Internal Server Error.
at Microsoft.Workflow.Common.AsyncResult.End[TAsyncResult](IAsyncResult result)
at Microsoft.Workflow.Client.HttpGetResponseAsyncResult`1.End(IAsyncResult result)
at Microsoft.Workflow.Client.ClientHelpers.SendRequest[T](HttpWebRequest request, T content) -
-- End of inner exception stack trace ---
at Microsoft.Workflow.Client.ClientHelpers.SendRequest[T](HttpWebRequest request, T content)
at Microsoft.Workflow.Client.WorkflowManagementClient.SendRequest[T](HttpWebRequest request, T content)
at Microsoft.Workflow.Client.WorkflowManager.Publish(WorkflowDescription description, Boolean terminateActiveInstances)
at Microsoft.SharePoint.WorkflowServices.FabricWorkflowManagementClient.PublishWorkflow(String serviceGroupName, WorkflowDescription workflow)
at Microsoft.SharePoint.WorkflowServices.WorkflowProxy.CreateDefinitionSubscription(String subscriptionName, String eventSource, List`1 eventTypes, String definitionName, IDictionary`2 metadata, WorkflowEventContext eventContext) StackTrace:
at Microsoft.Office.Server.Native.dll: (sig=35339f9c-8871-4ef1-9118-9c1bd0cb6598|2|microsoft.office.server.native.pdb, offset=131CE)
at Microsoft.Office.Server.Native.dll: (offset=21B4D)
Error 2 - Error publishing workflow subscription (republish or retry publish) information: Microsoft.Workflow.Client.InternalServerException: An internal error occured. For more details, please see the server logs. HTTP headers received
from the server - ActivityId: ba6e77cb-aaae-41a0-9cc8-1ea817d0045e. NodeId:
ServerName. Scope: /SharePoint/default/bc694777-7bbb-473e-ab2d-20087221a97a/5229793b-31a1-44b1-9b0b-374f38b762fd. Client ActivityId : a6daec9c-7139-7034-b4ee-edeb1f96ec2a. ---> System.Net.WebException: The remote server returned an error: (500)
Internal Server Error.
at Microsoft.Workflow.Common.AsyncResult.End[TAsyncResult](IAsyncResult result)
at Microsoft.Workflow.Client.HttpGetResponseAsyncResult`1.End(IAsyncResult result)
at Microsoft.Workflow.Client.ClientHelpers.SendRequest[T](HttpWebRequest request, T content) -
-- End of inner exception stack trace ---
at Microsoft.Workflow.Client.ClientHelpers.SendRequest[T](HttpWebRequest request, T content)
at Microsoft.Workflow.Client.WorkflowManagementClient.SendRequest[T](HttpWebRequest request, T content)
at Microsoft.Workflow.Client.WorkflowManager.Publish(WorkflowDescription description, Boolean terminateActiveInstances)
at Microsoft.SharePoint.WorkflowServices.FabricWorkflowManagementClient.PublishWorkflow(String serviceGroupName, WorkflowDescription workflow)
at Microsoft.SharePoint.WorkflowServices.WorkflowProxy.CreateDefinitionSubscription(String subscriptionName, String eventSource, List`1 eventTypes, String definitionName, IDictionary`2 metadata, WorkflowEventContext eventContext)
at Microsoft.SharePoint.WorkflowServices.FabricSubscriptionService.<>c__DisplayClass1.<CreateDefinitionSubscription>b__0()
at Microsoft.SharePoint.WorkflowServices.WorkflowServiceContextExtensions.InvokeWithEcosystemRetry(WorkflowServicesContext context, EcosystemRequiredMethod method)
at Microsoft.SharePoint.WorkflowServices.FabricSubscriptionService.CreateDefinitionSubscription(String subscriptionName, Guid eventSourceId, String eventSource, List`1 eventNames, String definitionName, IDictionary`2 metadata, WorkflowEventContext eventContext)
at Microsoft.SharePoint.WorkflowServices.WorkflowSubscriptionStorageEventReceiver.ItemUpdating(SPItemEventProperties properties)
Error3 - Microsoft.Workflow.Client.InternalServerException: An internal error occured. For more details, please see the server logs. HTTP headers received from the server - ActivityId: ba6e77cb-aaae-41a0-9cc8-1ea817d0045e. NodeId: ServerName.
Scope: /SharePoint/default/bc694777-7bbb-473e-ab2d-20087221a97a/5229793b-31a1-44b1-9b0b-374f38b762fd. Client ActivityId : a6daec9c-7139-7034-b4ee-edeb1f96ec2a. ---> System.Net.WebException: The remote server returned an error: (500) Internal Server Error.
at SPRequest.AddOrUpdateItem: UserPrincipalName=i:0).w|s-1-5-21-182846760-3036401646-508972453-351846, AppPrincipalName= ,bstrUrl=http://sharepointsite ,bstrListName={48A21758-9123-48F0-9BDE-9EB632B07BC6} ,bAdd=False ,bSystemUpdate=False ,bPreserveItemVersion=False
,bPreserveItemUIVersion=False ,bUpdateNoVersion=False ,pbstrNewDocId=00000000-0000-0000-0000-000000000000 ,bHasNewDocId=False ,bstrVersion=16 ,bCheckOut=False ,bCheckin=False ,bUnRestrictedUpdateInProgress=True ,bMigration=False ,bPublish=False ,bstrFileName=<null>
Any help appreciated. Thanks in advance.

Hi,
As I understand, you encountered the issue when you published a workflow on SharePoint 2013 workflow platform.
I wonder does it work well before when using 2013 workflow platform? If it works before, did you install any updates or change the configuration to the workflow related settings?
If this is the first time after you installed workflow manager 2013, then I’d recommend you try re-registering workflow service per the link below and post the result:
http://technet.microsoft.com/en-us/library/jj663115(v=office.15).aspx
http://technet.microsoft.com/en-us/library/jj658588(v=office.15).aspx
From the message you accessed workflow host uri, please make sure the account to wfsetup and wfservice account are both in wfadmins group.
http://blogs.msdn.com/b/briangre/archive/2013/02/20/least-privilege-configuration-for-windows-azure-workflow-with-sharepoint-2013.aspx
Regards,
Rebecca Tu
TechNet Community Support

Incoming call 400 Bad request

Hello,
I have setup a test deployment of Lync server 2013 with collocated mediation server, which is working fine now. I am now trying to test with different SIP trunk providers. Two of them are working fine now, after some finetuning at the provider. The third
and the most interesting provider for me, is not working properly:
They are providing two trunk hostnames: sw1.sip.domain.com and sw2.sip.domain.com. I have filled both in at the topology. The result is that outgoing calls are working fine but incoming calls result in a 400 Bad Request. Lync Logger states
"The host portion of the from header, sip.domain.com, arriving at MS listening port (5060) did not match any next hop peers' FQDN or IP Address".
I have examined the INVITES with wireshark for all three providers and have found the following difference with the working providers:
The CONTACT header does not match the same hostname/IP as the hostname in the FROM header (incoming call)
Is it mandatory to be the same as the hostname in the FROM header? What else could be the cause of the error?

Hi,
1. You must use a Microsoft certified service provider to ensure that your ITSP supports all of the functionality that traverses the SIP trunk
Check if the issued ITSP is certified by Microsoft:
http://technet.microsoft.com/en-us/office/dn788947
2. Please double check the settings on Lync Topology and make sure all Mediation configuration match Topology.
3. Check if CMS replicate status to be latest.
Best Regards,
Eason Huang
Eason Huang
TechNet Community Support

10gAS Portal and SSO issue, HTTP 400 Bad Request

New installation
10gAS Portal (9041)
Sun Solaris 9
Internet Explorer 6.0.28
After installation, I changed the mid-tier web cache listening port to 80 by following the instruction in OracleÂ® Application Server 10g Administrator's Guide:
http://download-east.oracle.com/docs/cd/B10464_05/core.904/b10376/ports.htm#sthref362
Now I am able to go to portal homepage with port 80:
http://<host-name>/pls/portal/
And when I click on the Login link, it correctly directs me to the SSO login page.
However, when I type in username and password, it returns HTTP 400 Bad Request error.
The weird thing is, if I enter the portal homepage URL again in the same browser, and click the login link again, I am logged in.
Any idea what might cause this issue?
Would re-register portal help?
Thanks,
Carol

The IIS settings probaly also need to get increased as well to accommodate the large number of groups.
I'll see if I can find a better link, but this should get it working.http://support.microsoft.com/kb/970875
Bump up the values, restart the box and see if this continues.
Cheers,
Rhoderick
Microsoft Senior Exchange PFE
Blog:
http://blogs.technet.com/rmilne
Twitter:   LinkedIn:
  Facebook:
  XING:
Note: Posts are provided “AS IS” without warranty of any kind, either expressed or implied, including but not limited to the implied warranties of merchantability and/or fitness for a particular purpose.

Exchange 2013 CU7 - Frequent Outlook 2013 Disconnections and Delays

We currently have the following environment:
Windows 2012 VM on Hyper-V with 24GB of RAM and 4 virtual procs (1 socket)
Cisco UCS, B200 M3 Blades
Exchange 2013 CU7
Exchange 2007 is in our environment, but public folders have been removed and only a few stale, unused accounts exist on it.
Two dual-role CAS/Mailbox servers
Mailbox servers are in a DAG
MAPI/HTTP is our connection protocol
.NET Framework 4.5.2
Clients are Outlook 2013 SP1 on Windows 7 and 8.1
(Currently round robin DNS, but we have a hardware load balancer we've temporarily taken out of the mix to solve this problem)
What we're seeing is frequent disconnections from Exchange, regardless of the CAS server. That is, both CAS servers will disconnect clients, but not at the same time. When we look at the Exchange boxes, we notice that the CPU is 99% - 100% each time the
disconnections occur. When we hunt down the IISWorker process causing the sudden CPU run, we see it comes back to the following app pools:
MSExchangeMAPIFrontEndAppPool
MSExchangeMAPIMailboxAppPool
(We were running RPC/HTTP, but switched to MAPI/HTTP to resolve the problem. We had the same issue with equivalent RPC app pools at the time.)
Eventually, within a minute or two, the CPU load will decrease and the clients connected via that CAS will regain connection. As you can imagine, the pain is felt more frequently by uncached clients--although everyone, regardless of caching, will see
the disconnections.
Basically, the problem sounds exactly as shown in this KB: http://support.microsoft.com/kb/2995145 Unfortunately, we already had .NET 4.5.2 installed, and have changed the environment variable and registry as shown in the article.
We're in contact with Microsoft Support, but thus far they're scratching their heads.
I'm clearing up all small errors to decrease the noise in the application error logs, but the most persistent one is Event ID 106 (MSExchange Common):
"Performance counter updating error. Counter name is Time in Resource per second, category name is MSExchange Activity Context Resources. Optional code: 2. Exception: The exception thrown is : System.InvalidOperationException: Instance 'ad-powershell-defaultdomain'
already exists with a lifetime of Process. It cannot be recreated or reused until it has been removed or until the process using it has exited."
Loading/reloading and recreation of the performance counters does not fix the problem, by Microsoft Support or us. Of course, this error existed before we started having issues; I'd just like to clean it up just in case it's a contributing factor.
Has anyone seen anything similar?

We're using a Barracuda load balancer (641), but we've eliminated that as a source of the problem. The CPU spikes and disconnections happen whether or not the load balancer is in use.
This problem is still ongoing, and we're still working with Microsoft Support. Right now they're focused on our environment, but having combed through it numerous times, there's nothing that stands out. I suspect this is a bug in CU7 (yet I would
readily accept our environment being at fault if it means we can identify and resolve the problem), but that's not the road Support is going down.
We've looked at storage I/O on the VM hosts (disk responses are 10 MS or less), added double the CPUs to each mail server (for a total of 8, each), disabled TCP chimney offload, run numerous Experfwiz log collections, etc... Now
the tech is focused on a particular mailbox database being the culprit because it also takes up more CPU when the MAPI app pools are gunning pretty high. I suspect that it is a symptom and not the problem, but I have no choice but to follow his lead.
What is your environment like? Are you also CU7? And did the problem show itself after a cumulative update was applied?

"The request failed with HTTP Status 400: Bad Request." when running reports

Hi,
I installed reporting services and the install went fine.  The Reporting Services are located on a different server. I can see all the reports in SCCM but when I try to run them I get the "400" error with the following details:
System.Net.WebException
The request failed with HTTP status 400: Bad Request.
Stack Trace:
   at System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage message, WebResponse response, Stream responseStream, Boolean asyncCall)
   at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object[] parameters)
   at Microsoft.Reporting.WinForms.Internal.Soap.ReportingServices2005.Execution.ReportExecutionService.LoadReport2(String Report, String HistoryID)
   at Microsoft.Reporting.WinForms.Internal.Soap.ReportingServices2005.Execution.RSExecutionConnection.<>c__DisplayClass2.<LoadReport>b__0()
   at Microsoft.Reporting.WinForms.Internal.Soap.ReportingServices2005.Execution.RSExecutionConnection.ProxyMethodInvocation.Execute[TReturn](RSExecutionConnection connection, ProxyMethod`1 initialMethod, ProxyMethod`1 retryMethod)
   at Microsoft.Reporting.WinForms.Internal.Soap.ReportingServices2005.Execution.RSExecutionConnection.LoadReport(String Report, String HistoryID)
   at Microsoft.Reporting.WinForms.ServerReport.EnsureExecutionSession()
   at Microsoft.Reporting.WinForms.ServerReport.SetParameters(IEnumerable`1 parameters)
   at Microsoft.ConfigurationManagement.AdminConsole.SrsReporting.ReportViewerWindowsForms.SetParameterValues_DoWork(Object sender, DoWorkEventArgs e)
I can open the URL from the SCCM server but when I select a report I am unable to select any report options if available. If no options are availble the report just doesn't run, I don't get and error if I select "View Report" mutiple
times.
If I connect to the Reporting Services site on the computer where it is installed all the reports run fine.
One thing I have noticed is that when I try to change or add a role assignment for Reporting Services the edited account always reverts back to the default settings and the added Domain user is dropped.
Thanks

I reviewed the topic and found a couple of steps I missed the first time around. I had to "Configure Reports to Use Report Builder 3.0 and setting the "Log on Locally" permission.
I then uninstalled the role and reinstalled it. I am still getting the 400 error.
When I inspected the SmsAdminUI.log I noticed the Error on the last line 2151811598 (it repeats in the log). I couldn't find anything specific related to it. By reading a few "related" Internet posts I came accross a intial setup
blog that noted some WMI firewall execptions (Async-in, DCOM-in and WMI-in) as require so I checked and they were not allowed on the SCCM server so I allowed them and tested with the same result. I turned them off again.
Here is the tail end of the SmsAdminUI.log
[19, PID:2684][01/24/2013 16:08:29] :[ReportProxy] - User-specified default Reporting Point [INC-SQL42.deccoinc.net] could not be found, [] is now the default Reporting Point.
[4, PID:2684][01/24/2013 16:08:30] :[ReportProxy] - User-specified default Reporting Point [INC-SQL42.deccoinc.net] could not be found, [] is now the default Reporting Point.
[15, PID:2684][01/24/2013 16:08:30] :[ReportProxy] - User-specified default Reporting Point [INC-SQL42.deccoinc.net] could not be found, [] is now the default Reporting Point.
[1, PID:2684][01/24/2013 19:06:02] :System.Management.ManagementException\r\nNot found \r\n   at System.Management.ManagementException.ThrowWithExtendedInfo(ManagementStatus errorCode)
   at System.Management.ManagementObject.Initialize(Boolean getObject)
   at System.Management.ManagementBaseObject.get_wbemObject()
   at System.Management.PropertyData.RefreshPropertyInfo()
   at System.Management.PropertyDataCollection.get_Item(String propertyName)
   at System.Management.ManagementBaseObject.GetPropertyValue(String propertyName)
   at System.Management.ManagementBaseObject.get_Item(String propertyName)
   at Microsoft.ConfigurationManagement.ManagementProvider.WqlQueryEngine.WqlConnectionManager.GetInstance(String objectPath)\r\nManagementException details:
instance of SMS_ExtendedStatus
Description = "Error retrieving object FileType=2";
ErrorCode = 2151811598;
File = "e:\\nts_sccm_release\\sms\\siteserver\\sdk_provider\\smsprov\\SspInterface.h";
Line = 1208;
Operation = "GetObject";
ParameterInfo = "SMS_SCI_SysResUse.FileType=2,ItemName=\"[\\\"Display=\\\\\\\\INC-SQL42.deccoinc.net\\\\\\\"]MSWNET:[\\\"SMS_SITE=INC\\\"]\\\\\\\\INC-SQL42.deccoinc.net\\\\,SMS SRS Reporting Point\",ItemType=\"System Resource Usage\",SiteCode=\"INC\"";
ProviderName = "ExtnProv";
StatusCode = 2147749890;
\r\n
[1, PID:2684][01/24/2013 23:39:14] :System.NullReferenceException\r\nObject reference not set to an instance of an object.\r\n   at Microsoft.ConfigurationManagement.AdminConsole.SmsCustomDialog.get_LocaleIndependentIdentifier()
   at Microsoft.ConfigurationManagement.AdminConsole.ShowDialogTaskHandler.DoTask(NavigationModelNodeBase node, SccmTaskConfiguration sccmTask, PropertyDataUpdated dataUpdatedDelegate, Boolean readOnly)\r\n
[1, PID:5008][01/25/2013 20:48:00] :System.Management.ManagementException\r\nNot found \r\n   at System.Management.ManagementException.ThrowWithExtendedInfo(ManagementStatus errorCode)
   at System.Management.ManagementObject.Initialize(Boolean getObject)
   at System.Management.ManagementBaseObject.get_wbemObject()
   at System.Management.PropertyData.RefreshPropertyInfo()
   at System.Management.PropertyDataCollection.get_Item(String propertyName)
   at System.Management.ManagementBaseObject.GetPropertyValue(String propertyName)
   at System.Management.ManagementBaseObject.get_Item(String propertyName)
   at Microsoft.ConfigurationManagement.ManagementProvider.WqlQueryEngine.WqlConnectionManager.GetInstance(String objectPath)\r\nManagementException details:
instance of SMS_ExtendedStatus
Description = "Error retrieving object FileType=2";
ErrorCode = 2151811598;
File = "e:\\nts_sccm_release\\sms\\siteserver\\sdk_provider\\smsprov\\SspInterface.h";
Line = 1208;
Operation = "GetObject";
ParameterInfo = "SMS_SCI_SysResUse.FileType=2,ItemName=\"[\\\"Display=\\\\\\\\INC-SQL42.deccoinc.net\\\\\\\"]MSWNET:[\\\"SMS_SITE=INC\\\"]\\\\\\\\INC-SQL42.deccoinc.net\\\\,SMS SRS Reporting Point\",ItemType=\"System Resource Usage\",SiteCode=\"INC\"";
ProviderName = "ExtnProv";
StatusCode = 2147749890;
\r\n

Download Manager - failing with error 400 Bad Request

Each time I try to download some patches from the download basket I get this error: The request failed: 400. Download Manager says the files are Partially Downloaded but the downloads never complete (they just cycle round one after another attempting each download before failing). The connection to SAP ssems to be made correctly (see trace file extract below)
I'm running JRE version 1.4.2_12; download manager ver 2.1.130. I've tried uninstalling & reinstalling JRE & download manager (numerous times). Does anyone have any suggestions about what might be the cause?
Thanks, Chris
PS - This is the relevant part of the trace file:
24-Aug-2007 09:29:06   Opening connection to 'https://smpdla.sap.com:443/00000084/217/KGPHA68.CAR?object_id=011000358700000405252007E&filepath=00000084\217\KGPHA68.CAR&uid=S0003245349'
24-Aug-2007 09:29:06   Sending request to SAP Service Marketplace Server (no tunneling)
24-Aug-2007 09:29:13   A response was received from the SAP Service Marketplace Server.
24-Aug-2007 09:29:13   Response received: 400 Bad Request
24-Aug-2007 09:29:13   Response Http Headers:
24-Aug-2007 09:29:13      Server=AkamaiGHost
24-Aug-2007 09:29:13      Mime-Version=1.0
24-Aug-2007 09:29:13      Content-Type=text/html
24-Aug-2007 09:29:13      Content-Length=340
24-Aug-2007 09:29:13      Expires=Fri, 24 Aug 2007 08:28:49 GMT
24-Aug-2007 09:29:13      Date=Fri, 24 Aug 2007 08:28:49 GMT
24-Aug-2007 09:29:13      Connection=close
24-Aug-2007 09:29:13   Response code: 400
24-Aug-2007 09:29:18   Notifying subscribers of download state ...
24-Aug-2007 09:29:18   The download has terminated ...
24-Aug-2007 09:29:18   getUserProxy: true
24-Aug-2007 09:29:18   getEffectiveProtocol: http
24-Aug-2007 09:29:18   detected: http / https w/o proxy request
24-Aug-2007 09:29:18   SMPResponse::sendRequestNormal
24-Aug-2007 09:29:18   Opening connection to 'http://service.sap.com:80/~form/download_basket?_MODE=OBJECT_VERSION&OBJID=011000358700000485532007E&'
24-Aug-2007 09:29:18   Sending request to SAP Service Marketplace Server (no tunneling)
24-Aug-2007 09:29:25   A response was received from the SAP Service Marketplace Server.
24-Aug-2007 09:29:25   Redirecting to 'https://WEBSMP108.SAP-AG.DE/~form/download_basket?_MODE=OBJECT_VERSION&OBJID=011000358700000485532007E&'...
24-Aug-2007 09:29:25   getUserProxy: true
24-Aug-2007 09:29:25   getEffectiveProtocol: https
24-Aug-2007 09:29:25   detected: http / https w/o proxy request
24-Aug-2007 09:29:25   SMPResponse::sendRequestNormal
24-Aug-2007 09:29:25   Opening connection to 'https://WEBSMP108.SAP-AG.DE/~form/download_basket?_MODE=OBJECT_VERSION&OBJID=011000358700000485532007E&'
24-Aug-2007 09:29:25   Sending request to SAP Service Marketplace Server (no tunneling)
24-Aug-2007 09:29:25   A response was received from the SAP Service Marketplace Server.
24-Aug-2007 09:29:25   Response received: 200 OK
24-Aug-2007 09:29:25   Response Http Headers:
24-Aug-2007 09:29:25      Date=Fri, 24 Aug 2007 08:29:02 GMT
24-Aug-2007 09:29:25      Server=Microsoft-IIS/6.0
24-Aug-2007 09:29:25      Content-Type=text/plain
24-Aug-2007 09:29:25      Content-Length=44
24-Aug-2007 09:29:25   getUserProxy: true
24-Aug-2007 09:29:25   getEffectiveProtocol: http
24-Aug-2007 09:29:25   detected: http / https w/o proxy request
24-Aug-2007 09:29:25   SMPResponse::sendRequestNormal
24-Aug-2007 09:29:25   Opening connection to 'http://service.sap.com:80/~form/download_basket?_MODE=DOWNLOAD_START2&OBJID=011000358700000485532007E&_VERSION=2.1.130&'
24-Aug-2007 09:29:25   Sending request to SAP Service Marketplace Server (no tunneling)
24-Aug-2007 09:29:25   A response was received from the SAP Service Marketplace Server.
24-Aug-2007 09:29:25   Redirecting to 'https://WEBSMP209.SAP-AG.DE/~form/download_basket?_MODE=DOWNLOAD_START2&OBJID=011000358700000485532007E&_VERSION=2.1.130&'...
24-Aug-2007 09:29:25   getUserProxy: true
24-Aug-2007 09:29:25   getEffectiveProtocol: https
24-Aug-2007 09:29:25   detected: http / https w/o proxy request
24-Aug-2007 09:29:25   SMPResponse::sendRequestNormal
24-Aug-2007 09:29:25   Opening connection to 'https://WEBSMP209.SAP-AG.DE/~form/download_basket?_MODE=DOWNLOAD_START2&OBJID=011000358700000485532007E&_VERSION=2.1.130&'
24-Aug-2007 09:29:25   Sending request to SAP Service Marketplace Server (no tunneling)
24-Aug-2007 09:29:26   A response was received from the SAP Service Marketplace Server.
24-Aug-2007 09:29:26   Response received: 200 OK
24-Aug-2007 09:29:26   Response Http Headers:
24-Aug-2007 09:29:26      Date=Fri, 24 Aug 2007 08:29:03 GMT
24-Aug-2007 09:29:26      Server=Microsoft-IIS/6.0
24-Aug-2007 09:29:26      Content-Type=text/html
24-Aug-2007 09:29:26      Content-Length=2416
24-Aug-2007 09:29:26   Number of URLs: 1
24-Aug-2007 09:29:26   Description lines: 56
24-Aug-2007 09:29:26   Adding HTTP1/1 Header: Range: bytes=0-*
24-Aug-2007 09:29:26   getUserProxy: true
24-Aug-2007 09:29:26   getEffectiveProtocol: https
24-Aug-2007 09:29:26   detected: http / https w/o proxy request
24-Aug-2007 09:29:26   SMPResponse::sendRequestNormal
24-Aug-2007 09:29:26   Opening connection to 'https://smpdla.sap.com:443/00000085/652/KGPHA69.CAR?object_id=011000358700000485532007E&filepath=00000085\652\KGPHA69.CAR&uid=S0003245349'
24-Aug-2007 09:29:26   Sending request to SAP Service Marketplace Server (no tunneling)
24-Aug-2007 09:29:33   A response was received from the SAP Service Marketplace Server.
24-Aug-2007 09:29:33   Response received: 400 Bad Request
24-Aug-2007 09:29:33   Response Http Headers:

Yes - I've checked the address w're pointing to & have rechecked several times with our network people re: the proxy.
The trace seems to show that we're certainly making the initial connections to SAP OK - it just gives up after a few redirections.
Chris

HTTP 400 Bad Request

Hello All,
I'm up against a show stopper. I have a simple region (lets call it the "Quote Region") of type SQL Query that returns rows from a table which I will need tp update. Occasionally the query will return a large number of rows, depending on the size of the customer's quote. My problem is when the quote is large (somewhere around 200 rows) and I perform an update I get HTTP 400 Bad Request "the webpage cannot be found", the URL says something about 7779/pls/apex/wwv_flow.accept.
The update is simple, it takes values that a user enters in another region and does a mass update to the lines in the Quote Region. The lines in the Quote region that are updated are determined by the user selecting them in a shuttle with the shuttle returning the line_id. For small quotes and even quotes with up to 195 lines everything works fine but I need this to work for large quotes! Does anyone know what's going on here???
I'm on version 3.1.2.00.02
Oracle Database 10g Enterprise Edition Release 10.2.0.4.0 - 64bi
PL/SQL Release 10.2.0.4.0 - Production
I don't think it's my code, but here is the mass update anonymous block for review...
DECLARE
l_selected APEX_APPLICATION_GLOBAL.VC_ARR2;
x PLS_INTEGER := 1;
c_loopcount NUMBER := 0;
c_labelcount NUMBER := 0;
l_records VARCHAR2(32000);
l_line_id NUMBER;
BEGIN
-- Check that the shuttle has values
If :P3_APPLY_TO_LINES = 'NA' Then
RAISE_APPLICATION_ERROR( -20110, 'At least one line is required.' );
End If;
-- Convert the colon separated string of values in the shuttle into
-- a PL/SQL array
l_selected := APEX_UTIL.STRING_TO_TABLE(:P3_APPLY_TO_LINES);
FOR i IN 1.. NVL(l_selected.count,0) LOOP
l_line_id := l_selected (i);
c_loopcount := c_loopcount +1;
-- loop through each of the label values that have been entered by the user
FOR i IN 1 .. apex_application.g_f11.COUNT LOOP
c_labelcount := c_labelcount +1;
-- Update the transaction table with the provided value
UPDATE forx_label_transactions
SET value = apex_application.g_f01 (i) -- the user supplied value
,last_update_date = sysdate
,last_updated_by = :P3_LAST_UPDATED_BY
,last_update_login = :P3_LAST_UPDATE_LOGIN
WHERE label_id = apex_application.g_f11 (i) -- the hidden label id that is the foreign key
AND source_transaction_id = l_line_id; -- the line id of the quote line
--AND source_transaction_id = 1074016;
END LOOP;
l_records := l_records||l_selected (i);
END LOOP;
:p3_labelcount := c_labelcount;
:p3_loopcount := c_loopcount;
:p3_selected := (l_records);
END;
Edited by: blue4speed on Oct 7, 2010 8:54 PM
Edited by: blue4speed on Oct 7, 2010 9:04 PM

When submitting a page there is some limit about the page size (I think 32K) after that it throws HTTP 400. We were also facing the same problem in our large tabular form. You can use Pagination to limit the rows displayed in a page to avoid this error.
But when using pagination you will face another issue. Let's say you have 100 rows and pagination is displaying only 10 rows. If you update some rows and press navigation button (Next/Previous) the changes you have made are lost and not saved. I also have a workaround for this if you are interested please let me know. I will post you if you need it.

HTTP 400 Bad Request Error

Application Express 3.1.1.00.09
We have some users who are experiencing what appears to be a browser problem in one of our APEX applications.
When clicking on any button that does an insert or update to the database some users get an HTTP-400 Bad Request error message. The database does not get updated and anything they click on after that shows that message. In most cases we have been able to restore the user’s browser to the default settings and the issue is resolved. However, we were not able to isolate which browser setting is causing the issue. We have seen the issue in IE 6, IE 7 and IE 8.
Here’s the error we see in the Apache server error log (minus the date time stamp and IP addresses):
mod_plsql: /pls/ax_tastest/wwv_flow.accept HTTP-400 Invalid name
Does anyone else have a solution for this? Know what's causing it?

HTTP 400 Bad Request Error from APEX 3.1.1.00.09.
We were able to determine that only PCs which had the Google toolbar installed were getting the HTTP 400 Bad Request Error from a particular page in one of our applications. Further testing revealed that turning off the ‘auto-fill’ feature of the Google toolbar would prevent the error from occurring and the application would behave normally. We were able to identify a specific item on the page that was the root cause. The item was using the type “Text area with HTML Editor” which has been deprecated. We changed the page item type to “HTML editor standard” and this has resolved the issue with or without the Google Toolbar and auto-fill feature enabled.
Summary:
•     Browser setting: Google toolbar enabled with auto-fill enabled.
Apex page item of type: ‘Text area with HTML Editor’.
When a user clicks on a button in the page, that executes a page process, it results in HTTP 400 error.
•     Browser setting: Google toolbar enabled with auto-fill disabled.
Apex page item of type: ‘Text area with HTML Editor’.
When a user clicks on a button in the page, everything goes through correctly and there is no error.
•     Browser setting: Google toolbar enabled with auto-fill disabled or enabled.
Apex page item of type: ‘HTML Editor Standard’.
When a user clicks on a button in the page, everything goes through correctly and there is no error.

APEX 3.1.1.00.09 – HTTP-400 Bad Request

We have some users who are experiencing what appears to be a browser problem in one of our APEX applications.
When clicking on any button that does an insert or update to the database some users get an HTTP-400 Bad Request error message. The database does not get updated and anything they click on after that shows that message. When this happens we have been able to restore the user’s browser to the default settings and the issue is resolved. However, we were not able to isolate which browser setting is causing the issue.
We have seen the issue in IE 6, IE 7 and IE 8. IE 6 must be upgraded and then reset, for 7 and 8 just a reset to default fixes the problem.
Here’s the error we see in the Apache server error log:
mod_plsql: /pls/ax_tastest/wwv_flow.accept HTTP-400 Invalid name
We’d like to determine which of the many browser settings could be causing this.

We got this error when upgrading from Apex 3.1 to 3.2 for our applications that use SSO authentication. This was our resolution (thanks to Scott):
Create schema apex_sso
Install the sso sdk into apex_sso schema (run the loadsdk script)
Connect as SYS from the apex core directory and run:
alter session set current_schema=apex_sso
grant execute on wwsec_sso_enabler_private to apex_030200
grant select on wwsec_enabler_config_info$ to apex_030200
alter session set current_schema=apex_030200
create synonym wwsec_enabler_config_info$ for apex_sso.wwsec_enabler_config_info$
create synonym wwsec_sso_enabler_private for apex_sso.wwsec_sso_enabler_private
drop public synonym wwv_flow_custom_auth_sso
@custom_auth_sso_902.sql
@custom_auth_sso_902.plb
create public synonym wwv_flow_custom_auth_sso for apex_030200.wwv_flow_custom_auth_sso
grant execute on wwv_flow_custom_auth_sso to public
copy rows from wwsec_enabler_config_info$ in flows_030100 table to the same table in apex_sso

ESB Portal : The remote server returned an error: (400) Bad Request

Hi,
I am getting the below error message while trying to access ESB Portal:
========================
Event code: 3005
Event message: An unhandled exception has occurred.
Event time: 12/18/2013 12:07:10 PM
Event time (UTC): 12/18/2013 12:07:10 PM
Event ID: 2a429911fb69455ab3b77348c8b259ce
Event sequence: 10
Event occurrence: 2
Event detail code: 0
Application information:
Application domain: /LM/W3SVC/1/ROOT/ESB.Portal-1-130318418493427545
Trust level: Full
Application Virtual Path: /ESB.Portal
Application Path: C:\Projects\Microsoft.Practices.ESB\Source\Samples\Management Portal\ESB.Portal\
Machine name: WIN-HG1MJEC7KJS
Process information:
Process ID: 3220
Process name: w3wp.exe
Account name: NT AUTHORITY\SYSTEM
Exception information:
Exception type: WebException
Exception message: The remote server returned an error: (400) Bad Request.
Request information:
Request URL: http://localhost/esb.portal/default.aspx
Request path: /esb.portal/default.aspx
User host address: ::1
User: WIN-HG1MJEC7KJS\ESBUser
Is authenticated: True
Authentication Type: Negotiate
Thread account name: NT AUTHORITY\SYSTEM
Thread information:
Thread ID: 4
Thread account name: NT AUTHORITY\SYSTEM
Is impersonating: False
Stack trace: at System.Net.HttpWebRequest.GetResponse()
at System.ServiceModel.Channels.HttpChannelFactory.HttpRequestChannel.HttpChannelRequest.WaitForReply(TimeSpan timeout)
Custom event details:
====================
I also looked at thread : http://social.msdn.microsoft.com/Forums/en-US/1fb510a8-9f4b-4e1e-9261-3273b037786c/esbportal-bad-request-400?forum=biztalkesb
However didn't able to find the workaround for the same.
Best Regards,
Harkirat

Hi,
On a local server you don't have to change the web.config if you use local Windows Groups. Check if the User is added to the "BizTalk Server Administrators" Group. Also check if the Group or the User has rights to access EsbExceptionDb & ESBAdmin
database. You also have to enable "Windows Authentication" in IIS for the ESB.Portal.
Local Machine settings:
ESB.Exceptions.Service\Web.config
<connectionStrings><add providerName="System.Data.SqlClient" connectionString="Integrated Security=SSPI;Data Source=.;Initial Catalog=EsbExceptionDb" name="EsbExceptionDbConnectionString"/></connectionStrings>
C:\Projects\Microsoft.Practices.ESB\Source\Samples\Management Portal\ESB.Portal\Web.config
<connectionStrings>
<add name="AdminDatabaseServer" providerName="System.Data.SqlClient" connectionString="Network Library=dbmssocn;Data Source=(local);Integrated Security=True;Initial Catalog=ESBAdmin;"/>
</connectionStrings>
<authentication mode="Windows"/>
<authorization><allow roles="BizTalk Application Users"/>
<allow roles="BizTalk Server Administrators"/>
<allow roles="Administrators"/>
<deny users="*"/>
</authorization>
Kind regards,
Tomasso Groenendijk
Blog
| Twitter
MCTS BizTalk Server 2006, 2010
If this answers your question please mark it accordingly

Error: 400 "Bad Request" for "deletetree", file "": Unsupported protocol .

Hi
I have an C# application suddenly crashing after months of operation. The application is running on a Windows7 machine and is controlling 2 x NI6602 PCI counter cards through daqmx. The only clues to what when wrong is the following messages in the Windows Application Log.
Message 1 (occurring first):
LabVIEW information: Error: 400 "Bad Request" for "deletetree", file "": Unsupported protocol .
Message 2:
Faulting application name: RecordingStationGUI.exe, version: 1.0.0.0, time stamp: 0x4e3fa214Faulting module name: KERNELBASE.dll, version: 6.1.7600.16385, time stamp: 0x4a5bdaaeException code: 0x80000003
Does anyone know what is causing this error and/or how I prevent this from happening again?
Regards,
mola

Where you ever able to resolve this issue? I have a very similar issue

Exchange 2013 CU7 OWA 400 Bad Request after successful login

Similar Messages

Maybe you are looking for