Skip to main content
Announcements
Have questions about Qlik Connect? Join us live on April 10th, at 11 AM ET: SIGN UP NOW
cancel
Showing results for 
Search instead for 
Did you mean: 
korsikov
Partner - Specialist III
Partner - Specialist III

failed to start QRS after update to 1.1.0

i'm just update my Sense Server 1.0.2 to 1.1.0 and as a result does not work Server because  failure Qlik Sense  repository service.

I attach error log. The text identifies the main cause.

Fatal exceptionObject reference not set to an instance of an object.?vAn exception was thrown while invoking the constructor 'Void .ctor()' on type 'DatabaseContext'. ---> Object reference not set to an instance of an object. (See inner exception for details.)
7 Replies
korsikov
Partner - Specialist III
Partner - Specialist III
Author

not found a solution. Export all applications, and made a clean installation of the central node and the second node. Import applications back, do the cluster configuration

celindho
Partner - Creator
Partner - Creator

Hi,

How did you export all your applications? Since QMC is down, i can't get to them that way...

-Christian

korsikov
Partner - Specialist III
Partner - Specialist III
Author

backups, regular backups save administrator ass. I use a virtual server, or before installing I do spanshot

But there is always a back-up method. just copy the application from c:\ProgramData\Qlik\Sense\Apps\ the directory, add them to the expansion of QVF and open a desktop or again import to server..

celindho
Partner - Creator
Partner - Creator

Ok, Thanks. This was our own internal test server so we did not have backups running. No big harm done, as most of the stuff was garbage anyway

-Christian

korsikov
Partner - Specialist III
Partner - Specialist III
Author

I have exactly the same situation. Developers tortured him with their applications. It is better to break the test server that would production everything worked well.

celindho
Partner - Creator
Partner - Creator

Hi, I have now updated an other site to 1.1. without problems. I'm now trying to pinpoint what might make a difference here.

Can you recall if you manually shut down the Qlik Services before running the update?

On the site where update failed, I had shut down the services before upgrading whereas on the site where update was a success, I did not shut down the services manually.

BR,

-Christian

korsikov
Partner - Specialist III
Partner - Specialist III
Author

tried to stop all services before upgrading. All the same, the error has not changed. The server does not work.