|
Home > Archive > BizTalk Server Setup > January 2005 > ConfigFramework Error - Enterprise Single Sign-On Service
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 |
ConfigFramework Error - Enterprise Single Sign-On Service
|
|
| Ricardo Quintanilla 2004-12-28, 7:49 am |
| i tried to install biztalk server 2004 on a Windows XP professional sp2 many
times, at least 10 times, but i cannot get success. i mean, the setup is
success, but when run the configuration tool always fall when place settings
for enterprise single sign-on. i have created a special account for the
service. it is an account with no special privilegies, just a user.
i have followed all the advises inside many support articles about
installing biztalk server on a Windows XP professional service pack, even
have disabled the windows firewall, in fact actually i am not using windows
firewall in order
to install biztalk server.
the configuration tool always fall with the following message:
"The Single Sign-On (SSO) Service on WXPPRO did not start within the
time-out limit"
here is the log file
[22:47:58 Info ConfigHelper] SQL Server name is: WXPPRO
[22:47:58 Info SSOServerCfg] Granting login access to Single Sign-On (SSO)
database SSODB on WXPPRO for SSO Administrators account
[22:47:59 Info ConfigHelper] NT Service: ENTSSO does not exist
[22:48:00 Info ConfigHelper] SSOService is a local entity.
[22:48:01 Info ConfigHelper] Granted 'Logon as Service' permission to
account: WXPPRO\SSOService
[22:48:01 Info ConfigHelper] Creating service: ENTSSO, start type: 2, exe:
E:\Program Files\Common Files\Enterprise Single Sign-On\ENTSSO.exe,
dependencies: WMI,RPCSS,COMSysApp,MSSQLSERVER, account: WXPPRO\SSOService
[22:48:01 Info ConfigFramework] Waiting for configuration thread to complete.
[22:48:02 Info ConfigHelper] Created service: ENTSSO
[22:48:02 Info SSOServerCfg] Installing Single Sign-On (SSO) performance
counters
[22:48:04 Info SSOServerCfg] Starting the Single Sign-On (SSO) service using
SSOService account
[22:48:09 Info SSOServerCfg] Checking the Single Sign-On (SSO) service state
on WXPPRO
[22:48:09 Info SSOServerCfg] The Single Sign-On (SSO) service state on
WXPPRO is 0X00000002
[22:48:09 Info SSOServerCfg] Checking the Single Sign-On (SSO) service state
on WXPPRO
[22:48:09 Info SSOServerCfg] The Single Sign-On (SSO) service state on
WXPPRO is 0X00000002
[22:48:10 Info SSOServerCfg] Checking the Single Sign-On (SSO) service state
on WXPPRO
[22:48:10 Info SSOServerCfg] The Single Sign-On (SSO) service state on
WXPPRO is 0X00000002
[22:48:10 Info SSOServerCfg] Checking the Single Sign-On (SSO) service state
on WXPPRO
[22:48:10 Info SSOServerCfg] The Single Sign-On (SSO) service state on
WXPPRO is 0X00000002
[22:48:10 Info SSOServerCfg] Checking the Single Sign-On (SSO) service state
on WXPPRO
[22:48:10 Info SSOServerCfg] The Single Sign-On (SSO) service state on
WXPPRO is 0X00000002
[22:48:10 Info SSOServerCfg] Checking the Single Sign-On (SSO) service state
on WXPPRO
[22:48:10 Info SSOServerCfg] The Single Sign-On (SSO) service state on
WXPPRO is 0X00000002
[22:48:10 Info SSOServerCfg] Checking the Single Sign-On (SSO) service state
on WXPPRO
[22:48:10 Info SSOServerCfg] The Single Sign-On (SSO) service state on
WXPPRO is 0X00000002
[22:48:11 Info SSOServerCfg] Checking the Single Sign-On (SSO) service state
on WXPPRO
[22:48:11 Info SSOServerCfg] The Single Sign-On (SSO) service state on
WXPPRO is 0X00000002
[22:48:11 Info SSOServerCfg] Checking the Single Sign-On (SSO) service state
on WXPPRO
[22:48:11 Info SSOServerCfg] The Single Sign-On (SSO) service state on
WXPPRO is 0X00000002
[22:48:11 Info SSOServerCfg] Checking the Single Sign-On (SSO) service state
on WXPPRO
[22:48:11 Info SSOServerCfg] The Single Sign-On (SSO) service state on
WXPPRO is 0X00000002
[22:49:17 Error SSOServerCfg]
c:\depot4000\jupiter\source\private\moza
rt\source\sso\ssoconfiguration\ssoserver
cfg\ssoservercfgimpl.cpp(1174):
The Single Sign-On (SSO) Service on WXPPRO did not start within the time-out
limit.
[22:49:17 Info SSOServerCfg] Leaving function: CSSOServerCfg::ConfigureFeature
[22:49:20 Info ConfigFramework] Showing MessageBox with text: The Single
Sign-On (SSO) Service on WXPPRO did not start within the time-out limit.
Return Code: 2
[22:49:20 Error ConfigFramework]
c:\depot4000\jupiter\source\private\comm
on\configwizard\exe\configthread.cpp(556): FAILED hr = 80004005
| |
|
| I have the same problem in installing 2k4.
I had tried everything i could to deal with it ,but all failed.
| |
| Imran Noor 2005-01-03, 2:47 am |
| It really works because i experienced it twice and it resolved the
configuration issues but dont claim that its the right way to do this.
All i want to share, because it took almost one working day to resolve, i
was installing Biztalk 2004 on two systems, one with Windows XP SP2 and the
otherone with Windows Server 2003 just for the R&D purpose, the conflict i
faced during this, every thing seems to be fine with pre-requirements and
installations but when it comes to the configuration part, it fails with the
smiliar messages like mentioned below . I was using a domain user account
with Local Administrator membership during the whole journey. The problems
resolved after i logged on locally with administrative rights. Still didnt
found any related material but it works.
The documentation that says all you need a account with the membership of
Local Administrators group but it dont works. Looking for the Biztalk gurus
to comment on this........
Regards,
Imran Noor
"zephr" <zephr@discussions.microsoft.com> wrote in message
news:4734D30A-5679-4AEA-AA0E-6C899C4431C0@microsoft.com...
>I have the same problem in installing 2k4.
> I had tried everything i could to deal with it ,but all failed.
| |
| Vinod Kancharla 2005-01-05, 5:53 pm |
| Ricardo,
You might be running into a known issue with XP SP2. This is documented in
the following KB article:
http://support.microsoft.com/?id=841893
Another possible reason:
# Issue using SSO Administrators accounts re-created in Active Directory
This issue occurs if the SSO Administrator account has been granted SQL
access, deleted from Active Directory, and then re-created. The new SSO
Administrators account has a different SID and the SSO service account,
running as a member of the original SSO Administrator account, is denied
access to the database.
As a work around, when the account is deleted from Active Directory, it
recommended that you manually delete the account from the list of allowed
login accounts using the SQL Enterprise Manager administrative tool.
This posting is provided "AS IS" with no warranties, and confers no rights.
"Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
|
|
|
|
|