Error in ESB Portal browsing

Question

We have installed BizTalk 2009 on Windows 2003 64 bit with SQL 2005 SP2 client tools. SQL 2005 SP2 on remote box.

We performed all the steps in the ESB installation document. When we try to browse ESB.Portal we are getting the following error:

----------------
Event code: 3006
Event message: A parser error has occurred.
Event time: 10/16/2009 12:13:16 AM
Event time (UTC): 10/16/2009 4:13:16 AM
Event ID: b9628c5e971240978b6db789dd51d4a6
Event sequence: 1
Event occurrence: 1
Event detail code: 0

Application information:
Application domain: /LM/W3SVC/1/Root/ESB.Portal-1-129001399966996773
Trust level: Full
Application Virtual Path: /ESB.Portal
Application Path: E:\Program Files\Microsoft BizTalk ESB Toolkit 2.0\Web\ESB.Portal\
Machine name: S3SLC08AP24

Process information:
Process ID: 6424
Process name: w3wp.exe
Account name: BLCORP\kpinnamaneni

Exception information:
Exception type: HttpException
Exception message: Could not load type 'Microsoft.Practices.ESB.Portal.Global'.

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: False
Authentication Type:
Thread account name: BLCORP\kpinnamaneni

Thread information:
Thread ID: 1
Thread account name: BLCORP\kpinnamaneni
Is impersonating: False
Stack trace: at System.Web.Compilation.BuildManager.ReportTopLevelCompilationException()
at System.Web.Compilation.BuildManager.EnsureTopLevelFilesCompiled()
at System.Web.Hosting.HostingEnvironment.Initialize(ApplicationManager appManager, IApplicationHost appHost, IConfigMapPathFactory configMapPathFactory, HostingEnvironmentParameters hostingParameters)

--------------------

I tried looked on few forums but still didn't find the solution for this. Let me know if you need more information on this.

---

RK

Answer 1

Hi, Yeah ,Kish I too faced the same error when i've installed ESB 2.0, Open the ESB. Portal solution from ..\Microsoft.Practices.ESB\Source\Samples\Management Portal\ESB.Portal. In that they parsed time as int.parse (search the variable as "tzo"). But India time is GMT + 5.5, so you've to change that to decimal.parse or hard code the the integer value as "6" coz the value of "tzo" will come as "5.5". It will work out only for India system. Check it out and let me know.

Answer 2

The system are in USA under Eastern Time Zone. Do I still need to make the above change? Is the error related to Time Zone?

---

RK

Answer 3

Hi, Ok give a try and check what value you are getting in that variable (tzo). I feel this is the error because it shows parser error only rite...

Answer 4

I found "var tzo = -1 * d.getTimezoneOffset()/60;" line in Default.aspx of ESB.Portal folder. I have changed it to "var tzo = 6;".

Still the problem is not resolved and failed with same error. There is no change in the error message.

Thanks for helping me in this regard.

---

RK

Answer 5

Hi, If the value of tzo is integer means you don't want to change, you can keep as it is. Dont want to hard code as 6. What error you are getting try to debug the portal and post the error message.

Answer 6

I also did the following change:
in Layout.Master.cs file, from "Session["tzo"] =int.Parse ( tzoqry);" to "Session["tzo"] =decimal.Parse ( tzoqry);". Still no success.

There is no change in the error message.

Thanks for helping me in this regard.

---

RK

Answer 7

It is in production environment, so we don't have debug tools on this box.
Did you ever installed ESB in Multi Server environment, like BizTalk & ESB on one box and SQL on remote box? If yes, can you give short notes on the steps you performed. It looks to me like I am missing something here.

I never installed it before. My Dev team installed it in thier local boxes, and they say they didn't had this issue in local box installation.

What are the differences between installing on local box (where BizTalk, ESB & SQL in one box) vs. Multi server environment (BizTalk & ESB in one box and SQL in another box)?

Thanks

---

RK

Answer 8

Hi, I haven't tried ESB in Multi Server environment, for us everything installed it in thier local boxes itself.

Answer 9

I've installed it in a distributed environment, one of the tweaks I had to do was make sure that the NTAuthenticationProviders equalled "NTLM, Negotiate"

