03-27-2018 11:02 AM
I´ve added a new vector set to M.Apps Enterprise. the vector layer comes from PostGIS, EPSG 3857 and has cache enabled. After adding the vector layer I created a vector set and tryed to generate a vector set. Everithing looks ok an I get no error messages, but the cache order never gets past the Queued state.
I´m guessing something is not working within the tile server but don know where to look. Any help would be welcome
03-27-2018 11:26 AM
Was this Tile Server publishing Vector Sets without issue previously or is this the first ventures with it?
If it was working previously it may just require a Service restart on the Tile Server. This restart of service has been known to get 'Queued' orders going again on good configurations.
If this is the first few ventures with the Tile Server and it is only queueing the orders instead of processing it likely means there is a configuration issue. For configuration it is important that warehouse user can start the Tile Service (Log on As Service) and should be a local system Administrator User. The warehouse user will also need to be able to write to the warehouse location.
I hope that helps get you started on the issue here.
03-27-2018 11:51 AM
Hi sclow , as you mentioned, it is a fresh install... I’ve used other instances before with no problems, I published the same table in another server with no problems, so I know it is the new installation that´s not working. I´m quite sure the used user accounts are all administrators and have able to write to the warehouse, but I’ll double check that.
03-27-2018 11:55 AM
If the M.App Service and Tile Service are on different servers also check that the Warehouse location configured for the Tile Service is a UNC path and reachable from that server.
03-27-2018 02:37 PM
Checked and checked again... All warehouses are accessible by the users, tile server is under the same computer so there is not communication issue there. The tile service is running with an administrator user.
And still... Queued!
03-28-2018 04:13 AM
Is the Master DB specified for the Tile Service the same as the one specified for M.App Enterprise Application?
If the issue persists after checking and confirming the suggestions on this thread I would recommend the next step be logging a support ticket to get some more in depth investigation.
04-02-2018 12:13 PM
After a several attempts to fix it, I decided to wipe the installation and do a new clean install... this time it works. Don´t know what was wrong but I have a working system now
11-02-2018 05:25 AM
in my new installation, die caching is stuck on queued. You have mentioned the configuration of the Warehouse and its user. I'm not sure how to check these information..
On the installation folder of the Tile Server, I have granted permissions to the local user and restarted the tile server. Is this the right procedure or are there steps missing?
Thank you very much for a short description,
11-05-2018 01:04 PM
M.App Enterprise application server and Tile Server must have read and write access to the warehouse folder. This is normally done by using a local admin account if both app server and tile server are on the same machine. If they are installed on separated machines you must use a shared folder for the Warehouse and either a domain account with proper privileges or 2 local admin accounts identical on both servers (same username and same password).
If the caching is stuck you may have a problem in one of your tenants, please check Studio logs for all of the tenants. In general to unlock it it is anyway enough to restart the Tile Service.