I’m currently building a new XI R3.1 server in order to roll out R3.1. We currently have a development server running R3.1 fine.
I’m trying to start the SIA with a network account which has been in use with the dev. server fine since it was created, and still working perfectly well (but its not once I built). However when I try and enter the credentials and try to start it, it tells me it was unable to start due to logon failure. It works fine with my network account, and as I say, the dev. server is using this account fine.
I’m sure this is going to be something really simple, so can someone point me in the right direction?
It’s likely / possible that you’re not logging into the CMS database - what did you set up to use for that, are you sure you’re making that connection?
can be many possible reasons for this - the one’s that I have run into are listed below -
-Server not being recognized in the domain.
-Service account (the network account that you are talking about) is not an local administrator
-might also depend on how the service account is created - sometimes interactive logon is denied based on group policies, but since you confirm that the dev instance is running fine on this account, this option can be ruled out.
-SPN’s not in place
Also I would suggest to have different service accounts for Dev and Prod instances. In case you want to roll out SSO, it might be helpful while creating SPN’s and keytabs…!!!
Yes - the account is a member of the local Admin group.
Well its the credentials for the SIA to use in the CCM, and its a domain account. I’ve been trying to follow the rough guidelines we have from our documentation of installing the R2 servers in the past, however it would make sense that Imight have to sort out the AD authentication first to use this domain system account.
[quote:34ce1ad42b=“smruti.panda”]can be many possible reasons for this - the one’s that I have run into are listed below -
-Server not being recognized in the domain.
-Service account (the network account that you are talking about) is not an local administrator
-might also depend on how the service account is created - sometimes interactive logon is denied based on group policies, but since you confirm that the dev instance is running fine on this account, this option can be ruled out.
-SPN’s not in place
Also I would suggest to have different service accounts for Dev and Prod instances. In case you want to roll out SSO, it might be helpful while creating SPN’s and keytabs…!!!
[/quote]
I’m pretty sure the server is on the domain fine, it seems to be. As above regarding the local admin group. I think interactive logon is disabled on this system account, but yes - it works fine for the Dev box.
EDIT: I’m also unable to configure Windows Active Directory authentication with the system account credentials, but it again works fine with mine.
Further to my last email. I’ve created a new system account to use for the R3 servers, and I’m no longer getting the logon error. However now when I try and start the service, it immediately stops without an error in the CCM.
In the log files, I’m getting the following:
2011-12-06 09:39:44.147 FATAL Thread-0 Failed to initialize Server Manager.
2011-12-06 09:39:44.147 FATAL Thread-0 Failed to initialize InfoStore Agent.
2011-12-06 09:39:44.147 FATAL Thread-0 Unable to start the Server Intelligence Agent.
EDIT: I’m also getting this in the windows event viewer:
Event Type: Error
Event Source: Server Intelligence Agent
Event Category: (50001)
Event ID: 4096
Date: 06/12/2011
Time: 13:03:20
User: N/A
Computer: [HOSTNAME]
Description:
[Node Name: [HOSTNAME]]
[User Name: SystemAccountName]
Server Intelligence Agent has failed to initialize because the bootstrap file D:\Program Files\Business Objects\BusinessObjects Enterprise 12.0\win32_x86_boe_[HOSTNAME].bootstrap can not be accessed. Please make sure no other program is using this file or restore it from your backup if it is missing.
The file is there though. Does this help shed any light on the problem?
(BOB member since 2011-06-08)
(BOB member since 2002-08-29)
(BOB member since 2011-11-11)
(BOB member since 2011-06-08)