Had problems upgrading msde db so thought id try installing sql server 2005 on another server and install BES to see whats involved but im having some basic problems...SQL from cd/network wont install!

I am getting this error...

TITLE: Microsoft SQL Server 2005 Setup
------------------------------

There was an unexpected failure during the setup wizard. You may review the setup logs and/or click the help button for more information.


Details
Product: SQL Server
ID: 50000
Source: setup.rll
Version: 10.0
Component: SQL Server Native Client
Message: A network error occurred while attempting to read from the file '%.*ls'.

Explanation
An attempt was made to install (or update) SQL Server Native Client on a computer where SQL Server Native Client is already installed, and where the existing installation was from an MSI file that was not named sqlncli.msi.

User Action
To resolve this error, uninstall the existing version of SQL Server Native Client. To prevent this error, do not install SQL Server Native Client from an MSI file that is not named sqlncli.msi.

That machine already has some SQL Server client stuff on it. Uninstall all SQL Server bits through add/remove and then reboot and start again. I had to argue with a guy the other day that this was the cause of his SQL Server install failure coz he couldn't see why the client tools affected the server tools. I guess some ppl have jst never used MS products before

when you say sql client stuff you mean anything that the cd may have installed up till the point of the crash because i have done this. Anything else i should uninstall?

When you look at add/remove i see sql server, native client, compatibility..., online docs...
Ive also tried uninstalling native client but it is required by the setup wizard thus when you re run the setup it will reinstall it for setup to run. it will then say its got native client installed and suggest i uninstall it....cue loop......

Sorry dude you have hit the limit of my SQL Server install knowledge, time to head to the MS forums . My guy had the exact same prob as you but after I said keep uninstalling SQL Server xxxx then start again it eventually worked. Only last thing to add is he is a local admin of the box he was installing on...

Did you enable file shareing?

cheers mate anyway, just seems very basic to be able to install from an official sql disc...Ive tried sql 'experts' who say uninstall native client but i say it needs it to install it..and so it goes round....

ok got it going, created db, installed bes. It connects to db ok but activations dont work.

Looking for more detailed Bes sql installations, where is a good one?

Have a search my friend and the threads will link you to the RIM db move guide. Did you remember to do the createdb bits (all in the guide before you ask!).

Any error messages you get upon activation? Please post them here.

im just testing various options atm 2008, sql, VM etc.

So I have a new server where i'll install sql server and besdb and bes so there are no moving etc, it's all new so trying to find the order in which to install. I installed sql, created db then installed bes and pointed it to the new sql db. This should be it should it not?

no errors just the rim dat email. Did all the permissions etc. In the sql server config manager it names protcols (all enabled) for MSSQLSERVER is this always the default name?

Please please do a search. There are plenty of threads here answering your questions, with links to all the RIM docs you need for this.

What do you mean 2008?

Compatability matrix
BlackBerry - BlackBerry Enterprise Server Compatibility

install guide?
BlackBerry - BlackBerry | Microsoft Exchange: BlackBerry Enterprise Server Pre-Installation Guide

Check out this document

http://na.blackberry.com/eng/deliver..._427146_11.pdf

and review the following chapter

"Setting up the database connection"

If you'd like to install BES on a single machine with SQL 2005, here's the way I'd do it:

Install Microsoft SQL Server 2005 Express Edition with Advanced Services (for the server and admin tools in one shot). During the SQL install, choose advanced options and set the default SQL instance to not be a named instance. This will allow you to refer to your SQL server as just the hostname. I'm not sure offhand, but I think it'll also default the SQL connection port 1433 instead of a dynamic port.

When the SQL install finishes, run the Surface Area Configuration tool from the Start menu and Click on Add New Administrator. Add a user in the upper-right corner (like domain\besadmin or something), select the SysAdmin role from the left, move it to the right, and hit OK. No need to reboot.

Start your BES install and choose SQL and remote SQL. Fill in the rest of your stuff, reboot, etc.

On reboot, when prompted for the SQL info, enter the hostname of the BES machine (since that's where SQL's running, right?) and Windows authentication. You're basically pointing the BES isntaller back at itself, if you look at a certain way... You should see the installer pause for a while as it searches for the BESMgmt database and then prompt you to create a new BESMgmt db.

Apologies if this has already been covered elsewhere...

- mike