[middlj]

I have installed BES 4.1 (well upgraded from 2.2.6) and I have sametime running at my company (has been for years). I added the IP of the BES to the stconfig.nsf file on the sametime server but my clients are continuting to get the

Service Error (302). Please contact your system administrator if the problem persists.

Error message. Now, I know I'm the system administrator but I'm hoping that someone here can help me, because I have no idea what I'm missing in this who scheme of things. Any help would be greatly appreciated.

[ccollerson]

We had a similar problem when upgrading from 4.0 to 4.1 - we ammended the stconfig.nsf but still got the error, only after restarting the Sametime service on the BES it starting working, i take it this has been restarted?

[middlj]

It was restarted the other day but what I ended up doing was restarting teh BES services as well. Seems to be working fine now. The strange thing was, it would work for some people but not for others. Go figure.

[middlj]

Very strange, I rebooted our BES today and now I'm seeing the same error again. I'm not sure if I'm missing something or what.

[Lamo]

Add the IP address of the BES server to the CommunityConnectivity document on the sametime server under the community Trusted IPS section.

Then restart the BlackBerry Instant Messaging Sametime Proxy service.

[middlj]

Originally Posted by Lamo

Then restart the BlackBerry Instant Messaging Sametime Proxy service.

I'm a bit confused. Should I find this service on the Blackberry server or the Sametime server? I have not installed anything on the Sametime server.

[boma0021]

go to the admin web site of your sametime server, there you will find this section no installation on sametime necessary

[middlj]

Originally Posted by boma0021

go to the admin web site of your sametime server, there you will find this section no installation on sametime necessary

So I'm on the admin site for it but I still don't see it.

The strange thing is, I have added the IP (to the stconfig.nsf file) and rebooted the actual sametime server and the BES an I'm still getting the error. Any other ideas?

[Joseph4200]

bump

I'm having the same issue

[middlj]

Originally Posted by Joseph4200

bump

I'm having the same issue

I was able to resolve this issue. It happened to be that the Collaboration Service had crashed on my BES. But it still said running in my services. A simple stop and start of it fixed my issue.

[tamizha]

Originally Posted by middlj

I was able to resolve this issue. It happened to be that the Collaboration Service had crashed on my BES. But it still said running in my services. A simple stop and start of it fixed my issue.

Yes, this is what I had to do. Thanks much guys.

[mpiggott]

Originally Posted by middlj

So I'm on the admin site for it but I still don't see it.

The strange thing is, I have added the IP (to the stconfig.nsf file) and rebooted the actual sametime server and the BES an I'm still getting the error. Any other ideas?

I'm at the same point as above. Any other ideas?

[mpiggott]

Originally Posted by Lamo

Add the IP address of the BES server to the CommunityConnectivity document on the sametime server under the community Trusted IPS section.

Then restart the BlackBerry Instant Messaging Sametime Proxy service.

Well that fixed it for me. I don't know anything about the Sametime Proxy Service. I restarted the sametime server after adding the BES to the Community Trusted IP section and everything works great. Hope this helps someone.