Hi there,
I'm trying to install the BT admin tools on a developer machine, that has to
connect to a BTS2004 standard edition on Win2003 server.
When running the Configuration Wizard I get the following error:
For Standard and Partner editions, joining a BizTalk group is not allowed.

Any suggestions as to what I am doing wrong?
Also, when I try to deploy an assembly to this server (either using the
deployment wizard or from Visual Studio) the deployment hangs (progress bar
is at 2/3rd) without any error. The assembly does not get installed.

Any help appreciated,
Thanks,
Michel

[ Post a follow-up to this message ]

Hi Michel,

The Standard edition of BizTalk server can only be used on one server (i.e.
only one server in the group, therefore no ability to join an existing
group). If you want to have more than one BizTalk Server in a group, you wil
l
need to use the Enterprise edition. More details in the FAQ here:
http://download.microsoft.com/downl...icensingFAQ.doc

Regards

Owen


"Michel" wrote:

> Hi there,
> I'm trying to install the BT admin tools on a developer machine, that has 
to
> connect to a BTS2004 standard edition on Win2003 server.
> When running the Configuration Wizard I get the following error:
> For Standard and Partner editions, joining a BizTalk group is not allowed.
>
> Any suggestions as to what I am doing wrong?
> Also, when I try to deploy an assembly to this server (either using the
> deployment wizard or from Visual Studio) the deployment hangs (progress ba
r
> is at 2/3rd) without any error. The assembly does not get installed.
>
> Any help appreciated,
> Thanks,
> Michel

[ Post a follow-up to this message ]

Hi Owen,

I don't want another server.
I just want to be able to administer an existing server and deploy
assemblies from developer workstations.

Am I using the wrong installation?

Thanks,
Michel

"OwenCutajar" wrote:
[vbcol=seagreen]
> Hi Michel,
>
> The Standard edition of BizTalk server can only be used on one server (i.e
.
> only one server in the group, therefore no ability to join an existing
> group). If you want to have more than one BizTalk Server in a group, you w
ill
> need to use the Enterprise edition. More details in the FAQ here:
> http://download.microsoft.com/downl...icensingFAQ.doc
>
> Regards
>
> Owen
>
>
> "Michel" wrote:
> 

[ Post a follow-up to this message ]

Are you trying to doa remote deployment? if you are able to remotely deploy
the assembly note that it should still be put in to gac of the remote
asembly. You may have to use APP Center to do that,

What Administration aspects are you trying to achieve remotely?


--------------------
Thread-Topic: Need help to configure II
thread-index: AcSLdJS4d7BZ/lJVTBKs9xVRtPsGcw==
X-WBNR-Posting-Host: 80.61.87.76
From: examnotes <Michel@discussions.microsoft.com>
References:  <08529FC6-8A16-4859-A631-05878166F938@microsoft.com>
<D3D984CD-6862-48BA-BD96-DC49B8F4DFE0@microsoft.com>
Subject: RE: Need help to configure II
Date: Thu, 26 Aug 2004 06:57:10 -0700
Lines: 42
Message-ID: <C26CCC5F-F5E7-42AE-A11C-7BD9CF28390D@microsoft.com>
MIME-Version: 1.0
Content-Type: text/plain;
charset="Utf-8"
Content-Transfer-Encoding: 7bit
X-Newsreader: Microsoft CDO for Windows 2000
Content-Class: urn:content-classes:message
Importance: normal
Priority: normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
Newsgroups: microsoft.public.biztalk.setup
NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.1.29
Path: cpmsftngxa10.phx.gbl!TK2MSFTNGXA03.phx.gbl
Xref: cpmsftngxa10.phx.gbl microsoft.public.biztalk.setup:4444
X-Tomcat-NG: microsoft.public.biztalk.setup

Hi Owen,

I don't want another server.
I just want to be able to administer an existing server and deploy
assemblies from developer workstations.

Am I using the wrong installation?

Thanks,
Michel

"OwenCutajar" wrote:

