|
Home > Archive > BizTalk Server Setup > September 2004 > Totally wasting time setting up BizTalk
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 |
Totally wasting time setting up BizTalk
|
|
| Very Frustrated Microsoft User 2004-08-29, 5:49 pm |
| I don't understand how come Microsoft would come out such non-QAed product.
Anyway, I have spent lots of time to configure BizTalk. Now I stuck at the
following errors in the log file.
[10:25:02 AM Error ConfigHelper] Connect to WMI failed on IIS v2
[10:25:02 AM Error ConfigHelper] Invalid namespace
From UI, it prompts premature complete msg box in loop while only 2/3 way to
the 100% in progress bar.
PLEASE HELP!!! Microsoft should be doing better than this.
| |
| Stefan Thurow 2004-09-02, 6:18 pm |
| I've installed BizTalk several times on different environments. From my
experience you shouldn't run into any issues *IF* you read and follow the
installation guide at http://go.microsoft.com/fwlink/?linkid=22120.
Just to set you expectations right: A BizTalk installation is not as easy as
installing Office, it's a pretty complex product targeted at IT
professionals. But if you follow the instructions, you should be able to
succeseed.
Cheers
Stefan
"Very Frustrated Microsoft User" wrote:
> I don't understand how come Microsoft would come out such non-QAed product.
> Anyway, I have spent lots of time to configure BizTalk. Now I stuck at the
> following errors in the log file.
>
> [10:25:02 AM Error ConfigHelper] Connect to WMI failed on IIS v2
> [10:25:02 AM Error ConfigHelper] Invalid namespace
>
> From UI, it prompts premature complete msg box in loop while only 2/3 way to
> the 100% in progress bar.
>
> PLEASE HELP!!! Microsoft should be doing better than this.
>
| |
| Paul Davidson 2004-09-03, 5:49 pm |
| First try configframework /u to undo any partial config that is there. If
it fails again, please attach the complete config log and any errors that
are in the eventvwr.
--------------------
Thread-Topic: Totally wasting time setting up BizTalk
thread-index: AcSN7xc7oOhXFRa3RzeznZKVofqNiA==
X-WBNR-Posting-Host: 63.206.92.129
From: =?Utf-8?B? VmVyeSBGcnVzdHJhdGVkIE1pY3Jvc29mdCBVc2Vy
?= <Very Frustrated
Microsoft User@discussions.microsoft.com>
Subject: Totally wasting time setting up BizTalk
Date: Sun, 29 Aug 2004 10:39:09 -0700
Lines: 12
Message-ID: <A9200808-6A8D-4B6D-868B-F42A6EAADABA@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:4454
X-Tomcat-NG: microsoft.public.biztalk.setup
I don't understand how come Microsoft would come out such non-QAed product.
Anyway, I have spent lots of time to configure BizTalk. Now I stuck at the
following errors in the log file.
[10:25:02 AM Error ConfigHelper] Connect to WMI failed on IIS v2
[10:25:02 AM Error ConfigHelper] Invalid namespace
From UI, it prompts premature complete msg box in loop while only 2/3 way
to
the 100% in progress bar.
PLEASE HELP!!! Microsoft should be doing better than this.
|
|
|
|
|