Deal of The Day! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

Qlik Exam QV12SA Topic 4 Question 65 Discussion

Actual exam question for Qlik's QV12SA exam
Question #: 65
Topic #: 4
[All QV12SA Questions]

A QlikView server environment is restarted multiple limes. The system administrator finds this message in the QlikView Server event

logs:

Restart: Server aborted trying to recover by restart. Reason for restart: Phoenix detected: Performance monitor stuck.

Which are three possible causes for this error? (Select three )

Show Suggested Answer Hide Answer
Suggested Answer: D

Contribute your Thoughts:

Willodean
1 months ago
I'm just gonna throw in a 'lack of permissions' for good measure, Willodeann though it's probably not the root cause. You nWillodeanr know when those pesky permissions will trip you up!
upvoted 0 times
Suzan
7 days ago
A: I think memory shortage could be one of the causes.
upvoted 0 times
...
...
Margery
1 months ago
Definitely file locking, memory shortage, and corruption in the performance counter library. Gotta love when the 'Phoenix' rises from the ashes of a crashed server.
upvoted 0 times
...
Leeann
1 months ago
Ah, the old 'Phoenix detected: Performance monitor stuck' issue. Classic! I'd say memory shortage, corrupt PGO files, and corruption in the performance counter library are the likely culprits here.
upvoted 0 times
...
Jody
1 months ago
I'm going with file locking, corrupt PGO files, and corruption in the performance counter library. Those all seem like plausible causes for the server to get stuck and need a restart.
upvoted 0 times
Alishia
5 days ago
Yeah, corruption in the performance counter library could definitely lead to the server being stuck and needing a restart.
upvoted 0 times
...
Goldie
13 days ago
Corrupt PGO files could also be a reason for the server needing to be restarted multiple times.
upvoted 0 times
...
Dwight
23 days ago
I agree, file locking could definitely cause the server to get stuck.
upvoted 0 times
...
...
Fairy
2 months ago
Hmm, I think it could be a memory shortage or corruption in the performance counter library. The event log message mentions a 'Performance monitor stuck', so that's a good clue.
upvoted 0 times
Ashlee
23 days ago
E) Corruption in performance counter library
upvoted 0 times
...
Ellsworth
24 days ago
B) Memory shortage
upvoted 0 times
...
Linwood
1 months ago
A) File locking
upvoted 0 times
...
...
Chauncey
2 months ago
I also think file locking could be a possible cause. If the files are locked, it could prevent the server from functioning properly.
upvoted 0 times
...
Vilma
2 months ago
I agree with Jacquelyne. Those reasons make sense because they could all lead to the server being restarted multiple times.
upvoted 0 times
...
Jacquelyne
2 months ago
I think the possible causes could be memory shortage, corrupt PGO files, and corruption in performance counter library.
upvoted 0 times
...

Save Cancel
az-700  pass4success  az-104  200-301  200-201  cissp  350-401  350-201  350-501  350-601  350-801  350-901  az-720  az-305  pl-300  

Warning: Cannot modify header information - headers already sent by (output started at /pass.php:70) in /pass.php on line 77