Checked the event viewer, the CMS is giving warnings, and most probably this is the reason for this error:
Unable to contact server XXXSERVER.DashboardsProcessingServer
on machine XXXSERVER.global.internal.AAABBBAAA.com to perform status notification.
Please check the server’s system log for errors.
Unable to contact server XXXSERVER.ConnectionServer
on machine XXXSERVER.global.internal.AAABBBAAA.com to perform status notification.
Please check the server’s system log for errors.
Unable to contact server XXXSERVER.ConnectionServer32
on machine XXXSERVER.global.internal.AAABBBAAA.com to perform status notification.
Please check the server’s system log for errors.
Moderator note:
There are too many topics that are urgent and important to those that started them and to few others. It’s simply impossible to make all those topics sticky in their respective forums.
Marek, I agree,
but take a look and see and there is probably no discussion on this, that has given a complete and full solution to this problem.[/quote]
Execute the following from a command line to create a .keystore file:
:\Program Files (x86)\SAP Business Objects\SAP Business Objects Enterprise XI 4.0\win64_x64\jdk\bin\keytool -genkey -alias tomcat -keyalg RSA
Upon executing the above command, you will be prompted for a keystore password, your full name, organizational unit, organization, city, state and country. At the end, you will be prompted for the keystore password again. This has to be the same password as the password you entered previously. Newer versions of the keytool will prompt you to hit ENTER to keep it the same.
Once finished, a self signed .keystore file will have been created in your user"s home directory:
For example: C:\Users\Administrator
Move this .keystore file from this directory to one in the Business Objects folder structure or any other folder
For example: C:\SSL
Browse to Tomcat’s server.xml file and create a backup file:
For example: C:\Program Files (x86)\SAP BusinessObjects\Tomcat6\conf
Open and edit the server.xml file in wordpad.
Uncomment the section below and add the two commands after keystorePass & keystoreFile. This section needs to reference the new location of the .keyfile and the password you specified when creating it.
<!-- Define a SSL HTTP/1.1 Connector on port 8443
8. Restart Tomcat and it should now be accessible using
https://Servername:8443/BOE/CMC
Hope this helps you.
Suthi
---
**suthijap** _(BOB member since 2011-03-01)_
After configuring SSL certificates on Tomcat and SIA have you checked the following?
Tomcat Configuration:
Modify the JAVA_OPTS for tomcat by editing the bobje/setup/env.sh script and adding the below block of options.
(to find the correct place vi the env.sh file and search for JAVA_OPTS. The first uncommented line should be the correct spot, just go to the end and add the block of options to the end, before the " so that all the options are contained within the quotes.
-Dbusinessobjects.orb.oci.protocol=ssl -DcertDir= -DtrustedCert=cacert.der -DsslCert=servercert.der -DsslKey=server.key -Dpassphrase=passphrase.txt
Alternatively you can modify the setenv.sh script within the tomcat/bin folder. To use this method do the following:
a. under the first line add this line: JAVA_OPTS=$JAVA_OPTS" -Dbusinessobjects.orb.oci.protocol=ssl -DcertDir= -DtrustedCert=cacert.der -DsslCert=servercert.der -DsslKey=server.key -Dpassphrase=passphrase.txt"
b. Add a second line (line 3 of the file) export JAVA_OPTS
c. save and exit the file
Open the Tomcat Administration Panel and Choose the Java Tab, add the following options to the existing JAVA_OPTIONS. Ensure there are no extra spaces at the end of each line: -Dbusinessobjects.orb.oci.protocol=ssl
-DcertDir=
-DtrustedCert=cacert.der
-DsslCert=servercert.der
-DsslKey=server.key
-Dpassphrase=passphrase.txt
Client and IIS Configuration: (This is for situations where the Client or IIS is NOT on the same host used for the process up to this point) a. Obtain the sslconfig.exe from a windows BOE server installation. If you do not have one please contact support and request this file.
b. Place the sslconfig.exe in the folder of the client machine.
c. Open a command prompt
d. cd
e. sslconfig.exe -dir C:/!test -mycert servercert.der -rootcert cacert.der -mykey server.key -passphrase passphrase.txt -protocol ssl
(BOB member since 2009-10-04)
(BOB member since 2009-10-04)
(BOB member since 2003-11-27)
is no argument to make this a sticky ,-) 
(BOB member since 2002-06-20)
(BOB member since 2006-10-05)