Changing TCP/IP port used by WebStatistica

Changing TCP/IP port used by WebStatistica

book

Article ID: KB0082163

calendar_today

Updated On:

Products Versions
Spotfire Statistica 10 and later versions

Description

WebStatistica service is inaccessible, users are getting a blank page output [with a gray band at the top] when trying to access WebStatistica login page, for older versions of Statistica ( prior versions to 13.0 ). 13.1 may spin on the login page and then throw the error 
"Your credentials failed to authenticate"  although the user has all the necessary permissions to login to Webstatistica.  Newer versions of Statistica will have a 404:Not found error on the webpage.

Other symptoms of Port-conflict include : 
1. Webstatistica service is stopped on the server.
2. Event Viewer on the Application server has the error : Failed to start Socket Server
   User-added image

Cause: The port that Webstatistica is configured to use (8081) is used by another program (often McAfee uses the same port)


 

Issue/Introduction

Changing TCP/IP port used by WebSTATISTICA

Resolution

The TCP/IP port that Webstatistica uses must be configured to use another port that is available.

1. Remote into the Webstatistica Server and select Start >> All Programs >> Statistica  >>WebStatistica >> Administration. On newer versions of Windows (10 and later versions) Type "administration" in the search bar

2. Expand Settings >> Connection and change the TCP/IP port number as shown below:

    User-added image

3. Click on Apply and OK

4. Browse to [Drive]\ WebSTATISTICAPub\wwwroot\config.php. Open the file with notepad or another text editor (launch application as administrator) of your choice and modify $PostVars["SoapPort"] to a port that is not used,like 8082. 
  
   User-added image

5. Start the WebStatistica service from Control Panel >> Administrative Tools >> Services. 


    User-added image
 

Additional Information


Notes: 
This modification affects two layers. This means that now Webstatistica service listens on port 8082; browser-based clients will not be affected as the PHP layer was updated to point to this port; other clients [if any] that talk directly to the service will have to be pointed to 8082.