Skip to main content
Announcements
Qlik Connect 2024! Seize endless possibilities! LEARN MORE
cancel
Showing results for 
Search instead for 
Did you mean: 
HamdiGA
Contributor II
Contributor II

Reload task fails without logs and work if manully started

Hello, 

(I'm using Qlik sense)

I have more than 20 applications to read, but the problème its many tasks failed to reload data with no log file. So every time I need to check the tasks and reload failed tasks manually. Anyone have a suggestion to resolve this problem?

Thanks 

 

HamdiGA_1-1626075995372.png

 

 

Labels (2)
8 Replies
MayilVahanan

Hi

There are many cases 

1. if you are running many jobs at the same time, it may failure

2. if QMC server memory is full or CPU Utilization reaches 100%, then it fails

3. If Section access are implemented, then if you not included the "SA_SCHEDULER ", it fails via QMC & it runs fine  via manual load.

4. Any folder permission might be missed out for the admin login (QMC)

Thanks & Regards, Mayil Vahanan R
Please close the thread by marking correct answer & give likes if you like the post.
Anil_Babu_Samineni

Can you please check this log and identify If you see this error?

Logfile path: C:\ProgramData\Qlik\Sense\Log\Engine\Trace\ServerName_System_Engine.txt

If you find this error,
<Your User ID> ExtendedException: Type '1013' thrown in file 'C:\Jws\engine-common-ws\src\AppObject\src\AppSerializer.cpp' in function '`anonymous-namespace'::AddScriptObject' on line '256'. Message: 'Unknown error' and additional debug info: 'Reload failed! AppScript is not yet available'
 
Please confirm this?
Please add me Anil_Babu_Samineni to interact faster when reply back. Speak low think High.

Before develop something, think If placed (The Right information | To the right people | At the Right time | In the Right place | With the Right context)
HamdiGA
Contributor II
Contributor II
Author

thank you 

But no I don't have this error in the Logfile, in revenge I have these lines at the time where tasks were supposed to start :

694 20210713T040033.318+0200 INFO fro1vhlqlik1 System.Engine.Engine 236 6502a376-638a-48eb-8d4e-a05a85a391cd AUTORITE NT\Système TheServer: Registering new server session 0 INTERNAL sa_scheduler 20210713T040033.318+0200 940 9624 0 20210712T143738.000+0200 6502a376-638a-48eb-8d4e-a05a85a391cd
695 20210713T040033.319+0200 INFO fro1vhlqlik1 System.Engine.Engine 49 a90e4b8b-057c-41f7-bf80-cfd1f5d79909 AUTORITE NT\Système QvContext: Setting JWT, payload: {"id":"UserDirectory=INTERNAL; UserId=sa_scheduler"} 0 Personal Me 20210713T040033.318+0200 12704 9624 91c19937-a0cd-4e79-9bb1-911f263eb0cf 20210712T143738.000+0200 a90e4b8b-057c-41f7-bf80-cfd1f5d79909
696 20210713T040033.324+0200 INFO fro1vhlqlik1 System.Engine.Engine 49 7b061f98-59c0-4986-92ac-8ca31beadef2 AUTORITE NT\Système QvSocket: Connected to server as user: 'UserDirectory=INTERNAL; UserId=sa_scheduler' for document: '/204dbfe5-c834-40ef-9084-35c8c8a412b6' on socket fe80::c6d:20fc:f50d:73bc:4747 <-> fe80::c6d:20fc:f50d:73bc:49322 with ttl: 0 0 INTERNAL sa_scheduler 20210713T040033.318+0200 940 9624 0 20210712T143738.000+0200 7b061f98-59c0-4986-92ac-8ca31beadef2
697 20210713T040033.325+0200 INFO fro1vhlqlik1 System.Engine.Engine 236 159393a5-2319-494b-b1a2-3782a129ba89 AUTORITE NT\Système Server: App Load: Beginning open of app 952a5e83-5ecb-44aa-b73c-34e67bb7e17b with user UserDirectory=INTERNAL; UserId=sa_scheduler and payload {"id":"UserDirectory=INTERNAL; UserId=sa_scheduler"} 0 INTERNAL sa_scheduler 20210713T040033.318+0200 12704 9624 91c19937-a0cd-4e79-9bb1-911f263eb0cf 952a5e83-5ecb-44aa-b73c-34e67bb7e17b 20210712T143738.000+0200 159393a5-2319-494b-b1a2-3782a129ba89
698 20210713T040033.330+0200 INFO fro1vhlqlik1 System.Engine.Engine 236 164c1051-2fe1-4a4d-912d-358bd7cba09c AUTORITE NT\Système DOC loading: Beginning load of document 952A5E83-5ECB-44AA-B73C-34E67BB7E17B. 0 INTERNAL sa_scheduler 20210713T040033.318+0200 14804 9624 91c19937-a0cd-4e79-9bb1-911f263eb0cf 952a5e83-5ecb-44aa-b73c-34e67bb7e17b 20210712T143738.000+0200 164c1051-2fe1-4a4d-912d-358bd7cba09c
699 20210713T040033.457+0200 INFO fro1vhlqlik1 System.Engine.Engine 236 fd75b6a4-abbb-4e28-ba8c-a299cd03d665 AUTORITE NT\Système Document Load: The document 952a5e83-5ecb-44aa-b73c-34e67bb7e17b was loaded. 0 INTERNAL sa_scheduler 20210713T040033.457+0200 14804 9624 91c19937-a0cd-4e79-9bb1-911f263eb0cf 952a5e83-5ecb-44aa-b73c-34e67bb7e17b 20210712T143738.000+0200 fd75b6a4-abbb-4e28-ba8c-a299cd03d665
700 20210713T040038.478+0200 INFO fro1vhlqlik1 System.Engine.Engine 236 b34c8fe5-7ff2-476e-be63-8a07a389119d AUTORITE NT\Système StdServer: OnRemoteClosed entered for socket fe80::c6d:20fc:f50d:73bc:4747 <-> fe80::c6d:20fc:f50d:73bc:49322, user: UserDirectory=INTERNAL; UserId=sa_scheduler, app: 952a5e83-5ecb-44aa-b73c-34e67bb7e17b. 0 Internal Engine 20210713T040038.478+0200 940 9624 0 20210712T143738.000+0200 b34c8fe5-7ff2-476e-be63-8a07a389119d
701 20210713T040038.482+0200 INFO fro1vhlqlik1 System.Engine.Engine 49 0ab98267-7699-4da6-8191-5a9544b06b8d AUTORITE NT\Système Abort request: Trying to abort: 6709 0 INTERNAL sa_scheduler 20210713T040038.481+0200 12704 9624 91c19937-a0cd-4e79-9bb1-911f263eb0cf 20210712T143738.000+0200 0ab98267-7699-4da6-8191-5a9544b06b8d
702 20210713T040038.530+0200 INFO fro1vhlqlik1 System.Engine.Engine 49 7e2a83af-45e9-4348-8d9f-42303af68d90 AUTORITE NT\Système Session stop reason: Socket closed by client 0 INTERNAL sa_scheduler 20210713T040038.499+0200 12704 9624 91c19937-a0cd-4e79-9bb1-911f263eb0cf 20210712T143738.000+0200 7e2a83af-45e9-4348-8d9f-42303af68d90

2nd : 

772 20210713T064532.398+0200 INFO fro1vhlqlik1 System.Engine.Engine 246 089d785f-e3ea-4e29-a742-6ce8e6c446be AUTORITE NT\Système QvContext: Setting JWT, payload: {"id":"UserDirectory=INTERNAL; UserId=sa_scheduler"} 0 Personal Me 20210713T064532.398+0200 13416 9624 ac5eff3d-e0f0-4659-a52a-4cb4e8928ba4 20210712T143738.000+0200 089d785f-e3ea-4e29-a742-6ce8e6c446be
773 20210713T064532.399+0200 INFO fro1vhlqlik1 System.Engine.Engine 101 a55e7746-fb4b-49bc-a4f7-e6d99c7d2fcf AUTORITE NT\Système TheServer: Registering new server session 0 INTERNAL sa_scheduler 20210713T064532.398+0200 940 9624 0 20210712T143738.000+0200 a55e7746-fb4b-49bc-a4f7-e6d99c7d2fcf
774 20210713T064532.404+0200 INFO fro1vhlqlik1 System.Engine.Engine 101 3340cf71-77e0-4480-997f-e0334558dcc9 AUTORITE NT\Système QvSocket: Connected to server as user: 'UserDirectory=INTERNAL; UserId=sa_scheduler' for document: '/b90918d9-7905-40c5-bb54-cadc14c51196' on socket fe80::c08:1e9a:f50d:73bc:4747 <-> fe80::c08:1e9a:f50d:73bc:49658 with ttl: 0 0 INTERNAL sa_scheduler 20210713T064532.398+0200 940 9624 0 20210712T143738.000+0200 3340cf71-77e0-4480-997f-e0334558dcc9
775 20210713T064532.404+0200 INFO fro1vhlqlik1 System.Engine.Engine 246 9a16f818-fef6-458b-ad8e-5970f974089f AUTORITE NT\Système Server: App Load: Beginning open of app 7974e8f2-c497-4361-aff2-7e49bca13757 with user UserDirectory=INTERNAL; UserId=sa_scheduler and payload {"id":"UserDirectory=INTERNAL; UserId=sa_scheduler"} 0 INTERNAL sa_scheduler 20210713T064532.398+0200 13416 9624 ac5eff3d-e0f0-4659-a52a-4cb4e8928ba4 7974e8f2-c497-4361-aff2-7e49bca13757 20210712T143738.000+0200 9a16f818-fef6-458b-ad8e-5970f974089f
776 20210713T064532.410+0200 INFO fro1vhlqlik1 System.Engine.Engine 246 fa471d28-0169-40ce-924d-be0e04de1da3 AUTORITE NT\Système DOC loading: Beginning load of document 7974E8F2-C497-4361-AFF2-7E49BCA13757. 0 INTERNAL sa_scheduler 20210713T064532.398+0200 14412 9624 ac5eff3d-e0f0-4659-a52a-4cb4e8928ba4 7974e8f2-c497-4361-aff2-7e49bca13757 20210712T143738.000+0200 fa471d28-0169-40ce-924d-be0e04de1da3
777 20210713T064532.547+0200 INFO fro1vhlqlik1 System.Engine.Engine 246 647a26b2-cbc0-458b-9e51-3aefa4399331 AUTORITE NT\Système Document Load: The document 7974e8f2-c497-4361-aff2-7e49bca13757 was loaded. 0 INTERNAL sa_scheduler 20210713T064532.547+0200 14412 9624 ac5eff3d-e0f0-4659-a52a-4cb4e8928ba4 7974e8f2-c497-4361-aff2-7e49bca13757 20210712T143738.000+0200 647a26b2-cbc0-458b-9e51-3aefa4399331
778 20210713T064533.200+0200 INFO fro1vhlqlik1 System.Engine.Engine 101 8dac4bfc-5abe-4caf-8f05-fdd944d205e1 AUTORITE NT\Système StdServer: OnRemoteClosed entered for socket fe80::c08:1e9a:f50d:73bc:4747 <-> fe80::c08:1e9a:f50d:73bc:49658, user: UserDirectory=INTERNAL; UserId=sa_scheduler, app: 7974e8f2-c497-4361-aff2-7e49bca13757. 0 Internal Engine 20210713T064533.199+0200 940 9624 0 20210712T143738.000+0200 8dac4bfc-5abe-4caf-8f05-fdd944d205e1
779 20210713T064533.202+0200 INFO fro1vhlqlik1 System.Engine.Engine 246 7ab01edf-707f-4813-9f51-aa7bc8ca4e3e AUTORITE NT\Système Abort request: Trying to abort: 6772 0 INTERNAL sa_scheduler 20210713T064533.200+0200 13416 9624 ac5eff3d-e0f0-4659-a52a-4cb4e8928ba4 20210712T143738.000+0200 7ab01edf-707f-4813-9f51-aa7bc8ca4e3e
780 20210713T064533.439+0200 INFO fro1vhlqlik1 System.Engine.Engine 246 0160bf64-d969-4db2-8512-1ca1e03622e9 AUTORITE NT\Système Session stop reason: Socket closed by client 0 INTERNAL sa_scheduler 20210713T064533.439+0200 13416 9624 ac5eff3d-e0f0-4659-a52a-4cb4e8928ba4 20210712T143738.000+0200 0160bf64-d969-4db2-8512-1ca1e03622e9
781 20210713T064541.561+0200 INFO fro1vhlqlik1 System.Engine.Engine 246 69f4ae5a-e5c6-4e08-ba84-0d8f6f0fda15 AUTORITE NT\Système DOC loading: Unloading document 7974e8f2-c497-4361-aff2-7e49bca13757, state UNLOADING. 0 Personal Me 20210713T064541.561+0200 13416 9624 fcf4ec5c-fde3-41cb-929a-7751064bc35e 20210712T143738.000+0200 69f4ae5a-e5c6-4e08-ba84-0d8f6f0fda15

Anil_Babu_Samineni

It's quite similar issue only, Can i suggest something? If so, go to PGADMIN and connect to QSR and then simply run this query and help me If you see this in result set?

select * From public."AppObjects" where "App_ID"='Your app ID' and "ObjectType" in ('app_appscript', 'LoadModel')
 

If you see only LoadModel and not app_appscript, we will see. But, Please confirm? 

Please add me Anil_Babu_Samineni to interact faster when reply back. Speak low think High.

Before develop something, think If placed (The Right information | To the right people | At the Right time | In the Right place | With the Right context)
kaushiknsolanki
Partner Ambassador/MVP
Partner Ambassador/MVP

Does those applications contain Section Access?

If yes then make sure that you have the below link in section access.

ADMIN, INTERNAL/SA_SCHEDULER,

 

Please remember to hit the 'Like' button and for helpful answers and resolutions, click on the 'Accept As Solution' button. Cheers!
HamdiGA
Contributor II
Contributor II
Author

Yes, I have the admin and the SA_SCHEDULER in the Access section, but the problem is that the task fail occasionally :
For example, I have a daily task: Yesterday the task failed, but today it have succeeded. 

HamdiGA_1-1626428877418.png

Can it be because of the time gap between two tasks i have 15 min between 2 tasks 

HamdiGA_2-1626429044981.png

 

kaushiknsolanki
Partner Ambassador/MVP
Partner Ambassador/MVP

It could be, sometimes if the task is taking more than 15 min the overlapping task may fail.

Please remember to hit the 'Like' button and for helpful answers and resolutions, click on the 'Accept As Solution' button. Cheers!
HamdiGA
Contributor II
Contributor II
Author

So do you think it is better to chose on triggers task and wait the previous tasks ?