Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
We have a 10+ years of Qlikview development where apps are still using .shared files. We are set up to use .tshared and when we create new applications they are defaulting to creating .tshared. We have also been able to convert some .shared to .tshared successfully. However, we are running into some issues where we convert a .shared to a .tshared, remove the .shared and replace it with the .tshared, but then see the app ignore the .tshared and create a new .shared file. I thought it might have something to do with settings on our servers running QV Server and Webserver, but they are all identical. We did start using an updated template for the new apps we create (which default to .tshared). Is there anything within the actual document settings that needs to change to recognize .tshared files?
We had the same. Try the following: stop QV Server Service; convert your shared files; start the service again. It should then pick up the tshared format. Also make sure that DefaultBlobDbType=1.
Hi all,
I can confirm what @eric_dielessen stated in that stopping the QVS service is key when converting the .shared files to .tshared, or copying .tshared files converted from another location into the mounted folders. If the QVS service is not running, you'll run into the symptoms described in the original post.
Best Regards
duzford13 You can try going into the settings.ini file and adding this line:
DefaultBlobDbType=1
Set the file format:
DefaultBlobDbType=0
With this setting, the .Shared format is used when creating new shared files.
DefaultBlobDbType=1
With this setting, the .TShared format is used when creating new shared files.
See the below KB article for more detailed information:
https://support.qlik.com/articles/Basic/What-is-DefaultBlobDbType
Thank you @Lucas_Gatling -
We made the change to our settings.ini files, but certain apps still won't recognize a .tshared file. All of our new apps spawn .tshared and some of our apps will recognize a converted .tshared. The ones that won't recognize the .tshared will also still create a new .shared. Just wondering if there is a setting within the application itself that is overriding.
@duzford13 wrote:
We have a 10+ years of Qlikview development where apps are still using .shared files. We are set up to use .tshared and when we create new applications they are defaulting to creating .tshared. We have also been able to convert some .shared to .tshared successfully. However, we are running into some issues where we convert a .shared to a .tshared, remove the .shared and replace it with the .tshared, but then see the app ignore the .tshared and create a new .shared file. I thought it might have something to do with settings on our servers running QV Server and Webserver, but they are all identical. We did start using an updated template for the new apps we create (which default to .tshared). Is there anything within the actual document settings that needs to change to recognize .tshared files? My AARP Medicare
The QlikView shared file cleaning tool is a command line tool that allows system administrators to verify (analyze) and purge (repair) shared files. This tool can also be used to convert between different shared file formats, see Converting the shared files. You can invoke it by running the QlikView Server executable (QVS.exe) with special parameters.
Thank you @Akeem. We do use the shared file cleaning tool and have converted some of our .shared files to .tshared. The problem is that when we remove the .shared file and replace with a .tshared, certain applications do not recognize the .tshared file and instead generate a new .shared. However, new applications we create do generate .tshared files and we've been able to convert some files successfully. That is why I am wondering if there is something specific (maybe a setting?) at the application level as well.
We had the same. Try the following: stop QV Server Service; convert your shared files; start the service again. It should then pick up the tshared format. Also make sure that DefaultBlobDbType=1.
Just two hints for things which might be related to the issue. The first is the use of prj-folder and the second is the origin major-release of the application. AFAIK are only older creation-releases properly converted by the next major-release or in other words skipping some major-releases may lead to incompatibilities.
Hi all,
I can confirm what @eric_dielessen stated in that stopping the QVS service is key when converting the .shared files to .tshared, or copying .tshared files converted from another location into the mounted folders. If the QVS service is not running, you'll run into the symptoms described in the original post.
Best Regards