Safetica Server - Complete Setup & Troubleshooting Guide

🚀 Safetica Server Setup & Installation

Complete guide to download, install, and configure Safetica Management Server

📥 Official Download Links

🛡️ Safetica Server

Main installation package (~1GB)

Download Server

👥 Partner Version

Enhanced features for partners

Partner Portal

💻 Agent Only

Client installation package (MSI)

Download Agent

📚 Documentation

Installation guides and manuals

Support Portal

🎯 Automatic Installation (Recommended)

Download safetica_setup.exe from official link above
Run as Administrator and select your preferred language
Choose "Automatic Installation" for new deployments
SQL Express Installation: Will be configured automatically if not present
Service Account: "Safetica" user created with SYSADMIN permissions
Default Password: S@fetic@2004
Instance Name: SERVERNAME\SAFETICA
Complete Installation and access console via web browser

🔧 Manual Installation (Existing SQL Server)

Download safetica_setup.exe
Run installer and choose "Manual Installation"
Select Components: Choose "Safetica Server" for both console and server
SQL Configuration: Enter existing SQL server details
Database Connection: Specify IP/server name and credentials
Multiple Instances: Use format servername\INSTANCE
Account Permissions: Ensure SYSADMIN or minimum DB_CREATOR + VIEW SERVER STATE
Complete Setup and test connectivity

✅ Post-Installation Verification:

Access Management Console via web browser
Verify SMS service is running in services.msc
Check Activity Monitor for connection status
Test client deployment to sample endpoints

⚙️ Prerequisites & System Requirements

Essential components and system requirements for successful installation

📦 .NET Framework 4.8.1 - Critical Requirement

Safetica requires the latest .NET Framework 4.8.1 for optimal performance and security.

🌐 Runtime (Web Installer)

Downloads files during installation. Internet required.

Download Runtime

💾 Offline Installer

Complete package for systems without internet access.

Download Offline

👨‍💻 Developer Pack

For development environments and Visual Studio integration.

Download Dev Pack

🎯 System Requirements:

OS: Windows Server 2016+ or Windows 10+ (64-bit)
RAM: Minimum 4GB, Recommended 8GB+ for production
Storage: 2GB free space for installation, 10GB+ for database
CPU: Multi-core processor recommended for 250+ endpoints
Network: TCP ports 4438 (default), 1433 (SQL), 80/443 (web console)
Permissions: Administrator rights for installation and service accounts

🗄️ SQL Server Requirements:

Supported Versions: SQL Server 2012+ (Recommended: 2016+ with latest service packs)
Express Edition: Suitable for up to 250 endpoints (10GB database limit)
Standard/Enterprise: Required for larger deployments (500+ endpoints)
Permissions: SYSADMIN preferred, minimum DB_CREATOR + VIEW SERVER STATE
Network: TCP/IP and Named Pipes protocols must be enabled
Browser Service: SQL Browser service must be running for remote connections

🔧 Pre-Installation Checklist:

✅ Windows Updates installed and system restarted
✅ .NET Framework 4.8.1 installed and verified
✅ SQL Server installed and accessible
✅ Firewall configured for required ports
✅ Antivirus exceptions added for Safetica folders
✅ Administrator account available for installation
✅ Network connectivity verified between SMS and SQL servers

📊 Activity Monitor - Essential Diagnostic Tool

Monitor SMS performance, diagnose issues, and understand system status

Launch Activity Monitor:
Path: C:\Program Files\Safetica Management Service\Tools\STActivityMonitor.exe
Access: Any Management Console admin account
Purpose: Real-time SMS status monitoring and performance analysis

📈 Top Section - SMS Status Overview ▼

Key Metrics to Monitor:

Server Runtime: Shows SMS uptime without service restarts
Long runtime = stable service, frequent restarts = investigate issues
Total/Opened/Waiting Connections: External connector status
Includes Safetica Clients (2 connections each) and Management Console
Request Queue: External component requests (settings updates, etc.)
Format: Current/Processed requests; A=average time, L=last time
Saving Queue: Logs waiting for database save operation
High numbers = database performance issues or disk space problems
Categorization Queue: Website/application validation requests
Validated against local database and external categorization server

