1. The remote server returned an error: (404) not Found
This error details are logged in Eventview, the snippet of the error is shown below:
Application information: Application domain: /LM/W3SVC/1/ROOT/ESB.Portal-1-130089573102692686 Trust level: Full Application Virtual Path: /ESB.Portal Application Path: C:\Projects\Microsoft.Practices.ESB\ESBSource\Source\Samples\Management Portal\ESB.Portal\ Machine name: Process information: Process ID: 10524 Process name: w3wp.exe Account name: NT AUTHORITY\NETWORK SERVICE Exception information: Exception type: WebException Exception message: The remote server returned an error: (404) Not Found. Request information: Request URL: http://localhost/ESB.Portal/default.aspx Request path: /ESB.Portal/default.aspx User host address: 127.0.0.1 User: Is authenticated: True Authentication Type: Negotiate Thread account name: NT AUTHORITY\NETWORK SERVICE Thread information: Thread ID: 7 Thread account name: NT AUTHORITY\NETWORK SERVICE Is impersonating: False Stack trace: at System.Net.HttpWebRequest.GetResponse()
at System.ServiceModel.Channels.HttpChannelFactory.HttpRequestChannel.HttpChannelRequest.WaitForReply(TimeSpan timeout)
Possible Causes
– Database connectivity – Esb Portal Web.Config does not have the correct database settings.
– Underlying web service connectivity issues – Esb Portal uses few web services deployed on IIS, e.g. Esb.BAM.Service, Esb.Exceptions.Service, Esb.BizTalkOperationService etc and if there is any issue with connectivity to these services, then it results in above errors.
Solution
• Check the web.config file for correct database connection strings, if you are testing locally you can replace them from following:
Check now if Esb portal works fine. If not then try and check each of above (under cause) mentioned web service if they are running fine or not, if not and you are facing an error like:
“The requested content appears to be script and will not be served by the static file handler.”
Try following steps:
• In a command prompt, change to the C:\Windows\Microsoft .NET\Framework\v3.0\Windows Communication Foundation\ directory, and then run ServiceModelReg.exe /x /i.
Note: This will ensure that WCF support is fully installed and available.
• Go to C:\Windows\Microsoft .NET\Framework\v4.0.30319\ and run aspnet_regiis –i
• iisreset
2. Index (zero based) must be greater than or equal to zero and less than the size of the argument list.
This error usually comes from BizTalk operation Service which is accessed by Esb Portal. The following error details is from EventViewer.
Application information: Application domain: /LM/W3SVC/1/ROOT/ESB.Portal-3-130089589367504127 Trust level: Full Application Virtual Path: /ESB.Portal Application Path: C:\Projects\Microsoft.Practices.ESB\ESBSource\Source\Samples\Management Portal\ESB.Portal\ Machine name: Process information: Process ID: 8828 Process name: w3wp.exe Account name: NT AUTHORITY\NETWORK SERVICE Exception information: Exception type: SoapException Exception message: An unexpected error occurred during initialization of the BizTalk Operations Service. —> Index (zero based) must be greater than or equal to zero and less than the size of the argument list.
Cause
It is an access right issue to retrieve information from BizTalk management database.
Solution
• Check BizTalk operation service application pool user account. This user account should be part of BTS_ADM_USERS Database role for BizTalk Management Database.
Vikas Bhardwaj's Blog 