Solved

Opening GML file error - URL resource cache - 'attempt to write a readonly database'

  • 29 August 2017
  • 3 replies
  • 7 views

Badge +6

My company receive AddressBasePremium from OS via disc, the data is stored in zipped GML files and has previously been pretty good to work with, however we may have changed some settings that appear to be affecting our ability to open GML files in desktop or the data inspector, the following error is thrown when attempting to view the data (freshly extracted from disc) in the inspector;

URL resource cache - 'attempt to write a readonly database'

A fatal error has occurred. Check the logfile above for details

Failed to read features from dataset 'E:\\Temp\\AddressBasePremium_FULL_2017-07-03_099_gml\\AddressBasePremium_FULL_2017-07-03_099.gml' using the 'GML' reader

I can't find anything that may be causing this, can anybody offer some assistance? I understand FME will be creating a temporary database for the tabular GML information so assume this may be permission issues, but my user account is a local admin.

icon

Best answer by dbryantgeo 30 August 2017, 17:33

View original

3 replies

Userlevel 4
Badge +13
Hi @dbryantgeo, are you able to share the full log?

 

Userlevel 4
Badge +25

Re the message:

Failed to read features from dataset 'E:\Temp

What is the E drive? Like you I'm thinking FME reads the data and makes a temporary store and that perhaps it's trying to write that store where it shouldn't. Your question says you are extracting the data then reading, and I just want to confirm you aren't reading from the disk directly (shouldn't make a difference, but it's the first thing to come to mind).

Where is your FME temporary path set to? For example, my log tells me:

INFORM|FME Configuration: Temporary folder is `C:\Users\imark\AppData\Local\Temp', set from environment variable `TEMP'

Has that changed recently? 

Also, what platform are you running on? The only reference to this error that I've seen before occurred on a Mac machine. Sadly the user never got back to us to finish figuring out the issue, but on the plus side that means they probably fixed it themselves, so it likely is a system configuration issue imo.

Badge +6

Hi Guys,

Thanks for your help, it was actually a really simple issue that I should have realised before. The FME user didn't have write access to the E drive. Gave them access and it now enables me to open GML files.

Sorry for using your time.

Darren

Reply