Location : Cleveland, OH
Some users, when attempting to attend a Sametime Meeting, never get connected to the meeting. Instead, they see a screen similar to this:

Restarting the browser doesn't help, neither does using a different browser.
However, there are two TechNotes that will help resolve this issue. The first one, "Java has discovered application components that could indicate a security concern" when attending Sametime classic meeting, will have you apply a hotfix for your version of Sametime. Before you start, you have to determine the version of Sametime you are running. Simple instructions for this can be found here. Once you have the version in hand, the next step is to download the hotfix. Click on the appropriate link on the TechNote. You will then see a screen similar to this:

Once you enter your credentials, a screen similar to this will appear:

Download the hotfix. You can then follow the instructions in the TechNote (with some additional information provided by my experience with these instructions):
1. Stop the Sametime server
2. Backup the following directory:
..Data\domino\html\sametime
3. Copy the contents of the data directory from the zip file into the Data directory on the Sametime server overwriting files which already exist
About the "copy:" Open the ZIP file, copy the files in the separate folders within the ZIP file, DO NOT simply copy the contents of the ZIP file to your Sametime server. If you do, refer back to Number 2, above (I really hope you did a backup before moving along). Each folder in the ZIP file has several files, those are the files you need to copy to your Sametime server, using the folder names as reference to where the files are to be dropped.
4. If the previous step did not overwrite files, the copy was not done to the correct location
5. Edit the the following files:
..\Lotus\Domino\data\domino\html\sametime\stappletver.txt
..\Lotus\Domino\data\domino\html\sametime\strequiredmrcversion.txt
Increment the STMRC_Version_Java2 value in both files.
For example, in the 8.0.2 resigned version (after following Technote 1385734) it is as follows:
STMRC_Version_Java2 = 8.00.02.133
Increment the least significant value by one:
STMRC_Version_Java2 = 8.00.02.134
For the stappletver.txt file, it looks similar to this:

The highlighted line has been incremented by 1, from 8.00.01.64 to 8.00.01.65.
The strequiredmrcversion.txt file looks similar to this:

The only line in this file, above, has been incremented from 8.00.01.64 to 8.00.01.65.
6. Start the Sametime server
The second Technote, "Java has discovered application components that could indicate a security concern" when accessing stlinks, has you changing a Java security setting. Open Control Panel, Java Control Panel. Click on the Advanced Tab. Change the Security - Mixed mode (sandboxed vs. trusted) security verification setting from "Enable - show warning if needed" to "Enable - hide warning and run with protections."

After applying the hotfix, editing two files, and changing your Java Control Panel, all users should now be able to access Sametime Meetings without any issue.
Link: "Java has discovered application components that could indicate a security concern" when accessing stlinks
Link: "Java has discovered application components that could indicate a security concern" when attending Sametime classic meeting
Technorati tag: SnTT Show-n-Tell Thursday

Restarting the browser doesn't help, neither does using a different browser.
However, there are two TechNotes that will help resolve this issue. The first one, "Java has discovered application components that could indicate a security concern" when attending Sametime classic meeting, will have you apply a hotfix for your version of Sametime. Before you start, you have to determine the version of Sametime you are running. Simple instructions for this can be found here. Once you have the version in hand, the next step is to download the hotfix. Click on the appropriate link on the TechNote. You will then see a screen similar to this:

Once you enter your credentials, a screen similar to this will appear:

Download the hotfix. You can then follow the instructions in the TechNote (with some additional information provided by my experience with these instructions):
1. Stop the Sametime server
2. Backup the following directory:
..Data\domino\html\sametime
3. Copy the contents of the data directory from the zip file into the Data directory on the Sametime server overwriting files which already exist
About the "copy:" Open the ZIP file, copy the files in the separate folders within the ZIP file, DO NOT simply copy the contents of the ZIP file to your Sametime server. If you do, refer back to Number 2, above (I really hope you did a backup before moving along). Each folder in the ZIP file has several files, those are the files you need to copy to your Sametime server, using the folder names as reference to where the files are to be dropped.
4. If the previous step did not overwrite files, the copy was not done to the correct location
5. Edit the the following files:
..\Lotus\Domino\data\domino\html\sametime\stappletver.txt
..\Lotus\Domino\data\domino\html\sametime\strequiredmrcversion.txt
Increment the STMRC_Version_Java2 value in both files.
For example, in the 8.0.2 resigned version (after following Technote 1385734) it is as follows:
STMRC_Version_Java2 = 8.00.02.133
Increment the least significant value by one:
STMRC_Version_Java2 = 8.00.02.134
For the stappletver.txt file, it looks similar to this:

The highlighted line has been incremented by 1, from 8.00.01.64 to 8.00.01.65.
The strequiredmrcversion.txt file looks similar to this:

The only line in this file, above, has been incremented from 8.00.01.64 to 8.00.01.65.
6. Start the Sametime server
The second Technote, "Java has discovered application components that could indicate a security concern" when accessing stlinks, has you changing a Java security setting. Open Control Panel, Java Control Panel. Click on the Advanced Tab. Change the Security - Mixed mode (sandboxed vs. trusted) security verification setting from "Enable - show warning if needed" to "Enable - hide warning and run with protections."

After applying the hotfix, editing two files, and changing your Java Control Panel, all users should now be able to access Sametime Meetings without any issue.
Link: "Java has discovered application components that could indicate a security concern" when accessing stlinks
Link: "Java has discovered application components that could indicate a security concern" when attending Sametime classic meeting
Technorati tag: SnTT Show-n-Tell Thursday
Comment posted by Keith Brooks07/28/2010 11:20:46 PM
Homepage: http://www.vanessabrooks.com
I believe this was also caused by a wayward version of Java itself in some cases which was resolved by upgrading yoru java or applying the patch you listed.
There is also a sneaky thing going on where a popup asks if you want to DENY the code from running. It used to say ALLOW and so everyone would click on the first option like always and get the message you showed at the start of the post.
Checking the wording and selecting the appropriate response from the popup may also resolve this issue in some circumstances.
But there are many reasons for meetings not starting.
Powered By : Domino
BlogSphere V1.3.1
Join The WebLog Revolution at BlogSphere.net

















- 