BookmarkSubscribeRSS Feed
🔒 This topic is solved and locked. Need further help from the community? Please sign in and ask a new question.
jbru
Calcite | Level 5

Dear Experts!

 

The "Install Post Processing" step of the SAS 9.4 installation process on Microsoft Windows Server 2012 R2 Standard x64 repeatedly fails for a planned Server and Middle Tier deployment.

 

Please see the following logs:

 

DeploymentSummary_datetime.html

Erfolgreich abgeschlossen - SAS Install Qualification Tool (W83001 Aktualisierung)
Vorgang abgeschlossen. Fehler aufgetreten - Verarbeitungschritte nach der Installation

 

deploywiz_datetime.log

INFO: CreateRegKey::RegOpenKeyExWg SOFTWARE\SAS Institute Inc.\Common Data\Shared Files\Secureclient\Consumers returns 2
INFO: CreateRegKey::Re: java.util.MissingResourceException: Can't find bundle for base name com.sas.tools.deployjni.shortcut.PropertyBundle, locale en_US
Can't find bundle for base name com.sas.tools.deployjni.shortcut.PropertyBundle, locale en_US

 

SDW_datetime.log

INFORMATION: Registering extension .sge default open(double click) action for grsgeditor
Sep 15, 2016 7:15:16 PM com.sas.ssn.InstallToolConnector postProcess
INFORMATION: Return Code: -1
Sep 15, 2016 7:19:03 PM com.sas.ssn.Chaining installNext
SCHWERWIEGEND: Install failure for: Verarbeitungschritte nach der Installation
Sep 15, 2016 7:19:03 PM com.sas.ssn.Chaining createDeploymentRegistryViewLink
INFORMATION: Creating deployoment registry view report with the command: [C:\Users\sas\AppData\Local\Temp\_setup1441\products\privatejre__99478__wx6__xx__sp0__1\bin\java.exe, -jar, C:\SASHome\deploymntreg\sas.tools.viewregistry.jar]
Sep 15, 2016 7:19:03 PM com.sas.ssn.Chaining createDeploymentRegistryViewLink
INFORMATION: Deployment registry view is written to: C:\SASHome\InstallMisc\InstallLogs

 

IT_datetime_install.log File

2017-06-01 19:15:16 InstallationTask - Invocation of SAS returned 115
2017-06-01 19:15:16 Controller - An error occurred during processing:
2017-06-01 19:15:16 Controller - There is a problem that seems to be an issue with the installer: Could not invoke public static int com.sas.tools.installs.it.tasks.BuildSASDesktopTask.postInstall() on instance null
2017-06-01 19:15:16 Controller - com.sas.tools.installs.it.InstallException: Aufrufen von public static int com.sas.tools.installs.it.tasks.BuildSASDesktopTask.postInstall() auf Instanz null nicht möglich.
at com.sas.tools.installs.it.ProcessingTask.invoke(ProcessingTask.java:111)
at com.sas.tools.installs.it.Controller.postProcess(Controller.java:1482)
at com.sas.ssn.InstallToolConnector.postProcess(InstallToolConnector.java:826)
at com.sas.ssn.Chaining.launchInstall(Chaining.java:1255)
at com.sas.ssn.Chaining.installNext(Chaining.java:580)
at com.sas.ssn.Chaining.run(Chaining.java:309)
Caused by: java.lang.reflect.InvocationTargetException
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at com.sas.tools.installs.it.ProcessingTask.invoke(ProcessingTask.java:104)
... 5 more
Caused by: com.sas.tools.installs.it.InstallException: SAS Foundation error while performing post install task [SAS invocation return code of 115
]
at com.sas.tools.installs.it.tasks.InstallationTask.processSASOutput(InstallationTask.java:836)
at com.sas.tools.installs.it.tasks.BuildSASDesktopTask.winPostInstallExecute(BuildSASDesktopTask.java:188)
at com.sas.tools.installs.it.tasks.BuildSASDesktopTask.postInstall(BuildSASDesktopTask.java:81)
... 10 more

2017-06-01 19:15:16 Controller - Caused by:
2017-06-01 19:15:16 Controller - java.lang.reflect.InvocationTargetException
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at com.sas.tools.installs.it.ProcessingTask.invoke(ProcessingTask.java:104)
at com.sas.tools.installs.it.Controller.postProcess(Controller.java:1482)
at com.sas.ssn.InstallToolConnector.postProcess(InstallToolConnector.java:826)
at com.sas.ssn.Chaining.launchInstall(Chaining.java:1255)
at com.sas.ssn.Chaining.installNext(Chaining.java:580)
at com.sas.ssn.Chaining.run(Chaining.java:309)
Caused by: com.sas.tools.installs.it.InstallException: SAS Foundation error while performing post install task [SAS invocation return code of 115
]
at com.sas.tools.installs.it.tasks.InstallationTask.processSASOutput(InstallationTask.java:836)
at com.sas.tools.installs.it.tasks.BuildSASDesktopTask.winPostInstallExecute(BuildSASDesktopTask.java:188)
at com.sas.tools.installs.it.tasks.BuildSASDesktopTask.postInstall(BuildSASDesktopTask.java:81)
... 10 more

2017-06-01 19:15:16 Controller - Caused by:
2017-06-01 19:15:16 Controller - SAS Foundation error while performing post install task [SAS invocation return code of 115
]
2017-06-01 19:15:16 Controller - com.sas.tools.installs.it.InstallException: SAS Foundation error while performing post install task [SAS invocation return code of 115
]
at com.sas.tools.installs.it.tasks.InstallationTask.processSASOutput(InstallationTask.java:836)
at com.sas.tools.installs.it.tasks.BuildSASDesktopTask.winPostInstallExecute(BuildSASDesktopTask.java:188)
at com.sas.tools.installs.it.tasks.BuildSASDesktopTask.postInstall(BuildSASDesktopTask.java:81)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at com.sas.tools.installs.it.ProcessingTask.invoke(ProcessingTask.java:104)
at com.sas.tools.installs.it.Controller.postProcess(Controller.java:1482)
at com.sas.ssn.InstallToolConnector.postProcess(InstallToolConnector.java:826)
at com.sas.ssn.Chaining.launchInstall(Chaining.java:1255)
at com.sas.ssn.Chaining.installNext(Chaining.java:580)
at com.sas.ssn.Chaining.run(Chaining.java:309)

 

I would appreciate any hints and guidance about what could be wrong. Please tell me if any additional infos are necessary.

 

Thank you,

Jürgen

 

1 ACCEPTED SOLUTION

Accepted Solutions
AndrewHowell
Moderator

@jbru:

  • Something broken: SAS Tech Support
  • "How do I.." discussion: SAS Communities

An installation can't wait for a discussion to take place here. Contact your local Tech Support ASAP (although please post the solution here..)

View solution in original post

4 REPLIES 4
LinusH
Tourmaline | Level 20
Looks like a typical issue for SAS tech support.
Data never sleeps
jbru
Calcite | Level 5

Found some similar forum entries about such errors (although not the same error code) saying it could have something to do with the Java version used, although this version brings its own Private Java version.

 

Would be grateful for any clues. Please tell me if there are certain other logs worth to investigate. 

AndrewHowell
Moderator

@jbru:

  • Something broken: SAS Tech Support
  • "How do I.." discussion: SAS Communities

An installation can't wait for a discussion to take place here. Contact your local Tech Support ASAP (although please post the solution here..)

JuanS_OCS
Amethyst | Level 16

Hello @jbru, Jurgen,

 

 I would really recommend you the advise provided by @LinusH and @AndrewHowell. Perhaps you might find help from here about those, based on our experience, but the real knowledge is at SAS Technical Support. Could you already open a ticket at tech. support? Probably the sooner the best.

 

Leaving this remark aside, the reasons for this error can be multiple. Just from the top of my mind I can think of: 8.3 name convention was not enabled before you started the installation of binaries, or the license (sid file) is not corred/updated, or you have got already a JAVA_HOME variable for your current Java, which might be in conflict with the private Java, or missing permissions in your operating system folders... as said, plural options.

 

One thing you could do, to get more information, is to run the setup.exe with the "-loglevel 2" parameter, to re-run the post-installation steps with debug level on logging. Anyway, SAS Tchnical Support probably would ask you for this extended logs.

 

Hope it helps a bit.

suga badge.PNGThe SAS Users Group for Administrators (SUGA) is open to all SAS administrators and architects who install, update, manage or maintain a SAS deployment. 

Join SUGA 

CLI in SAS Viya

Learn how to install the SAS Viya CLI and a few commands you may find useful in this video by SAS’ Darrell Barton.

Find more tutorials on the SAS Users YouTube channel.

Discussion stats
  • 4 replies
  • 5927 views
  • 6 likes
  • 4 in conversation