Quantcast
Channel: SCN : Discussion List - BI Platform
Viewing all articles
Browse latest Browse all 5403

BIP 4.1 SP4 Uninstall Causes Fail After Reinstall

$
0
0

I have installed Business Objects (BIP?  BOE? BOBJ?) 4.1 SP4 on Windows 2012 for a three system landscape.  One of them accidentally ended up on the wrong drive.

 

I checked the admin guide and the installation guide.  I did not find anything about uninstalling it, so I uninstalled using the Windows control panel Programs and Features option.

It removed the services but left the directory in C:\Program Files(x86), so I deleted it, restarted the server and reinstalled on the correct drive.

 

The new installation does not start.  In the new installation's logging directory I see an SIA trace:

 

None,2014 10 31 17:05:32:734,"[Node Name: APBOQ][User Name: AP-BOQ$]Server APBOQRequest PortPublished Addresses: AP-BOQ.xxx.com:6410.

Listening on port(s): 10.204.1.82:6410, [0:0:0:0:0:0:0:1]:6410."

Error,2014 10 31 17:05:34:031,"Failed to create directory C:\Program Files (x86)\SAP BusinessObjects\SAP BusinessObjects Enterprise XI 4.0\conf\APBOQ, NCS instrumentation could be off."

None,2014 10 31 17:05:34:252,"[Node Name: APBOQ][User Name: AP-BOQ$]Server Intelligence Agent is running."

None,2014 10 31 17:05:36:363,"[Node Name: APBOQ][User Name: AP-BOQ$]Server Intelligence Agent: CMS APBOQ.CentralManagementServer is being auto-booted."

Error,2014 10 31 17:05:36:427,"[Node Name: APBOQ][User Name: AP-BOQ$]Server Intelligence Agent: server APBOQ.CentralManagementServer failed to launch. It is possible the working directory or file path is invalid. CreateProcess error=267, The directory name is invalid"

Error,2014 10 31 17:05:36:428,Invalid path: C:/Program Files (x86)/SAP BusinessObjects/SAP BusinessObjects Enterprise XI 4.0/win64_x64//cms.exe with working dir C:/Program Files (x86)/SAP BusinessObjects/SAP BusinessObjects Enterprise XI 4.0/win64_x64/.

None,2014 10 31 17:06:37:826,"[Node Name: APBOQ][User Name: AP-BOQ$]Server Intelligence Agent is stopping."

 

The SIA is trying to find cmd.exe in the original installation. There is clearly some part of the original installation that has not been removed, and SIA is finding it and using it to find files.

 

Do you, by any chance, know where what I need to do to fix this?

Thank you for your help.

Russ


Viewing all articles
Browse latest Browse all 5403

Trending Articles