⚠️ Warning Signs:
• Saving queue constantly high (>1000)
• Request processing times increasing
• Frequent connection drops
• Short server runtime periods

🔌 Bottom Section - Connection Details ▼

Connection Information Analysis:

Type: Connection source identification
Agent = Safetica Client, Console = Management interface
Computer: Source computer hostname
Helps identify which endpoints are connected
IP Address: Network address of connecting system
Useful for network troubleshooting and security audits
Runtime: Connection duration since establishment
Long runtimes = stable connections, short = connectivity issues
Last Read: Timestamp of most recent data exchange
Recent timestamps = active communication
Download/Upload: Data traffic volume since connection start
High volumes may indicate data synchronization or log transmission

⚙️ Server Configuration Tool ▼

🚨 CAUTION: Advanced tool that directly modifies registry entries. Always consult Safetica Support before making major changes. Service restart required for changes to take effect.

Access Path:

Activity Monitor → Toolbar → Options → Server Configuration

Common Configuration Entries:

ClientServicePort: Change default SMS communication port (default: 4438)
Useful for client redirection during maintenance
DefinitionAutoUpdate: Enable/disable automatic definition updates
Control update behavior in restricted environments
IntegrationLevel: Set integration level without console
1000 = compatible mode for troubleshooting
MinimumUpdateFreeSpaceMB: Required free space for SMS updates
Adjust based on server storage capacity

Emergency Port Change Commands:

# Redirect clients to alternative port
STAservice.exe -clientport 44382

# Restore to default port
STAservice.exe -clientport 4438

# Apply changes
net stop "Safetica Management Service"
net start "Safetica Management Service"

🔧 Installation Troubleshooting

Resolve common installation problems, SQL configuration issues, and setup failures

❌ Installation Fails - Missing Prerequisites ▼

Symptoms:

.NET version check errors (installer performing background checks)
Installation folder not empty errors
Missing prerequisites warnings
Installer exits unexpectedly without error message

Root Causes:

Missing or outdated .NET Framework 4.8.1
Windows not fully updated
Previous installation remnants in directory
Insufficient user permissions
Antivirus blocking installation files

Complete Resolution Steps:

Update System:
- Install all Windows Updates
- Restart system after updates
Install .NET Framework 4.8.1:
- Download from Microsoft: Official .NET 4.8.1
- Use offline installer for systems without internet
- Restart system after installation
Clean Previous Installation:
# Check and clean installation folder dir "C:\Program Files\Safetica Management Service" # If files exist, delete the folder contents rmdir /s "C:\Program Files\Safetica Management Service" # Clean registry entries regedit # Navigate to: HKEY_LOCAL_MACHINE\SOFTWARE\Safetica Technologies\Safetica Management Service # Delete the entire key if present
Run Installation:
- Right-click safetica_setup.exe → "Run as Administrator"
- Temporarily disable antivirus real-time protection
- Choose appropriate installation type

Prevention for Future Installations:
• Add antivirus exceptions for Safetica folders
• Add regular system updates
• Keep .NET Framework current

🗄️ SQL Server Account Configuration ▼

Automatic Setup Requirements:

SQL Server located on same machine as SMS
Current user has Windows authentication to SQL
User can create/modify SQL Server accounts
User has sufficient administrative permissions

When Manual Setup Required:

SQL Server on separate/remote machine
Insufficient Windows authentication permissions
Corporate security policies restrict account creation
Using existing SQL Server instance with restrictions

Manual SQL Account Creation:

