SQL Server 2000 + 2005 Working On Same Windows 2003 Server As Seperate Instances
Nov 20, 2006
Hi all,
I just asked some people to help me out and phone microsoft with the
following information, kindly they refused unless we setup a support
contract with them first, for pre-sales information. (That really does
not sound like good business sense to me - anyway here is our problem,
if anyone could help thanks).
"To tell and ask microsoft:
We will be setting up a microsoft sql server 2000 instance running on a
windows 2003 server.
1) We need to check this can run alongside a microsoft 2003 sql server
(either workgroup or standard edition), on the same machine. Are there
any .dll clashes if we do this? If there are can we run SQL Server
2000, in a virtual machine running windows 2000 professional. (I have a
licenced copy we can use for this).
2) If we run one instance of 2000, and one of 2003 of the sql servers,
can one use the processor licence model, and one use the CAL licence
model."
Thanks for any help, and any idea why they actually force you to use
news groups for pre-sales information?
Where can I further educate myself on this subject?
Right off from the start I would assume that installing SQL Server 2000 or 2005 on Windows Server 2003 that is set up as a web server hosting a website would be against "best practices." Is my assumption right?
Common sense tells me to not to host a website on a pc that is also hosting my database.
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
Hi,Is it possible to install on a Windows server 2003,SQL SERVER 2000 in the folowing configuration :SQL server 7.0 as a default InstanceandSQL server 2000 as a named instance.Thanks for your answer.
My uncle runs a small networking company and has extra licenses for Windows 2003 Server as well as SQL Server 2000. Since I just graduated from college and have started working as a database programmer (for a different company) I'd like to setup a small server at home to learn more about SQL (as well as networking, but SQL is my primary concern). I know I can setup SQL Server 2000 on my main PC, but I'd still like to set everything up in a server environment.
So, what I'm wondering is if any books (or web sites?) exist that walk you through setting up Windows 2003 Server and SQL Server 2000. I've actually set these up before (it's not very complicated) but I'm not sure if I did it the "correct" way.
Ideally if any books exist on O'Reilly's Safari Bookshelf that would be even better.
We got SQL Server 2000 Standard Edition SP3 running on Windows 2003 Standard Edition server.
Now, we would like to apply windows 2003 SP2 to the Operating System.
We are concerned that whether windows 2003 SP2 is compatible with SQL server 2000 (SP3)?
I was looking at the application compatibility chart for Windows 2003 SP2.Among them Microsoft SQL Server Standard (2000) was listed but with no Service pack details. And also does Standard means standard edition there?
My Question - Is windows 2003 server SP2 compatible with SQL Server 2000 (SP3) Standard Edition? And what if I plan to apply SP4 to Sql Server ?
I'moving my asp application to a new hosting server.
So when i tried the setup locally with the live DB & application in my test machine... The DB access is denied when application tries to hit the DB.
DB is in seperate machine with SQL Server 2000 & application(ASP) is in Windows server 2003..... Kindly help me with your suggestions....on what went wrong?
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 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
set up windows 2003 serversql server 2000have public IP from netword soluctionsI can see websitewhat settings to i need to open up sql server to the public?
Hello ALL I have configured a website on a windows 2003 server, while its database is residing on a remote server with sqlserver 2000 database. In the connection string, I use the server IP address for the remote SQL server, and when the website is browsed, i get an error something similar to the one below: 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) If I test the same website on windows XP, it will connect to the remote server without a problem. Can Anyone please give me a tip about the windows operating system, what should I do to over come this? Thanks in advance regards, Mykhan
We got SQL Server 2000 Standard Edition SP3 running on Windows 2003 server.
Now, we would like to apply windows 2003 SP1 to the Operating System.
We are concerned that whether windows 2003 SP1 is compatible with SQL server 2000 (SP3)?
I was looking at the application comaptibility chart for Windows 2003 SP1.Among them SQL Server 2000 Enterprise Edition Service Pack 3a was listed but not the Standard Edition.
My Question - Is windows 2003 server SP1 is compatible with SQL Server 2000 (SP3)?
I am trying to install SQL 2005 in a 2-node virtual Windows 2003 cluster. I set the cluster up through Virtual Server 2005 with 2 virtual nodes and one virtual domain. The nodes can connect to each other as well as the physical machine. When I try to install a fresh copy of SQL 2005 on my cluster, I get an error every time. The error stops the installation while checking system configuration after installing prerequisites. The log file entry is as follows:
******************************************* Setup Consistency Check Report for Machine: --SERVERNAME-- ******************************************* Article: WMI Service Requirement, Result: CheckPassed Article: MSXML Requirement, Result: CheckPassed Article: Operating System Minimum Level Requirement, Result: CheckPassed Article: Operating System Service Pack Level Requirement, Result: CheckPassed Article: SQL Compatibility With Operating System, Result: CheckPassed Article: Minimum Hardware Requirement, Result: CheckPassed Article: IIS Feature Requirement, Result: Warning Description: IIS is not installed, therefore Report Server feature will be disabled Action: Install IIS in order for Report Server feature to be enabled Article: Pending Reboot Requirement, Result: CheckPassed Article: Performance Monitor Counter Requirement, Result: CheckPassed Article: Default Installation Path Permission Requirement, Result: CheckPassed Article: Internet Explorer Requirement, Result: CheckPassed Article: Check COM+ Catalogue, Result: CheckPassed Article: ASP.Net Registration Requirement, Result: CheckPassed Article: Minimum MDAC Version Requirement, Result: CheckPassed <Func Name='PerformDetections'> 1 Loaded DLL:C:Program FilesMicrosoft SQL Server90Setup Bootstrapsqlsval.dll Version:2005.90.1399.0 Error: Action "InvokeSqlSetupDllAction" threw an exception during execution. Error information reported during run: Source File Name: datastorecachedpropertycollection.cpp Compiler Timestamp: Fri Jul 29 01:13:49 2005 Function Name: CachedPropertyCollection::findProperty Source Line Number: 130 ---------------------------------------------------------- Failed to find property "ComputerList" {"SqlComputers", "", ""} in cache Source File Name: datastoreclusterinfocollector.cpp Compiler Timestamp: Fri Sep 16 13:20:12 2005 Function Name: ClusterInfoCollector::collectClusterVSInfo Source Line Number: 883 ---------------------------------------------------------- Failed to detect VS info due to datastore exception. Source File Name: datastoreclustergroupsproperties.cpp Compiler Timestamp: Fri Jul 29 01:13:49 2005 Function Name: ClusterGroupScope.SharedDisks Source Line Number: 56 ---------------------------------------------------------- Failed to find a cluster group that owned shared disk: J: WinException : 2 Error Code: 0x80070002 (2) Windows Error Text: The system cannot find the file specified. Source File Name: datastoreclustergroupsproperties.cpp Compiler Timestamp: Fri Jul 29 01:13:49 2005 Function Name: ClusterGroupScope.SharedDisks Source Line Number: 56
I have a SQL 2000 DB server running win 2k. I have just recently bought a new webserver that has 2003 server installed on it.
When I try to connect to SQL (through a webapp) using integrated security I get the error message Login failed for user 'NT AUTHORITYANONYMOUS LOGON'
I've tried configuring an application pool to run as a domain user and place the web app into the app pool but the pool fails. The event viewer has an error message that reads IDENTITY OF THE APPLICATION POOL IS INVALID
I've even tried congifuring the process model section of the machine.config to run as a domain user. Its almost as if the identity is not getting passed over to sql.
any ideas please!!!!!!!!! This is driving me nutZZZZZZ
I have several database on a Windows Server 2003. I re-registered this SQLserver, which is local, and after that I cannot see any of the databases inthe Enterprise Manager. The databases still work, since my applications workfine. I have no clue how can I make these databases visible in EnterpriseManager. I tried registering this SQL Server in Enterprise Manager underWindows accounts and SQL Server accounts. Nothing works.Can anybody help?
I have a Windows 2003 Enterprise x64 edition cluster setup and functioning normally. Now, I am trying to get SQL Server 2000 installed as a failover cluster but am having some difficulty. When installing, I get the message '[sqsrvres] ODBC sqldriverconnect failed' in the event log. The message happens when the installer is trying to bring the SQL Server Service resource online.
I am able to ping the name of the instance successfully. I am able to manually start the 'MSSQL$InstanceName' service. I have turned off the firewall on both machines, but this did not help. I have the DTC Service setup as a resource in the same cluster group.
I also read http://support.microsoft.com/default.aspx?scid=kb;en-us;815431 which seemed promising, but did not reolve the problem.
I have a mobile device application using mobile sql 2005 replicating with sql 2000 in a x86 environment. This works fine!
I'm having issues getting this to work under Windows Server 2003 X64.
I've got all the components installed under the X64 environment including CLR 2.0 X64 and the mobile sql tools. the but when I run the Configure Web Synchronization Wizard I get the following error. SQL Server 2005 Mobile Edition Server Tools were not found on the IIS server. Run the SQL Server 2005 Mobile Edition Server Tools installer....
My question is: Were do I get the X64 version of these tools?
sqlce30setupen.msi sql2Ken@P4.msi
The SQL environment is X86 as follows: SQL2000 SP4
Microsoft SQL Server 2000 - 8.00.2039 (Intel X86) May 3 2005 23:18:38 Copyright (c) 1988-2003 Microsoft Corporation Standard Edition on Windows NT 5.2 (Build 3790: Service Pack 1)
Windows 2003 Server and all client PCs are all on the same network. I installed SQL 2005 std version on windows server 2003 and created a database and tables in it.
I have two users, who want to connect to SQL server 2005 from their PCs (they have windows XP):
These are two things that I need to facilitate:
1) They want to be able to write queries using Query Designer and run from their PCs.
2) I created an MS Access database on my PC, I want to use Access database as a front end to the SQL server database. I will create queries, forms in Access DB, and I want to be able to get the data from SQL server Database to do this. I guess I can use ODBC to connect to tables in SQL server database.
3) I want to connect SQL server to Oracle database, and run oracle stored procedures. I want to load the results of oracle stored procedures into SQL server database tables. I guess I will use IIS for this.
Any suggestions are appreciated, especially with item number 1.
SQL Server Reporting Services 2005 Service would not Start on windows server 2003. Working great till yesterday and no changes were made to config file.
Here is the error in Event log
Event Type: Error Event Source: SQL Server Report Service Event Category: None Event ID: 0 Date: 12/13/2007 Time: 8:25:59 AM User: N/A Computer: XXXXXXXXXXX Description: Service cannot be started. Microsoft.ReportingServices.Diagnostics.Utilities.ServerConfigurationErrorException: The report server has encountered a configuration error. See the report server log files for more information. at Microsoft.ReportingServices.Library.ServiceAppDomainController.Start(Boolean firstTime) at Microsoft.ReportingServices.NTService.ReportService.OnStart(String[] args) at System.ServiceProcess.ServiceBase.ServiceQueuedMainCallback(Object state) For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Here is i found in log files ReportingServicesService!resourceutilities!4!12/13/2007-08:25:59:: i INFO: Running on 0 physical processors, 1 logical processors ReportingServicesService!servicecontroller!4!12/13/2007-08:25:59:: e ERROR: Exception caught loading and setting code permissions policy level: System.Security.XmlSyntaxException: Invalid syntax on line 158. at System.Security.Util.Parser.GetRequiredSizes(TokenizerStream stream, Int32& index) at System.Security.Util.Parser.ParseContents() at System.Security.Util.Parser..ctor(Tokenizer t) at System.Security.SecurityManager.LoadPolicyLevelFromStringHelper(String str, String path, PolicyLevelType type) at System.Security.SecurityManager.LoadPolicyLevelFromString(String str, PolicyLevelType type) at Microsoft.ReportingServices.Library.ServiceController.SetAppDomainPolicy() ReportingServicesService!servicecontroller!4!12/13/2007-08:25:59:: e ERROR: Error Starting Service: System.Security.XmlSyntaxException: Invalid syntax on line 158. at System.Security.Util.Parser.GetRequiredSizes(TokenizerStream stream, Int32& index) at System.Security.Util.Parser.ParseContents() at System.Security.Util.Parser..ctor(Tokenizer t) at System.Security.SecurityManager.LoadPolicyLevelFromStringHelper(String str, String path, PolicyLevelType type) at System.Security.SecurityManager.LoadPolicyLevelFromString(String str, PolicyLevelType type) at Microsoft.ReportingServices.Library.ServiceController.SetAppDomainPolicy() at Microsoft.ReportingServices.Library.ServiceController.StartService(Boolean firstStart)
hi everyone, can anyone help me how to install sql 2005 server express edition on windows server 2003 x64 edition. because its my first time installing on a 64 bit OS i dont know how. When i tried installing it gives a warning on ASP.Net , when i ignore that & continue the installation. when installing now the SQLServer Management Studio Express now it says "installation of this product failed because it is not supported on this qperating system....." any idea?
Re: Best Practices (security): Should SQL Server (2005) *not* be installed on the same physical HD as the Windows OS (Server 2003 R2) ?
Hi,
We're setting up some new servers, and today I'm looking into best practices for the SQL Server Setup portion of it.
The servers have include 2 x 250G HD, and from what I've read, where IIS is concerned, it should not be installed on the drive that has the OS on it, for security reasons. I was wondering if the installation of SQL Server should be on the non-OS drive as well ?
I was a Oracle Developer / DBA on Unix Environments all along my career, Very recently iam starting to manage a SQL Server 2005/Windows 2003 Server setup.
Part of my new job is to automate to load Huge Data files/Flat Files (3/4 GB in size) into SQL Server 2005 DB.
Have these initial questions.. Since the files are too large to open at once... What sort of Command Line Interfaces people use on the Windows Boxes.. like doing a "wc" (Word Count) / GREP 'ng Files / Massaging Data Files one line at a time (Like using SED / AWK Commands).. Etc
I have installed SQL server 2005 enterprise edition on Windows 2003 virtual PC (full installation). The installation went through successfully. However, after install completed, I cannot find any of the client tools under the start menu -> all programs -> Microsoft SQL server 2005 menu. The only item listed under the SQL server 2005 is Configuration Tools, which is used to configure the database server.
I have tried to install the client component again (in case I didn't install them at the first place) but the installation process cannot be started since it detected that the client components have been installed already. I can also see the sql server native client running in the services.
The server engine is working fine since I can connect to that sql server using another machine where I have the client tool (SQL server management studio).
One of my friends has exactly the same problem. He installed the sql server 2005 Standard edition on windows 2003 server (full installation), but the client tools are not showing up in the start menu either.
I also checked the location for the SQL server management studio (Microsoft SQL server/90/Tools/Binn/VSShell/Common7/IDE), there is only one folder called publicAssemblies listed under. Is this correct or something is missing?
I am developing a windows application that needs to communicate with a remote SQL server 2005 database. Server allows remote connections and MSDTC service also running. Do I need to run MSDTC service on the client machine where I use desktop application ? any ideas ? It's throwing some error like 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.
But my SQL Server allows remote connection, and I am able to do a select statement. But when I insert/update anything, it's throwing this error. I guess some problem with MSDCT. Anybody have any idea ?
If SQL Server Setup fails, Setup will roll back the installation but may not remove all .manifest files. The workaround is to rename the files and then rerun Setup. For more information, see How to: Work Around COM+ Check Failure in SQL Server Setup.
I have been unable to install SQL Express 2005 Server on my Windows 2003 Server (with SP2 installed). I keep getting an error message saying that Microsoft Windows Installer 3.1 is not installed.
Click here for image
So, I downloaded Microsoft Windows Installer 3.1 v2 (WindowsInstaller-KB893803-v2-x86.exe) but whenever I try to install it I get an error message saying that "the Service Pack version of this system is newer than the update you are applying" and that there is no need to install the update and it stops there.
Click here for image
Is there a workaround to this? How can I get Microsoft Windows Installer 3.1 installed? I tried going to the Windows Update site, I already have everything installed and I even started the Windows Installer service manually. Has anyone else experienced this?
How can I get SQL Server 2005 Express installed if not how can I install SQL Server 2000 on tihs machine? The only reason I am trying to install SQL Server 2005 is because wanted to try it so I uninstalled SQL Server 2000 now I can no longer install SQL Server 2000 again because it won't let me because of the SP2 patch.
