BizTalk 2006: Log4Net stops logging ?

Of the many logging options available around, often the choice comes down to NOT what is the best in the industry but what is currently being used in your organization. And you won’t have an option of looking at alternatives UNLESS you have a very good reason. This post isn’t about choosing a logging component [...]

Read Full Post »

BizTalk 2006: Performance comparision – To debatch or not ?

At a client site, our BizTalk 06 was running into performance problems (something very common with BizTalk ). And I jumped into the party to generate some statistics to find out what was really happening. To make matters GREAT – the guy who actually developed the BizTalk application had moved on to another [...]

Read Full Post »

Performance tuning with BizTalk 2006

 BizTalk tuning is in itself a HUGE topic and there are various resources available on the internet. The aim of this article is to point out several factors one should consider in a BizTalk implementation from a hardware and software perspective also touching the concept of throttling. I’ve often found out that developers and infrastructure [...]

Read Full Post »

Single vs Multiple hosts in BizTalk 2006

While designing for availability in BizTalk 06 – I’m aware of two possible options
1) Running multiple hosts (quick fix)
2) Clustering the BizTalk server database (long term fix)
In this post, we shall be looking into option 1 to compare between single and multiple hosts.
After installing BizTalk 2006 on your machine, you’ll end up with one default [...]

Read Full Post »

Shared Memory Provider, error: 0 – No process is on the other end of the pipe

A connection was successfully established with the server, but then an error occurred during the login process. (provider: Shared Memory Provider, error: 0 – No process is on the other end of the pipe.)
Solution: Add the ASPNET user to the database login assigning it the correct privilege.

Read Full Post »

Failed to connect to server "machinename" (Microsoft.SqlServer.SmoEnum)

To reproduce the error..
Created a SQL login – Windows Authentication
The default DB = myTempDb
Deleted myTempDb using the Sql Server Management Studio.

Solution:
Change the default Db to master and it solves the problem..
sp_defaultdb ‘MyDomain\Zeeshan’, master

Read Full Post »