[TTCTECH]

I'm having a heck of a problem getting BES to recognize Sametime Messenger as an application.

I searched through all the posts, and still have not found a solution this this.

My procedure:
1) Downloaded SametimeOTA.zip
2) Extracted the files to the BES server's "C:\Program Files\Common Files\Research in Motion\Shared\Applications\Sametime Messenger" folder.
3) Ran "loader.exe/index" from "C:\Program Files\Common Files\Research in Motion\Apploader"
4) Created a Sametime Messenger Application Policy
5) Created a new software Configuration.

This is where it blows up. I can select Sametime Messenger from the right-most column drop-down, but the application does not appear within the Application Name/Application Software section.

The only clue I have is that there doesn't seem to be an ALX file with the OTA version.

Am I simply missing something here?

Thanks

[Jadey]

I have had exactly the same problems - thought I was doing something wrong too! In versions 1 and 2...

I have "fixed" it by using the wired deployment files via BES. Seems to work, and pushes out OTA OK.
I never had ANY problems after that with the "RIM for SameTime" client (as opposed to Domino written app, never used that in production) - this was with version 1.x though, not 2.x. I am having other random problems with 2.x - seems to be making 8310s and 8110s reboot http://www.blackberryforums.com/gene...t-reboots.html

[TTCTECH]

Thanks Jadey,

I tried it with the regular files, same result.

[boma0021]

I still have the same problem see my thread
http://www.blackberryforums.com/bes-...n-showing.html
I hardly blieve that we are the only people with that problem.

[mrrlg]

Glad to see I'm not the only one, still no ALX file in the latest version.

[Jadey]

Wirelessly posted

I've just sorted a T-support contract. As this is the RIM client, I'm hoping I can log this as a support issue. I'll give it a go.

[TTCTECH]

Excellent Jadey,

Please let us know how you make out (OTA pushes are tricky enough without RIM messing with the recipe).

[boma0021]

Jadey,
have you heard anyting from RIM?

[DarthBBerry]

I was experiencing the same problem too recently. Seems as though the SametimeOTA.zip is if you want to deploy via in internal web service. If you use the regular Sametime.zip and create a software configuration, it works normally.

Now if I can only get my device to accept the upgrade and not give me that stupid: "Device State Invalid" message....

[TTCTECH]

Thanks. I finally got it to work using the file "Sametime_Desktop_2.1.10c".

Is there some easy method of telling (via the BES console) when the software configuration has indeed made it to the BB phone?

Thanks

[DarthBBerry]

Originally Posted by TTCTECH

Thanks. I finally got it to work using the file "Sametime_Desktop_2.1.10c".

Is there some easy method of telling (via the BES console) when the software configuration has indeed made it to the BB phone?

Thanks

Under the Configuration Name section You'll see if it was applied successfully.

[Jadey]

My email to RIM
================
I'm having a problem getting BES to recognise SameTime Messenger as an application.

My procedure:

1) Downloaded SametimeOTA.zip from BlackBerry.com
2) Extracted the files to the BES server's "C:\Program Files\Common Files\Research in Motion\Shared\Applications\Sametime Messenger" folder.
3) Ran "loader.exe/index" from "C:\Program Files\Common Files\Research in Motion\Apploader"
4) Created a SameTime Messenger Application Policy
5) Created a new software Configuration.

This is where it blows up. I can select SameTime Messenger from the right-most column drop-down, but the application does not appear within the Application Name/Application Software section.

The only clue I have is that there doesn't seem to be an ALX file with the OTA version - am I simply missing something here?

FYI, during testing: I downloaded the OTA Version 2.0.25, I extracted the file and the SameTime ALX file was missing. So I downloaded the normal version too and copied the ALX File to the OTA Folder. After reindexing - the software was getting to the user device and installed without any errors, only the Icon is not showing up on the BB.

Many thanks and best regards
================


Reply from RIM
================
Thank you for contacting BlackBerry Customer Support. We are pleased to assist you.

The reason why you are not seeing the application listed after you create the Software Configuration is that Sametime Application is not indexing correctly, please check the following. I have included a screenshot that you may find very helpful.

