Re: Sql Server 2005 Dev. Ed. on Windows Server 2003

First of all, it seems that you are attempting using SQL Server 2005 Developer Edition for your production server. This is against the license agreement of this product of Microsoft. You are allowed to use this edition of SQL Server only for demonstration, test and development purposes and of course if you have a valid license for it.

You did not mention if your Windows XP is with its SP2 or not, but Windows Server 2003 has a Windows Firewall ships with it. And this Windows Firewall comes also with Windows XP' s SP2. Have you configured your Windows Firewall on your Windows Server? For Windows Firewall settings see these links:
http://support.microsoft.com/kb/841249
http://msdn.microsoft.com/en-us/library/ms175043(SQL.90).aspx

I suggest you to try to connect to your SQL Server instance on the Windows Server machine using SSMS which is installed on your Windows XP machine. So, you'll see if the problem is about the software settings or if there is another problem (with the Windows Firewall, or port, or protocol configuration) or your Windows Server or SQL Server...

--
Ekrem Önsoy



"BrianR" <BrianR@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message news:CC3DFD49-2D92-47DE-9441-6AFD17C1C31B@xxxxxxxxxxxxxxxx
I'm replacing an older computer which is running Widows XP Pro and Sql 2000.
We are accessing the current sql server via a web app (ASP). This has worked
great but it's time to upgrade and I've purchased a new Dell server with
Windows 2003 Server installed. I've done the following:
- installed SQL 2005 Dev. Ed.
- made sure sql server was set to allow remote connections (Sql Serv.
Config)
- created a new DSN on the web server to point to new sql server
- attached database(s) after detaching the database(s) on the old sql
server 2000 and copying the MDF/LDF files over to the new sql server 2005

I continue to get 500.100 error (ADODB.Recordset (0x800A0E78) "Operation is
not allowed when the object is closed". This is failing in the index.asp file
as soon as it tries to read a recordset from the database. It doesn't
complain when it connects to the database using DSN.

I installed SQL 2005 Dev. Ed. on my laptop (XP) with IIS running and I've
been able to connect to my local DB using DSN and on the older Sql 2000
server using DSN without an issue.

What is so different with SQL Server 2005 on XP Pro and Server 2003?

BrianR

.

Relevant Pages

  • Re: Group Policy Results Wizard
    ... I guess we can rule out Windows ... If you can't reach the WMI from the server you will want to try to reach it ... switching off the Windows Firewall on one of the clients, ... Business Server Windows Firewall" (not Small Business Server ...
    (microsoft.public.windows.server.sbs)
  • Re: SQL Server 2005 Login Problem
    ... There are two authentication method in SQL Server. ... 1- Windows Authentication ... 2- Mixed Authentication (through SQL Server logins and Windows accounts) ...
    (microsoft.public.sqlserver.clients)
  • RE: My Documents Redirection error
    ... We can upgrade the instance SharePoint ... >> is no need to manually migrate data from MSDE to SQL server and all dada ... >> How to back up and restore http://companyweb data in Windows Small ...
    (microsoft.public.windows.server.sbs)
  • Re: server authentication & ASP authentication
    ... on to the client workstation with an authorized Windows account. ... SQL Server with Windows authentication. ...
    (microsoft.public.sqlserver.security)
  • RE: My Documents Redirection error
    ... > is no need to manually migrate data from MSDE to SQL server and all dada is ... > How to back up and restore http://companyweb data in Windows Small Business ... Insert the Microsoft Windows Small Business Server 2003 Premium ...
    (microsoft.public.windows.server.sbs)
Loading