Error when creating a new ABAP project

[Former Member]

Hello ADT Gurus,

I'm trying to start using Eclipse for ABAP development. However after successful installation of ADT into Eclipse I'm still not able to create an ABAP project.

When I want to create ABAP project I always receive following error message:

An error has occurred. See error log for more details.

No enum constant com.sap.adt.destinations.model.internal.ISystemConfigurationInternal.OriginType.NUL

Does anyone have an idea, solution, suggestion....advice?

Thank you in advance.

My environment:

Windows 7 Enterprise 64bit

Eclipse Kepler 4.3.2

ADT 2.28.5

SAP GUI 7.30

SAP NetWeaver 7.31 SP8

Regards

Martin

[Former Member]

Hi Martin,

As you mention your environment is fine. There is required minimum configration from server side to enable the elipse base development.

There are 2 possibility for failure of create project.

1) Check with you basis team, All neccessary configraion in place in sap server side.

2) Please check eclipse base development invironment installed correctly in you system with administrative right of you system while installing the eclipse and ADT(.i.e. Install all the eclispe and ADT with administrative right of you PC)

3) It required special authorization to you user id for access to ADT.

Please check the below link http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/d018987d-0417-3110-fd83-9c5f193f2...

[ravi_lanjewar]

Hi Martin,

As you mention your environment is fine. There is required minimum configration from server side to enable the elipse base development.

There are 2 possibility for failure of create project.

1) Check with you basis team, All neccessary configraion in place in sap server side.

2) Please check eclipse base development invironment installed correctly in you system with administrative right of you system while installing the eclipse and ADT(.i.e. Install all the eclispe and ADT with administrative right of you PC)

3) It required special authorization to you user id for access to ADT.

Please check the below link http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/d018987d-0417-3110-fd83-9c5f193f2...

[Former Member]

Hi Ravi,

thanks for your advices.

Nevertheless I've checked your proposals and all look good from my side, so it seems that the problem is still somewhere else...

Most likely it is caused by our new saplogon.ini file which we've recently updated from a "few" local systems to a corporate level list (about 160 systems)

When I switch to the old saplogon.ini, it works normally.

Is anyone aware of any specific saplogon.ini settings which is required for AIE?

Or...Is there any kind of documentation regarding saplogon.ini requirements for AIE?

Thank you in advance.

Regards

Martin

[UweFetzer_se38]

Hi Martin,

are you allowed to edit the saplogon.ini? Would be nice to know whether it's a bug in ADT (too many entries) and/or a false entry in the saplogon.ini which also should be handled in ADT.

Can you delete entries until the saplogon.ini works?

[Former Member]

Hi Uwe,

thanks for your advice.
That's exactely how I proceeded today and at the end found a reason of my error.... yey

There were invalid parameters in section [Origin] of my saplogon.ini file.

See attached screenshot.

According to OSS note 99435 - 'NUL' is not an allowed value.

Those items don't  refer to a SAP systems, they represents only kind of a "separator" between landscapes with a description.

My problem was solved by changing those values to 'USEREDIT' .

Anyway...native SAP logon worked w/o problems even with these invalid entries in saplogon.ini.

Regards

Martin

[UweFetzer_se38]

Good to hear that it works now.

But maybe you should also create an incident (prio "low") in SAP Marketplace regarding this problem. The ADT team is always happy for customer response.