Historic Initialization Error in Geo SCADA

[sesa442236]

Hi,

We are getting a configuration error, which details as "The database was unable to initialize historic data, This may be because a directory and/ file has been moved " in the status window.

What are the possible resolution options?

GeoSCADA 2022 May2023 Update

[tfranklin · Accepted solution]

Well that'd be a first for me.  If I had to guess, one of two things. 

1. Your historic folder did in fact move.  I still wouldn't expect to see this on startup though.  I'd think GS would just chug along and start from scratch with no history and wouldn't report an issue, assuming a DB was there.
2. The User that the DBServer process runs as cannot access the directory.

I'd probably start by looking at the permissions on the historic folder in Windows.  Typically there are some DBStartup logs that would help pinpoint what's happening here.  You should also right click that server icon and select the top option.  Usually it'll launch a pop-up window that hints at potential issues, and in this case it might give a clue to a related issue that you're seeing from the image posted. 

[AdamWoodlandToo]

I usually see this when I imported some other server's Registry settings onto a VM, and that server had historic on to something other than C:, and the VM only has a C:.

Check the path in the Registry at HKLM\Software\Schneider Electric\ClearSCADA\DB\, actually check all the paths there are pointing to a valid drive, Historic is probably the first of the Historian locations and Events and the rest are pointing off somewhere else invalid too

Never seen it being just an NTFS permission issue but its possible, DBServer runs as SYSTEM by default and its pretty tough to remove those permissions. If the historic files have been copied then maybe.

[JChamberlain1]

You will want to look at where the server is expecting the DB. Since it was apparently able to initialise the config and data streams, perhaps it has been set to somewhere inaccessible, for example a drive that doesn't exist, has failed or as trent says DBServer doesn't have permissions for. The other thing to look out for is rogue antivirus or similar if you haven't set up exclusions.