Application Development Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Showing results for 
Search instead for 
Did you mean: 

ADT on Windows Server 2012 Standard?

former_member182411
Active Participant
0 Kudos

Hi ADT-Team,

we are working with the latest AS ABAP Trial version 7.40 deployed in AWS and try to access it by ADT. Our client is an AWS instance based on Microsoft Windows Server 2012 Standard. We installed SAP HANA Studio provided by the trial version. On top of this we installed ADT into the HANA Studio as recommended in the tutorial video.

When HANA Studio is started we receive an error concerning ADT and JCO3. Is this a known issue?

ABAP communication layer is not configured properly. This might be caused by missing Microsoft Runtime DLLs VS2010. Consult the installation guide or download page for further details on how to install this component.

We tried to reinstall the mentioned MS runtime DLL but did not solve this issue, even re-installing HANA Studio was not helpful. The complete stack trace can be found in the document attached.

Has anyone had the same problem?

Thx in advance for your help,

Martin

3 REPLIES 3

former_member182411
Active Participant
0 Kudos

Hi again,

it has got to do with the used operating system. Installing Eclipse with ADT on Windows Server 2008 RC8 works fine.

Are there any plans to release ADT for Win Server 2012?

Thx in advance,

Martin

0 Kudos

Hi,

I realize this is an old thread. But just wanted to share that we are running HANA Studio 97.02 on Win Server 2012 R2 (even though it is not on the PAM yet).

It requires a few mods: It is necessary to manually specify the OS during the installation (using a flag) and you have to make sure it does not use IPv6 when connecting to the database (set param in .ini file).

Best regards
Tommy Baunwall

former_member186216
Active Participant
0 Kudos

Hi Martin,

please have a look at this support note:

https://service.sap.com/sap/support/notes/2041195

Best regards,

Marco