Hi,
I haven't stumbled into this issue before, but I don't look much into
Windows deploys.
I can only guess... are you using the default data directory, and is it
placed in "c:\programs\..."?
If so, I have vague memories of Windows having some sort of protection
under there, not allowing
changes on disk (actually, reverting them I believe).
If that's the case, maybe install setting an external data directory (it's
always good practice anyways)
and make sure the user that's running the GeoServer service can write on it
Cheers
Andrea
On Sat, Aug 4, 2018 at 1:51 AM Carlock, Brett <bcarl...@agrinetix.com>
wrote:
> Hi! Firstly, thanks for your excellent software. GeoServer is an amazing
> tool and I have rather enjoyed my time learning about it this past year.
>
>
>
> Background:
>
> Windows x64 Host (Server 2012)
>
> Oracle JRE8v181 x86
>
> Pure Java JAI/JIO
>
> GeoServer v2.13.2 installed as a Service with the Tanuki Wrapper
>
> GeoServer data-dir that has been migrated from 2.5.x up to 2.13.2
>
> Semi-Manual rename of files/folders and edits of coverage/layer/store xml
> files to make everything XML-Safe accomplished by me when migrating from
> 2.8.x to versions beyond (2.12.3) [a whole other issue :C]
>
> Things worked fine until migration from 2.12.3 to 2.13.0.
>
>
>
> Issue summary:
>
> Layers that I add with new Stores (for example: Rx.tiff or Rx.shp with
> associated SLD) will be rendered perfectly fine in the Preview Layers
> section in GeoServer, as well as being able to be seeded/cached using the
> embedded GWC, and the cached tiles previewed perfectly fine through the GWC
> Tile Layers Preview function.
>
>
>
> QGIS v2.18.22 and v3.2.1 load/display/query the above layers perfectly
> fine.
>
>
>
> Gdalinfo does not report anything that appears to be amiss to me.
>
>
>
> These same layers WILL NOT draw/display through our website wrapper (based
> upon OpenLayers), yet layers that existed prior will render just fine.
>
>
>
> Neither the wrapper log nor the data-dir log seem to throw any
> exceptions/info/warn when those layers are “turned on” in our web wrapper.
>
>
>
> I’ve looked through the mailinglist, Bing/Google, SE, SO and have not come
> across this issue before.
>
>
>
> I’ve almost convinced myself that nuking our data-dir and rebuilding
> manually would be worthwhile since I’m sure I introduced some funkiness
> when I did my XML-Safe sprint to get beyond 2.8.x, but there are around
> 1000 layers/stores and about 230 workspaces, so I’m hoping I can (with some
> help/guidance/knowledge) fix up what we have running.
>
>
>
> Thank you sincerely for your time and any help I may receive,
>
> Brett
>
> ------------------------------------------------------------------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> _______________________________________________
> Geoserver-users mailing list
>
> Please make sure you read the following two resources before posting to
> this list:
> - Earning your support instead of buying it, but Ian Turton:
> http://www.ianturton.com/talks/foss4g.html#/
> - The GeoServer user list posting guidelines:
> http://geoserver.org/comm/userlist-guidelines.html
>
> If you want to request a feature or an improvement, also see this:
> https://github.com/geoserver/geoserver/wiki/Successfully-requesting-and-integrating-new-features-and-improvements-in-GeoServer
>
>
> Geoserver-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/geoserver-users
>
--
Regards, Andrea Aime == GeoServer Professional Services from the experts!
Visit http://goo.gl/it488V for more information. == Ing. Andrea Aime
@geowolf Technical Lead GeoSolutions S.A.S. Via di Montramito 3/A 55054
Massarosa (LU) phone: +39 0584 962313 fax: +39 0584 1660272 mob: +39 339
8844549 http://www.geo-solutions.it http://twitter.com/geosolutions_it
------------------------------------------------------- *Con riferimento
alla normativa sul trattamento dei dati personali (Reg. UE 2016/679 -
Regolamento generale sulla protezione dei dati “GDPR”), si precisa che ogni
circostanza inerente alla presente email (il suo contenuto, gli eventuali
allegati, etc.) è un dato la cui conoscenza è riservata al/i solo/i
destinatario/i indicati dallo scrivente. Se il messaggio Le è giunto per
errore, è tenuta/o a cancellarlo, ogni altra operazione è illecita. Le
sarei comunque grato se potesse darmene notizia. This email is intended
only for the person or entity to which it is addressed and may contain
information that is privileged, confidential or otherwise protected from
disclosure. We remind that - as provided by European Regulation 2016/679
“GDPR” - copying, dissemination or use of this e-mail or the information
herein by anyone other than the intended recipient is prohibited. If you
have received this email by mistake, please notify us immediately by
telephone or e-mail.*
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Geoserver-users mailing list
Please make sure you read the following two resources before posting to this
list:
- Earning your support instead of buying it, but Ian Turton:
http://www.ianturton.com/talks/foss4g.html#/
- The GeoServer user list posting guidelines:
http://geoserver.org/comm/userlist-guidelines.html
If you want to request a feature or an improvement, also see this:
https://github.com/geoserver/geoserver/wiki/Successfully-requesting-and-integrating-new-features-and-improvements-in-GeoServer
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users
