Sql Server 2005 Dev. Ed. on Windows Server 2003
- From: BrianR <BrianR@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Wed, 3 Sep 2008 05:48:01 -0700
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
.
- Follow-Ups:
- Re: Sql Server 2005 Dev. Ed. on Windows Server 2003
- From: Ekrem Önsoy
- Re: Sql Server 2005 Dev. Ed. on Windows Server 2003
- Prev by Date: Re: unable to install sql server 2005 enterprise edition on windows vista home premium
- Next by Date: Cannot upgrade SQL Server 2005 Reporting Services from Standard to Enterprise
- Previous by thread: unable to install sql server 2005 enterprise edition on windows vista home premium
- Next by thread: Re: Sql Server 2005 Dev. Ed. on Windows Server 2003
- Index(es):
Relevant Pages
|