Create SQL Server Login:
-- Connect to SQL Server Management Studio -- Navigate to Security > Logins > New Login -- SQL Authentication setup: CREATE LOGIN safetica WITH PASSWORD = 'YourStrongPassword123!'; -- Windows Authentication (if domain environment): CREATE LOGIN [DOMAIN\SafeticaService] FROM WINDOWS;
Assign Required Permissions:
-- Best Practice (SYSADMIN): ALTER SERVER ROLE sysadmin ADD MEMBER safetica; -- Minimum Required (Production): ALTER SERVER ROLE dbcreator ADD MEMBER safetica; GRANT VIEW SERVER STATE TO safetica; -- Emergency Minimum (Not Recommended): -- Create database first, then assign db_owner
Configure SMS Database Connection:
- Same Server: localhost or .
- Named Instance: servername\INSTANCENAME
- Remote Server: 192.168.1.100 or sqlserver.domain.com
- Custom Port: servername,1433

Database Name Prefix Options:
• Default: safetica (creates safetica_data, safetica_log)
• Custom: company_safetica (for multiple instances)
• Clean Install: Change prefix to create fresh database

🌐 Network Connection Issues ▼

Common Network Problems:

Cannot connect to remote SQL Server during installation
"Network path not found" errors
"Login failed for user" messages
Timeout errors during database connection test

Network Configuration Checklist:

1. SQL Server Browser Service:

Open SQL Server Configuration Manager
Navigate to SQL Server Services
Ensure "SQL Server Browser" is running
Set startup type to "Automatic"

2. Network Protocols:

SQL Server Configuration Manager → SQL Server Network Configuration
Select "Protocols for [INSTANCENAME]"
Enable "Named Pipes" protocol
Enable "TCP/IP" protocol
Check TCP/IP properties for port configuration

3. Firewall Configuration:

# Windows Firewall rules for SQL Server
# Default SQL port
netsh advfirewall firewall add rule name="SQL Server" dir=in action=allow protocol=TCP localport=1433

# SQL Browser service
netsh advfirewall firewall add rule name="SQL Browser" dir=in action=allow protocol=UDP localport=1434

# Verify current SQL port configuration
netstat -an | findstr :1433

4. Connection Testing:

# Test SQL connectivity from SMS server
telnet sqlserver 1433
Test-NetConnection sqlserver -Port 1433

Dynamic Ports: If TCP Dynamic Ports = 0, it means dynamic ports are enabled. If there are other settings stated, it has to be taken into consideration when setting Database Connection in Safetica Management Console - Profile.

⚠️ General Troubleshooting

Common operational problems and performance issues

💾 Insufficient Disk Space - Critical Issue ▼

Symptoms:

New logs stop appearing in Management Console
Console loads extremely slowly or times out
Error in service_lastrun.txt: "Could not allocate space for object"
Database error mentioning filegroup is full
SQL Express 10GB limitation reached

Root Causes:

SQL Express database reached 10GB limit
Insufficient disk space on database server
Archiving tasks not configured properly
Log retention policies too aggressive
Large file operations generating excessive logs

Immediate Resolution Steps:

Emergency Client Redirection:
# Navigate to SMS installation folder cd "C:\Program Files\Safetica Management Service" # Redirect clients to alternative port STAservice.exe -clientport 44382 # Restart SMS service net stop "Safetica Management Service" net start "Safetica Management Service"
Database Maintenance:
- Open SQL Server Management Studio
- Right-click database → Tasks → Shrink → Database
- Wait for shrink operation to complete
Archive and Clean Data:
- Option A: Schedule archive and delete task in console
- Option B: Manual cleanup via SQL queries (contact Safetica Support)
- Target: Keep 6-9 months of recent data
Restore Normal Operations:
# Restore default client port STAservice.exe -clientport 4438 # Restart SMS service net stop "Safetica Management Service" net start "Safetica Management Service"

Best Practices for Prevention:
• SQL Express: Schedule quarterly archiving (9 months → 6 months)
• 250+ Endpoints: Upgrade to SQL Server Standard
• Monitor: Set up disk space alerts at 80% capacity
• Automate: Configure automatic archiving tasks

⏱️ Logs Not Appearing in Real-Time ▼

Performance Indicators:

Log processing takes excessive time (>5 minutes)
Management Console shows outdated information
Activity Monitor shows high queue numbers
Reports missing recent activity
Dashboard metrics appear delayed

