SIA not start

Hi Shahid, Everyone,

I believe this issue would have been already fixed. Its been a long time now. However, I happened to face exactly the same issue over this weekend. I would like to share my experience and the steps taken to fix it. Hopefully, it helps someone in the future.

Issue Detail :

We did a repair of the Design Studio 1.6 BIP add-on and redeployed the webapps as required.

When we tried restarting the SIA, it was not coming up. We could see exactly the same error as mentioned by Shahid. The error msg was in the file called "servername_jvm_xxxx.log" under the \logging\ folder.

Analysis & Resolution :

1) No error msgs found in the Event Viewer logs

2) Added tracing for the SIA in CCM (-trace xs), but no logs were getting generated

3) Happened to come across SAP note 1840756, it was similar to our issue.

4) Everytime, we tried starting the SIA, it created 2 files -

a. servername_jvm_xxxx.log (which had the error msg)

b. servername_gc.log (which was empty)

5) We checked the size of the java folders in not-working machine (machine) and another machine where SIA was running (machineB)

6) As we were getting "Exception in thread main", it was quite possible that certain java/jar files were missing as mentioned in the SAP note above.

7) number of objects (files & folders) under java\lib\ folder in machineA & machine B were different

Machine A had less number of objects (probably caused by the repair installation)

8) Renamed the java\lib\ folder in machine A to java\lib_backup

9) copied the java\lib folder from MachineB to machineA

10) SIA started working 😊

Hope this helps someone in the future !

Regards,

Monish

One impotent thing that my client tool also installed in BOBJ server and 3 days before my developer repair client tool from control panel programs after that today I restart server and now SIA not start I read I link

http://www.forumtopics.com/busobj/viewtopic.php?t=200995&sid=1adb7c50de913f2f571d46c2e2b3e8e9

He also face same issue after repair BO server it's SIA started again

my query is what about our development also it loost ?

regards

One impotent thing that my client tool also installed in BOBJ server and 3 days before my developer repair client tool from control panel programs after that today I restart server and now SIA not start I read I link

http://www.forumtopics.com/busobj/viewtopic.php?t=200995&sid=1adb7c50de913f2f571d46c2e2b3e8e9

He also face same issue after repair BO server it's SIA started again

my query is what about our development also it loost ?

regards

One impotent thing that my client tool also installed in BOBJ server and 3 days before my developer repair client tool from control panel programs after that today I restart server and now SIA not start I read I link

http://www.forumtopics.com/busobj/viewtopic.php?t=200995&sid=1adb7c50de913f2f571d46c2e2b3e8e9

He also face same issue after repair BO server it's SIA started again

my query is what about our development also it loost ?

regards

Look in the Windows Event Viewer application logs to see if any errors exist. Another option would be to enable the SIA trace from the CCM. If you double click on the SIA when its stopped, you can add a -trace to the command line to enable the trace. The logs may give you a better idea of why its not starting. One main cause can beIf the port is in use for the SIA, usually 6410. If its in use, then it won't be able to start.

Also, make sure that (because you are talking about a BI4.1 update) you do not have the infamous MS C++ issue as explained for example in @Patrick Perrier 's article here http://scn.sap.com/docs/DOC-49453

Hi

Check Note 1951035, it worked for me, I applied the solution as if my computer were 64 and 32 bits (both) as I had to install JavaAccessBridge Manually.

Regards