cancel
Showing results for 
Search instead for 
Did you mean: 

SLD configuration error: No host name and HTTP port defined in Exchange Profile for sld

Former Member
0 Kudos

Dear all,

after an upgrade to EP 7.4 SP11 Im getting a cyclic error in portal logs, obviously related to SLD config:

indeed, due system landscape data supplier config all seems to be ok and pinging of appropriate destinations resp sending test data to SLD works well :

We didnt had this issue before upgrade and also didnt change the SLD config afterwards. Also, we have controlled needed destinations and user on SLD resp portal, all seems to be ok so far. I cant find any clues on this on the marketplace or SCN, excepting some pointers to missing SLD config e.g. from my good PI colleague https://scn.sap.com/people/j%C3%B6rgthiesman. But this doesnt seems to be the Problem, any ideas? Thanks,

cheers

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos
hemanth2
Product and Topic Expert
Product and Topic Expert
0 Kudos

Dear Lawrence,

Hope you are doing good.

Is it possible to attach the default trace so that we can check this further. Most likely some XI related configuration is missing..


Hope this helps.

_ _ _ _ _ _ _ _ _

Kind Regards,

Hemanth
SAP Active Global Support

_ _ _ _ _ _ _ _ _

Former Member
0 Kudos

Hi Hemanth,

thank you for your friendly support, Im attaching appropriate trace sequence for you. Since it seems to be a periodic task, this one occurs in 5 min interval. Also: we noticed if we provide admin role for guest user, all exceptions are gone excepting the one I attached a screenshot for in my entire post. Not sure why he is trying to use guest at all, since in fact the user maintained on appropriate destination should be used, as far I got it. Thanks,

cheers

Former Member
0 Kudos

Meanwhile I tool a look to XPI Configuration Service in NWA and have the suspicion appropriate config entries could be wrong, since URL's are showing to the local machine without using FQDN e.g.:

But I cant find any portal related documentation on configuration, could somebody point me to please? Thanks,

cheers

hemanth2
Product and Topic Expert
Product and Topic Expert
0 Kudos

Dear Lawrence,


Thank you for the file.

Please see sap note 2198240 - No host name and HTTP port defined in Exchange Profile ; this is the exact issue that you are facing.


Hope this helps.

_ _ _ _ _ _ _ _ _

Kind Regards,

Hemanth

Former Member
0 Kudos

Thanks Hemanth, seems this is it. Strange is, Im pretty sure to have search for "SLD configuration error: No host name..." on the marketplace, but havent seen the 2198240, must have done something wrong or the search index is updatet meanwhile.

However, Im not able to find com.sap.aii.ib, is this one CE-specific and isnt available on EP systems? Indeed Applications->ExchangeInfrastrucutre is there and can be set to "Fatal". Im assumung its kicking following exception, which is still coming even after reconfiguring the XPI service:

Indeed, as far I got it in generally, this KB article is not EP-specific. We still dont understand why this service is there at all, and why we have to set those configuration to CE. My customer dont likes the idea of handling issues through setting trace level's up at all, and imho they are right. Also, as we found out the wrong service setting is already configured on pre-upgrade EP Systems (7.31). The trace entries mentioned in the note never occured on those.

Hemanth, we really would like to understand what the stuff is good for and how to configure it properly on EP. Due my logic, the trace entries didnt had any effect on SLD feedbacks, do we need it at all? Since there are obviously no practical consequences if it runs properly or not, maybe we should simply put it off? Is there  any EP-specific documentation on this? I hope you can help us on this, thank you very much,

cheers

hemanth2
Product and Topic Expert
Product and Topic Expert
0 Kudos

Dear Lawrence,


The only reason i can think of is that there are remnants of old components (cause if you are using a EP only server with no PI applications/usage type, then this does not make much sense in your landscape).
Perhaps if you are sure about this, you can deactivate (set it to fatal/none etc.)

From just an EP point of view, if the server connects to the SLD fine, then the related links should work; the exchange profile kind of setting does not make much sense

Hope this helps.

_ _ _ _ _ _ _ _ _

Kind Regards,

Hemanth

Former Member
0 Kudos

Thank you very much Hemanth, I forwarded your statement to our management resp. BASIS and PI colleagues. My two cents on this after all are:

1.)after consulting with our PI responsible, he never noticed a necessity for mentioned XPI service on any other AS Java machine excepting PI itself. We took a look into wide AS Java EP landscape of our customer and have found this one on all EP's, independently from stack characteristic, stand or choosen installation scope (also on my local EP 7.4 SP9 e.g.). My colleagues from PI resp BASIS are supposing the presence of XPI on non PI AS Java stacks is a packaging error. I have the same suspicion, but can neither confirm nor deny this assumption, since we are not able to get an official statement on the purpose of this service infrastructure on an EP or find any documentation on that. My PI colleague pointed me to PI-specific documentation for XPI service infrastructure, which we have seen already and is not applicable for an EP

2.)The management of our customer is not gone wild about disabling logs as a way to solve an issue, to say it in a gentle way. Due my customer such kind of "corrections" does not really confirm them in using EP as a plattform, in addition trusting in SAP as reliable and quiality-conscious software supplier. However, since I wasnt able to offer an other solution, the logs for ExchangeInfrastrucutre are off now and the default trace clean


Hemanth, thank you again for your friendly and contemporary support, I really appreciate it.


cheers

hemanth2
Product and Topic Expert
Product and Topic Expert
0 Kudos

Dear Lawrence,

Yes, I do understand the predicament. The issue is that components (or SCAs) like "messaging" etc., which are traditional XI components, are now part of a standard SAP server with usage type AS JAVA. This can lead to some issues like this.
Is it possible that you send across the system info so that we can check the deployed components.

Navigate to http://<server>:<port>/nwa/sysinfo

-> navigate to component info-> software components

-> export to Spreadsheet.

Hope this helps.

_ _ _ _ _ _ _ _ _

Kind Regards,

Hemanth

Former Member
0 Kudos

Hemanth, Im attaching the sys info of my local VM. Thanks,

cheers

hemanth2
Product and Topic Expert
Product and Topic Expert
0 Kudos

Dear Lawrence,

Thank you for that. As suspected, this is not an XI installation. Core XI components like XI adapter framework, XI tools etc are missing. As mentioned earlier, because Messaging etc. are available in the latter releases, it is somehow interfering with the settings. I will try to report this to the XI team and perhaps they can check this as well.
However, presently, you can go ahead with the plan that is in place to avoid this error.
Regards,
Hemanth

Former Member
0 Kudos

Thank you Hemanth, as I noticed the responsible person seems to have introduced an error correction with the note 2217231 resp. source code amendment

cheers

Answers (0)