Okay so I managed to get through the first hurdle, changing the code in the job to
_liveDatabaseFileName = Web.VirtualPathUtilityEx.RebasePhysicalPath(System.Configuration.ConfigurationManager.AppSettings["databaseFileName"]);
and instead adding to web.config
<add key="databaseFileName" value="[appDataPath]\Geolocation\GeoLiteCity.dat" />
Now my next problem is that whatever user the application is using isn't allowed to access the TEMP folder on the server, which is where GeoLiteCity.dat.new is stored. Sooo... next question, to the server techy: How is .NET/ EPiServer users set up with IIS on a Windows Server (2012)? Are this rights maintanable in the code, in config, or in IIS?
I know this isn't exactly EPiServer related so feel free to close this topic.
Okay, so I've found out that this job is an old default job probably going back to EPiServer 6, maybe even older. And it's not functionality we're using.
So, I'm marking this solved on "outdated default scheduled job that's probably no longer a part of EPi and I should probably just remove it".
Hi,
After updating to CMS Core 10.10.1 (from an early 10 version) I seem to have an issue with MaxMind. I'm unsure if it's a MaxMind related issue or has something to do with the configuration (which I haven't touched.) Basically it looks like the code is unable to fetch the property "databaseFileName" from web.config.
web.config:
Place where referenced (it's a scheduled Job):
I get an "Object reference not set to instance of an object" exeption on _liveDatabaseFileName because parameters fetched from the config comes out empty. ("Enumeration yielded no results".)
Again, this might not be EPiServer related at all, but if anyone has any hints on where I should start looking, that would be greatly appreciated. (I was unable to find any release information from MaxMind, although I didn't look too hard.)