Hi, I'm having a rough weekend and really need some advice. We've been having some problems with our SQL Server ever since an upgrade to SQL 2K and then were moved by the IT security people to a new domain that is not in a trust relationship with the domain the SQL Server is on. After the move, attempts to log into a CMMS application we use, called Maximo, are failing. The error indicated that the user's domain login isn't trusted with the SQL Server. This is odd, because we use SQL Server Authentication and each user has a different username on the SQL Server and shouldn't care about the domain login, so I don't know why it's even being passed. This application has been working fine on SQL Server 7 for the past 3 years.
Our SQL Server is setup for Mixed Mode (set during installation and verified in Ent Mgr) and the clients are using ODBC to connect with TCP/IP port 1433 (setup with the client configuration in the ODBC properties) using SQL Server Authentication. The problem is that the settings seem to be ignored and it's using Windows Authentication only, which is a major problem. All of the grants are given to the SQL Server user by the Maximo application and all records are tracked by the login, so we can't use Windows Authentication. I am able to add the user's domain login to SQL Server and give it RW rights to the database and the user is able to login, however unable to run reports because the grants are given to the SQL Server login, not the domain login.
I tried removing the server from the domain it was on and making it a stand alone server, which resulted in the following error:
Login failed for user '(null)'. Reason: Not associated with a trusted SQL Server connection.
This is telling me that it's ignoring SQL Server Authentication. I've also tried installing Patch 3a on SQL Server and installing MDAC 2.8 on the client.
I choose SQL and windows authetication during SQL Express 2005 install. Will this has any impact on the connection string in my Visual Studio 2005 environment?
Hi, Just upgraded some development desktops to Vista Business. However we need to still connect to some older remote windows 2000/SQL 2000 servers.
Trying to setup an ODBC system DSN on our Vista Business local desktop we get the following errors -
-START ERROR WINDOW- Connection Failed: SQLState: '01000' SQL Server Error: 772 [Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]ConnectionOpen (SECDoClientHandshake()0. Connection failed: SQLState: '08001' SQL Server Error: 18 [Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]SSL Security Error -END ERROR WINDOW-
Any help greatly appreciated as this is stopping us from making database/table connections etc. We've checked the firewall setup and all is well there.
PS - we can still connect fine using XP or windows 2000 desktops and their local DSNs.
Hello,I received the error message below when i'm trying to install SQLServer 2000 standard edition into a Windows 2000 Professionaleworkstation.Error :Microsoft SQL server 2000 Standard Edition server components is notsupported on this operating system. Only client components will beavailable for installation.Any request modification ?Best regards,Thanks
I've just started getting this EXCEPTION_ACCESS_VIOLATION (0xc0000005) on machines using Windows 2000 sp4 connecting to SQLServer. This is crashing JVMs (multiple Sun versions and BEA also) in the Java VM frame (outside our code). This has just started recently - perhaps with the last set of patches? Has anyone else seen this or know what I could do to get more information? Could this be related to updates to named pipes?
We have a SQL Server 7.0 system in NT 4.0 environment. We upgraded our users to Access 2000 and started to work with this. Now we installed a new server which is Windows 2000 based and the domain is different from the SQL servers domain. We then installed Access 2000 on Windows 2000 to use with terminal server. But I noticed that there was a problem with the program. I then looked at the program which was written on Access 2000 and saw that the tables and views can't be seen. The program runs but I can't see the views and tables. Another thing is access disconects from SQL Server when I want to see the tables. So what can be the problem.
In one part there is an Access 2000 on Windows 2000 server. On the other part SQL Server 7.0 on Windows NT 4.0. And Access can't see the tables in SQL server.
I am trying to install microsoft sql server 2000 enterprise edition on a windows 2000 advance server. I keep getting error message
A previous program installation created pending file operations on the installation machine. You must restart the computer before running . I have restarted machine and no change.
What does error message mean and what is solution?
We installed SQL7 over the weekend. Everything was working peachy through yesterday. This morning SQL server is requiring all of the queries to require references to the username in the from clause...
For example
"Select * from mytable" used to work fine. Not it requires "select * from username.mytable"
I'm logged in as the same username, which is the DB Owner as well. Any idea why this is happening all the sudden?
Can I install SQL Server 2000 on Windows 2000 Professional, I have tried but message was "this platform is not supported" and only client components will be installed after installing, I was unable to create any database.
Can SQL Server 2000 Enterprise Edition (32-bit) be installed on a Windows 2003 Server R2 SP2 64-bit clustered system?
I have the Windows Cluster fully patched, but when I try to install SQL server 2000 Ent Ed (32-bit) from the directory 'd:englishsql2000entx86setupsetupsql.exe' it hangs after I enter the virtual server IP.
NB. I have successfully installed SQL 2000 Ent Ed (32-bit) on a clustered Windows 2003 Server (NOT R2)
Any help or pointers would be greatly appriciated.
Hi, I have a problem.I have two computers (clients), one with Windows 2000 and second withWindows XP. And a third computer (server) with a Windows 2000 and MS SqlServer 2000.I have a TABLE with two rows: 'row' and 'row ' (space).And SQL: 'select * from TABLE where row = 'row'If I run this SQL on computer with Windows 2000 it works ok (return only onerow: 'row').If I run this SQL on computer with Windows XP it works really strange(return two rows: 'row' and 'row ' ) - it can't see this spaces.Is there differences between MS Sql Server on W2000 and WXP?Thanks for the helpMagda
Hi all,I have a Windows 2003 server, which is also a terminal server forapplication, with sql 2000 installed. My company has developed anapplication that uses SQL 2000 as its database. The application is aclient/server one. In each client computer there's a link to theapplication on the server. There is no problem with Windows 98,Windows 2000 pro, Windows xp pro clients, but the windows 95 onescannot log in to the database. The log of the application shows thefollowing error:connection error -2147467259. Cannot open database requested in login'database name'. Login fails.Till a week ago the application was running on a Windows 2000 serverwith SQL 2000 install and the W95 clients had no problem connecting tothe database, so my guess is the error has something to do withWindows 2003 server, but what'causing the error?I tried to install a newer version of MDAC (MDAC 2.5, the last versionof MDAC you can install on W95)but with no success. By the way W95clients have no problem accessing shared folder on the Windows 2003server.Any idea?ThanksMarino
This is my first post and I am a newbie user of SQL Server as well. I am using SQL Server 2005 Express edition. I have also installed SQL Server 2005 Mangement Studio express.
Initially I was under Windows Authetication but today I changed it to mix mode. After doing everything and enabling the authentication for the "sa" user I am getting the following error.
In the login dialog window for the user name I am providing: sa
TITLE: Connect to Server ------------------------------
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.) (Microsoft SQL Server, Error: 233)
When I try the second time it gives this error:
TITLE: Connect to Server ------------------------------
Currently, I have the client side of SQL Server 6.5 (Enteprise Manager, Security Manager, Books Online, etc.) installed and running under Windows NT 4.0 Workstation. When I attempt to install the same package under Windows 2000 Professional I get the following message - This program does not run correctly on this version of windows. To continue, click Run Program. Has anyone sucessfully installed this under Windows 2000 Professional? Are there any patches or service packs to apply? Thanks.
We are going to upgrade to windows 2000 in the near future. We currently use sql server 6.5. Can anyone tell me if SQL 6.5 will run on windows 2000? Also will SQL server v7 run on windows 2000 or do I need to upgrade to SQL 2000?
WHEN I TRY TO LOAD THE SQL 2000 SERVER I GET THE FOLLOWING ERROR:
MICROSOFT SQL SERVER 2000 DEVELOPER EDITION SERVER COMPONENT IS NOT SUPPORTED ON THIS OPERATING SYSTEM. ONLY CLIENT COMPONENTS WILL BE AVAILABLE FOR INSTALLATION.
AT THE PRESENT I AM RUNNING WINDOWS ME AS THE OPERATING SYSTEM. THIS VERSION OF SQL SERVER 2000 WAS BOUGHT FROM MICROSOFT A COUPLE OF MONTHS AGO. THIS IS MY FIST TIME TRYING TO INSTALL IT.
Hello y'all, I have to do a new install of SERVER 2000 using WINDOWS 2003 . Has anyone done this. If so, what are the steps. Should I expect any problems ? Any help appreciated. Thanx
I was wondering how to install SQL Server 2000 on a windows xp system as I have seen it on one of my friend's PC and I was also able to do it 5 years ago... lol
Just don't remember it. I know it's perfectly compatible with Windows 2000 server and above. I was just looking for a hack on this...
We have a financial software package that has been certified for SQL 2005 and Windows 2003 server. Will SQL 2005 run on a Windows 2000 server? I don’t want to build a new server at this time unless I really have too.
I have XP workstations and windows 2003 SBS. I setup an ODBC for anapplication (tried both User and System DSN), but after a few usage, I getthe following error:Connection failed:SQLState: 'HY000'SQL Server Error: 0[Microsoft][ODBC SQL Server Driver]Cannot generate SSPI context.Any ideas? Is this a bug?--Thank youPlease post only
Hi, I currently have a Compaq ProLiant DL360 server running with Windows Terminal Server 2000. I want to switch to a Dell server, but the old server contains 5 terminal users. How can I switch the license to the Dell server?
For a SQL Server 2000 machine that performs no other function than being a database server with no web services, reporting services, or analysis services, I'm wondering if there is any documentation on what services would typically be running and, more importantly, which ones could be stopped.
For example, I'm looking at a server and I see services such as Computer Browser and Microsoft Search. I don't see why either of these services are necessary for this machine.
Hi, I am having a problem connecting my .net applications from the application server to the database server. When I run the application from my windows xp (sp2) box it works fine. When I try to connect via SQL Management Studio to the database server from the application server I get the same error. Here is the error: System.Data.SqlClient.SqlException: An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server) Here is the Environment: App Server: Windows Server 2003 Standard Edition Inside Company's Firewall/ Network Database Server: Windows Server 2000 Advanced Edition SQL Server 2000 SP4 Remote Connections to the Server is checked Enable Protocols: Named Pipes & TCP/IP TCP/IP Port: 1402 (I don't know why it isn't the default of 1433) The db server is sitting out side the Company's firewall (don't ask me why). I can access it fine from inside the firewall on my XP box but not from windows server 2003. There is a web server outside the our network that also connects to the db server with no problem and that is running Windows Server 2003 Web Edition. I can ping the db server from the app server using the IP address. I tried using the IP address and the port 1402 in my connection string but that didn't work from any machine (XP and Server). I imagine the issue is somehow related to the company's firewall but why would it only block Windows Server 2003 and not XP? What do I tell the network admin to change? Any help would be appreciated. Thanks, Oran
My school is runnnig SQL Server 2005 and i want to connect to it using authetication (userid & passphrase). As i coded the windows application i used localhost as my own computer and IntegratedSecurity shown below. I'm new in C# and SQL. I would appriciate if someone could help me out.
using System; using System.Data; using System.Data.SqlClient; using System.Text;
namespace Personregister { class DBManager { SqlConnection conn; SqlConnectionStringBuilder builder;
public DBManager() { builder = new SqlConnectionStringBuilder(); builder.DataSource="localhost"; builder.InitialCatalog = "Personregister"; builder.IntegratedSecurity = true; conn = new SqlConnection(builder.ToString());
