cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
techreg
Engaged Sweeper III
We have a Win2003 Enterprise Edition x64 server where it has been installed SQL 2008 Express Edition. The SQL server has been configured as indicated in the LS manual (TCP/IP and Named Pipes connections enabled, SQL Browser service started), yet the LS installer is not able to connect to the SQL server.

I've checked that I am able to connect to the SQL server, both locally and from another workstation, using the same db login credentials (SQL mode, since the server is not in a domain for the time being), therefore it has to be something in the LS installation procedure. In an old message of this forum I've read that SQL 2008 Express Edition was not yet supported by the LS installer, but is it still the case? Is there a workaround? I wouldn't like to revert back to SQL 2005 Express Edition (which worked perfectly on a x86 server) because the SQL 2005 Report Service doesn't exist for x64 (there is a kludgy workaround that I don't like too much).

Thanks!
2 REPLIES 2
Hemoco
Lansweeper Alumni
2008 should work, could you post screenshots of the installer error and the working manual connections please.
techreg
Engaged Sweeper III
Well, I've found what was wrong.

Apparently (because I don't remember what occurred when I installed LS against SQL 2005 Express), when the Lansweeper installer looks for a SQL server, in the case of the SQL 2008 Express it doesn't select automatically the default db instance, hence the combo box is filled only with the server name instead of server\dbinstance. I overlooked for awhile this fact, hence the request (never ever install something at end of a hard day...)

I think that, even if the dialog states the correct syntax for the string, the server lookup function should fill the field correctly for the user.

Well, just my 2 cents. Thanks anyway for the answer.