cancel
Showing results for 
Search instead for 
Did you mean: 

SIA fails to start after uninstalling SAP Integration Kit

Former Member
0 Kudos

We are trying to upgrade our SAP IK from SP2 to SP3. After uninstalling SAP IK, SIA will not start anymore. Has anyone run into a similar problem? This happened to one of our sandbox environment in the past, and there was no way to start SIA after trying out a few options, so we had to reinstall BOE to get it up again. Can anyone share if they've run into the same thing?

Our Environment:

Windows Server 2003 R2 SP2

BOE XI 3.1 SP3

Accepted Solutions (0)

Answers (2)

Answers (2)

IngoH
Active Contributor
0 Kudos

Hi Brad,

why would you uninstall ? there is a SP3 patch out there as well.

Ingo

Former Member
0 Kudos

Hi Ingo,

We try to setup "BusinessObjects Integration for SAP XI 3.1 ServicePack 3". This setup wanted to unistall sp2 and after unistall we face to same problem with Brad.

There is also an upgrade at the link below for integration kit;

Support packages and patches SAP -> BusinessObjects Integration for SAP XI 3.1 ServicePack 3

installation and upgrade -> BOE XI 3.1 INTG SAP UPDATE WIN

Is this the sp3 upgrade that you have talked about or Is there a different setup?

Edited by: Burcu Kocas on Sep 16, 2010 10:12 AM

Former Member
0 Kudos

Hey Burku,

We were not able to start SIA after uninstalling the SAP IK. There must be something wrong with the uninstaller that broke the BOE install. At the end we had to uninstall and re-install BOE again. Just make sure that you UNCHECK the "initialize database" option during installation so you won't lose your previous BOE settings.

But yes, for those who have not gone ahead and uninstall SAP IK, you should use the upgrade patch instead as suggested by Ingo.

- Brad

Former Member
0 Kudos

Actually - I've fixed this a number of times by (first backup CMS DB & FileStore):

Adding a New SIA in CCM, naming it the same as the host SIA that won't start, using same port, and selecting "Create default servers on new node" and checking "Recreate Server Intelligence Agent...", using same port as existing CMS (eg. 6400), and this should do the trick.

Former Member
0 Kudos

Hi Brad,

We have the same problem, how did you solve?