[gverhoeven]

Hi guys,

If I try to logon to the Blackberry Administration Service IE will reply with a 'HTTP Error 404 - File or directory not found.' error message.

I searched on the web for a solution, but didn't succeed.

It's a new BES 5.1 installation. The error message in the BBAS-AS log file is:

(07/09 15:29:27:531):{main} [org.apache.coyote.http11.Http11Protocol] [INFO] Initializing Coyote HTTP/1.1 on http-APPLICATION.EHP.CORP%2F10.0.0.2-18180
(07/09 15:29:27:562):{main} [org.apache.coyote.http11.Http11Protocol] [ERROR] Error initializing endpoint
java.io.EOFException

There are a lot of people having these problems. But on the web I can't find anyone who has this problem.

Normally there should be a message like:

java.net.BindException: Address already in use: JVM_Bind:443

I run MS Exchange 2003 on the same server.

Maybe you could help me out.

Thanks

[gverhoeven]

Thinking........

Does anyone know if BES can be installed on a Exchange Server which has rpc over https installed?

[noname]

Click this and go get KB18185, which will leads you to KB18175.

Let me google that for you

[gverhoeven]

That's the problem, I don't get the JVM_Bind:443 error.

This is the error I got:

(07/09 15:29:27:531):{main} [org.apache.coyote.http11.Http11Protocol] [INFO] Initializing Coyote HTTP/1.1 on http-APPLICATION.EHP.CORP%2F10.0.0.2-18180
(07/09 15:29:27:562):{main} [org.apache.coyote.http11.Http11Protocol] [ERROR] Error initializing endpoint
java.io.EOFException

[gverhoeven]

I have multiple IP addresses all on the same NIC. BES is taking the lowest numbered Address, instead of the default (first) IP address under Network Properties.

Can this be this issue? Is there a way to get BES binding to my primary IP 10.0.0.10

[illy]

i have a 100% identical issue over here, as described in the first post, but cannot find the cause of it :(
did anyone succesfully resolve this?

[goldsmith81]

I have been having this same issue for about a month. The error that I am getting is the same in the original post.

Please help!!

[gverhoeven]

I have resolved this issue. But first I need to explain my hardware configuration:

There where two NIC's:

WAN with 2 IP addresses
LAN with 1 IP address

I've change my primary NIC from WAN to LAN.

Google on 'change primary NIC' and you will find some procedures (I'm not able to post links or images)

I've also changed the HTTPS service port to 663 because OWA was using 443.

The last thing you need to check is the DNS configuration.
In my case I couldn't access the Administration Service with the fqdn. By changing the fqdn:443 with the primary IP address (in my case 172.16.254.111:663) I could access it, and the problem was solved.

Hopefully this will help others solving this problem.

[jjbova]

Awesome find. Just out of curiosity, are you guys short on servers? Why are you teaming up the NICs in that way?