Removed components from 7.40 Compilation 2

[former_member213920]

i read this note and downloaded the viewer and editor into a folder, it says to import it into server, but  i get a message " the specified path is not a valid installation server.

i did manage to install the ECL viewer, but it would only install as a patch, when i tried to import it i received the same message as the editor. How do i import the script into the server?

Removed components as of 7.40 Compilation 2: The “Controls for the SAPscript Legacy Text Editor” and the “ECL Viewer” have been removed from the SAP GUI delivery as of 7.40 Compilation 2. See SAP

Note 2192210.

thanks

Larry

[former_member213920]

Jude,

i've since then deleted and recreated the packages from a backup file. i was merely trying to add the component to all my exiting packages, not a stand along installer, was this not the correct thing to do?

thanks larry

[jude_bradley]

Yes it was Larry, that's why it puzzles me why it didn't work as I would expect it to.

If I've time today I'll try a test on a vm to see what happens.

Jude

[Former Member]

Hi Larry,

you must to extract first into a folder.

Example in my case for SAPscript Legacy Text Editor:

SAPSLTESP00_0-70001053.EXE /Extract=C:\test

Now you can import from C:\test

Must also work for ECL viewer.

Regards,

Günther

[jyrki_sderkvist2]

Hi Günther,

I had problem gettng ECL Viewer into SAP Installation Server 9.0.69 from

SAP GUI 7.40 Compilation 2.

Followed your instruction about extracting the first executable for ECL Viewer

ECL70_0-10009623.exe.

After that I could import ECL Viewer product to SAP Installation Server and then patch ECL Viewer

with the remaining ECL-files

Regards,

Jyrki

[reinold_mller]

Hi Jyrki,

but this doesn't install ECL Viewer at the clients.

I also added ECL viewer in the same way to my installation server after upgrade to 7.4 Comp. 2.

I also have ECL Viewer as a component within my installation packages.

After the installation to a client there in no EAI Viewer installed.

I think I'll open an incident at sap support.

Regards

Reinhold

[jude_bradley]

Hello Reinhold

Adding the ECL viewer and pushing out to the clients should work.

Can you attach the most recent nwsapsetup.log file here so we can review it?

Jude

[reinold_mller]

Hi Jude,

please find enclosed last nwsapsetup.log as zipped file attachment.

Regards

Reinhold

NwSapSetup2.txt.zip

[jude_bradley]

Hello Reinhold,

I don't see any errors referring specifically to ECL Viewer here.

There are a few failed dependencies though.

On the installation server "nwsapsetupadmin" tool, can you test by clicking "check server", to make sure you have all the required files present in the installation server?

Thanks in advance,

Jude

[former_member213920]

Thanks Gunther,

I did extract the files and imported them into the server, i updated each of my packages but after that the only thing each of my packages contained was the ECL viewer, all the gui components were gone

thanks

larry 

[Former Member]

Hi Larry,

so the import was successful -OK.

Restart the server delete the package and define it again.

This must work.

Regards

Günther

[former_member213920]

yes, that was one of the first things i did, but when i installed it onto the server and updated my packages, the only thing in all the packages was the viewer.

[reinold_mller]

Hi Larry,

I have the same problem. I hope here is anyone who can help.

Reinhold

[jude_bradley]

Did you check the below link?

https://websmp101.sap-ag.de/~form/handler?_APP=00200682500000001943&_EVENT=LIST&EVENT=LIST&ENR=01200...

If yes, please check

Regards,

Jude

[former_member213920]

Jude,

i got the viewer imported, but, that the only thing each of my packages contained was the ECL viewer, all the gui components were gone after updating my packages (26), installed on about 600 machines...

thanks

larry

[jude_bradley]

Not sure why that happened, Larry.

It should add these components to the existing package,not create it's own standalone.

Did you create a seperate package, or a single-file-installer package?

The sapsetup.log file should throw some light on the subject.