| Paul Davidson 2004-10-25, 5:48 pm |
| From the dev:
<snip>
Recent problems have been due to users reconfiguring localhost so that it’s
no longer 127.0.0.1. I think the easiest way to check it to run “ping
localhost” at a command prompt – it should resolve to 127.0.0.1. The other
way is to look in c:\WINDOWS\system32\drivers\etc\hosts, and make sure
there is a line “127.0.0.1 localhost” in it (and only 1 definition of
localhost, as well).
The other previous issue had to do with port 3132 being used when the
Update Service attempted to open it. However, we now “reserve” the port
during setup, although that doesn’t take effect until the next reboot. But
if they’ve tried over several days, it should not be the problem,
especially if they have rebooted in-between attempts. (Now this doesn’t
stop a different app from specifically asking for port 3132, but since the
port number is registered to us, it shouldn’t happen).
When the Update Service fails to start, it should log something in the
application event log. In some cases the account doesn’t have permission to
create a new category (in this case, “RuleEngineUpdateService”), so the
writing fails. The way around this is to configure the Rule Engine Update
Service to use an administrator’s account, so you can see the log.
<snip>
--------------------
X-Tomcat-ID: 492262691
References: <3E0283CA-0977-4B52-BC0D-5C9DCBA38C48@microsoft.com>
<G7AOt1lWEHA.1996@cpmsftngxa10.phx.gbl>
<31B29B6E-B5A7-4C27-8052-6E403E154416@microsoft.com>
<vD2PBtweEHA.1576@cpmsftngxa06.phx.gbl>
<AB2C0F97-4E7A-410F-9750-E88878BFDF33@microsoft.com>
<ATj7j$vfEHA.2876@cpmsftngxa06.phx.gbl>
<RtZEmMLgEHA.3356@cpmsftngxa06.phx.gbl>
<CGkROTLgEHA.3356@cpmsftngxa06.phx.gbl>
<D2635F26-A613-4F4F-95DB-C731BB08F6D9@microsoft.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_0001_097FA112"
Content-Transfer-Encoding: 7bit
From: paulda@online.microsoft.com (Paul Davidson)
Organization: Microsoft
Date: Mon, 25 Oct 2004 20:22:16 GMT
Subject: RE: Provider load failure RuleEngineConfig initial installation BT
X-Tomcat-NG: microsoft.public.biztalk.setup
Message-ID: <DuF9SBtuEHA.2092@cpmsftngxa10.phx.gbl>
Newsgroups: microsoft.public.biztalk.setup
Lines: 1438
Path: cpmsftngxa10.phx.gbl
Xref: cpmsftngxa10.phx.gbl microsoft.public.biztalk.setup:4806
NNTP-Posting-Host: TOMCATIMPORT1 10.201.218.122
I recently reproed a simular issue on Win2003. Please try this fix while I
send ask the devs to look into this.
Check if you have a host file entry that precedes local host(127) by name
or address. 127.0.0.1 localhost should be the first entry in your host
file(%systemroot%\system32\drivers\etc\h
osts). Please let us know if that
helps.
--------------------
Thread-Topic: Provider load failure RuleEngineConfig initial installation BT
thread-index: AcSq1GKy90ixs/RmRe+bSlagnBchBw==
X-WBNR-Posting-Host: 204.153.206.15
From: "=?Utf-8?B?Um9iZXJ0Qg==?=" <RobertB@discussions.microsoft.com>
References: <3E0283CA-0977-4B52-BC0D-5C9DCBA38C48@microsoft.com>
<G7AOt1lWEHA.1996@cpmsftngxa10.phx.gbl>
<31B29B6E-B5A7-4C27-8052-6E403E154416@microsoft.com>
<vD2PBtweEHA.1576@cpmsftngxa06.phx.gbl>
<AB2C0F97-4E7A-410F-9750-E88878BFDF33@microsoft.com>
<ATj7j$vfEHA.2876@cpmsftngxa06.phx.gbl>
<RtZEmMLgEHA.3356@cpmsftngxa06.phx.gbl>
<CGkROTLgEHA.3356@cpmsftngxa06.phx.gbl>
Subject: RE: Provider load failure RuleEngineConfig initial installation BT
Date: Tue, 5 Oct 2004 05:11:03 -0700
Lines: 580
Message-ID: <D2635F26-A613-4F4F-95DB-C731BB08F6D9@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: cpmsftngxa06.phx.gbl!TK2MSFTNGXA03.phx.gbl
Xref: cpmsftngxa06.phx.gbl microsoft.public.biztalk.setup:4691
X-Tomcat-NG: microsoft.public.biztalk.setup
Just wondering if anything has been found out regarding this problem. Is
more information needed? Any status whatsoever? This has put a bit of a
crimp in some planned development and any help to resolve this for future
efforts would be appreciated.
"Paul Davidson" wrote:
> Also run depends.exe on Biztalk's provider as well. <biztalk install
> directory>\BtsWmiProvider.dll
>
> -paul
> --------------------
> Newsgroups: microsoft.public.biztalk.setup
> From: paulda@online.microsoft.com (Paul Davidson)
> Organization: Microsoft
> Date: Thu, 12 Aug 2004 21:27:16 GMT
> Subject: RE: Provider load failure RuleEngineConfig initial installation
BT
> X-Tomcat-NG: microsoft.public.biztalk.setup
> MIME-Version: 1.0
> Content-Type: multipart/alternative;
> boundary="--Next.Tomcat.Message.With.ASCII.and.RTF.8973497230230"
> Content-Transfer-Encoding: 7bit
>
> Robert, can you check the wbem logs in %systemroot%\system32\wbem\logs?
> Also run depends.exe on the WMI provider dll.
> %systemroot%\system32\wbem\wmiprov.dll
>
> depends.exe(dependency walker) is a tool that comes with support tools,
VS
> or platform SDK - essentially it should be on a dev box. Let me know if
> you can't find it.
>
> -paul
> --------------------
> X-Tomcat-ID: 452990167
> References: <3E0283CA-0977-4B52-BC0D-5C9DCBA38C48@microsoft.com>
> <G7AOt1lWEHA.1996@cpmsftngxa10.phx.gbl>
> <31B29B6E-B5A7-4C27-8052-6E403E154416@microsoft.com>
> <vD2PBtweEHA.1576@cpmsftngxa06.phx.gbl>
> <AB2C0F97-4E7A-410F-9750-E88878BFDF33@microsoft.com>
> MIME-Version: 1.0
> Content-Type: multipart/alternative;
boundary="----=_NextPart_0001_1727FE58"
> Content-Transfer-Encoding: 7bit
> From: paulda@online.microsoft.com (Paul Davidson)
> Organization: Microsoft
> Date: Tue, 10 Aug 2004 17:31:34 GMT
> Subject: RE: Provider load failure RuleEngineConfig initial installation
BT
> X-Tomcat-NG: microsoft.public.biztalk.setup
> Message-ID: <ATj7j$vfEHA.2876@cpmsftngxa06.phx.gbl>
> Newsgroups: microsoft.public.biztalk.setup
> Lines: 1165
> Path: cpmsftngxa06.phx.gbl
> Xref: cpmsftngxa06.phx.gbl microsoft.public.biztalk.setup:4336
> NNTP-Posting-Host: tomcatimport2.phx.gbl 10.201.218.182
>
> Just to let you know, I forwarded on your issue to the feature team to
see
> if they can help. I'll post(or they will) as soon as I hear back from
them.
>
> -paul
> --------------------
> Thread-Topic: Provider load failure RuleEngineConfig initial installation
BT
> thread-index: AcR7DhHa4zXQMQv6R8OIFHJNQ35YRA==
> X-WBNR-Posting-Host: 204.153.206.15
> From: "=?Utf-8?B?Um9iZXJ0Qg==?=" <RobertB@discussions.microsoft.com>
> References: <3E0283CA-0977-4B52-BC0D-5C9DCBA38C48@microsoft.com>
> <G7AOt1lWEHA.1996@cpmsftngxa10.phx.gbl>
> <31B29B6E-B5A7-4C27-8052-6E403E154416@microsoft.com>
> <vD2PBtweEHA.1576@cpmsftngxa06.phx.gbl>
> Subject: RE: Provider load failure RuleEngineConfig initial installation
BT
> Date: Thu, 5 Aug 2004 10:03:03 -0700
> Lines: 444
> Message-ID: <AB2C0F97-4E7A-410F-9750-E88878BFDF33@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: cpmsftngxa06.phx.gbl!TK2MSFTNGXA03.phx.gbl
> Xref: cpmsftngxa06.phx.gbl microsoft.public.biztalk.setup:4304
> X-Tomcat-NG: microsoft.public.biztalk.setup
>
> Thank you for your quick reply. The kb was 839186. It didn't match the
> hr but the error message ("failed to load configuration data for
> feature: RulesEngine") was the same. I can't find anything that appears
> directly related in event viewer (I had checked the app and system logs
> previously), however, I did find this:
>
> ======================================
> Event Type: Warning
> Event Source: WinMgmt
> Event Category: None
> Event ID: 47
> Date: 8/5/2004
> Time: 12:21:51 AM
> User: N/A
> Computer: WD-ROBERTB-XP
> Description:
> WMI ADAP was unable to retrieve data from the PerfLib subkey:
> SYSTEM\CurrentControlSet\Services\mssind
ex\Performance\Library, error
code:
> 0x80041009
>
> For more information, see Help and Support Center at
> http://go.microsoft.com/fwlink/events.asp.
> ======================================
>
> It's the only WMI related message I find and the time it happened is a bit
> off (though I was trying to configure this just before that time,
> unfortunately). The message also doesn't appear again since that time,
> and I've given it a shot a couple times since then.
>
> As far as the path variables, the system32 and system32/wbem
> are there (I did restart the system at least a couple times in my attempts
> to get the configuration wizard to work, hoping that this would perform
> some voodoo). I'll admit, I'm real weak on WMI right now, so I'm not
> really sure what to be looking for with that. If there's any other info
> you need, let me know.
>
> Thanks again.
>
>
> "Paul Davidson" wrote:
>
installation
> BT
installation
> BT
comes[vbcol=seagreen]
SSOServer[vbcol=seagreen]
> RulesEngine
> Configured:
Installed:[vbcol=seagreen]
> Configured:
Installed:[vbcol=seagreen]
> yes
yes[vbcol=seagreen]
> Configured:
Installed:[vbcol=seagreen]
yes[vbcol=seagreen]
> yes
> WMI
> installed
> for:
> for:
> for:
> MOT
> for:
> for:
> for:
RulesEngine[vbcol=seagreen]
namespace[vbcol=seagreen]
>
c:\depot4000\jupiter\source\private\moza
rt\source\engine\rules\configfwkext\[vbc
ol=seagreen]
>
c:\depot4000\jupiter\source\private\moza
rt\source\engine\rules\configfwkext\[vbc
ol=seagreen]
> to
> file
>
c:\depot4000\jupiter\source\private\comm
on\configwizard\exe\jupiterconfigtoo[vbc
ol=seagreen]
>[/vbcol]
c:\depot4000\jupiter\source\private\comm
on\configwizard\exe\jupiterconfigtoo[vbc
ol=seagreen]
> Configured:
Installed:
> Configured:
Installed:
> yes
yes
> Configured:
Installed:[vbcol=seagreen]
yes[vbcol=seagreen]
> yes
ProgID:[vbcol=seagreen]
> Engine
HwsWMIProvider[vbcol=seagreen]
HwsWebService[vbcol=seagreen]
Engine,BTSCfg[vbcol=seagreen]
MessageQueuing[vbcol=seagreen]
> SSOServer,Engine
> ProgID:
> problems,
> the
> The
> errors
> installation
> BTS
I[vbcol=seagreen]
>
c:\depot4000\jupiter\source\private\moza
rt\source\engine\rules\configfwkext\[vbc
ol=seagreen]
>
c:\depot4000\jupiter\source\private\moza
rt\source\engine\rules\configfwkext\[vbc
ol=seagreen]
to
>
c:\depot4000\jupiter\source\private\comm
on\configwizard\exe\jupiterconfigtoo[vbc
ol=seagreen]
>
c:\depot4000\jupiter\source\private\comm
on\configwizard\exe\jupiterconfigtoo[vbc
ol=seagreen]
> Configured:
>
>
>
>
>[/vbcol]
|