Performance Bottlenecks:

Insufficient server memory (RAM)
High CPU utilization on SMS server
Database server performance issues
Network latency between SMS and SQL
Disk I/O bottlenecks on database storage
Too many concurrent client connections

Diagnostic and Resolution:

1. Performance Monitoring:

# Check SMS service resource usage
tasklist /fi "imagename eq STAservice.exe" /fo table /v

# Monitor system performance
perfmon.exe
# Add counters: Processor Time, Available Memory, Disk Queue Length

# SQL Server performance
# Open SQL Server Management Studio → Activity Monitor

2. Activity Monitor Analysis:

Check queue status (Saving, Request, Categorization)
Monitor connection count and stability
Review average processing times
Identify bottleneck queues

3. Hardware Optimization:

Memory: Increase RAM if consistently >80% usage
CPU: Consider multi-core upgrade for high load
Storage: Move database to SSD storage
Network: Ensure gigabit connectivity

4. Configuration Tuning:

# SQL Server optimization
# Increase memory allocation for SQL Server
# Configure maximum server memory in SQL properties

# SMS optimization via Activity Monitor
# Toolbar → Options → Server configuration
# Adjust processing threads if available

Recommended Hardware (Production):
• Small (1-250 endpoints): 4GB RAM, 2-core CPU
• Medium (250-500 endpoints): 8GB RAM, 4-core CPU
• Large (500+ endpoints): 16GB+ RAM, 8-core CPU, dedicated SQL server

🔄 Update Troubleshooting

Resolve failed updates, timeouts, and recovery procedures

🔄 STAService Did Not Stop in Time ▼

Symptoms:

The update seems to start normally, but after a while, you receive a general notification that it failed.
When updating from the update package, progress stops on checking the .NET version. Afterwards, the update fails. This is not due to missing .NET but due to the STAService process still running.
In services.msc, Safetica Management Service is in the stopping state, even after the notification about failed update is displayed.

Reason:

The most common reason for this is that saving/request/categorization queues were full and could not be processed in time (see the Activity Monitor chapter for reference). This might happen in older versions of Safetica, but should not happen in version 9.9.31 and newer. Another culprit might be a hanging transaction on the database which prohibits the SMS from stopping. This might be happening due to insufficient hardware either on the side of the database or SMS and is mainly present in large environments.

Fix:

Right after the SMS finally stops and restarts, run the update again. After restart, it should go through without any issue.
Temporarily redirect Safetica Clients
- Using the SMS:
  - Wait for the service to restart.
  - Change SMS port either via command line or Activity Monitor.
  - Restart SMS again and run the update.
  - After the update is fully finished, change the port back to default and restart SMS again.
- Using the firewall:
  - Just set up a blocking policy for incoming connections on port 4438.
Restart the update

The issues caused by full queues should not be present in version 9.9.28 and newer.

🔄 Update Failed and SMS Does Not Start ▼

Symptoms:

Update has failed with the standard error screen in Safetica Management Console.
After that, Safetica Management Console remains unusable without SMS connecting back.
Safetica Management Service folder does not contain all the files.

Issue Source:

This issue occurs most commonly when the installation/update process is terminated while it had not finished. Installation is usually terminated by another security software, which kills the process, and therefore, prohibits rollback to the original version.

Fix:

Repairing this situation is fairly easy but includes a complete reinstall of SMS. This will, however, leave the collected data intact, so there is no risk in doing so.
Navigate to C:\Program Files and rename the folder Safetica Management Service to anything else.
Download the installer of the same SMS version and run a manual installation of SMS (if you are not sure which version you are currently running, verify it in the registry entry: Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Safetica Technologies\Safetica Management Service).
Leave the pre-filled settings within the installer and run the installation.
(optional) From the original folder, copy files cert.pem and key.pem and paste them into the newly created folder for Safetica Management Service
Now you can log back in

Note: To mitigate this issue in the future, we recommend setting exceptions for Safetica Management Service folders in any 3rd party security software:

