Skip to main content
cancel
Showing results for 
Search instead for 
Did you mean: 
Shahzad_Ahsan
Creator III
Creator III

Qlik Sense services cannot start

Hi

I have stucked in an issue. My Services are stopped automatically.

I have restarted my Server but the services couldn't start. I am trying manually then also it is failed. The snapshot error comes when triying to start manually

Error1.jpg

6 Replies
rubenmarin

Hi Shahzad, I haven't found this error myself but seems that files are missed.

Check if repository exists in  %ProgramFiles%\Qlik\Sense\Repository\Repository.exe

Also data has to be in %ProgramData%\Qlik\Sense\Repository

https://help.qlik.com/en-US/sense/April2018/Subsystems/PlanningQlikSenseDeployments/Content/Deployme...

Shahzad_Ahsan
Creator III
Creator III
Author

Hi Ruben

"Repository.exe" file does not exist in this path %ProgramFiles%\Qlik\Sense\Repository\Repository.exe

But here %ProgramData%\Qlik\Sense\Repository  , lots of folder exists

rubenmarin

That file should exist, also a Repository.exe.config, wich the configuration file of the service. If your version is old maybe is located in other folder.

Both the message and the missing file points in the same direction: the file is lost so there is no way the service starts. I'm not sure if a repair install can solve this. You can try it if you have a backup to return to your actual (or working) point, or contact support if you are not sure.

Shahzad_Ahsan
Creator III
Creator III
Author

I have repaired qlik sense. Now the services are started.

But still hub is not opening

Shahzad_Ahsan
Creator III
Creator III
Author

Sequence#         Timestamp         Level     Hostname           Logger  Thread  Id            ServiceUser        Message                Exception            StackTrace          ProxySessionId Id2

1              20180521T004748.660+0300       INFO      KAMCQLIKSENSE             System.Repository.Repository.QRSMain 7                3ac04257-2adb-42fc-a6b4-25db2580d916              NT AUTHORITY\SYSTEM [DatabaseTimeout set to: 0 seconds ]                                                                3ac04257-2adb-42fc-a6b4-25db2580d916

2              20180521T004748.722+0300       INFO      KAMCQLIKSENSE             System.Repository.Repository.QRSMain 7                9c0447e2-a3b8-4dd1-9ac0-1a3e0b8fa9bf              NT AUTHORITY\SYSTEM [ExecutionResultsAmountKept set to: 3 items. ]                                                             9c0447e2-a3b8-4dd1-9ac0-1a3e0b8fa9bf

3              20180521T004748.722+0300       INFO      KAMCQLIKSENSE             System.Repository.Repository.QRSMain 7                339aee54-3572-4d85-8ff3-5fcb6f745308                NT AUTHORITY\SYSTEM                [RunExecutionResultsTriggeredCleaningAgent set to: False. ]                                                        339aee54-3572-4d85-8ff3-5fcb6f745308

4              20180521T004748.722+0300       INFO      KAMCQLIKSENSE             System.Repository.Repository.QRSMain 7                294e6965-dc5c-4ada-bf20-13a5b3c27834              NT AUTHORITY\SYSTEM                [ExecutionResultsCleaningAgentIntervalInMinutes set to: 720 minutes. ]                                                294e6965-dc5c-4ada-bf20-13a5b3c27834

5              20180521T004748.722+0300       INFO      KAMCQLIKSENSE             System.Repository.Repository.QRSMain 7                ae72e234-2124-4e70-8971-a19319d81aab             NT AUTHORITY\SYSTEM                [ExecutionResultsDatabaseCleaningThresholdInDays set to: 7 days. ]                                                        ae72e234-2124-4e70-8971-a19319d81aab

6              20180521T004748.722+0300       INFO      KAMCQLIKSENSE             System.Repository.Repository.QRSMain 7                d3f8f8f6-e606-4f2d-ba9c-f7ad4f2e42b4 NT AUTHORITY\SYSTEM [StartupWaitForDatabaseSeconds set to: 300 seconds]                                                              d3f8f8f6-e606-4f2d-ba9c-f7ad4f2e42b4

7              20180521T004748.722+0300       INFO      KAMCQLIKSENSE             System.Repository.Repository.QRSMain 7                a66a51a3-4e18-4338-8031-ff6806cc7a0f                NT AUTHORITY\SYSTEM [EnableRestoreHostname set to: False. ]                                                  a66a51a3-4e18-4338-8031-ff6806cc7a0f

8              20180521T004748.800+0300       INFO      KAMCQLIKSENSE             System.Repository.Repository.QRSMain 7                0cb7f361-fd2e-490e-978d-921d6615ed26              NT AUTHORITY\SYSTEM Initializing..                                                         0cb7f361-fd2e-490e-978d-921d6615ed26

9              20180521T004748.800+0300       INFO      KAMCQLIKSENSE             System.Repository.Repository.QRSMain 7                2852e124-96dc-4936-937b-44b1437b946a            NT AUTHORITY\SYSTEM [Running with floating central]                                                   2852e124-96dc-4936-937b-44b1437b946a

10           20180521T004748.862+0300       INFO      KAMCQLIKSENSE             System.Repository.Repository.QRSMain 7                3c7c0c23-d9b1-455a-b11f-d4d5a7a4f508               NT AUTHORITY\SYSTEM Waiting up to 300 seconds for database to respond                                                      3c7c0c23-d9b1-455a-b11f-d4d5a7a4f508

11           20180521T005248.840+0300       ERROR  KAMCQLIKSENSE             System.Repository.Repository.QRSMain 7                4b73ba61-3eb4-4c7c-b710-48e4e45ef61b             NT AUTHORITY\SYSTEM Fatal exception during startup                Waiting for database timed out after 0 seconds     at Repository.Core.Database.DatabaseConnectionMonitor.WaitForDatabase(IDatabaseConnection databaseConnection, Int32 intervalMilliseconds, Int32 timeoutMilliSeconds)↵↓   at Repository.QRSMain.<WaitForDatabase>b__32_0(IDatabaseConnectionFactory databaseConnectionFactory)↵↓   at Qlik.Sense.Common.Ioc.WorkScope.Work(Action`1 action)↵↓   at Repository.QRSMain.Run(String[] args)                         4b73ba61-3eb4-4c7c-b710-48e4e45ef61b

Please check the error in log file

rubenmarin

Seems it fails connecting to the repository database. I think the best option is to open a case with support and look at why the fies were lost in the first place.