WebGIS Discussions

Need a push in the right direction when configuring WebMap, Portal or SDI services? Looking for hints and tips, or just looking for Ideas and information? The WebGIS discussion board is where you start those discussions, connect and share information.
Showing results for 
Search instead for 
Do you mean 
Reply
Highlighted
Regular Contributor
Posts: 224
Registered: ‎07-27-2016
Accepted Solution

WMPS cache build fails

Hi Guys,

 

I am at a loss.
Maybe someone can point me in a direction I have not tried already.

We have 2 servers running the same version of webmap (2018 Update 1)
Both of them have the same service source, lets call it Wmps_A with the same workspaces published to them.Both have their metadata located on a SQL server instance with the actual data being displayed pulled from Oracle


The only difference is that the one gets the data from a production oracle database and the other from a QA oracle database.
Structure between the 2 databases are the same , production data just more up to date.

Both these service sources worked fine for a few months(QA still does), then the production WMPS_A cache started not building up completly.
First I thought maybe there is some geometry issues in the new data that QA does not have explaining why QA WMPS_A is still fine.
Long story short, I asked the DB Admin to refresh(clone) production to QA and this will cause QA to have the same effect so I can start fiddling with it.
After the clone , I tested WMPS_A on QA, it was working fine.Deleted all WMPS_A cache and xml capabilities files , again rebuild was completed with no issue.
I have removed WMPS_A SC from production , re-created it and replaced the metadata with a copy of the QA WMPS_A metadata, also replace the webmap publisher directory with the one from QA , still same effect.
Cache rebuild always stops at 174 of 401 images with xml about 10% of the size it should be.
I created a new WMPS_Test on production , and also used the QA metadata, stil exact same effect 174 of 401 images with xml about 10%

So in theory both WMPS_A on QA and WMPS_A on Production is the same...uses the same metadata pointing to the same oracle data , but the one on the qa server builds cache completly and the one on production not.

FYI: Webmap on the Production server has about 12 WMPS applications , 11 of them builds fine and works fine.

Here is a log snippit , cache images build fine until here (Cant see any issue related to legend entry 84):

