cancel
Showing results for 
Search instead for 
Did you mean: 
Read only

error No host available, all connections are down

Former Member
0 Likes
607

Hi,

Ive read the other threads regarding this same error message. We are currently in the process of migrating sap xmii 11.5 from a test server to a live server. The previous server had xmii run under the default website - the new install is to run under a new website on IIS. If i browse the folder illuminator from the default website (home directory C:\inetpub\wwwroot) the xmii menu page will appear. Doing the same from the new xmii website (home directory C:\inetpub\wwwroot\Illuminator) produces the error page "No host available, all connections are down". The security server is setup as http://<machine name>/LHSecurity and all install instructions were followed. The scripts virtual directory has been created and annonymous access allowed etc. etc.

Have read about creating a new server certificate and importing this into the j2sdk cacerts file, is this relevant as the suppossed entry does not exist on the test server which runs correctly ?

Have noticed under Security Services tab that the link to security Manager is missing when the security server is named http://<machine name>/LHSecurity - and on clicking System Security access is denied with the "No host available, all connections are down " error. Should i change the security server name to http://Localhost/LHSecurity - the link appears and System Security does not produce an error ? Guessing this must be a security setting preventing access ?

Regards,

Emmett O'Connor

Accepted Solutions (0)

Answers (2)

Answers (2)

Former Member
0 Likes

Hi,

Not using https, no content has of yet been migrates as we have been testing the server prior to this.

The security server is http://<machine name>/LHSecurity - but noticed this excludes the security manger link and throws up errors in the system security when set to this as opposed to when i input localhost insted of the machine name. Presuming this has to be some sort of access issue to do with xMII as it returns an error page when trying to run the URL to the default page.

When i run http://<machine name>/LHSecurity from a browser on either the server or remote pc it returns the login page from which i can login - it returns login successful.

Unfortunately don't have access to note 939130 as i dont have the system number at the moment.

Regards,

Emmett

Message was edited by:

Emmett O'Connor

jamie_cawley
Product and Topic Expert
Product and Topic Expert
0 Likes

From the note:

2. Open the Windows IIS Admin page. Find the Scripts folder (Default

location is the Default Web Site folder) and right click on it and goto

properties. From here navigate to the Directory Security tab. Click on

the top Edit button for Anonymous Access, make sure that Anonymous

Access is enabled (the top checkbox next to Anonymous Access must be

checked). Exit out of IIS and close all browsers for this to take

effect.

Also make sure Digest and Basic authentication are NOT checked.

Also check you folder permissions for the Lighthammer, Servletexec-AS and inetpub dir. Make sure the local system account has full control and that is is propagated down to all folders and files.

Also confirm that you don't have any conflicting DNS entries regarding the xMII machine. Pinging the machine locally and from a client should confirm this.

Regards,

Jamie

Former Member
0 Likes

These have all been checked and are set accordingly. Unfortunately same result.

Only difference between this install and the previous test server enviroment, was that the test enviroment - it ran under the default default website, here it is running under its own web site - but even allowing it tio work off the default website produces the same error message.

Regards,

Emmett

jamie_cawley
Product and Topic Expert
Product and Topic Expert
0 Likes

Try using http://<ip address>/LHSecurity for the security server. Restart the servletexec service after the change is made and then attempt to access the login page.

Regards,

Jamie

Former Member
0 Likes

Still no success Jamie, appreciate the help. Have managed to access that note and implemented as said but without success.

Regards,

Emmett

jamie_cawley
Product and Topic Expert
Product and Topic Expert
0 Likes

Did you try logging in with http://<ip address>/Lighthammer

Regards,

Jamie

Former Member
0 Likes

Have tried this - returns the same error message, am i fighting a losing battle ?

Am i correct in saying it has to be an xMII / Security issue when IIS seems to be passing to xMII to take over authentication ?

Regards,

Emmett

Former Member
0 Likes

Emmet,

I am not sure whether you rebooted the server or not.

I got the same message in our server. I tried in several places and I am not sure what the problem is. But I rebooted the server itself. After this every thing went fine.

Thanks,

Srini.

Former Member
0 Likes

Afraid i have Srini,

on several occassions as i have already uninstalled and re-installed the app twice to see if this helped.

Regards,

Emmett

Former Member
0 Likes

This is the full text of the error produced in security system on trying to lauch it, if anyone can throw light on it.

Error. The server encountered an unexpected condition which prevented it from fulfilling the request.

java.io.IOException: No host available, all connections are down

