[MisterGriffiths]

Does anyone run a knife edge cutover configuration for the purposes of Disaster Recovery/Business Continuity and upgraded their environment to SP6?

We have recently upgraded and have subsequently found a number of SQL errors in the SYNC logs.

Our environment is BES 4.1.6 (upgraded from BES 4.1.4 Base), Exchange 2003 and SQL 2000.

When we performed the upgrade, we took down all services and first upgraded our DR site. We brought up all the services, left it running for an hour and didn't experience any issue or find any errors logged. We then took down the service at the DR site and proceeded to upgrade the Primary servers. When we brought up the services here, we almost immediately started seeing the errors in the SYNC log.

We've had about 100 occurrences in the last few days but we aren't getting any reported problems from the affected users.

At typical set of error entries is as follows:

[46042] (09/15 10:05:40.498):{0x1594} [SYNC-SSession] Received 8 bytes from device. [Surname, Firstname:1703, SID=89123984, SEQ=1/1]
[60000] (09/15 10:05:40.498):{0x1594} [ODBCRecord::DeleteRecord] SQL = "DELETE FROM SyncRequest WHERE UserConfigID = ? AND SyncDataSourceId = ? AND CmdID = ?".
[60000] (09/15 10:05:40.498):{0x1594} [ODBCRecord::DeleteRecord] DATA = "UserConfigID[1703] SyncDataSourceId[2023] CmdID[-1] ".
[60000] (09/15 10:05:40.498):{0x1594} [ODBCRecord::DeleteRecord] Number of rows deleted = 1
[60000] (09/15 10:05:40.498):{0x1594} [ODBCRecord::DoCreateRecord] SQL = "SET NOCOUNT ON; INSERT INTO SyncRecordState (UserConfigID, SyncDataSourceId, SyncDbTypeId, TableId, GUID, UID, FieldHashes) VALUES (?, ?, ?, ?, ?, ?, ?) ; SELECT SCOPE_IDENTITY(); SET NOCOUNT OFF".
[60000] (09/15 10:05:40.498):{0x1594} [ODBCRecord::DoCreateRecord] DATA = "UserConfigID[1703] SyncDataSourceId[10827] SyncDbTypeId[7118] TableId[0] GUID[18732] UID[18732] FieldHashes[0x030086470766] ".
[20000] (09/15 10:05:40.498):{0x1594} [ODBCRecord::DoCreateRecord] SQL error: [0x80040E2F Cannot insert duplicate key row in object 'SyncRecordState' with unique index 'idx_SyncRecordState_1'.] Source: [Microsoft OLE DB Provider for SQL Server] SQL State: [23000] NativeError: [2601]
[20000] (09/15 10:05:40.498):{0x1594} [ODBCRecord::DoCreateRecord] SQL error: [0x80040E2F The statement has been terminated.] Source: [Microsoft OLE DB Provider for SQL Server] SQL State: [01000] NativeError: [3621]
[20000] (09/15 10:05:40.498):{0x1594} [ODBCRecord::DoCreateRecord] COM Error 0x80040E2F - IDispatch error #3119 - Source: "Microsoft OLE DB Provider for SQL Server" - Description "Cannot insert duplicate key row in object 'SyncRecordState' with unique index 'idx_SyncRecordState_1'."
[20000] (09/15 10:05:40.498):{0x1594} [ODBCRecord::DoCreateRecord] SQL = "SET NOCOUNT ON; INSERT INTO SyncRecordState (UserConfigID, SyncDataSourceId, SyncDbTypeId, TableId, GUID, UID, FieldHashes) VALUES (?, ?, ?, ?, ?, ?, ?) ; SELECT SCOPE_IDENTITY(); SET NOCOUNT OFF".
[20000] (09/15 10:05:40.498):{0x1594} [ODBCRecord::DoCreateRecord] DATA = "UserConfigID[1703] SyncDataSourceId[10827] SyncDbTypeId[7118] TableId[0] GUID[18732] UID[18732] FieldHashes[0x030086470766] ".
[26031] (09/15 10:05:40.514):{0x1594} [SYNC-SSession] Failed to update field hash in SyncRecordState. [Surname, Firstname:1703, DS=Config, DB=Enterprise Configuration, UID=18732]
[46019] (09/15 10:05:40.514):{0x1594} [SYNC-SSession] SSession is finished. [Surname, Firstname:1703, SID=89123984, CLID=39, ECLID=1933]
[60000] (09/15 10:05:40.514):{0x1594} [ODBCRecord::DoSetValue] SQL = "UPDATE SyncUserState SET State = ? WHERE UserConfigID = ? AND SyncUserStateTypeId = ?".
[60000] (09/15 10:05:40.514):{0x1594} [ODBCRecord::DoSetValue] DATA = "State[40] UserConfigID[1703] SyncUserStateTypeId[2] ".
[60000] (09/15 10:05:40.514):{0x1594} [ODBCRecord::DoSetValue] Number of rows updated = 1


