Error 2140 Interner Windows Nt
for Help Receive Real-Time Help Create a Freelance Project Hire for a Full Time Job Ways to Get Help Ask a Question Ask for Help Receive Real-Time Help Create a Freelance Project Hire for a Full Time Job Ways to Get Help Expand Search Submit Close Search Login Join Today Products BackProducts Gigs Live Careers Vendor Services Groups Website Testing Store Headlines Experts Exchange > Questions > error 2140 - internal windows Nt error Want to Advertise Here? Solved error 2140 - internal windows Nt error Posted on 1998-02-04 Windows Networking 1 Verified Solution 2 Comments 1,688 Views Last Modified: 2013-12-19 could you tell me why I get "Error 2140-internal Windows NT error" when i try to run the exchange directory synchronisation service, and how i go about resolving this error. The scenario is that i am trying to migrate exchange 4.0 folders on server A to exchange 5.0 on server B, both in the same domain. Server B is the new PDC. 0 Question by:faisalfarooq Facebook Twitter LinkedIn Google LVL 32 Best Solution byjhance Configuring to Avoid Error 2140 When Starting an Exchange Server You might receive the following error message when starting the Internet Mail Connector service on the computer configured with Microsoft Go to Solution 2 Comments Message Author Comment by:faisalfarooq1998-02-04 Adjusted points to 100 0 LVL 32 Overall: Level 32 Windows Networking 7 Message Accepted Solution by:jhance1998-02-04 Configuring to Avoid Error 2140 When Starting an Exchange Server You might receive the following error message when starting the Internet Mail Connector service on the computer configured with Microsoft Exchange Server: Stop "Could not start the Microsoft Exchange Internet Mail Connector service on ..." Error 2140: An internal Windows NT error occurred. If so, the following event will be logged in the event viewer: EventID 4058 Category: Initialization/Termination This error occurs when the TCP/IP protocol properties for DNS name resolution are not properly configured, for example when there is a blank entry for the DNS domain name. Û To configure a DNS domain name 1. Click the Start button, point to Settings, and then click Control Panel. 2. Double-click the Network icon, click the Protocols tab, in the Network Protocols list click TCP/IP Protocol, and then c
ManagementDevelopment ToolsSystem AdministrationApplication Building BlocksDownloadsDocumentationContinuous Software ManagementLicensingPlatform AvailabilityAddonSoftware ERPBASIS Transformer AMISalesSales Overviewb‑commerceHow to BuyPartnership ProgramSolutionsSolutions OverviewTraining/TutorialsDemo ShowcaseDownloadsProfessional ServicesSupportSupport OverviewFAQsKnowledge BaseDiscussion ForumsTech Support PolicyEventsEvents OverviewTrainingJava Break ArchivesTechCon2015About UsBASIS OverviewContact UsThe BASIS Advantage MagazineAnnouncementsPress ReleasesManagementLegalMaps and DirectionsLogosLiterature Support Overview FAQs Knowledge Base Discussion Forums Tech Support Policy The BASIS AdvantageCurrent IssuePrevious Issues You are hereHome KB#00720-Error 2140: An internal Windows NT error occured when starting the PRO/5 NT Data Server as a service Title: Error 2140: An internal Windows NT error occured https://www.experts-exchange.com/questions/10038036/error-2140-internal-windows-Nt-error.html when starting the PRO/5 NT Data Server as a service Description: When attempting to start the PRO/5 Data Server service, the following error may occur: Could not start the Pro5 Data Server service Error 2140: An internal Windows NT error occured Resolution: This error can occur for a few reasons: 1) This error may occur when attempting to start the http://www.basis.com/kb00720 data server and specifying a port that is already in use by another service. To remedy the error, change the port specified in Conrol Panel under the Pro5 server configuration. 2) This error may occur when attempting to start the data server when logged in as a user without proper permissions. To remedy the error, log in as the administrator (or another account with sufficient privileges) and then start the Data Server. 3) If there is anything wrong with the config.bbx file for the PRO/5 Data Server. To remedy the error, check the config.bbx file for the Data Server and recreate it if needed. Minimum requirements for this config file are: setopts byte 4, bit $20$ all invalid drives DSKSYN'd the FCBS, CIBS, and STBLEN parameters can be used (and probably should be) but are not required. Last Modified: 06/08/1999 Product: PRO/5 Data Server Operating System: Windows NTOS Error: 2140 BASIS structures five components of their technology into the BBx Generations.
Copyright BASIS International Ltd. All rights reserved. Provider of BBx® Generations. Contact us.NT 4.0 Novell NetWare 5.1 symptom Error: "Windows NT http://support.novell.com/docs/Tids/Solutions/10061486.html Error 2140: An internal Windows NT error occurred." Some services are not fully starting when the NT Serverreboots SERVER service hangs on reboot Event Viewer shows errors on services NDS service does not start automatically NET LOGIN service does not start automatically Browser service error 2140 starts automatically once in a while -322 - Buffer zero length System status waiting for a connection "Service is in a Stop Pending State" change Upgraded PDC and BDC from NDS for NT 2.0 to Account Management 2.1 after first server was upgraded to error 2140 interner NDS 85.12a from 7.51a cause Resolve the NDSSERVER service problem andother services will start fix Removed eDirectory from the NT server and rebooted. NT server accepted authentication and other products loaded without error. document Document Title: Error: "Windows NT Error 2140: An internal Windows NT error occurred." Document ID: 10061486 Solution ID: NOVL44304 Creation Date: 02Apr2001 Modified Date: 03Dec2002 Novell Product Class:Novell eDirectory disclaimer The Origin of this information may be internal or external to Novell. Novell makes all reasonable efforts to verify this information. However, the information provided in this document is for your information only. Novell makes no explicit or implied claims to the validity of this information. Any trademarks referenced in this document are the property of their respective owners. Consult your product manuals for complete trademark information.