SIA dont start after install BI Platform 4.0 SP04

[Former Member]

Hi, Experts!

I install BO server 4.0 SP04. After installation SIA (Server Intelligence Agent) dont start. When i try to start it from Central Configuration Manager, SIA will down immediately, and dont start.

The database is response, and DB is ok.

In BO logs i dont see useful  information...

Windows Server 2008 R2 sp1, Oracle 11.2.0.3, 16 Gb RAM

Please help me with my problem!

[Former Member · Accepted solution]

I solve my problem:

install SAP BI Platform 4.0 SP02 Server. Its OK without any problems. Then I install SP04, then patch 3. Everything is good.

Thanks to all!

[Former Member]

First, check the SIA is running with domain account as ROHIT say then check the domain user permission on sia.exe, SvcMgr.exe.  You can follow the following steps:

1. Go to <Business Objects home dir>\Business Objects Enterprise 12.0\win32_x86
2. Search for sia.exe.
3. Right click on it and go to its properties.
4. Click on Security tab.
5. Under group or user name click on Add.
6. Add the domain user through which we are trying to start SIA.
7. Give this user Full Control.
8. Click Apply and Ok.
9. Repeat the steps 3 to 8 for SvcMgr.exe

I do hope you will got the answer, if not let me know.

[Former Member]

Hi, Muhammad !

Thanks for your reply.

I try to start SIA on Administrator (local user).

Just in case i check sia.exe and SvcMgr.exe files. The security settings is ok.

[Former Member]

what does event viewer logs say ?

Is SIA running with domain account or local account?

[denis_konovalov]

if you enable SIA and CMS trace (admin guide) - what do the logs say ?

If you review install .logs - are there any errors or failures in them ?

[Former Member]

Denis, thanks!

1. Where i can see install log ? I dont find it.

2. When i start SIA new log file are created:

sapjvm opt 61_REL NTAMD64

Compiled: May  3 2012 13:09:51

---

Now: 2012-08-23 12:27:50

PID: 2896

current dir: F:\SAP BusinessObjects\SAP BusinessObjects Enterprise XI 4.0\win64_x64

---

---

Option is not recommended for use in productive environments: -XX:+ExitVMOnOutOfMemoryError

JVMX version - May  3 2012 13:12:37 - 61_REL - optU - windows amd64 - 6 - bas2:171636 (mixed mode)

(CompilerOracle read from file F:\SAP BusinessObjects\SAP BusinessObjects Enterprise XI 4.0\win64_x64\sapjvm\jre\.hotspot_compiler)

-----------------------

3. Also i see trace file, for example:

FILE_TYPE:DAAA96DE-B0FB-4c6e-AF7B-A445F5BF9BE2

ENCODING:UTF-8

RECORD_SEPARATOR:30

COLUMN_SEPARATOR:124

ESC_CHARACTER:27

COLUMNS:Location|Guid|Time|Tzone|Trace|Log|Importance|Severity|Exception|DeviceName|ProcessID|ThreadID|ThreadName|ScopeTag|MajorTick|MinorTick|MajorDepth|MinorDepth|RootName|RootID|CallerName|CallerID|CalleeName|CalleeID|ActionID|DSRRootContextID|DSRTransaction|DSRConnection|DSRCounter|User|ArchitectComponent|DeveloperComponent|Administrator|Unit|CSNComponent|Text

SEVERITY_MAP: |None|S|Information|W|Warning|E|Error|A|Assertion|F|Fatal

HEADER_END

|B51D20299375451A86A97AE0EF6BBF900|2012 08 23 10:27:58.155|-0700|Error| |>>| | |TraceLog| 3316|   1|main            | |0|0|0|0|BIPSDK.SessionMgr:logon|SAP-BO4:3316:1.2:1|-|-|BIPSDK.SessionMgr:logon|SAP-BO4:3316:1.2:1|ChAMKcg_.kB.lxzWjxZQU3o2|||||||||com.crystaldecisions.sdk.occa.security.internal.LogonService||Server SAP-BO4:6400 not found or server may be down (FWM 01003) Connection refused: connect

|B51D20299375451A86A97AE0EF6BBF901|2012 08 23 10:27:58.171|-0700|Error| |>>| | |TraceLog| 3316|   1|main            | |0|0|0|0|BIPSDK.SessionMgr:logon|SAP-BO4:3316:1.2:1|-|-|BIPSDK.SessionMgr:logon|SAP-BO4:3316:1.2:1|ChAMKcg_.kB.lxzWjxZQU3o2|||||||||com.crystaldecisions.sdk.occa.security.internal.LogonService||Server SAP-BO4:6400 not found or server may be down (FWM 01003) Connection refused: connect

|B51D20299375451A86A97AE0EF6BBF902|2012 08 23 10:27:58.171|-0700|Error| |>>| | |TraceLog| 3316|   1|main            | |0|0|0|0|BIPSDK.SessionMgr:logon|SAP-BO4:3316:1.2:1|-|-|BIPSDK.SessionMgr:logon|SAP-BO4:3316:1.2:1|ChAMKcg_.kB.lxzWjxZQU3o2|||||||||com.crystaldecisions.sdk.occa.security.internal.LogonService||Is the CMS alive? Ensure the CMS supports SDK version 1400

|B51D20299375451A86A97AE0EF6BBF903|2012 08 23 10:27:58.171|-0700|Error| |>>| | |TraceLog| 3316|   1|main            | |0|0|0|0|BIPSDK.SessionMgr:logon|SAP-BO4:3316:1.2:1|-|-|BIPSDK.SessionMgr:logon|SAP-BO4:3316:1.2:1|ChAMKcg_.kB.lxzWjxZQU3o2|||||||||com.crystaldecisions.sdk.occa.security.internal.LogonService||Is the CMS alive? Ensure the CMS supports SDK version 1400

[denis_konovalov]

Install logs will be in InstallData\logs directory.

The defgault logs in \logging directory might not have enough info, you need to enable trace (Admin guide for how to).

[Former Member]

Denis, thanks!

I add the follow line in BO_trace.ini file :

active=true;

severity='E';

importance='xl';

size=1000000;

keep_num=437;

also i change 'active' status from true to false (active=false; )

But logs files in \logging folder dont change. I past log file in previos post.

[denis_konovalov]

active=false; means no trace.

Importance is better to have at xs

[Former Member]

Now:

active=true;

severity='E';

importance='xs';

size=1000000;

keep_num=437;

logs files dont change.

Setup log setupengine.log about 15 Mb... What are need to look at this file?

[denis_konovalov]

any errors, fails, exceptions, cannot's etc..