December 2009 Entries

Re Configuring BizTalk Error : Could not connect to SSOSQL and ENT SSO service does not show up under services mmc

Sometimes while re configuring your BizTalk Server you may face this problem under ENT SSO configuration. Quick solution to this reregister the SSOSQL.dll. So, navigating to "C:\Program Files\Common Files\Enterprise Single Sign-On\SSOSQL.dll "folder in the Visual Studio Commmand prompt and running 'regasm SSOSQL.dll'. Next step is to restore the Master Scret Server Database, if you want to use the existing the SSO DB, which you should. In order to restore the SSO master secret, you must have previously...
  • Share This Post:
  • Share on Twitter
  • Share on Facebook
  • Share on Technorati

BizTalk Deployment : Error - Can not update assembly "XXXXXX". To update assembly "XXXX" remove the following assembly "XXXXXXXXXX".

Most of the time you receive this error when you change or modify your schema project wherein your schema project is referred inside the orchestration project. The question which arise in your mind from where should I remove this resource. From GAC or from References or from resources. I would suggest to remove the reference of schema project from the referencing project and then remove the assembly of referencing project from the BizTalk resources and if possible remove the assemlies from the GAC...
  • Share This Post:
  • Share on Twitter
  • Share on Facebook
  • Share on Technorati

warning BEC2004: Delimiters are not unique, field and component seperator are the same

You may receive this error due to incorrect placing of elements in ISA segment. This make you irritated if you are not able to figure where you are missing out in spacing in your ISA segment message in X12 message. Below is the corrcet ISA segment and you could verify your ISA segment against this. Also on msdn the description and resolution of the mentioned problem is detailed. ISA*00* *00* *02*XXXX *01*XXXXXXXXX *091210*1153*U*00401*000000... http://msdn.microsoft.com/e...
  • Share This Post:
  • Share on Twitter
  • Share on Facebook
  • Share on Technorati

Exception occurred when persisting state to the database.

Received the dreaded error again and again while BizTalk Orchestration tried to persist the state into database. Struggled quite a bit. I was using Dynamic bindindg and partner orchestration port was set to "messagebox". I was using this to send the Custom Exceptions to BizTalk which were already subscribed to "Send Error" port so there was no problem in subscription. Solution: Finally, It look of lot of time to figure out the problem. It was being caused due to a duplicate subscription in the Message...
  • Share This Post:
  • Share on Twitter
  • Share on Facebook
  • Share on Technorati

AS2 Processing with BizTalk.

I started the implementation of AS2 and MDN for one of our EDI client. Here are some thoughts about the AS2 implementation in BizTalk when I looked at below url at MSDN. http://msdn.microsoft.com/e... 1- Signature (outbound) - This is required in a scenario when you send a signed document to the partner. For this you need to create your own "private key" and this will be stored under "Current User\Personal". This is the signing certificate used for sending signed messages...
  • Share This Post:
  • Share on Twitter
  • Share on Facebook
  • Share on Technorati

Learn VSTS 2010 and Get awsome rewards

Microsoft India has launched a challenge which gives an opportunity to all the Visual Studio to WIN - I20 car. So dont wait. Go and register and win exciting prizes. http://vsalmchallenge.com/ There are taining courses also available on channel9 for VSTS 2010 Beta 2. Cheers, Vishnu
  • Share This Post:
  • Share on Twitter
  • Share on Facebook
  • Share on Technorati

«December»
SunMonTueWedThuFriSat
293012345
6789101112
13141516171819
20212223242526
272829303112
3456789