Hi newbie here! (well I've been looking for last 12 month ).

Server: Win 2000 terminal server
Current BES: 3.6.5.8

I have attempted an upgrade now a good few times without success. It gets through every stage of the upgrade fine until the final part and the install progress bar gets stuck near the end at the same spot everytime. I have attached a screen shot for your viewing, it seems to halt when editing time zones in the Registry (I'm guessing here)..Everything seems to go smooth up until this point.


I have searched high and low on the net and also RIM support (they won't support me unless I have at least 1.5gb ram!) and cannot find a replication of this problem.

I have the install log if needed.

Many thanks for looking and I appreciate any idea's \ suggestions!!

Yeah post the install log or at least the error at the very bottom

Here are the last 20 or so lines from the log:

[30000] (01/08 13:49:24):{0x43C} SQL being executed:
DROP TABLE #tmpPK
[30000] (01/08 13:49:24):{0x43C} SQL executed successfully
[30000] (01/08 13:49:24):{0x43C} SQL being executed:
-------------------------------------------------------------------------------------------------------
if object_id('dbo.sp_ServiceConfig') is not null drop PROCEDURE dbo.sp_ServiceConfig
[30000] (01/08 13:49:24):{0x43C} SQL executed successfully
[30000] (01/08 13:49:24):{0x43C} SQL being executed:
-------------------------------------------------------------------------------------------------------
-- procedure sp_ServiceConfig insert BB service info into tables : sp_ServiceConfig, ServiceTable
-- [IN] @type - type of BB service BB Agent : BBA
-- [IN] @host name may be IP address
-- [IN] @port - UDP port
-- [IN] @iid - internal BB service id
-- [IN] @pid - process id id BB service
-- [IN] @rimdata - dbsn structure as RimString
-- [IN] @timeout - timeout between refresh notifications
-- [OUT] @version - dbsn version

CREATE PROCEDURE dbo.sp_ServiceConfig @type NVARCHAR(4), @host NVARCHAR(255), @port INT, @iid INT,
@pid INT, @rimdata VARBINARY(7400), @timeout INT, @version INT OUTPUT
AS
SET NOCOUNT ON
SET @version = 0
DECLARE @id INT
IF object_id('master..xp_RIMdbns') IS NOT NULL AND object_id('master..xp_RIMinitialize') IS NOT NULL
BEGIN
SELECT @id = id FROM dbo.ServiceConfig WHERE iid = @iid AND host = @host AND type = @type
DECLARE
[30000] (01/08 13:49:24):{0x43C} SQL Informational Message from CBESDBInstaller::ExecuteSql.executeDirect: Cannot add rows to sysdepends for the current stored procedure because it depends on the missing object 'master..xp_RIMdbns'. The stored procedure will still be created.
[30000] (01/08 13:49:24):{0x43C} SQL Informational Message from CBESDBInstaller::ExecuteSql.executeDirect: Cannot add rows to sysdepends for the current stored procedure because it depends on the missing object 'master..xp_RIMinitialize'. The stored procedure will still be created.
[30000] (01/08 13:49:24):{0x43C} SQL Informational Message from CBESDBInstaller::ExecuteSql.executeDirect: Cannot add rows to sysdepends for the current stored procedure because it depends on the missing object 'master..xp_RIM_version'. The stored procedure will still be created.
[30000] (01/08 13:49:24):{0x43C} SQL executed successfully
[30000] (01/08 13:49:24):{0x43C} SQL being executed:

-------------------------------------------------------------------------------------------------------
if object_id('dbo.TR_ServiceConfig') is not null drop TRIGGER dbo.TR_ServiceConfig
[30000] (01/08 13:49:24):{0x43C} SQL executed successfully
[30000] (01/08 13:49:24):{0x43C} SQL Informational Message from CBESDBInstaller::ExecuteSql.execute2: Cannot add rows to sysdepends for the current stored procedure because it depends on the missing object 'master..xp_RIMdelete_srv_list'. The stored procedure will still be created.
[30000] (01/08 13:49:24):{0x43C} SQL executed successfully
[30000] (01/08 13:49:24):{0x43C} [PIPTOOL]: Leaving DBInfoDlg.
[30000] (01/08 13:49:24):{0x43C} [PIPTOOL]: SQL Server: (Mailsvr1), DB Name: (BESMgmt), DB Auth: (SQL Auth) SQL User Name: () sa
[30000] (01/08 13:49:24):{0x43C} [PIPTOOL]: Entering BESMigrateDlg.
[30000] (01/08 13:49:28):{0x43C} [PIPTOOL]: Leaving BESMigrateDlg.
[30000] (01/08 13:49:28):{0x43C} [PIPTOOL]: Entering IMTypeDlg.
[30000] (01/08 13:49:29):{0x43C} [PIPTOOL]: Entering InstallationInfoDlg.
[30000] (01/08 13:49:29):{0x43C} [PIPTOOL]: Leaving IMTypeDlg.
[30000] (01/08 13:49:29):{0x43C} [PIPTOOL]: IM Type: (0)
[30000] (01/08 13:52:15):{0x43C} [PIPTOOL]: Exiting PIPTool from InstallationInfoDlg.
====== END OF LOG ======

I'm now thinking of a quick way to get round this, luckily I only have 3 users on my BES!

If no-one can offer a suggestion, I might just remove the whole thing and start a fresh install from 4.1 as opposed to upgrading.