[benexp]

does replacing these files require a service restart or server restart in order to take effect?

[JSylvia007]

I replaced both files, and restarted the whole server, and I still see the errors. Both are for Bolds...

[H.Nayl]

Anyone get these to stop? I'm seeing the same thing as well for bold only users.

[dvscool]

Updating device.xml doesn't resolve this issue as you can see at the start of this post.

admins who are getting this error. Are you running SP6?

I would like to try that shortly.
Glad I'm not the only one with this issue.

[benexp]

Im running SP6.

Full version is 4.1.6.9

[JSylvia007]

Wirelessly posted (Bold 9000 (AT&T))

Same here as Benexp. Have updated the vendor and device xmls. Still issues. Here too.

[dvscool]

Has anyone spoken with RIM? I will be doing that if necessary I guess, but would rather not.

[JSylvia007]

I just opened a ticket with my TSupport on the website. I'll let everyone know when I get a response.

[JSylvia007]

TSupport told me to replace the Device.XML file... already done, did a DIFF on both files, they are the same as the one RIM lists in KB13589.

I've updated the call and am awaiting their next response.

~Jake

[dvscool]

cool thanks for the update.....

[JSylvia007]

well gentlemen... we've uncovered new ground. This is NOT a BES issue, so i'm told. It's an issue with SRP at RIM.

Show of hands... Who is using a BOLD with an OS other than the one supplied by your carrier? Please post stats and details:

# of BOLDS on BES: 4
# running Different OS Version: 2
Carrier: AT&T
Carrier Version: .167
Other Versions: .190

[JSylvia007]

Okay, looks like we may have a solution. Please see below:

I have researched the warning message that is coming up in the application log for your users that have a BlackBerry Bold. That particular message indicates WIFI traffic. It is not going to cause an issue with your BlackBerry Enterprise Server. This often comes up if you have enabled WIFI enterprise activation in your environment. To determine if this is the case, you can verify by doing the following:

1) On the BlackBerry Enterprise Server go to start/programs/BlackBerry Enterprise Server. Select BlackBerry Server Configuration.
2) Within the BlackBerry Enterprise Server Configuration, select the OTA WIFI activation tab. If any of the top two boxes are checked, uncheck them if you do not want permit WIFI activations.

This issue has been addressed in the newest BlackBerry Enterprise Server version.

Trying it now.

[dvscool]

I don't have those boxes checked....they never have been

[JSylvia007]

Me either... Back to the drawing board. I am running BES 4.1.6 MR2 and neither of those boxes were checked.

~Jake

[dvscool]

could it be that due to new features on the bold this SHOULD be enabled?

[JSylvia007]

Actually, now that i'm running MR2, these might have disappeared... I'll keep watch and update.

Edit...

Nope... Still happening...

[cavy]

yup i just went to 4.1.6 MR2 today and its still happening for me and the other bold users. I don't see it causing any ill effects though as mine is working fine. Just don't like seeing errors.

[JSylvia007]

Good News Finally! I just received this from RIM:

Hello Jacob,

I just wanted to send you an email providing you an update to this case. This case was created because you were seeing the following warning message in the application/router logs:

"The description for Event ID ( 20000 ) in Source ( BlackBerry Router ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: [DEVICE_SRP:24A1C01E:00d48008] Receive_UNKNOWN, VERSION=2, CMD=241."

After further investigation and testing, this turns out to be an issue with our software. What this warning is a result of is users utilizing WIFI to connect to the BlackBerry Enterprise Server as opposed to the mobile network. Users are still able to utilize WIFI without issue. What is generating this warning is when a user switches to WIFI a configuration status change is sent to the BlackBerry Infrastructure to let it know that is now utilizing WIFI as opposed to the mobile network. In turn, the BlackBerry Infrastructure sends that configuration status change to the BlackBerry Enterprise Server. This is where the break down occurs. The BlackBerry Enterprise Server doesn't understand that configuration status change and that is where the warning is generated. Please note, the configuration status change is informational only and that is why users are still able to utilize WIFI to perform tasks utilizing the BlackBerry Enterprise Server. This issue has been passed along to development to investigate and correct in a future release. Once a SDR has been created I will contact you back again to provide that. Thank you for your patience in this matter.

[dvscool]

Thats nice to hear.

I opened a ticket with RIM as well on this issue, and they were having me do all sorts of crazy things, (formatting devices, looking at permissions). all of which I knew was not the issue.

In my opinion, BES spits out too many warnings to begin with.

[IAmTheAllspark]

Hey Jacob,

Did RIM ever get back to you with an SDR number?