2019-12-18 09:11:05,383 [ 16] DEBUG Pipes for: 82 - {Intergraph.WebSolutions.Core.MapPublisherConnector.Service.Common.PipeTree.PipeTreeInfoProvider}
2019-12-18 09:11:05,383 [ 16] DEBUG OriginatingPipe - {Intergraph.WebSolutions.Core.MapPublisherConnector.Service.Common.PipeTree.PipeTreeInfoProvider}
2019-12-18 09:11:12,320 [ 16] WARN Failed filtering OriginatingPipeRecordSet with "1=0". Exception from HRESULT: 0x80040131 - {Intergraph.WebSolutions.Core.MapPublisherConnector.Service.FeatureClass}
2019-12-18 09:11:12,352 [ 16] DEBUG End FilterLegendEntryRS. - {Intergraph.WebSolutions.Core.MapPublisherConnector.Service.FeatureClass}
2019-12-18 09:11:12,399 [ 16] DEBUG Legend icon created at C:\Program Files\Common Files\Hexagon\Services\Instances\WMPS-Service\\cache\WMPS_ITIS_TEST\82.png - {Intergraph.WebSolutions.Core.MapPublisherConnector.Service.Legend}
2019-12-18 09:11:12,414 [ 16] DEBUG Creating legend graphic for 83 - {Intergraph.WebSolutions.Core.MapPublisherConnector.Service.Legend}
2019-12-18 09:11:12,414 [ 16] INFO Obtained secret key - {Intergraph.WebSolutions.Core.MapPublisherConnector.Service.Utils}
2019-12-18 09:11:12,414 [ 16] INFO Obtained secret key - {Intergraph.WebSolutions.Core.MapPublisherConnector.Service.Utils}
2019-12-18 09:11:12,414 [ 16] DEBUG Regular legend entry, filtering - {Intergraph.WebSolutions.Core.MapPublisherConnector.Service.Legend}
2019-12-18 09:11:12,414 [ 16] DEBUG Start FilterLegendEntryRS. - {Intergraph.WebSolutions.Core.MapPublisherConnector.Service.FeatureClass}
2019-12-18 09:11:12,414 [ 16] DEBUG Pipes for: 83 - {Intergraph.WebSolutions.Core.MapPublisherConnector.Service.Common.PipeTree.PipeTreeInfoProvider}
2019-12-18 09:11:12,430 [ 16] DEBUG OriginatingPipe - {Intergraph.WebSolutions.Core.MapPublisherConnector.Service.Common.PipeTree.PipeTreeInfoProvider}
2019-12-18 09:11:17,117 [ 16] WARN Failed filtering OriginatingPipeRecordSet with "1=0". Exception from HRESULT: 0x80040131 - {Intergraph.WebSolutions.Core.MapPublisherConnector.Service.FeatureClass}
2019-12-18 09:11:17,149 [ 16] DEBUG End FilterLegendEntryRS. - {Intergraph.WebSolutions.Core.MapPublisherConnector.Service.FeatureClass}
2019-12-18 09:11:17,149 [ 16] DEBUG Legend icon created at C:\Program Files\Common Files\Hexagon\Services\Instances\WMPS-Service\\cache\WMPS_ITIS_TEST\83.png - {Intergraph.WebSolutions.Core.MapPublisherConnector.Service.Legend}
2019-12-18 09:11:17,164 [ 16] DEBUG Creating legend graphic for 84 - {Intergraph.WebSolutions.Core.MapPublisherConnector.Service.Legend}
2019-12-18 09:11:17,164 [ 16] INFO Obtained secret key - {Intergraph.WebSolutions.Core.MapPublisherConnector.Service.Utils}
2019-12-18 09:11:17,164 [ 16] INFO Obtained secret key - {Intergraph.WebSolutions.Core.MapPublisherConnector.Service.Utils}
2019-12-18 09:11:17,164 [ 16] DEBUG Regular legend entry, filtering - {Intergraph.WebSolutions.Core.MapPublisherConnector.Service.Legend}
2019-12-18 09:11:17,164 [ 16] DEBUG Start FilterLegendEntryRS. - {Intergraph.WebSolutions.Core.MapPublisherConnector.Service.FeatureClass}
2019-12-18 09:11:17,164 [ 16] DEBUG Pipes for: 84 - {Intergraph.WebSolutions.Core.MapPublisherConnector.Service.Common.PipeTree.PipeTreeInfoProvider}
2019-12-18 09:11:17,180 [ 16] DEBUG OriginatingPipe - {Intergraph.WebSolutions.Core.MapPublisherConnector.Service.Common.PipeTree.PipeTreeInfoProvider}
2019-12-18 09:11:20,555 [ 16] ERROR Exceptin while FilterLegendEntryRS - {Intergraph.WebSolutions.Core.MapPublisherConnector.Service.FeatureClass}
System.Runtime.InteropServices.COMException (0x800706BE): The remote procedure call failed. (Exception from HRESULT: 0x800706BE)
at Intergraph.GeoMedia.PipelineHelper.IPipelineHelper.GetDuplicateQueryPipelineWithNoRecords(Query InputQuery, Queries& OutputOPQueries)
at Intergraph.WebSolutions.Core.MapPublisherConnector.Service.FeatureClass.GetDuplicateRecordSetWithNoRecords(GWMMapServerHelper mapServer, GRecordset objGrs)
at Intergraph.WebSolutions.Core.MapPublisherConnector.Service.FeatureClass.FilterOriginatingPipeRecordsetByAttributeFilter(GWMMapServerHelper mapServer, LegendEntry objLegendEntry, String sFilter)
at Intergraph.WebSolutions.Core.MapPublisherConnector.Service.FeatureClass.FilterLegendEntryRS(GWMMapServerHelper mapServer, LegendEntry objLegendEntry, String filter, String applicationId, String metadataConnectionString)
2019-12-18 09:11:20,555 [ 16] DEBUG Could not create legend graphic - {Intergraph.WebSolutions.Core.MapPublisherConnector.Service.Legend}
System.Runtime.InteropServices.COMException (0x800706BE): The remote procedure call failed. (Exception from HRESULT: 0x800706BE)
at Intergraph.GeoMedia.PipelineHelper.IPipelineHelper.GetDuplicateQueryPipelineWithNoRecords(Query InputQuery, Queries& OutputOPQueries)
at Intergraph.WebSolutions.Core.MapPublisherConnector.Service.FeatureClass.GetDuplicateRecordSetWithNoRecords(GWMMapServerHelper mapServer, GRecordset objGrs)
at Intergraph.WebSolutions.Core.MapPublisherConnector.Service.FeatureClass.FilterOriginatingPipeRecordsetByAttributeFilter(GWMMapServerHelper mapServer, LegendEntry objLegendEntry, String sFilter)
at Intergraph.WebSolutions.Core.MapPublisherConnector.Service.FeatureClass.FilterLegendEntryRS(GWMMapServerHelper mapServer, LegendEntry objLegendEntry, String filter, String applicationId, String metadataConnectionString)
at Intergraph.WebSolutions.Core.MapPublisherConnector.Service.Legend.createLegendEntryGraphic(GWMMapServerHelper mapServer, LegendEntry objLE, String urlImage, String applicationId)
2019-12-18 09:11:20,571 [ 16] DEBUG Disposing of the BoundingBoxTransformer - {Intergraph.WebSolutions.Core.MapPublisherConnector.Service.Common.BoundingBoxTransformer}
2019-12-18 09:11:20,571 [ 16] DEBUG -- disposing of AltCoordSystemPaths - {Intergraph.WebSolutions.Core.MapPublisherConnector.Service.Common.BoundingBoxTransformer}
2019-12-18 09:11:20,571 [ 16] DEBUG -- disposing of CoordSystemsMgrs - {Intergraph.WebSolutions.Core.MapPublisherConnector.Service.Common.BoundingBoxTransformer}
2019-12-18 09:11:20,571 [ 16] DEBUG -- disposing of CoordSystems - {Intergraph.WebSolutions.Core.MapPublisherConnector.Service.Common.BoundingBoxTransformer}
2019-12-18 09:11:20,571 [ 16] DEBUG -- disposing of the ServerTransService - {Intergraph.WebSolutions.Core.MapPublisherConnector.Service.Common.BoundingBoxTransformer}
2019-12-18 09:11:20,571 [ 16] ERROR Session Identifier: urn:uuid:cc31b0b2-58d5-4fd4-be2e-122b8cacac59 message: Error Get Legend by Application Id: WMPS_ITIS_TEST. Error message: The RPC server is unavailable. (Exception from HRESULT: 0x800706BA) - {Intergraph.WebSolutions.Core.MapPublisherConnector.Service.Legend}
2019-12-18 09:11:20,571 [ 16] INFO Session Identifier: urn:uuid:cc31b0b2-58d5-4fd4-be2e-122b8cacac59 message: End Get Legend from Application: WMPS_ITIS_TEST - {Intergraph.WebSolutions.Core.MapPublisherConnector.Service.Legend}
2019-12-18 09:11:20,571 [ 16] DEBUG Open Connection - {Intergraph.WebSolutions.Core.MapPublisherConnector.Service.MapPublisherApplication.MapPublisherApplicationCapabilitiesBuilder}
2019-12-18 09:11:20,571 [ 16] DEBUG >>> Begin GetQueryCollection() <<< - {Intergraph.WebSolutions.Core.MapPublisherConnector.Service.Legend}
2019-12-18 09:11:20,571 [ 16] DEBUG Getting queries parameters collection - {Intergraph.WebSolutions.Core.MapPublisherConnector.Service.Legend}
2019-12-18 09:11:20,571 [ 16] DEBUG Getting Queries Collection. - {Intergraph.WebSolutions.Core.MapPublisherConnector.Service.Legend}

 

Any help will be greatly appreciated.

 

Kind Regards

Jacques

Highlighted
Technical Evangelist
Posts: 1,307
Registered: ‎09-11-2015

Re: WMPS cache build fails

Hi Jacques,

 

When you compare the working and non-working WMPS capabilities XML, can you perhaps note the legend entry before which the XML generation stopped? Then create a new service source with just this one legend entry and see if it builds the WMPS cache fine?

 

The HRESULT message says something about error while trying to obtain GRecordset Extension (if I'm not mistaken). It could as well mean that there's a problem in GDO metadata for the feature class (not the publisher metadata).

 

Jan

Jan Neumann
Post Sales Engineer Web Applications
Hexagon Geospatial

Highlighted
Regular Contributor
Posts: 224
Registered: ‎07-27-2016

Re: WMPS cache build fails

Hi Jan,

 

Thanks for the reply.

I actually figured it out this morning after a long struggle, and now it just seems silly.

QA build fine cause I think the response from the QA database is much quicker due to less activity.

So given the fact that the service source is reasonably large the instance timed out while building cache.

After expanding the timout of webmap on the production server the cached build fine.

 

Kind Regards

Jacques