QlikViewServer - how to track it over Christmas

[datanibbler]

Hi,

we have a very current problem here:

Probably because of our version of QlikViewServer - we don't know for sure - it repeatedly stops altogether - no more reloads are executed until we restart it all. A ticket with QlikTech is open because of this, but I guess we'll just have to upgrade to the newest version.

The issue is, that won't be done until we have a cconsultant on site which in turn won't happen before the end of January.

Now the Christmas holidays are approaching and the two of us - we only have two QlikView_developers - are out for a while.

Moreover, when the QlikView_Server stops altogether, the emails sent by the QMC about reload_failures are not triggered, so unless someone actually looks at the QMC, nobody will notice.

I think we'll have to insert someone else into the group of "QlikView_administrators" so that he will be able to look at the QMC.

Does anyone know another way we could do that?

Thanks a lot!

Best regards,

DataNibbler

[#2]

It's not the greatest solution in the world, but you could just have a job set up with alerting enabled in the application to email you every hour.  If you stop getting that email, you could assume your server has stopped working.

[prieper]

You may watch the server via remote control,

else create a batch to restart the server at regular intervals (triggered by WINDOWS-scheduler).

This might ensure, that even without watching, the server might get restarted once a day (or each 12 hours), thus you may loose not that much production-time ...

we use a script like fllws:

:

*******************************************************************************************

:

***

***

:

***

Start/Stop the QlikView-Server

***

:

***

in order to free memory / supposed to run daily at midnight

***

:

***

***

:

*** added stopping of all services (recommended by QlikTech 20140506                    ***

:

*******************************************************************************************

:	SET CalDirectory= "C:\ProgramData\QlikTech\QlikViewServer\"
	SET UserCal= "C:\ProgramData\QlikTech\QlikViewServer\CalData.pgo"
	SET BorrCal= "C:\ProgramData\QlikTech\QlikViewServer\BorrowedCalData.pgo"

:	Stop Servers
	net stop qlikviewserver
	net stop QlikviewWebserver
	net stop QlikviewManagementService
	net stop QlikviewDirectoryServiceConnector

:	Wait a moment
	ping -n 31 127.0.0.1 > NUL

:	Start the servers
	net start qlikviewserver
	net start QlikviewWebserver
	net start QlikviewManagementService
	net start QlikviewDirectoryServiceConnector HTH Peter

[datanibbler]

Thanks! Yes, that solution seems very worth trying.

We'll just have a small app that must fail every time, so we should get email.

Can we forward that email or re-route it to a private account?

[datanibbler]

Hi Peter,

thanks for the suggestion! I think it's good - QlikTech has told us the server should be restarted regularly, though daily does seem a bit much - but it wouldn't be for long. Only until we can update to the newest version at the end of January.

Only, that is not up to me - I've already made a similar suggestion to our IT_guys to have a batch to restart the server once a month and they told me that they won't do that - don't ask me why, it's not open to comprehension, nor to discussion 😉

[Peter_Cammaert]

BTW If you want to know your current QV version, visit one of the last pages of the QMC (System->About). Every service is listed with its build number. Post the "Product Version" of QlikView Server (QVS) and I'll get back to you with a release number.

[datanibbler]

Thanks Peter!

The release number is at the moment not critical. We will update to the latest version, but only at the end of January when we have an external consultant onsite.

I have in the meantime tested and confirmed that the QlikView_Server does send error_emails to private email adresses.

That is one step further towards a working solution.

Best regards,

DataNibbler

[prieper]

Hi,

actually we do a restart each night. I always feel uncomfortable to have the day starting with a high amount of RAM still blocked / not released by QlikView. Was told, that all files are unloaded, but the server still keeps the cached selections in memory. Was also told, that this would not harm the performance, but .....

In order to prevent a failure due to non-starting of a service, have made another batch, which runs 10 mins after the above and which contains only the starting params. Thus in case that - for whatever reason - some service does not start, it will be triggered in a second batch to start.

HTH Peter

[flipside]

You only need to stop/start the SERVICES not the SERVER, if your IT think it's the latter I can understand their concerns, but restarting services shouldn't be an issue.

Incidentally I run my services reboot via a scheduled task in QMC rather than Windows Scheduler. If you have the ability to get a batch file on the server (with the net stop and net start commands), a new QVW doc on the server (to execute the .bat/.cmd file) and have rights in QMC to schedule it, then you may not need IT support.

flipside

[datanibbler]

Hi flipside,

that is an excellent idea! So I have the impression, since several people have now said so, that restarting the services on a regular basis is no out_there idea.

Does restarting the services also free up the RAM? I know that QlikView keeps the RAM even when it's not needed anymore, so the RAM_usage slowly builds up over time.

Unfortunately, I cannot create a batch file on the server to stop and start the services, but maybe my supervisor can do that.

Let's see.