Not sure if this solves your problem though, this information is not in the documentation - one of the things I cam across when trying to do it.

Keep in mind as well that when you install the portal it has some installation dependencies on Microsoft Visual Studio. You have two ways to get around this, identify the DLL's and register them on the portal or install VS.NET on the portal, install the Management Portal and then remove it.

I did the latter for a production environment and have had no problems thus far.

Answer 10

I have copied all the "bin" & "obj" folders of all the web services from QA environment. And I passed through this error.

Now I stuck at another error:

------------------------------------
Event code: 3005
Event message: An unhandled exception has occurred.
Event time: 10/20/2009 3:35:40 PM
Event time (UTC): 10/20/2009 7:35:40 PM
Event ID: 91dfdb052c0a4f3ea6b400965d7ba097
Event sequence: 4
Event occurrence: 1
Event detail code: 0

Application information:
Application domain: /LM/W3SVC/1/Root/ESB.Portal-1-129005409391139226
Trust level: Full
Application Virtual Path: /ESB.Portal
Application Path: E:\Program Files\Microsoft BizTalk ESB Toolkit 2.0\Source\Samples\Management Portal\ESB.Portal\
Machine name: S3SLC08AP24

Process information:
Process ID: 3368
Process name: w3wp.exe
Account name: NT AUTHORITY\NETWORK SERVICE

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: 127.0.0.1
User: BLCORP\kpinnamaneni
Is authenticated: True
Authentication Type: Negotiate
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.Net.HttpWebRequest.GetResponse()
at System.ServiceModel.Channels.HttpChannelFactory.HttpRequestChannel.HttpChannelRequest.WaitForReply(TimeSpan timeout)

------------------------

I know this is general error which doesn't give exact location to fix, I am looking for some suggestions what to check. I did following things:
- Network Service account is used for all web services
- Domain account has all required access
- All web.config, app.config files are updated with correct database details

I am not sure what am I missing here?

---

RK

Answer 11

Hi Hatchman, Thanks for the response. I set NTAuthenticationProviders equalled "NTLM, Negotiate".

Can you just brief out the steps you did in multi server environemnt?
And mainly, which user account used where?
ANy initial set up you did on SQL box or local box( where Biztalk & ESB installed).

Thanks for your help.

---

RK

Answer 12

Sure mate here is what I did from memory for the Portal part of the multi-server environment

1. Installed the O/S (Windows Server Datacenter 64 bit)
2. Configured IIS
3. I then configured the IIS NTAUthenticationProviders for NTLM and Negotiate
4. Configured WSS 3.0 SP2 – moved it to another port so that Port 80 is kept free
5. Installed the BizTalk Server 2009 BAM and SharePoint Service using BizTalk Enterprise Edition
6. I then installed Visual Studio 2008 and SP1
7. I then set both the 32 and 64 bit versions of Powershell to run unrestricted because if you don’t installing the Management Portal fails on a 64 bit machine.
8. Installed the ESB Toolkit pre-requisites (Chart Controls, Enterprise Library etc...)
9. Ran the ManagementPortal bat file
10. Removed Visual Studio

 Everything in my multi site uses domain accounts, including the ESB Portal and Toolkit on the BizTalk Servers and SQL Servers. I have heard that this hasn’t worked for a few people but I did not have a problem.

Whenever I install BizTalk Server and SQL Server   in a multi server environment I always log onto the machines using the domain service accounts for BizTalk (primarily the one that runs for the in-process host) and SQL because that ensures that they work as expected when deployed to production. I never use a standard user account because I have found in the past that it gives me permission and security issues.

In short you should have Active Directory set up with all the accounts and groups required for your BizTalk production environment (and test and dev as well) before you install anything. After that only use those accounts to log into machines when running installs and these groups when configuring things to detect security issues, especially with Portals, early on. If you install under a user account or a domain account with elevated privileges you'll only find about these issues later which can be difficult to correct.

Answer 13

Hatchman, Thanks alot for your tips and suggestions.

I have resolved all the issues and ESB Portal is successfully up and running.

Here is what i did:
I removed the the existing installation and did everything again.
The only thing i done it different this time is, I have modified all the app.config and web.config (with SQL server name) files before creating the web services in IIS.
I did everything manually.

I got error while executing batch file.

---

RK