Qlik Community

QlikView Deployment

Discussion Board for collaboration related to QlikView Deployment.

Announcements
QlikView Fans! We’d love to hear from you.
Share your QlikView feedback with the product team… Click here to participate in our 5-minute survey.
Rules, plus terms and conditions, can be found here.
Not applicable

What informations contain .meta and .shared files ?

Hi all,

we have actually 10 proview applications running on a server and used in Ajax mode by users.

we have a problem when we deliver some enhancements on these applications.

A message "Unexpected exception occurs" appears in Internet Explorer with no possibility to access application.

A solution is to delete the file ".meta" on the server but I don't know what informations contains this file and what will be the consequence for the users?

If possible, can you also give me informations about .shared file?

Thanks a lot for your answers

Greg

1 Solution

Accepted Solutions
Emmanuelle-Bustos
Valued Contributor

Re: What informations contain .meta and .shared files ?

Hi Grégory Nallet  you can see in the Server reference manual all about .meta files as this:

9.1 User Documents

A user document is the document that an end user sees when accessing a document on QlikView Server (QVS). To fully identify a user document, both the QVS server/cluster and the path relative to the server have to be known. Technically, a user document consists of three files:

1. .qvw file that contains the data and layout.

2. .META file that contains:

     a. AccessPoint attributes

     b. Pre-load options

     c. Authorization (Document Metadata Service – that is, DMS – mode only)

3. .Shared file (see below)

Note! If the user document is distributed by the QlikView Distribution Service, both the .qvw and the data in the .META file are overwritten.

Shared Files

-There are multiple objects available for user collaboration and sharing through QlikView Server:

-Bookmarks

-Sheet objects, including charts

-Reports

-Annotations

From Server Reference Manual pp. 51 (Attached)

And concerning to the "Unexpected Error Occurred" have you been able to reproduce the issue, and are you totally sure by deleting the .meta files you solve the problem?

3 Replies
Not applicable

What informations contain .meta and .shared files ?

Hi,

I do not know anything about .meta, but the .shared contains for example:

- User selections for restoring selections when user opens the report next time

- Manual inputs

- Changes when document is release for online colaboration

Regards,

Björn

Not applicable

What informations contain .meta and .shared files ?

Hi Nallet,

As i know that the access control list is maintain in the .meta file which is attached to the document i.e.qvwdocument.meta . We use it through DMS authorisation.

It may help you...

Emmanuelle-Bustos
Valued Contributor

Re: What informations contain .meta and .shared files ?

Hi Grégory Nallet  you can see in the Server reference manual all about .meta files as this:

9.1 User Documents

A user document is the document that an end user sees when accessing a document on QlikView Server (QVS). To fully identify a user document, both the QVS server/cluster and the path relative to the server have to be known. Technically, a user document consists of three files:

1. .qvw file that contains the data and layout.

2. .META file that contains:

     a. AccessPoint attributes

     b. Pre-load options

     c. Authorization (Document Metadata Service – that is, DMS – mode only)

3. .Shared file (see below)

Note! If the user document is distributed by the QlikView Distribution Service, both the .qvw and the data in the .META file are overwritten.

Shared Files

-There are multiple objects available for user collaboration and sharing through QlikView Server:

-Bookmarks

-Sheet objects, including charts

-Reports

-Annotations

From Server Reference Manual pp. 51 (Attached)

And concerning to the "Unexpected Error Occurred" have you been able to reproduce the issue, and are you totally sure by deleting the .meta files you solve the problem?

Community Browser