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
I've been having a complete nightmare trying to resolve certain error message in the event view after configuring and starting the NAS server. Upon starting the service and refreshing the service status changes to STARTED, however in the even view I keep getting the error messages below. Please could someone help me? (thank you).
The NAV database is in SQL and the application appears to be running fine.
Event Type: WarningEvent Source: SERVERNAMEEvent Category: NoneEvent ID: 20010Date: 7/14/2009Time: 8:06:06 AMUser: N/AComputer: CRM-SRV-01Description:The description for Event ID ( 20010 ) in Source ( SERVERNAME ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: The program failed to publish Microsoft Dynamics NAV Database Server Service Connection Point in Active Directory.
In order for Microsoft Dynamics NAV Database Server to publish a Service Connection Point, the Active Directory Schema on the network domain.
MS NAV version 5.0Windows Server 2003Microsoft SQL 2008
The event is just stating that the Database Service cannot be published to AD. This does not effect in anyway the operation of the NAV server service or the NAV client, the service does not need to be published. You can ignore the message. Just to restate; this is a warning message only and does not affect the operation of NAV in anyway and can be safely ignored.
Just for your information the following is from w1w1ism.pdf, about publishing NAV server in AD:"Before you can publish a Navision Database Server in the network, you must add a definition of a Navision service connection point to the Active Directory. Navision Database Server uses this service connection point to publish itself in the network and the clients use this information to locate the server and to find out how to connect to it. Only servers that have been installed as a service can be published in the network. To add a definition of a Navision Database Server to the Active Directory, you must add a Schema Extension to Active Directory. This must only be done once for each forest of domains and domain trees, regardless of how many Navision Database Servers are in that forest. When you install Navision Database Server, a file called schemaXt.exe is copied into the folder that contains Navision Database Server. Run this file to add a definition of a Navision service connection point to the Active Directory. Starting up a Navision Database Server (running as a service) will publish a service connection point using the definition that has been added to Active Directory."
Business Applications communities