POST
|
Glad to hear you were able to solve the issue! Thanks for posting your solution.
... View more
02-01-2013
10:54 AM
|
0
|
0
|
11
|
POST
|
Duplicate thread. Let's consolidate our collective responses and replies here: https://sourceforge.net/projects/geoportal/forums/forum/1096644/topic/6635299/index/page/1
... View more
01-25-2013
04:22 AM
|
0
|
0
|
43
|
POST
|
Okay, fishing expedition. Let's check on some basics. 1. Tomcat is running and you can log in to Tomcat manager. http:// <your_server>:8080/manager/html 2. From the Tomcat App Manager, you can see a /geoportal listed under Applications? 3. What happens when you click on the /geoportal link from the Tomcat manager app? Other questions: a. The geoportal web app is deployed in <tomcat_directory>/webapps. Example: C:\Program Files\Apache Software Foundation\Tomcat 7.0\webapps\geoportal b. Your are using the right Postgres JDBC driver for your 9.1 database: postgresql-9.1-903.jdbc4.jar c. The JDBC driver is deployed to <tomcat_directory>/lib d. You have set up the JDBC configuration file (geoportal.xml) and it is in the <tomcat_dir>/conf/Catalina/localhost folder. OPTIONAL CONFIG: Rename geoportal.xml file as context.xml, and move it to the geoportal/META-INF folder. And a suggestion: After making any change to your setup/config, stop Tomcat, delete all the log files, and restart Tomcat. That way you are always looking at fresh logs and the latest errors and warnings (rather than old errors).
... View more
01-24-2013
10:48 AM
|
0
|
0
|
14
|
POST
|
Then (most likely) the issue lies with how the ExtractTask is deployed and configured on ArcGIS Server. Can you check if the ArcGIS Server account (arcgis or arcsoc) has all the write/read/execute privileges it needs on the folders being used by the Extract Task? You might want to review the information in this link: "Making your data accessible to ArcGIS Server", http://resources.arcgis.com/en/help/main/10.1/index.html#/Making_your_data_accessible_to_ArcGIS_Server/01540000039r000000/
... View more
01-24-2013
10:18 AM
|
0
|
0
|
11
|
POST
|
Are there any other errors in the log file? What port are you running Tomcat on? (when you say localhost: port#, you are specifying a specific port number correct? like localhost:8080/geoportal)
... View more
01-24-2013
05:22 AM
|
0
|
0
|
14
|
POST
|
Not seen this behavior before. Have you verified that the Extract Task works from running it within ArcMap? Verified the Extract Task works from the ArcGIS Server REST API?
... View more
01-23-2013
05:11 AM
|
0
|
0
|
11
|
POST
|
And you are still not seeing any search results? May I ask you to change the approval status of all your approved records to 'Disapproved', then filter on 'Disapproved' records and set them all to 'Approved' and see if that makes a difference (i.e. you get search results).
... View more
01-23-2013
05:09 AM
|
0
|
0
|
43
|
POST
|
Something is broken on the gpt.rar you attached. Sounds like the metadata is not getting written to the Geoportal index. You can view the index from http:// <insert your Geoportal server domain>/geoportal/rest/index/stats. Likely culprits to investigate: 1. The Geoportal index location exists and is specified correctly in gpt.xml (value in /lucene/indexLocation) 2. Make sure the index location path is writable by the process running the Geoportal Server web container Good luck
... View more
01-18-2013
04:52 AM
|
0
|
0
|
43
|
POST
|
I'm 99% sure your customizations to the INSPIRE profile web editor are the cause. Did you make a backup before customizing, if you need to roll back? Anyway, I've seen these errors before after customizing an Profile for the editor. Here's the likely culprit: The metadata is validating against an XSD (the URL specified in /schema/xsdLocation of the INSPIRE definition.xml file). That shouldn't be a problem, right? Well, the XSD *only wants to see the metadata elements in the EXACT order* as they are written in the XSD URL. So, even if your custom INSPIRE is writing out all the metadata elements correctly, you will still see the errors provided in the starting thread because the XSD validation is failing. It's not a Geoportal issue, it's an XSD issue. And yes, it can be very frustrating. The solution? Make sure the organization (tabs, etc) in your custom INSPIRE profile editor write the metadata elements out in the same order as the XSD. (or ... remove the XSD validation 😉 Good luck
... View more
01-17-2013
04:34 AM
|
0
|
0
|
26
|
POST
|
Looks like Geoportal is classifying your metadata as ISO INSPIRE profile. Is that correct (what you expect)? Are you trying to save the metadata through an Upload or through the built-in editor? Have you made customizations to your INSPIRE metadata profile definition and/or editor?
... View more
01-16-2013
06:50 AM
|
0
|
0
|
26
|
Online Status |
Offline
|
Date Last Visited |
03-11-2021
01:09 PM
|