Quantcast
Channel: Spiceworks Community - Latest topics
Viewing all articles
Browse latest Browse all 183865

Migrating Spiceworks data from 6.1.01100 to 6.2.00880

$
0
0

Hi,

We're in the process of moving Spiceworks to a new server. I've got v6.2.00880 installed on the new server, but the existing server / data is on 6.1.01100. I've followed the guide that was published in the Spiceworks forum to create the data backup and move the data / db folders to the new install, but Spiceworks is unable to start the service on the new server due to timing out when starting the service. This is an extract from the startup.log file.: -

spiceworks:in `eval'
spiceworks:in `load'I, [2013-03-28T10:28:11.502295 #2672] INFO -- : ---------- Setting up to run Spiceworks ----------
I, [2013-03-28T10:28:11.502295 #2672] INFO -- : root => C:/Program Files (x86)/Spiceworks
I, [2013-03-28T10:28:11.502295 #2672] INFO -- : app root => C:/Program Files (x86)/Spiceworks/pkg/gems/spiceworks-6.2.00880
I, [2013-03-28T10:28:11.502295 #2672] INFO -- : port => 9675
I, [2013-03-28T10:28:11.502295 #2672] INFO -- : https port => 9676
I, [2013-03-28T10:28:11.502295 #2672] INFO -- : https required => false
I, [2013-03-28T10:28:11.502295 #2672] INFO -- : version => 6.2.00880
I, [2013-03-28T10:28:11.502295 #2672] INFO -- : environment => production
I, [2013-03-28T10:28:11.502295 #2672] INFO -- : verbose => false
I, [2013-03-28T10:28:11.502295 #2672] INFO -- : Starting spiceworks server
I, [2013-03-28T10:28:11.502295 #2672] INFO -- : Starting spiceworks server as a service
I, [2013-03-28T10:28:11.517919 #2672] INFO -- : Service state: 0
I, [2013-03-28T10:28:11.517919 #2672] INFO -- : Service state: 0
#
C:/Program Files (x86)/Spiceworks/pkg/gems/spiceworks_lib-6.2.00880/database/migrator.rb:13:in `initialize'
C:/Program Files (x86)/Spiceworks/pkg/gems/spiceworks_lib-6.2.00880/database/migrator.rb:13:in `new'
C:/Program Files (x86)/Spiceworks/pkg/gems/spiceworks_lib-6.2.00880/database/migrator.rb:13:in `schema_versions'
C:/Program Files (x86)/Spiceworks/pkg/gems/spiceworks_lib-6.2.00880/database/migrator.rb:41:in `should_migrate?'
C:/Program Files (x86)/Spiceworks/pkg/gems/spiceworks_lib-6.2.00880/command/migrates_database.rb:29:in `check_and_migrate_database'
C:/Program Files (x86)/Spiceworks/pkg/gems/spiceworks_lib-6.2.00880/command/service.rb:35:in `run'
C:/Program Files (x86)/Spiceworks/pkg/gems/spiceworks_lib-6.2.00880/command.rb:13:in `block in run'
C:/Program Files (x86)/Spiceworks/pkg/gems/spiceworks_lib-6.2.00880/command.rb:12:in `each'
C:/Program Files (x86)/Spiceworks/pkg/gems/spiceworks_lib-6.2.00880/command.rb:12:in `run'
C:/Program Files (x86)/Spiceworks/pkg/gems/spiceworks-6.2.00880/bin/loader.rb:46:in `

'
spiceworks:in `eval'
spiceworks:in `load'

The line regarding 'unable to open database file' concerns me. Would the differing versions cause that? It so, how would I best get Spiceworks to recognise my data please?

Just some additional info: the new server is running Windows Server 2012, the old one is Server 2003. The new Spiceworks install did get as far as a login screen when I first installed it.

There's a good chance I won't look at this until after Easter, so have a good one!

Cheers.

Phil.


Viewing all articles
Browse latest Browse all 183865

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>