I suppose my questions are:

Does anyone run a similar configuration and have you seen the same errors?
Can anyone give any insight into the purpose of the SyncRecordState Table?
How would this be affecting users?

[ashworth]

"SQL error: [0x80040E2F Cannot insert duplicate key row in object 'SyncRecordState' with unique index 'idx_SyncRecordState_1'.] Source: [Microsoft OLE DB Provider for SQL Server] SQL State: [23000] NativeError: [2601]"

That does not look good. It looks like you may have some DB corruption or invalid indexs/keys within your db. I would take a backup of the DB and have your DBA take a look at it. If he wants to know what it shoudl look like just create a black DB with createdb.exe and then he can compare your existing db with your production db. If you dont have a DBA then I would call RIM and get them to take a look at it.

[MisterGriffiths]

Hey Ash, thanks for the reply and sorry for the delay with my update, I've been somewhat busy with this issue.

We are still working through this problem, although it doesn't seem to be affecting service. RIM are also working with us now.

Would still be interested to know if anyone else has ever seen these warnings in their own SYNC logs.

[Dookie]

Originally Posted by MisterGriffiths

Hey Ash, thanks for the reply and sorry for the delay with my update, I've been somewhat busy with this issue.

We are still working through this problem, although it doesn't seem to be affecting service. RIM are also working with us now.

Would still be interested to know if anyone else has ever seen these warnings in their own SYNC logs.

I have the very same errors. No idea where they come from. I've checked the DB and there are no corruptions. Looks really weird, going to call RIM today.
Did you get any information from them so far?

[Dookie]

BTW: i've tried and it works somehow so far. When i've found those issue, i've tried to move the user between servers. Which basically only rescans users mailbox, and sends a new service books to the device. An guess what? The errors will not come up again in the log.

So i guess that the DB is ok, but the BlackBerry SW is somehow messed up. Any ideas?

[MisterGriffiths]

RIM have informed us not to worry about this now.

Further testing proved that reoccurrences of the issue were unlikely. We took the device of a user associated with the problem, deleted and then undeleted the 'Desktop[Sync]' Service Book from the BlackBerry, forcing a synchronisation. There were no further warnings seen for the user.

[fleece]

Having similar problems on initial BES system (4.1.6.10) for Exchange 2003 SP2...

I've got 1 user on the system (me, "SF"). Having problem syncing new Exchange contact records created on the Exchange server side using Outlook on a PC. The new contact records aren't making it to the device (8820 v4.5.0.69).

Seeing these errors in log...

