The Forums on slxdeveloper.com are now retired. The forum archive will remain available for the time being. Thank you for your participation on slxdeveloper.com!
|
|
Error on launching Visual Analyzer
Posted: 02 Jul 08 9:26 AM
|
Hello,
has anybody got such error while launching customised .qvw file in SLX Visual Analyzer:
Visual Analyzer - Could not Open Default file: Local Library:testError HRESULT E_FAIL has been returned from a call to a COM component. at QlikView.Doc.Fields(String _Name)
at iReports.iReport.QVFieldValueExists(String FieldName, String FieldValue)
at iReports.iReport.CheckSLXUserID(String Username)
at iReports.iReport.InitiReportSettings()
at iReports.iReport.OpenDocument(String DocName)
at iReports.iReport.set_DocName(String Value)
at iReports.iReport.set_CurrentiReportFile(iReportFile Value)QlikView
In documentation it is said that it can be caused by that fact that .qvw file was created with QlikView earlier then v8. But we use QlikView v8.01.
The .qvw file that we've received with Visual Analyzer opens correctly. But it contains sample data. And when i tried to create my own .qvw file with our data, it causes error that i mentioned above.
BUT! in Visual Analyzer as a separate application it opens and shows the correct data, and in QlickView too.
Thanks.
|
|
|
|
Re: Error on launching Visual Analyzer
Posted: 09 Feb 09 1:56 PM
|
Alex,
Did you ever get a solution for this. I am going around in circles with the same issue on one particular custom VA report.
Thanks,
Todd |
|
|
|
Re: Error on launching Visual Analyzer
Posted: 10 Feb 09 4:36 AM
|
You did not mention what version of VA you are dealing with here.
(2.5 or 2.6)
One thing to try is to unrelease the VA plugins & re-release them.
(I kid you not).
The other thing that can cause it depends on how you built your QVW. VA is looking for certain variables to pass information into and if the variable is missing when it looks for it - you will get that message as well. There is (as far as I know) no documented list of required variables, so I usually start off with a gutted copy of the sample one.
Hope that helps
ws |
|
|
|
Re: Error on launching Visual Analyzer
Posted: 10 Feb 09 9:00 AM
|
Thanks Walter. In my case this customer is on VA 2.5 and has a bunch of remote users, so upgrading is not a great option right off the bat.
I am aware of the known issue with editing any report in a Qlikview developer version other than 8.0 for VA 2.5, so I took the VA 2.5 OOB report, this kept all variables, the module code, and I also left the connection and usersecurity portions of the load script alone. Then I cleared the rest and added a simple load script for accout table data. I did all of this in a retro install of the old Qlikview 8.0.1 version.
Still the same message on any report I have edited and saved.
I have not tried re-releasing plugins, I will try that today and see if it works. |
|
|
|
Re: Error on launching Visual Analyzer
Posted: 10 Feb 09 10:49 AM
|
I think 2.5 is probably more stable than 2.6.
The re-release of plugins was the answer I got from SLX Support of all places.
There also seems to be a problem where you get "Failed to Open Document" 3x before it finally does.
If you like messageboxes, you can go into the VA Configuration and turn on Verbose Messages.
good luck with it.
ws |
|
|
|
Re: Error on launching Visual Analyzer
Posted: 10 Feb 09 12:37 PM
|
Re-Released all plugins in the VA2.5 project and still get the H_REF errors. I don't have this problem with VA2.6 at another customer, so I am thinking that direction is my next step. I don't use the OOB VA report, just need it to successfully open the custom report version for remote users so I can use the library to send out QVW's that will make a data connection to SQL Express. The only other alternative I can think of right now is a QVW with a direct connection string for every remote user, which is not feasible for this project. Just too many users.
Any other thoughts that have worked around VA defects for people? |
|
|
|
Re: Error on launching Visual Analyzer
Posted: 10 Feb 09 1:22 PM
|
If you are making your connections via $(SLXDB_NAME) and $(SQL_NAME), then it should get that at runtime, regardless of what machine you run it on.
Have you tried the verbose messages to see if it tells you anything useful?
ws |
|
|
|
Re: Error on launching Visual Analyzer
Posted: 11 Feb 09 2:35 AM
|
Hi Todd, Walter.
I've solved that problem long before but haven't wrote the solution.
I've created the whole new .qvw file with no any tables that are used in the standard file and was getting an error I've mentioned above.
Then I added tables USERIDS and UserAccess and that helped. I think UserAccess is the key table. Also I have Variable USESLXPassword = True but I'm not sure it is required.
The only thing is that all users that work with VA from SLX should be loaded into the UserAccess table. Otherwise they will get errors on launching VA.
I load USERIDS and UserAccess tables like it is done in the standard file, but I don't load all the SLX users, but only those who work with VA. For that purpose I created new Team named Visual Analyzer.
Regards,
Alexey. |
|
|
|
Re: Error on launching Visual Analyzer
Posted: 11 Feb 09 12:52 PM
|
I have verbose messages ON and where things break down is the message "USERCODE exists is False"
In out of the box VA this message comes across as True. I have left the useraccess settings intact and have inline load for the ADMIN usercode, etc.
The only difference now is that I pulled this out of the hidden script section, maybe I will move it back in there to see if it helps. IN the meantime, any thoughts on what setting would be missing for it to fail on USERCODE check? |
|
|
|
Re: Error on launching Visual Analyzer
Posted: 11 Feb 09 1:29 PM
|
| OK, got it. It is some combination of UseSLXpassword, the Useraccess, Userid and users load secitons of VA, and completing a full reload as ADMIN user first even after the error message occurs, to initially load the inline usercode records. It is working now so I am not going to dig deeper. |
|
|
|