LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

HTML report refuses to be opened

When I'm under "User" or "Guest" login
on WinXP sp2 (FAT32), HTML report refuses to be opened with "Open HTML Report in browser.vi" in IE (the same story with the OPERA, forinst).

When I'm under "Administrator", it's OK.

How can I work it out?
Thanks.
0 Kudos
Message 1 of 7
(3,157 Views)
Hello,
 
Have you tried sharing the National Instruments folder under Program Files?  The Open HTML Report in browser.vi uses a core function whose block diagram cannot be viewd (it is password protected), but it probably calls a dll which non-administrators don't have access to.  If this doesn't work, I'll play more on my machine as well, but I am having problems creating new users at the moment so I can't try this before posting 😞  Let me know the results, and we'll keep searching for an answer!
 
Best Regards,
 
JLS
Best,
JLS
Sixclear
0 Kudos
Message 2 of 7
(3,121 Views)
Hello,
 
I just wanted to update here, that I was able to try this today, and did not have problems with either "Open HTML Report in browser.vi" or  "Open URL in Default Browser.vi" when logged on as a restricted user (in the Users group).  Do you see an error message?  Have there been any special restrictions made for the user profile you logged in with?  Did my previous suggestion work?
 
I hope this helps eliminate possiblities for the problem!
 
Best Regards,
 
JLS
Best,
JLS
Sixclear
0 Kudos
Message 3 of 7
(3,105 Views)
Unfortunately, I can't try out my VI as a VI, and only can work it in *.exe: the machine under consideration have no LV installed and is always busy :(.
But soon may be I'll have a chance to do that.

My PC has LabVIEW installed and there is no problem running VI opening report under any user login.

Still, may be the executable is the Reason?

Thanks a lot, JLS!
0 Kudos
Message 4 of 7
(3,095 Views)
Hello,
 
I suppose it could be the exe - one requirement is that _exclsub.llb and _wordsub.llb must be added as support files when building an application or a dynamic link library with the application builder.  Those libraries can be found in the directory:
 
C:\Program Files\National Instruments\LabVIEW 7.1\vi.lib\addons\_office
 
If you haven't already, try including those as support files when you build the exe, and try it on your machine that only has the LabVIEW Runtime Engine again.
 
Best Regards,
 
JLS
Best,
JLS
Sixclear
0 Kudos
Message 5 of 7
(3,081 Views)
Still is it alright when I'm under "administrator"
on the same PC with the same .exe.
So can those libraries' absence be the reason,
if i catch you right?

Thanks.
0 Kudos
Message 6 of 7
(3,071 Views)
Hello,
 
Those libraries contain VIs which are called by reference by some of the toolkit VIs, and therefor must be added as dynamic VIs in order for an executable using them to function correctly.  I would expect to see a different error, but though I should at least mention it.  I also wanted to ask if you tried creating a non-administrator account on your computer, and running the executable there.  If that works, it would be a strong indication that it's a problem on that specific machine.
 
Best Regards,
 
JLS 
Best,
JLS
Sixclear
0 Kudos
Message 7 of 7
(3,060 Views)