cancel
Showing results for 
Search instead for 
Did you mean: 

Unable to login into my fresh install of BO 4.1Sp6 edge edition???

Former Member
0 Kudos

I am working on BO 4.1 SP6 .

I am getting the below error:

Account information not recognized: Could not reach CMS . The CMS on machine was stopped due to a critical error. (FWM 20031)


When i check the error log (error_cms) it shows :


I did the following steps

  • Change the account the SIA runs with:
    1. go to CCM
    2. stop SIA
    3. go to Properties of SIA
    4. in 'Logged On As' section uncheck 'System Account' and provide domain account that has access to CMS database
    5. start SIA

       OR

  • Provide the account to log on to the CMS database with:
    1. go to CCM
    2. stop SIA
    3. go to Properties of SIA
    4. go to Configuration tab, click on 'Specify' button, provide CMS database information including login and password of a user that has access to CMS database
    5. start SIA

Again now i am facing problem with this .

can any one suggest me the permanent solution ...... to  this is issue

Accepted Solutions (0)

Answers (3)

Answers (3)

Former Member
0 Kudos

Hi Dinesh,

After the "intializing" state with what state the server status ends with? (like running, stopped, or initializing itself)

If it is stuck with some status and not in running state then do create a new one.

Check the logs and see if there is any information about the failure of this server.

Or as suggested in the previous posts split the Adatpive Processing Server (APS) as mentioned in the SAP note 1694041.

Please share your findings.

Thanks,

Arun


former_member209323
Active Participant
0 Kudos

Hi,

1) Split the Adatpive processing server as mentioned in the note 1694041.

2) If you are not using Auditing, Go to CMC - Auditing - Turn Off Auditing.

Regards,

Shreejith

ShailendarAnugu
Product and Topic Expert
Product and Topic Expert
0 Kudos

Hi Dinesh,

Please see the SCN Thread Account information not recognized:Could not re... | SCN , which addresses the issue.

Thanks,

Shailu.