
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Internal inconsistency, type CPV, detected
Hi everyone,
I was opening locally a model in a server and I stumbled upon this error. I did some searching in the official documentation and Google and I didn't find anything.
Any help would be greatly appreciated.
Kind regards.
- « Previous Replies
-
- 1
- 2
- Next Replies »
Accepted Solutions

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
If that's true, the bug is back.
I just ran into the "internal inconsistency, type CPV" message using fat client 12.10 SR8.
Regards
Eric


- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi Julio,
have you found out anything about this yet?
I get the same error and it seems like I cannot open my QVW-Files anymore. (I tried several times.)
Is there a trick to open the files again?
Regards
Tamara

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
May be this is the Issue:
Internal inconsistency, type CRT, detected: This error is because of corrupted shared files.
Even though it's not officially supported, download the Power Tools.
Included in the Power Tools:
SharedFileViewer
Provides insight into the QlikView Server .shared files belonging to .qvw documents. The .shared file stores server data
such as server/shared bookmarks, server objects (charts and objects created by a client via the server), annotations and
other data that is specific to the document. The tool visualizes the content of the binary .shared file and provides options
to "Repair" legacy files, as well as defrag large .shared files.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi,
Which qlikview version you have installed on your machine ?
Vikas
If the issue is solved please mark the answer with Accept as Solution & like it.
If you want to go quickly, go alone. If you want to go far, go together.


- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi Vikas,
I think, I found the reason for our problem.
QlikView took very long to save the document and the process wasn’t responding after a while and got killed. So probably the saving process was not finished and therefor some needed information was missing.
We restored a backup and will redo out changes.
Thanks for your help.
Regards
Tamara

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
you need to deploy qlikview 12.10 SR7 this bugs are fixed.
Vikas
If the issue is solved please mark the answer with Accept as Solution & like it.
If you want to go quickly, go alone. If you want to go far, go together.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
If that's true, the bug is back.
I just ran into the "internal inconsistency, type CPV" message using fat client 12.10 SR8.
Regards
Eric


- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
It is happening to mee too in 12.10 SR8


- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- Stop the QlikView WebServer Service or the QlikView Settings Service
- Navigate to C:\Program Files\QlikView\Web Server
- Open QVWebServer.exe.config
- Inside the <appSettings> section, add the following key (if not already present):
<add key="SocketTimeOutInSeconds" value="600"/> - Save the file, and start the QlikView WebServer Service or the QlikView Settings Service
.png)

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Are people seeing this with the "Open in server" option as well as "Open"? I just experienced for the first time today using a simple "Open" of a QVW local to the machine I'm on. Additionally, I'll note that once I closed the error windows, I was able to eventually open the QVW. Thanks.

- « Previous Replies
-
- 1
- 2
- Next Replies »