C:\Program Files\Safetica Management Service
C:\ProgramData\Safetica Management Service
C:\ProgramData\STEventService

🔄 Database Conversion is Not Able to Finish ▼

Symptoms:

The update does not finish even after a long time.
All services seem to be running normally.
After you restart Safetica Management Console, you will see a message that database conversion is running.
You can also see an error message about insufficient disk space or full filegroup in SQL logs or Service_lastrun.txt

Issue Source:

Database conversion is stuck in a loop and the query cannot be performed correctly. The most common reason for this behavior is insufficient space in the database, mainly with SQL Server Express which is limited to 10GB. In some cases, the database runs out of disk space due to a large transaction log.

Fix:

This issue does not have a simple solution and requires manual intervention on the database.

First, open SQL Management Studio and login into the database. Right-click on the database name "Reports - standard reports - Disk usage by top tables". Export the list and send it to Safetica support with a request for database cleanup querys.

Navigate to C:\Program Files\Safetica Management Service and rename STAService.exe to "aSTAservice.exe"

open CMD as administrator and run command "taskkill /f /im staservice.exe"

Open SQL Management Studio and log in

Right-click on the database - shrink - database and wait for it to finish

Now you will have to decide how old data you want to keep/delete. Modify the query you received from Safetica support. You will need to change the dates at the end of the lines. The format is YYYYMMDDHHMMSS so if you want to keep 6 months of data the data should be 20201101000000. At this moment this concerns only file operation logs

Run the query (right-click on the database)

After the query finishes, you should see the number of affected rows

Shrink the database again (optional)

Now you will have to rebuild columnstore index. When you click on the + then tables and find table file_operation_log. Click on + and indexes. The first index should include columnstore in the name. Right-click on it and select rebuild.

After it finishes shrink the database again which should release enough of the space for the update.

Rename "aSTAservice.exe" back to the "STAservice.exe" and run restart.bat in the same location

Wait for the update to finish.

🗄️ Database Issues & Maintenance

Connection problems, full databases, and advanced maintenance procedures

🚫 Cannot Connect to Management Console ▼

Connection Failure Symptoms:

Web browser shows "Connection refused" or timeout
SMS service repeatedly restarts in services.msc
Debuglog.txt shows "middleware initialization" failure
Service_lastrun.txt contains database connection errors

Database Connection Issues:

SQL Server service stopped or crashed
Network connectivity lost between SMS and SQL
Database credentials changed or expired
Database in single-user or restricted mode
Firewall blocking database connections

Systematic Troubleshooting:

1. Verify SQL Server Status:

# Check SQL Server service
services.msc
# Look for "SQL Server (INSTANCENAME)" - should be "Running"

# Command line verification
sc query MSSQLSERVER
sc query "MSSQL$SAFETICA"

# Test SQL connectivity
sqlcmd -S servername\instancename -E
# Or with SQL authentication:
sqlcmd -S servername\instancename -U username -P password

2. Review SMS Logs:

Debug Log: C:\ProgramData\Safetica Management Service\debuglog.txt
Service Log: C:\ProgramData\Safetica Management Service\logs\service_lastrun.txt
Look for specific error messages about database connections

3. Database Status Verification:

-- Connect via SQL Management Studio
-- Check database status
SELECT name, state_desc, user_access_desc 
FROM sys.databases 
WHERE name LIKE 'safetica%';

-- Verify filegroup status
SELECT name, state_desc 
FROM sys.filegroups 
WHERE data_space_id IN (
    SELECT data_space_id FROM sys.database_files
);

4. Network Connectivity Test:

# Test network connection to SQL server
telnet sqlservername 1433

# Test DNS resolution
nslookup sqlservername

# Ping test
ping sqlservername

# Port connectivity check
Test-NetConnection sqlservername -Port 1433

⚡ Database Performance Issues ▼

Performance Indicators:

Service_lastrun.txt shows "Busy (SavingQueue.cpp [58])" errors
Activity Monitor displays high queue numbers
Console login takes excessive time
Reports generation times out
Real-time monitoring lags significantly

