11 Replies Latest reply: Nov 5, 2009 5:21 PM by Stefan Bäckstrand RSS

    QlikView Server 9 SR1 64 bit error and crash

    michaelm

      Hi

      we just upgraded to the latest version of server 9 and have had two crashes today. Event log contains this message

      "Server aborted trying to recover by restart. Reason for restart: Internal inconsistency, type D, detected. "

      wondering if anyone else has run into this and has any ideas?

      Michael

        • QlikView Server 9 SR1 64 bit error and crash
          Stefan Bäckstrand

          These errors are considered bugs and should be debugged by a Qliktech Support Technician. Report this as a case to support@qliktech.com and attach the document (if possible) and steps to reproduce. Also include detailed information about your environment, such as the QVS DSI.

          • QlikView Server 9 SR1 64 bit error and crash

            We're going to V9 SR1 w/64 bit. Have you seen any other issues, has this one been fixed?

              • QlikView Server 9 SR1 64 bit error and crash
                michaelm

                Hi,

                this one just popped on 2 days ago, no fix yet, been sending logs and info to Support. Other issues; I had lots of problems with the macros that we use (lots of post reload macros) that stopped working. We also use scheduled tasks for our reloading btw. Anyway what I discovered is that the macros would fail because in my .bat files I was using the /r option which worked fine with version 8.5. However under version 9 the macros fail to execute. Switching to /l in the .bat files solved the problem as the various objects I was exporting were now "visible". Other problems were found with the current selections in the IE plugin toolbar. Under v9 you could see the current selections, but not clear them. I modified all our apps to use the current selections layout object and told my uses to stop using the toolbar item. I have only tried it briefly under 9sr1, but that one seems to be fixed now.

                Our big issue probably stemmed from our environment. When we first went to v9 our IE users, when they connected to the server were being assigned 2 CALS for each user. one for the server account and another that showed up as a user with "<NW-username>" (we are a novell shop). Took some help from QliKTech support to find that by checking Prohibit Anonymous under Authentication, Client, in the enterprise management console solved that problem.

                 

                 

                • QlikView Server 9 SR1 64 bit error and crash
                  Joachim Rogginer

                  Actually, I've already seen the error/message "Internal inconsistency, type D, detected" in several scenarios, not too often, but again and again, in QV 9, in QV 9 SR1, in 32 and in 64 bit. And I could hardly ever reproduce it (and so I never could occupy support). And I could not make out what the situations in which the error occurred had in common... Once it occurred to my mind that "D" might stand for "Don't know!" - or "Dont't tell you!" ;-))

                  Rgds,
                  Joachim

                   

                  • QlikView Server 9 SR1 64 bit error and crash
                    Stefan Bäckstrand

                    The "Internal inconsistency" errors is not by definition an issue in it self, but a pointer to what type of error that has occured when inconsistency did. These errors can for e.g. be an access violation or a number of other, often memory related, issues. They are not harmful to persistent data, but is most probably going to empty the working set for QVS as an evasive maneuver to not cause any more inconsistency or errors.

                    Often the errors can be a symptom of a somewhat bad document design, or an indication of memory shortage, or any other number of issues. Sometimes there are workarounds, but they are always seen as bugs.

                    They occur in very specific situations, and not very often if all is correctly done, which is why we require as much information as possible when troubleshooting these errors. Document, steps-2-reproduce and environment information is a must.

                      • QlikView Server 9 SR1 64 bit error and crash
                        michaelm

                        I have sent over all the details that I can think of, logs, the about info from the mgmt console. Server has 32 gig of ram so I can't image that is an issue. Been trying to hone in on what triggers it, it just started happening in the last 3 days. The real trouble is that it is causing the qvs.exe to hang, and my users get a No Server message in the Access Point home page.

                        Thanks for the info

                          • QlikView Server 9 SR1 64 bit error and crash
                            Stefan Bäckstrand

                            I didn't say that memory related necessarily meant shortage of memory. It could be a mapped area in memory that is cleared and then referenced, or a faulty pointer, or read/write access violation, or.. and so on. And as I said; the "hang" of QVS is because the server will most probably clear the working set or that sometimes the process crashes as a result of the error.

                      • QlikView Server 9 SR1 64 bit error and crash

                        Morning, we are scheduled to upgrade, has this been resolved?

                          • QlikView Server 9 SR1 64 bit error and crash
                            Stefan Bäckstrand

                            Still, this is no static error. It is an indication that some kind of inconsistency has occurred when processing data in memory and is a pointer to where this has occurred. We treat every issue as separate bugs, and to be able to trap the error, we need steps to reproduce in the affected document.

                            Internal inconsistency errors can occur as a result of bugs and it might occur as a result of performance exhaustion or bad document/expression design - there's no way to tell until we can look at the document, server performance, expressions and other factors.

                            Hence; this issue is not specific for this build, or any other. There is no reason to not upgrade to SR1 or SR2 because of this issue.