BlackBerry Forums Support Community

BlackBerry Forums Support Community (http://www.blackberryforums.com/)
-   BES Admin Corner (http://www.blackberryforums.com/bes-admin-corner/)
-   -   Error Accessing DB after 5.0.2 Upgrade (http://www.blackberryforums.com/bes-admin-corner/242859-error-accessing-db-after-5-0-2-upgrade.html)

loweredxtreme 01-06-2011 03:51 PM

Error Accessing DB after 5.0.2 Upgrade
 
I went through the process of upgrading the BES to the 5.0.2 from 5.0.1 and the database upgraded successfully. After is requested a reboot, the upgrade tried to complete but the program errored out. The program was trying to complete the install but came up with "Cannot connect to SQL database"

I went to the log files and here is what it said:

Login failed for user 'sa'.

For more information, see Help and Support Center at Events and Errors Message Center: Basic Search.

2011-01-03 15:06:59.15 Server Microsoft SQL Server 2005 - 9.00.4035.00 (Intel X86)
Nov 24 2008 13:01:59
Copyright (c) 1988-2005 Microsoft Corporation
Express Edition on Windows NT 5.2 (Build 3790: Service Pack 2)

2011-01-03 15:06:59.31 Server (c) 2005 Microsoft Corporation.
2011-01-03 15:06:59.31 Server All rights reserved.
2011-01-03 15:06:59.31 Server Server process ID is 1576.
2011-01-03 15:06:59.31 Server Authentication mode is MIXED.
2011-01-03 15:06:59.32 Server Logging SQL Server messages in file 'C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\ERRORLOG'.
2011-01-03 15:06:59.32 Server This instance of SQL Server last reported using a process ID of 1584 at 1/3/2011 3:06:52 PM (local) 1/3/2011 11:06:52 PM (UTC). This is an informational message only; no user action is required.
2011-01-03 15:06:59.32 Server Registry startup parameters:
2011-01-03 15:06:59.37 Server -d C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\master.mdf
2011-01-03 15:06:59.37 Server -e C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\ERRORLOG
2011-01-03 15:06:59.37 Server -l C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\mastlog.ldf
2011-01-03 15:06:59.51 Server SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
2011-01-03 15:06:59.51 Server Detected 2 CPUs. This is an informational message; no user action is required.
2011-01-03 15:06:59.83 Server Error: 8315, Severity: 16, State: 1.
2011-01-03 15:06:59.83 Server SQL Server performance counter 'Page lookups/sec' not found in registry. SQL Server performance counters are disabled.
2011-01-03 15:06:59.91 Server Error: 3409, Severity: 16, State: 1.
2011-01-03 15:06:59.91 Server Performance counter shared memory setup failed with error -1. Reinstall sqlctr.ini for this instance, and ensure that the instance login account has correct registry permissions.
2011-01-03 15:07:02.81 Server Using dynamic lock allocation. Initial allocation of 2500 Lock blocks and 5000 Lock Owner blocks per node. This is an informational message only. No user action is required.
2011-01-03 15:07:05.57 Server Database mirroring has been enabled on this instance of SQL Server.
2011-01-03 15:07:06.21 spid5s Starting up database 'master'.
2011-01-03 15:07:07.21 spid5s Recovery is writing a checkpoint in database 'master' (1). This is an informational message only. No user action is required.
2011-01-03 15:07:08.21 spid5s SQL Trace ID 1 was started by login "sa".
2011-01-03 15:07:08.35 spid5s Starting up database 'mssqlsystemresource'.
2011-01-03 15:07:08.42 spid5s The resource database build version is 9.00.4035. This is an informational message only. No user action is required.
2011-01-03 15:07:09.02 spid7s Starting up database 'model'.
2011-01-03 15:07:09.09 spid5s Server name is 'BESSERVER-P\BLACKBERRY'. This is an informational message only. No user action is required.
2011-01-03 15:07:09.13 spid5s Starting up database 'msdb'.
2011-01-03 15:07:09.63 Server A self-generated certificate was successfully loaded for encryption.
2011-01-03 15:07:09.70 spid7s Clearing tempdb database.
2011-01-03 15:07:09.78 Server Server is listening on [ 'any' <ipv4> 1407].
2011-01-03 15:07:09.79 Server Server local connection provider is ready to accept connection on [ \\.\pipe\SQLLocal\BLACKBERRY ].
2011-01-03 15:07:09.79 Server Server named pipe provider is ready to accept connection on [ \\.\pipe\MSSQL$BLACKBERRY\sql\query ].
2011-01-03 15:07:09.81 Server Dedicated administrator connection support was not started because it is not available on this edition of SQL Server. This is an informational message only. No user action is required.
2011-01-03 15:07:10.90 Server SQL Server is now ready for client connections. This is an informational message; no user action is required.
2011-01-03 15:07:11.02 spid7s Starting up database 'tempdb'.
2011-01-03 15:07:11.39 spid5s Recovery is complete. This is an informational message only. No user action is required.
2011-01-03 15:07:11.53 spid10s The Service Broker protocol transport is disabled or not configured.
2011-01-03 15:07:11.55 spid10s The Database Mirroring protocol transport is disabled or not configured.
2011-01-03 15:07:11.99 spid10s Service Broker manager has started.
2011-01-03 15:10:26.22 Server Server resumed execution after being idle 155 seconds: user activity awakened the server. This is an informational message only. No user action is required.
2011-01-03 15:10:27.16 spid51 Starting up database 'BESMgmt'.
2011-01-03 15:11:17.41 Logon Error: 18456, Severity: 14, State: 16.
2011-01-03 15:11:17.41 Logon Login failed for user 'sa'. [CLIENT: ]
2011-01-03 15:11:22.47 Logon Error: 18456, Severity: 14, State: 16.
2011-01-03 15:11:22.47 Logon Login failed for user 'sa'. [CLIENT: ]
2011-01-03 15:11:23.01 Logon Error: 18456, Severity: 14, State: 16.
2011-01-03 15:11:23.01 Logon Login failed for user 'sa'.[CLIENT: ]
2011-01-03 15:11:23.97 Logon Error: 18456, Severity: 14, State: 16.
2011-01-03 15:11:23.97 Logon Login failed for user 'sa'.[CLIENT: ]
2011-01-03 15:11:27.89 Logon Error: 18456, Severity: 14, State: 16.
2011-01-03 15:11:27.89 Logon Login failed for user 'sa'. [CLIENT: ]
2011-01-03 15:11:28.12 Logon Error: 18456, Severity: 14, State: 16.
2011-01-03 15:11:28.12 Logon Login failed for user 'sa'. [CLIENT: ]
2011-01-03 15:11:30.66 Logon Error: 18456, Severity: 14, State: 16.
2011-01-03 15:11:30.66 Logon Login failed for user 'sa'. [CLIENT: ]
2011-01-03 15:11:33.05 Logon Error: 18456, Severity: 14, State: 16.
2011-01-03 15:11:33.05 Logon Login failed for user 'sa'. [CLIENT: ]
2011-01-03 15:11:33.35 Logon Error: 18456, Severity: 14, State: 16.
2011-01-03 15:11:33.35 Logon Login failed for user 'sa'. [CLIENT: ]
2011-01-03 15:11:35.54 Logon Error: 18456, Severity: 14, State: 16.
2011-01-03 15:11:35.54 Logon Login failed for user 'sa'.[CLIENT: ]
2011-01-03 15:11:37.73 Logon Error: 18456, Severity: 14, State: 16.
2011-01-03 15:11:37.73 Logon Login failed for user 'sa'. [CLIENT: ]
2011-01-03 15:11:39.13 Logon Error: 18456, Severity: 14, State: 16.
2011-01-03 15:11:39.13 Logon Login failed for user 'sa'. [CLIENT: ]
2011-01-03 15:11:39.33 Logon Error: 18456, Severity: 14, State: 16.
2011-01-03 15:11:39.33 Logon Login failed for user 'sa'. [CLIENT: ]
2011-01-03 15:11:44.11 Logon Error: 18456, Severity: 14, State: 16.
2011-01-03 15:11:44.11 Logon Login failed for user 'sa'. [CLIENT: ]
2011-01-03 15:11:45.58 Logon Error: 18456, Severity: 14, State: 16.
2011-01-03 15:11:45.58 Logon Login failed for user 'sa'. v
2011-01-03 15:11:49.48 Logon Error: 18456, Severity: 14, State: 16.
2011-01-03 15:11:49.48 Logon Login failed for user 'sa'. [CLIENT: ]
2011-01-03 15:11:51.82 Logon Error: 18456, Severity: 14, State: 16.
2011-01-03 15:11:51.82 Logon Login failed for user 'sa'. [CLIENT: ]
2011-01-03 15:11:55.06 Logon Error: 18456, Severity: 14, State: 16.
2011-01-03 15:11:55.06 Logon Login failed for user 'sa'. [CLIENT: ]
2011-01-03 15:11:55.10 Logon Error: 18456, Severity: 14, State: 16.
2011-01-03 15:11:55.10 Logon Login failed for user 'sa'.[CLIENT: ]
2011-01-03 15:11:55.45 Logon Error: 18456, Severity: 14, State: 16.
2011-01-03 15:11:55.45 Logon Login failed for user 'sa'. [CLIENT: ]
2011-01-03 15:12:05.28 spid54 Starting up database 'BMSStore'.
2011-01-03 15:12:19.49 Logon Error: 18456, Severity: 14, State: 16.
2011-01-03 15:12:19.49 Logon Login failed for user 'sa'. [CLIENT: ]
2011-01-03 15:12:27.85 Logon Error: 18456, Severity: 14, State: 16.
2011-01-03 15:12:27.85 Logon Login failed for user 'sa'. [CLIENT: ]
2011-01-03 15:12:29.00 spid59 Using 'xpstar90.dll' version '2005.90.4035' to execute extended stored procedure 'xp_regread'. This is an informational message only; no user action is required.
2011-01-03 15:12:31.39 Logon Error: 18456, Severity: 14, State: 16.
2011-01-03 15:12:31.39 Logon Login failed for user 'sa'. [CLIENT: ]
2011-01-03 15:19:09.04 Logon Error: 18456, Severity: 14, State: 16.
2011-01-03 15:19:09.04 Logon Login failed for user 'sa'. [CLIENT: ]
2011-01-03 15:19:19.44 Logon Error: 18456, Severity: 14, State: 16.
2011-01-03 15:19:19.44 Logon Login failed for user 'sa'. [CLIENT: ]
2011-01-03 15:19:29.68 Logon Error: 18456, Severity: 14, State: 16.
2011-01-03 15:19:29.68 Logon Login failed for user 'sa'. [CLIENT: ]
2011-01-03 15:19:40.39 Logon Error: 18456, Severity: 14, State: 16.
2011-01-03 15:19:40.39 Logon Login failed for user 'sa'. [CLIENT: ]
2011-01-03 15:19:50.63 Logon Error: 18456, Severity: 14, State: 16.
2011-01-03 15:19:50.63 Logon Login failed for user 'sa'. [CLIENT: ]
2011-01-03 16:14:08.85 Logon Error: 18456, Severity: 14, State: 16.
2011-01-03 16:14:08.85 Logon Login failed for user 'sa'. [CLIENT: ]
2011-01-03 16:14:18.86 Logon Error: 18456, Severity: 14, State: 16.
2011-01-03 16:14:18.86 Logon Login failed for user 'sa'. [CLIENT: ]
2011-01-03 16:14:28.88 Logon Error: 18456, Severity: 14, State: 16.
2011-01-03 16:14:28.88 Logon Login failed for user 'sa'. [CLIENT: ]
2011-01-03 16:14:38.89 Logon Error: 18456, Severity: 14, State: 16.
2011-01-03 16:14:38.89 Logon Login failed for user 'sa'. [CLIENT: ]
2011-01-03 16:14:48.90 Logon Error: 18456, Severity: 14, State: 16.
2011-01-03 16:14:48.90 Logon Login failed for user 'sa'. [CLIENT: ]
2011-01-03 16:36:05.74 spid106 Starting up database 'md-is'.
2011-01-03 16:50:47.07 Logon Error: 18456, Severity: 14, State: 16.
2011-01-03 16:50:47.07 Logon Login failed for user 'sa'. [CLIENT: ]
2011-01-03 16:50:57.14 Logon Error: 18456, Severity: 14, State: 16.
2011-01-03 16:50:57.14 Logon Login failed for user 'sa'. [CLIENT: ]
2011-01-03 16:51:07.14 Logon Error: 18456, Severity: 14, State: 16.
2011-01-03 16:51:07.14 Logon Login failed for user 'sa'. [CLIENT: ]
2011-01-03 16:51:17.16 Logon Error: 18456, Severity: 14, State: 16.
2011-01-03 16:51:17.16 Logon Login failed for user 'sa'. [CLIENT: ]
2011-01-03 16:51:27.16 Logon Error: 18456, Severity: 14, State: 16.
2011-01-03 16:51:27.16 Logon Login failed for user 'sa'. [CLIENT: ]
2011-01-03 17:00:18.36 spid108 Using 'xplog70.dll' version '2005.90.4035' to execute extended stored procedure 'xp_msver'. This is an informational message only; no user action is required.
2011-01-03 17:16:16.37 Logon Error: 18456, Severity: 14, State: 16.
2011-01-03 17:16:16.37 Logon Login failed for user 'sa'. [CLIENT: ]
2011-01-03 17:16:26.36 Logon Error: 18456, Severity: 14, State: 16.
2011-01-03 17:16:26.36 Logon Login failed for user 'sa'. [CLIENT: ]
2011-01-03 17:16:36.38 Logon Error: 18456, Severity: 14, State: 16.
2011-01-03 17:16:36.38 Logon Login failed for user 'sa'. [CLIENT: ]
2011-01-03 17:16:46.38 Logon Error: 18456, Severity: 14, State: 16.
2011-01-03 17:16:46.38 Logon Login failed for user 'sa'. [CLIENT: ]
2011-01-03 17:16:56.39 Logon Error: 18456, Severity: 14, State: 16.
2011-01-03 17:16:56.39 Logon Login failed for user 'sa'. [CLIENT: ]
2011-01-03 17:22:11.88 Logon Error: 18456, Severity: 14, State: 16.
2011-01-03 17:22:11.88 Logon Login failed for user 'sa'. [CLIENT: ]
2011-01-03 17:22:21.90 Logon Error: 18456, Severity: 14, State: 16.
2011-01-03 17:22:21.90 Logon Login failed for user 'sa'. [CLIENT: ]
2011-01-03 17:22:31.90 Logon Error: 18456, Severity: 14, State: 16.
2011-01-03 17:22:31.90 Logon Login failed for user 'sa'. [CLIENT: ]]
2011-01-03 17:22:41.91 Logon Error: 18456, Severity: 14, State: 16.
2011-01-03 17:22:41.91 Logon Login failed for user 'sa'. [CLIENT: ]
2011-01-03 17:22:51.93 Logon Error: 18456, Severity: 14, State: 16.
2011-01-03 17:22:51.93 Logon Login failed for user 'sa'. [CLIENT: ]
2011-01-03 22:01:30.60 Backup Database backed up. Database: BESMgmt, creation date(time): 2010/06/25(18:47:05), pages dumped: 18961, first LSN: 6613:701:58, last LSN: 6613:725:1, number of dump devices: 1, device information: (FILE=1, TYPE=DISK: {'C:\WINDOWS\TEMP\BESMgmt201101032201.bak'}). This is an informational message only. No user action is required.
2011-01-03 22:01:54.70 Backup Database backed up. Database: BMSStore, creation date(time): 2010/06/25(18:50:28), pages dumped: 35381, first LSN: 2005:607:37, last LSN: 2005:623:1, number of dump devices: 1, device information: (FILE=1, TYPE=DISK: {'C:\WINDOWS\TEMP\BMSStore201101032201.bak'}). This is an informational message only. No user action is required.
2011-01-04 22:00:14.33 Backup Database backed up. Database: BESMgmt, creation date(time): 2010/06/25(18:47:05), pages dumped: 19079, first LSN: 6659:954:192, last LSN: 6659:1059:1, number of dump devices: 1, device information: (FILE=1, TYPE=DISK: {'C:\WINDOWS\TEMP\BESMgmt201101042200.bak'}). This is an informational message only. No user action is required.
2011-01-04 22:00:38.67 Backup Database backed up. Database: BMSStore, creation date(time): 2010/06/25(18:50:28), pages dumped: 35381, first LSN: 2005:630:37, last LSN: 2005:646:1, number of dump devices: 1, device information: (FILE=1, TYPE=DISK: {'C:\WINDOWS\TEMP\BMSStore201101042200.bak'}). This is an informational message only. No user action is required.

Initial DB was setup with Mixed mode authentication using "sa". I checked the DB through Studio Express Manager and was able to login in using the "sa" credentials. Also verified "sa" is the owner of the DB.

Any suggestions?

Thanks!

penguin3107 01-06-2011 08:40 PM

Re: Error Accessing DB after 5.0.2 Upgrade
 
You're using the sa account to try to authenticate? That's not good.
You should be using the BES service account. (BESadmin)

When you did the upgrade (and/or installed BES) what user account were you logged into the machine as?

loweredxtreme 01-07-2011 04:11 PM

Re: Error Accessing DB after 5.0.2 Upgrade
 
I was logged in as "BESAdmin".

Just during the upgrade, it asked for DB access and I used the "sa" account since we run in mixed mode. Not NT user.

Was that not correct?

penguin3107 01-07-2011 04:27 PM

Re: Error Accessing DB after 5.0.2 Upgrade
 
The BESMgmt database should only be accessed by the BESadmin user account.
Not sa.

loweredxtreme 01-10-2011 02:16 PM

Re: Error Accessing DB after 5.0.2 Upgrade
 
Is there a way to roll back the install to the beginning so I can alter the login sequence that you may know of?

Because as of right now the the database has successfully upgraded and it shows the upgrade in the Program list

BB-Tech support 01-10-2011 02:32 PM

Re: Error Accessing DB after 5.0.2 Upgrade
 
Quote:

Originally Posted by loweredxtreme (Post 1692707)
Is there a way to roll back the install to the beginning so I can alter the login sequence that you may know of?

Because as of right now the the database has successfully upgraded and it shows the upgrade in the Program list

Yes you can start from begging
You suppose to have BESMgmt.bak in SQL data folder (loo in backup)

Now you have to uninstall BES
you have to detach your BESMgmt database from sql
and you have to create new blank database
follow this KB
KB03112-How to move the BlackBerry Configuration Database to a new Microsoft SQL Server instance
be sure that database folder is from installation of bes which database backup is (5.0.1)
also download
Microsoft SQL Server Management Studio Express
Download details: Microsoft SQL Server Management Studio Express
its easier to setup permissions for BESMgmt database
after you create blank database, then restore backup into that new besmgmt
for safe side you can install bes5.0.1 and then upgrade to 5.0.2

hope this help


All times are GMT -5. The time now is 09:20 PM.

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