[46042] (09/29 16:38:36.624):{0x13D4} [SYNC-SSession] Received 7 bytes from device. [SF:1, SID=12761109, SEQ=1/1]
[20000] (09/29 16:38:36.687):{0x13D4} [ODBCRecord::DoCreateRecord] SQL error: [0x80040E2F Cannot insert duplicate key row in object 'SyncRecordState' with unique index 'idx_SyncRecordState_1'.] Source: [Microsoft OLE DB Provider for SQL Server] SQL State: [23000] NativeError: [2601]
[20000] (09/29 16:38:36.687):{0x13D4} [ODBCRecord::DoCreateRecord] SQL error: [0x80040E2F The statement has been terminated.] Source: [Microsoft OLE DB Provider for SQL Server] SQL State: [01000] NativeError: [3621]
[20000] (09/29 16:38:36.687):{0x13D4} [ODBCRecord::DoCreateRecord] COM Error 0x80040E2F - IDispatch error #3119 - Source: "Microsoft OLE DB Provider for SQL Server" - Description "Cannot insert duplicate key row in object 'SyncRecordState' with unique index 'idx_SyncRecordState_1'."
[20000] (09/29 16:38:36.687):{0x13D4} [ODBCRecord::DoCreateRecord] SQL = "SET NOCOUNT ON; INSERT INTO SyncRecordState (UserConfigID, SyncDataSourceId, SyncDbTypeId, TableId, GUID, UID, FieldHashes) VALUES (?, ?, ?, ?, ?, ?, ?) ; SELECT SCOPE_IDENTITY(); SET NOCOUNT OFF".
[20000] (09/29 16:38:36.687):{0x13D4} [ODBCRecord::DoCreateRecord] DATA = "UserConfigID[1] SyncDataSourceId[11728] SyncDbTypeId[28675] TableId[73] GUID[1846] UID[-1846] FieldHashes[0x200046211D632100B91301EC7E00825F0E09] ".
[26029] (09/29 16:38:36.687):{0x13D4} [SYNC-SSession] Failed to add state record in SyncRecordState. [SF:1, DS=Exchange, DB=Address Book, TB=73, UID=-1846]
[46032] (09/29 16:38:36.687):{0x13D4} [SYNC-SSession] Send XML response to Exchange connector. [SF:1]
[46019] (09/29 16:38:36.687):{0x13D4} [SYNC-SSession] SSession is finished. [SF:1, SID=12761109, CLID=27, ECLID=59]

[MisterGriffiths]

Try deleting and then undeleting the 'Desktop[Sync]' Service Book on your handheld and then go to Enterprise Activation within Options > Advanced Options.

This should show you all the different Sync processes running and allow you see if anything else is failing to Sync.

[Dookie]

Originally Posted by MisterGriffiths

RIM have informed us not to worry about this now.

Further testing proved that reoccurrences of the issue were unlikely. We took the device of a user associated with the problem, deleted and then undeleted the 'Desktop[Sync]' Service Book from the BlackBerry, forcing a synchronisation. There were no further warnings seen for the user.

Funny, i thought that it will not be something really big. But for those users, wireless sync stopped working, which is a big thing for them. Anyway - deleting the book or moving the users between servers is prolly the same way. It refreshes the service books.
Thanks for info.

[fleece]

Originally Posted by MisterGriffiths

Try deleting and then undeleting the 'Desktop[Sync]' Service Book on your handheld and then go to Enterprise Activation within Options > Advanced Options.

This should show you all the different Sync processes running and allow you see if anything else is failing to Sync.

Thanks. I tried that. Doesn't seem to help. Everything else seems to sync okay when re-activating after Desktop[SYNC] service book delete & undelete, but problem reoccurs.

I'm going to desktop restore an empty address book to the device and resync. If that doesn't work, I'll reinstall BES.

[MisterGriffiths]

Maybe remove your account from the BES (removing the BES info from the mailbox) and wipe the handheld, then try to add yourself again and EA before reinstalling the BES.

[fleece]

Originally Posted by MisterGriffiths

Maybe remove your account from the BES (removing the BES info from the mailbox) and wipe the handheld, then try to add yourself again and EA before reinstalling the BES.

Thanks. That seemed to fix it.