Jump to content

< Back to Forum


Errors After Updating Oto 7.5

  • Please log in to reply

#1 andrewfleury 14 March 2017 - 06:40 AM

After updating our test environment to 7.5, everything seems to work except I seem to have a xxxx_vgEngine.txt files regularly filled with an error (not when any of the lines are use). It seems like every minute or so:

163703.873  13               dial  calling DB_Open as conn_Main=null
163703.873  13               Db_Open GetFactory call [VistaDB.NET20]
163703.873  13         ERROR v7.5.6117.35767 (30-Sep-16 18:52:14.30) Db_Open GetFactory : Unable to find the requested .Net Framework Data Provider.  It may not be installed.
   at System.Data.Common.DbProviderFactories.GetFactory(String providerInvariantName)
   at ktlib.vgDb.vgDb_ProviderInvariant.Db_Open()
163704.435   4               stats init exit as bDatabaseInitCompleted not set
163705.435   4               stats init exit as bDatabaseInitCompleted not set
163706.435   4               stats init exit as bDatabaseInitCompleted not set
163707.435   4               stats init exit as bDatabaseInitCompleted not set
163708.435   4               stats init exit as bDatabaseInitCompleted not set

It is still unconfirmed if 7.5 will solve the issue since I could never reproduce this anyways. Only after upgrading to 7.5 and have it running for a few days will we be able to tell

Thank you

#2 SupportTeam 14 March 2017 - 09:38 AM

Looks like your Config.xml file has some very old database settings in it.


Could you please .ZIP up and post your Config.xml file (it is located in VoiceGuide's \conf\ subdirectory)


The issue here will most likely get fixed by removing the database settings from Config.xml and letting VoiceGuide use the default database engine (SQLite).




When installing new version of VoiceGuide over existing version the Config.xml woudl have been kept and the Config.xml that came with new version would  have been saved in file: Config.xml.defaultinstall


It may be good idea to take the Config.xml.defaultinstall and rename that to Config.xml and change the scripts etc. in that file.

(Backup the current Config.xml first).

#3 andrewfleury 14 March 2017 - 11:35 PM

Actually strangely enough, all the old files were in a folder called Config while the new ones were in a folder called conf

I did as you suggested and re-used the default config file coming with the installation and added my scripts to it. This stopped the errors.