How to configure server to listen TCP/IP port on Microsoft SQL Server?

In this article we will look how to configure or enable SQL Server database engine to listen to a particular port.

1. Open MS sql server configuration manager

Goto SQL server Network Configuration section >> Open protocol for SQLSERVER

You will see Protocol TCP/IP is showing in Disabled status. By default it is disabled.

SQL Server Configuration Manager

2. Enable the TCP IP port

Default it will be Disabled, we have to enable it to listen a server request.

a. Double click on the TCP/IP option, a new window will appear.

b. From Protocol tab Select the Enabled value as Yes.

Enable TCP/IP in SQL Server

3. Open the IP Address tab now. Here you will find few IP<n>, and you need to enable the right one and configure with write port.

Here, we will enable our localhost server request on port number 1433. 1433 is default port for MS sql server, which you may change as your wish. Configure the following values here.

Active = Yes

Enabled = Yes

IP Address = 127.0.0.0

TCP Dynamic Ports = <keep it empty>. Default you may find 0 here, please remove the value 0.

TCP Port = 1433

After making all these changes hit on apply button.

Configure TCP IP properties in MS SQL SERVER

4. If you not sure about the request server and your application is unable to listen to configured IPn, then please update the IPAll section at the end of this IPs with same port number 1433.

IPALL MS SQL Server Configuration TCP/IP

Note: These changes will not work until and unless we restart the SQL services. To restart the services. Again go to MS SQL server configuration manager.

Open SQL Server Configuration Manger >> click on SQL Server Service >> SQL Server (SERVER NAME) >> Right click on that and select the restart option.

References:

configure a server to listen on a specific tcp port

Hissa

Hum mehnatkash jagwaalon se jab apna hissa maangenge
Ek khet nahin, ek desh nahin, hum saari duniya maangenge

Yaan sagar sagar moti hain, yaan parbat parbat heere hain
Yeh saaraa maal hamaara hai, hum saara khazaana maangenge

Jo khoon baha, jo baag ujde, jo geet dilon mein qatl hue
Har qatre ka, har ghunche ka, har geet ka badla maangenge

Se seth byopaari rajwaade dus laakh to hum das laakh karod
Yeh kitne din America se jeene ka sahaara maangenge

Jab saf seedhi ho jaayegi, jab sab jhagde mit jaayenge
Ham har ik desh ke jhande par ik laal sitaara maangenge

-- Faiz Ahmed Faiz

Communal violence and commissions on riots in India

India experienced many communal violence is past and still it is happening, even we are in 21st century and billion of our civilians are literate.

Post independence government of India form few committees to inquiry some deadly and highly impacted riots. Below is the list of the few committees.

1961 Jabalpur riots, Justice Shiv Dayal Srivastava Committee
1967 Ranchi riots, Raghubir Dayal Commission
1969 Ahmedabad riots, Justice P Jaganmohan Reddy
1970 Maharashtra riots, D P Madan Commission of Inquiry
1979 Jamshedpur, Bihar, Jitendra Narain Commission of Inquiry
1980 Moradabad, Justice M P Saxena
1981 Biharsharif, Bihar, Balasubramanian Commission
1984 Delhi, Justice Jaggannath Misra Commission 1985 and Justice Nanavati Commission 1999
1989-90 Bhagalpur Communal Riots Inquiry Commission
1992-93 Bombay, Justice Srikrishna Commission
1998 Coimbatore, P R Gokulakrishna Commission of Inquiry
1999 Manoharpur, Orissa Wadhwa Commission probed burning of Graham Staines
2002 Ahmedabad, Justice Nanavati and Justice K G Shah
2011 Gopalgarh, Rajasthan Justice Sunil Kumar Garg Commission
2013 Muzaffarnagar, Justice Vishnu Sahai Commission

Million of riot victims are still waiting for justice from judiciary. These commissions are failed to find any solution to stop the violence in future. Recently, in year 2020 "Delhi Riot", Capital city of India, New Delhi gone by 5 days riots between Hindu and Muslim community which killed more than 50 people. This is the situation of capital city of India, law and order of Delhi police. Many eyewitness said new agencies that "Police joined the rioters and supporting rioters to raise the violence."

Reference:

Clear script cache in AEM

At some point you may face the issue where your AEM page is not getting loaded and following errors getting printed in error log file.

Errors:

*ERROR* [182.75.136.107 [1589236795135] GET /content/jorvee/tools/en_us/gen-tool-10-10.html HTTP/1.1] com.day.cq.wcm.core.impl.WCMDeveloperModeFilter Error during include of SlingRequestPathInfo: path='/content/jorvee/tools/en_us/gen-tool-10-10/jcr:content', selectorString='null', extension='html', suffix='null'org.apache.sling.api.SlingException: Cannot get DefaultSlingScript: java.io.IOException: java.util.concurrent.TimeoutException: Idle timeout expired: 60000/60000 ms

*ERROR* [0:0:0:0:0:0:0:1 [1531894023650] GET /content/we-retail/us/en/user/smartlist.html HTTP/1.1] com.day.cq.wcm.core.impl.WCMDeveloperModeFilter Error during include of SlingRequestPathInfo: path='/content/jorvee/tools/en_us/gen-tool-10-10/jcr:content', selectorString='null', extension='html', suffix='null'
org.apache.sling.api.SlingException: Cannot get DefaultSlingScript: Identifier com.adobe.cq.wcm.core.components.models.Page cannot be correctly instantiated by the Use API

Resolution:

To solve this issue we need to clear the cached HTML and JS files from AEM.

Solution 1:

Browse the "Adobe Experience Manager Web Console Script Cache Status" http://localhost:4502/system/console/scriptcache
at the bottom of the page there is a "Clear Cache" button, click on the button to clear all the above listed cached scripts. You may also clear one by one if you doesn't want to clear all of them. To remove the individual script click on the remove button next to that script in right.

Adobe Experience Manager Web Console Script Cache Status

Solution 2:

Restart your AEM environment.

rashid jorvee blog

Menu