Saturday, March 22, 2008

Could not configure BAM Portal in BizTalk 2006

When configuring BAM Portal you may come across a situation where in you cannot select users and groups in the BAP Portal configuration page in BizTalk configuration window.
This may happen due to various reasons and one of them is as below.
- If you have already configured BAM Portal but removed the portal from the website. Hence the configuration information remained in the BAM Config tables and is not removed from there.

To clear the config information stored earlier, use the BM.EXE and export the config file into a xml and removed the http://ServerName:80/BAM and reimport the config file using BM.EXE.
Now you should be able to configure the BAM portal from BizTalk Configuration window.

Wednesday, March 5, 2008

Wireless over DSL with fixed IP

First connect the DSL modem directly to the computer using which you are configuring the DSL connection. Setup the internet connection by using the login /password and the fixed IP given. Remember to notedown the details are these are required while configuring the wireless. Also notedown the Primary DNS. Once the internet connection is established using a wired connection between DSL and Computer then just open the browser and by default the DSL modem home page should appear. And now go to connection setting page and change the connection PPPOE to bridge connection save and exit which will restart the DSL modem. Now connect the wireless router to DSL modem and login to the home page of wireless router where you can set the configuration setting and select PPPOE and enter the details (like login, pswd, IP address given by ISP and the DNS) properties of WAN. Now save these settings and you are good to go.

Friday, February 29, 2008

Removing SourceSafe dependencies from a solution/project

Situation:Your buddy has created a cool VB.NET application that you want to use. He sends you the source code and it consists of a solution (MySolution) containing a single project (MyProject). You attempt to open the solution and find that it has SourceSafe dependencies. You need to remove all the VSS stuff from the solution/project files.
Solution:
1 - Go to the folder containing the solution files and delete the following: mssccprj.scc MyProject.vssscc vssver.scc
2 - Open MyProject.sln in your favorite text editor and remove the following section: GlobalSection(SourceCodeControl) = preSolution ... EndGlobalSection
3 - Go to the folder containing the project files and delete the following: MyProject.vbproj.vspscc mssccprj.scc vssver.scc
4 - Open MyProject.vbproj in your text editor and remove the following lines: SccProjectName = "SAK" SccLocalPath = "SAK" SccAuxPath = "SAK" SccProvider = "SAK"
Now you can open the solution/project with no source control errors.

Thursday, October 4, 2007

Configuring IIS for BTSHTTPReceive.dll

How to configure IIS for a BizTalk 2006 HTTP Receive Location
First thing you need to do is to make sure that IIS's security is not going to be blocking your calls to the BTSHTTPReceive.dll. To do this goto your IIS manager and click on the Web Service Extension node and right click it and 'Add a new Web Service Extension'. Now browse to the location of BTSHTTPReceive.dll (by default installation its in :\Program Files\Microsoft BizTalk Server 2006\HttpReceive\ folder). Also remember to check the 'Set extension status to Allowed' checkbox. It is also a good idea to create a new application pool for your application to run in. When creating one make sure that the user account used is a member of the BizTalk Isolated Hosts group and the IIS_WPG group.
Now your going to create a new virtual directory in IIS under Default Web Site. Make sure you link the location of BTSHTTPReceive.dll in the content directory. Also make sure you use the new application pool you just setup. Make sure that both Read and Execute permissions are selected, and that Execute permissions are set to Scripts and Executables. After this you should be all set to start setting up your HTTP Receive Location within BizTalk Explorer
Note: Make sure websites are refreshed.

Friday, September 21, 2007

Zombie identification in Biztalk 2006

Zombies can be identified in Biztalk server 2006 by using the following query in the messagebox database.

SELECT * FROM HostNameQ_Suspended where nErrorCategory = 4


In the above query HostName should be replaced with corresponding host name in which you want to identify the Zombies. If the above query return any rows then it indicates that there are Zombies present.

Thursday, August 30, 2007

BizTalk DW Reporting Faulting application btsntsvc.exe, version 3.5.1602.0

BizTalk DW Reporting Faulting application btsntsvc.exe, version 3.5.1602.0
If you are seeing this error in application log,
Set the value of
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\BizTalk Server\3.0\DW\TracingEnabled to 0. Default is 1.

Thursday, August 23, 2007

New transaction cannot enlist in the specified transaction coordinator

The "SQL" adapter is suspending an outbound message going to destination http://www.blogger.com/ servername/DBName/". Details:"New transaction cannot enlist in the specified transaction coordinator. ".

The problem was resolved when I changed :
Administrative Tools \ Component Services \ My Computer \ Properties \ MSDTC \ Security Configuration \ Transaction Manager Communication \ "Mutual Authentication Required" --> and check "Incoming Caller Authentication Required"