BlackBerry Forums Support Community

BlackBerry Forums Support Community (http://www.blackberryforums.com/)
-   BES Admin Corner (http://www.blackberryforums.com/bes-admin-corner/)
-   -   BES Problem and Migration (http://www.blackberryforums.com/bes-admin-corner/101849-bes-problem-migration.html)

Urlryn 10-26-2007 10:12 AM

BES Problem and Migration
 
Greetings all!

Little background here on my existing BES.

Inherited a single standalone from a pervious admin (aren't we all so lucky! :smile: )
This box has been upgraded and tinkered with since stoneages like version 2x.

Current Version is: 4.1.0.38 MSDE: 2000.86.1830.0
Database Name: BESMgmt

Last upgrade attempt prior to me inheriting it was moving the server from 4.1.0.38 to 4.1.4. This failed and was restored from backup. Second attempted failed and again restored.

The box is currently having lots of problems with the OS and Blackberry.
example:
Having to restart BB services or the server 2-3 times a day
Reinstalling the BES Mgr 4.1 on a laptop/desktop generates a error when trying to connect to it to the old server database. The error basically states that I need to upgrade to the latest version of the BES Mgr software. Downloaded the current version on Blackberry/RIM website. I got the Same error. Tried several different version. Users that already have the software installed are not affected. Just if we have to reinstall we can't.

So time to get rid of this old dog!

Plan A
First I built a second blackberry server up to 4.1.0.38 to match the existing one. Then attempted to link them together so I could just migrate the users over to the new server.

But no matter what I tried I couldn't get them to see each other or link the new server to the old server database. When I attempted to connect to the old BES database I would get error stating that the Database was a PRE 4.0 database?

How can the database be Pre 4.0 when it was upgraded to 4.1?
Is there a way around this just to get the users to the new server?

Plan B
Build a second blackberry server up to the latest version. And pray there is a utility or some way to migrate all 550 worldwide users to the new server without having to reactivate every blackberry?

Thank you

amukhey 10-26-2007 01:42 PM

Is this in Notes or exchange?

Urlryn 10-26-2007 01:53 PM

Its in a exchange enviroment!

hdawg 10-26-2007 03:11 PM

Quote:

Greetings all!
Greetings, salutations,and YO!

Quote:

Little background here on my existing BES.
Always a good thing ... I'm feeling spunky this afternoon so I'll reply to everything you've listed ... even if it is a bit off topic and I get on a rant about bananas or beer on a Friday afternoon while working :razz:

Quote:

Inherited a single standalone from a pervious admin (aren't we all so lucky! :smile: )
At least you've got BES now! It rules!

Quote:

This box has been upgraded and tinkered with since stoneages like version 2x.
In fact that would be prior to the stoneages ... you're prehistoric.

Quote:

Current Version is: 4.1.0.38 MSDE: 2000.86.1830.0
Database Name: BESMgmt

Last upgrade attempt prior to me inheriting it was moving the server from 4.1.0.38 to 4.1.4. This failed and was restored from backup. Second attempted failed and again restored.
That is odd. 4.1 upgrades should really have no problem going to 4.1.4.

Quote:

The box is currently having lots of problems with the OS and Blackberry.
example:
Having to restart BB services or the server 2-3 times a day
Reinstalling the BES Mgr 4.1 on a laptop/desktop generates a error when trying to connect to it to the old server database. The error basically states that I need to upgrade to the latest version of the BES Mgr software. Downloaded the current version on Blackberry/RIM website. I got the Same error. Tried several different version. Users that already have the software installed are not affected. Just if we have to reinstall we can't.
Well ... you need to run the same version of BB Manager that your BES is running. Different versions (or service packs) running together aren't supported / won't work. If you're downloading 4.1.4 and running it against 4.1 that would be an issue.

Quote:

So time to get rid of this old dog!
NO NO NO NO NO!!!! Just teach it some new tricks :)

Quote:

Plan A
First I built a second blackberry server up to 4.1.0.38 to match the existing one. Then attempted to link them together so I could just migrate the users over to the new server.

But no matter what I tried I couldn't get them to see each other or link the new server to the old server database. When I attempted to connect to the old BES database I would get error stating that the Database was a PRE 4.0 database?

How can the database be Pre 4.0 when it was upgraded to 4.1?
Is there a way around this just to get the users to the new server?
A reasonable plan. You got a new SRP key I take it? Connecting to the MSDE database remotely can be tricky ... did you configure proper network access on the MSDE server? A phased migration.

Quote:

Plan B
Build a second blackberry server up to the latest version. And pray there is a utility or some way to migrate all 550 worldwide users to the new server without having to reactivate every blackberry?
Ahhh, a knife edge. (or spork edge if you're feeling sassy)

I'm going to recommend you go with plan C. Since you inherited this and you really don't know exactly what is going on (and not to be mean, but you don't appear to have a heck of a lot experience with BES ... not to worry, the more you play the more you'll learn) ... I would break down and call RIM for support during the upgrade.

Check the forums here for phased migration and knife edge ... also check out BlackBerry Technical Solution Center for the knowledgebase articles. Then with some specific questions we can help out here and address each point one at a time.

Good luck!

amukhey 10-26-2007 04:10 PM

Couldnt have said it better hdawg!

Urlryn 10-31-2007 02:23 PM

well one question left unanswered! :D

When attempting to configure the new BES to connect with the current BES it responds with this error message:
The database already exxists and is a pre 4.0 database. Updating pre 4.0 database is not supported. Delete the database and retry or manually update it.

The current BES was upgraded from 3x to 4.1. So I shouldn't be seeing a error of the database being Pre 4.0?

If there is a issue with the database...are there any type of utilities for diagnosing and fixing these types of issues?

I do believe i'm using the exact same version of the software the current BES is using.

Urlryn

hdawg 10-31-2007 02:47 PM

It looks like your database may have been already upgraded to 4.1 SP2 ...

On the BES perform this at a command prompt:

osql -E -d BESMgmt -Q "select *from serverdbversion" > C:\1.txt

and paste the contents of 1.txt

Urlryn 10-31-2007 04:02 PM

CurrentVersion CreateDateTime BuildDateTime Id
-------------------------------- ----------------------- ----------------------- -----------
0.0.403 2000-01-01 00:00:00.000 NULL 1
4.0 2006-02-20 16:04:48.143 2004-10-15 00:00:00.000 2
0.0.401 2000-01-01 00:00:00.000 NULL 3
0.0.402 2000-01-01 00:00:00.000 NULL 4
0.0.403 2000-01-01 00:00:00.000 NULL 5
4.0 2006-02-21 14:58:54.833 2004-10-15 00:00:00.000 6
0.0.401 2000-01-01 00:00:00.000 NULL 7
0.0.402 2000-01-01 00:00:00.000 NULL 8
0.0.403 2000-01-01 00:00:00.000 NULL 9
4.0 2006-02-21 15:10:33.333 2004-10-15 00:00:00.000 10
0.0.404 2000-01-01 00:00:00.000 NULL 11
0.0.401 2000-01-01 00:00:00.000 NULL 12
0.0.402 2000-01-01 00:00:00.000 NULL 13
0.0.403 2000-01-01 00:00:00.000 NULL 14
0.0.404 2000-01-01 00:00:00.000 NULL 15
4.0 2006-02-27 14:55:07.200 2004-10-15 00:00:00.000 16
0.0.401 2000-01-01 00:00:00.000 NULL 17
0.0.402 2000-01-01 00:00:00.000 NULL 18
0.0.403 2000-01-01 00:00:00.000 NULL 19
0.0.404 2000-01-01 00:00:00.000 NULL 20
4.0 2006-02-27 15:01:32.550 2004-10-15 00:00:00.000 21
4.1 2006-03-24 19:57:18.987 2006-01-30 00:00:00.000 37
4.1.2 2007-07-13 15:10:19.617 NULL 38
4.0 2004-11-30 20:54:58.820 2004-10-15 00:00:00.000 22
0.0.401 2000-01-01 00:00:00.000 NULL 23
0.0.402 2000-01-01 00:00:00.000 NULL 24
0.0.403 2000-01-01 00:00:00.000 NULL 25
0.0.401 2000-01-01 00:00:00.000 NULL 26
0.0.402 2000-01-01 00:00:00.000 NULL 27
0.0.403 2000-01-01 00:00:00.000 NULL 28
4.0 2006-02-20 15:56:50.657 2004-10-15 00:00:00.000 29
0.0.401 2000-01-01 00:00:00.000 NULL 30
0.0.402 2000-01-01 00:00:00.000 NULL 31
0.0.401 2000-01-01 00:00:00.000 NULL 32
0.0.402 2000-01-01 00:00:00.000 NULL 33
0.0.403 2000-01-01 00:00:00.000 NULL 34
0.0.404 2000-01-01 00:00:00.000 NULL 35
4.0 2006-02-27 14:58:15.187 2004-10-15 00:00:00.000 36
(38 rows affected)

Urlryn 11-05-2007 10:59 AM

So what does this tell us hdawg?


Also I am thinking of moving to a SQL database rather then the local MSDE.
Is there someplace I can read up on best practices, procedures and/or Pros/cons of using SQL vs MSDE?

hdawg 11-05-2007 11:59 PM

Quote:

Originally Posted by Urlryn (Post 728692)
So what does this tell us hdawg?


Also I am thinking of moving to a SQL database rather then the local MSDE.
Is there someplace I can read up on best practices, procedures and/or Pros/cons of using SQL vs MSDE?

sorry for the delay ... been traveling (still am) ... it shows that your DB Schema is already at 4.1.2 so you'll need to use that installer.

4.1.2 2007-07-13 15:10:19.617 NULL 38 ... July 13th ring a bell?

If you search here or at BlackBerry Technical Solution Center for MSDE to SQL or migrate SQL MSDE you'll find lots of info ... Do you already have an SQL server? Cost and network reliance on a potentially shared resource are the only downsides to full blown SQL.

Urlryn 11-06-2007 08:49 AM

Ok so now that i fully know that the database is 4.1.2 I can attempt to upgrade to 4.1.3 then 4.1.4. Question is the Pre 4.0 error.
That error is being generated cause I maybe using a older/newer version thats not compatible to the current BES?

Yep! We pretty much have a nice cluster of SQL Servers for various applications and such. So that won't be an issue to switch over.

I'm more concerned about performace changes, disaster recovery and just plain adding additional BES to the enviroment with more ease down the road.

Thanks Hdawg!

Urlryn

hdawg 11-06-2007 04:15 PM

Don't do 4.1.3, just do 4.1.4 (and then apply MR2 - Maintenance Release 2) ... all service packs are inclusive of all prior service packs.

BES isn't very SQL intensive, but it does require regular and responsive communication with SQL. BES Services won't start unless it can reach the SQL database (hence why moving it remotely is somewhat of a risk), but the SQL server can go down and mail will still continue to flow within the BES environment.

Definitely moving to SQL now will help when you go forward and add more BES servers.

Urlryn 11-07-2007 10:56 AM

Great! Thank you for all the help Hdawg!

Its been very appreciated!

Urlryn

Urlryn 11-22-2007 04:33 AM

Welp got the new server up and running. All patched and updated to 4.1.4.
Switched the database from MSDE to SQL with out a hitch.

Was able to move users over to the new server with no problems at all.

I started with myself then the IT department and this sunday the rest of the company. Couple problems are being reported:

1. If someone is replying to a email, they are failing or saving as drafts only.
2. Lookup feature just doesn't work: I've tried 3 lookups and its each time it just sat there doing nothing. I let the lookup run for roughly an hour on my blackberry without touching it.

Did I miss something configuration wise on the new BB server?

Urlryn

hdawg 11-22-2007 06:22 AM

Quote:

Originally Posted by Urlryn (Post 748287)
Welp got the new server up and running. All patched and updated to 4.1.4.
Switched the database from MSDE to SQL with out a hitch.

Was able to move users over to the new server with no problems at all.

I started with myself then the IT department and this sunday the rest of the company. Couple problems are being reported:

1. If someone is replying to a email, they are failing or saving as drafts only.
2. Lookup feature just doesn't work: I've tried 3 lookups and its each time it just sat there doing nothing. I let the lookup run for roughly an hour on my blackberry without touching it.

Did I miss something configuration wise on the new BB server?

Urlryn

Is this only with messages that were already on the device prior to the ugprade? e.g. They have no problems creating new mail or replying to mail received since the upgrade?

Its possible that service books have become corrupted ... if you resend service books to a given device, perform a soft reset on the device, and then attempt to perform an address lookup does it still fail? Can you check the MAGT log for anything associated with that user at the time that you performed the lookup to look for an error?

DarkWater 11-22-2007 07:12 AM

Sort of along the same lines a hdawg's thinking.

When you go to Compose Email, is it giving errors saying "No message services found. You will only be able to save a draft"

If this is what you meant when you mentioned drafts, then yeah the service books are damaged or flat out missing.

Urlryn 11-22-2007 09:28 AM

When using the Lookup feature..it just sits there at [Looking up: Persons Name] and does nothing. I let it sit there for nearly 2 hours and never changed or generated a error on the blackberry device itself.

I did resend the IT policy and Service book last night after I noticed this problem on my blackberry. I am trying to soft reset now.

Urlryn 11-22-2007 10:01 AM

Ok soft boot didn't do anything.

So went ahead and did a hard reboot.

I'm able to lookup some names and not others. Most of the time it just sits there forever other times it will say failed.

My Reconcile button keeps vanishing. I resend service book and it reappears. I use it once and its gone.

Mail read on blackberry isn't updating outlook
Mail Deleted in Outlook isn't being deleted on Handheld.

Sounding like maybe need to reload the handheld?
But if this starts happening to everybody i do not want to reactivate everybody! =)

Downloading the logs to my computer to see if anything is in there. Is there anything specific I should be looking for?

Urlryn

Urlryn 11-22-2007 12:36 PM

Server1 = BEServer
Server2 = Blackberry (new one)


MAGT Log:

[40000] (11/22 00:00:16.597):{0xF80} [BIPP] Received datagram, Tag=16800
[40700] (11/22 00:00:16.597):{0xCCC} {urlryn@mydomain.com} Receiving packet from device, size=41, TransactionId=-1915297221, Tag=16800, content type=CMIME, cmd=0x3
[40698] (11/22 00:00:16.597):{0xCCC} {urlryn@mydomain.com} Receiving OTAFM request from device, Tag=16800, TransactionId=-1915297221
[30198] (11/22 00:00:16.597):{0xCCC} {urlryn@mydomain.com} Received OTAFM_CONFIG_REQUEST from device
[30197] (11/22 00:00:16.597):{0xCCC} {urlryn@mydomain.com} Sending OTAFM_CONFIG to device, ServerSupport=207, UserConfig=63, Conflict=1
[40583] (11/22 00:00:16.597):{0xCCC} {urlryn@mydomain.com} Sending packet to device, Size=48, Tag=21469, TransactionId=-951824489
[40279] (11/22 00:00:16.597):{0xCCC} {urlryn@mydomain.com} SubmitToRelaySendQ, Tag=21469
[40699] (11/22 00:00:16.597):{0xCCC} {urlryn@mydomain.com} OTAFM request from device processed
[40279] (11/22 00:00:16.597):{0xCCC} {urlryn@mydomain.com} SubmitToRelaySendQ, Tag=16800
[40000] (11/22 00:00:16.612):{0x1604} [BIPP] Send data, Tag=21469
[40000] (11/22 00:00:16.612):{0x1604} [BIPP] Send status DATA_ACCEPTED, Tag=16800

[30162] (11/22 00:00:33.316):{0x17D4} {urlryn@mydomain.com} Service name has changed, old=BEServer, new=Blackberry
[30161] (11/22 00:00:33.316):{0x17D4} {urlryn@mydomain.com} Routing info has changed, old=BESSRP#, new=BLACKSRP#, service=Blackberry
[50102] (11/22 00:00:33.316):{0x17D4} [AUDIT] [email address] - User activated on the BES
[40446] (11/22 00:00:33.316):{0x17D4} {urlryn@mydomain.com} Handheld just activated on this server

[40259] (11/22 00:00:33.394):{0x17D4} {urlryn@mydomain.com} *****Redirection on*****
[40442] (11/22 00:00:33.394):{0x17D4} User settings: email=urlryn@mydomain.com, routing=BLACKSRP#, service=Blackberry, device=24233F47, calendar=1, MDS=1, userOTAFM=63, incradle=0, SMIME=0, sentItems=1, dir=wolfda, server=DATACENTEREX
[40000] (11/22 00:00:33.394):{0x17D4} {urlryn@mydomain.com} *** OTAKEYGEN *** switching services completed successfully

[40000] (11/22 00:00:56.146):{0xF80} [BIPP] Received datagram, Tag=16820
[40700] (11/22 00:00:56.146):{0x698} {urlryn@mydomain.com} Receiving packet from device, size=41, TransactionId=-1915297218, Tag=16820, content type=CMIME, cmd=0x3
[40698] (11/22 00:00:56.146):{0x698} {urlryn@mydomain.com} Receiving OTAFM request from device, Tag=16820, TransactionId=-1915297218
[30264] (11/22 00:00:56.146):{0x698} {urlryn@mydomain.com} Received FOLDER_LIST_REQUEST from device
[40699] (11/22 00:00:56.146):{0x698} {urlryn@mydomain.com} OTAFM request from device processed
[40279] (11/22 00:00:56.146):{0x698} {urlryn@mydomain.com} SubmitToRelaySendQ, Tag=16820
[40000] (11/22 00:00:56.146):{0x1604} [BIPP] Send status DATA_ACCEPTED, Tag=16820
[40442] (11/22 00:00:56.177):{0x1068} User settings: email=urlryn@mydomain.com, routing=BLACKSRP#, service=Blackberry, device=24233F47, calendar=1, MDS=1, userOTAFM=63, incradle=0, SMIME=0, sentItems=1, dir=wolfda, server=DATACENTEREX
[40696] (11/22 00:00:56.177):{0x1084} {urlryn@mydomain.com} Generating folder list
[40711] (11/22 00:00:56.333):{0x1084} {urlryn@mydomain.com} FolderID=-25 ParentFolderID=-32 FolderType=OTHER
[40711] (11/22 00:00:56.333):{0x1084} {urlryn@mydomain.com} FolderID=-42 ParentFolderID=-4 FolderType=OTHER
[40711] (11/22 00:00:56.333):{0x1084} {urlryn@mydomain.com} FolderID=-39 ParentFolderID=-4 FolderType=OTHER
[40711] (11/22 00:00:56.333):{0x1084} {urlryn@mydomain.com} FolderID=-7 ParentFolderID=-8 FolderType=OTHER
[40711] (11/22 00:00:56.333):{0x1084} {urlryn@mydomain.com} FolderID=-31 ParentFolderID=-4 FolderType=OTHER
[40711] (11/22 00:00:56.333):{0x1084} {urlryn@mydomain.com} FolderID=-12 ParentFolderID=-4 FolderType=OTHER
[40711] (11/22 00:00:56.333):{0x1084} {urlryn@mydomain.com} FolderID=-37 ParentFolderID=-32 FolderType=OTHER
[40711] (11/22 00:00:56.333):{0x1084} {urlryn@mydomain.com} FolderID=-27 ParentFolderID=-32 FolderType=OTHER
[40711] (11/22 00:00:56.333):{0x1084} {urlryn@mydomain.com} FolderID=-11 ParentFolderID=-32 FolderType=OTHER
[40711] (11/22 00:00:56.333):{0x1084} {urlryn@mydomain.com} FolderID=-33 ParentFolderID=-4 FolderType=OTHER
[40711] (11/22 00:00:56.333):{0x1084} {urlryn@mydomain.com} FolderID=-38 ParentFolderID=-32 FolderType=OTHER
[40711] (11/22 00:00:56.333):{0x1084} {urlryn@mydomain.com} FolderID=-17 ParentFolderID=-33 FolderType=OTHER
[40711] (11/22 00:00:56.333):{0x1084} {urlryn@mydomain.com} FolderID=-24 ParentFolderID=-32 FolderType=OTHER
[40711] (11/22 00:00:56.333):{0x1084} {urlryn@mydomain.com} FolderID=-10 ParentFolderID=-33 FolderType=OTHER
[40711] (11/22 00:00:56.333):{0x1084} {urlryn@mydomain.com} FolderID=-30 ParentFolderID=-4 FolderType=OTHER
[40711] (11/22 00:00:56.333):{0x1084} {urlryn@mydomain.com} FolderID=-29 ParentFolderID=-4 FolderType=OTHER
[40711] (11/22 00:00:56.333):{0x1084} {urlryn@mydomain.com} FolderID=-26 ParentFolderID=-32 FolderType=OTHER
[40711] (11/22 00:00:56.333):{0x1084} {urlryn@mydomain.com} FolderID=-36 ParentFolderID=-32 FolderType=OTHER
[40711] (11/22 00:00:56.333):{0x1084} {urlryn@mydomain.com} FolderID=-15 ParentFolderID=-4 FolderType=OTHER
[40711] (11/22 00:00:56.333):{0x1084} {urlryn@mydomain.com} FolderID=-6 ParentFolderID=-33 FolderType=OTHER
[40711] (11/22 00:00:56.333):{0x1084} {urlryn@mydomain.com} FolderID=-34 ParentFolderID=-25 FolderType=OTHER
[40711] (11/22 00:00:56.333):{0x1084} {urlryn@mydomain.com} FolderID=-13 ParentFolderID=-1 FolderType=OTHER
[40711] (11/22 00:00:56.333):{0x1084} {urlryn@mydomain.com} FolderID=-4 ParentFolderID=-1 FolderType=INBOX
[40711] (11/22 00:00:56.333):{0x1084} {urlryn@mydomain.com} FolderID=-32 ParentFolderID=-4 FolderType=OTHER
[40711] (11/22 00:00:56.333):{0x1084} {urlryn@mydomain.com} FolderID=-16 ParentFolderID=-33 FolderType=OTHER
[40711] (11/22 00:00:56.333):{0x1084} {urlryn@mydomain.com} FolderID=-40 ParentFolderID=-32 FolderType=OTHER
[40711] (11/22 00:00:56.333):{0x1084} {urlryn@mydomain.com} FolderID=-8 ParentFolderID=-4 FolderType=OTHER
[40711] (11/22 00:00:56.333):{0x1084} {urlryn@mydomain.com} FolderID=-22 ParentFolderID=-4 FolderType=OTHER
[40711] (11/22 00:00:56.333):{0x1084} {urlryn@mydomain.com} FolderID=-41 ParentFolderID=-32 FolderType=OTHER
[40711] (11/22 00:00:56.333):{0x1084} {urlryn@mydomain.com} FolderID=-9 ParentFolderID=-33 FolderType=OTHER
[40711] (11/22 00:00:56.333):{0x1084} {urlryn@mydomain.com} FolderID=-14 ParentFolderID=-1 FolderType=SENT_ITEMS
[40711] (11/22 00:00:56.333):{0x1084} {urlryn@mydomain.com} FolderID=-35 ParentFolderID=-25 FolderType=OTHER
[40711] (11/22 00:00:56.333):{0x1084} {urlryn@mydomain.com} FolderID=-21 ParentFolderID=-33 FolderType=OTHER
[40711] (11/22 00:00:56.333):{0x1084} {urlryn@mydomain.com} FolderID=-19 ParentFolderID=-4 FolderType=OTHER
[40711] (11/22 00:00:56.333):{0x1084} {urlryn@mydomain.com} FolderID=-20 ParentFolderID=-1 FolderType=OTHER
[40711] (11/22 00:00:56.333):{0x1084} {urlryn@mydomain.com} FolderID=-18 ParentFolderID=-33 FolderType=OTHER
[40711] (11/22 00:00:56.333):{0x1084} {urlryn@mydomain.com} FolderID=-5 ParentFolderID=-32 FolderType=OTHER
[40711] (11/22 00:00:56.333):{0x1084} {urlryn@mydomain.com} FolderID=-3 ParentFolderID=-1 FolderType=DELETED_ITEMS
[40711] (11/22 00:00:56.333):{0x1084} {urlryn@mydomain.com} FolderID=-1 ParentFolderID=0 FolderType=IPM_SUBTREE
[30261] (11/22 00:00:56.333):{0x1084} {urlryn@mydomain.com} Queuing FOLDER_LIST for device, sending 39 folders
[40697] (11/22 00:00:56.333):{0x1084} {urlryn@mydomain.com} Folder list generated
[30290] (11/22 00:00:56.333):{0x136C} {urlryn@mydomain.com} sending OTAFM command to device, transactionId=-951824487, Tag=21495, size=1258
[40279] (11/22 00:00:56.333):{0x136C} {urlryn@mydomain.com} SubmitToRelaySendQ, Tag=21495
[30066] (11/22 00:00:56.333):{0x136C} Total Msgs Pending 1
[40000] (11/22 00:00:56.333):{0x1604} [BIPP] Send data, Tag=21495

[40000] (11/22 00:00:58.990):{0xF80} [BIPP] Received datagram, Tag=16821
[40700] (11/22 00:00:58.990):{0xBD0} {urlryn@mydomain.com} Receiving packet from device, size=1801, TransactionId=-1915297217, Tag=16821, content type=CMIME, cmd=0x3
[40698] (11/22 00:00:58.990):{0xBD0} {urlryn@mydomain.com} Receiving OTAFM request from device, Tag=16821, TransactionId=-1915297217
[30213] (11/22 00:00:58.990):{0xBD0} {urlryn@mydomain.com} Received OTAFM_CONFIG from device. UserConfig = 63, Conflict = 1
[40000] (11/22 00:00:59.037):{0xF80} [BIPP] Received datagram, Tag=16822
[41079] (11/22 00:00:59.037):{0xBD0} {urlryn@mydomain.com} PagerImp::SaveChanges: changed items = 36, 58
[40000] (11/22 00:00:59.052):{0x7D0} {Colleen.Richardson@GrantPrideco.com} Processed MULTI_STATS from Dispatcher, Tag=16822
[30266] (11/22 00:00:59.083):{0xBD0} {urlryn@mydomain.com} Sending OTAFM_CONFIG_ACK to device, UserConfig=63, Conflict=1
[40583] (11/22 00:00:59.083):{0xBD0} {urlryn@mydomain.com} Sending packet to device, Size=45, Tag=21499, TransactionId=-951824486
[40279] (11/22 00:00:59.083):{0xBD0} {urlryn@mydomain.com} SubmitToRelaySendQ, Tag=21499
[40000] (11/22 00:00:59.083):{0x1604} [BIPP] Send data, Tag=21499
[30214] (11/22 00:00:59.083):{0xBD0} {urlryn@mydomain.com} Received MESSAGE_LIST from device
[41079] (11/22 00:00:59.099):{0xBD0} {urlryn@mydomain.com} PagerImp::SaveChanges: changed items = 65
[30281] (11/22 00:00:59.099):{0xBD0} {urlryn@mydomain.com} Received MESSAGE_LIST_ACK tag in MESSAGE_LIST from device, MessageListId=1095683962
[40526] (11/22 00:00:59.099):{0xBD0} {urlryn@mydomain.com} Beginning Email Reconciliation. Number of device messages 325
[40620] (11/22 00:00:59.208):{0xBD0} {urlryn@mydomain.com} EmailReconciliation: Phase 1
[40620] (11/22 00:00:59.224):{0xBD0} {urlryn@mydomain.com} EmailReconciliation: Phase 2
[40620] (11/22 00:00:59.224):{0xBD0} {urlryn@mydomain.com} EmailReconciliation: Phase 3
[40529] (11/22 00:00:59.224):{0xBD0} {urlryn@mydomain.com} Device Message Matched, RefId=-2145622381
[40589] (11/22 00:00:59.224):{0xBD0} {urlryn@mydomain.com} MessageReconcile - Reconciling Message RefId=-2145622381, devicestatus=1, msgstatus=1, sentstatus=1, devicefolder=-14, msgfolder=-14, sentfolder=-14
[40592] (11/22 00:00:59.224):{0xBD0} {urlryn@mydomain.com} MessageReconcile - Message already reconciled, RefId=-2145622381
[40529] (11/22 00:00:59.224):{0xBD0} {urlryn@mydomain.com} Device Message Matched, RefId=-2145506295
[40589] (11/22 00:00:59.224):{0xBD0} {urlryn@mydomain.com} MessageReconcile - Reconciling Message RefId=-2145506295, devicestatus=1, msgstatus=1, sentstatus=1, devicefolder=-4, msgfolder=-4, sentfolder=-4
[40592] (11/22 00:00:59.224):{0xBD0} {urlryn@mydomain.com} MessageReconcile - Message already reconciled, RefId=-2145506295
[40182] (11/22 00:00:59.224):{0xBD0} {urlryn@mydomain.com} MAPIMailbox::RefIDtoEntryID - Found RefId=-2139549667
[40529] (11/22 00:00:59.224):{0xBD0} {urlryn@mydomain.com} Device Message Matched, RefId=-2139549667
[40589] (11/22 00:00:59.224):{0xBD0} {urlryn@mydomain.com} MessageReconcile - Reconciling Message RefId=-2139549667, devicestatus=3, msgstatus=1, sentstatus=3, devicefolder=-8, msgfolder=-8, sentfolder=-8
[40592] (11/22 00:00:59.224):{0xBD0} {urlryn@mydomain.com} MessageReconcile - Message already reconciled, RefId=-2139549667
[40529] (11/22 00:00:59.224):{0xBD0} {urlryn@mydomain.com} Device Message Matched, RefId=-2135496259
[40589] (11/22 00:00:59.224):{0xBD0} {urlryn@mydomain.com} MessageReconcile - Reconciling Message RefId=-2135496259, devicestatus=1, msgstatus=1, sentstatus=1, devicefolder=-14, msgfolder=-14, sentfolder=-14
[40592] (11/22 00:00:59.224):{0xBD0} {urlryn@mydomain.com} MessageReconcile - Message already reconciled, RefId=-2135496259
[40529] (11/22 00:00:59.224):{0xBD0} {urlryn@mydomain.com} Device Message Matched, RefId=-2132955040
[40589] (11/22 00:00:59.224):{0xBD0} {urlryn@mydomain.com} MessageReconcile - Reconciling Message RefId=-2132955040, devicestatus=1, msgstatus=1, sentstatus=1, devicefolder=-14, msgfolder=-14, sentfolder=-14
[40592] (11/22 00:00:59.224):{0xBD0} {urlryn@mydomain.com} MessageReconcile - Message already reconciled, RefId=-2132955040
[40529] (11/22 00:00:59.224):{0xBD0} {urlryn@mydomain.com} Device Message Matched, RefId=-2132706826
[40589] (11/22 00:00:59.224):{0xBD0} {urlryn@mydomain.com} MessageReconcile - Reconciling Message RefId=-2132706826, devicestatus=1, msgstatus=1, sentstatus=1, devicefolder=-8, msgfolder=-8, sentfolder=-8
[40592] (11/22 00:00:59.224):{0xBD0} {urlryn@mydomain.com} MessageReconcile - Message already reconciled, RefId=-2132706826
[40182] (11/22 00:00:59.224):{0xBD0} {urlryn@mydomain.com} MAPIMailbox::RefIDtoEntryID - Found RefId=-2125501212
[40529] (11/22 00:00:59.224):{0xBD0} {urlryn@mydomain.com} Device Message Matched, RefId=-2125501212
[40589] (11/22 00:00:59.224):{0xBD0} {urlryn@mydomain.com} MessageReconcile - Reconciling Message RefId=-2125501212, devicestatus=3, msgstatus=1, sentstatus=3, devicefolder=-14, msgfolder=-14, sentfolder=-14
[40592] (11/22 00:00:59.224):{0xBD0} {urlryn@mydomain.com} MessageReconcile - Message already reconciled, RefId=-2125501212
[40182] (11/22 00:00:59.224):{0xBD0} {urlryn@mydomain.com} MAPIMailbox::RefIDtoEntryID - Found RefId=-2111849229
[40529] (11/22 00:00:59.224):{0xBD0} {urlryn@mydomain.com} Device Message Matched, RefId=-2111849229
[40589] (11/22 00:00:59.240):{0xBD0} {urlryn@mydomain.com} MessageReconcile - Reconciling Message RefId=-2111849229, devicestatus=3, msgstatus=1, sentstatus=3, devicefolder=-14, msgfolder=-14, sentfolder=-14
[40592] (11/22 00:00:59.240):{0xBD0} {urlryn@mydomain.com} MessageReconcile - Message already reconciled, RefId=-2111849229
[40182] (11/22 00:00:59.240):{0xBD0} {urlryn@mydomain.com} MAPIMailbox::RefIDtoEntryID - Found RefId=-2111719681
[40529] (11/22 00:00:59.240):{0xBD0} {urlryn@mydomain.com} Device Message Matched, RefId=-2111719681
[40589] (11/22 00:00:59.240):{0xBD0} {urlryn@mydomain.com} MessageReconcile - Reconciling Message RefId=-2111719681, devicestatus=3, msgstatus=1, sentstatus=3, devicefolder=-14, msgfolder=-14, sentfolder=-14
[40592] (11/22 00:00:59.240):{0xBD0} {urlryn@mydomain.com} MessageReconcile - Message already reconciled, RefId=-2111719681
[40529] (11/22 00:00:59.240):{0xBD0} {urlryn@mydomain.com} Device Message Matched, RefId=-2097318001
[40589] (11/22 00:00:59.240):{0xBD0} {urlryn@mydomain.com} MessageReconcile - Reconciling Message RefId=-2097318001, devicestatus=1, msgstatus=1, sentstatus=1, devicefolder=-8, msgfolder=-8, sentfolder=-8
[40592] (11/22 00:00:59.240):{0xBD0} {urlryn@mydomain.com} MessageReconcile - Message already reconciled, RefId=-2097318001
[40529] (11/22 00:00:59.240):{0xBD0} {urlryn@mydomain.com} Device Message Matched, RefId=-2047879194
[40589] (11/22 00:00:59.240):{0xBD0} {urlryn@mydomain.com} MessageReconcile - Reconciling Message RefId=-2047879194, devicestatus=1, msgstatus=1, sentstatus=1, devicefolder=-8, msgfolder=-8, sentfolder=-8
[40592] (11/22 00:00:59.240):{0xBD0} {urlryn@mydomain.com} MessageReconcile - Message already reconciled, RefId=-2047879194

Cut out most of this for space reasons!

[40589] (11/22 00:00:59.505):{0xBD0} {urlryn@mydomain.com} MessageReconcile - Reconciling Message RefId=1909824618, devicestatus=1, msgstatus=1, sentstatus=1, devicefolder=-14, msgfolder=-14, sentfolder=-14
[40592] (11/22 00:00:59.505):{0xBD0} {urlryn@mydomain.com} MessageReconcile - Message already reconciled, RefId=1909824618
[40529] (11/22 00:00:59.505):{0xBD0} {urlryn@mydomain.com} Device Message Matched, RefId=2014623546
[40589] (11/22 00:00:59.505):{0xBD0} {urlryn@mydomain.com} MessageReconcile - Reconciling Message RefId=2014623546, devicestatus=1, msgstatus=1, sentstatus=1, devicefolder=-14, msgfolder=-14, sentfolder=-14
[40592] (11/22 00:00:59.505):{0xBD0} {urlryn@mydomain.com} MessageReconcile - Message already reconciled, RefId=2014623546
[40529] (11/22 00:00:59.505):{0xBD0} {urlryn@mydomain.com} Device Message Matched, RefId=2026628488
[40589] (11/22 00:00:59.505):{0xBD0} {urlryn@mydomain.com} MessageReconcile - Reconciling Message RefId=2026628488, devicestatus=1, msgstatus=1, sentstatus=1, devicefolder=-14, msgfolder=-14, sentfolder=-14
[40592] (11/22 00:00:59.505):{0xBD0} {urlryn@mydomain.com} MessageReconcile - Message already reconciled, RefId=2026628488
[40529] (11/22 00:00:59.505):{0xBD0} {urlryn@mydomain.com} Device Message Matched, RefId=2123984283
[40589] (11/22 00:00:59.505):{0xBD0} {urlryn@mydomain.com} MessageReconcile - Reconciling Message RefId=2123984283, devicestatus=1, msgstatus=1, sentstatus=1, devicefolder=-14, msgfolder=-14, sentfolder=-14
[40592] (11/22 00:00:59.505):{0xBD0} {urlryn@mydomain.com} MessageReconcile - Message already reconciled, RefId=2123984283
[40529] (11/22 00:00:59.505):{0xBD0} {urlryn@mydomain.com} Device Message Matched, RefId=2133355212
[40589] (11/22 00:00:59.505):{0xBD0} {urlryn@mydomain.com} MessageReconcile - Reconciling Message RefId=2133355212, devicestatus=1, msgstatus=1, sentstatus=1, devicefolder=-14, msgfolder=-14, sentfolder=-14
[40592] (11/22 00:00:59.505):{0xBD0} {urlryn@mydomain.com} MessageReconcile - Message already reconciled, RefId=2133355212
[40620] (11/22 00:00:59.505):{0xBD0} {urlryn@mydomain.com} EmailReconciliation: Phase 1
[40620] (11/22 00:00:59.505):{0xBD0} {urlryn@mydomain.com} EmailReconciliation: Phase 4
[30280] (11/22 00:00:59.505):{0xBD0} {urlryn@mydomain.com} Email Reconciliation Successful
[40531] (11/22 00:00:59.505):{0xBD0} {urlryn@mydomain.com} EmailReconciliation finished. Number of messages matched = 317. Time = 0:00
[30277] (11/22 00:00:59.505):{0xBD0} {urlryn@mydomain.com} Sending MESSAGE_LIST_ACK to device, MessageListId=1095683962
[40583] (11/22 00:00:59.505):{0xBD0} {urlryn@mydomain.com} Sending packet to device, Size=45, Tag=21500, TransactionId=-951824485
[40279] (11/22 00:00:59.505):{0xBD0} {urlryn@mydomain.com} SubmitToRelaySendQ, Tag=21500
[40699] (11/22 00:00:59.505):{0xBD0} {urlryn@mydomain.com} OTAFM request from device processed
[40279] (11/22 00:00:59.505):{0xBD0} {urlryn@mydomain.com} SubmitToRelaySendQ, Tag=16821
[40000] (11/22 00:00:59.505):{0x1604} [BIPP] Send data, Tag=21500
[40000] (11/22 00:00:59.505):{0x1604} [BIPP] Send status DATA_ACCEPTED, Tag=16821
[30066] (11/22 00:00:59.505):{0x17BC} Total Msgs Pending 1
[40442] (11/22 00:00:59.537):{0x17BC} User settings: email=urlryn@mydomain.com, routing=BLACKSRP#, service=Blackberry, device=24233F47, calendar=1, MDS=1, userOTAFM=63, incradle=0, SMIME=0, sentItems=1, dir=wolfda, server=DATACENTEREX
[40692] (11/22 00:00:59.537):{0xAB0} {urlryn@mydomain.com} Starting message moved rescan
[40693] (11/22 00:00:59.552):{0xAB0} {urlryn@mydomain.com} Message moved rescan completed
[40690] (11/22 00:00:59.552):{0xB9C} {urlryn@mydomain.com} Starting message status rescan
[40691] (11/22 00:00:59.552):{0xB9C} {urlryn@mydomain.com} Message status rescan completed


These entrys below appear over and over again for everybody thats been move to the new server:

[30162] (11/22 00:01:44.461):{0xC98} {urlryn@mydomain.com} Service name has changed, old=Blackberry, new=BEServer
[30161] (11/22 00:01:44.461):{0xC98} {urlryn@mydomain.com} Routing info has changed, old=BLACKSRP#, new=BESSRP#, service=BEServer
[40861] (11/22 00:01:44.461):{0xC98} {urlryn@mydomain.com} New user added to the server - setting pending fields to this server's settings
[50094] (11/22 00:01:44.461):{0xC98} [AUDIT] [email address] - User added to the BES
[40240] (11/22 00:01:44.461):{0xC98} {urlryn@mydomain.com} Handled by other server BEServer

[41079] (11/22 00:02:44.761):{0xBD0} {urlryn@mydomain.com} PagerImp::SaveChanges: changed items = 37, 38
[30162] (11/22 00:02:44.777):{0xBD0} {urlryn@mydomain.com} Service name has changed, old=BEServer, new=Blackberry
[30161] (11/22 00:02:44.777):{0xBD0} {urlryn@mydomain.com} Routing info has changed, old=BESSRP#, new=BLACKSRP#, service=Blackberry
[50102] (11/22 00:02:44.777):{0xBD0} [AUDIT] [email address] - User activated on the BES
[40446] (11/22 00:02:44.777):{0xBD0} {urlryn@mydomain.com} Handheld just activated on this server



I couldn't find anything specifically for LOOKUPs listed here. I had 5-6 txt files to scour through.

Urlryn 11-26-2007 10:54 AM

These issues were now starting to hit everybody that was moved to the new server. I had to move them back to the old one.....and half had to be reactivated. ugh!

Time for RIM Support call?

This is a brand new Server load with
Windows 2003 SP1
Exchange 2003 Admin tools
BES 4.1.0 Base
BES 4.1.4 update
BES 4.1.4 mr3

Antivirus Mcafee + Epolicy


Urlryn


All times are GMT -5. The time now is 04:48 AM.

Powered by vBulletin® Version 3.6.12
Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.