Loading

×Sorry to interrupt
Uncaught ReferenceError: addCTracking is not defined
throws at https://kb.vmware.com/resource/KM_TealiumTrackingJS?v=0.5:100:1

Refresh

Cookie Preference Center

General Information on cookies

When you visit our website, we use cookies to ensure that we give you the best experience. This information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies by clicking on the different category headings to find out more and change your settings. However, blocking some types of cookies may impact your experience on the site and the services we are able to offer. Further information can be found in our

Cookie Policy.

Strictly Necessary

Strictly Necessary

Always Active

Strictly Necessary

Strictly necessary cookies are always enabled since they are essential for our website to function. They enable core functionality such as security, network management, and website accessibility. You can set your browser to block or alert you about these cookies, but this may affect how the website functions. For more information please visit www.aboutcookies.org or www.allaboutcookies.org.

Cookie Details‎

Performance

Performance

Performance

Performance cookies are used to analyze the user experience to improve our website by collecting and reporting information on how you use it. They allow us to know which pages are the most and least popular, see how visitors move around the site, optimize our website and make it easier to navigate.

Cookie Details‎

Please confirm your settings by refreshing the page.

Functional

Functional

Functional

Functional cookies help us keep track of your past browsing choices so we can improve usability and customize your experience. These cookies enable the website to remember your preferred settings, language preferences, location and other customizable elements such as font or text size. If you do not allow these cookies, then some or all of these services may not function properly.

Cookie Details‎

Advertising

Advertising

Advertising

Advertising cookies are used to send you relevant advertising and promotional information. They may be set through our site by third parties to build a profile of your interests and show you relevant advertisements on other sites. These cookies do not directly store personal information, but their function is based on uniquely identifying your browser and internet device.

Cookie Details‎

Advertising Cookies

Consent Leg.Interest

Select All Vendors

Select All Vendors

Select All Hosts

Select All

Clear Filters

Information storage and access

Apply

Confirm My Choices Reject All Allow All

My Subscriptions

Loading

Knowledge Base

Smarts installation fails without an error message (351269)

Last Updated: 3/22/2024Categories: TroubleshootingTotal Views: 3243Language:
English

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Symptoms

Smarts installation fails without an error message

Smarts suite does not install

Resolution

There are may be multiple reasons why a Smarts installation may fail without an error message being generated. To troubleshoot this issue, complete the following steps. If you cannot find the problem and solution on your own, contact EMC Support for further troubleshooting and quote this solution ID. Collect and provide the data collected at each step to EMC Support as noted.

Get all the available options and application arguments for a Smarts installer file by running the help command as in the following example:

./setup-ACM-2_2_0_0-solaris.bin -is:help

The help command should output the following options and application arguments which are available for the Smarts installer program:

-is:log <filename>    The is:log option with the <filename> argument will log debug messages to <filename> argument you provide.
-is:javahome <dir>  The <dir> argument is the JRE home directory that points to the directory containing bin/java.
-is:tempdir <dir>      The <dir> argument is the temporary directory to be used by the launcher.
-cp:a <classpath>    The -cp:a option with the <classpath> argument appends the <classpath> to the launcher's classpath.
-cp:p <classpath>    The -cp:p option with the <classpath> argument prepends the <classpath> to the launcher's classpath.
-is:extract                   Extracts the contents of the archive.
-is:nospacecheck      Turns off the launcher disk space checking.
-is:version                   Returns launcher version and exits.
-is:help                         Prints this help message and exits

Use the available options and application arguments to investigate the problem with the Smarts installation. The usage for the commands in the preceding step is as follows:

setup-ACM-2_2_0_0-solaris.bin [OPTIONS] [APPLICATION_ARGUMENTS]

The following example would output log debug messages to the file name you provide as the <filename> argument:

setup-ACM-2_2_0_0-solaris.bin  -is:log <filename>

If you cannot determine the problem using the preceding command options and arguments, run the following trace-log command (this will output a large amount of data).

$bash -x   setup-SAM-7_1_0_0-sol.bin 2> trace-log

Run the md5sum command on the installation pkg as in the following example:

fusion:suite$ md5sum setup-ACM-2_2_0_0-solaris.bin
12eea3aa45b6789c123fe4bac56f7cf0  setup-ACM-2_2_0_0-solaris.bin

Contact EMC Support for further troubleshooting. Provide the log generated by the trace-log command and the md5sum command output.

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

Additional Resources

No results for undefined

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

Related Versions:

VMware Smart Assurance - SMARTS

Take Our Survey

Support Assistant