An Error Occured While Testing The Nspi Interface
(עברית)المملكة العربية السعودية (العربية)ไทย (ไทย)대한민국 (한국어)中华人民共和国 (中文)台灣 (中文)日本 (日本語) HomeOnline20132010Other VersionsLibraryForumsGalleryEHLO Blog Ask a question Quick access Forums home Browse forums users FAQ Search related threads Remove From My Forums Answered by: Outlook Anywhere - An error occurred while testing the NSPI RPC endpoint Previous Versions of Exchange > Exchange Server 2010 Question 0 Sign in to vote Greetings Exchange community. Please bear with me as this is my first exchange migration. I'm hoping that someone can assist me with a problem that is driving me absolutely insane. I have searched forums for hours and I am still unable to come up with a resolution to this problem... For the purpose of confidentially, I will be using the contoso.com domain within this thread... I am in the midst of a migration from Exchange 2007 SP3 to Exchange 2010 SP2 rollup4v2. Our Exchange 2010 environment consists of a single hub transport / client access server, and a single mailbox server. We are not using an edge transport server. I am having a problem getting outlook anywhere to function properly with our non-domain outlook 2010 clients... When setting up an email account for outlook anywhere, I am either endlessly prompted for authentication, or receive the following errors: "The action cannot be completed. The connection to Microsoft Exchange is unavailable. Outlook must be online or connected to complete this action". "Your server or mailbox names cannot be resolved". Within the e-mail account setup I have proxy settings in place "msstd:mail.contoso.com" and I am using Basic authentication from the outlook client, NTLM (for outlook anywhere) on the exchange hub/cas server. I ran the ExRCA for outlook anywhere using autodiscover. All tests pass, with the exception of the last: Testing the Name Service Provider Interface (NSPI) on the Exchange Mailbox serve
in Exchange 2010 Exclaimer 3,204 Followers - Follow 43 Mentions12 Products Neal (Exclaimer) Sales & Marketing Manager GROUP SPONSORED BY EXCLAIMER IN THIS DISCUSSION IIS Microsoft Exchange Server 2010 Microsoft 489902 Followers Follow Join the Community! Creating your account only takes a few minutes. Join Now I'm working on setting up RPC over HTTP on Exchange 2003 SP2. RPC over HTTP was previous set up (no idea if it was ever working) and everything appears to be in place. If I run the Remote Connectivity Analyzer if fails at: An error occurred while testing the NSPI RPC endpoint. Test Steps Attempting to ping RPC endpoint 6004 (NSPI Proxy https://social.technet.microsoft.com/Forums/exchange/en-US/85886a9c-753f-45a0-8883-d75501b48c95/outlook-anywhere-an-error-occurred-while-testing-the-nspi-rpc-endpoint?forum=exchange2010 Interface) on server xxxxxxxxxx. Additional Details The RPC_S_SERVER_UNAVAILABLE error (0x6ba) was thrown by the RPC Runtime process. I've checked Netstat and 6004 is listening and I've telnet'd to it and it responds (but the response is blank!!) So maybe that is the issue. What should the response look like if it is healthy? DNS seems to be fine as does AD. Reply Subscribe RELATED TOPICS: RPC over HTTP for Exchange 2003 issues Exchange 2003 to https://community.spiceworks.com/topic/323555-rpc-over-http-exchange-2003-r2-failing-with-nspi-unreachable 2010 migration - RPC over HTTPS How to setup RPC over HTTP for Exchange 2003?   1 2 3 4 Next ► 78 Replies Datil OP Jono Apr 11, 2013 at 5:29 UTC What program did you use to test ? OOPS edit saw that now ! Obvious ones;- Is the RPC service running ? Have you run RPCPING http://support.microsoft.com/kb/831051
Edited Apr 11, 2013 at 5:40 UTC 0 Ghost Chili OP Thanks A.J. Stringham Apr 11, 2013 at 2:02 UTC Firewall issue? Try disabling any AV temporarily and see if that fixes it. Or add an exception. A.J. 0 Pure Capsaicin OP Scott Alan Miller Apr 11, 2013 at 2:03 UTC Niagara Technology Group (NTG) is an IT service provider. A.J. Stringham Geek wrote: Firewall issue? Try disabling any AV temporarily and see if that fixes it. Or add an exception. A.J. It's all one server so unless it is blocking the loopback. 1 Ghost Chili OP Thanks A.J. Stringham Apr 11, 2013 at 2:04 UTC Scott Alan Miller wrote: A.J. Stringham Geek wrote: Firewall issue? Try disabling any AV temporarily and see if that fixes it. Or add an exception. A.J. It's all one server so unless it is blocking the loopback. Try disabling the AV. A.J. 0work. I cant set up my CCV email at home and I have tried every setting combination I have read about. On the server “Outlook Anywhere” is enabled and I have tried both “basic and NTLM authentication” https://citrt.onthecity.org/plaza/topics/63e6b329733a11fbc8e5e4b942d86680249087e1?group_id=53258 RPC over HTTP Proxy is also running Server Manager/Features Firewall is allowing HTTP and HTTPS We can sucessfully set up exchange mail on our smart phones from anywhere. Outlook OWA works fine from home mail.ccvonline.com Interact using http://serverfault.com/questions/390123/the-name-cannot-be-resolved-the-operation-failed-when-connecting-rpc-over-http your Facebook account: Login with Facebook Comments Jim Michael Nothing pops out to me immediately, but are you familiar with https://www.testexchangeconnectivity.com/ ? It’s a fantastic (Miscrosoft-run) site for testing Exchange connectivity issues. I’d start with an Outlook connectivity test an error and see what errors it gives you. Chris Green it just autodiscover not working? or the actual connection to it that is failing? Chris Holub The other guy that works with me tried that https://www.testexchangeconnectivity.com/ and said it was working. i just tried it and see an error. I think he was only trying Exchange ActiveSync. I just tested the RPC over HTTP and got an error Testing the Name Service Provider Interface (NSPI) on an error occured the Exchange Mailbox server. An error occurred while testing the NSPI RPC endpoint. Test Steps Attempting to ping RPC endpoint 6004 (NSPI Proxy Interface) on server CCVEXCHANGE07.ccvonline.com. The attempt to ping the endpoint failed. Tell me more about this issue and how to resolve it Additional Details The RPC_S_SERVER_UNAVAILABLE error (0×6ba) was thrown by the RPC Runtime process. Angela Creason Do you have the URL set incorrectly for the RPC over HTTP? I can’t remember if it is a URL or server name. Whatever I’m talking about has mms in it. We had that set incorrectly once and experienced similar symptoms. Chris Holub RPC over HTTP as a feature is on but I dont see a way tp go look at any info about it. It’s one of the feature that you can have running or not. Jim Michael Maybe this will help? http://technet.microsoft.com/en-us/library/dd439392(v=exchg.80).asp Jeromy Stark If you are using Office 2007, you might need to do the register hack. HKEY_CURRENT_USER\Software\Microsoft\Office\12.0\Outlook\RPC 3. On the Edit menu, point to New, and then click DWORD Value. 4. Type DefConnectOpts, and then press ENTER. 5. Right-click DefConnectOpts, and then click Modify. 6. In the Value data box, type 0, and then click OK. Chris Holub I think I need someone to log in remotely with me and see if the
Start here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack Overflow the company Business Learn more about hiring developers or posting ads with us Server Fault Questions Tags Users Badges Unanswered Ask Question _ Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute: Sign up Here's how it works: Anybody can ask a question Anybody can answer The best answers are voted up and rise to the top The Name cannot be resolved. The operation failed. When connecting RPC over HTTP (exchange 2010) up vote 0 down vote favorite I am getting the error "The Name cannot be resolved. The operation failed." for users of a certain database on our Exchange cluster for our tests to a new server migration with a Client Access Server. The email actually worked after it was moved to a new server until we deleted the address and attempted to again resolve the user account and server. We can't get it to work at at all now. The users cannot resolve the Microsoft Exchange Server or Mailbox when entering the info into a new account and I ran a test with the account at testexchangeconnectivity.com and the error below came up: Testing the Name Service Provider Interface (NSPI) on the Exchange Mailbox server. An error occurred while testing the NSPI RPC endpoint. Test Steps Attempting to ping RPC endpoint 6004 (NSPI Proxy Interface) on server (MailServer the account was migrated from). The endpoint was pinged successfully. Additional Details RPC Status Ok (0) returned in 953 ms. Testing NSPI "Check Name" for user user@domain.com against server (MailServer the account was migrated from). An error occurred while attempting to resolve the name. Additional Details An unexpected error was returned from NspiResolveNames. Code: 2147500037 Auto discover is set up as well and points to the proper server to connect to but the internal server name(where you enter the account as well) shows the old server. Any ideas would be appricated! Thanks windows-server-2008-r2 exchange-2010 outlook-2010 share|improve this question asked May 17 '12 at 19:13 Jeff 575514 add a comment| 1 Answer 1 active oldest votes up vote 0 down vote accepted Figured it out. We updated the old and new server