Choose from several options for complete web, email and data security.
Evaluate Websense products by watching demos and installing evaluation software.
Learn how Websense solutions help keep our customer safe, secure and productive
Get information on product updates, support resources and more.
Get the most out of support in five simple steps.
Find tools and assets to help sell Websense solutions.
Come work for the global leader in unified information security.
Triton USC on one server
Log Server, Policy Server and all the other services on another server.
Customer is having an issue on the Triton USC, when he logs an alert says that Log Database is not available. I follow all steps to reconffigure the ODBC connection on the server with the Triton USC, I even use the Triton installer with no success.
So I decide to delete the ODBC configuration, log again to clean the old configuration and retry, but when I log again, the error is gone, I even clean some old partitions, and everything is fine.
So this leads me to the following question. Does Websense store database configuration on another place? registry, tomcat?
Hope this helps someone else, and hope Websense can shed some light on database configuration.
We have a very similar scenario where WS doesn't want to connect to any of the old databases. We had to rebuild our deployment due to a faulty NIC issue - apparently Websense can't cope with a bad NIC or swapping the NIC. The answer was build a new server - lucky for us it was VM & we had the resources because this meant totally trashing our deployment and starting from scratch. At this point we couldn't get the server to communicate with the SQL connection, no matter that nothing had changed SQL side. The solution - build a new instance and get that working. Now we can't retrieve historic data. WS just won't communicate with the old databases. I currently have a call open with support and will be happy to share any solution if/when discovered.
If you named your new instance with a different name, there are good chances you can still access your old data.
Depending on your OS your configuration should be found under:
Windows 32-bit server: Select Start > Control Panel > Administrative Tools > Data Sources (ODBC).
Windows 64-bit or R2 server: Navigate to the %SystemDrive%\Windows\SysWOW64 directory and launch the odbcad32.exe application. Ensure that you right click on the executable and select Run As Administrator.
Whenever you want to access your old data you can do so by changing database under:
Main > Reporting > Investigative Reports > Options >
Check event viewer on your Log Server in order to see the reason why you can't access your old instance.
Thanks for the response. We've been through all of that, guess my post wasn't very clear. Yes, our configuration is all on a single server & yes we created a new instance which is different from the environment you describe. However, the reason I replied to your post is that I believe WS is holding onto information that has since been modified - IE server / instance / database / account information, etc... This is what I'm after, what you originally were looking for - is there a file that contains this information somewhere else that was perhaps overlooked during an upgrade or migration - IE config file, registry, tomcat, etc...