Performance Bottlenecks:

Database server overwhelmed with requests
Insufficient memory allocation to SQL Server
High disk I/O on database storage
Missing or fragmented database indexes
Transaction log growth issues
Concurrent user load exceeding capacity

Performance Optimization:

1. SQL Server Performance Monitoring:

-- Check current connections and processes
SELECT 
    session_id, 
    status, 
    command, 
    cpu_time, 
    memory_usage,
    reads, 
    writes,
    logical_reads
FROM sys.dm_exec_requests
WHERE session_id > 50;

-- Monitor wait statistics
SELECT TOP 10 
    wait_type, 
    wait_time_ms, 
    percentage = wait_time_ms * 100.0 / SUM(wait_time_ms) OVER()
FROM sys.dm_os_wait_stats 
WHERE wait_time_ms > 0
ORDER BY wait_time_ms DESC;

2. Database Maintenance:

-- Update database statistics
UPDATE STATISTICS safetica_data;

-- Rebuild fragmented indexes
ALTER INDEX ALL ON safetica_data.dbo.file_operation_log REBUILD;

-- Check database integrity
DBCC CHECKDB('safetica_data') WITH NO_INFOMSGS;

3. SQL Server Configuration:

Memory: Set max server memory to 75% of total RAM
Recovery Model: Set to SIMPLE for better performance
Auto-Growth: Configure reasonable auto-growth settings
Tempdb: Place on separate fast storage if possible

Version 9.9.25+ Improvement: Console requests prioritized during high load. Login should work even when database is busy, but root cause still needs addressing.

🔒 Database is in Read-Only Mode ▼

Symptoms:

Cannot connect to console
New logs are not saved
In service_lastrun.txt you will find an error that includes string read-only (you can search for it within the log)

Issue Source:

In some cases, when SQL server was terminated unexpectedly, after a failed update or in some specific situations within the SQL server, it might happen that some of the filegroups will be switched to single-user or read-only state. In such a situation, the service will not work correctly and you might encounter an issue when connecting to the Safetica Management Console.

Fix:

ALTER DATABASE safetica_data SET SINGLE_USER WITH ROLLBACK IMMEDIATE;
ALTER DATABASE safetica_data MODIFY FILEGROUP safetica_data_fg READWRITE;
ALTER DATABASE safetica_data SET MULTI_USER
                            

Note: if you have Safetica database installed with a different prefix you will need to adjust the query accordingly.

💥 Database is Full ▼

Symptoms:

The most common issue for the failing initialization of SQL is the lack of database space. This happens most commonly due to the fact that the Express version of the SQL server has a limitation of 10GB per database. When the service is running for an extended period of time without regular maintenance, this limit gets exhausted and database function is hindered. To verify this situation you can check SQL logs via SQL management studio. In here you will see information about exceeding the allocated space.

In the case of the SQL Standard version, which does not have the pre-defined limitation for database size, it is dependent on the available disk space. This space can be filled up by the database itself, or by transaction log, which stores information about the active transactions.

Issue Source:

If the customer reports a full database there are several options based on how did the database fill up. Try to understand what had happened and ask the customer for additional info on what precluded the issue. Then based on that you can follow one of the steps further

The database is filled up with logs, during normal usage
- That means that they have automatic backup and overwrite enabled which prevents the database from stopping
- They are able to get into the console
- Normal archivation tasks should work just fine, it is sufficient to create backup and delete task to clean up space
Database filled up during update and the update failed (console is available)
- in some rare cases when the update fails it is still possible to access the console
- in such cases run archivation tasks
Database filled up during update - update is ongoing (console is unavailable)
- most of the cases are connected to an update during which the SMS is updated correctly but the conversion scripts that should run during the update do not have sufficient space in DB and get stuck
- Check the DB error log via SQL management studio, you should be able to see a log about exceeding the allocated database size
- In such a case, you will need to perform manual DB cleanup. This is targeted mainly on the file_operation_log as it is usually the largest and most frequently modified. Therefore if new columns are added to a large number of rows it requires a sufficient amount of disk space.