> Hi Michel,
>
> The Standard edition of BizTalk server can only be used on one server
(i.e.
> only one server in the group, therefore no ability to join an existing
> group). If you want to have more than one BizTalk Server in a group, you
will
> need to use the Enterprise edition. More details in the FAQ here:
>
http://download.microsoft.com/downl...15-bd80-8c1c127
e88e7/LicensingFAQ.doc[vbcol=seagreen]
>
> Regards
>
> Owen
>
>
> "Michel" wrote:
> 
has to[vbcol=seagreen] 
allowed.[vbcol=seagreen] 
bar[vbcol=seagreen] 

[ Post a follow-up to this message ]

Hi Michel,

My guess would be that Microsoft consider "more than one BizTalk machine in
a BizTalk group" as being outside the scope of the license you're using. I'v
e
done what you are talking about using the Enterprise Edition, so it is
possible to do what you're saying, just with a different edition.

The deployment story in BTS2004 is a bit flaky in that you need a machine
with VS and Office to perform some of the functions easily. So you either
have a choice of sticking these on your production machine, or you can
package up anything you need to deploy (using the Depoyment Tool) and deploy
them that way.

Hope this helps,

Owen

---------------------------
http://www.u-g-h.com
---------------------------
"Michel" wrote:
[vbcol=seagreen]
> Hi Owen,
>
> I don't want another server.
> I just want to be able to administer an existing server and deploy
> assemblies from developer workstations.
>
> Am I using the wrong installation?
>
> Thanks,
> Michel
>
> "OwenCutajar" wrote:
> 

[ Post a follow-up to this message ]

Hi Naveen,

> Are you trying to doa remote deployment? if you are able to remotely deplo
y
> the assembly note that it should still be put in to gac of the remote
> asembly. You may have to use APP Center to do that,
Doesn't the Deployment wizard take care of this?
Does this mean I need to be physically behind the server?

> What Administration aspects are you trying to achieve remotely?
I just want to use the Visual Studio editors, that's it. Or better put, I
want to develop on another machine as the server.

Thanks,
Michel

[ Post a follow-up to this message ]

Hi Owen,

> The deployment story in BTS2004 is a bit flaky in that you need a machine
> with VS and Office to perform some of the functions easily. So you either
> have a choice of sticking these on your production machine, or you can
> package up anything you need to deploy (using the Depoyment Tool) and depl
oy
> them that way.
Are you suggesting to perform the actual deployment by sitting behind the
server machine?
I really starting to think this Standard version is completely useless. I
just want a server and another computer to do the development on. How
complicated can this be?
I feel completely ripped by MS, this is something they failed to mention
when asking about versions and prices.

Thanks for your reply,
Michel

[ Post a follow-up to this message ]

Hi Michel,

What you need is one machine with the Developer edition on it, on which you
devlop, test and package any artifacts you need. Once you have packaged them
up (using the BizTalk Deploment Wizard), you can move them to the production
server (running the Standard version of BizTalk) and deploy and test them
there.

How does this sound ?

Regards

Owen

"Michel" wrote:

> Hi Owen,
> 
> Are you suggesting to perform the actual deployment by sitting behind the
> server machine?
> I really starting to think this Standard version is completely useless. I
> just want a server and another computer to do the development on. How
> complicated can this be?
> I feel completely ripped by MS, this is something they failed to mention
> when asking about versions and prices.
>
> Thanks for your reply,
> Michel

[ Post a follow-up to this message ]

Hi Owen,

Thanks for all the help. This sounds like the way to go (though I'd prefer
to deploy directly).
I still feel a bit cheated reading the price list "$749 US per developer". I
wish the sales people at MS would have been more explicit about what it is
that you need for BTS to work. I had the impression one BTS server licence
and VS for a developer would be enough. Oh well...

Thanks,
Michel
=======
"OwenCutajar" wrote:
[vbcol=seagreen]
> Hi Michel,
>
> What you need is one machine with the Developer edition on it, on which yo
u
> devlop, test and package any artifacts you need. Once you have packaged th
em
> up (using the BizTalk Deploment Wizard), you can move them to the producti
on
> server (running the Standard version of BizTalk) and deploy and test them
> there.
>
> How does this sound ?
>
> Regards
>
> Owen
>
> "Michel" wrote:
> 

[ Post a follow-up to this message ]