Skip to main content

Connection Issues

Troubleshooting guide for connection problems with Sigmafine and SigmafineHub.

Cannot Connect to Sigmafine Server​

Symptoms​

  • Error message: "Unable to connect to Sigmafine Server"
  • Client application fails to connect
  • Timeout errors when attempting connection

Common Causes and Solutions​

1. Server Not Running​

Check Server Status:

Get-Service -Name "Sigmafine*"

Start the Service:

Start-Service -Name "SigmafineServer"

2. Firewall Blocking Connection​

Required Ports:

  • Sigmafine Server: Port 5457 (default)
  • SQL Server: Port 1433 (default)
  • IIS/Web Server: Ports 80, 443

Windows Firewall Rule:

New-NetFirewallRule -DisplayName "Sigmafine Server" -Direction Inbound -Protocol TCP -LocalPort 5457 -Action Allow

3. Incorrect Server Address​

Verify Configuration:

  • Check client configuration file: SigmafineClient.exe.config
  • Confirm server hostname or IP address
  • Test network connectivity: Test-NetConnection -ComputerName <servername> -Port 5457

4. Network Issues​

Test Connectivity:

# Ping the server
ping servername

# Test port connectivity
Test-NetConnection -ComputerName servername -Port 5457

Database Connection Failures​

Symptoms​

  • "Cannot connect to database" errors
  • Login failures
  • Timeout errors during database operations

Solutions​

1. Verify SQL Server Service​

Get-Service -Name "MSSQL*"
Start-Service -Name "MSSQLSERVER"

2. Check Connection String​

Location: Web.config or SigmafineServer.exe.config

Example:

<connectionStrings>
  <add name="SigmafineDB" 
       connectionString="Server=localhost;Database=Sigmafine;Integrated Security=true;" 
       providerName="System.Data.SqlClient" />
</connectionStrings>

3. Verify Database Permissions​

Required Permissions:

  • db_datareader
  • db_datawriter
  • Execute permissions on stored procedures

Grant Permissions (SQL):

USE Sigmafine;
ALTER ROLE db_datareader ADD MEMBER [DOMAIN\SigmafineUser];
ALTER ROLE db_datawriter ADD MEMBER [DOMAIN\SigmafineUser];

4. Enable TCP/IP Protocol​

  1. Open SQL Server Configuration Manager
  2. Navigate to SQL Server Network Configuration
  3. Enable TCP/IP protocol
  4. Restart SQL Server service

PI System Connection Issues​

Symptoms​

  • Cannot connect to PI Data Archive
  • "PI Server not found" errors
  • Tag lookup failures

Solutions​

1. Verify PI SDK Installation​

  • Ensure PI SDK is installed on Sigmafine server
  • Version should match PI Server compatibility requirements
  • Check: C:\\Program Files\\PIPC\\

2. Check PI Connection Settings​

Test PI Connection:

# Using PI SDK
piconfig
# Type: @node <servername>
# Should show connection details

3. Verify PI Trust Configuration​

On PI Server:

  • Open PI System Management Tools (PI SMT)
  • Check Connections > Trusts
  • Ensure Sigmafine server is in trust list

4. Network Security and Ports​

PI Server Ports:

  • PI Data Archive: Port 5450
  • PI AF Server: Port 5457, 5459

Test Connection:

Test-NetConnection -ComputerName piserver -Port 5450

Web Application Connection Issues​

Symptoms​

  • SigmafineHub website not loading
  • "500 Internal Server Error"
  • Authentication failures

Solutions​

1. Check IIS Service​

# Check IIS service
Get-Service -Name "W3SVC"

# Start IIS
Start-Service -Name "W3SVC"

2. Verify Application Pool​

Check Application Pool Status:

  1. Open IIS Manager
  2. Navigate to Application Pools
  3. Ensure SigmafineHub pool is started
  4. Check Identity has proper permissions

3. Review Web.config​

Common Issues:

  • Incorrect connection strings
  • Missing authentication settings
  • Invalid module configurations

4. Check Event Logs​

# Application log
Get-EventLog -LogName Application -Source "ASP.NET*" -Newest 20

# System log
Get-EventLog -LogName System -Source "Service Control Manager" -Newest 20

VPN and Remote Access Issues​

Solutions​

  1. Verify VPN Connection

    • Confirm VPN is connected and stable
    • Check assigned IP address is on correct subnet

  2. DNS Resolution

    • Ensure internal DNS names resolve correctly
    • May need to use IP addresses instead of hostnames

  3. Split Tunneling

    • Verify traffic to Sigmafine server routes through VPN
    • Check routing table: route print

Additional Resources​

Still Having Issues?​

Contact Sigmafine Support:

Last updated on