MENU
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 )
Suggested Answer: D
Get Premium QV12SA Questions
as Interactive Web-Based Practice Test or PDF
Real Exam Format
Detailed Explanations
Instant Access
Get Your Practice Test
35 comments · newest first
GL
Glory
10 months ago
Corruption in performance counter library? Wow, didn’t see that one coming!
TH
Thurman
10 months ago
I’m not so sure about file locking being the issue.
LE
Leanna
10 months ago
Definitely could be memory shortage.
GR
Gregoria
10 months ago
Lack of permission? That seems a bit off.
DA
Daniel
11 months ago
I think corrupt PGO files are a likely cause too.
GL
Glory
11 months ago
Corruption in the performance counter library sounds plausible, but I can't recall if we covered that specifically. I might lean towards option E.
SA
Samira
11 months ago
I think file locking could be a reason too, but I’m not confident. We discussed it briefly in class.
EV
Eveline
11 months ago
I'm not entirely sure, but I feel like corrupt PGO files might lead to problems like this. It sounds familiar from our practice questions.
AL
Alease
11 months ago
I remember something about memory shortages causing issues in server environments, so I think option B could be a cause.
SH
Sheridan
12 months ago
I feel pretty confident about this one. The error message points to issues with the performance monitoring, so I'm leaning towards the memory shortage and corruption in the performance counter library as the most likely causes.
DE
Delmy
12 months ago
The file locking and lack of permission options seem like reasonable possibilities too. I'll make sure to read through the question carefully and consider all the options before selecting my answers.
IN
Inocencia
12 months ago
I'm a bit confused by the "Phoenix detected" part. Is that a specific QlikView error or something more general? I'll need to research that a bit more.
BE
Belen
1 year ago
Okay, let's see. The error message mentions a "Phoenix detected: Performance monitor stuck" issue, so I'm guessing memory shortage or corruption in the performance counter library could be the culprits.
LA
Lashawn
1 year ago
Hmm, this looks like a tricky one. I'll need to carefully consider the error message and the possible causes listed.
WI
Willodean
1 year 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!
BU
Buck
1 year ago
D: Lack of permissions could also be a contributing factor, you never know.
NI
Nichelle
1 year ago
C: I agree, corruption in the performance counter library could definitely cause issues.
MA
Marion
1 year ago
B: Yeah, corrupt PGO files might also be a reason for the error.
SU
Suzan
1 year ago
A: I think memory shortage could be one of the causes.
MA
Margery
1 year 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.
CA
Cammy
1 year ago
Corruption in the performance counter library can also lead to server crashes.
WA
Wayne
1 year ago
Memory shortage is a common reason for server restarts.
TH
Theodora
1 year ago
File locking can definitely cause the server to restart.
LE
Leeann
1 year 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.
JO
Jody
1 year 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.
AL
Alishia
1 year ago
Yeah, corruption in the performance counter library could definitely lead to the server being stuck and needing a restart.
GO
Goldie
1 year ago
Corrupt PGO files could also be a reason for the server needing to be restarted multiple times.
DW
Dwight
1 year ago
I agree, file locking could definitely cause the server to get stuck.
FA
Fairy
2 years 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.
AS
Ashlee
1 year ago
E) Corruption in performance counter library
EL
Ellsworth
1 year ago
B) Memory shortage
LI
Linwood
1 year ago
A) File locking
CH
Chauncey
2 years ago
I also think file locking could be a possible cause. If the files are locked, it could prevent the server from functioning properly.
VI
Vilma
2 years ago
I agree with Jacquelyne. Those reasons make sense because they could all lead to the server being restarted multiple times.
JA
Jacquelyne
2 years ago
I think the possible causes could be memory shortage, corrupt PGO files, and corruption in performance counter library.