Showing posts with label biztalk. Show all posts
Showing posts with label biztalk. Show all posts

Wednesday, February 24, 2010

Deploying BizTalk 2009 Applications

After long time i had to refresh my knowledge about deploying a BizTalk application. I did all these things some time back and totally forgot the things what i did. Anyhow after developing a small orchestration sample in VS 2008, i tried deploying the application. It successfully deploys but i couldn't see the Application in the Biz Talk Administration Console. totally confused and was searching for the deployed Application name after restarting the service for one, two, three times. I had to make sure is that the schema, map were deployed or not. When i checked in the All Artifacts node, so i was able to find my schema, map were deployed successfully.

So after that i had to check the properties of the BizTalk project what i did developed in VS. When i checked the properties so the Application Name was empty.

image

In this case at the time of deploying, VS automatically deploys the application as “BizTalk Application 1” and when i checked the maps, schema folders, all my files were deployed there.

image

so i had to insert a name for the Application Name in VS 2008 and had to redeploy it again. At the time of deploying VS prompts you saying that the DLL is already deployed. What you have to do is remove the assembly from the GAC (C:\Windows\Assembly) and as well as the orchestration, map and schema files from the BizTalk Administrator Console. Once its done try to deploy it again and finally it was deployed successfully. :)

image

Tuesday, January 05, 2010

Biztalk Poster

Biztalk poster (Silverlight enabled) -

Check this out :

http://www.microsoft.com/biztalk/capabilities/reader/ .

Scroll/Zoom + click on a section where the help and various MSDN articles come up. really helpful for us. :)

Thursday, December 03, 2009

Service Unavailable and SharePoint Error: Some or all identity references could not be translated

Currently i was working with some BizTalk test projects using a Virtual Machine installed with Windows 2003. I have installed BizTalk 2006 in the same machine in which i was doing some SharePoint projects. For me to install BizTalk 2006 i had to install DNS and the Active Directory. Prior to installing this BizTalk, SharePoint was working fine without giving me any headache.

After installing BizTalk it started to give me problems when i tried to access the SharePoint Central Administration. It prompted me for Service Unavailable error, Grr rrrr (at that time i was thinking if i need to redo these things again such as installing windows 2003 in a new virtual machine, after that installing DNS, installing Active Directory, installing MOSS 2009 and installing BizTalk 2009 - it will waste my time for sure).

So i know it was due to the installation of the Active Directory and i had to reset the permission in Application Pools in IIS (go to IIS, browse Application Pools and select your Application => right click and go to properties => from there select the Identity Tab and change the User Name and accordingly change the password.

image

Once its over when i tried to browse for SharePoint sites another error was prompting me saying “Some or all identity references could not be translated” (Hard Luck). So i was searching to resolve this problem. so Finally the utility STSADM was there to help us. You can find this tool under C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\BIN and just execute this command by replacing the proper login with the domain name followed by the password.

"stsadm.exe -o updatefarmcredentials -userlogin domainname\username –password yourpassword "

image

Once you executed the above command please make sure to do iisreset –noforce

Hurray!!! now everything works fine without any hassle. Hassle free of life.

Make sure to re-run the SharePoint Products and Technologies wizard once the above said steps are finished.

image

guys for more information please refer this URLs:

http://www.neilrichards.net/blog/?p=73

http://coolsubhash-tech.blogspot.com/2007/05/some-or-all-identity-references-could.html

http://www.keirgordon.com/post/SharePoint-Server-Error-Some-or-all-identity-references-could-not-be-translated.aspx

Failed to add resource(s). Resource () is already in store and is either associated with another application or with another type

image

when i was working with biztalk orchestration, there was an error prompted at the time when i did the deployment : “

Error 1 Failed to add resource(s). Resource (-Type="System.BizTalk:BizTalkAssembly" -Luid="BizTalkServerTestProjectAmmar, Version=1.0.0.0, Culture=neutral, PublicKeyToken=dda761d103beeac0") is already in store and is either associated with another application or with another type. 0 0 “

I thought we should just deploy the way that we are doing with other applications. But when researched about this if we didn't specify any value for the Application Name in the Deployment properties page, then VS used to deploy the orchestration in BizTalk Server named with BizTalk Application 1.

image

To overcome the above said error i had to remove the resource file located under Resources folder as below:

image

once its done, the orchestration was deployed in the BizTalk Server successfully. :)

To avoid this in future, set explicitly deployment target application in the Visual Studio project properties by: right click - Configuration properties - Deployment - Application Name.