![]() If the issue persists, please repair your SQL Database by rebuilding the Resource Database using this Microsoft official procedure: The issue you were experiencing should be fixed.Navigate the Console to: Configuration > Database Maintenance Options > Database backend settings.The GFI LanGuard Console should start normally now This will change the Database type of GFI LanGuard from SQL to Access.Locate the key: and change the CDATA value from to.Open the XML file named: toolcfg_database.xml ( rightClick > Edit).Navigated to GFI LanGuard configuration files, usually located in: C:\ProgramData\GFI\LanGuard 11.If the connection succeeds but you still can't access the GFI LanGuard Console, troubleshoot if the issue is still associated with the SQL Server performing the following steps: If the connection fails, troubleshoot your SQL Server.Test the connection to the SQL DB using Windows Authentication or specific user name and password, depending on which settings you've configured in GFI LanGuard.Rename the new text document and change its extensions to.Create an empty document on the Desktop | rightClick > New > Text Document.Open File Explorer and enable View > File name extensions.Verify that the user logged into the server has access to the SQL Database following this procedure: "error ","CrmiModule","Given DB connection is null." ENVIRONMENT Inspecting the log: lanss_v114_dashboard.csv - you notice the following error: The GFI LanGuard console hangs without displaying any error message.Ĭonsulting the EventViewer - Application log you see the Error (1002) : "The program LanGuard.exe stopped interacting with Windows and was closed" ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |