Please send us an error report as follows:
1. Start Omniscope.
2. Turn on this setting "Settings > Advanced > Miscellaneous > Report recognised errors as bugs".
3. Restart Omniscope.
4. Reproduce the problem.
5. This will prompt an error dialog to show.
6. Please send this report to us.

I'd like to jump on this thread, as I'm having an almost identical error.

I am looking at the online version of Omniscope and have embedded a [Launch] button in a SharePoint web page[1]. The file I'd like to open is on the same site as the page - and it's a site to which I have Admin/Owner permissions.

When I click [Launch], the Omniscope 2.5/build 316 - Viewer (Online) - is launched, initialization is performed and I am prompted for a Username and Password. I enter my correct SharePoint credentials and get the almost the same message as that described above:

File could not be opened/Error writing to server/The server has terminated the connection. You may not have permission to access the selected resource.

I can mount the site as a network drive on my PC, browse to the file and open it without problems with the same instance of the online viewer.

Any ideas?

Thanks,

KW

[1] for the record, the code I've embedded was generated by the Link Builder and is as follows (the hexification of spaces and slashes in my site address was done by the Link Builder - I copied straight text into the "File to open:" text entry box):



var url = "http://tc.visokio.com/webstart/launch_"+Math.random()+".jnlp?name=FID+Monthy+Deck+Prototype&open=http%3A%2F%2Fln-sharepoint.csintra.net%2Fit%2FFIDIT%2FSupport%2FFID%2520Monthly%2520Service%2520Reports%2FFID_MonthlyOmniscope.iok+&rand="+Math.random();
deployJava.createWebStartLaunchButton(url);

Hi Walsh,

We have fixed this issue with sharepoint, could you please verify that the fix works by using the following URL to build your link and let us now know how you get on.

http://tc.visokio.com/webstart/?open=%5bINSERT%20LINK%20HERE%5d&build=temp

Thanks for the feedback, Mohamed - the fix seems to have done the trick. I got an error message - v2.6 seems to object to one of my formula fields - that I sent back to you, but otherwise and at first sight, all seems to be fine.

Thanks again.

We fixed the issue with your formula field, the fix will be available in tonight's build Omniscope 2.6-alpha b392.

Please download it tomorrow and rebuild your webstart links using this build.

Thanks! I'll give it try on Monday and let you know.

I'm still picking up build 391 - and, not surprisingly - still seeing the error.

Please click "Daily builds" on the download page to get the latest.

Thanks, Steve, but I was referring to the Web version of Omniscope and, specifically, to the version that's launched by the link in Mohamed's post above (4th post in this thread). Build 391 complains about one of the files I'm trying to open with it.

You *can* configure the online version to use a specific build, but it's fiddly. Use "customise link" and look at the notes. Post back here if you get stuck.

Bear in mind that if you do this, and create a customised web start link to anything where the build is specified, these links expire after a week or two, when the releases are expunged from the site as they are superceded.

The link above sets the build name to temp (http://tc.visokio.com/webstart/?open=%5bINSERT%20LINK%20HERE%5d&build=temp). I've tried changing it - I used "omni26/auto/b2-6_b392" for the build and "2.6 b392" for the version, as per the notes, but I get a message box saying Unable to launch Omniscope 2.6 b392(online)..

Kevin, apologies, it appears I misread both your posts. Let's start over. Mohamed's temp link was only so you could get the fix and test ahead of nightly build, so you can ignore that by now - we'll remove this build from the site. Later today (in the next hour or so) you'll see that the Launch button on the main 2.6 page launches a newer version, which should include the Sharepoint fix.

Thanks Steve - sorry to bug you, but is this the main 2.6 page? I'd like to get hold of the updated script for the launch button but can't find another 2.6 page.

I've now got the button working fine and opening the file from my SharePoint - thanks! I've distributed the link to a colleague and he gets an error message when he clicks the Launch button (see attached):

Bad Installation. Error invoking Java VM (SysExec)
C:\Program Files\Javasoft\JRE\1.3.1\bin\javaw.exe

The user has a 1.5.0 installation, as well as the 1.3.1 that's being picked up. I have an environment variable named QTJAVA (no idea what it's for) and have asked the user to set his environment to the same value as mine and reboot. He still gets the error message. How does Omniscope know which version of Java it should be looking at?

This sounds like a corrupt Java installation. Usually, the last-installed version of Java takes precedence. Reinstalling Java 5 (or switching to Java 6) is usually the best advice.

With Omniscope Online, we specify Java 1.5+ or later (also called Java 5). Java Web Start is responsible for locating the correct version of Java. This is why this is probably a corrupt Java installation, and reinstalling should fix it.

Have a look at the following:

http://forums.visokio.com/discussion/comment/2266/#Comment_2266