How to Add exception to 1433 SQL Port through Windows Firewall in Windows 10?

Adding exception to 1433 SQL Port through Windows Firewall in Windows 10 is no different than that in Windows 8, 8.1 and 7. However, their is a change in the procedure of adding exception in Windows Firewall from the previous version of Windows like Windows XP, etc.

The following are the few simple steps which will guide you through the process of adding exception through the Windows Firewall:

1) Open the Control Panel.

2) Select Windows Firewall from option in the Control Panel.

3)Then Select the Advance Settings option from inside the Windows Firewall.

4) The exception can be provided on the Inbound and Outbound access of the Port depending upon the usage.

5) In this case, we Select the Inbound Rule so that we can provide the exception to access the 1433 port of any system which we are trying to access.

6) To create a New Rule for the 1433 port, Select the New Rule option from the Right Menu Pane.

7) A box as shown below will open, now Select the Port and Click Next.

8) Check mark on the TCP Option and Specify Local Ports as 1433 and then Click Next.

9) Check mark on the Allow the Connection radio button and then Click Next.

10) The three option as shown in the below screen are default selected. Let it remain as it is and then Click on Next.

11) Now, the last and final step is to name your Rule which is made to provide exception in the Windows Firewall for the 1433 SQL  Server Port and then Press Finish.

Congratulations! Your Windows Firewall exception now has been successfully added to your rules. Kindly drop a comment below to ask anything related to the topic or off the topic. Thanks for Reading!

You can only able to Telnet the Port 1433 only if the Telnet Client Windows Features in Enabled. Read the Article to know : How to Enable Telnet in Windows (with Pictures)


Regards,

Syed Aley Mehdi

How to fix the Error: "Warning: you must recover this database prior to access."

Mainly cause of this Warning “Warning: you must recover this database prior to access.” is the corruption of transaction log file for the database. For recovery of this database you need to follow these steps :

1) Open ‘SSMS’ with ‘SA’ or ‘Super’ credentials.

2) Go to ‘Databases‘ and select your respective  suspected database.

3) Right click on that database and select ‘New Query’.

4) Run the following commands sequentially one by one.

• EXEC sp_resetstatus [Database name]
• ALTER DATABASE [Database name] SET EMERGENCY
• DBCC checkdb([Database name])
• ALTER DATABASE [Database name] SET SINGLE_USER WITH ROLLBACK IMMEDIATE.
• DBCC CheckDB ([Database name],REPAIR_ALLOW_DATA_LOSS)
• ALTER DATABASE [Database name] SET MULTI_USER

5) After successful execution of all commands your database is recovered and ready for use.


Enjoyed the topic, Please do subscribe to our newsletter to get updated with every post without a miss.

Thanks for reading,

Shubin Dongre

Error: You are not authorized to sign in. Verify that you are using valid credentials and that you have been setup as a user in Microsoft Dynamics Navision.

In Navision 2013 R2, we are using Role Tailored Client (RTC) for client usage different from previous versions.

The reason for the error,   “You are not authorized to sign in. Verify that you are using valid credentials and that you have been setup as a user in Microsoft Dynamics NAV” is the unavailability of windows login in our NAV database.
Run these following commands to resolve the issue:

1. Open ‘SSMS’ with ‘SA’ or ‘Super’ credentials.

2. Go to ‘Databases‘ and select your respective database.

3. Right click on that database and select ‘New Query’.

4. Run these following commands

USE [Database Name]
GO
delete from [dbo].[User]
delete from [dbo].[Access Control]
delete from [dbo].[User Property]
delete from [dbo].[Page Data Personalization]
delete from [dbo].[User Default Style Sheet]
delete from [dbo].[User Metadata]
delete from [dbo].[User Personalization]

5. Open ‘Microsoft Dynamics NAV Server Administration Tool‘.

6. In Navision service credential select start as ‘Network Service’.

7. Restart Instance for updation of changes.

8. Restart ‘Microsoft Dynamics NAV Role Tailored Client‘.

9. Then create your ‘System ID’ in RTC for future use.


Enjoyed the topic, Please do subscribe to our newsletter to get updated with every post without a miss.

Thanks for reading

Shubin Dongre