Skip to main content

Removing Certain Workstation Registry Settings to Resolve "CANNOT CONNECT TO RFMS" Error

  • Updated

Windows Fileserver

On the WINDOWS FILESERVER, for success with RFMS, install MSSQLServer following the RFMS documented process. 

 

Pay special attention to Windows Defender Firewall settings and some others (see below)!

 

  1. Open Windows Defender Firewall Ports (Inbound only)
    1. TCP: 1433
    2. UDP: 1433,1434
  2. SQLServer Browser Service set to Automatic startup
  3. Mixed Mode Authentication
  4. SQL Server Configuration – Protocols – Activate “Named Pipes” & “TCP/IP” if not already
  5. Custom location for SQLData
  6. User ‘SA’ - Password (e.g. R*******!)

 

 

 Windows Workstation

On the WINDOWS WORKSTATION, avoid “additional” REGISTRY settings in ANY of the MSSQLSERVER groups (see Below). 

 

There are 3 (sometimes 4) REGISTRY Groups containing the MSSQLSERVER Key and 3 typical SubKeys (Client, SuperSocketNetLib,LastConnect)

 

  1. Computer\HKEY_CURRENT_USER\SOFTWARE\Classes\VirtualStore\MACHINE\SOFTWARE\WOW6432Node\Microsoft\MSSQLServer
  2. Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer
  3. Computer\HKEY_USERS\S-1-5-21-3751593094-2903760194-909210082-1103\SOFTWARE\Classes\VirtualStore\MACHINE\SOFTWARE\WOW6432Node\Microsoft\MSSQLServer  (*NOTE: Your key will vary slightly!)
  4. Computer\HKEY_USERS\S-1-5-21-3751593094-2903760194-909210082-1103_Classes\VirtualStore\MACHINE\SOFTWARE\WOW6432Node\Microsoft\MSSQLServer  (*NOTE: Your key will vary slightly!)

 

Empty Configuration

 

Here’s a look at an empty configuration.  If you have a problem, clear all settings in each of the below in EVERY Registry Group.  This WORKS every time to restore SQL access for the Workstation!!

 

\MSSQLServer

.\Client

..\SuperSocketNetLib

 …\LastConnect

 

Bad Configuration

 

Here’s a look at a potentially BAD configuration, with many additional settings.  This configuration has been known to FAIL.

 

Computer\HKEY_CURRENT_USER\SOFTWARE\Classes\VirtualStore\MACHINE\SOFTWARE\WOW6432Node\Microsoft

\MSSQLServer

.\Client

..\SuperSocketNetLib

 …\LastConnect –

KeyString: IMP9\SQLExpress (For Example)

StringData: 2078867445:np:\\IMP9\pipe\MSSQL$SQLEXPRESS\sql\query

 

 

Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft

\MSSQLServer

.\Client –

KeyDWORD: SharedMemoryOn

BinaryData: 0x00000000

 ..\ConnectTo

  ..\DBLib –

  KeyString: AutoAnsiToOem

  StringData: OFF

 

  KeyString: UseIntlSettings

  StringData: OFF

    ..\SuperSocketNetLib –

  KeyDWORD: Encrypt

  BinaryData: 0x00000000 (0)

 

  KeyString: ProtocolOrder

  MultiZData: (Empty/Blank)

     …\tcp –

  KeyDWORD: DefaultPort

  BinaryData: 0x00000599 (1433)

 

 

Computer\HKEY_USERS\S-1-5-21-3751593094-2903760194-909210082-1103\SOFTWARE\Classes\VirtualStore\MACHINE\SOFTWARE\WOW6432Node\Microsoft

\MSSQLServer

.\Client

..\SuperSocketNetLib

 …\LastConnect –

KeyString: IMP9\SQLExpress (For Example)

StringData: -2078867445:np:\\IMP9\pipe\MSSQL$SQLEXPRESS\sql\query

 

 

Computer\HKEY_USERS\S-1-5-21-3751593094-2903760194-909210082-1103_Classes\VirtualStore\MACHINE\SOFTWARE\WOW6432Node\Microsoft

\MSSQLServer

.\Client

..\SuperSocketNetLib

 …\LastConnect –

KeyString: IMP9\SQLExpress (For Example)

StringData: -2078867445:np:\\IMP9\pipe\MSSQL$SQLEXPRESS\sql\query

 

Also, see Resolving “SQL Server Login” issue when starting RFMS or QuickPay.

 

Powered by Zendesk