VistaDB valid license error out of nowhere

Hi,

One of our clients starting getting the following error when visiting filevista URL in a shared hosting environment.  It was a previously working installation and client claims that no unusual activity led to the issue.  It is v4 as the hosting provider has not upgraded to ASP.NET 4.0.  An ideas on things to check for to fix this?

Thanks in advance...Mike King




Server Error in '/files' Application.
--------------------------------------------------------------------------------

You must have a valid license to use VistaDB.  Ensure you have a licenses.licx file in your project at compile time. 
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code. 

Exception Details: System.ComponentModel.LicenseException: You must have a valid license to use VistaDB.  Ensure you have a licenses.licx file in your project at compile time.

Source Error: 

An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.  

Stack Trace: 


[LicenseException: You must have a valid license to use VistaDB.  Ensure you have a licenses.licx file in your project at compile time.]
   VistaDB.VistaDBLicense.KKNJDFCNGJKLFHADDGLAGNNFBFLPPKANEBAA(Type , Object ) +55
   VistaDB.VistaDBLicense.OOHDLADFCGDPCBGMAOIGKDPAGOANBBEDKJKI(Type , Object , Boolean ) +48
   VistaDB.VistaDBLicense.OOHDLADFCGDPCBGMAOIGKDPAGOANBBEDKJKI(Boolean ) +39
   LGMJDMOGBJCCGMHCMLJFPDDLKLDPFCMHLKKO.LDDLHFCKEFDBCPCAPDFHCMGMFIHBOMEHOCAM.PDIMBEBMFGKLOBFPNAPPJKLEJDOEOMJLBEPP(String , VistaDBDatabaseOpenMode , String , Boolean , Boolean ) +68

[VistaDBException (0x75): You must have a valid license to use VistaDB.  Ensure you have a licenses.licx file in your project at compile time.
Error 117 (Provider v. 4.0.14.1): Cannot open database:  D:\inetpub\blahblahblah\files\App_Data\database/FileVista.vdb4
]
   LGMJDMOGBJCCGMHCMLJFPDDLKLDPFCMHLKKO.LDDLHFCKEFDBCPCAPDFHCMGMFIHBOMEHOCAM.PDIMBEBMFGKLOBFPNAPPJKLEJDOEOMJLBEPP(String , VistaDBDatabaseOpenMode , String , Boolean , Boolean ) +393
   LGMJDMOGBJCCGMHCMLJFPDDLKLDPFCMHLKKO.LDDLHFCKEFDBCPCAPDFHCMGMFIHBOMEHOCAM.OpenDatabase(String , VistaDBDatabaseOpenMode , String ) +17
   LGMJDMOGBJCCGMHCMLJFPDDLKLDPFCMHLKKO.OBPFHPDCHJFDHDLLILDHCABANGBPBNIDJEFC.OpenDatabase(String , VistaDBDatabaseOpenMode , String , Boolean ) +108
   VistaDB.Provider.VistaDBConnection.Open() +345
   GleamTech.FileVista.DataManager.GetConfiguration() +90
   GleamTech.FileVista.ApplicationManager.LoadConfiguration() +33
   GleamTech.FileVista.ApplicationManager..cctor() +909

[TypeInitializationException: The type initializer for 'GleamTech.FileVista.ApplicationManager' threw an exception.]
   GleamTech.FileVista.ApplicationManager.get_AuthenticationManager() +0
   GleamTech.FileVista.GlobalAsax.Application_AcquireRequestState(Object sender, EventArgs e) +608
   System.Web.SyncEventExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() +68
   System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously) +75

--------------------------------------------------------------------------------
Version Information: Microsoft .NET Framework Version:2.0.50727.3634; ASP.NET Version:2.0.50727.3618 

I managed to fix this issue by downloading a trial version of VistaDB and locating the VistaDB.4.dll file in the rutime folder.

I replaced the VistaDB.4.dll file in the bin folder of filevista application and it started workng again.

I suppose the dll file has some built-in license expiration?  if so, that is a nasty surprise and Isuspect you may have other upset clients run across this issue if they can not upgrade...like me.

Mike,
Sorry for the inconvenience.
This is strange, it shouldn’t have complained about vistadb license because GleamTech.FileVista.dll (v4.0) was already compiled against vistadb. I guess this was caused by a conflicting VistaDB version on the shared hosting. Fortunately, VistaDB removed this license protection in later versions.

For future reference, newer versions of FileVista (after v4.1) includes the license-free VistaDB dll so this should never happen again.

Thanks Cem...good to know.