by Ali Raza Zaidi on April 20, 2012
Today I am trying to generate XSD from Well formed XML. Visual studio return this error
WFX to XSD schema generation module is not installed. Execute C:Program FilesMicrosoft BizTalk Server 2006SDKUtilitiesSchema GeneratorInstallWFX.vbs to install the WFX to XSD schema generation module.
To resolve this issue, simply run the aforementioned VB script; you’ll also need to run the InstallDTD.vbs script to add DTD support.
Some times run installWFX.vbs does not solve the problem then do one more step copy dll inside
“C:Program FilesMicrosoft BizTalk Server 2006SDKUtilitiesSchema Generator” to folder “C:Program Files (x86)Microsoft BizTalk Server 2010Developer ToolsSchema Editor Extensions”
It will solve the problem
by Ali Raza Zaidi on April 17, 2012
I found this error, when I just complete the installation of ESB toolkit on my machine. I found that I missed the following Filters on “All.Exceptions” send port
ErrorReport.FailureCode – Exists
Microsoft.Practices.ESB.ExceptionHandling.Schemas.Property.FaultCode – Exists
When I set the these filters on send port. All exception port successfully enlisted and start
by Ali Raza Zaidi on April 4, 2012
After hundreds of time failure on BizTalk configuration failed at configuring SSOS with error
Failed to connect to the SQL database SSODB on SQL Server
The best solution I found was to re-register the ssosql.dll on the following manner:
1. start the visual studio command prompt
2. go to the ssosql.dll C:Program FilesCommon FilesEnterprise Single Sign-On
3. regasm ssosql.dll
and probably you are finished.
On 64 bit machine somehow or other regasm did not gac the ssosql.dll, when checked I assembly folder it contains old dll, so on 64 machine you have to regac ssosql.dll manually.
by Ali Raza Zaidi on February 5, 2012
I face an error while creation file location at my personal computer for
Could not store transport type data for Primary Transport of Send Port ‘SendPort1′ to config store. Primary SSO Server ‘ALIRAZA-PC’ failed. Cannot perform encryption or decryption because the secret is not available from the master secret server. See the event log (on computer ‘ALIRAZA-PC’) for related errors.
(Microsoft.BizTalk.ExplorerOM)
After doing google i found following solution.
REASON:
——-
Maybe someone had reset the service account password or any other cause.
———
SOLUTION:
———
If you get this SSO error:
Cannot perform encryption or decryption because the secret is not available from the master secret server, do the following steps:
1. Open command prompt:
2. Go to c:program filescommon filesenterprise single sign-on
type: ssoconfig -restoresecret SSO9F54.bak (the sso back up file created at the time of biztalk configuration)
3) Give the valid password
4)On success, type: ssoconfig -backupsecret latestbackup.dat
Give a password, and perform them successfully to take the backup of latest sso config file.
by Ali Raza Zaidi on January 9, 2012
Currently working on sftp BizTalk adapter, I have to configure SSL site on my local machine. I got following error when run the local host.
HTTP Error 403.14 – Forbidden
The Web server is configured to not list the contents of this directory.
The issue was that .Net framework 4.0 was not installed on my machine, possible I installed iis after installation of visual studio.
So here is what you need to do to fix it.
1.) Run a command prompt as Administrator.
2.) Copy and paste the following text “C:WindowsMicrosoft.NETFramework64v4.0.30319aspnet_regiis.exe -i”
This is assuming that you have already installed .Net Framework 4.0 , but not in the correct order.
by Ali Raza Zaidi on January 5, 2012
So, I installed Biztalk 2010 on Winows 7 with SQL server 2008 R2 on a 32 bit machine. Biztalk configuration worked smoothly as one would expect it to until the wizard tried to enable BAM portal. Biztalk configuration wizard threw an error saying “Default Web Site can’t be validated”. I did some research and found that almost everyone that had this error got it fixed by installing “IIS6 compatibility” role on the Server. But in my case, this role was already installed. But just to be sure, I uninstalled it–> restarted the server and installed it back. Only to find that it did not make any difference!
I tried hacking my way by physically creating BAM application on the IIS but did not work either. Since BAM is a pre-compiled version, I could not debug it as I would do in an asp.net web application. Then, I thought of creating a new website called “BAM” at the same level as the “Default Website” but on a different port (not 80). In my case, I used port 81. I ran the Biztalk Configuration wizard, pointed it to “BAM” site instead of “Default WebSite” and it worked!!
Later, I did some research and found out that this is a “bug” or a “known behavior” with Biztalk 2010 installation. It seems creating a new site for BAM is generally accepted solution.
Check out :http://social.msdn.microsoft.com/Forums/en/biztalkgeneral/thread/ef650460-c219-4b34-bc7a-41bb7e75ec81
by Ali Raza Zaidi on December 11, 2011
Currently working on BizTalk 2006 applications, during testing freshly created and deployed version of one application, I got error at failure executing the receive pipeline:
There was a failure executing the receive pipeline: “Microsoft.BizTalk.DefaultPipelines.XMLReceive, Microsoft.BizTalk.DefaultPipelines, Version=3.0.1.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35″ Source: “XML disassembler” Receive Port:
Reason:
Cannot locate document specification because multiple schemas matched the message type
Basically message type is combination of root node and namespace is one of the most typically used to promoted properties for subscription, in fact almost every orchestration uses Message Type as part of its subscription. So it is important to keep message type unique across the different schema deployed on server.
Possible solution:
Solution Number one :
If schema are same used in different application. Make an extra project for schemas, and placed require schemas there. Compiled the new project and created dll for schema in target applications. In this way we can exclude this exception.
Solution Number Two:
One solution is that if we are using xml Receive then in the pipeline definition at receive location level, set the “Allow Unrecognized Documents” to true. This will solve the schema conflict issue.
Solution Number Three :
if schema are different, but same namespace and root name then
create a new send port for service, go to send pipeline properties and set DocumentSpecNames property to fully qualified name of schema in format <schema type>+<root name> ,<schema assembly full name>. This Pipeline property tells BizTalk exact location of schema to be loaded and thus avoid conflict
for example:
ReportLostV2.CardReportLostPC_Package_STORED_PROCEDURES_2+STOP_LIST, Card.ReportLostV2, Version=1.0.0.0, Culture=neutral, PublicKeyToken=9b51853b6987xxxx
you can get DocumentSpecNames value from SchemStrongName context property.
by Ali Raza Zaidi on October 6, 2011
With reference to Abdul Rafay’ he developed excellent web console for BizTalk . You can find it form here (http://btswebconsole.codeplex.com/)
Project Description
BizTalk 2010 Web Console allows administrators/operators to perform operations below from the browser.
- Stop/Start/Restart Host Instances
- View Status of Service Instances by applying queries to the group.
- Stop/Start/Unenlist Orchestrations, Send Ports and Send Port Group
- Stop/Start Receive Locations
It works on Single/Multi-Server environment and has been tested on BizTalk Server 2009 and BizTalk Server 2010.
reference : http://abdulrafaysbiztalk.wordpress.com/2011/10/01/biztalk-2010-web-console/
by Ali Raza Zaidi on September 8, 2011
The goal of BizTalk Server 2010 is to help organizations create automated business processes that span diverse applications and platforms.
Along with its core messaging and orchestration capabilities, the product includes a BRE for working with complex business rules and BAM to let information workers track running processes. Additional components, such as EDI support, the RFID server, SOA infrastructure support, Enterprise Single Sign-On, and HIS address other related challenges.
From its initial roots in EAI and B2B integration, BizTalk Server has grown into a foundation for BPM. As the change to a service-oriented world rolls on, BizTalk Server 2010 will continue to play an important part in automating business processes in a diverse world.
Understanding BizTalk Server 2010 requires a grasp of how it addresses each of these three areas:
- Connecting applications within a single organization, commonly referred to as enterprise application integration (EAI). As more organizations move toward service-oriented architecture (SOA), the approach to doing this also becomes increasingly service-oriented.
- Connecting applications in different organizations, typically referred to as business-to-business (B2B) integration.
- Supporting the holistic approach to working with automated business processes that’s defined by business process management (BPM).
you can download white paper from here
Original Post reference : http://obieosobalu.wordpress.com/2011/04/14/white-paper-see-how-microsoft-biztalk-server-2010-can-address-your-business-needs/
by Ali Raza Zaidi on July 20, 2011
ERROR: 0xC0002A0F: Could not contact the SSO server . Check that SSO is configured and that the SSO service is running on that server. (RPC: 0x800706D9: There are no more endpoints available from the endpoint mapper.)
Second issue I found when I try to configure a receive port my testing application on local machine, Unfortunately I found two services are not running properly on my machine.
- “Remote Procedure Call (RPC)”
- “Enterprise Single Singon”
I restart both, but found that Enterprise Single Sign on has credential issue, it saved the old password, because I am using windows authentication on Sql server and for all services. I update my Single Sign on authentication as below the screenshot
Its working for me.
