- SAP Community
- Products and Technology
- Technology
- Technology Q&A
- Wily Introscope: Fatal Error
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for
Options
- Subscribe to RSS Feed
- Mark Question as New
- Mark Question as Read
- Bookmark
- Subscribe
- Printer Friendly Page
- Report Inappropriate Content
Wily Introscope: Fatal Error
Former Member
Options
- Subscribe to RSS Feed
- Mark Question as New
- Mark Question as Read
- Bookmark
- Subscribe
- Printer Friendly Page
- Report Inappropriate Content
on 07-08-2010 2:10 PM
Hi,
i've tried to install Wily Introscope Manager 8.1 on our Solution Manager 7.0. Our Solution Manager is running on AIX 6.1 and the Java Version is 1.4.2. When I start the installation with the command ./introscope8.1.0.0aix64SAP.bin I get the following message:
Installing ...
Silent installer completed with status of: FATAL_ERROR. For more details, consult install logs at: /usr/sap/ccms/wilyintroscope/install. Please wait for the command prompt to return...
Installation Complete.The directory /usr/sap/ccms/wilyintroscope ist empty, so I can't search problems in the log file.
I've accepted the eula.txt and I also think installation.properties will be okay.
Can you help me?
Best regards.
Andreas
- SAP Managed Tags:
- SAP Solution Manager
Accepted Solutions (0)
Answers (8)
Answers (8)
Former Member
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
07-20-2010
8:55 AM
Hi,
the installation was successful!!
The problem was, that the directory /usr/sap/ccms/wilyintroscope was created by root. So, it wasn't possible to install it with adm
Thanks a lot!
Best regards,
Peter Müller
Edited by: Peter Müller on May 30, 2011 2:19 PM
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Former Member
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
07-08-2010
3:15 PM
####################################
# WebView Install Settings
#
# ============================
# Specify the port on which WebView will listen for HTTP connections.
# Also specify the hostname and port of the Introscope Enterprise Manager
# to which WebView will connect.
wvPort=8080
wvEmHost=localhost
wvEmPort=6001
#####################################################
# WebView As Windows Service Settings
#-----------------------------------------------
# Specify whether to configure WebView as a Windows
# Service. This option is only available for Windows.
shouldConfigWvAsService=false
# Enter a unique service name for the Service if one is desired.
# The service name is for use by the Windows registry.
# The service name must be 8 characters or less, with no spaces.
wvAsServiceName=IScopeWV
# Enter a unique display name for the Service if one is desired.
# The display name is for use in Windows control panels, and with
# the NET START command. It may contain spaces.
wvAsServiceDisplayName=Introscope WebView
#########################################
# WebView Advanced JVM Settings
#----------------------------------
#
# These options should only be configured by advanced users.
# If you are unsure of which values to enter, keep the defaults by
# leaving these properties commented out.
# Specify the path to the JVM that will be used to run WebView.
# The path may be absolute, or relative to the Introscope home.
# On Windows, backslashes must be escaped.
# Example [Windows]: jre\\bin\\java.exe
# Example [Unix]: jre/bin/java
#wvLaxNlCurrentVm=
# Specify any desired command line arguments to be used by the
# WebView JVM. The recommended setting for the headless switch is:
# - false for Windows, AIX, HP-UX, Linux, and Solaris platforms
# - true for other UNIX and mainframe platforms
#wvLaxNlJavaOptionAdditional=-Xms128m -Xmx512m -Djava.awt.headless=false
####################################
# ProbeBuilder Install Settings
#
# =============================
#########################################
# ProbeBuilder Advanced JVM Settings
#-----------------------------------
#
# These options should only be configured by advanced users.
# If you are unsure of which values to enter, keep the defaults by
# leaving these properties commented out.
# Specify the path to the JVM that will be used to run the Workstation.
# The path may be absolute, or relative to the Introscope home.
# On Windows, backslashes must be escaped.
# Example [Windows]: jre\\bin\\java.exe
# Example [Unix]: jre/bin/java
#pbLaxNlCurrentVm=
# Specify any desired command line arguments to be used by the
# Enterprise Manager JVM.
#pbLaxNlJavaOptionAdditional=-Xms32m -Xmx64m
###############################
# InstallAnywhere Settings
#
# ========================
# Installer UI mode. Do not edit.
INSTALLER_UI=silentYou must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Former Member
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
07-08-2010
3:14 PM
# If the above chosen features list includes Enterprise Manager or WebView,
# specify the location of the external component library's End User
# License Agreement (EULA). This agreement must be acknowledged and accepted
# by the end user in order for installation to proceed. To acknowledge
# and accept the agreement:
# - open it in a text editor and read the terms and conditions
# - edit the end of the file to indicate acceptance of the license
# - save the changes
# - specify the agreement's location using the property below
# The EULA location may be specified with an absolute or relative path.
# Relative paths will be resolved relative to the installer launch directory.
# On Windows, backslashes must be escaped.
# Example Windows value: C:\\Documents and Settings\\eula.txt
# Example Unix value: /home/myuser/eula.txt
eulaFile=/tmp/introscope/eula.txt
##########################################
# Enterprise Manager Install Settings
#
# ================
# Port used by Enterprise Manager to listen for incoming connections.
emPort=6001
# Port used by Enterprise Manager to serve web applications.
emWebPort=8081
#####################################################
#####################################################
# Enterprise Manager Transaction Storage Settings
#------------------------------------------------
#
# The Enterprise Manager automatically stores Transaction Traces to disk.
# Specify a fixed length of time (in days) to store trace data.
# To conserve disk space, choose a lower value.
# To store more trace data, choose a higher value.
emTxTraceDataShelfLife=14
# Specify a directory for storing trace data.
#
# Be sure to choose a directory with sufficient storage space.
# CA recommends a minimum of 2 GB for test systems and 20 GB for production.
# The directory path may be absolute, or relative to the Introscope home.
# On Windows, backslashes must be escaped.
# Example [Windows]: traces\\mytraces
# Example [Unix]: traces/mytraces
emTxTraceDir=traces
# If disk space is a concern, you can optionally specify a disk space cap
# for trace data.
emTxTraceDiskSpaceCap=
#####################################################
# Enterprise Manager Data Storage Settings
#-----------------------------------------
#
# SmartStor(TM) is a feature that records all Introscope data to disk,
# where it can be quickly viewed and analyzed without the need for a database.
# SmartStor is always enabled.
# Specify the storage directory for SmartStor.
# Be sure to choose a directory that contains sufficient disk space for your
# data. A typical minimum is 35 GB. See the Sizing Guide for more information
# on estimating disk space requirements for your specific environment.
# The directory path may be absolute, or relative to the Introscope home.
# On Windows, backslashes must be escaped.
# Example [Windows]: data\\mystorage
# Example [Unix]: data/mystorage
emDataStoreDir=data
#####################################################
# Enterprise Manager Advanced JVM Settings
#-----------------------------------------
#
# These options should only be configured by advanced users.
# If you are unsure of which values to enter, keep the defaults by
# leaving these properties commented out.
# Specify the path to the JVM that will be used to run the Enterprise
# Manager. The path may be absolute, or relative to the Introscope home.
# On Windows, backslashes must be escaped.
# Example [Windows]: jre\\bin\\java.exe
# Example [Unix]: jre/bin/java
#emLaxNlCurrentVm=
# Specify any desired command line arguments to be used by the
# Enterprise Manager JVM. The recommended setting for the headless
# switch is:
# - false for Windows, AIX, HP-UX, Linux, and Solaris platforms
# - true for other UNIX and mainframe platforms
#emLaxNlJavaOptionAdditional=-Xms512m -Xmx512m -Djava.awt.headless=false
#####################################################
# Enterprise Manager As Windows Service Settings
#-----------------------------------------------
# Specify whether to configure the Enterprise Manager as a Windows
# Service. This option is only available for Windows.
shouldConfigEmAsService=false
# Enter a unique service name for the Service if one is desired.
# The service name is for use by the Windows registry.
# The service name must be 8 characters or less, with no spaces.
emAsServiceName=IScopeEM
# Enter a unique display name for the Service if one is desired.
# The display name is for use in Windows control panels, and with
# the NET START command. It may contain spaces.
emAsServiceDisplayName=Introscope Enterprise ManagerYou must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Former Member
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
07-08-2010
3:12 PM
# If the above chosen features list includes Enterprise Manager or WebView,
# specify the location of the external component library's End User
# License Agreement (EULA). This agreement must be acknowledged and accepted
# by the end user in order for installation to proceed. To acknowledge
# and accept the agreement:
# - open it in a text editor and read the terms and conditions
# - edit the end of the file to indicate acceptance of the license
# - save the changes
# - specify the agreement's location using the property below
# The EULA location may be specified with an absolute or relative path.
# Relative paths will be resolved relative to the installer launch directory.
# On Windows, backslashes must be escaped.
# Example Windows value: C:\\Documents and Settings\\eula.txt
# Example Unix value: /home/myuser/eula.txt
eulaFile=/tmp/introscope/eula.txt
##########################################
# Enterprise Manager Install Settings
#
# ================
# Port used by Enterprise Manager to listen for incoming connections.
emPort=6001
# Port used by Enterprise Manager to serve web applications.
emWebPort=8081
#####################################################
#####################################################
# Enterprise Manager Transaction Storage Settings
#------------------------------------------------
#
# The Enterprise Manager automatically stores Transaction Traces to disk.
# Specify a fixed length of time (in days) to store trace data.
# To conserve disk space, choose a lower value.
# To store more trace data, choose a higher value.
emTxTraceDataShelfLife=14
# Specify a directory for storing trace data.
#
# Be sure to choose a directory with sufficient storage space.
# CA recommends a minimum of 2 GB for test systems and 20 GB for production.
# The directory path may be absolute, or relative to the Introscope home.
# On Windows, backslashes must be escaped.
# Example [Windows]: traces\\mytraces
# Example [Unix]: traces/mytraces
emTxTraceDir=traces
# If disk space is a concern, you can optionally specify a disk space cap
# for trace data.
emTxTraceDiskSpaceCap=
#####################################################
# Enterprise Manager Data Storage Settings
#-----------------------------------------
#
# SmartStor(TM) is a feature that records all Introscope data to disk,
# where it can be quickly viewed and analyzed without the need for a database.
# SmartStor is always enabled.
# Specify the storage directory for SmartStor.
# Be sure to choose a directory that contains sufficient disk space for your
# data. A typical minimum is 35 GB. See the Sizing Guide for more information
# on estimating disk space requirements for your specific environment.
# The directory path may be absolute, or relative to the Introscope home.
# On Windows, backslashes must be escaped.
# Example [Windows]: data\\mystorage
# Example [Unix]: data/mystorage
emDataStoreDir=dataYou must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Former Member
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
07-08-2010
2:54 PM
########################################################################
#
# Introscope Silent Installation Response File For SAP End User CD
#
# Sample Response File
# CA Wily Introscope(R) Version 8.1 Release 8.1.0.0
# Copyright (c) 2008 CA. All Rights Reserved.
# Introscope(R) is a registered trademark of CA.
#
#######################################################################
########################################################################
# How to install silently and use this file:
#
# Introscope can be installed in silent mode (i.e. requiring no
# interaction with a GUI or console). A silent install can use the
# settings specified in a response file.
#
# Silent installation can be performed as follows:
#
# Name this file: installer.properties
# Place it in the same directory as the installer executable.
# Invoke the installer from the desktop by double clicking on it,
# or from a command prompt by typing the appropriate command:
#
# .\installer.exe (on Windows)
# ./installer.bin (on Unix)
# java -classpath installer.jar install
#
#
#######################################################################
#######################
# General Settings
#
# ================
# Directory where Introscope is to be installed.
# On all platforms, the path must end with a file separator.
# On Windows, backslashes must be escaped.
# Example Windows install directory: C:\\IntroscopeSilentInstall\\
# Example Unix install directory: /IntroscopeSilentInstall/
# Left blank, this property will default to:
# C:\\usr\\sap\\ccms\\wilyintroscope\\ (on Windows)
# /usr/sap/ccms/wilyintroscope/ (on Unix)
USER_INSTALL_DIR=
# Introscope features to install. Must be a comma-delimited list.
# Example: Enterprise Manager,WebView,ProbeBuilder
silentInstallChosenFeatures=Enterprise Manager,ProbeBuilder,WebView
# If the above chosen features list includes Enterprise Manager or WebView,
# specify the location of the external component library package (zip or tar).
# The external component library package can be downloaded from:
# http://opensrcd.ca.com/ips/osgi
# The package is required in order for these features to run.
# If no package is specified, installation cannot be performed.
# The package location may be specified with an absolute or relative path.
# Relative paths will be resolved relative to the installer launch directory.
# On Windows, backslashes must be escaped.
# Example Windows value: C:\\osgiPackages.v1.windows.zip
# Example Unix value: /osgiPackages.v1.unix.tar
externalComponentPackage=/tmp/introscope/osgiPackages.v1.unix.tar
Edited by: Andreas on Jul 8, 2010 4:09 PM
Edited by: Rob Burbank on May 30, 2011 11:25 AM
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
jiamin_pan
Participant
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
07-08-2010
3:48 PM
In ur Installer file, plz maintain the pathes for Eula, externalcomponentPackage and the USER_INSTALL_DIR
#######################
General Settings
'USER_INSTALL_DIR=' plz maintain this line !
Example Unix value: /osgiPackages.v1.unix.tar
externalComponentPackage=/tmp/introscope/osgiPackages.v1.unix.tar indicate the right path too !
jiamin_pan
Participant
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
07-08-2010
2:42 PM
would u plz also upload the Installer file which indicates the installation path and the source files ?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Former Member
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
07-08-2010
2:36 PM
eula.txt:
##############################################################################
#
# End User License Agreement File
#
##############################################################################
# JHotDraw 5.3; JasperReports 1.3.3; JFreeCharts 1.0.8
# The above-referenced libraries (collectively, the "LGPL Software") are open
# source software libraries that are used with the CA Wily Introscope(R) Version 8.0
# software ("Introscope"). The LGPL Software is not owned by CA, Inc. ("CA").
# Use, copying, distribution and modification of the LGPL Software is governed
# by the GNU Lesser General Public License ("LGPL") version 2.1. A copy of the
# LGPL license can be found in the osgiPackages zip or tar file in which the
# LGPL Software is distributed. Additionally, a copy of the LGPL license can
# be found at http://opensource.org/licenses/lgpl-2.1.php or write to the
# Free Software Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA
# 02111-1307 USA. CA makes the source code for the LGPL Software, including
# any modifications, available at http://opensrcd.ca.com/ips/osgi, and includes
# a copy of the source code in the same zip or tar file as the executable code.
# Use of the Introscope software is governed solely by the CA end user license
# agreement ("EULA"), not by the LGPL license. You cannot use, copy, modify or
# redistribute any Introscope code except as may be expressly set forth in the
# EULA. The LGPL Software is provided "AS IS" WITHOUT WARRANTY OR CONDITION OF
# ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, WITHOUT LIMITATION, THE
# IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE.
# Further details of the disclaimer of warranty with respect to the LGPL
# Software can be found in the LGPL license itself. To the full extent
# permitted under applicable law, CA disclaims all warranties and liability
# arising from or related to any use of the LGPL Software.
# These terms must be acknowledged and accepted in order for installation to
# proceed. To accept these terms, change the parameter as indicated at the end
# of this file and save your changes.
# LGPL:
# Do you accept or reject the terms of the Lesser GNU Public License?
# The set of valid values for LGPL is: {accept, reject}.
LGPL=acceptI'm sorry, but there is no log. The directory /usr/sap/ccms/wilyintroscope ist empty.
Is it possible, that the installation log ist in another directory?
Best regards.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
jiamin_pan
Participant
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
07-08-2010
2:25 PM
plz upload ur EULA and install log
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Ask a Question
Related Content
- DME format version upgradation from pain.001.002.03 to pain.001.001.09 in Technology Q&A
- Unable to load metadata of fiori apps in WebIDE. in Technology Q&A
- Unable to clone the SAP NEO git service from VSCODE in Technology Q&A
- SAP Business Objects - FRUN System Monitoring - No Matching Introscope for pattern for CMS metrics in Technology Q&A
- Getting ready to start using SAP Focused Run in Technology Blogs by SAP
Top Q&A Solution Author
| User | Count |
|---|---|
| 87 | |
| 10 | |
| 10 | |
| 10 | |
| 7 | |
| 6 | |
| 6 | |
| 5 | |
| 5 | |
| 4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.