Error Occurred During The Login Process
Contents |
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 but then an error occurred during the login process error 233 Learn more about hiring developers or posting ads with us Stack Overflow Questions Jobs Documentation
An Error Occurred During The Authentication Process
Tags Users Badges Ask Question x Dismiss Join the Stack Overflow Community Stack Overflow is a community of 4.7 million programmers, just like
An Error Occurred During The Encoding Process
you, helping each other. Join them; it only takes a minute: Sign up SQL Server 2008 Connection Error “No process is on the other end of the pipe” up vote 17 down vote favorite Let me begin
An Error Occurred During The Submit Process
by saying, I am aware of this thread and others around the web that seek to trouble shoot this issue. The solutions posted there do not apply to my issue. I have spent 5 hours trying to resolve this before deciding to ask the question. The problem: When I attempt to log into SSMS (or connect from a java application) using SQL Authentication I get this error: A connection was successfully established with the server, an error occurred during the submit process adobe reader but then an error occurred during the login process. (provider: Shared Memory Provider, error: 0 - No process is on the other end of the pipe.) (Microsoft SQL Server, Error: 233) Although it does work, it is not an option for me to use integreated authentication. The database I am attempting to connect to is on the same machine as my SSMS instance. There is no network, this is a stand-alone system. NAMED PIPES is ENABLED in my configuration, I HAVE rebooted since, TCP IP is a higher priority than named pipes in my configuration. I have even gone as far as to uninstall SQL Server and reinstall it, to no avail. The details of my SQL Server instance are as follows: Microsoft SQL Server Management Studio - 10.0.2531.0 Microsoft Analysis Services Client Tools - 10.0.1600.22 Microsoft Data Access Components (MDAC) - 6.1.7601.17514 Microsoft MSXML - 3.0 5.0 6.0 Microsoft Internet Explorer - 9.0.8112.16421 Microsoft .NET Framework - 2.0.50727.5466 Operating System - 6.1.7601 Configuration details are as follows: http://i45.tinypic.com/vxdz7c.png http://i45.tinypic.com/vxdz7c.jpg I connect from java using this code. Class.forName("com.microsoft.sqlserver.jdbc.SQLServerDriver"); String connectionUrl = "jdbc:sqlserver://localhost;database=AdventureWorks;integratedSecurity=false;User=JIMBO; Password=JIMBO;"; Connection con = DriverManager.getConnection(connectionUrl); But please remember, this error also occurs when I atttempt to log in to SSMS directly. Thanks in advance. -Jim sql-server-2008 share|improve this question edited Mar 23 '13 at 9:48 asked Mar 23 '13 at 9:09 Jim
Tips/Tricks Top Articles Beginner Articles Technical Blogs Posting/Update Guidelines Article Help Forum Article Competition Submit an article or tip Post your Blog quick answersQ&A Ask a Question View Unanswered Questions View All Questions... C# questions Linux questions ASP.NET questions SQL an error occurred during logon questions VB.NET questions discussionsforums All Message Boards... Application Lifecycle> Running a Business Sales / an error occurred during logon 0xc00006d exchange Marketing Collaboration / Beta Testing Work Issues Design and Architecture ASP.NET JavaScript C / C++ / MFC> ATL / WTL / STL Managed an error occurred during logon 0xc00002ee C++/CLI C# Free Tools Objective-C and Swift Database Hardware & Devices> System Admin Hosting and Servers Java .NET Framework Android iOS Mobile SharePoint Silverlight / WPF Visual Basic Web Development Site Bugs / Suggestions Spam and http://stackoverflow.com/questions/15585069/sql-server-2008-connection-error-no-process-is-on-the-other-end-of-the-pipe Abuse Watch features Competitions News The Insider Newsletter The Daily Build Newsletter Newsletter archive Surveys Product Showcase Research Library CodeProject Stuff communitylounge Who's Who Most Valuable Professionals The Lounge The Insider News The Weird & The Wonderful The Soapbox Press Releases Non-English Language > General Indian Topics General Chinese Topics help What is 'CodeProject'? General FAQ Ask a Question Bugs and Suggestions Article Help Forum Site Map Advertise with us About our Advertising http://www.codeproject.com/Questions/356619/A-connection-was-successfully-established-with-the Employment Opportunities About Us Ask a Question All Questions All Unanswered FAQ A connection was successfully established with the server, but then an error occurred during the login process. (provider: Shared Memory Provider, error: 0 - No process is on the other end of the... Rate this: Please Sign up or sign in to vote. See more: SQL-Server Hi all!!! I created a database owner in sql-server 2008. I set authentication type to sql server authentication , added username and password to it then set the user mapping for this user to be database owner. Now when i am trying to run management studio using sql sever authentication , it's showing me this error A connection was successfully established with the server, but then an error occurred during the login process. (provider: Shared Memory Provider, error: 0 - No process is on the other end of the pipe.) (.Net SqlClient Data Provider) I tried to find solution on google but can't find any specific solution. Posted 28-Mar-12 22:16pm ujjwal uniyal1.5K Add a Solution 7 solutions Top Rated Most Recent Rate this: Please Sign up or sign in to vote. Solution 1 Accept Solution Reject Solution This error happens becasue the named pipe support is not enabled for your SQL server.To enable named pipes or for workarounds see the link http://msdn.microsoft.com/en-us/library/ms
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 http://serverfault.com/questions/747623/sql-server-local-instance-no-process-is-on-the-other-end-of-the-pipe 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 error occurred rise to the top SQL Server, local instance, No process is on the other end of the pipe up vote 0 down vote favorite On a fresh installation, on my local SQL server instance, using SQL Server Management Studio, I can login with my Windows authentication, but not with my sa user. In both cases, I'm using (local) as my Server name. The error is the following: A error occurred during connection was successfully established with the server, but then an error occurred during the login process. (provider: Shared Memory Provider, error: 0 - No process is on the other end of the pipe.) (Microsoft SQL Server, Error: 233) The password is correct, since I've change it. I did reboot my computer since the installation of SQL Server. The SQL Server Agent is not running; I believe it's only for the jobs. The SQL Server Browser is not running; I believe it's only for remote connections, and it's not running as well on another computer where I don't experience the problem. In the SQL Server Configuration Manager, the SQL Native CLient (both 32 and 64 bits) enables Shared Memory, TCP/IP and Named Pipes (I didn't changed anything on these settings) In the SQL Server Configuration Manager, the SQL Server Network Configuration only allows Shared Memory and TCP/IP; Named Pipes and VIA are disabled (I didn't changed anything on these settings) In the SQL Server Configuration Manager, trying to activate the Named Pipes for the Network Configuration (and to restart the MSSQLSERVER service) didn't fixed the problem (I didn't reboot for this change). I've tried to change the connextion Server name from (local) to 192.168.x.x