Symptom
An existing CI and DB reside on Unix/AIX with hostname example: (A)
You install a new dialog instance with a different hostname, example (B), on windows via Sapinst.
The sapinst_dev.log contains errors like
ERROR:
The step start with step key |NW_DI|ind|ind|ind|ind|0|0|NW_DI_Instance|ind|ind|ind|ind|di|0|start was executed with status ERROR (Last error reported by the step: Instance <name> reached state SHUTDOWN after having state STARTING. Giving up).
R3trans is not able to connect to the database for the windows instance and issues the following error in the trans.log.
ERROR => unable to load DB2 library '\\hostname\sapmnt\<SID>\SYS\global\db6\WINDOWS_AMD64\db6_clidriver\bin\db2app64.dll'. Reason: The application has failed to start because its side-by-side configuration is incorrect. Please see the application event log or use the command-line sxstrace.exe tool for more detail.
Read more...
Environment
BC-CST-STS
BC-INS
BC-DB-DB6
Product
Keywords
client, new, sapinst_dev.log, sapcpe, trans.log, startsap , KBA , BC-DB-DB6-INS , Installation SAP System , Problem
About this page
This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).Search for additional results
Visit SAP Support Portal's SAP Notes and KBA Search.