at com.lighthammer.util.HttpConnectionManager.getServerURL(HttpConnectionManager.java:166)

at com.lighthammer.util.HttpConnectionManager.connect(HttpConnectionManager.java:259)

at com.lighthammer.util.HttpConnectionManager.retrieve(HttpConnectionManager.java:242)

at com.lighthammer.cas.client.CASUtil.getList(CASUtil.java:284)

at com.lighthammer.cas.client.CASUtil.getRoles(CASUtil.java:116)

at pagecompile._Admin._PermissionEditor_xjsp._jspService(_PermissionEditor_xjsp.java:111)

at com.newatlanta.servletexec.JspHttpJspPage.service(JspHttpJspPage.java:41)

at com.newatlanta.servletexec.JspServlet.service(JspServlet.java:1036)

at javax.servlet.http.HttpServlet.service(HttpServlet.java:856)

at com.newatlanta.servletexec.SERequestDispatcher.forwardServlet(SERequestDispatcher.java:638)

at com.newatlanta.servletexec.SERequestDispatcher.forward(SERequestDispatcher.java:236)

at com.newatlanta.servletexec.SERequestDispatcher.internalForward(SERequestDispatcher.java:283)

at com.newatlanta.servletexec.SEFilterChain.doFilter(SEFilterChain.java:96)

at com.lighthammer.cms.system.CMSFilter.doFilter(CMSFilter.java:131)

at com.newatlanta.servletexec.SEFilterChain.doFilter(SEFilterChain.java:60)

at com.newatlanta.servletexec.ApplicationInfo.filterApplRequest(ApplicationInfo.java:2159)

at com.newatlanta.servletexec.ApplicationInfo.processApplRequest(ApplicationInfo.java:1823)

at com.newatlanta.servletexec.ServerHostInfo.processApplRequest(ServerHostInfo.java:937)

at com.newatlanta.servletexec.ServletExec.ProcessRequest(ServletExec.java:1091)

at com.newatlanta.servletexec.ServletExec.ProcessRequest(ServletExec.java:973)

at com.newatlanta.servletexec.ServletExecService.processServletRequest(ServletExecService.java:167)

at com.newatlanta.servletexec.ServletExecService.Run(ServletExecService.java:204)

at com.newatlanta.servletexec.HttpServerRequest.run(HttpServerRequest.java:487)

Regards,

Emmett O'Connor

Former Member
0 Likes

Finally figured out this error, was caused pretty much on our own side - we are using http headers due to multiple sites running on the one server. xMII instead of looking at the machine name had to look at the website name so it could find the Security server.

i.e. instead of http://<machine name>\LHSecurity

had to be http://<website http header association>\LHSecurity

fact that it had http:// infront of it should have registered with me but didn't for a while.

Thanks for the input on this.

Regards,

Emmett O'Connor

Former Member
0 Likes

Hi Emmett,

I was wondering if you could give an example of what the "website http header association" entry looks like in you Security Server Editor. I have not seen this before and I am curious

http://<website http header association>/LHSecurity

Very Kind Regards,

Diana Hoppe

Former Member
0 Likes

Diana,

Security entry is exactly as you entered

http://<website http header association>/LHSecurity

i.e http://myxmiiwebpage.xmii.intra/LHSecurity have to hit the IIS website assosiciation and not the actual server name.

Regards,

Emmett

Former Member
0 Likes

Thanks, Emmett. It was the IIS website association that I was interested in seeing, as even though I work with xMII on a daily basis, I don't get to see it from the customer's point of view.

Kind Regards,

Diana

Former Member
0 Likes

Sorry for the late reply Diana,

Basically what was done on the website side of things was :

Under IIS/WebsiteName - properties - website tab - advanced > in here we have setup an assosiciation so that anything hitting the web server IP address most have in its host header the assosiciation implemented here. So anybody wanting to verify against the security aspect of xMII had to got through the web host header (company.website.intra) and not against the machine.

So http://machinename/LHSecurity wasn't finding the security aspect of xMII were as http://company.website.intra/LHSecurity does.

Regards,

Emmett

jamie_cawley
Product and Topic Expert
Product and Topic Expert
0 Likes

Are you using https? If not, then don't worry about the cacerts file.

What directories and content did you migrate? Did you test this prior to migrating the content?

The security server should be http://<machine name>/LHSecurity and not http://localhost/LHSecurity

What happens when you attempt to navigate to http://<machine name>/LHSecurity from a client machine and on the server?

Also check note 939130