|
Home > Archive > BizTalk Server General > April 2005 > redeplouing the same project
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
redeplouing the same project
|
|
| nalaka 2005-04-22, 5:58 pm |
| Hi...
when I deploy a give project for the second time...
I get two errors.
1. First one is that the version is already deployed.
I manualy increase the vesrion... and the problem goes away
2. second is that, it complains the "receive location", already exists.
given that this is the second time I deploy the same project...
what is the method to stop this error..
( I for now undeploy the earlier version)
| |
| Peter Huang [MSFT] 2005-04-23, 2:49 am |
| Hi,
Currently I am looking for somebody who could help you on it. We will reply
here with more information as soon as possible.
If you have any more concerns on it, please feel free to post here.
Thanks for your understanding!
Best regards,
Peter Huang
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
This posting is provided "AS IS" with no warranties, and confers no rights.
| |
| Paul Somers [MVP+BizTalk] 2005-04-24, 5:47 pm |
|
1. You must undeploy the first version before deploying a new version, this
is standard, unless you increase the version number. (not recommended)
Ensure you have no suspended or running instances of any messages or
orchestrations for this assembly in HAT or it will complain.
In visual studio you can set the redeploy option under the project
properties under deployment, it will remove the old version and deploy the
new one (same version number) on top of the old one.
2.If you have a specify now receive port, if you try to redeploy the
assembly under a new version this receive port will already exist, again
remove the receive port first, or do not use specify now, bind it after
deploy. Again using the re-deploy option under visual studio will remove the
port and re-deploy it automatically.
General best practice is to ensure you do not just increase versions like
you have done. Rather make sure that the version is un-deployed first and
then re-deploy the same version again.
There are tools to make this easier on gotdotnet. Let me know if you can't
find them.
Regards,
Paul Somers [MVP]
From: "nalaka" <nalaka@nospam.nospam>
Subject: redeplouing the same project
Date: Friday 22 April 2005 11:28 PM
Hi...
when I deploy a give project for the second time...
I get two errors.
1. First one is that the version is already deployed.
I manualy increase the vesrion... and the problem goes away
2. second is that, it complains the "receive location", already exists.
given that this is the second time I deploy the same project...
what is the method to stop this error..
( I for now undeploy the earlier version)
| |
| WenJun Zhang[msft] 2005-04-25, 2:51 am |
| Hi Nalaka,
In the project's property->configuration properties->deployment, you
can change redeploy to true. Increasing version number to make there
are multiple copies of assembly isn't a goog manner. I suggest you
use BizTalk Deployment wizard to clear up everything and then
redeploy again.
Best regards,
WenJun Zhang
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader
so that others may learn and benefit from your issue.
========================================
=============
Business-Critical Phone Support (BCPS) provides you with technical
phone support at no charge during critical LAN outages or "business
down" situations. This benefit is available 24 hours a day, 7 days a
week to all Microsoft technology partners in the United States and
Canada.
This and other support options are available here:
BCPS:
https://partner.microsoft.com/US/te...rtoverview/4001
0469
Others:
https://partner.microsoft.com/US/te...upportoverview/
If you are outside the United States, please visit our International
Support page: http://support.microsoft.com/common/international.aspx
========================================
=============
This posting is provided "AS IS" with no warranties, and confers no
rights.
|
|
|
|
|