Breaking news from around the world
Get the Bing + MSN extension
Now Available in Community - MBAS 2019 Presentation Videos
Catch the most popular sessions on demand and learn how Dynamics 365, Power BI, PowerApps, Microsoft Flow, and Excel are powering major transformations around the globe. | View Gallery
2019 release wave 2 Discover the latest updates to Dynamics 365Release overview guides and videos Release Plan | Early Access Availability
Ace your Dynamics 365 deployment with packaged services delivered by expert consultants. | Explore service offerings
Connect with the ISV success team on the latest roadmap, developer tool for AppSource certification, and ISV community engagements | ISV self-service portal
The FastTrack program is designed to help you accelerate your Dynamics 365 deployment with confidence.
FastTrack Program | Finance TechTalks | Customer Engagement TechTalks | Talent TechTalks | Upcoming TechTalks
Most of you must have faced this error and a lot of times it is resolved by restarting SQL agent services or by enabling named pipes in SQL Service Configuration Manager. But this time i discovered something new. For your information, i had my database and application on different servers. In order to resolve this i had to add port 1434 (UDP Protocol Type) in Windows Firewall Inbound Rules.
Open Windows Firewall Advanced Security, and from there navigate to Inbound Rules>>New Rule.
Navigate to Protocols and Ports, select UDP in Protocol Type and add port 1434,
That is it ! :)
Business Applications communities