Lansweeper Service Running - 9254 not listening on netstat

[MatthewNos]

I've used netstat -a to see if 9254 was listening , it is not. I've checked services and the lansweeper service is running.
I did the upgrade properly from freeware to premium with no problems.
My error log reads as follows :

1/22/2009 1:15:57 PM : Database connection successful, starting up service

1/22/2009 1:30:35 PM : Cannot connect to database, check your config file, will try again in 1 minute
-------------------------------------------------------------------------
Cannot open database "Lansweeper32" requested by the login. The login failed.
Login failed for user 'lssqluser32'.
1/22/2009 1:31:36 PM : Database connection successful, starting up service

1/22/2009 1:54:42 PM : Stopping service

1/22/2009 2:02:18 PM : Cannot connect to database, check your config file, will try again in 1 minute
-------------------------------------------------------------------------
A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server)
1/22/2009 2:03:33 PM : Cannot connect to database, check your config file, will try again in 1 minute
-------------------------------------------------------------------------
A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server)
1/22/2009 2:04:47 PM : Cannot connect to database, check your config file, service will be stopped
-------------------------------------------------------------------------
A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server)

I have pipes enabled as well as TCP/IP
I can log into the GUI using integrated login,
The connection Tester works :
Ping test OK
-----------------------------------------------
Remote registry test OK
-----------------------------------------------
Remote WMI access test OK
-----------------------------------------------
Remote \\127.0.0.1\c$ access test OK

Here is my command line :
C:\Program Files\lansweeper32\lslcient>lsclient server
Lansweeper client
-----------------
Connecting...
Failed

C:\Program Files\lansweeper32\lslcient>lsclient IP
Lansweeper client
-----------------
Connecting...
Failed

C:\Program Files\lansweeper32\lslcient>lsclient server.domain.com
-----------------
Connecting...
Failed

I can log into the web browser using
http://server/lansweeper32/

What am I doing wrong? I can't seem to find the answer in the forum that fits.
I am using SQL Express 2005.
I have tried 2008 and had more problems, so i reverted to 2005.
Suggestions?

[MatthewNos]

when i try to upload the file unaltered it says that it is an invalid file type.
Also, I changed the initial catalog name to "lansweeper32" and it still doesn't connect to the database.
I have then restarted the server and tried to connect using LSclient, and it still has the failed error.
I changed it to the database name SQLEXPRESS (that's the db name) and it didn't connect using that either.
-m

[Hemoco]

Could you explain this?

You've done a clean install of version 3.2.

The database name in version 3.2 is called "lansweeper32" (hardcoded)
Yet your config file points to initial catalog = Lansweeper instead of "lansweeper32"

Also please upload your config file unaltered.

[MatthewNos]

Ok here is the file

[Hemoco]

By attach I mean: press the attach button after posting and upload the file.

You've done a clean install of version 3.2.

The database name in version 3.2 is called "lansweeper32" (hardcoded)
Yet your config file points to initial catalog = Lansweeper instead of "lansweeper32"

[MatthewNos]

Here is my config file, not sure what you mean by attach, but I will put it in code brackets.
:

<?xml version="1.0" encoding="utf-8"?>
<configuration>
  <appSettings>
    <add key="ConnectionString" value="Persist Security Info=False;Data Source=127.0.0.1;Initial Catalog=Lansweeper;User ID=lssqluser;Password=" />
    <add key="ConcurrentThreads" value="20" />
    <add key="ListenPort" value="9524" />
    <add key="Activescanning" value="1" />
  </appSettings>
</configuration>

Also, the user lssqluser does exist. I logged into the GUI properly with that user.

[Hemoco]

Your service is running but it cannot connect to the database (it also couldn't connect in the freeware mode)

Cannot open database "Lansweeper32" requested by the login. The login failed.
Login failed for user 'lssqluser32'.

Could you please attach your lansweeperservice.exe.config file (attach, not paste)

Also check your sqlserver if a user lssqluser32 exists, if it it owner of the database Lansweeper32 and if the password is correct with the one in the config file.

[nerditup]

I think i'm experiencing the same problem you are. I just installed it for the first time on a clean Server 2003 (with updates) machine. I try to run lsclient on the server or on any other machine and it fails. I can get to the web interface from any machine, but that won't help me since I can't get any computers scanned.

i'm also using the domain administrator as the user. i'm not sure what else to try since the documentation is sparse. i am really pumped about getting the premium version, but i'm not going to spend the money if the free version doesn't even work.

[MatthewNos]

No sir, I started from 3.2, then replaced the service when I upgraded to PRO, it has never worked even on non-pro mode either.
I have started from scratch 2 dozen times, and end up the same way, the port isn't being listened to, and the service seems up and running.
I have stopped the service, and when I try to restart the service it times out.
I am using the domain administrator as the user i.e. domain\administrator for the service.

[Cobra7]

I'm not sure, but if you were like us and used 3.1 then upgraded to Pro 3.2, our SQL database stayed at Lansweeper31. You could try that, but only a guess.