Help Center
News
Help Center
News
Popular
Architecture and High-level Information
Scans
Agents
How to Use Dashboards
How to Use Data Asset Inventory
How to Install\Uninstall and Set Up Spirion Sensitive Data Platform
How to Use Logs
How to Manage Users and Roles
Settings and Resources
Additional Resources
Reports
Reporting API
Customer Support Articles
How to Follow Data Through the Search PipelineEndpoint for Windows Configuration Reference GuideEndpoint Software Command Line InterfaceBasic Troubleshooting Steps (Enterprise Console)Endpoints or Results Fail to be Displayed in the ConsoleMongoDB and TLS 1.3SQL Client SQL Exception ErrorHow to Troubleshoot Spirion Client Search Failures and How to WhitelistCustomer Notice – Spirion Agent Update & Security Assessment for PostgreSQLHow to Enable Verbose/Debug Logging for the Endpoint ServiceHow can I monitor the status of a queue job?Can I monitor the job queue status automatically?Troubleshooting: "Unable to find job queue: search_queue"How to Verify the Discovery Agent's StatusHow to check if port 6433 is open on your networkWhat is the SDM Translator Service?How to Create a Single Tenant App for OneDrive and Exchange Online SearchesHow to Configure Spirion for Sybase DiscoveryHow to Use Certificates to Authenticate with SharePoint OnlineHow to Quarantine to a Remote Location Using Spirion Sensitive Data PlatformA Server Error has Occurred: How to use the Chrome Developer ToolsWhy doesn't my Oracle 19c Database scan?How to Enable Full Disk Access on a Mac AgentWhy is My Scan Node Running Out of Disk Space?What to do about Message Processing and Delays, also known as 'Lag,' in SpirionDetails About the Box API used by Spirion to Search Box AccountsHow to Build a Mac Package (PKG)How to Sanitize AgentsHow to Set User and Role AccessHow to Enable SSL Communication between Linux Agents and the Spirion ConsoleHow to Enable HTTPS for the Spirion ConsoleHow to Search BoxFAQ: How do I avoid being prompted to re-login to the Spirion console?Spirion Sensitive Data Platform Scan PerformanceHow to Authenticate to SharePoint On-PremiseHow to Configure Spirion Sensitive Data Platform to Connect to an Oracle DatabaseFAQ: Linux 12.5 Client Package Build WorkaroundTroubleshoot Exchange Online Using Microsoft Graph ExplorerFAQ: What to do when an agent will not start the discovery team scan?Required SQL Server PermissionsHow to Scan Microsoft Teams with Spirion Sensitive Data PlatformField Input Using Linux Machines Anti-virus Alerts Received during Spirion SearchVersion 13.6 MSI Installation Issues - Exe file not signedWhat are common firewall rules needed for distributed scans?
Release Notes

How to Configure Spirion for Sybase Discovery

Use this article to configure the Spirion Windows Client for Sybase discovery.

Requirements

Read should be the only permission that is needed to search a database. To test you can run a query to get data under the same user, if it can query data then the Spirion Client should be able to do it also using the same user credentials.

How to Install Sybase Client

Discovery of Sybase requires a component of the Sybase Open Client with the libsybct.dll or libct.dll in a location registered in the PATH System variable.

NOTE – You may need to restart your machine after installation in order to add the location of the client DLLs to the system PATH environment variable. This can be confirmed by reviewing the PATH system variable to ensure that C:\SAP\OCS-16_0\dll has been added.

 

How to Create a sql.ini File

A sql.ini file is used by the client to reference need path information to the database server. After the client is installed create a sql.ini file in c:\SAP\ini with a configuration to match your installation. This INI file may be copied directly from the Sybase server, however, only the query service type is needed. 

Take note of the server name between the square brackets in the INI file as this will be used as the server name in the connection configuration. In the example below the server name is sybase1 will be used.

Note: In this example, it is configured to use port 5020

How to Configure and Test

Initial database configuration and testing are best accomplished using the Spirion Client for Windows.  Once the connection string is successfully built and tested it can be copied to a console policy for a scheduled search process. 

Configuration of Sybase requires:

  • Server Name - Server name comes from a sql.ini file that identifies the server by IP and port
  • User Name - Valid account with at least read permissions to the target databases
  • Password - Valid password for the User Name being used to connection
    (Optional) Database Name - a specified database on the targeted server

Use the following steps to Configure and Test Connection:

  1. Launch the Spirion Client for Windows.
  2. Click the Locations tab.
  3. Click the arrow below Databases and select Customize Database Settings

  4. Click in the Database Type field to reveal the drop down of built in connections.

  5. Click Sybase
  6. Click the Configure button
  7. Enter the field data.

  8. Click the Test Connection button.
    When the connection is successful a message is displayed.

    If the connection is unsuccessful review the connection fields and the troubleshooting section of this article.
  9. Now the search can be executed from the client or the connection string can be added to the scheduled task policy to be executed via the console. To copy the connection string highlight the entire string and copy.

How to Troubleshoot

If the Test Connection action fails, the current log provides information that is useful for troubleshooting.  

The logs for interactive searches are located at "C:\Users\<YourProfileName>\AppData\Local\Identity Finder\logs," or more easily from the client user interface using the following steps:

  1. Launch the Spirion Client for Windows.
  2. Click the Configuration tab
  3. Click the smaller arrow below Logging
  4. Select View Current Log

     

The following is a list of common log messages and their resolutions:

  • Error: Unable to open database (libsybct.dll: The specified module could not be found.  libct.dll: The specified module could not be found. DBMS API Library loading fails This library is a part of DBMS client installation, not SQLAPI++ Make sure DBMS client is installed and this required library is available for dynamic loading):
  • Resolution: Ensure the SDK for Adaptive Server Enterprise has been installed and the location to libsybct.dll is added to the PATH system variable on the client.
  • Error: Unable to open database (cs_ctx_alloc -> CS_MEM_ERROR)
  • Resolution: Ensure the SDK for Adaptive Server Enterprise has been installed and the location to libsybct.dll is added to the PATH system variable on the client. 
  • Error: Unable to open database (Login failed.)
    Resolution: validate and supply correct username and password

Additional References

Was this article helpful?

Powered by Product Fruits