Help! Can't install new BES 4.1.4 - SQL error "
 

Help, I am trying to install BES 4.1.4 on a Windows 2003 SBS server fully patched. I get up to this step:

http://img522.imageshack.us/img522/9...4052549xd0.png

I have downloaded the latest SQL Server Express 2005 and ran it with the default install options, during which everything completed successfully and did not indicate any problems. However I cannot get past this stage. I am really desperate, can anyone help me through here? Thanks!

server is "besx_4.1.4.exe" downloaded direct from RIM.

Take a closer look at your SQL data and backup paths... "MSSQL.1". You sure you are running default instance?

Is the service SQLSERVER Service started? Can you telnet to SERVER01 at port 1433 and be returned a blank screen with a blinking cursor?

Same folder structure as i have and i am fairly sure i just accepted the defaults as i went.

Yup, SQL 2005 does this; even Std / Ent. editions with the ".1" stuff for the default instance.

i may well be wrong but my memory is prompting me that i needed the machine name as well as the SQL instance, even locally.

I am afraid to uninstall/reinstall the SQL server because isn't SQL express used for some SBS2003 native functions? I don't want their server to go down or get its settings screwed up irrevocably because I tried to install the BES. :?

I checked and yes the SQLEXPRESS service is running. I tried stopping and restarting it, and then opening a TELNET session to localhost:1433 and it says "Connecting To localhost...Could not open connection to the host, on port 1433: Connect failed" so I guess that means its not working? I am dying on the vine here guys is there some tutorial or PDF guide I can follow for installing a BES including the prerequisites?

from a command prompt:

telnet server01 1433

and then press enter

The screen should go blank and a blinking cursor will appear if you've connected successfully.

well I can't telnet to the localhost 1433. It seems like the service is running and I see it in services.msc and task manager. How can I troubleshoot this guys? This customer is getting antsy now. :sad:
http://img175.imageshack.us/img175/7...5040428ue0.png

Comparing the screen shots i am guessing the machine is SERVER01, and the SQL instance is SQLEXPRESS, try SERVER01\SQLEXPRESS in the database field, may not work i am no expert but it is ringing very faint bells from my own install a few months ago.

I might be barking up totally the wrong tree here, but BlackBerry Search Results

I think that David got it, the default instance of MS SQL Server 2005 Express is called SQLEXPRESS. The name is listed in the Services, also, there are 3 sqlserver.exe's running. If there is only one SQL instance then it should be called SQLEXPRESS. Every instance has a name and they will be listed in the Services screen. Try telnet server01\SQLEXPRESS 1433, and try using that as your DB server in the installation.

I don't think you can use SQL 2005 Express with 4.1. If I am not mistaking you have to use MSDE or SQL 2000, 2005 not Express.

And try to point to the server\instance.

You can run SQL 2005 Express with BES 4.1 other than using SQL Enterprise, 2000, and MSDE.

I thought that it didn't work with MDS Services, though? Not that we know that luckman212 selected "with MDS Services" as the install type, of course - if not, it's not an issue.

Maybe I'm missing something here, but I'm not sure why an extra install of SQL 2005 Express was needed. Any reason that the built-in MSDE 2000 in SBS 2003 wouldn't have done the job? Could that be what's causing the unusual SQL instance path? I'd have expected "C:\Program Files\Microsoft SQL Server\MSSQL\Data" myself. The .1, .2 and .3 directories exist, but (on a non SBS server) seem to contain stuff for the OLAP and other new stuff that's part of 2005.

i am running BES on SQL Express 2005, same box as the BES, and i have the .1 path same as the OP, in the .1 folder i have a MSSQL folder. This is on a standard 2003 server.

My mistake, MDS Services doesn't work with SQL Express.