09-23-05 10:52 PM
You need to restart BizTalk process for the changes to take the effect.
That's a common problem, because all apps in te same host run in a single
app domain, and recycling app domain when somebody deploys a new
orchestration in the production environment is a really bad idea. So, the
host should be restarted manually.
Regards,
Eldar
http://blogs.msdn.com/eldarm/default.aspx
This posting is provided "AS IS" with no warranties, and confers no rights.
Business Process Integration Team
Get Connected!
Meet and interact with key BizTalk Server program managers, developers, and
testers, and let them and other BizTalk Server community team members and
Most Valuable Professionals help you solve your product questions.
Navigate to http://msdn.microsoft.com/subscriptions/support/ in your
webrowser and register as a managed customer to receive MSDN Managed
Newsgroup Support!
MSDN managed newsgroups are available in English to MSDN Universal,
Enterprise, Professional, and Operating Systems subscribers to receive
free, unlimited technical support on select Microsoft technologies as well
as to share ideas with other subscribers.
--------------------[vbcol=seagreen]
sv3- dRi9T4434YrpvYW0wdjFNj0GhoQs4e2aHJ+Mv3NP
Tkp0uxiimtsxgYuw6l4uvO0oJJIz0YqT
ofvG/ Yd!XHb+ct6WhF98B7pn8J4jSba6wWlNkXVPUBxdZ
Aw8HkUGQ1HYrvseCb7OSYfN[vbcol=seagreen]
complaint properly[vbcol=seagreen]
TK2MSFTNGXA01.phx.gbl!TK2MSFTNGP08.phx.gbl!newsfeed00.sul.t-online.de!t-onli
ne.de!border2.nntp.dca.giganews.com!border1.nntp.dca.giganews.com!nntp.gigan
ews.com!local01.nntp.dca.giganews.com!news.giganews.com.POSTED!not-for-mail[vbcol=seagreen]
i've a great trouble with my biztalk 2004!!
during applications testing, i need to make changes to my biztalk
application and test it many times. So i undeply-deploy it but no
changes in assembly run! it's like i never redeply the new
application. i used the biztalk deployment wizard too, but i got the
same problem yet. the only chance for me to see my new application
really deployed is to stop-start the whole server!!! but that's
impossible in a production environment. i think the assembly really
remains in GAC even if it seems to be undeployed. is there a way to
solve my problem???
thanx in advance for your reply.
OH
ps. i use biztalk server 2004 (no sp1) on Windows 2000 server SP4
[vbcol=seagreen]
[ Post a follow-up to this message ]
|