[jkh1]

Hi - am failing to get 5.0.1 installed onto an SBS2003 system. I have successfully installed 4.1.4 on numerous SBS servers in the past within an hour and without any issues, and assumed that this new version would be as simple. After several hours yesterday in front of client looking like the rear end of a pantomime horse, I had to give up and go home, which doesn't look good from a customer's standpoint.

The process that i followed was to create an MSDE database using the version installed by SBS2003 (SQL 2000 i believe). I then started the service as normal and proceeded with the install. After the reboot and it asked me which tye of install i wanted, i chose the "use existing" (as per 4.1.4) at which point it found the SBSMONITORING database. I changed settings to tell it to use the BESMgmt instead but it will not create the required database. The install log shows what appears to be a common issue - Restart Time service as reported by another installed called George.

Restarting and trying to create a database from scratch had exactly the same result. Following the answers that worked for GeorgeTuk I installed SQL 2005 Management and SQL 2005 Express and even resorted to running the Createdb.exe after changing the BESMgmt.cfg file to suit my needs - all of which results in the same error message

Just to prove that there are no serious issues with the server, I have this morning located, downloaded and installed BES Pro 4.1.4 (which I have used successfully for three years and countless small businesses) and guess what it worked 100%. However, I only have a single user licence for the 4.1.4 and the client has a multi-user licence for 5.0.1 which means i need to install the newer version.

When going through the install of 5, it doesn't like 4 being installed, so i have removed it to start the install of 5 again. It won't use the database created by v4 even though I have listed in Add / Remove Programmes an SQL Server Desktop Engine (BESMGMT) and in Services I have an MSSQL$BESMGMT running.

If i choose to create a new blackberry configuration database, it detects SQL Native client (9.00.3042.00), SQL 2008 Native client (10.1.2531.0) and SQL Server (version 8.00.1100)

I have again tried to install the software and chosen to install the SQL 2005 Express SP3 included with the installation set. With this install, after the reboot, the Database information screen now comes up with SERVERNAME\BLACKBERRY, DB name BESMgmt, Port 1433 but I still get the same issue i have had since yesterday -

The application cannot connect to the database server that you specified verify the following :-

Database info you provided is correct
database server is running
Port config matches the db instance you are connecting to
TCP is enabled for the SQL instance that hosts the DB

I have checked the admin rights for besadmin - in local admin, not in domain admin, has SQL admin rights in SQL Surface area wotsit but still will not latch onto a database.


I am rapidly losing patience with this - if the install from RIM doesn't create the necessary links correctly for the install then what else will ?

Many thanks for any assistance given or thoughts on suicide methods. Nine hours to install a "new" version of something that took an hour isn't right.

[nobody7290]

Have you tried, what happens if you allow the installer to use the SBSMONITORING instance ?

The installer will then create a BESmgmt in that instance.

[jkh1]

Hi - thanks for the sole reply !!

Since installing the "included" SQL, i have no way of changing back to SBSMonitoring. The server name is now greyed out and shows FSMSBS1\BLACKBERRY

[nobody7290]

If you uninstall the server, and, remove the program directory, then, use regedit to remove everything under hklm/Software/research in motion
Remote the sql 2005,
You should be able to select a existing sql server again.

Btw. I dont see a problem using the sbsmonitoring instance. I installed a server this way accidentialyl a few years ago, and, it still is running fine.

[jkh1]

Hi again nobody,

I am not sure that i didn't try that yesterday, but i am still wondering why i cannot connect to the database. Presumably i am missing something obvious as the version 4 will install to the MSDE database I created, but no database seems to be avaiable to v5 at install.

With over 100 people being good enough to look at my cry for help, I had hoped some learned guru would be able to call me a dozy wombat and tell me which regkey needed a modification !

thanks

[nobody7290]

Have you:
Database info you provided is correct
database server is running
Port config matches the db instance you are connecting to
TCP is enabled for the SQL instance that hosts the DB

?

Still I think it would be a good test to check if you can use the SBSMONITORING database. If that works you know at least the problem is not the Database or BESx.

[jkh1]

Re database connection details. The last attempt was to allow the installer to install SQL and create the necessary settings for itself, so that after the reboot it has populated all the boxes by itself. I would have hoped that this would have been the guaranteed method of connecting to a database. I have probably overlooked something simple such as security or such like, but for the life of me cannot work out what or where.

Whilst i would be happy to uninstall everything and start again, I have no real faith in the connection to SBSMONITORING working any better than the current array of databases. BES professional 4.1.4 installed 100% but I dont think it will be possible to aquire new codes from RIM now that they have provided Express codes to my client.

Thanks though for the support. If i find the solution i will let you know.

[nobody7290]

Check again the Database settings:
set a static port not equal to the SBSmonitoring instance ( >1024 which is not used)
mode: windows trusted
better manually delete the BESmgmt database you created before making another try.
check if TCP/IP protocol is enabled on all interfaces (or, on the interface where the Server will connect)
try again