Unable to install BAM on Windows 2003 Server that also has Terminal Services installed
(Doc ID 566214.1)
Last updated on MARCH 08, 2017
Applies to:Oracle Application Server Integration BAM - Version: 10.1.3.3.0 to 10.1.3.4.0
Microsoft Windows Server 2003
Microsoft Windows Server 2003 R2 (32-bit)
You are unable to install Business Activity Monitoring (BAM) onto a Windows 2003 Server that has Terminal Services installed.
The installer will return numerous errors similar (but not restricted to) these:
- Unable to find D:\djdsuo\OracleBAM\BAM\ServerScripts\cs\GlobalAssemblyInfo.cs
Unable to create virtual directory.
- Error with command: D:\djdsuo\OracleBAM\BAM\gacutil.exe
Parameters: -if D:\djdsuo\OracleBAM\BAM\Oracle.BAM.ADC.Api.dll
- Error with command:
Parameters: -if D:\djdsuo\OracleBAM\BAM\Oracle.BAM.Middleware.dll
Error code: 2
- Error calling cluster.exe. Error code: 1753
Param: restype "Oracle BAM Activi Data Cache" /create
- If you have an existing ADC, it must be upgraded manually after the install
If this is a new install, you must manually create a new ADC after the install.
'adcVersionChecker.exe' is not recognized as an internal or external command, operable program or batch file.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document
|This document is being delivered to you via Oracle Support's Rapid Visibility (RaV) process, and therefore has not been subject to an independent technical review.|