Fix:

Besides the insufficient space in the database, another possible issue is insufficient disk space for the transaction log. This log stores information about active transactions and their modification in case of any failure. In such a case, data stored in the log is used for reverting the transactions to the original state.

Due to this logic, transactions that modify large amounts of data need to log their activity. This increases the size of the log, and in the case of large databases or smaller disks, it might take all of the free disk space.

There are some general recommendations on what to do to minimize the size of the log and avoid potential issues.

Keep the database size in a reasonable size. We recommend keeping 6 months of data in the database and older data in backup archives. This ensures that the database size remains at reasonable levels and improves performance during the updates and modifications.
Make sure that there is enough disk space. Take into consideration the warnings before the update if there is insufficient disk space on the database server
As an advanced measure, you can keep the transaction log on a separate disk, which you can increase/decrease in size depending on your needs
Keep the recovery model in database settings on Simple. This ensures that when the transaction finishes successfully transaction log is cleared and returned back to minimum size.

🗄️ SQL Installation Tips

Automatic and manual SQL setup guidance

The installation package of MS SQL 2017 Express is included in the Safetica installation package. However, SQL server can be independently or within the automatic installation of Safetica. It is also possible to connect Safetica to a database server that already has other databases running. In such a case, make sure that this server has enough hardware resources to run multiple instances/databases.

Supported Versions

For a direct installation, minimum of MS SQL 2012 and above, with MS SQL 2016 as a recommended SQL version
For migration or clean installation of the database server, we recommend using an updated server to the latest versions including service packs

Note: During the migration, you might encounter an error when moving to MS SQL 2016 without a service pack, as it does not support clustered column store indexes used in our design. That is why we recommend making sure that you are always running the latest build of the SQL server.

Automatic Installation

All configuration is done automatically
Service account Safetica is created automatically during the installation of SMS with sysadmin permissions
The default password for "safetica" account is S@fetic@2004
Safetica Management Service will have a pre-defined connection to the database via the above-mentioned account
The default instance name is SERVERNAME\SAFETICA

Manual Installation from Safetica Installer Package

Can be automatically started from Safetica installer during installation of Safetica Management Service via "New installation of SQL Server Express"

Installation from the Safetica package differs from an SQL installer downloaded from the official websites. These are the main differences:

During the installation, the install directory cannot be selected
"sa" account cannot be configured
you cannot specify services which you want to install
the only thing that can be changed is the instance name
in order to modify installation properties, the corresponding (or newer) version of the SQL server has to be downloaded from the official websites

Manual Installation from Other Sources

If there is already SQL server installed it is not necessary to install it again. You can create a separate instance on an already existing SQL server if it meets the recommended settings.

We recommend creating a separate instance for Safetica databases, however, an already existing instance can be used. In order to do so, you have to specify the connection details manually as can be seen in section SMS - Installation.

Potential Network Issues When Connecting to Already Installed SQL Server

When using an existing instance or SQL server was installed from another source, there are some pre-requisites that might not be set by default and need to be adjusted manually. In order to connect SMS to the database server you will need:

Running SQL Browser service, which is responsible for delegating the incoming connections. The current state of the SQL browser can be verified via the SQL server configuration manager
Another requirement is to have enabled Named Pipes and TCP/IP protocol for SQL. This can be adjusted in SQL Server Configuration Manager - SQL Server Network configuration - Protocols for "INSTANCENAME". In this view, you can verify the current settings, as well as the IP address of the server and port settings for the SQL. If the TCP Dynamic Ports is set to 0 it means that the dynamic ports are enabled. If there are other settings stated, it has to be taken into consideration when setting Database Connection in Safetica Management Console - Profile.

📥 Essential Downloads & Resources

Official software downloads, tools, and documentation links

🔗 Microsoft Downloads

🌐 .NET Framework 4.8.1

Web installer - requires internet connection

Web Installer

💾 .NET Framework 4.8.1

Offline installer - complete complete package

Offline Installer

🗄️ SQL Server 2022 Express

