Essential Viewer Error

Post Reply
User avatar
neil.walsh
Posts: 444
Joined: 16 Feb 2009, 13:45
Contact:

HI,

Just in case you're having an issue with the WAR file itself, here is a link to a copy of the essential_viewer.war file.

Delete any essential_viewer.war files and any essential_viewer folders in the existing webapps folder.

Tomcat should deploy (unpack) this WAR file automatically. Do not unzip this file. Similarly, WAR files must be copied to the webapps folder itself and not any sub-folders.

https://app.box.com/s/fcotiapb3lv7hmgl46og

Let us know how you get on.

Cheers

Neil
bien
Posts: 8
Joined: 18 Aug 2014, 04:20

Hi,

Still not working...even with added memory.

Regards
Bien
User avatar
neil.walsh
Posts: 444
Joined: 16 Feb 2009, 13:45
Contact:

Hi Bien,

I'm at little unsure of what things you've tried so before we try to offer any more help can you provide some confirmation on the following. The more information you can provide the better...

Questions...

Do you have full administrator rights to the PC you are using?

Is the PC "locked down" in anyway?

When you ran the Essential installation wizard, did you specify any paths different from the default?

Have you manually created any folders/subfolders within Tomcat?

Are the WAR files in the root of the webapps folder?

Can you provide screenshots of the following?
- The Tomcat webapps folder
- The http://localhost:8080 screen in a browser
- The http://localhost:8080/essential_viewer screen in a browser

Did you try downloading the copy of the WAR file I posted?

If so, when you copy this to the Tomcat webapps folder, does it auto-deploy i.e. does it unpack itself without any intervention from yourself?

I think once we understand these things we can look at what the root cause of the problem is here. As I said earlier, the more information you can provide us regarding the installation then the better we can help.

Cheers

Neil
bien
Posts: 8
Joined: 18 Aug 2014, 04:20

Hi Neil,

Thank you so much - I found out what I was doing wrong.

I created a folder called essential_viewer under webapps. I think I did this at installation - I must have jumped ahead of myself there thinking I needed to manually create it.

I didn't actually see that response regarding downloading the war file.

Of course when unpacking the essential_viewer.war files it will not unpack because of the existing folder it cannot be read. I also placed essential viewer.war file under the essential_viewer folder.

I downloaded the war file you provided and I used Tomcat to unpack it under the webapps root folder and went to localhost:8080/essential_viewer and viola! all there...

Now on to getting information into the intances...

Thanks heaps at least it is now generating the report.

Bien
User avatar
jonathan.carter
Posts: 1087
Joined: 04 Feb 2009, 15:44

Thanks for posting the solution that you found.

Great to hear - and do let us know how you get on from here.

Jonathan
Essential Project Team
expressiontree
Posts: 2
Joined: 25 Jan 2015, 06:59

Very first solution: I tried provided solution but it didn't solve the issue. The reason being that in case if you have everything installed correct and working at browser level can still get this error. Means, if your Essential Viewer is perfect in your browser and available at http://localhost:8080/essential_viewer can still have this issue [if your essential viewer is not available with localhost, try replacing localhost with your machine name].

Ok, so then what is the issue?
Answer is - Nothing :)

there is a trick, go to your http://localhost:8080/essential_viewer and hit enter....
browser will redirect to full url [something like - http://localhost:8080/essential_viewer/ ... e&cl=en-gb]. Wait for complete homepage load and then copy the url. Now use this url in Protege while publishing instead of http://localhost:8080/essential_viewer.

and then publish, :D it worked ! correct?
expressiontree
Posts: 2
Joined: 25 Jan 2015, 06:59

I had similar issue and none of suggestion given here worked. I could resolve publishing issue of Protege by using full url instead of http://localhost:8080/essential_viewer/ from browser for essential viewer.
It looks like http://localhost:8080/essential_viewer/ ... LABEL=Home
But even it resolves Protege publishing issue, but essential viewer doesn't show anything.

after long if and buts, the solution was using Tomcat 6.0.41 and not any higher version. Now everything works as desired.
User avatar
jonathan.carter
Posts: 1087
Joined: 04 Feb 2009, 15:44

To publish to the Viewer, only the first part of the URL is correct. All other parameters in that URL will be ignored and should not be used in the "Essential Viewer" field.

All that's required is http://<HOSTNAME>:<PORT>/essential_viewer

Jonathan
Essential Project Team
Ferel
Posts: 1
Joined: 29 Apr 2015, 13:14

By no means I mean to hijck this thread, but I join in with this problem.
I installed everything and entered some test data, while reading the tutorials. Then I wanted to test the viewer and got the same error. If I enter localhosz:8080/essential_viewer the result is:
Exception encountered during send
Failed to send snapshot to the Report Service:
No response from teh Report Service at this URL.
The command window shows:
I/O exception (java.net.SocketException) caught when processing request: Software caused connection abort: socket write error.

I can access the viewer in my browser by entering the URL. If I check the session list in Tomcat it is empty.
On the other hand if I enter http://localhost:8080/essential_viewer/report?
as the Viewer URL (or copy the URL from the browser) it will open up two sessions (and not close them in the end) with the tomcat server, go through with sending and result in "Sent images: 0" and claiming success.

I tried reinstalling all components, but no avail. Right now I am using Tomcat 8.0.21.

Any further recommendations or things to check if everything is interacting properly?
User avatar
jonathan.carter
Posts: 1087
Joined: 04 Feb 2009, 15:44

Hi,

This is most likely due to the '/' issue that we have encountered with Tomcat 8. Please see this post here, which explains how to resolve it.

Jonathan
Essential Project Team
Post Reply