Error: Path to URL.VI

[leocavadas]

Why path to url.vi in Open HTML Report in Browser (Path).vi put the text file://localhost/ before my net path builded with Current VI's Path.vi.

Example:

File Location: \\server01\labviewproduction\help\pag01.html

file location=file patch => path to url => file://localhost/server01\labviewproduction\help\pag01.html =>It's is wrong path.

My Help file HTML don't open in Browser.....MESSAGE: don't is possible find file.

[smercurio_fc]

The "Path to URL" VI that's in that library is pretty dumb. The Open HTML Report in Browser (path) VI is just a wrapper that calls the string input version of the Open URL in Default Browser polymorphic VI. You can do the same thing yourself by simply doing the following:




Message Edited by smercurio_fc on 02-12-2008 09:42 AM

[leocavadas]

Thx for tip smercurio_fc,

        but I tried it and the same message appear. Now i think that problem is special caracters %20 that is inserted in path, because in message appear %20 in substituion to white space.

More than one messages appear:

Don't is possible find

'file://server/techniques/advanced/sound%2520and%2520vibration/labview/help/test.html'

Other message:

Don't is possible find

'\\server\techniques\advanced\sound%20and%20vibration\labview\help\test.html'

Labview try several ways to solve path, but dont work.

Labview version 7.1

Order Analysis and Sound and Vibration toolkits

WinXP Professional SP2

[smercurio_fc]

Hmm.... It seems the stock Open URL in Default Browser VI doesn't handle file URLs all that well. I see the issue you're referring to.

What's interesting is that if you call the Open URL in Default Browser core VI directly with a valid file:// URL, it doesn't launch the browser. It doesn't generate an error either. It just doesn't do anything. Yet, I can paste the file:// URL directly in the browser (tried IE and Firefox), so I know the URL is valid.

You can call the Open URL in Default Browser core VI instead of the Open URL in Default Browser VI in the example I had shown. (The Open URL in Default Browser VI simply replaces the spaces in the string and then calls the Open URL in Default Browser core VI.) This seems to work with UNC paths that have spaces. Warning: One odd thing that I found is that the browser got launched, but sometimes returning to LabVIEW crashed LabVIEW. I couldn't replicate this all the time. If you encounter this issue, I would suggest the System Exec route, as done in the example VI in this message.

It seems that NI has a little work to do with that VI and file URLs.

[leocavadas]

smercurio_sc,

after a long and exhaustive test, my conclusion is that the problem is in path to URL VI that added file://localhost/ to my network path file. If this VI put only file: before my network path file would work very well.

Thanks for your analysis, i will see the post that suggested.

Have a good day.