Free database server for small deployments

Download SQL Express

🛠️ SQL Management Studio

Essential database management tool

Download SSMS

🎯 Quick Reference - Essential File Locations:

# SMS Installation and Tools
C:\Program Files\Safetica Management Service\
C:\Program Files\Safetica Management Service\Tools\STActivityMonitor.exe

# Log Files (Critical for Troubleshooting)
C:\ProgramData\Safetica Management Service\debuglog.txt
C:\ProgramData\Safetica Management Service\logs\service_lastrun.txt

# Registry Configuration
HKEY_LOCAL_MACHINE\SOFTWARE\Safetica Technologies\Safetica Management Service

# Service Management
services.msc → "Safetica Management Service"

🚨 Emergency Command Reference:

# Client Redirection (Maintenance Mode)
STAservice.exe -clientport 44382
net restart "Safetica Management Service"

# Restore Normal Operations
STAservice.exe -clientport 4438
net restart "Safetica Management Service"

# Force Service Management
taskkill /f /im staservice.exe
net start "Safetica Management Service"

# SQL Server Service Check
sc query MSSQLSERVER
sc query "MSSQL$SAFETICA"

# Network Connectivity Tests
telnet sqlserver 1433
Test-NetConnection sqlserver -Port 1433

📞 Support Resources:

Safetica Support Portal: support.safetica.com
Database Cleanup Queries: Contact Safetica Support for environment-specific queries
Implementation Guides: Available on support portal for detailed setup instructions
System Requirements: Latest hardware recommendations at support.safetica.com
Best Practices: Architecture guides for enterprise deployments

🚨 Most Common Issues (Check These First!)

❌ Installation Fails

🗄️ Database Full (10GB Limit)

🔌 Cannot Connect to Console

⏱️ Logs Not Real-Time

🔄 Update Timeouts

🔧 SQL Connection Errors

🚀 Safetica Server Setup & Installation

📥 Official Download Links

🛡️ Safetica Server

👥 Partner Version

💻 Agent Only

📚 Documentation

🎯 Automatic Installation (Recommended)

🔧 Manual Installation (Existing SQL Server)

✅ Post-Installation Verification:

⚙️ Prerequisites & System Requirements

📦 .NET Framework 4.8.1 - Critical Requirement

🌐 Runtime (Web Installer)

💾 Offline Installer

👨‍💻 Developer Pack

🎯 System Requirements:

🗄️ SQL Server Requirements:

🔧 Pre-Installation Checklist:

📊 Activity Monitor - Essential Diagnostic Tool

Key Metrics to Monitor:

Connection Information Analysis:

Access Path:

Common Configuration Entries:

Emergency Port Change Commands:

🔧 Installation Troubleshooting

Symptoms:

Root Causes:

Complete Resolution Steps:

Automatic Setup Requirements:

When Manual Setup Required:

Manual SQL Account Creation:

Common Network Problems:

Network Configuration Checklist:

1. SQL Server Browser Service:

2. Network Protocols:

3. Firewall Configuration:

4. Connection Testing:

⚠️ General Troubleshooting

Symptoms:

Root Causes:

Immediate Resolution Steps:

Performance Indicators:

Performance Bottlenecks:

Diagnostic and Resolution:

1. Performance Monitoring:

2. Activity Monitor Analysis:

3. Hardware Optimization:

4. Configuration Tuning:

🔄 Update Troubleshooting

Symptoms:

Reason:

Fix:

Symptoms:

Issue Source:

Fix:

Symptoms:

Issue Source:

Fix:

🗄️ Database Issues & Maintenance

Connection Failure Symptoms:

Database Connection Issues:

Systematic Troubleshooting:

1. Verify SQL Server Status:

2. Review SMS Logs:

3. Database Status Verification:

4. Network Connectivity Test:

Performance Indicators:

Performance Bottlenecks:

Performance Optimization:

1. SQL Server Performance Monitoring:

2. Database Maintenance:

3. SQL Server Configuration:

Symptoms:

Issue Source: