SAP Language Pack installation file

 SAP Language Pack installation files are normally bundled with SAP main installation file for example with SAP ERP or SAP Netweaver installation. 

All the supported language will be available in the main installation folder. At some point during installation, SAP Customers may just select the required languages to be installed. 

How to download

  1. Launch SAP One Launchpad and sign on with your S-user id.
  2. Go to SAP Download Chicklets
  3. Navigate to Installation and Upgrade Sections
  4. Select My company software or Navigate through alphabetical order
  5. Search for SAP ERP category and navigate for installation files .


Assuming once the installation completes, for some SAP customers there will be required for their to update the language installed with the latest updates, this normally happens which the local government introduce new financial tax regulations. 

For this, repeat the same process on how to download above but this time navigate at point 3 for Support Package and Patches and then follow the step 4 and 5.

In this section you will find supplementary language packages for the related countries.

Updating language packages are done normaly done using T-code SMLT.


How to enable sap archiving objects

Follow these steps to activate the archiving information structure:

  • Select the archiving administration that best suits your needs (transaction SARA)
  • Select the Goto Information System option.
  • Customizing is the option to choose.
  • Enter SAP PRODUCT AIS in the Archive Infostructure field.
  • Then select Archive Infostructure Activate from the drop-down menu.

How do I archive FI documents in SAP

 In SAP, how do I archive financial documents?

Configuration. Enter Object: FI DOCUMNT (For archiving FI Documents) in the SARA tcode. Select the Customize button...

Object: FI DOCUMNT for archiving FI documents (For archive FI Documents) Choose the Write Option. Put a name for the version and click keep it.

Object: FI DOCUMNT is now used to remove the documents. Select Delete.

Major SAP MM and Purchase Order Tables

 I notice whenever when archive are being scoped, important tables needs to be identified and when i was searching the below table it was interesting as i could and had gotten it from Early watch alerts documents and also by some guru's in some forums long time ago and can't really remember now. 

But In SAP, how can I get a list of tables?

Using the t-code SE16, press f4 on the table name, then click on info system and type * in the table name. I don't have access to SAP right now, however I believe the table DD02T has a list of all the tables. Look at the table with SE16.

SAP MM tables

  • MARA – General Data, material type.
  • MAKT– Short Texts, descriptions.
  • MARM– Conversion Factors.
  • MVKE – Sales Org, distribution channel.
  • MLAN – Sales data, tax indicator, tax.
  • MARC – classification.
  • MBEW – Plant Planning Data.
  • MLGN – Valuation Data.

SAP Purchase Order Tables
  • EKKO - Purchasing Document Header.
  • EKPO - Purchasing Document Item.
  • EKBE - History per Purchasing Document.
  • EKKN - Account Assignment in Purchasing Document.

SAP S/4HANA Migration Cockpit

My review of the some of the important note that i took when performing S/4hana migration, below is just brief but there are more to it which you should refer to the SAP guide.

What is SAP's 4HANA migration cockpit, and how does it work?

The SAP S/4HANA migration cockpit makes it easier to move corporate data from one system to another. Migration objects are used by the SAP S/4HANA migration cockpit to identify and transmit important data. A migration object explains how to transfer data from SAP S/4HANA to a specified business object.


The SAP S/4HANA Migration Cockpit aids in the data migration process from SAP/non-SAP systems to SAP S/4HANA using preset migration objects. The source and target structures, as well as relationships and mapping information, are all detailed in the migration object.


SAP Migration Cockpit (SMC) is a new tool from SAP that is integrated into both cloud and on-premises versions of SAP S/4 HANA. It's designed to help with data transformation and loading into SAP S/4 HANA.


The process of shifting data from one system to another is known as data migration. While this may appear to be a simple task, it necessitates a change in storage as well as a database or application. Any data migration will include at least the transform and load steps in the extract/transform/load (ETL) process.


How long does it take to migrate SAP?

depends roughly 10 to 15 months or more depending on type and size

Moving from traditional SAP systems to SAP S/4HANA should take between 10 and 15 months, according to SAP.

SAP Fiori Licensing - Front End Server

 

Often we think about how SAP Fiori are being license throughout the use of various SAP products. Well for instance Solution Manager has fiori access, SAP Marketing has Fiori access, SAP One Launchpad in SAP Public domain as Fiori user interface.

Now coming to straight to the facts:

It took me a while to understand how the license works and for my environment i managed to find it out but for the rest of  component software which uses fiori it might be packaged differently. You may want to check with your SAP contract or account manager. 

SAP Fiori is included as part of SAP Gateway license in general that comes along when  a customer sign up SAP Netweaver products. 

However not only that Fiori access are also bundled in different ways maybe  you need to explore with super admin access in SAP one launch pad on LIC tab to see how SAP fiori intergrated and to which product.


How to check SAP License entitlement

 Quick information on how to check our SAP product in use license entitlement.


Enter the License Utilization Information Application (LUI) either through SAP ONE Support Launchpad or directly to gain an overview of your company's current licence consumption and licence entitlement.

How do I get to LUI?

The LUI application is currently only accessible to Super Admins.

In order for each S User to have access to the LUI application, the firm Super Amdin must assign the following profiles to them in the SAP One Support Launchpad:

Using Access Licenses in the Cloud

Use of on-premises access licences

SAP IS-RETAIL Installation

 Is there really SAP IS-RETAIL Installation software - This is just to give you bit understanding on how it works and where to get the installation files. 

Because IS-Retail is an industry solution built on top of an ERP solution, there is no specialised guide. As a result, you must install SAP ERP using the requested release. Check out the SAP ERP installation guide.


You must enable IS-Retail in the switch framework after installing SAP ERP; see "SAP Note 1075202 - FAQ: Setting the Retail Switch" for more information.

SAP Hybris Marketing 1809 SAP_CUAN 140

SAP Marketing Cloud (formerly Hybris Marketing) is a marketing system that unifies user data into an unified hub to give real-time context-based data on individual customers and anonymous visitors.

Technical requirement

  • SAP Marketing is based on the following components:
  • SAP HANA 2.0, SPS03 or higher
  • Foundation on ABAP Platform 1809, version for SAP HANA, including the following components:
  • ABAP Platform 1809, version for SAP HANA (ABAP FND 1809 ON HANA)
  • SAP Business Suite Foundation (S4FND 103 DEV)
  • SAP MDG Foundation (MDG_FND 803 SP00 or higher)


This will enable brands to provide consistent, contextual, and relevant experiences to customers throughout their journey, regardless of the marketing channel or device they use.


Data Management: gives you a 360-degree perspective of people who connect with your business, allowing you to target them in the proper context and in real time.

Recommendation: provides your clients with timely and highly appropriate recommendations, assisting you in converting interest into conversion.

Segmentation: allows you to customise campaigns across many platforms with high-performing audience segmentation in real-time.


SAP Marketing Cloud (formerly Hybris Marketing) is a marketing system that unifies user data into an unified hub to give real-time context-based data on individual customers and anonymous visitors.


Hybris Marketing is one such product available in the market for marketing capability that is cloud-based and on-premises, and has the capabilities and tools to assist organisations in overcoming the issues described above. We will examine and introduce some of the important Out Of Box functionalities of Hybris cloud marketing solution offers to the business fraternity in the remainder of this article.

SAP Custom Code migration tools (CCMSIDB)

 You can use the Custom Code Migration app to look at custom code that has to be transferred from a SAP Business Suite system to SAP S/4HANA (on premise). This app performs S/4HANA custom code tests to evaluate the development objects to be adopted.


All references to SAP objects in your custom code are detected by the Custom Code Analyzer. These references' metadata is saved in a ZIP file. Continue with Downloading the Analysis Result as a ZIP File once the background job processing is complete.


A customer can examine if his SAP Business Suite custom code fits with the scope and data structure of SAP S/4HANA on-premise edition using the Custom Code Migration Worklist (technically part of SAP NetWeaver 7.5). The diagram that follows

Upgrading windows server 2008 to windows server 2019, two step upgrade required

 For upgrading windows 2008 to windows 2019 - it can be straightly done with an in place upgrade to windows server 2019/

To simplify the steps follows:-

1. Upgrade your current windows server 2008 to either windows servre 2012 or 2016 first

2. Then from either 2012 or 2016 upgrade to 2019.

Simple as that.

In most cases there are scenarios where customers with windows server 2008 or 2008 R2 are reaching the maintenance end date, therefore Microsoft gives flexible choices, 

1. Move your Windows 2008 R2 as it is to Microsoft Azure, in which you will be given time of extended warranty, as this gives you time to plan for you future upgrade to Windows server 2019 upgrade. 

You may need to check the latest white papers from Microsoft portal if these features are still available.

Always consider not fogetting ipconfig and systeminfo file to be backup before starting the upgrade.

As for the procedure for upgrading , i would say it's a preety much wizard driven process that you don't have to crack your head so much.

For the steps and screen shots for upgrading, you can already get via google search, youtube for those independent people posting it or get it directly from Microsoft itself since you already would have a runtime license.

Applying SAP Maintenance Certificate - SAP Note 1898812 How to Renew a maintenance certificate

 

As for SAP maintenance certificate are concern it's very important as if you are planning to update and software within SAP landscape and if your maintenance certificate are not updated, their error would pop up in the abap system hence causing issue.


You can easily request maintenace certificate or license key from SAP one launchpad under 

Application lifecycle management -> SAP Solution Manager -> Processes 7.2 -> Maintenance certiciate. 

The component name of Maintenance certificate in case if you run into issue and you plan to lodge a case with SAP then choose SV-SMG-LIC

Maintenance certificate is just ensuring customers with the right corresponding maintenance agreement are allowed to apply SPAM, SAINT, JSPM and etc..

Remember before you do import or Support packages ensure to apply maintenance certificate others standard error might pop up this is applicable to SPAM/SAINT version 0034.

You might not need to worry if you SAP product is running on SAP Netweaver 7.0 but if its higher then Maintenance certificate is required.

Validity of maintenance certificate is somewhat within 3 months.

As a rule of thumb to checkif you have maintenance certificate just execute t-code SLICENSE and check the New License to see if it displays infor such as Digital -signed License Keys.






Migrating to SAP Hana Database consideration on SAP Netweaver Parameter

Just ome quick tips on parameter to be alert when initiating SAP Netweaver Hana Database Migration  


All Databases: r3load and jload Procedures

While migrating to SAP hana Database consideration requirement for SAP Netweaver Instance parameters

rsdb/prefer_in_itab_opt
rsdb/max_in_blocking_factor
rsdb/min_in_blocking_factor
rsdb/prefer_union_all
rsdb/prefer_join
rsdb/prefer_fix_blocking
rsdb/max_blocking_factor
rsdb/min_blocking_factor
rsdb/max_union_blocking_factor
rsdb/min_union_blocking_factor





SAP Business Objects BI Essential components

 SAP Business Objects BI Essential components

Do you know the most basic essential component of  SAP Business Objects BI is as below. 

  • Reporting.
  • Data Discovery and Visualization.
  • Application and Dashboard Building.
  • Deployment and Administration.
  • You can also call it centralized suite for reporting dashboard and visualization. While being a BI laters in SAP technology front. It's sophistication makes data to be visualized in a more predominant way. 



Of course as I'm writting based on my own experience therefore the below just based on my experience and not from any master guide perhaps it could be a minimum guide from it.

This is just my shortcut of notes performing installation, however you can always google sap public domain sites for more tips and tricks info or guides. 

Installation quite straight forward all you need in a minimum is 
8GB or more RAM
Disk space of 20GB
CPU around 4 Cores
Windows operating system x64
Java 1.6 or more higher version
Microsoft .Net framwrk and Windows installer all 3.5 higher. 








Check your pre-requisite

The press next on welcome screen and accept the license agreement
After which product key required to be entered. 
Choose your language - English

I normally choose full installation type




You can select whether to configure and install Sybase SQL Anywhere 

You also need to choose the CMS database

You must select Tomcat web application in this case normally it would be TOMCAT 7.0

The configure install subversion 

Proceed with SIA - Server intelligence agent

CMS Port info to be entered. 

Password for Administrator

Configure sybase sql anywhere

Configure Tomcat

Configure HTTP listening port

Enter subversion repository port number, user account and password.

configure SMD agent for solution manager connectivity

You may choose introscope enterprise manager

Finally Start the installation - it will take a short while till you reach Finish installation. 

Post steps

Login to CMC to further configure - you may use the configuration wizard.



























How to find out your SAP Enhance package level

 How to find out your SAP Enhance package level

Quick tips

Most of you for sure this would be a perhaps mind blowing tips.


1. How to do you find out your SAP enhance Package level for SAP ECC6

Asnwer : - Login to your SAP -> System Status - > In the list of Support packages Look for module

SAP_APPL - 601  this means 6 is your SAP ECC6 while 01 means Enhance package 1

SAP_APPL - 606 this means 6 is your SAP ECC6 while 01 means Enhance package 6

SAP_APPL - 604 this means 6 is your SAP ECC6 while 01 means Enhance package 4

Hope this helps..



SAP Maintenance Planner, Transaction ID, Push to Download Basket, Download Stack.xml


This maybe the qiuckest, simplified note on how to learn about generating stack.xml and what its about.

In the current SAP technology I'm sure those SAP basis folks would have heard or went through the following ways to get their new system or existing system installed or even would have downloaded simplest pluggin of support pakcages to certain extreme. 

But i know rarely SAP basis folks touched so much on Maintenance optimizer, Maintenance Planner, knowing what is Support Package Stacks and side-effect reports outcomes. 

Well today i would like to share with you simple ways to understand SAP Maintenance Planner


Scenario 1 - If you plan to download a new installation 

In Maintenance Planner choose --> Plan a new system 

Scenario 2- If plan for upgrade example SAP ECC6 EHP5 to SAP ECC6 EHP8

In Maintenance Planner choose -->  Choose Explore system

Scenario 3 - If you plan to download Support Packages only 

In Maintenance Planner choose -->  Choose Explore system


Answer : Goto SAP one lauchpad --> login with S user id, -> in the screen goto Maintenance Planner -> Choose Explore system or Plan a new system tab --> enter relevant details such as sap product, db , os and then next button top left all the way till you get few options 

Push to Download basket , Download Stack.XML

So what happens here is that once you have went through the Plan process, maintenance planner have created a repository requirement of all your components required for installation or upgrade, where you dont have to choose manually during those days before maintenance planner existed.

Then at the screen it gives you option either to download on the spot by choosing download basket  and generate Stack.xml where both are required unless if  want to manually perform installation or upgrade. 

Push to Download basket , Download Stack.XML

Define change -> Select Files --> Download Files -- > Complete


As you can see the Push to download basket option, basically what it does, is that all the selected software component are then linked or pushed to your SAP download manager tagged to your S user id. ( In ur repository server you need to have SAP download manager application downloaded which are available in SAP one launch pad download center. 

At the ame time you need to download stack.xml - this is used for installing any system for example sapinst with xxxxxxxstack.xml file and the rest are taken care by the  installation process.

At the end when you click complete - a PDF file given stating your Stack.xml details of all the software selected, purpose of the software and transaction id. 

All downloaded software , stack.xml and PDF file need to be kept in 1 single location. 

You may have notice Transaction ID. what is this?

Well its basically content of all the stack.xml that you have generated, for example if you have generated 10 stacks.xml either r new system or upgrade, then all these are recorded as transaction in the Transaction tab in Maintenance Planner. Therefore in the future you can always enter the Transaction tab and check your Stack.XML that you have created. 


Well hope this helps and clarifies all relevant information required for you to use Maintenance planner confidently. The understanding is very important.





Niping network diagnosis SAP Note 500235

 Niping network diagnosis SAP Note 500235


Basis consultant often feels stuck in a situation when it come to performance issues where user or factory located far away from the central server of the SAP, for instance:-


SAP ECC EHP7 server located in New Zealand DC ( Server) 

While user is located in New York Office ( User) 

A factory located in France. (Factory) 

Basic consultant often blinded by the fact that to look at connectivity and QOS (SAP Network dedicated throughout the corporate network which sometimes termed as quality of service)


Now when P1 raised by the user saying SAP is slow for them, the first thing support will look at are system performance, dev_traces files for any hints, abap dump if its ever generated by users and etc . BUT never the thought comes most of the times to look at network quality. 

This is the reason why SAP introduced their own version of ping test which is called NIPING. while niping test is often associated when user connects to the central system through SAProuter. 

NIPING is similar to PING and the whole idea is to check if there's any latency in comparison for the particular user connecting to SAP server located remotely.

There are few ways in utilizing NIPING as below

1. Measuring RTT

niping -c -H <nipingsvr> -B 1 -L 100
(The buffersize of 1 may cause an error in other version of niping. If yes please use  niping -c -H <nipingsvr> -B 20 -L 100  )

Some examples in using Niping

2. Long LAN stability test:

niping -c -H <nipingsvr> -B 10000 -D 100 -L 360000

The uses 100000 bytes per second of bandwidth (about 10% of a 10 mbps Ethernet) and will last 10 hours as how the parameter works.

3. Long WAN test (idle timeouts):

niping -c -H <nipingsvr> -P -D 3600000

Every hour, this test starts a TCP connection and delivers a test packet (delay of 3600000ms). It lasts for ten hours. The purpose is to see if a "idle timeout" interrupts the TCP connection. 

4. Short throughput/stability test:

niping -c -H <nipingsvr> -B 1000000 -L 100

Connection is tested with 100 MB of data as quickly as possible. This should take roughly 10 seconds on a 100 Mbps Ethernet connection. 

Maintenance Planner Stack. XML - Please leave comments

Maintenance Planner Stack. XML - Please leave comments


 I notice that many might be a expert in planning your xml stacks while those working in operations or handking SAP day to day operation might not even tasted in creating xml stacks ever in their lifes. 

I hope those you come by this this particular blogs can share in the comments atleast of some topics related to creation of xml stacks, purpose for, why the intention and etc. 

Generally the evolution of Stacks.xml started with making installation and upgrade media available through secure network instead previously it was distributed via disc, CD and other media ( that was the way back then). 

The last time around we used to receive CD's from SAP for the collection of product that we were using.  After which we safeguard those CD's in a tight locker for security and safety purposes. 

As time passes by when internet became more violantly available, SAP came up with loading these installation CD's through website, for me it was interesting, eventough ordering CD was easy by just raising a ticket but getting it online was even better.

Then i knew the comes SAP download Manager where you can park all you downloads and if you get ever intererupted due to network failure, the activity resumes back after and the downloads are intact with the use of SAP download manager.

Its was then SAP start introducing or maybe introduced much earlier, just that i might have realized about Solution manager t-code MOPZ ( Maintenance optimer ) this is used to download your stacks. 

To cut it short now through SAP LaunchPad -> SAP has Maintenance planner . Now this is where it get more simpler for integrator, installers, implementers, compared to previously it requires tremendous effort navigatin through MOPZ. 


For those whom are experts, maybe share our ideas, how you use this day to day basis, thanks.

 

How to solve dump LOAD_VERSION_LOST and dump LOAD_PROGRAM_LOST

 

How to solve dump LOAD_VERSION_LOST and dump LOAD_PROGRAM_LOST


This has been an issues very common in the SAP Circle where the dumps occurs whenever user_exit being changed or a new program being transported to production system.
Normally the solution is the revert to old program and fix the program if there are quick fix. However there are SAP notes clearly defining steps on how to resolve such issues , another method is to clear the dialog buffer or sometimes of there are no programs changed the always SAP system being restarted instead of wasting enormousness time in resolving such issues.

SAP Note : 2385919 - How to solve dump LOAD_VERSION_LOST and dump LOAD_PROGRAM_LOST

However below are some steps of my own, lets see if it works for you.

You must ensure that the programme load is loaded in the programme buffer before you can run an ABAP programme (PXA).
When you run a programme load, this is locked to prevent it from being relocated from the buffer.

The programme locks may not be kept for extended wait durations because the programme buffer is restricted in capacity (for example, user interaction). As a result, during the deployment, all previously configured locks are freed.

The programme load may be moved from the buffer after a short time if the system works actively on the application server.

If you now alter the programme before the application continues (for example, due of a transport), the database identifies that the programme has changed (the total time stamp is newer) when you reload the programme (RELOAD).

The system prompts the brief dump " LOAD PROGRAM LOST" to avoid inconsistencies when executing the programme (the programme may have changed so significantly that follow-on issues occur).
You must not alter the software that has been terminated.

This can also be caused by changing a dependant object.

The report RSDEPEND can be used to determine when the programme was last created and which change caused the total time stamp to be set. This could be the case, for example, if the DDIC types or programme inclusions used have changed.
Search the RSDEPEND result list for objects with the same or similar time stamp as the total time stamp. This method makes it simple to locate the trigger. These dependent objects were then updated using either a transport or a direct system change.

If the short dump occurs frequently, you should take steps to reduce the likelihood of it happening again.
Increase the programme buffer to prevent any further swaps.
Make sure you only import transports when there is no or a minimal load. Especially in a manufacturing environment.

Instaling Hana Studio - All you need to know the steps

 Installing HANA Studio - Fundamental


Hana Studio is one of the easiest tools or interfaces to install let me in your server, desktop, or laptop, today I will share the screenshot that I went through in setting up Hana Studio with ease. 

HANA Studio is an Eclipse-based, integrated development environment (IDE) that is used to develop artifacts in a HANA server. 2. It enables technical users to manage the SAP HANA database, create and manage user authorizations, create new or modify existing models of data, and others. 



choose hdbsetup.exe









error quite common - but don't worry although the log looks scary but trust me to fix this just make sure you downloaded the right Hana Studio downloads software that's all. 

let's continue ( i had error so i downloaded a new set of Hana Studio executables and restarted the setup process and it worked.



Completed - hurray......




Now you can access to you Hana Studio by adding the details of the server as usual. 

Hana studio is the base of whatever Hana system that you are touching. 

Better start using these features rather than just accessing to SAP NW or SAP ECC that runs on HANA and manage them via SAP T-code. 


Below are the installation logs and how it looks like ....

HANA Studio installation Logs – just for reference purposes

22:05:05.636 - INFO:   Installing signal handler

22:05:05.636 - INFO:     Handler for signal INT

22:05:05.636 - INFO:     Handler for signal PIPE

22:05:05.636 - INFO:     Handler for signal ABRT

22:05:05.636 - INFO:     Handler for signal FPE

22:05:05.636 - INFO:     Handler for signal QUIT

22:05:05.636 - INFO:     Handler for signal TERM

22:05:05.636 - INFO:   ---------------------------------------------------------

22:05:05.636 - INFO:   System Information

22:05:05.636 - INFO:   ---------------------------------------------------------

22:05:05.637 - INFO:     Operating System: Windows

22:05:05.637 - INFO:     Architecture    : AMD64

22:05:05.637 - INFO:     Version         : NT 6.3

22:05:05.637 - INFO:     Subversion      :

22:05:05.637 - INFO:     Cpu features    : sse sse2 cmpxchg16b

22:05:05.637 - INFO:     xxcomputernamexx Name       : xxcomputernamexx

22:05:05.637 - INFO:   ---------------------------------------------------------

22:05:05.637 - INFO:   END: System Info

22:05:05.637 - INFO:   ---------------------------------------------------------

22:05:05.637 - INFO:   ---------------------------------------------------------

22:05:05.637 - INFO:   Installer Information

22:05:05.637 - INFO:   ---------------------------------------------------------

22:05:05.638 - INFO:     Installer is part of installation kit

22:05:05.638 - INFO:     Version is 1.2.32 (git hash: 0eafe05e7489)

22:05:05.638 - INFO:     GitHash is 0eafe05e7489

22:05:05.638 - INFO:     Platform is NTamd64

22:05:05.638 - INFO:     Perl version is v5.22.1

22:05:05.638 - INFO:     Running as gui application

22:05:05.638 - INFO:     Using wxWidgets 3.0.2

22:05:05.638 - INFO:     -------------------------------------------------------

22:05:05.638 - INFO:     Program Call Information

22:05:05.638 - INFO:     -------------------------------------------------------

22:05:05.638 - INFO:       Caller program name is hdbsetup

22:05:05.638 - INFO:       Command line arguments:

22:05:05.638 - INFO:       Current directory: D:\IMPORTANT_DOCUMENT\EDU_SOFT_TUTORIAL_CERT\Software\hana studio\HANA Studio 122_11 Windows 64 Bit\SAP_HANA_STUDIO

22:05:05.638 - INFO:       Installer directory: D:\IMPORTANT_DOCUMENT\EDU_SOFT_TUTORIAL_CERT\Software\hana studio\HANA Studio 122_11 Windows 64 Bit\SAP_HANA_STUDIO\instruntime

22:05:05.638 - INFO:       Pid is 8456

22:05:05.638 - INFO:     -------------------------------------------------------

22:05:05.638 - INFO:     END: Program Call Information

22:05:05.638 - INFO:     -------------------------------------------------------

22:05:05.638 - INFO:     -------------------------------------------------------

22:05:05.638 - INFO:     Environment Dump

22:05:05.638 - INFO:     -------------------------------------------------------

22:05:05.638 - INFO:       ALLUSERSPROFILE = C:\ProgramData

22:05:05.638 - INFO:       APPDATA = C:\Users\xxuseridxx\AppData\Roaming

22:05:05.638 - INFO:       COMMONPROGRAMFILES = C:\Program Files\Common Files

22:05:05.638 - INFO:       COMMONPROGRAMFILES(X86) = C:\Program Files (x86)\Common Files

22:05:05.638 - INFO:       COMMONPROGRAMW6432 = C:\Program Files\Common Files

22:05:05.638 - INFO:       COMPUTERNAME = xxcomputernamexx

22:05:05.638 - INFO:       COMSPEC = C:\WINDOWS\system32\cmd.exe

22:05:05.638 - INFO:       DRIVERDATA = C:\Windows\System32\Drivers\DriverData

22:05:05.638 - INFO:       FP_NO_xxcomputernamexx_CHECK = NO

22:05:05.638 - INFO:       HOMEDRIVE = C:

22:05:05.638 - INFO:       HOMEPATH = \Users\xxuseridxx

22:05:05.638 - INFO:       LOCALAPPDATA = C:\Users\xxuseridxx\AppData\Local

22:05:05.638 - INFO:       LOGONSERVER = \\xxcomputernamexx

22:05:05.638 - INFO:       NUMBER_OF_PROCESSORS = 8

22:05:05.638 - INFO:       ONEDRIVE = C:\Users\xxuseridxx\OneDrive

22:05:05.638 - INFO:       OS = Windows_NT

22:05:05.639 - INFO:       PATH = C:\Program Files (x86)\Common Files\Oracle\Java\javapath;C:\ProgramData\Oracle\Java\javapath;C:\Program Files\Common Files\Microsoft Shared\Windows Live;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\WINDOWS\System32\WindowsPowerShell\v1.0\;C:\WINDOWS\System32\OpenSSH\;C:\Program Files\Common Files\Microsoft Shared\Windows Live;C:\Users\xxuseridxx\AppData\Local\Microsoft\WindowsApps

22:05:05.639 - INFO:       PATHEXT = .COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSH;.MSC

22:05:05.639 - INFO:       PROCESSOR_ARCHITECTURE = AMD64

22:05:05.639 - INFO:       PROCESSOR_IDENTIFIER = Intel64 Family 6 Model 42 Stepping 7, GenuineIntel

22:05:05.639 - INFO:       PROCESSOR_LEVEL = 6

22:05:05.639 - INFO:       PROCESSOR_REVISION = 2a07

22:05:05.639 - INFO:       PROGRAMDATA = C:\ProgramData

22:05:05.639 - INFO:       PROGRAMFILES = C:\Program Files

22:05:05.639 - INFO:       PROGRAMFILES(X86) = C:\Program Files (x86)

22:05:05.639 - INFO:       PROGRAMW6432 = C:\Program Files

22:05:05.639 - INFO:       PSMODULEPATH = C:\WINDOWS\system32\WindowsPowerShell\v1.0\Modules\

22:05:05.639 - INFO:       PUBLIC = C:\Users\Public

22:05:05.639 - INFO:       SAP_DIR_PERF = J:\usr\sap\PRFCLOG

22:05:05.639 - INFO:       SYSTEMDRIVE = C:

22:05:05.639 - INFO:       SYSTEMROOT = C:\WINDOWS

22:05:05.639 - INFO:       TEMP = C:\Users\xxuseridxx\AppData\Local\Temp

22:05:05.639 - INFO:       TMP = C:\Users\xxuseridxx\AppData\Local\Temp

22:05:05.639 - INFO:       USERDOMAIN = xxcomputernamexx

22:05:05.639 - INFO:       USERDOMAIN_ROAMINGPROFILE = xxcomputernamexx

22:05:05.639 - INFO:       USERNAME = xxuseridxx

22:05:05.639 - INFO:       USERPROFILE = C:\Users\xxuseridxx

22:05:05.639 - INFO:       VBOX_MSI_INSTALL_PATH = C:\Program Files\Oracle\VirtualBox\

22:05:05.639 - INFO:       WINDIR = C:\WINDOWS

22:05:05.639 - INFO:       WINDOWS_TRACING_FLAGS = 3

22:05:05.639 - INFO:       WINDOWS_TRACING_LOGFILE = C:\BVTBin\Tests\installpackage\csilogfile.log

22:05:05.639 - INFO:       __COMPAT_LAYER = Installer

22:05:05.639 - INFO:     -------------------------------------------------------

22:05:05.639 - INFO:     END: Environment Dump

22:05:05.639 - INFO:     -------------------------------------------------------

22:05:05.639 - INFO:   ---------------------------------------------------------

22:05:05.639 - INFO:   END: Installer Information

22:05:05.639 - INFO:   ---------------------------------------------------------

22:05:05.640 - INFO:   Detecting installation kit

22:05:05.646 - INFO:     Using manifest file 'D:\IMPORTANT_DOCUMENT\EDU_SOFT_TUTORIAL_CERT\Software\hana studio\HANA Studio 122_11 Windows 64 Bit\SAP_HANA_STUDIO\studio\manifest'

22:05:05.657 - INFO:     SAP HANA Studio installation kit detected.

22:05:05.657 - INFO:   ---------------------------------------------------------

22:05:05.657 - INFO:   Looking for installation packages in 'D:\IMPORTANT_DOCUMENT\EDU_SOFT_TUTORIAL_CERT\Software\hana studio\HANA Studio 122_11 Windows 64 Bit\SAP_HANA_STUDIO\studio'

22:05:05.657 - INFO:   ---------------------------------------------------------

22:05:05.658 - INFO:     Checking archive CLIENTINST.TGZ

22:05:05.664 - INFO:       Installler is part of installation kit

22:05:05.910 - INFO:       Name = Client Installer

22:05:05.910 - INFO:       Id = clientInstaller

22:05:05.910 - INFO:       Version = 1.00.120.065.1498514485

22:05:05.910 - INFO:       GitHash =

22:05:05.910 - INFO:       Number of Files = 38

22:05:05.910 - INFO:       Size = 30.574 mb

22:05:05.910 - INFO:       Description = Client Installer

22:05:05.910 - INFO:       Checksum = fb54ecd61741c4a9a3d93d858d7c406d

22:05:05.910 - INFO:     Checking archive DIRECTOR.TGZ

22:05:05.917 - INFO:       Name = Studio Director

22:05:05.917 - INFO:       Id = newdbstudioDirector

22:05:05.917 - INFO:       Version = 2.3.25

22:05:05.917 - INFO:       GitHash =

22:05:05.917 - INFO:       Number of Files = 291

22:05:05.917 - INFO:       Size = 198.041 mb

22:05:05.918 - INFO:       Description = Studio Director

22:05:05.918 - INFO:       Checksum = 9555b2ebdd27c7139266f4e001fe0476

22:05:05.918 - INFO:   ---------------------------------------------------------

22:05:05.918 - INFO:   END: Installation Packages (start: 22:05:05.657 duration: 00:00:00.260)

22:05:05.918 - INFO:   ---------------------------------------------------------

22:05:05.984 - INFO:   Checking configuration of installation (dialog Define Studio Properties)

22:05:30.250 - INFO:     Parameter 'vm' (JavaVm) is not set

22:05:30.250 - INFO:     Parameter 'repository' (SourceRepositoryUrl) is set to value = 'file:D:\IMPORTANT_DOCUMENT\EDU_SOFT_TUTORIAL_CERT\Software\hana studio\HANA Studio 122_11 Windows 64 Bit\SAP_HANA_STUDIO\studio\repository'

22:05:30.250 - INFO:     Parameter 'path' (PATH) is set to value = 'C:\Program Files\sap\hdbstudio12'

22:05:30.250 - INFO:     Parameter 'skip_vcredist' (SkipVCRedist) is set to value = 'No'

22:05:30.250 - INFO:     Parameter 'StartStudioAfterInstallation' is set to value = 'Yes'

22:05:30.250 - INFO:     Parameter 'features' (SelectedFeatures) is set to value = 'admin,appdev,dbdev'

22:05:30.267 - INFO:   ---------------------------------------------------------

22:05:30.267 - INFO:   Checking installation...

22:05:30.267 - INFO:   ---------------------------------------------------------

22:05:30.267 - INFO:     Looking for Microsoft C/C++ runtime redistributable

22:05:30.269 - INFO:       Scanning for installed Visual C++ runtimes

22:05:30.272 - INFO:         Found Microsoft Visual C++ 2008 Redistributable - x64 9.0.30729.4148

22:05:30.273 - INFO:         Found Microsoft Visual C++ 2008 Redistributable - x64 9.0.21022

22:05:30.273 - INFO:         Found Microsoft Visual C++ 2010  x64 Redistributable - 10.0.40219

22:05:30.274 - INFO:         Found Microsoft Visual C++ 2005 Redistributable (x64) - 8.0.61000

22:05:30.274 - INFO:         Found Microsoft Visual C++ 2010  x86 Redistributable - 10.0.40219

22:05:30.275 - INFO:         Found Microsoft Visual C++ 2013 x86 Minimum Runtime - 12.0.21005

22:05:30.275 - INFO:         Found Microsoft Visual C++ 2013 x86 Additional Runtime - 12.0.21005

22:05:30.276 - INFO:         Found Microsoft Visual C++ 2013 x64 Additional Runtime - 12.0.40660

22:05:30.277 - INFO:         Found Microsoft Visual C++ 2008 Redistributable - x64 9.0.30729

22:05:30.278 - INFO:         Found Microsoft Visual C++ 2008 Redistributable - x64 9.0.30729.6161

22:05:30.279 - INFO:         Found Microsoft Visual C++ 2008 Redistributable - x86 9.0.30729.6161

22:05:30.279 - INFO:         Found Microsoft Visual C++ 2008 Redistributable - x86 9.0.21022

22:05:30.280 - INFO:         Found Microsoft Visual C++ 2005 Redistributable (x64) - 8.0.56336

22:05:30.281 - INFO:         Found Microsoft Visual C++ 2005 Redistributable (x64) - 8.0.59192

22:05:30.282 - INFO:         Found Microsoft Visual C++ 2005 Redistributable (x86) - 8.0.56336

22:05:30.282 - INFO:         Found Microsoft Visual C++ 2005 Redistributable (x86) - 8.0.61001

22:05:30.283 - INFO:         Found Microsoft Visual C++ 2013 x64 Minimum Runtime - 12.0.40660

22:05:30.284 - INFO:         Found Microsoft Visual C++ 2008 Redistributable - x86 9.0.30729.4148

22:05:30.285 - INFO:         Found Microsoft Visual C++ 2008 Redistributable - x86 9.0.30729

22:05:31.303 - INFO:       Found Microsoft C/C++ runtime redistributable 'msdev2005SP1_vcredist_x64.exe' (6.00.2900.2180 (xpsp_sp2_rtm.040803-2158))

22:05:31.303 - INFO:       Skipping 'msdev2005SP1_vcredist_x64.exe'

22:05:32.853 - INFO:       Found Microsoft C/C++ runtime redistributable 'msdev2010_vcredist_x64.exe' (10.0.40219.01)

22:05:32.853 - INFO:       Microsoft Visual C++ 2010  x64 Redistributable - 10.0.40219 is out-dated

22:05:32.853 - INFO:       'msdev2010_vcredist_x64.exe' has to be installed

22:05:32.853 - INFO:     Preparing package 'Studio Director'...

22:05:32.853 - INFO:     Checking package 'Studio Director'...

22:05:32.853 - INFO:     Preparing package 'Client Installer'...

22:05:32.853 - INFO:     Checking package 'Client Installer'...

22:05:32.853 - INFO:     Checking required and available disk space per file system...

22:05:32.860 - INFO:     File System Utilization Summary:

22:05:32.861 - INFO:    

22:05:32.861 - INFO:     | Mount Point | Used by

22:05:32.861 - INFO:     | C:\         | program files, Installation Path

22:05:32.861 - INFO:    

22:05:32.861 - INFO:     | Mount Point | Required disk space (KB) | Available disk space (KB) |

22:05:32.861 - INFO:     | C:\         | 613112                   | 37533296                  |

22:05:32.861 - INFO:     ...DONE. Enough disk space available.

22:05:34.404 - INFO:     Checking for installation files locked by running processes...

22:05:34.407 - INFO:     ...DONE. No locked files.

22:05:34.408 - INFO:   ---------------------------------------------------------

22:05:34.408 - INFO:   END: Installation Check (start: 22:05:30.267 duration: 00:00:04.141)

22:05:34.408 - INFO:   ---------------------------------------------------------

22:05:35.883 - INFO:   ---------------------------------------------------------

22:05:35.883 - INFO:   Installing SAP HANA Studio to C:\Program Files\sap\hdbstudio12...

22:05:35.883 - INFO:   ---------------------------------------------------------

22:05:35.892 - INFO:     Opening install registry

22:05:35.892 - INFO:       Create new InstallRegistry file

22:05:35.893 - INFO:       InstallRegistry successfully locked

22:05:35.893 - INFO:       Wrote 89 bytes

22:05:35.901 - INFO:       InstallRegistry: reserved 4096 kb disk space

22:05:35.955 - INFO:     Installing Microsoft C/C++ Runtime...

22:05:35.955 - INFO:       Starting external program D:\IMPORTANT_DOCUMENT\EDU_SOFT_TUTORIAL_CERT\Software\hana studio\HANA Studio 122_11 Windows 64 Bit\SAP_HANA_STUDIO\studio\msdev2010_vcredist_x64.exe

22:05:35.955 - INFO:         Command line is: "D:\IMPORTANT_DOCUMENT\EDU_SOFT_TUTORIAL_CERT\Software\hana studio\HANA Studio 122_11 Windows 64 Bit\SAP_HANA_STUDIO\studio\msdev2010_vcredist_x64.exe" /q

22:05:40.355 - INFO:         Program terminated with exit code 0

22:05:40.365 - INFO:     Installing package 'Studio Director'...

22:05:40.365 - INFO:       Set package invalid

22:05:40.365 - INFO:         Writing registry

22:05:40.367 - INFO:           Wrote 66084 bytes

22:05:40.368 - INFO:       Extracting into directory C:\Program Files\SAP\hdbstudio12

22:05:40.368 - INFO:       Extracting director/artifacts.xml

22:05:40.375 - INFO:         file info: mode = 0444, size = 15223 bytes

22:05:40.376 - INFO:       Extracting director/configuration/config.ini

22:05:40.378 - INFO:         file info: mode = 0444, size = 755 bytes

22:05:40.378 - INFO:       Extracting director/configuration/org.eclipse.equinox.simpleconfigurator/bundles.info

22:05:40.381 - INFO:         file info: mode = 0444, size = 7813 bytes

22:05:40.381 - INFO:       Extracting director/configuration/org.eclipse.update/platform.xml

22:05:40.388 - INFO:         file info: mode = 0444, size = 311 bytes

22:05:40.388 - INFO:       Extracting director/eclipse.exe

22:05:40.417 - INFO:         file info: mode = 0444, size = 312832 bytes

22:05:40.417 - INFO:       Extracting director/eclipse.ini

22:05:40.420 - INFO:         file info: mode = 0444, size = 367 bytes

22:05:40.420 - INFO:       Extracting director/eclipsec.exe

22:05:40.446 - INFO:         file info: mode = 0444, size = 18432 bytes

22:05:40.446 - INFO:       Extracting director/features/com.sap.ide.sapjvm.jre_81.8.8.A/META-INF/MANIFEST.MF

22:05:40.450 - INFO:         file info: mode = 0444, size = 639 bytes

22:05:40.450 - INFO:       Extracting director/features/com.sap.ide.sapjvm.jre_81.8.8.A/META-INF/SAP_SE_G.RSA

22:05:40.456 - INFO:         file info: mode = 0444, size = 8928 bytes

22:05:40.456 - INFO:       Extracting director/features/com.sap.ide.sapjvm.jre_81.8.8.A/META-INF/SAP_SE_G.SF

22:05:40.459 - INFO:         file info: mode = 0444, size = 700 bytes

22:05:40.459 - INFO:       Extracting director/features/com.sap.ide.sapjvm.jre_81.8.8.A/feature.properties

22:05:40.461 - INFO:         file info: mode = 0444, size = 247 bytes

22:05:40.461 - INFO:       Extracting director/features/com.sap.ide.sapjvm.jre_81.8.8.A/feature.xml

22:05:40.463 - INFO:         file info: mode = 0444, size = 1184 bytes

22:05:40.463 - INFO:       Extracting director/features/com.sap.ide.sapjvm.jre_81.8.8.A/feature_de.properties

22:05:40.466 - INFO:         file info: mode = 0444, size = 227 bytes

22:05:40.466 - INFO:       Extracting director/features/com.sap.ide.sapjvm.jre_81.8.8.A/feature_en.properties

22:05:40.468 - INFO:         file info: mode = 0444, size = 217 bytes

22:05:40.468 - INFO:       Extracting director/features/com.sap.ide.sapjvm.jre_81.8.8.A/feature_fr.properties

22:05:40.470 - INFO:         file info: mode = 0444, size = 240 bytes

22:05:40.470 - INFO:       Extracting director/features/com.sap.ide.sapjvm.jre_81.8.8.A/feature_ja.properties

22:05:40.472 - INFO:         file info: mode = 0444, size = 303 bytes

22:05:40.472 - INFO:       Extracting director/features/com.sap.ide.sapjvm.jre_81.8.8.A/feature_zh_CN.properties

22:05:40.474 - INFO:         file info: mode = 0444, size = 314 bytes

22:05:40.475 - INFO:       Extracting director/p2/org.eclipse.equinox.p2.core/cache/artifacts.xml

22:05:40.477 - INFO:         file info: mode = 0444, size = 976 bytes

22:05:40.477 - INFO:       Extracting director/p2/org.eclipse.equinox.p2.core/cache/binary/com.sap.ndb.studio.director.executable.win32.win32.x86_64_1.8.0

22:05:40.485 - INFO:         file info: mode = 0644, size = 35112 bytes

22:05:40.485 - INFO:       Extracting director/p2/org.eclipse.equinox.p2.engine/.settings/org.eclipse.equinox.p2.artifact.repository.prefs

22:05:40.492 - INFO:         file info: mode = 0444, size = 7784 bytes

22:05:40.492 - INFO:       Extracting director/p2/org.eclipse.equinox.p2.engine/.settings/org.eclipse.equinox.p2.metadata.repository.prefs

22:05:40.495 - INFO:         file info: mode = 0444, size = 3130 bytes

22:05:40.495 - INFO:       Extracting director/p2/org.eclipse.equinox.p2.engine/profileRegistry/DefaultProfile.profile/.data/org.eclipse.equinox.internal.p2.touchpoint.eclipse.actions/jvmargs

22:05:40.498 - INFO:         file info: mode = 0644, size = 74 bytes

22:05:40.498 - INFO:       Extracting director/p2/org.eclipse.equinox.p2.engine/profileRegistry/DefaultProfile.profile/.lock

22:05:40.500 - INFO:         file info: mode = 0444, size = 0 bytes

22:05:40.500 - INFO:       Extracting director/p2/org.eclipse.equinox.p2.engine/profileRegistry/DefaultProfile.profile/1436291195081.profile.gz

22:05:40.502 - INFO:         file info: mode = 0644, size = 349 bytes

22:05:40.502 - INFO:       Extracting director/p2/org.eclipse.equinox.p2.engine/profileRegistry/DefaultProfile.profile/1436291195088.profile.gz

22:05:40.505 - INFO:         file info: mode = 0644, size = 352 bytes

22:05:40.505 - INFO:       Extracting director/p2/org.eclipse.equinox.p2.engine/profileRegistry/DefaultProfile.profile/1436291201826.profile.gz

22:05:40.510 - INFO:         file info: mode = 0644, size = 18743 bytes

22:05:40.511 - INFO:       Extracting director/p2/org.eclipse.equinox.p2.engine/profileRegistry/DefaultProfile.profile/1436291202332.profile.gz

22:05:40.517 - INFO:         file info: mode = 0644, size = 18742 bytes

22:05:40.517 - INFO:       Extracting director/plugins/com.sap.ide.sapjvm.jre.win32.x86_64_81.8.8.A/META-INF/MANIFEST.MF

22:05:40.524 - INFO:         file info: mode = 0444, size = 15307 bytes

22:05:40.524 - INFO:       Extracting director/plugins/com.sap.ide.sapjvm.jre.win32.x86_64_81.8.8.A/META-INF/SAP_SE_G.RSA

22:05:40.530 - INFO:         file info: mode = 0444, size = 8927 bytes

22:05:40.530 - INFO:       Extracting director/plugins/com.sap.ide.sapjvm.jre.win32.x86_64_81.8.8.A/META-INF/SAP_SE_G.SF

22:05:40.537 - INFO:         file info: mode = 0444, size = 14855 bytes

22:05:40.537 - INFO:       Extracting director/plugins/com.sap.ide.sapjvm.jre.win32.x86_64_81.8.8.A/META-INF/maven/com.sap.ide.sapjvm/com.sap.ide.sapjvm.jre.win32.x86_64/pom.properties

22:05:40.540 - INFO:         file info: mode = 0644, size = 141 bytes

22:05:40.540 - INFO:       Extracting director/plugins/com.sap.ide.sapjvm.jre.win32.x86_64_81.8.8.A/META-INF/maven/com.sap.ide.sapjvm/com.sap.ide.sapjvm.jre.win32.x86_64/pom.xml

22:05:40.543 - INFO:         file info: mode = 0644, size = 3014 bytes

22:05:40.543 - INFO:       Extracting director/plugins/com.sap.ide.sapjvm.jre.win32.x86_64_81.8.8.A/META-INF/p2.inf

22:05:40.545 - INFO:         file info: mode = 0444, size = 233 bytes

22:05:40.545 - INFO:       Extracting director/plugins/com.sap.ide.sapjvm.jre.win32.x86_64_81.8.8.A/jre/.hotspot_compiler

22:05:40.547 - INFO:         file info: mode = 0444, size = 482 bytes

22:05:40.548 - INFO:       Extracting director/plugins/com.sap.ide.sapjvm.jre.win32.x86_64_81.8.8.A/jre/COPYRIGHT

22:05:40.550 - INFO:         file info: mode = 0444, size = 3318 bytes

22:05:40.550 - INFO:       Extracting director/plugins/com.sap.ide.sapjvm.jre.win32.x86_64_81.8.8.A/jre/THIRDPARTYLICENSEREADME.txt

22:05:40.558 - INFO:         file info: mode = 0444, size = 178403 bytes

22:05:40.559 - INFO:       Extracting director/plugins/com.sap.ide.sapjvm.jre.win32.x86_64_81.8.8.A/jre/Welcome.html

22:05:40.562 - INFO:         file info: mode = 0444, size = 955 bytes

22:05:40.562 - INFO:       Extracting director/plugins/com.sap.ide.sapjvm.jre.win32.x86_64_81.8.8.A/jre/bin/JAWTAccessBridge-64.dll

22:05:40.575 - INFO:         file info: mode = 0444, size = 9216 bytes

22:05:40.575 - INFO:       Extracting director/plugins/com.sap.ide.sapjvm.jre.win32.x86_64_81.8.8.A/jre/bin/JAWTAccessBridge-64.pdb

22:05:40.583 - INFO:         file info: mode = 0444, size = 183296 bytes

22:05:40.583 - INFO:       Extracting director/plugins/com.sap.ide.sapjvm.jre.win32.x86_64_81.8.8.A/jre/bin/JavaAccessBridge-64.dll

22:05:40.599 - INFO:         file info: mode = 0444, size = 144896 bytes

22:05:40.599 - INFO:       Extracting director/plugins/com.sap.ide.sapjvm.jre.win32.x86_64_81.8.8.A/jre/bin/JavaAccessBridge-64.pdb

22:05:40.610 - INFO:         file info: mode = 0444, size = 551936 bytes

22:05:40.611 - INFO:       Extracting director/plugins/com.sap.ide.sapjvm.jre.win32.x86_64_81.8.8.A/jre/bin/WindowsAccessBridge-64.dll

22:05:40.632 - INFO:         file info: mode = 0444, size = 109568 bytes

22:05:40.632 - INFO:       Extracting director/plugins/com.sap.ide.sapjvm.jre.win32.x86_64_81.8.8.A/jre/bin/WindowsAccessBridge-64.pdb

22:05:40.647 - INFO:         file info: mode = 0444, size = 1190912 bytes

22:05:40.648 - INFO:       Extracting director/plugins/com.sap.ide.sapjvm.jre.win32.x86_64_81.8.8.A/jre/bin/attach.pdb

22:05:40.656 - INFO:         file info: mode = 0444, size = 240640 bytes

22:05:40.657 - INFO:       Extracting director/plugins/com.sap.ide.sapjvm.jre.win32.x86_64_81.8.8.A/jre/bin/awt.dll

22:05:40.689 - INFO:         file info: mode = 0444, size = 1654272 bytes

22:05:40.690 - INFO:       Extracting director/plugins/com.sap.ide.sapjvm.jre.win32.x86_64_81.8.8.A/jre/bin/awt.pdb

22:05:40.734 - INFO:         file info: mode = 0444, size = 5614592 bytes

22:05:40.735 - INFO:       Extracting director/plugins/com.sap.ide.sapjvm.jre.win32.x86_64_81.8.8.A/jre/bin/dcpr.dll

22:05:40.751 - INFO:         file info: mode = 0444, size = 164352 bytes

22:05:40.751 - INFO:       Extracting director/plugins/com.sap.ide.sapjvm.jre.win32.x86_64_81.8.8.A/jre/bin/dcpr.pdb

22:05:40.763 - INFO:         file info: mode = 0444, size = 519168 bytes

22:05:40.763 - INFO:       Extracting director/plugins/com.sap.ide.sapjvm.jre.win32.x86_64_81.8.8.A/jre/bin/dt_shmem.dll

22:05:40.777 - INFO:         file info: mode = 0444, size = 30720 bytes

22:05:40.777 - INFO:       Extracting director/plugins/com.sap.ide.sapjvm.jre.win32.x86_64_81.8.8.A/jre/bin/dt_shmem.pdb

22:05:40.816 - INFO:         file info: mode = 0444, size = 281600 bytes

22:05:40.817 - INFO:       Extracting director/plugins/com.sap.ide.sapjvm.jre.win32.x86_64_81.8.8.A/jre/bin/dt_socket.dll

22:05:40.832 - INFO:         file info: mode = 0444, size = 25088 bytes

22:05:40.832 - INFO:       Extracting director/plugins/com.sap.ide.sapjvm.jre.win32.x86_64_81.8.8.A/jre/bin/dt_socket.pdb

22:05:40.841 - INFO:         file info: mode = 0444, size = 240640 bytes

22:05:40.842 - INFO:       Extracting director/plugins/com.sap.ide.sapjvm.jre.win32.x86_64_81.8.8.A/jre/bin/fontmanager.dll

22:05:40.860 - INFO:         file info: mode = 0444, size = 277504 bytes

22:05:40.860 - INFO:       Extracting director/plugins/com.sap.ide.sapjvm.jre.win32.x86_64_81.8.8.A/jre/bin/fontmanager.pdb

22:05:40.878 - INFO:         file info: mode = 0444, size = 1608704 bytes

22:05:40.878 - INFO:       Extracting director/plugins/com.sap.ide.sapjvm.jre.win32.x86_64_81.8.8.A/jre/bin/hprof.dll

22:05:40.895 - INFO:         file info: mode = 0444, size = 152576 bytes

22:05:40.896 - INFO:       Extracting director/plugins/com.sap.ide.sapjvm.jre.win32.x86_64_81.8.8.A/jre/bin/hprof.pdb

22:05:40.908 - INFO:         file info: mode = 0444, size = 756736 bytes

22:05:40.908 - INFO:       Extracting director/plugins/com.sap.ide.sapjvm.jre.win32.x86_64_81.8.8.A/jre/bin/instrument.dll

22:05:40.929 - INFO:         file info: mode = 0444, size = 132096 bytes

22:05:40.930 - INFO:       Extracting director/plugins/com.sap.ide.sapjvm.jre.win32.x86_64_81.8.8.A/jre/bin/instrument.pdb

22:05:40.945 - INFO:         file info: mode = 0444, size = 1174528 bytes

22:05:40.946 - INFO:       Extracting director/plugins/com.sap.ide.sapjvm.jre.win32.x86_64_81.8.8.A/jre/bin/j2pcsc.dll

22:05:40.961 - INFO:         file info: mode = 0444, size = 14336 bytes

22:05:40.962 - INFO:       Extracting director/plugins/com.sap.ide.sapjvm.jre.win32.x86_64_81.8.8.A/jre/bin/j2pcsc.pdb

22:05:40.971 - INFO:         file info: mode = 0444, size = 224256 bytes

22:05:40.972 - INFO:       Extracting director/plugins/com.sap.ide.sapjvm.jre.win32.x86_64_81.8.8.A/jre/bin/j2pkcs11.dll

22:05:40.998 - INFO:         file info: mode = 0444, size = 95232 bytes

22:05:40.999 - INFO:       Extracting director/plugins/com.sap.ide.sapjvm.jre.win32.x86_64_81.8.8.A/jre/bin/j2pkcs11.pdb

22:05:41.010 - INFO:         file info: mode = 0444, size = 453632 bytes

22:05:41.010 - INFO:       Extracting director/plugins/com.sap.ide.sapjvm.jre.win32.x86_64_81.8.8.A/jre/bin/jaas_nt.dll

22:05:41.024 - INFO:         file info: mode = 0444, size = 14848 bytes

22:05:41.024 - INFO:       Extracting director/plugins/com.sap.ide.sapjvm.jre.win32.x86_64_81.8.8.A/jre/bin/jaas_nt.pdb

22:05:41.033 - INFO:         file info: mode = 0444, size = 183296 bytes

22:05:41.033 - INFO:       Extracting director/plugins/com.sap.ide.sapjvm.jre.win32.x86_64_81.8.8.A/jre/bin/jabswitch.exe

22:05:41.049 - INFO:         file info: mode = 0444, size = 27648 bytes

22:05:41.049 - INFO:       Extracting director/plugins/com.sap.ide.sapjvm.jre.win32.x86_64_81.8.8.A/jre/bin/jabswitch.pdb

22:05:41.059 - INFO:         file info: mode = 0444, size = 479232 bytes

22:05:41.059 - INFO:       Extracting director/plugins/com.sap.ide.sapjvm.jre.win32.x86_64_81.8.8.A/jre/bin/java.dll

22:05:41.078 - INFO:         file info: mode = 0444, size = 205312 bytes

22:05:41.078 - INFO:       Extracting director/plugins/com.sap.ide.sapjvm.jre.win32.x86_64_81.8.8.A/jre/bin/java.exe

22:05:41.108 - INFO:         file info: mode = 0444, size = 220672 bytes

22:05:41.108 - INFO:       Extracting director/plugins/com.sap.ide.sapjvm.jre.win32.x86_64_81.8.8.A/jre/bin/java.pdb

22:05:41.125 - INFO:         file info: mode = 0444, size = 1362944 bytes

22:05:41.126 - INFO:       Extracting director/plugins/com.sap.ide.sapjvm.jre.win32.x86_64_81.8.8.A/jre/bin/java_crw_demo.dll

22:05:41.140 - INFO:         file info: mode = 0444, size = 32768 bytes

22:05:41.140 - INFO:       Extracting director/plugins/com.sap.ide.sapjvm.jre.win32.x86_64_81.8.8.A/jre/bin/java_crw_demo.pdb

22:05:41.150 - INFO:         file info: mode = 0444, size = 299008 bytes

22:05:41.150 - INFO:       Extracting director/plugins/com.sap.ide.sapjvm.jre.win32.x86_64_81.8.8.A/jre/bin/javaw.exe

22:05:41.180 - INFO:         file info: mode = 0444, size = 220672 bytes

22:05:41.181 - INFO:       Extracting director/plugins/com.sap.ide.sapjvm.jre.win32.x86_64_81.8.8.A/jre/bin/javaw.pdb

22:05:41.199 - INFO:         file info: mode = 0444, size = 1682432 bytes

22:05:41.199 - INFO:       Extracting director/plugins/com.sap.ide.sapjvm.jre.win32.x86_64_81.8.8.A/jre/bin/jawt.dll

22:05:41.202 - INFO:         file info: mode = 0444, size = 8192 bytes

22:05:41.202 - INFO:       Extracting director/plugins/com.sap.ide.sapjvm.jre.win32.x86_64_81.8.8.A/jre/bin/jawt.pdb

22:05:41.212 - INFO:         file info: mode = 0444, size = 430080 bytes

22:05:41.212 - INFO:       Extracting director/plugins/com.sap.ide.sapjvm.jre.win32.x86_64_81.8.8.A/jre/bin/jdwp.dll

22:05:41.230 - INFO:         file info: mode = 0444, size = 310272 bytes

22:05:41.230 - INFO:       Extracting director/plugins/com.sap.ide.sapjvm.jre.win32.x86_64_81.8.8.A/jre/bin/jdwp.pdb

22:05:41.245 - INFO:         file info: mode = 0444, size = 1125376 bytes

22:05:41.245 - INFO:       Extracting director/plugins/com.sap.ide.sapjvm.jre.win32.x86_64_81.8.8.A/jre/bin/jjs.exe

22:05:41.258 - INFO:         file info: mode = 0444, size = 10240 bytes

22:05:41.259 - INFO:       Extracting director/plugins/com.sap.ide.sapjvm.jre.win32.x86_64_81.8.8.A/jre/bin/jjs.pdb

22:05:41.266 - INFO:         file info: mode = 0444, size = 175104 bytes

22:05:41.267 - INFO:       Extracting director/plugins/com.sap.ide.sapjvm.jre.win32.x86_64_81.8.8.A/jre/bin/jli.dll

22:05:41.290 - INFO:         file info: mode = 0444, size = 188928 bytes

22:05:41.290 - INFO:       Extracting director/plugins/com.sap.ide.sapjvm.jre.win32.x86_64_81.8.8.A/jre/bin/jli.pdb

22:05:41.308 - INFO:         file info: mode = 0444, size = 1666048 bytes

22:05:41.308 - INFO:       Extracting director/plugins/com.sap.ide.sapjvm.jre.win32.x86_64_81.8.8.A/jre/bin/jpeg.dll

22:05:41.324 - INFO:         file info: mode = 0444, size = 183808 bytes

22:05:41.325 - INFO:       Extracting director/plugins/com.sap.ide.sapjvm.jre.win32.x86_64_81.8.8.A/jre/bin/jpeg.pdb

22:05:41.337 - INFO:         file info: mode = 0444, size = 699392 bytes

22:05:41.337 - INFO:       Extracting director/plugins/com.sap.ide.sapjvm.jre.win32.x86_64_81.8.8.A/jre/bin/jsdt.dll

22:05:41.351 - INFO:         file info: mode = 0444, size = 14848 bytes

22:05:41.351 - INFO:       Extracting director/plugins/com.sap.ide.sapjvm.jre.win32.x86_64_81.8.8.A/jre/bin/jsdt.pdb

22:05:41.359 - INFO:         file info: mode = 0444, size = 216064 bytes

22:05:41.359 - INFO:       Extracting director/plugins/com.sap.ide.sapjvm.jre.win32.x86_64_81.8.8.A/jre/bin/jsound.dll

22:05:41.373 - INFO:         file info: mode = 0444, size = 18432 bytes

22:05:41.374 - INFO:       Extracting director/plugins/com.sap.ide.sapjvm.jre.win32.x86_64_81.8.8.A/jre/bin/jsound.pdb

22:05:41.382 - INFO:         file info: mode = 0444, size = 232448 bytes

22:05:41.383 - INFO:       Extracting director/plugins/com.sap.ide.sapjvm.jre.win32.x86_64_81.8.8.A/jre/bin/kcms.dll

22:05:41.400 - INFO:         file info: mode = 0444, size = 252928 bytes

22:05:41.400 - INFO:       Extracting director/plugins/com.sap.ide.sapjvm.jre.win32.x86_64_81.8.8.A/jre/bin/kcms.pdb

22:05:41.415 - INFO:         file info: mode = 0444, size = 1223680 bytes

22:05:41.416 - INFO:       Extracting director/plugins/com.sap.ide.sapjvm.jre.win32.x86_64_81.8.8.A/jre/bin/keytool.exe

22:05:41.430 - INFO:         file info: mode = 0444, size = 10240 bytes

22:05:41.430 - INFO:       Extracting director/plugins/com.sap.ide.sapjvm.jre.win32.x86_64_81.8.8.A/jre/bin/keytool.pdb

22:05:41.438 - INFO:         file info: mode = 0444, size = 175104 bytes

22:05:41.438 - INFO:       Extracting director/plugins/com.sap.ide.sapjvm.jre.win32.x86_64_81.8.8.A/jre/bin/kinit.exe

22:05:41.452 - INFO:         file info: mode = 0444, size = 10240 bytes

22:05:41.452 - INFO:       Extracting director/plugins/com.sap.ide.sapjvm.jre.win32.x86_64_81.8.8.A/jre/bin/kinit.pdb

22:05:41.460 - INFO:         file info: mode = 0444, size = 175104 bytes

22:05:41.461 - INFO:       Extracting director/plugins/com.sap.ide.sapjvm.jre.win32.x86_64_81.8.8.A/jre/bin/klist.exe

22:05:41.475 - INFO:         file info: mode = 0444, size = 10240 bytes

22:05:41.475 - INFO:       Extracting director/plugins/com.sap.ide.sapjvm.jre.win32.x86_64_81.8.8.A/jre/bin/klist.pdb

22:05:41.483 - INFO:         file info: mode = 0444, size = 175104 bytes

22:05:41.484 - INFO:       Extracting director/plugins/com.sap.ide.sapjvm.jre.win32.x86_64_81.8.8.A/jre/bin/ktab.exe

22:05:41.497 - INFO:         file info: mode = 0444, size = 10240 bytes

22:05:41.498 - INFO:       Extracting director/plugins/com.sap.ide.sapjvm.jre.win32.x86_64_81.8.8.A/jre/bin/ktab.pdb

22:05:41.511 - INFO:         file info: mode = 0444, size = 175104 bytes

22:05:41.512 - INFO:       Extracting director/plugins/com.sap.ide.sapjvm.jre.win32.x86_64_81.8.8.A/jre/bin/lcms.dll

22:05:41.529 - INFO:         file info: mode = 0444, size = 228864 bytes

22:05:41.529 - INFO:       Extracting director/plugins/com.sap.ide.sapjvm.jre.win32.x86_64_81.8.8.A/jre/bin/lcms.pdb

22:05:41.542 - INFO:         file info: mode = 0444, size = 946176 bytes

22:05:41.542 - INFO:       Extracting director/plugins/com.sap.ide.sapjvm.jre.win32.x86_64_81.8.8.A/jre/bin/management.dll

22:05:41.557 - INFO:         file info: mode = 0444, size = 42496 bytes

22:05:41.558 - INFO:       Extracting director/plugins/com.sap.ide.sapjvm.jre.win32.x86_64_81.8.8.A/jre/bin/management.pdb

22:05:41.567 - INFO:         file info: mode = 0444, size = 528384 bytes

22:05:41.567 - INFO:       Extracting director/plugins/com.sap.ide.sapjvm.jre.win32.x86_64_81.8.8.A/jre/bin/mlib_image.dll

22:05:41.588 - INFO:         file info: mode = 0444, size = 647680 bytes

22:05:41.588 - INFO:       Extracting director/plugins/com.sap.ide.sapjvm.jre.win32.x86_64_81.8.8.A/jre/bin/mlib_image.pdb

22:05:41.599 - INFO:         file info: mode = 0444, size = 650240 bytes

22:05:41.599 - INFO:       Extracting director/plugins/com.sap.ide.sapjvm.jre.win32.x86_64_81.8.8.A/jre/bin/net.dll

22:05:41.616 - INFO:         file info: mode = 0444, size = 130560 bytes

22:05:41.617 - INFO:       Extracting director/plugins/com.sap.ide.sapjvm.jre.win32.x86_64_81.8.8.A/jre/bin/net.pdb

22:05:41.629 - INFO:         file info: mode = 0444, size = 658432 bytes

22:05:41.629 - INFO:       Extracting director/plugins/com.sap.ide.sapjvm.jre.win32.x86_64_81.8.8.A/jre/bin/nio.dll

22:05:41.646 - INFO:         file info: mode = 0444, size = 67072 bytes

22:05:41.646 - INFO:       Extracting director/plugins/com.sap.ide.sapjvm.jre.win32.x86_64_81.8.8.A/jre/bin/nio.pdb

22:05:41.658 - INFO:         file info: mode = 0444, size = 519168 bytes

22:05:41.659 - INFO:       Extracting director/plugins/com.sap.ide.sapjvm.jre.win32.x86_64_81.8.8.A/jre/bin/npt.dll

22:05:41.673 - INFO:         file info: mode = 0444, size = 15360 bytes

22:05:41.674 - INFO:       Extracting director/plugins/com.sap.ide.sapjvm.jre.win32.x86_64_81.8.8.A/jre/bin/npt.pdb

22:05:41.683 - INFO:         file info: mode = 0444, size = 307200 bytes

22:05:41.683 - INFO:       Extracting director/plugins/com.sap.ide.sapjvm.jre.win32.x86_64_81.8.8.A/jre/bin/orbd.exe

22:05:41.698 - INFO:         file info: mode = 0444, size = 10240 bytes

22:05:41.700 - INFO:       Extracting director/plugins/com.sap.ide.sapjvm.jre.win32.x86_64_81.8.8.A/jre/bin/orbd.pdb

22:05:41.708 - INFO:         file info: mode = 0444, size = 175104 bytes

22:05:41.708 - INFO:       Extracting director/plugins/com.sap.ide.sapjvm.jre.win32.x86_64_81.8.8.A/jre/bin/pack200.exe

22:05:41.728 - INFO:         file info: mode = 0444, size = 10240 bytes

22:05:41.728 - INFO:       Extracting director/plugins/com.sap.ide.sapjvm.jre.win32.x86_64_81.8.8.A/jre/bin/pack200.pdb

22:05:41.736 - INFO:         file info: mode = 0444, size = 175104 bytes

22:05:41.737 - INFO:       Extracting director/plugins/com.sap.ide.sapjvm.jre.win32.x86_64_81.8.8.A/jre/bin/policytool.exe

22:05:41.751 - INFO:         file info: mode = 0444, size = 10240 bytes

22:05:41.753 - INFO:       Extracting director/plugins/com.sap.ide.sapjvm.jre.win32.x86_64_81.8.8.A/jre/bin/policytool.pdb

22:05:41.761 - INFO:         file info: mode = 0444, size = 175104 bytes

22:05:41.761 - INFO:       Extracting director/plugins/com.sap.ide.sapjvm.jre.win32.x86_64_81.8.8.A/jre/bin/rmid.exe

22:05:41.776 - INFO:         file info: mode = 0444, size = 10240 bytes

22:05:41.776 - INFO:       Extracting director/plugins/com.sap.ide.sapjvm.jre.win32.x86_64_81.8.8.A/jre/bin/rmid.pdb

22:05:41.797 - INFO:         file info: mode = 0444, size = 175104 bytes

22:05:41.798 - INFO:       Extracting director/plugins/com.sap.ide.sapjvm.jre.win32.x86_64_81.8.8.A/jre/bin/rmiregistry.exe

22:05:41.811 - INFO:         file info: mode = 0444, size = 10240 bytes

22:05:41.812 - INFO:       Extracting director/plugins/com.sap.ide.sapjvm.jre.win32.x86_64_81.8.8.A/jre/bin/rmiregistry.pdb

22:05:41.820 - INFO:         file info: mode = 0444, size = 175104 bytes

22:05:41.820 - INFO:       Extracting director/plugins/com.sap.ide.sapjvm.jre.win32.x86_64_81.8.8.A/jre/bin/sapjvm_addons.dll

22:05:41.836 - INFO:         file info: mode = 0444, size = 78848 bytes

22:05:41.836 - INFO:       Extracting director/plugins/com.sap.ide.sapjvm.jre.win32.x86_64_81.8.8.A/jre/bin/sapjvm_addons.pdb

22:05:41.849 - INFO:         file info: mode = 0444, size = 691200 bytes

22:05:41.850 - INFO:       Extracting director/plugins/com.sap.ide.sapjvm.jre.win32.x86_64_81.8.8.A/jre/bin/sapjvm_inspector.dll

22:05:41.868 - INFO:         file info: mode = 0444, size = 74752 bytes

22:05:41.868 - INFO:       Extracting director/plugins/com.sap.ide.sapjvm.jre.win32.x86_64_81.8.8.A/jre/bin/sapjvm_inspector.pdb

22:05:41.880 - INFO:         file info: mode = 0444, size = 625664 bytes

22:05:41.880 - INFO:       Extracting director/plugins/com.sap.ide.sapjvm.jre.win32.x86_64_81.8.8.A/jre/bin/server/Xusage.txt

22:05:41.882 - INFO:         file info: mode = 0444, size = 0 bytes

22:05:41.882 - INFO:       Extracting director/plugins/com.sap.ide.sapjvm.jre.win32.x86_64_81.8.8.A/jre/bin/server/jvm.dll

22:05:42.031 - INFO:         file info: mode = 0444, size = 13479424 bytes

22:05:42.032 - INFO:       Extracting director/plugins/com.sap.ide.sapjvm.jre.win32.x86_64_81.8.8.A/jre/bin/server/jvm.pdb

22:05:42.517 - INFO:         file info: mode = 0444, size = 51743744 bytes

22:05:42.518 - INFO:       Extracting director/plugins/com.sap.ide.sapjvm.jre.win32.x86_64_81.8.8.A/jre/bin/server/sapjvm.info

22:05:42.521 - INFO:         file info: mode = 0444, size = 45 bytes

22:05:42.521 - INFO:       Extracting director/plugins/com.sap.ide.sapjvm.jre.win32.x86_64_81.8.8.A/jre/bin/servertool.exe

22:05:42.534 - INFO:         file info: mode = 0444, size = 10240 bytes

22:05:42.535 - INFO:       Extracting director/plugins/com.sap.ide.sapjvm.jre.win32.x86_64_81.8.8.A/jre/bin/servertool.pdb

22:05:42.543 - INFO:         file info: mode = 0444, size = 175104 bytes

22:05:42.543 - INFO:       Extracting director/plugins/com.sap.ide.sapjvm.jre.win32.x86_64_81.8.8.A/jre/bin/splashscreen.dll

22:05:42.560 - INFO:         file info: mode = 0444, size = 240128 bytes

22:05:42.561 - INFO:       Extracting director/plugins/com.sap.ide.sapjvm.jre.win32.x86_64_81.8.8.A/jre/bin/splashscreen.pdb

22:05:42.575 - INFO:         file info: mode = 0444, size = 1092608 bytes

22:05:42.575 - INFO:       Extracting director/plugins/com.sap.ide.sapjvm.jre.win32.x86_64_81.8.8.A/jre/bin/sunec.dll

22:05:42.590 - INFO:         file info: mode = 0444, size = 152064 bytes

22:05:42.590 - INFO:       Extracting director/plugins/com.sap.ide.sapjvm.jre.win32.x86_64_81.8.8.A/jre/bin/sunec.pdb

22:05:42.600 - INFO:         file info: mode = 0444, size = 551936 bytes

22:05:42.601 - INFO:       Extracting director/plugins/com.sap.ide.sapjvm.jre.win32.x86_64_81.8.8.A/jre/bin/sunmscapi.dll

22:05:42.615 - INFO:         file info: mode = 0444, size = 25600 bytes

22:05:42.616 - INFO:       Extracting director/plugins/com.sap.ide.sapjvm.jre.win32.x86_64_81.8.8.A/jre/bin/sunmscapi.pdb

22:05:42.627 - INFO:         file info: mode = 0444, size = 289792 bytes

22:05:42.628 - INFO:       Extracting director/plugins/com.sap.ide.sapjvm.jre.win32.x86_64_81.8.8.A/jre/bin/t2k.dll

22:05:42.646 - INFO:         file info: mode = 0444, size = 275456 bytes

22:05:42.646 - INFO:       Extracting director/plugins/com.sap.ide.sapjvm.jre.win32.x86_64_81.8.8.A/jre/bin/t2k.pdb

22:05:42.659 - INFO:         file info: mode = 0444, size = 1028096 bytes

22:05:42.660 - INFO:       Extracting director/plugins/com.sap.ide.sapjvm.jre.win32.x86_64_81.8.8.A/jre/bin/tnameserv.exe

22:05:42.675 - INFO:         file info: mode = 0444, size = 10240 bytes

22:05:42.675 - INFO:       Extracting director/plugins/com.sap.ide.sapjvm.jre.win32.x86_64_81.8.8.A/jre/bin/tnameserv.pdb

22:05:42.683 - INFO:         file info: mode = 0444, size = 175104 bytes

22:05:42.683 - INFO:       Extracting director/plugins/com.sap.ide.sapjvm.jre.win32.x86_64_81.8.8.A/jre/bin/unpack.dll

22:05:42.699 - INFO:         file info: mode = 0444, size = 91648 bytes

22:05:42.700 - INFO:       Extracting director/plugins/com.sap.ide.sapjvm.jre.win32.x86_64_81.8.8.A/jre/bin/unpack.pdb

22:05:42.710 - INFO:         file info: mode = 0444, size = 561152 bytes

22:05:42.711 - INFO:       Extracting director/plugins/com.sap.ide.sapjvm.jre.win32.x86_64_81.8.8.A/jre/bin/unpack200.exe

22:05:42.727 - INFO:         file info: mode = 0444, size = 223232 bytes

22:05:42.727 - INFO:       Extracting director/plugins/com.sap.ide.sapjvm.jre.win32.x86_64_81.8.8.A/jre/bin/unpack200.pdb

22:05:42.739 - INFO:         file info: mode = 0444, size = 658432 bytes

22:05:42.739 - INFO:       Extracting director/plugins/com.sap.ide.sapjvm.jre.win32.x86_64_81.8.8.A/jre/bin/verify.dll

22:05:42.755 - INFO:         file info: mode = 0444, size = 53248 bytes

22:05:42.755 - INFO:       Extracting director/plugins/com.sap.ide.sapjvm.jre.win32.x86_64_81.8.8.A/jre/bin/verify.pdb

22:05:42.765 - INFO:         file info: mode = 0444, size = 289792 bytes

22:05:42.765 - INFO:       Extracting director/plugins/com.sap.ide.sapjvm.jre.win32.x86_64_81.8.8.A/jre/bin/w2k_lsa_auth.dll

22:05:42.781 - INFO:         file info: mode = 0444, size = 17920 bytes

22:05:42.781 - INFO:       Extracting director/plugins/com.sap.ide.sapjvm.jre.win32.x86_64_81.8.8.A/jre/bin/zip.dll

22:05:42.796 - INFO:         file info: mode = 0444, size = 95744 bytes

22:05:42.797 - INFO:       Extracting director/plugins/com.sap.ide.sapjvm.jre.win32.x86_64_81.8.8.A/jre/bin/zip.pdb

22:05:42.810 - INFO:         file info: mode = 0444, size = 429056 bytes

22:05:42.810 - INFO:       Extracting director/plugins/com.sap.ide.sapjvm.jre.win32.x86_64_81.8.8.A/jre/buildinfo.txt

22:05:42.813 - INFO:         file info: mode = 0444, size = 154 bytes

22:05:42.813 - INFO:       Extracting director/plugins/com.sap.ide.sapjvm.jre.win32.x86_64_81.8.8.A/jre/lib/accessibility.properties

22:05:42.816 - INFO:         file info: mode = 0444, size = 155 bytes

22:05:42.816 - INFO:       Extracting director/plugins/com.sap.ide.sapjvm.jre.win32.x86_64_81.8.8.A/jre/lib/amd64/jvm.cfg

22:05:42.818 - INFO:         file info: mode = 0444, size = 656 bytes

22:05:42.819 - INFO:       Extracting director/plugins/com.sap.ide.sapjvm.jre.win32.x86_64_81.8.8.A/jre/lib/calendars.properties

22:05:42.821 - INFO:         file info: mode = 0444, size = 1438 bytes

22:05:42.821 - INFO:       Extracting director/plugins/com.sap.ide.sapjvm.jre.win32.x86_64_81.8.8.A/jre/lib/charsets.jar

22:05:42.860 - INFO:         file info: mode = 0444, size = 3147994 bytes

22:05:42.861 - INFO:       Extracting director/plugins/com.sap.ide.sapjvm.jre.win32.x86_64_81.8.8.A/jre/lib/classlist

22:05:42.871 - INFO:         file info: mode = 0444, size = 80761 bytes

22:05:42.871 - INFO:       Extracting director/plugins/com.sap.ide.sapjvm.jre.win32.x86_64_81.8.8.A/jre/lib/cmm/CIEXYZ.pf

22:05:42.875 - INFO:         file info: mode = 0444, size = 51236 bytes

22:05:42.876 - INFO:       Extracting director/plugins/com.sap.ide.sapjvm.jre.win32.x86_64_81.8.8.A/jre/lib/cmm/GRAY.pf

22:05:42.879 - INFO:         file info: mode = 0444, size = 632 bytes

22:05:42.879 - INFO:       Extracting director/plugins/com.sap.ide.sapjvm.jre.win32.x86_64_81.8.8.A/jre/lib/cmm/LINEAR_RGB.pf

22:05:42.883 - INFO:         file info: mode = 0444, size = 1044 bytes

22:05:42.883 - INFO:       Extracting director/plugins/com.sap.ide.sapjvm.jre.win32.x86_64_81.8.8.A/jre/lib/cmm/PYCC.pf

22:05:42.890 - INFO:         file info: mode = 0444, size = 274474 bytes

22:05:42.890 - INFO:       Extracting director/plugins/com.sap.ide.sapjvm.jre.win32.x86_64_81.8.8.A/jre/lib/cmm/sRGB.pf

22:05:42.893 - INFO:         file info: mode = 0444, size = 3144 bytes

22:05:42.893 - INFO:       Extracting director/plugins/com.sap.ide.sapjvm.jre.win32.x86_64_81.8.8.A/jre/lib/content-types.properties

22:05:42.895 - INFO:         file info: mode = 0444, size = 5824 bytes

22:05:42.896 - INFO:       Extracting director/plugins/com.sap.ide.sapjvm.jre.win32.x86_64_81.8.8.A/jre/lib/currency.data

22:05:42.899 - INFO:         file info: mode = 0444, size = 4074 bytes

22:05:42.899 - INFO:       Extracting director/plugins/com.sap.ide.sapjvm.jre.win32.x86_64_81.8.8.A/jre/lib/ext/access-bridge-64.jar

22:05:42.910 - INFO:         file info: mode = 0444, size = 203890 bytes

22:05:42.911 - INFO:       Extracting director/plugins/com.sap.ide.sapjvm.jre.win32.x86_64_81.8.8.A/jre/lib/ext/cldrdata.jar

22:05:42.960 - INFO:         file info: mode = 0444, size = 4003636 bytes

22:05:42.961 - INFO:       Extracting director/plugins/com.sap.ide.sapjvm.jre.win32.x86_64_81.8.8.A/jre/lib/ext/dnsns.jar

22:05:42.990 - INFO:         file info: mode = 0444, size = 9432 bytes

22:05:42.991 - INFO:       Extracting director/plugins/com.sap.ide.sapjvm.jre.win32.x86_64_81.8.8.A/jre/lib/ext/jaccess.jar

22:05:43.098 - INFO:         file info: mode = 0444, size = 48350 bytes

22:05:43.099 - INFO:       Extracting director/plugins/com.sap.ide.sapjvm.jre.win32.x86_64_81.8.8.A/jre/lib/ext/localedata.jar

22:05:43.121 - INFO:         file info: mode = 0444, size = 1311463 bytes

22:05:43.121 - INFO:       Extracting director/plugins/com.sap.ide.sapjvm.jre.win32.x86_64_81.8.8.A/jre/lib/ext/meta-index

22:05:43.124 - INFO:         file info: mode = 0444, size = 909 bytes

22:05:43.124 - INFO:       Extracting director/plugins/com.sap.ide.sapjvm.jre.win32.x86_64_81.8.8.A/jre/lib/ext/nashorn.jar

22:05:43.151 - INFO:         file info: mode = 0444, size = 2008988 bytes

22:05:43.152 - INFO:       Extracting director/plugins/com.sap.ide.sapjvm.jre.win32.x86_64_81.8.8.A/jre/lib/ext/sunec.jar

22:05:43.225 - INFO:         file info: mode = 0444, size = 39773 bytes

22:05:43.226 - INFO:       Extracting director/plugins/com.sap.ide.sapjvm.jre.win32.x86_64_81.8.8.A/jre/lib/ext/sunjce_provider.jar

22:05:43.237 - INFO:         file info: mode = 0444, size = 278075 bytes

22:05:43.238 - INFO:       Extracting director/plugins/com.sap.ide.sapjvm.jre.win32.x86_64_81.8.8.A/jre/lib/ext/sunmscapi.jar

22:05:43.312 - INFO:         file info: mode = 0444, size = 32654 bytes

22:05:43.313 - INFO:       Extracting director/plugins/com.sap.ide.sapjvm.jre.win32.x86_64_81.8.8.A/jre/lib/ext/sunpkcs11.jar

22:05:43.324 - INFO:         file info: mode = 0444, size = 249387 bytes

22:05:43.324 - INFO:       Extracting director/plugins/com.sap.ide.sapjvm.jre.win32.x86_64_81.8.8.A/jre/lib/ext/zipfs.jar

22:05:43.333 - INFO:         file info: mode = 0444, size = 80143 bytes

22:05:43.334 - INFO:       Extracting director/plugins/com.sap.ide.sapjvm.jre.win32.x86_64_81.8.8.A/jre/lib/flavormap.properties

22:05:43.336 - INFO:         file info: mode = 0444, size = 4005 bytes

22:05:43.337 - INFO:       Extracting director/plugins/com.sap.ide.sapjvm.jre.win32.x86_64_81.8.8.A/jre/lib/fontconfig.bfc

22:05:43.339 - INFO:         file info: mode = 0444, size = 3670 bytes

22:05:43.339 - INFO:       Extracting director/plugins/com.sap.ide.sapjvm.jre.win32.x86_64_81.8.8.A/jre/lib/fontconfig.properties.src

22:05:43.346 - INFO:         file info: mode = 0444, size = 10779 bytes

22:05:43.346 - INFO:       Extracting director/plugins/com.sap.ide.sapjvm.jre.win32.x86_64_81.8.8.A/jre/lib/fonts/LucidaBrightDemiBold.ttf

22:05:43.350 - INFO:         file info: mode = 0444, size = 75144 bytes

22:05:43.351 - INFO:       Extracting director/plugins/com.sap.ide.sapjvm.jre.win32.x86_64_81.8.8.A/jre/lib/fonts/LucidaBrightDemiItalic.ttf

22:05:43.354 - INFO:         file info: mode = 0644, size = 75124 bytes

22:05:43.355 - INFO:       Extracting director/plugins/com.sap.ide.sapjvm.jre.win32.x86_64_81.8.8.A/jre/lib/fonts/LucidaBrightItalic.ttf

22:05:43.359 - INFO:         file info: mode = 0444, size = 80856 bytes

22:05:43.359 - INFO:       Extracting director/plugins/com.sap.ide.sapjvm.jre.win32.x86_64_81.8.8.A/jre/lib/fonts/LucidaBrightRegular.ttf

22:05:43.367 - INFO:         file info: mode = 0444, size = 344908 bytes

22:05:43.368 - INFO:       Extracting director/plugins/com.sap.ide.sapjvm.jre.win32.x86_64_81.8.8.A/jre/lib/fonts/LucidaSansDemiBold.ttf

22:05:43.375 - INFO:         file info: mode = 0444, size = 317896 bytes

22:05:43.375 - INFO:       Extracting director/plugins/com.sap.ide.sapjvm.jre.win32.x86_64_81.8.8.A/jre/lib/fonts/LucidaSansRegular.ttf

22:05:43.388 - INFO:         file info: mode = 0444, size = 698236 bytes

22:05:43.389 - INFO:       Extracting director/plugins/com.sap.ide.sapjvm.jre.win32.x86_64_81.8.8.A/jre/lib/fonts/LucidaTypewriterBold.ttf

22:05:43.395 - INFO:         file info: mode = 0444, size = 234068 bytes

22:05:43.395 - INFO:       Extracting director/plugins/com.sap.ide.sapjvm.jre.win32.x86_64_81.8.8.A/jre/lib/fonts/LucidaTypewriterRegular.ttf

22:05:43.401 - INFO:         file info: mode = 0644, size = 242700 bytes

22:05:43.402 - INFO:       Extracting director/plugins/com.sap.ide.sapjvm.jre.win32.x86_64_81.8.8.A/jre/lib/hijrah-config-umalqura.properties

22:05:43.409 - INFO:         file info: mode = 0644, size = 14331 bytes

22:05:43.409 - INFO:       Extracting director/plugins/com.sap.ide.sapjvm.jre.win32.x86_64_81.8.8.A/jre/lib/images/cursors/cursors.properties

22:05:43.412 - INFO:         file info: mode = 0644, size = 1320 bytes

22:05:43.413 - INFO:       Extracting director/plugins/com.sap.ide.sapjvm.jre.win32.x86_64_81.8.8.A/jre/lib/images/cursors/invalid32x32.gif

22:05:43.415 - INFO:         file info: mode = 0644, size = 153 bytes

22:05:43.416 - INFO:       Extracting director/plugins/com.sap.ide.sapjvm.jre.win32.x86_64_81.8.8.A/jre/lib/images/cursors/win32_CopyDrop32x32.gif

22:05:43.419 - INFO:         file info: mode = 0644, size = 165 bytes

22:05:43.419 - INFO:       Extracting director/plugins/com.sap.ide.sapjvm.jre.win32.x86_64_81.8.8.A/jre/lib/images/cursors/win32_CopyNoDrop32x32.gif

22:05:43.422 - INFO:         file info: mode = 0644, size = 153 bytes

22:05:43.422 - INFO:       Extracting director/plugins/com.sap.ide.sapjvm.jre.win32.x86_64_81.8.8.A/jre/lib/images/cursors/win32_LinkDrop32x32.gif

22:05:43.425 - INFO:         file info: mode = 0644, size = 168 bytes

22:05:43.425 - INFO:       Extracting director/plugins/com.sap.ide.sapjvm.jre.win32.x86_64_81.8.8.A/jre/lib/images/cursors/win32_LinkNoDrop32x32.gif

22:05:43.428 - INFO:         file info: mode = 0644, size = 153 bytes

22:05:43.428 - INFO:       Extracting director/plugins/com.sap.ide.sapjvm.jre.win32.x86_64_81.8.8.A/jre/lib/images/cursors/win32_MoveDrop32x32.gif

22:05:43.430 - INFO:         file info: mode = 0644, size = 147 bytes

22:05:43.431 - INFO:       Extracting director/plugins/com.sap.ide.sapjvm.jre.win32.x86_64_81.8.8.A/jre/lib/images/cursors/win32_MoveNoDrop32x32.gif

22:05:43.434 - INFO:         file info: mode = 0644, size = 153 bytes

22:05:43.434 - INFO:       Extracting director/plugins/com.sap.ide.sapjvm.jre.win32.x86_64_81.8.8.A/jre/lib/jce.jar

22:05:43.443 - INFO:         file info: mode = 0444, size = 114708 bytes

22:05:43.443 - INFO:       Extracting director/plugins/com.sap.ide.sapjvm.jre.win32.x86_64_81.8.8.A/jre/lib/jsse.jar

22:05:43.458 - INFO:         file info: mode = 0444, size = 623213 bytes

22:05:43.458 - INFO:       Extracting director/plugins/com.sap.ide.sapjvm.jre.win32.x86_64_81.8.8.A/jre/lib/jvm.hprof.txt

22:05:43.461 - INFO:         file info: mode = 0444, size = 4312 bytes

22:05:43.461 - INFO:       Extracting director/plugins/com.sap.ide.sapjvm.jre.win32.x86_64_81.8.8.A/jre/lib/logging.properties

22:05:43.464 - INFO:         file info: mode = 0444, size = 2514 bytes

22:05:43.465 - INFO:       Extracting director/plugins/com.sap.ide.sapjvm.jre.win32.x86_64_81.8.8.A/jre/lib/management-agent.jar

22:05:43.467 - INFO:         file info: mode = 0444, size = 370 bytes

22:05:43.467 - INFO:       Extracting director/plugins/com.sap.ide.sapjvm.jre.win32.x86_64_81.8.8.A/jre/lib/management/jmxremote.access

22:05:43.470 - INFO:         file info: mode = 0444, size = 4077 bytes

22:05:43.470 - INFO:       Extracting director/plugins/com.sap.ide.sapjvm.jre.win32.x86_64_81.8.8.A/jre/lib/management/jmxremote.password.template

22:05:43.473 - INFO:         file info: mode = 0644, size = 2920 bytes

22:05:43.473 - INFO:       Extracting director/plugins/com.sap.ide.sapjvm.jre.win32.x86_64_81.8.8.A/jre/lib/management/management.properties

22:05:43.481 - INFO:         file info: mode = 0644, size = 14415 bytes

22:05:43.481 - INFO:       Extracting director/plugins/com.sap.ide.sapjvm.jre.win32.x86_64_81.8.8.A/jre/lib/management/snmp.acl.template

22:05:43.484 - INFO:         file info: mode = 0444, size = 3486 bytes

22:05:43.484 - INFO:       Extracting director/plugins/com.sap.ide.sapjvm.jre.win32.x86_64_81.8.8.A/jre/lib/meta-index

22:05:43.487 - INFO:         file info: mode = 0444, size = 2166 bytes

22:05:43.487 - INFO:       Extracting director/plugins/com.sap.ide.sapjvm.jre.win32.x86_64_81.8.8.A/jre/lib/net.properties

22:05:43.494 - INFO:         file info: mode = 0444, size = 3144 bytes

22:05:43.494 - INFO:       Extracting director/plugins/com.sap.ide.sapjvm.jre.win32.x86_64_81.8.8.A/jre/lib/psfont.properties.ja

22:05:43.497 - INFO:         file info: mode = 0444, size = 2915 bytes

22:05:43.497 - INFO:       Extracting director/plugins/com.sap.ide.sapjvm.jre.win32.x86_64_81.8.8.A/jre/lib/psfontj2d.properties

22:05:43.504 - INFO:         file info: mode = 0444, size = 10716 bytes

22:05:43.505 - INFO:       Extracting director/plugins/com.sap.ide.sapjvm.jre.win32.x86_64_81.8.8.A/jre/lib/resources.jar

22:05:43.539 - INFO:         file info: mode = 0444, size = 3521184 bytes

22:05:43.539 - INFO:       Extracting director/plugins/com.sap.ide.sapjvm.jre.win32.x86_64_81.8.8.A/jre/lib/rt.jar

22:05:44.255 - INFO:         file info: mode = 0444, size = 73189222 bytes

22:05:44.256 - INFO:       Extracting director/plugins/com.sap.ide.sapjvm.jre.win32.x86_64_81.8.8.A/jre/lib/security/US_export_policy.jar

22:05:44.259 - INFO:         file info: mode = 0444, size = 3026 bytes

22:05:44.260 - INFO:       Extracting director/plugins/com.sap.ide.sapjvm.jre.win32.x86_64_81.8.8.A/jre/lib/security/blacklist

22:05:44.263 - INFO:         file info: mode = 0444, size = 4149 bytes

22:05:44.263 - INFO:       Extracting director/plugins/com.sap.ide.sapjvm.jre.win32.x86_64_81.8.8.A/jre/lib/security/blacklisted.certs

22:05:44.270 - INFO:         file info: mode = 0444, size = 1188 bytes

22:05:44.270 - INFO:       Extracting director/plugins/com.sap.ide.sapjvm.jre.win32.x86_64_81.8.8.A/jre/lib/security/cacerts

22:05:44.276 - INFO:         file info: mode = 0444, size = 42077 bytes

22:05:44.277 - INFO:       Extracting director/plugins/com.sap.ide.sapjvm.jre.win32.x86_64_81.8.8.A/jre/lib/security/java.policy

22:05:44.286 - INFO:         file info: mode = 0444, size = 2619 bytes

22:05:44.286 - INFO:       Extracting director/plugins/com.sap.ide.sapjvm.jre.win32.x86_64_81.8.8.A/jre/lib/security/java.security

22:05:44.294 - INFO:         file info: mode = 0444, size = 21855 bytes

22:05:44.294 - INFO:       Extracting director/plugins/com.sap.ide.sapjvm.jre.win32.x86_64_81.8.8.A/jre/lib/security/local_policy.jar

22:05:44.297 - INFO:         file info: mode = 0444, size = 3527 bytes

22:05:44.298 - INFO:       Extracting director/plugins/com.sap.ide.sapjvm.jre.win32.x86_64_81.8.8.A/jre/lib/security/trusted.libraries

22:05:44.299 - INFO:         file info: mode = 0444, size = 0 bytes

22:05:44.299 - INFO:       Extracting director/plugins/com.sap.ide.sapjvm.jre.win32.x86_64_81.8.8.A/jre/lib/sound.properties

22:05:44.306 - INFO:         file info: mode = 0444, size = 1249 bytes

22:05:44.306 - INFO:       Extracting director/plugins/com.sap.ide.sapjvm.jre.win32.x86_64_81.8.8.A/jre/lib/src_ecc.zip

22:05:44.315 - INFO:         file info: mode = 0444, size = 153782 bytes

22:05:44.316 - INFO:       Extracting director/plugins/com.sap.ide.sapjvm.jre.win32.x86_64_81.8.8.A/jre/lib/tzdb.dat

22:05:44.323 - INFO:         file info: mode = 0444, size = 101371 bytes

22:05:44.323 - INFO:       Extracting director/plugins/com.sap.ide.sapjvm.jre.win32.x86_64_81.8.8.A/jre/lib/tzmappings

22:05:44.329 - INFO:         file info: mode = 0444, size = 8602 bytes

22:05:44.329 - INFO:       Extracting director/plugins/com.sap.ide.sapjvm.jre.win32.x86_64_81.8.8.A/plugin.properties

22:05:44.332 - INFO:         file info: mode = 0444, size = 70 bytes

22:05:44.333 - INFO:       Extracting director/plugins/org.apache.commons.codec_1.6.0.v201305230611.jar

22:05:44.342 - INFO:         file info: mode = 0444, size = 258015 bytes

22:05:44.342 - INFO:       Extracting director/plugins/org.apache.commons.logging_1.1.1.v201101211721.jar

22:05:44.352 - INFO:         file info: mode = 0444, size = 68107 bytes

22:05:44.352 - INFO:       Extracting director/plugins/org.apache.httpcomponents.httpclient_4.3.6.v201411290715.jar

22:05:44.368 - INFO:         file info: mode = 0444, size = 849668 bytes

22:05:44.368 - INFO:       Extracting director/plugins/org.apache.httpcomponents.httpcore_4.3.3.v201411290715.jar

22:05:44.380 - INFO:         file info: mode = 0444, size = 318024 bytes

22:05:44.381 - INFO:       Extracting director/plugins/org.eclipse.core.contenttype_3.5.0.v20150421-2214.jar

22:05:44.390 - INFO:         file info: mode = 0444, size = 99189 bytes

22:05:44.391 - INFO:       Extracting director/plugins/org.eclipse.core.jobs_3.7.0.v20150330-2103.jar

22:05:44.400 - INFO:         file info: mode = 0444, size = 107123 bytes

22:05:44.400 - INFO:       Extracting director/plugins/org.eclipse.core.net.win32.x86_64_1.0.100.v20140124-2013.jar

22:05:44.445 - INFO:         file info: mode = 0444, size = 29259 bytes

22:05:44.446 - INFO:       Extracting director/plugins/org.eclipse.core.net_1.2.300.v20141118-1725.jar

22:05:44.455 - INFO:         file info: mode = 0444, size = 71284 bytes

22:05:44.455 - INFO:       Extracting director/plugins/org.eclipse.core.runtime.compatibility.registry_3.6.0.v20150318-1505/.api_description

22:05:44.461 - INFO:         file info: mode = 0644, size = 258 bytes

22:05:44.462 - INFO:       Extracting director/plugins/org.eclipse.core.runtime.compatibility.registry_3.6.0.v20150318-1505/META-INF/ECLIPSE_.RSA

22:05:44.464 - INFO:         file info: mode = 0644, size = 6274 bytes

22:05:44.465 - INFO:       Extracting director/plugins/org.eclipse.core.runtime.compatibility.registry_3.6.0.v20150318-1505/META-INF/ECLIPSE_.SF

22:05:44.467 - INFO:         file info: mode = 0644, size = 474 bytes

22:05:44.467 - INFO:       Extracting director/plugins/org.eclipse.core.runtime.compatibility.registry_3.6.0.v20150318-1505/META-INF/MANIFEST.MF

22:05:44.469 - INFO:         file info: mode = 0644, size = 1263 bytes

22:05:44.469 - INFO:       Extracting director/plugins/org.eclipse.core.runtime.compatibility.registry_3.6.0.v20150318-1505/about.html

22:05:44.484 - INFO:         file info: mode = 0444, size = 1432 bytes

22:05:44.484 - INFO:       Extracting director/plugins/org.eclipse.core.runtime.compatibility.registry_3.6.0.v20150318-1505/fragment.properties

22:05:44.487 - INFO:         file info: mode = 0644, size = 603 bytes

22:05:44.487 - INFO:       Extracting director/plugins/org.eclipse.core.runtime.compatibility.registry_3.6.0.v20150318-1505/runtime_registry_compatibility.jar

22:05:44.535 - INFO:         file info: mode = 0644, size = 12437 bytes

22:05:44.535 - INFO:       Extracting director/plugins/org.eclipse.core.runtime_3.11.0.v20150405-1723.jar

22:05:44.544 - INFO:         file info: mode = 0444, size = 76888 bytes

22:05:44.544 - INFO:       Extracting director/plugins/org.eclipse.ecf.filetransfer_5.0.0.v20150512-1727.jar

22:05:44.553 - INFO:         file info: mode = 0444, size = 51128 bytes

22:05:44.554 - INFO:       Extracting director/plugins/org.eclipse.ecf.identity_3.5.0.v20150512-1727.jar

22:05:44.562 - INFO:         file info: mode = 0444, size = 61096 bytes

22:05:44.562 - INFO:       Extracting director/plugins/org.eclipse.ecf.provider.filetransfer.httpclient4.ssl_1.0.0.v20150512-1727.jar

22:05:44.629 - INFO:         file info: mode = 0444, size = 13182 bytes

22:05:44.630 - INFO:       Extracting director/plugins/org.eclipse.ecf.provider.filetransfer.httpclient4_1.0.1043.v20150512-1727.jar

22:05:44.639 - INFO:         file info: mode = 0444, size = 70799 bytes

22:05:44.639 - INFO:       Extracting director/plugins/org.eclipse.ecf.provider.filetransfer.ssl_1.0.0.v20150512-1727.jar

22:05:44.678 - INFO:         file info: mode = 0444, size = 9060 bytes

22:05:44.678 - INFO:       Extracting director/plugins/org.eclipse.ecf.provider.filetransfer_3.2.200.v20150512-1727.jar

22:05:44.688 - INFO:         file info: mode = 0444, size = 127283 bytes

22:05:44.688 - INFO:       Extracting director/plugins/org.eclipse.ecf.ssl_1.1.0.v20150512-1727.jar

22:05:44.731 - INFO:         file info: mode = 0444, size = 13953 bytes

22:05:44.732 - INFO:       Extracting director/plugins/org.eclipse.ecf_3.4.0.v20150512-1727.jar

22:05:44.741 - INFO:         file info: mode = 0444, size = 100821 bytes

22:05:44.741 - INFO:       Extracting director/plugins/org.eclipse.equinox.app_1.3.300.v20150423-1356.jar

22:05:44.749 - INFO:         file info: mode = 0444, size = 86680 bytes

22:05:44.750 - INFO:       Extracting director/plugins/org.eclipse.equinox.common_3.7.0.v20150402-1709.jar

22:05:44.759 - INFO:         file info: mode = 0444, size = 111675 bytes

22:05:44.759 - INFO:       Extracting director/plugins/org.eclipse.equinox.ds_1.4.300.v20150423-1356.jar

22:05:44.777 - INFO:         file info: mode = 0444, size = 195728 bytes

22:05:44.778 - INFO:       Extracting director/plugins/org.eclipse.equinox.frameworkadmin.equinox_1.0.600.v20150522-2234.jar

22:05:44.795 - INFO:         file info: mode = 0444, size = 63562 bytes

22:05:44.797 - INFO:       Extracting director/plugins/org.eclipse.equinox.frameworkadmin_2.0.200.v20150423-1455.jar

22:05:45.288 - INFO:         file info: mode = 0444, size = 36365 bytes

22:05:45.288 - INFO:       Extracting director/plugins/org.eclipse.equinox.launcher.win32.win32.x86_64_1.1.300.v20150602-1417/META-INF/ECLIPSE_.RSA

22:05:45.291 - INFO:         file info: mode = 0644, size = 6284 bytes

22:05:45.292 - INFO:       Extracting director/plugins/org.eclipse.equinox.launcher.win32.win32.x86_64_1.1.300.v20150602-1417/META-INF/ECLIPSE_.SF

22:05:45.297 - INFO:         file info: mode = 0644, size = 510 bytes

22:05:45.297 - INFO:       Extracting director/plugins/org.eclipse.equinox.launcher.win32.win32.x86_64_1.1.300.v20150602-1417/META-INF/MANIFEST.MF

22:05:45.300 - INFO:         file info: mode = 0644, size = 1103 bytes

22:05:45.300 - INFO:       Extracting director/plugins/org.eclipse.equinox.launcher.win32.win32.x86_64_1.1.300.v20150602-1417/about.html

22:05:45.302 - INFO:         file info: mode = 0444, size = 1445 bytes

22:05:45.302 - INFO:       Extracting director/plugins/org.eclipse.equinox.launcher.win32.win32.x86_64_1.1.300.v20150602-1417/eclipse_1611.dll

22:05:45.479 - INFO:         file info: mode = 0644, size = 58368 bytes

22:05:45.480 - INFO:       Extracting director/plugins/org.eclipse.equinox.launcher.win32.win32.x86_64_1.1.300.v20150602-1417/launcher.win32.win32.x86_64.properties

22:05:45.492 - INFO:         file info: mode = 0644, size = 620 bytes

22:05:45.493 - INFO:       Extracting director/plugins/org.eclipse.equinox.launcher_1.3.100.v20150511-1540.jar

22:05:45.510 - INFO:         file info: mode = 0444, size = 50527 bytes

22:05:45.510 - INFO:       Extracting director/plugins/org.eclipse.equinox.p2.artifact.repository_1.1.400.v20150513-2116.jar

22:05:45.522 - INFO:         file info: mode = 0444, size = 140039 bytes

22:05:45.522 - INFO:       Extracting director/plugins/org.eclipse.equinox.p2.core_2.4.0.v20150527-1706.jar

22:05:45.533 - INFO:         file info: mode = 0444, size = 72151 bytes

22:05:45.533 - INFO:       Extracting director/plugins/org.eclipse.equinox.p2.director.app_1.0.400.v20150423-1455.jar

22:05:45.543 - INFO:         file info: mode = 0444, size = 51443 bytes

22:05:45.543 - INFO:       Extracting director/plugins/org.eclipse.equinox.p2.director_2.3.200.v20150423-1455.jar

22:05:45.552 - INFO:         file info: mode = 0444, size = 103538 bytes

22:05:45.553 - INFO:       Extracting director/plugins/org.eclipse.equinox.p2.directorywatcher_1.1.100.v20150423-1455.jar

22:05:45.630 - INFO:         file info: mode = 0444, size = 33007 bytes

22:05:45.631 - INFO:       Extracting director/plugins/org.eclipse.equinox.p2.engine_2.4.0.v20150511-1532.jar

22:05:45.641 - INFO:         file info: mode = 0444, size = 206643 bytes

22:05:45.641 - INFO:       Extracting director/plugins/org.eclipse.equinox.p2.extensionlocation_1.2.200.v20150423-1455.jar

22:05:45.720 - INFO:         file info: mode = 0444, size = 35136 bytes

22:05:45.721 - INFO:       Extracting director/plugins/org.eclipse.equinox.p2.garbagecollector_1.0.200.v20131115-1210.jar

22:05:45.895 - INFO:         file info: mode = 0444, size = 25061 bytes

22:05:45.896 - INFO:       Extracting director/plugins/org.eclipse.equinox.p2.jarprocessor_1.0.400.v20150430-1836.jar

22:05:45.905 - INFO:         file info: mode = 0444, size = 68216 bytes

22:05:45.905 - INFO:       Extracting director/plugins/org.eclipse.equinox.p2.metadata.repository_1.2.200.v20150428-1613.jar

22:05:45.914 - INFO:         file info: mode = 0444, size = 118253 bytes

22:05:45.914 - INFO:       Extracting director/plugins/org.eclipse.equinox.p2.metadata_2.3.0.v20150511-1532.jar

22:05:45.926 - INFO:         file info: mode = 0444, size = 342666 bytes

22:05:45.927 - INFO:       Extracting director/plugins/org.eclipse.equinox.p2.publisher.eclipse_1.2.0.v20150601-1708.jar

22:05:45.938 - INFO:         file info: mode = 0444, size = 227749 bytes

22:05:45.938 - INFO:       Extracting director/plugins/org.eclipse.equinox.p2.publisher_1.4.0.v20141117-0929.jar

22:05:45.947 - INFO:         file info: mode = 0444, size = 95337 bytes

22:05:45.948 - INFO:       Extracting director/plugins/org.eclipse.equinox.p2.reconciler.dropins_1.1.300.v20150423-1455.jar

22:05:46.033 - INFO:         file info: mode = 0444, size = 48352 bytes

22:05:46.033 - INFO:       Extracting director/plugins/org.eclipse.equinox.p2.repository.tools_2.1.100.v20150423-1455.jar

22:05:46.044 - INFO:         file info: mode = 0444, size = 237689 bytes

22:05:46.044 - INFO:       Extracting director/plugins/org.eclipse.equinox.p2.repository_2.3.100.v20150428-1613.jar

22:05:46.053 - INFO:         file info: mode = 0444, size = 131666 bytes

22:05:46.054 - INFO:       Extracting director/plugins/org.eclipse.equinox.p2.touchpoint.eclipse_2.1.300.v20150423-1455.jar

22:05:46.136 - INFO:         file info: mode = 0444, size = 127923 bytes

22:05:46.137 - INFO:       Extracting director/plugins/org.eclipse.equinox.p2.touchpoint.natives_1.2.0.v20150519-1136.jar

22:05:46.156 - INFO:         file info: mode = 0444, size = 74196 bytes

22:05:46.156 - INFO:       Extracting director/plugins/org.eclipse.equinox.p2.transport.ecf_1.1.100.v20150521-1342.jar

22:05:46.256 - INFO:         file info: mode = 0444, size = 42539 bytes

22:05:46.257 - INFO:       Extracting director/plugins/org.eclipse.equinox.p2.updatesite_1.0.500.v20150423-1455.jar

22:05:46.266 - INFO:         file info: mode = 0444, size = 95080 bytes

22:05:46.267 - INFO:       Extracting director/plugins/org.eclipse.equinox.preferences_3.5.300.v20150408-1437.jar

22:05:46.276 - INFO:         file info: mode = 0444, size = 128643 bytes

22:05:46.277 - INFO:       Extracting director/plugins/org.eclipse.equinox.registry_3.6.0.v20150318-1503.jar

22:05:46.287 - INFO:         file info: mode = 0444, size = 182901 bytes

22:05:46.287 - INFO:       Extracting director/plugins/org.eclipse.equinox.security.win32.x86_64_1.0.100.v20130327-1442.jar

22:05:46.354 - INFO:         file info: mode = 0444, size = 35334 bytes

22:05:46.354 - INFO:       Extracting director/plugins/org.eclipse.equinox.security_1.2.100.v20150423-1356.jar

22:05:46.364 - INFO:         file info: mode = 0444, size = 108521 bytes

22:05:46.364 - INFO:       Extracting director/plugins/org.eclipse.equinox.simpleconfigurator.manipulator_2.0.100.v20150423-1455.jar

22:05:46.429 - INFO:         file info: mode = 0444, size = 25362 bytes

22:05:46.430 - INFO:       Extracting director/plugins/org.eclipse.equinox.simpleconfigurator_1.1.100.v20150423-1455.jar

22:05:46.523 - INFO:         file info: mode = 0444, size = 43279 bytes

22:05:46.523 - INFO:       Extracting director/plugins/org.eclipse.equinox.util_1.0.500.v20130404-1337.jar

22:05:46.761 - INFO:         file info: mode = 0444, size = 77932 bytes

22:05:46.762 - INFO:       Extracting director/plugins/org.eclipse.osgi.compatibility.state_1.0.100.v20150402-1551.jar

22:05:46.778 - INFO:         file info: mode = 0444, size = 241527 bytes

22:05:46.779 - INFO:       Extracting director/plugins/org.eclipse.osgi.services_3.5.0.v20150519-2006.jar

22:05:46.791 - INFO:         file info: mode = 0444, size = 110093 bytes

22:05:46.792 - INFO:       Extracting director/plugins/org.eclipse.osgi_3.10.100.v20150529-1857.jar

22:05:46.813 - INFO:         file info: mode = 0444, size = 1304916 bytes

22:05:46.813 - INFO:       Extracting director/plugins/org.eclipse.update.configurator_3.3.300.v20140518-1928.jar

22:05:46.823 - INFO:         file info: mode = 0444, size = 101014 bytes

22:05:46.824 - INFO:       Extracting director/plugins/org.sat4j.core_2.3.5.v201308161310.jar

22:05:46.836 - INFO:         file info: mode = 0444, size = 362968 bytes

22:05:46.837 - INFO:       Extracting director/plugins/org.sat4j.pb_2.3.5.v201404071733.jar

22:05:46.848 - INFO:         file info: mode = 0444, size = 241956 bytes

22:05:46.848 - INFO:       Extracting director/plugins/org.tukaani.xz_1.3.0.v201308270617.jar

22:05:46.857 - INFO:         file info: mode = 0444, size = 109753 bytes

22:05:46.858 - INFO:       Set package valid

22:05:46.858 - INFO:         Writing registry

22:05:46.859 - INFO:           Wrote 66084 bytes

22:05:46.874 - INFO:     Installing package 'Client Installer'...

22:05:46.876 - INFO:       Set package invalid

22:05:46.876 - INFO:         Writing registry

22:05:46.878 - INFO:           Wrote 74372 bytes

22:05:46.878 - INFO:       Extracting into directory C:\Program Files\SAP\hdbstudio12

22:05:46.878 - INFO:       Extracting install/hdbinst.exe

22:05:46.893 - INFO:         file info: mode = 0755, size = 39424 bytes

22:05:46.894 - INFO:       Extracting install/hdbuninst.exe

22:05:46.908 - INFO:         file info: mode = 0755, size = 39424 bytes

22:05:46.908 - INFO:       copying install/instruntime/DND.dll

22:05:46.908 - INFO:       file info: mode = 0666, size = 61440 bytes

22:05:46.923 - INFO:       copying install/instruntime/Cwd.dll

22:05:46.923 - INFO:       file info: mode = 0666, size = 15872 bytes

22:05:46.938 - INFO:       copying install/instruntime/overloading.pm

22:05:46.938 - INFO:       file info: mode = 0666, size = 1808 bytes

22:05:46.941 - INFO:       copying install/instruntime/lcm_res.tgz

22:05:46.941 - INFO:       file info: mode = 0666, size = 132984 bytes

22:05:46.946 - INFO:       copying install/instruntime/sdbrun.dll

22:05:46.947 - INFO:       file info: mode = 0666, size = 884224 bytes

22:05:46.964 - INFO:       copying install/instruntime/Exporter/Heavy.pm

22:05:46.964 - INFO:       file info: mode = 0666, size = 6551 bytes

22:05:46.967 - INFO:       copying install/instruntime/msvcp100.dll

22:05:46.968 - INFO:       file info: mode = 0666, size = 608080 bytes

22:05:46.987 - INFO:       copying install/instruntime/Dumper.dll

22:05:46.987 - INFO:       file info: mode = 0666, size = 31744 bytes

22:05:47.001 - INFO:       copying install/instruntime/Expat.dll

22:05:47.001 - INFO:       file info: mode = 0666, size = 189440 bytes

22:05:47.015 - INFO:       copying install/instruntime/Wx.dll

22:05:47.015 - INFO:       file info: mode = 0666, size = 2960384 bytes

22:05:47.042 - INFO:       copying install/instruntime/warnings.pm

22:05:47.042 - INFO:       file info: mode = 0666, size = 44896 bytes

22:05:47.049 - INFO:       copying install/instruntime/warnings/register.pm

22:05:47.049 - INFO:       file info: mode = 0666, size = 759 bytes

22:05:47.052 - INFO:       copying install/instruntime/strict.pm

22:05:47.052 - INFO:       file info: mode = 0666, size = 4433 bytes

22:05:47.054 - INFO:       copying install/instruntime/Socket.dll

22:05:47.054 - INFO:       file info: mode = 0666, size = 26112 bytes

22:05:47.067 - INFO:       copying install/instruntime/HiRes.dll

22:05:47.067 - INFO:       file info: mode = 0666, size = 17408 bytes

22:05:47.081 - INFO:       copying install/instruntime/IO.dll

22:05:47.081 - INFO:       file info: mode = 0666, size = 16896 bytes

22:05:47.095 - INFO:       copying install/instruntime/Exporter.pm

22:05:47.095 - INFO:       file info: mode = 0666, size = 18746 bytes

22:05:47.102 - INFO:       copying install/instruntime/Grid.dll

22:05:47.102 - INFO:       file info: mode = 0666, size = 272384 bytes

22:05:47.118 - INFO:       copying install/instruntime/FCGI.dll

22:05:47.118 - INFO:       file info: mode = 0666, size = 44544 bytes

22:05:47.133 - INFO:       copying install/instruntime/LibXML.dll

22:05:47.133 - INFO:       file info: mode = 0666, size = 318464 bytes

22:05:47.148 - INFO:       copying install/instruntime/version/regex.pm

22:05:47.149 - INFO:       file info: mode = 0666, size = 4100 bytes

22:05:47.152 - INFO:       copying install/instruntime/Carp.pm

22:05:47.152 - INFO:       file info: mode = 0666, size = 30355 bytes

22:05:47.158 - INFO:       copying install/instruntime/Win32.dll

22:05:47.159 - INFO:       file info: mode = 0666, size = 39936 bytes

22:05:47.173 - INFO:       copying install/instruntime/SQLDBC.dll

22:05:47.174 - INFO:       file info: mode = 0666, size = 5447168 bytes

22:05:47.194 - INFO:       copying install/instruntime/version.pm

22:05:47.194 - INFO:       file info: mode = 0666, size = 1622 bytes

22:05:47.197 - INFO:       copying install/instruntime/Base64.dll

22:05:47.197 - INFO:       file info: mode = 0666, size = 14336 bytes

22:05:47.210 - INFO:       copying install/instruntime/lcm_pm.tgz

22:05:47.210 - INFO:       file info: mode = 0666, size = 1193410 bytes

22:05:47.219 - INFO:       copying install/instruntime/Encode.dll

22:05:47.219 - INFO:       file info: mode = 0666, size = 29184 bytes

22:05:47.233 - INFO:       copying install/instruntime/vars.pm

22:05:47.233 - INFO:       file info: mode = 0666, size = 2414 bytes

22:05:47.235 - INFO:       copying install/instruntime/wxmsw30u_vc_sdb.dll

22:05:47.235 - INFO:       file info: mode = 0666, size = 15474176 bytes

22:05:47.293 - INFO:       copying install/instruntime/perl522.dll

22:05:47.293 - INFO:       file info: mode = 0666, size = 1544192 bytes

22:05:47.313 - INFO:       copying install/instruntime/Getopt/Long.pm

22:05:47.313 - INFO:       file info: mode = 0666, size = 82447 bytes

22:05:47.321 - INFO:       copying install/instruntime/constant.pm

22:05:47.321 - INFO:       file info: mode = 0666, size = 14724 bytes

22:05:47.328 - INFO:       copying install/instruntime/libxml2.dll

22:05:47.328 - INFO:       file info: mode = 0666, size = 1339904 bytes

22:05:47.345 - INFO:       copying install/instruntime/overload.pm

22:05:47.345 - INFO:       file info: mode = 0666, size = 53339 bytes

22:05:47.352 - INFO:       copying install/instruntime/lcm_pm_ext.tgz

22:05:47.352 - INFO:       file info: mode = 0666, size = 1051392 bytes

22:05:47.360 - INFO:       cannot copy signature manifest file SIGNATURE.SMF: file not found

22:05:47.360 - INFO:       Set package valid

22:05:47.360 - INFO:         Writing registry

22:05:47.362 - INFO:           Wrote 80566 bytes

22:05:47.364 - INFO:     File '*.swidtag' not found under 'D:\IMPORTANT_DOCUMENT\EDU_SOFT_TUTORIAL_CERT\Software\hana studio\HANA Studio 122_11 Windows 64 Bit\SAP_HANA_STUDIO'

22:05:47.367 - INFO:     Running Equinox P2 Director...

22:05:47.367 - INFO:       Starting external program C:\Program Files\SAP\hdbstudio12\director\eclipse.exe

22:05:47.367 - INFO:         Command line is: "C:\Program Files\SAP\hdbstudio12\director\eclipse.exe" -application org.eclipse.equinox.p2.director -installIU "com.sap.ndb.studio.product.base, com.sap.ndb.studio.admin.feature.feature.group, com.sap.ndb.studio.appdev.feature.feature.group, com.sap.ndb.studio.dbdev.feature.feature.group" -repository "file:D:\IMPORTANT_DOCUMENT\EDU_SOFT_TUTORIAL_CERT\Software\hana studio\HANA Studio 122_11 Windows 64 Bit\SAP_HANA_STUDIO\studio\repository" -profile hdbstudio -d

22:05:51.298 - INFO:         Output line 1: Installing com.sap.ndb.studio.product.base 2.3.25.

22:05:51.298 - INFO:         Output line 2: Installing com.sap.ndb.studio.admin.feature.feature.group 2.3.25.

22:05:51.298 - INFO:         Output line 3: Installing com.sap.ndb.studio.appdev.feature.feature.group 2.3.25.

22:05:51.298 - INFO:         Output line 4: Installing com.sap.ndb.studio.dbdev.feature.feature.group 2.3.25.

22:07:42.147 - INFO:         Output line 5: Operation completed in 111440 ms.

22:07:43.466 - INFO:         Program terminated with exit code 0

22:07:43.521 - INFO:     Wrote 80566 bytes

22:07:43.522 - INFO:     InstallRegistry successfully unlocked

22:07:43.522 - INFO:     InstallRegistry closed

22:07:43.470 - INFO:   ---------------------------------------------------------

22:07:43.470 - INFO:   END: Installing SAP HANA Studio (start: 22:05:35.883 duration: 00:02:07.587)

22:07:43.470 - INFO:   ---------------------------------------------------------