|
Home > Archive > BizTalk Server Setup > February 2005 > BTS2004: ConfigFramework problem
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 |
BTS2004: ConfigFramework problem
|
|
|
| ConfigFramework fails with the error "Rules Engine Update Service failed to
start. See event viewer for more details.". In event viewer i cannot find
any errors. After ConfigFramework rollbacks changes made to the system,
Rules Engine Update Service status is "Starting", StartupType is "Disabled".
OS: Windows XP SP2
Installtion of all necessary Software Prerequisites was performed step by
step by recommendations given in
http://download.microsoft.com/downl...llation%20Guide(EN).htm#ebiz_depl_install_godj
and was successfull with no errors. Installation of all components BTS2004
was successful with no errors. I checked port 3132 using "netstat -ano" -
noone is listening to it.
When I tried to install and configure BTS2004 using VMware Workstation with
installed just XP SP2 and no other applications - ConfigFramework succeeds.
What could be wrong? I've attached ConfigFramework log file.
Thanks.
| |
|
| Sorry, the log file is too big. Here is the section with error:
[15:54:50 Info ConfigHelper] NT Service: ENTSSO does not exist
[15:54:59 Info ConfigFramework] Waiting for configuration thread to
complete.
[15:55:10 Info ConfigFramework] Waiting for configuration thread to
complete.
[15:55:21 Info ConfigFramework] Waiting for configuration thread to
complete.
[15:55:22 Info ConfigHelper] bz_dev is a local entity.
[15:55:22 Info ConfigHelper] Granted 'Logon as Service' permission to
account: domain\bz_dev
[15:55:22 Info ConfigHelper] Creating service: ENTSSO, start type: 2, exe:
C:\Program Files\Common Files\Enterprise Single Sign-On\ENTSSO.exe,
dependencies: WMI,RPCSS,COMSysApp,MSSQLSERVER, account: domain\bz_dev
[15:55:23 Info ConfigHelper] Created service: ENTSSO
[15:55:23 Info SSOServerCfg] Installing Single Sign-On (SSO) performance
counters
[15:55:24 Info SSOServerCfg] Starting the Single Sign-On (SSO) service using
domain\bz_dev account
[15:55:25 Info SSOServerCfg] Checking the Single Sign-On (SSO) service state
on COMPUTERNAME
[15:55:25 Info SSOServerCfg] The Single Sign-On (SSO) service state on
COMPUTERNAME is 0X00000002
[15:55:25 Info SSOServerCfg] Checking the Single Sign-On (SSO) service state
on COMPUTERNAME
[15:55:25 Info SSOServerCfg] The Single Sign-On (SSO) service state on
COMPUTERNAME is 0X00000002
[15:55:26 Info SSOServerCfg] Checking the Single Sign-On (SSO) service state
on COMPUTERNAME
[15:55:26 Info SSOServerCfg] The Single Sign-On (SSO) service state on
COMPUTERNAME is 0X00000002
[15:55:26 Info SSOServerCfg] Checking the Single Sign-On (SSO) service state
on COMPUTERNAME
[15:55:26 Info SSOServerCfg] The Single Sign-On (SSO) service state on
COMPUTERNAME is 0X00000002
[15:55:26 Info SSOServerCfg] Checking the Single Sign-On (SSO) service state
on COMPUTERNAME
[15:55:26 Info SSOServerCfg] The Single Sign-On (SSO) service state on
COMPUTERNAME is 0X00000002
[15:55:26 Info SSOServerCfg] Checking the Single Sign-On (SSO) service state
on COMPUTERNAME
[15:55:26 Info SSOServerCfg] The Single Sign-On (SSO) service state on
COMPUTERNAME is 0X00000002
[15:55:26 Info SSOServerCfg] Checking the Single Sign-On (SSO) service state
on COMPUTERNAME
[15:55:26 Info SSOServerCfg] The Single Sign-On (SSO) service state on
COMPUTERNAME is 0X00000002
[15:55:27 Info SSOServerCfg] Checking the Single Sign-On (SSO) service state
on COMPUTERNAME
[15:55:27 Info SSOServerCfg] The Single Sign-On (SSO) service state on
COMPUTERNAME is 0X00000002
[15:55:27 Info SSOServerCfg] Checking the Single Sign-On (SSO) service state
on COMPUTERNAME
[15:55:27 Info SSOServerCfg] The Single Sign-On (SSO) service state on
COMPUTERNAME is 0X00000002
[15:55:27 Info SSOServerCfg] Checking the Single Sign-On (SSO) service state
on COMPUTERNAME
[15:55:27 Info SSOServerCfg] The Single Sign-On (SSO) service state on
COMPUTERNAME is 0X00000002
[15:55:27 Info SSOServerCfg] Checking the Single Sign-On (SSO) service state
on COMPUTERNAME
[15:55:27 Info SSOServerCfg] The Single Sign-On (SSO) service state on
COMPUTERNAME is 0X00000002
[15:55:27 Info SSOServerCfg] Checking the Single Sign-On (SSO) service state
on COMPUTERNAME
[15:55:27 Info SSOServerCfg] The Single Sign-On (SSO) service state on
COMPUTERNAME is 0X00000002
[15:55:28 Info SSOServerCfg] Checking the Single Sign-On (SSO) service state
on COMPUTERNAME
[15:55:28 Info SSOServerCfg] The Single Sign-On (SSO) service state on
COMPUTERNAME is 0X00000002
[15:55:28 Info SSOServerCfg] Checking the Single Sign-On (SSO) service state
on COMPUTERNAME
[15:55:28 Info SSOServerCfg] The Single Sign-On (SSO) service state on
COMPUTERNAME is 0X00000002
[15:55:28 Info SSOServerCfg] Checking the Single Sign-On (SSO) service state
on COMPUTERNAME
[15:55:28 Info SSOServerCfg] The Single Sign-On (SSO) service state on
COMPUTERNAME is 0X00000004
[15:55:28 Info SSOServerCfg] The Single Sign-On (SSO) service is running
[15:55:28 Info SSOServerCfg] Generating the Master Secret
[15:55:28 Info SSOServerCfg] Leaving function:
CSSOServerCfg::ConfigureFeature
[15:55:28 Info ConfigFramework] Successfully configured feature:
SSOServer,Engine
[15:55:28 Info ConfigFramework] Retrieved cached IConfig object for feature:
MessageQueuing ProgID: MSEBiz.MSMQTConfig
[15:55:28 Info ConfigFramework] Currently configuring: MessageQueuing
[15:55:28 Info MSMQTConfig] Entering function:
CMSMQTConfig::ConfigureFeature
[15:55:28 Info MSMQTConfig] Message Queuing will use computer name
COMPUTERNAME
[15:55:28 Info MSMQTConfig] Message Queuing will bind to all IP addresses on
this computer (no side-by-side mode)
[15:55:28 Info MSMQTConfig] Leaving function: CMSMQTConfig::ConfigureFeature
[15:55:28 Info ConfigFramework] Successfully configured feature:
MessageQueuing
[15:55:28 Info ConfigFramework] Retrieved cached IConfig object for feature:
RulesEngine ProgID: MSEBiz.RuleEngineConfig
[15:55:28 Info ConfigFramework] Currently configuring: RulesEngine
[15:55:28 Info RuleEngineConfig] Entering function:
CRuleEngineConfig::ConfigureFeature
[15:55:28 Info RuleEngineConfig] Configuring Feature: RulesEngine
[15:55:28 Info ConfigHelper] Connected to WMI namespace
[15:55:28 Info ConfigHelper] set security credentials to WMI namespace
[15:55:29 Info ConfigHelper] Did not find existing database:
BizTalkRuleEngineDb on computer: COMPUTERNAME
[15:55:30 Info ConfigHelper] Created SQL database: BizTalkRuleEngineDb on
computer: COMPUTERNAME collation: Default
[15:55:30 Info ConfigHelper] Executed SQL script: C:\Program
Files\Microsoft BizTalk Server 2004\Schema\\BTS_Security_Logic.sql on
database: BizTalkRuleEngineDb on computer: COMPUTERNAME
[15:55:30 Info ConfigHelper] Executed SQL script: C:\Program
Files\Microsoft BizTalk Server 2004\Schema\\BTS_Version_Schema.sql on
database: BizTalkRuleEngineDb on computer: COMPUTERNAME
[15:55:30 Info ConfigHelper] Executed SQL script: C:\Program
Files\Microsoft BizTalk Server 2004\Schema\\BTS_Version_Logic.sql on
database: BizTalkRuleEngineDb on computer: COMPUTERNAME
[15:55:30 Info ConfigHelper] Executed SQL script: C:\Program
Files\Microsoft BizTalk Server 2004\Schema\\Backup_Setup_All_Tables.sql on
database: BizTalkRuleEngineDb on computer: COMPUTERNAME
[15:55:30 Info ConfigHelper] Executed SQL script: C:\Program
Files\Microsoft BizTalk Server 2004\Schema\\Backup_Setup_All_Procs.sql on
database: BizTalkRuleEngineDb on computer: COMPUTERNAME
[15:55:31 Info ConfigHelper] Executed SQL script: C:\Program
Files\Microsoft BizTalk Server 2004\Schema\\BTS_RulesEngine_Schema.sql on
database: BizTalkRuleEngineDb on computer: COMPUTERNAME
[15:55:32 Info ConfigHelper] Executed SQL script: C:\Program
Files\Microsoft BizTalk Server 2004\Schema\\BTS_RulesEngine_Logic.sql on
database: BizTalkRuleEngineDb on computer: COMPUTERNAME
[15:55:32 Info ConfigHelper] Connected to WMI namespace
[15:55:32 Info ConfigHelper] set security credentials to WMI namespace
[15:55:32 Info ConfigFramework] Waiting for configuration thread to
complete.
[15:55:33 Info ConfigHelper] NT Service: RuleEngineUpdateService does not
exist
[15:55:33 Info ConfigHelper] bz_dev is a local entity.
[15:55:33 Info ConfigHelper] Granted 'Logon as Service' permission to
account: domain\bz_dev
[15:55:33 Info ConfigHelper] Creating service: RuleEngineUpdateService,
start type: 2, exe: C:\Program Files\Microsoft BizTalk Server
2004\RuleEngineUpdateService.exe, dependencies: (null), account:
domain\bz_dev
[15:55:35 Info ConfigHelper] Created service: RuleEngineUpdateService
[15:55:43 Info ConfigFramework] Waiting for configuration thread to
complete.
[15:55:54 Info ConfigFramework] Waiting for configuration thread to
complete.
[15:55:55 Error RuleEngineConfig] The Rule Engine Update Service failed to
start. Please check the Event Viewer for more details.
[15:55:55 Error RuleEngineConfig]
c:\depot4000\jupiter\source\private\moza
rt\source\engine\rules\configfwkext\exte
nsion\ruleengineconfig.cpp(573):
FAILED hr = 80004005
[15:55:55 Info RuleEngineConfig] Leaving function:
CRuleEngineConfig::ConfigureFeature
[15:55:57 Info ConfigFramework] Showing MessageBox with text: The Rule
Engine Update Service failed to start. Please check the Event Viewer for
more details. Return Code: 2
[15:55:57 Error ConfigFramework]
c:\depot4000\jupiter\source\private\comm
on\configwizard\exe\configthread.cpp(556):
FAILED hr = 80004005
[15:55:57 Error ConfigFramework]
****************************************
******
[15:55:57 Error ConfigFramework] *** Configuration failed - Rolling back...
***
[15:55:57 Error ConfigFramework]
****************************************
******
[15:55:57 Error ConfigFramework] Configuration failed - rolling back...
| |
|
| I found the solution. Panda Platinum Internet Security antivirus was
installed on my PC. When I disabled all types of protection - it didn't
help. When I stopped and disabled all Panda services - it didn't help.
ConfigFramework sucessfully completed only when I completely uninstalled
antivirus.
|
|
|
|
|