Installer stalled for hours?

[SirArion]

Ran the setup for 4.0 on our premium Lansweeper server, the SQL database is hosted on another server.

Setup seems to have stalled at this point and I am unsure if I should kill this or just let it go?? Been running for 4hours against a db of 2.5gb.

"Setup is updating your database to the latest version"
Currently running sql code:
-- end check all constraints
-- PRINT 'Changing computername keyfield'
DECLARE @computername nvarchar(300)
DECLARE @TEL int
DECLARE @TEMPSQL nvarchar(4000)
SET @TEL = 1
Declare Allcomputers cursor for
select computername from tblcomputers

open Allcomputers
fetch next from Allcomputers into @computername
WHILE @@fetch_status = 0
BEGIN
SET @TEMPSQL = N'update tblcomputers set computername = ' + '''' + cast(@TEL as varchar) + '''' + ' where computername = ' + '''' + @computername + ''''
EXEC sp_executesql @TEMPSQL

SET @TEL = @TEL + 1
FETCH NEXT FROM Allcomputers INTO @computername
END

CLOSE Allcomputers
DEALLOCATE Allcomputers

[sticky]

Lansweeper wrote:

sticky wrote:
About 31 hours so far 😞

How big is your database.
How much computers.
Do you see any sql server activity?

8Gb, about 9,500 computers.
No I'm not seeing any SQL server activity. SQL profiler is showing no activity against the lansweeper db.

lansweeperdb process is showing as suspended on PAGEIOLATCH_SH.

Still running btw, almost 48 hours now. Beginning to lose hope here...

[Hemoco]

In beta tests the upgrade took 5-10 hours for some users (depending on the database size)
So keep it running.

[d1eter]

Lansweeper wrote:
In beta tests the upgrade took 5-10 hours for some users (depending on the database size)
So keep it running.

5 hours is the minimum in your beta tests..?

I was expecting "one minute up to one hour" as stated in the installation message..

[Hemoco]

d1eter wrote:
5 hours is the minimum in your beta tests..?

5-10 This was the maximum in the beta tests.
How long is it running?

[d1eter]

in our system.., which only has 800MB of lansweeperdb, the database update also seems to stalled at that same point.

any info from Lansweeper officials..?

I don't think it's normal to behave like that...

[nathan_budd]

Hi all,

My database is much smaller, only 500 systems and I thought mine had stalled too. After about an hour however, it kicked off again pretty quickly. I expect it'll come good if you wait it out.

[efosshaug]

Hi all.

Same problem here, been running on this script for 3 hours now . 4GB database on seperate SQL-server, about 6000 computers.

Will let it run until tomorrow(in Norway)

Hope someone from Lansweeper can advice on if it should run this long or if I should abort and restore?

Espen

[amagner]

SirArion wrote:
Ran the setup for 4.0 on our premium Lansweeper server, the SQL database is hosted on another server.

Setup seems to have stalled at this point and I am unsure if I should kill this or just let it go?? Been running for 4hours against a db of 2.5gb.

"Setup is updating your database to the latest version"
Currently running sql code:
-- end check all constraints
-- PRINT 'Changing computername keyfield'
DECLARE @computername nvarchar(300)
DECLARE @TEL int
DECLARE @TEMPSQL nvarchar(4000)
SET @TEL = 1
Declare Allcomputers cursor for
select computername from tblcomputers

open Allcomputers
fetch next from Allcomputers into @computername
WHILE @@fetch_status = 0
BEGIN
SET @TEMPSQL = N'update tblcomputers set computername = ' + '''' + cast(@TEL as varchar) + '''' + ' where computername = ' + '''' + @computername + ''''
EXEC sp_executesql @TEMPSQL

SET @TEL = @TEL + 1
FETCH NEXT FROM Allcomputers INTO @computername
END

CLOSE Allcomputers
DEALLOCATE Allcomputers

Same problem here. DB is abt 1.8 - 2.0GB and I let it run for over 3 hours before I killed it and went back to LS 3.5xxx (techs and support people screaming at me) . SQLExpress 2005 though. Maybe that has something to do with it? Support email sent, awaiting some kind of reply. May try again tomorrow.

[sticky]

Oops your comment made me go back and check... was looking at the log file size! doh. Have updated my original post with the correct size of 8Gb.

More info: Activity monitor is showing the lansweeperdb process currently as 'suspended'. Am trying to find out why...

[KHabershon]

Whoa 20 hours .. LOL that's a long time for a 1.5gb db, ugh I have 7k systems!