Stuck on "DLM Dashboard is just starting up"
vahtis
Posts: 2
Hi,
after updating to latest version DLM Dashboard is not opening. It is stuck on first screen.
Loading…
DLM Dashboard is just starting up
I have restarted services with no help. I did even restart the whole server, but no help there either.
Any ideas what to try next.
after updating to latest version DLM Dashboard is not opening. It is stuck on first screen.
Loading…
DLM Dashboard is just starting up
I have restarted services with no help. I did even restart the whole server, but no help there either.
Any ideas what to try next.
Tagged:
Comments
Sorry for the issue you are having with the DLM Dashboard starting. We have opened a ticket for this issue so we can further troubleshoot what could be happening. I'll be responding there as soon as I finish this post.
Red Gate Software
US Product Support
I am seeing the same problem.
After a power failure and restart of my server, Dashboard will not load.
Loading…
DLM Dashboard is just starting up
Any suggestions on what the issue is and how to resolve it?
Thanks.
It has now magically fixed itself, I guess I just needed to wait a little longer.
2016-10-27 16:48:40.465 -04:00 [Fatal] An unhandled exception occurred.
System.AggregateException: One or more errors occurred. ---> Autofac.Core.DependencyResolutionException: An exception was thrown while executing a resolve operation. See the InnerException for details. ---> One or more errors occurred. (See inner exception for details.) ---> System.AggregateException: One or more errors occurred. ---> Raven.Abstractions.Exceptions.IndexDoesNotExistsException: Could not find index named: DbConfigsOrphanStatus
at Raven.Storage.Esent.StorageActions.DocumentStorageActions.IndexLastUpdatedAt(String name)
at Raven.Database.DocumentDatabase.<>c__DisplayClass8f.<Query>b__84(IStorageActionsAccessor actions)
at Raven.Storage.Esent.TransactionalStorage.ExecuteBatch(Action`1 action, EsentTransactionContext transactionContext)
at Raven.Storage.Esent.TransactionalStorage.Batch(Action`1 action)
at Raven.Database.DocumentDatabase.Query(String index, IndexQuery query, CancellationToken externalCancellationToken, Action`1 headerInfo, Action`1 onResult)
at Raven.Client.Embedded.EmbeddedDatabaseCommands.<>c__DisplayClass27.<StreamQuery>b__21()
at System.Threading.Tasks.Task.Execute()
--- End of inner exception stack trace ---
It seems there is an issue with the RavenDB that is used internally by DLM Dashboard.
The best option here will be to delete the RavenDB which will unfortunately erase all previous history and force DLM Dashboard to completely recreate the database with the necessary indexes. Can you please:
• Open your services panel and stop all three DLM Dashboard services (DLM Dashboard Monitoring Service, DLM Dashboard Storage Service, and DLM Dashboard Web Server)
• Go to C:\ProgramData\Red Gate\SQL Lighthouse\
• Rename the RavenDB folder to RavenDBOld (if this was indeed a new install though, you can just delete the RavenDB folder)
• Restart the DLM Dashboard services and then try loading DLM Dashboard again
I hope this helps!
Kind regards,
Alex
Have you visited our Help Center?
Follow Alex B.'s instructions above, except with some differences - we are going to keep the data and ditch the indexes, forcing DLM Dashboard to rebuild the corrupted indexes.
-Open your services panel and stop all three DLM Dashboard services (DLM Dashboard Monitoring Service, DLM Dashboard Storage Service, and DLM Dashboard Web Server)
-Go to C:\ProgramData\Red Gate\SQL Lighthouse\
-Go to the RavenDB folder and delete the following folders:
1) CompiledIndexCache
2) IndexDefinitions
3) Indexes
-Open your services panel and start all three DLM Dashboard services (DLM Dashboard Monitoring Service, DLM Dashboard Storage Service, and DLM Dashboard Web Server)
-Browse to the DLM home page. It will show the same message from before "DLM Dashboard is just starting up" - but this time it's actually rebuilding the missing indexes. Be patient - depending on the size of your Raven DB it could take a few minutes. Ours was 1.4 gigs, and it took about 3 minutes.
-You should end up with your DLM Dashboard fully working again, without having to rebuild.
Is there an option to increase the rebuilding-indexes-timeout ? The default is 30 minutes and my data file is 19GB and it crashes.
I had to Rename the RavenDB folder and start over (and lose all history)