Skip to main content
Announcements
Have questions about Qlik Connect? Join us live on April 10th, at 11 AM ET: SIGN UP NOW
cancel
Showing results for 
Search instead for 
Did you mean: 
Not applicable

Documentation of the EventIDs in the EventLog?

Hi,

is there any documentation of the EventIDs avaiable which are writen by the QlikViewServer into the EventLog?

E.g. I guess that EventID 108 means that the document has been loaded the first time through the Access Point.

Regards

1 Solution

Accepted Solutions
StefanBackstrand
Partner - Specialist
Partner - Specialist

Well, in that case we are talking about two different components. Reload tasks (which is handled by the ReloadEngine or Publisher) will not output any error messages to the QVS event log, since Publisher/ReloadEngine has it's own set of log files; namely the Task logs and the Publisher logs. I suggest you look in those log files instead, at the date and time of the failed reload task.

And I simply repeat my answer; the raw messages you are seeing in the Windows Event log are because the QVS components have for some reason not gotten registered properly, and thus the event entries will not have the correct "templates" needed to output the entries in the informative way that we are used to.

You can try and workaround the issue (which has nothing to do with Publisher tasks, though, only QVS event entries) by doing this on the QVS server:

  1. On the QVS server, open the Windows Registry editor, by clicking Start, selecting Run.. and type regedit and press enter. (You can also bring up the Run.. menu with the keyboard command Win+R)
  2. Under the HKLM\System\CurrentControlSet\Services\Eventlog\Application node, add a key named QlikViewServer.
  3. Under this node, add an Expandable String Value named EventMessageFile, and set its value to the path to the system's QVS.exe, for eg. C:\Program Files\Qlikview\Server\QVS.exe.
  4. Add a DWORD value, name it "TypesSupported", and set its value to 7.
  5. Re-open or refresh the Event Viewer window.

View solution in original post

7 Replies
ashfaq_haseeb
Champion III
Champion III

HI Anderber

I suggest to go through Below post

http://community.qlik.com/forums/p/35865/165417.aspx

hope this fullfill your requirement

Regards

ASHFAQ

Not applicable
Author

Unfortunately I can't find any explanation of the EventIDs in the thread you mentioned.

Regards

StefanBackstrand
Partner - Specialist
Partner - Specialist

There have been issues when "parsing" entries in the WIndows Event log to proper Qlikview messages. Please review the QVS event logs during the entry time, since all messages written in the Windows Event log will wind up there as well. I'm not sure the QVS log verbosity align between the two though.

Not applicable
Author

There must be a difference in the QVS log verbosity because recently I found warnings relating to the reload of a document in the Windows EventLog but I can't find an entry in the eventlog (Events_SERVERNAME.log).

So I simply repeat my question. Is there no documentation the EventIDs available since you as the manufacturer should be able to deliver this documentation. Shouldn't you?

Regards

StefanBackstrand
Partner - Specialist
Partner - Specialist

Well, in that case we are talking about two different components. Reload tasks (which is handled by the ReloadEngine or Publisher) will not output any error messages to the QVS event log, since Publisher/ReloadEngine has it's own set of log files; namely the Task logs and the Publisher logs. I suggest you look in those log files instead, at the date and time of the failed reload task.

And I simply repeat my answer; the raw messages you are seeing in the Windows Event log are because the QVS components have for some reason not gotten registered properly, and thus the event entries will not have the correct "templates" needed to output the entries in the informative way that we are used to.

You can try and workaround the issue (which has nothing to do with Publisher tasks, though, only QVS event entries) by doing this on the QVS server:

  1. On the QVS server, open the Windows Registry editor, by clicking Start, selecting Run.. and type regedit and press enter. (You can also bring up the Run.. menu with the keyboard command Win+R)
  2. Under the HKLM\System\CurrentControlSet\Services\Eventlog\Application node, add a key named QlikViewServer.
  3. Under this node, add an Expandable String Value named EventMessageFile, and set its value to the path to the system's QVS.exe, for eg. C:\Program Files\Qlikview\Server\QVS.exe.
  4. Add a DWORD value, name it "TypesSupported", and set its value to 7.
  5. Re-open or refresh the Event Viewer window.

Not applicable
Author

[quote user="Stefan Bäckstrand"]

And I simply repeat my answer; the raw messages you are seeing in the Windows Event log are because the QVS components have for some reason not gotten registered properly, and thus the event entries will not have the correct "templates" needed to output the entries in the informative way that we are used to.

Now I got you. This wasn't that clear from your last answer.


You can try and workaround the issue (which has nothing to do with Publisher tasks, though, only QVS event entries) by doing this on the QVS server:
<ol><li>On the QVS server, open the Windows Registry editor, by clicking Start, selecting Run.. and type regedit and press enter. (You can also bring up the Run.. menu with the keyboard command Win+R)</li><li>Under the HKLM\System\CurrentControlSet\Services\Eventlog\Application node, add a key named QlikViewServer. </li><li>Under this node, add an Expandable String Value named EventMessageFile, and set its value to the path to the system's QVS.exe, for eg. C:\Program Files\Qlikview\Server\QVS.exe. </li><li>Add a DWORD value, name it "TypesSupported", and set its value to 7. </li><li>Re-open or refresh the Event Viewer window. </li></ol><div></div>


This resolved it. Now the entries in the EventLog are shown the right way. Thanks.

Regards

StefanBackstrand
Partner - Specialist
Partner - Specialist

I'm glad it worked out. Sorry for the short first answer. 🙂