| Martin Krieger 2006-04-27, 7:26 am |
| > - It seems to be necessary, that the local account for BizTalk basic
> configuration must be an administrator. Otherwise the EntSSO
> configuration fails. And if I now move the account from the
> administrators group to the users group the EntSSO startup still fails
This problem was caused by inconsistent user groups in the SQL Server
and Windows. At some point of my installation attempts there was a SQL
logon for the 'SSO Administrators' Windows group created. Then the
Windows group was removed and recreated - resulting in a SQL logon which
looks like linking to a windows group but in fact not connected to any
existing item.
Does anybody know a tool to trace such Windows / SQL Server
'inconsistent sid' issues with less effort? Is it possible to change the
sid of an existing SQL logon or is delete and recreate the only solution?
> - If the BTSUser account is an administrator, I can start all services
> and BizTalk works as expected. But on system startup the EntSSO service
> first fails, causing BizTalk startup to fail. But after a while the
> EntSSO service starts again, successfully. But then I need to start the
> BizTalk service by hand:
This issue is still open.
Martin
|