| jredfield 2005-02-17, 2:46 am |
| I had BizTalk Server 2004 installed, configured and running just fine
for several weeks. I recently installed several Windows updates that
I was prompted to install. My configuration is Windows 2000 Server
with SP4, BizTalk 2004, and SQL Server 2000, all on one PC.
A few days after installing the updates, I tried to start an
orchestration for the first time after the updates were installed. It
had previously ran fine for weeks. It failed to start, and I traced
the problem to the Enterprise Single Sign-On service not running.
When I try to start it manually, I get an access denied error.
Looking in the Event Viewer, I see the message:
"The SSO service could not start because the service account it is
running under is not a member of the SSO Admin account.
SSO Admin account: SSO Administrators
SSO service account: KNI\KNOXDEV$
The KNI is our domain, and KNOXDEV is the machine name. When I log
onto this PC, I use a domain admin account, which is also a member of
SSO Administrators, and every other BizTalk group that was created.
When I configure the SSO service (in the service properties dialog
box) to use the Local System Account, I get the error described
above. If I click on "This account" and enter the username and
password which I log onto the machine with, I get another error in
the Event Viewer:
"Could not start the Enterprise Single Sign-On Service service on
Local Computer. Error 1069: The service did not start due to a logon
failure."
I don't recall what Windows updates were installed, since I really
wasn't presented with the list of updates--I just installed them when
prompted to do so. I don't know if one of those files caused the SSO
problem.
Please help!
Thanks,
John
|