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?
Hi all,Have a situation that my company has never run across before. Clientis running NT4 for the domain server, using terminal services 2000 andrunning an application with a SQL Server backend and they areexperiencing locking problems. Once one person gets locked out theneveryone trying to access that tables is also locked out as a result.It is not specific to a certain User, or module within theapplication. It's not a specific time of the day (like when a backupwould be running) and sometimes it's in the middle of the night whenthere are actually less Users on the system.We have 500 customers using this application. Most are using SQLServer backend, alot of the newer customers are using TerminalServices, and the number of Users is not accessive as compared to ourother customers. THe only difference is that I do not specificallyknow of another client with an NT4 Domain server in the mix.We actually switched to SQL Server as the recommended back end due tolocking issues using SQLBase because SQL Server is row locking andSQLBase is page locking. Since making this change we have stoppedseeing the locking for years until now. Is this a SQLServer issue orissue with the NT Domain server?Anyone have any ideas???ThanksA
I need to know if Microsoft supports SQL Server 2000 running on the same server that functions as a Terminal Server (both NT and Windows 2000).
I checked out Microsoft.com and found that SQL Server 7 is supported with NT Terminal Services but can't locate any compatability information SQL 2000.
PS: I know this configuration doesn't make sense from a performance perspective but my customers will want to do this anyway.
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?
Has anyone else found problems with their Terminal server after installing SP 3 for SQL 7.0? Our users permissions changed for their printers and ODBC was giving all kinds of cryptic error messages. When the users rights were changed from Domain User to Domain Admin everything works fine. We have been able to reproduce this on numerous servers.and always after we applied the SP did the problems start.
In the past I have had SQL and Terminal server on the same PC.With SQL and Windows 2003 Terminal server, you can not have them on thesame PC.How can I make this work with SQL and Terminal and 2 different PC's? Ihave 30 users that need to log on to my SQL database.
We connect via terminal services to an excel spreadsheet that has anODBC link to an access database using a pivot table, when we try torefresh the data within the excel spreadsheet we receive the followingerror "the microsoft jet database engine cannot find the input table orquery....."this works ok if the user connects to terminal services as theadministrator however if they connect as any other issue it won't workAnyone got any ideas?(have tried 2000 ts and 2003 ts)
I am specifically looking for a KB article, best practice, white paper etc, that states it is not recommended that SQL Server (either 2000 or 2005) is installed on a WIndows 2003 Server that is also running Terminal Services in application mode.
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
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
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.