Hexagon Geospatial
MENU

Developer Discussions

Discuss topics with other Hexagon Geospatial Power Portfolio developers and experts to get the most out of our products.
Showing results for 
Search instead for 
Do you mean 
Reply
Highlighted
dal
Contributor
Posts: 39
Registered: ‎05-09-2016
Accepted Solution

WebMap 2016: Unable to create library database objects. Standard metadata tables may be missing

Dear all,

 

We encountered an issue with WebMap 2016 (16.00.0100.0009) in conjunction with WMS-Service sources (created with WebMap 2016) having dynamic labels.

On the testserver everything works well. However, on the productive system, we encounter quite a bunge of event-viewer entries saying "unable to create library database objects. Standard metadata tables may be missing".

 

The above mentioned event-viewer entries always refer to a WebMap log files. The refered log-files show two different patterns:

1) Pattern 1: Logfile not containing any error --> {C3BB2BD7-B385-4584-88DC-41EF921605D2}.GWMLog

2) Pattern 2: Logfile with a pretty mysterious entry: "GMWS: Error - GetLegendEntry: GetLegendEntries: The Method '~' for the Object '~' failed --> {A07C060D-8DAB-4AD0-932F-D1DB8B555F9C}.GWMLog (--> however, the error message is originally logged in German: "Die Methode '~' für das Objekt '~' ist fehlgeschlagen")

 

Has anybody an idea what might cause this error message? And, what might be the reasons for causing the event-viewer error message "unable to create library database objects. Standard metadata tables may be missing"

 

Any hints are highly appreciated.

Thanks and Regards,

Dominik

hbm
Staff
Posts: 279
Registered: ‎11-05-2015

Re: WebMap 2016: Unable to create library database objects. Standard metadata tables may be missing

Both the log files indicate an error condition, dal. Even though one of them is not entirely obvious:

{A07C060D-8DAB-4AD0-932F-D1DB8B555F9C}.GWMLog
2017-04-12 13:55:28 (1.259404) - Connected 80040bc6
2017-04-12 13:55:28 (1.259432) - End of ActivateOrConnectLibrary 80040bc6
2017-04-12 13:55:28 (1.261531) - Exiting AddLibraryConnection - 80040bc6

{C3BB2BD7-B385-4584-88DC-41EF921605D2}.GWMLog
2017-04-12 13:58:42 (0.937650) - Connected 80040bc6
2017-04-12 13:58:42 (0.937675) - End of ActivateOrConnectLibrary 80040bc6
2017-04-12 13:58:42 (0.938836) - Exiting AddLibraryConnection - 80040bc6


Lots and lots of detailed GWMLog entries don't indicate an error connection directly, but instead append a HRESULT to the log line.

 

According to http://community.hexagongeospatial.com/t5/WebGIS-Q-A/COMException-error-from-HRESULT-while-working-w... this HRESULT means GF_HE_TooManyOpenTables which might be related to the fact that you are using a myriad of Access Warehouse libraries and saturated the global connection limit of the JET OLEDB provider, see answer to this stack overflow question: http://stackoverflow.com/questions/5367668/how-many-users-can-open-a-connection-to-microsoft-access

dal
Contributor
Posts: 39
Registered: ‎05-09-2016

Re: WebMap 2016: Unable to create library database objects. Standard metadata tables may be missing

Thanks for the hint. It is very likely that we're confronted with the open-tables-limitation of Access in this particular situation. I'll discuss further steps with our customer.

 

Regards,

Dominik

Contributor
Posts: 60
Registered: ‎03-08-2017

Re: WebMap 2016: Unable to create library database objects. Standard metadata tables may be missing

hbm,

 

we have around 40 WMS services on one server and we seem to be reaching this msaccess limit.

 

Any workaround on your side ? What's is the known maximum number of services on one server ?

 

Thanks

Technical Evangelist
Posts: 790
Registered: ‎09-11-2015

Re: WebMap 2016: Unable to create library database objects. Standard metadata tables may be missing

Hi Olyster,

 

A workaround is to not use Access for metadata, you can use SQL server (Express it just fine) and Oracle (which seems bit too bulky for this scenario).

 

There's no real limit of maximum number of services as it rather depends on the number of users and MapServer instances. hbm will perhaps correct me :-)

 

Jan

Jan Neumann
Post Sales Engineer Web Applications
Hexagon Geospatial

Contributor
Posts: 60
Registered: ‎03-08-2017

Re: WebMap 2016: Unable to create library database objects. Standard metadata tables may be missing

[ Edited ]

Hi jan,

 

here, the maximum number of services we can have on a single server is 30. The 31st causes the 0x80040BC6 - GF_HE_TooManyOpenTables error.

 

We thought about using Oracle or Sql Server but, correct me if I'm wrong, we need one schema per service. That means that if we have 40 services with four levels of development (dev, integration, system, production) we will have to manage 160 users. It's feasable but I think that the data model should be able to manage many services with a single user.

 

Thanks for your answer jan and have a nice one !

 

 

 

Technical Evangelist
Posts: 790
Registered: ‎09-11-2015

Re: WebMap 2016: Unable to create library database objects. Standard metadata tables may be missing

Hi Olyster,

 

You are correct about that you need single schema per service source.

Unfortunately this is a legacy on how was the original service source architecture created years back and it would require some amount of redesign efforts in order to handle multiple data sets in a single schema. A couple of more tables would be needed + there's a risk that a single corruption could affect more than one service.

 

Maybe you could just split the usage to:

  • DEV, TEST, INTEGRATION - use Access
  • PROD - use Oracle

 

Jan

Jan Neumann
Post Sales Engineer Web Applications
Hexagon Geospatial

hbm
Staff
Posts: 279
Registered: ‎11-05-2015

Re: WebMap 2016: Unable to create library database objects. Standard metadata tables may be missing

What Jan said stands with the small correction that the number of connections made to the metadata does not depend on the number of external WebMap users. The variables that affect this are the number of service sources, number of map servers on the machine and the service source type as the WebMap Publisher Portal type is a bit more metadata hungry than the WMS and WFS ones. Hard limits on maximum number of simultaneous connections and open tables exist for this type of "database". They are 255 and 2048 respectively. These are system-wide.
The WebMap Publisher Metadata are in part a GeoMedia Library and as long as those require different users to be isolated, it will stay true for WebMap.
Contributor
Posts: 60
Registered: ‎03-08-2017

Re: WebMap 2016: Unable to create library database objects. Standard metadata tables may be missing

hbm,

 

thanks for the informations.

 

FYI : there was 8 MapServers originally and I got the error when adding the 31st service. I then tried with one Mapserver and I still got the error on the 31st service ?!

Do you need immediate support?
Please submit a Ticket through our
Development Ticket Portal.