1) Make sure that when you created the directory structure Research In Motion\Shared\Applications is spelled correctly.
2) Create a folder called Sametime and extract the content of the ZIP file into the folder. Make sure that the .alx files are directly under the Sametime folder.
3) Then perform the loader.exe /index. If it index correctly you will see two files PkgDBCache.xml and Specifications.xml.
4) Create the software configuration once again.

If you require further assistance, please don't hesitate to contact us either by replying to this message or by calling us at one of the numbers below.

Thank you again for contacting us.

Have a great day.
================


I've written back, and explained again that no ALX file in the OTA config etc. Will see what they come back with.

[DavidAdams]

Have successfully used the desktop files, all of them, to push the ST client out, left it long enough and sure enough the Manager now shows "Application Status - Up to date".

Didn't use any of the OTA download.

[DarthBBerry]

Jadey,
Download sametime.zip; NOT sametimeOTA.zip.

The OTA does not contain the .alx files. It's for placing the application on an internal web server and telling your users to go there from their devices.

The sametime.zip (without the OTA) has all the correct files.

[TTCTECH]

Originally Posted by DarthBBerry

Under the Configuration Name section You'll see if it was applied successfully.

Do I have to do a search for the app' in question via the Software Config Status tab in BES?

Thanks

[DavidAdams]

Just highlight the user and scroll to the bottom of his details.

[TTCTECH]

Perfect!

Thanks

[noname]

I see what happened here. WE ALL overlooked and use SametimeOTA.zip. See this KB05302 which we all dutifully used for using software configuration to deploy sametime.

BlackBerry Search Results

In it says:
{
Background

Sametime.zip - Used for deployment through a software configuration in BlackBerry Manager
SametimeOTA.zip - Used for deployment through a web site accessed by the BlackBerry® Browser or the customized web page loader.asp
}

Who started it all by using SametimeOTA.zip??? Ha!

[noname]

Originally Posted by Jadey

My email to RIM
================
I'm having a problem getting BES to recognise SameTime Messenger as an application.

My procedure:

1) Downloaded SametimeOTA.zip from BlackBerry.com
2) Extracted the files to the BES server's "C:\Program Files\Common Files\Research in Motion\Shared\Applications\Sametime Messenger" folder.
3) Ran "loader.exe/index" from "C:\Program Files\Common Files\Research in Motion\Apploader"
4) Created a SameTime Messenger Application Policy
5) Created a new software Configuration.

This is where it blows up. I can select SameTime Messenger from the right-most column drop-down, but the application does not appear within the Application Name/Application Software section.

The only clue I have is that there doesn't seem to be an ALX file with the OTA version - am I simply missing something here?

FYI, during testing: I downloaded the OTA Version 2.0.25, I extracted the file and the SameTime ALX file was missing. So I downloaded the normal version too and copied the ALX File to the OTA Folder. After reindexing - the software was getting to the user device and installed without any errors, only the Icon is not showing up on the BB.

Many thanks and best regards
================


Reply from RIM
================
Thank you for contacting BlackBerry Customer Support. We are pleased to assist you.

The reason why you are not seeing the application listed after you create the Software Configuration is that Sametime Application is not indexing correctly, please check the following. I have included a screenshot that you may find very helpful.

1) Make sure that when you created the directory structure Research In Motion\Shared\Applications is spelled correctly.
2) Create a folder called Sametime and extract the content of the ZIP file into the folder. Make sure that the .alx files are directly under the Sametime folder.
3) Then perform the loader.exe /index. If it index correctly you will see two files PkgDBCache.xml and Specifications.xml.
4) Create the software configuration once again.

If you require further assistance, please don't hesitate to contact us either by replying to this message or by calling us at one of the numbers below.

Thank you again for contacting us.

Have a great day.
================


I've written back, and explained again that no ALX file in the OTA config etc. Will see what they come back with.

Can't believe RIM Tech missed 'SametimeOTA.zip"!!!

[Jadey]

I know. Their random naming convention (i.e. file called OTA should not be used for an OTA deployment from BES!) probably has confused their staff.
This was all emailed a few days ago, before I saw the posts from DarthBBerry explaining the file names. RIM will probably come back with the same answer... eventually!