Re: Here's a rather broad question...

Stephen,

Thanks for ignoring the tone used in my original response--your answer (eg,
asking for specific error messages) was exactly what I did NOT want to hear.
:-)

I'm familiar enough with using ADO with VBScript/Javascript in ASP pages,
having developed this particular system (and used it for several years now)
on XP 32-bit / SQL Server 2000 (and then migrated to SQL Server 2005 last
year shortly after it came out). I'm now at a stage where I use XP 64-bit
as my primary OS, so it's only natural that I'd want to migrate this to the
64-bit version of SQL Server 2005. Although I'm a believer in "not fixing
what's not broken", I'm also a developer who's very much interested in
eventually migrating to 64-bit computing. I think it's a great OS for my
own everyday use, so I wanna make sure all the stuff I write also works
natively on it--why shouldn't it; the underlying system may be different,
but my own ASP/ADO code should require very few changes, if any.

On XP 32-bit it was pretty straightforward--I set up a system data source
with the ODBC control panel applet, and my ASP code simply used
"DSN=[whatever]" as its connection string--that's it, and I had no
authentication or permission issues with SQL Server 2000. When I made the
move to SQL Server 2005 (but still on XP 32-bit) I remember having to assign
specific permissions to grant the anonymous IIS user access to the database.
The problem I'm now seeing seems to be twofold: (a) I'm told by the system
the data source name doesn't exist despite recreating it with the control
applet and (b) if I try to use a "real" connection string right in the ASP
code (trying the various examples provided at www.connectionstrings.com) I'm
running into authentication problems just trying to connect. I suspect my
problem stems more from my lack of SQL Server 2005 user/permission knowledge
than ADO itself. As far as I can tell, I suspect the default (anonymous)
IIS user doesn't have the proper permissions to access the database, and I
just can't figure out the right permissions. The changes I need to make can
very well be in SQL or IIS (or both), but I figured since ADO is where the
link between the two is made, it would make sense to ask in an ADO
(*classic* ADO) newsgroup...

I don't have the exact error messages in front of me right now, but I'll try
to revert back to a clean install state for both SQL and IIS--at this point
I've made so many changes to both that I've probably busted all "normal"
user permissions...once I've gone through this...this is where I was hoping
to get pointers to maybe some high-level steps for this particular
environment (XP64/SQL64/IIS/ADO). Of course I'm having a hell of a time
finding the right keywords to get relevant results on Google, hence I
figured it'd be easier to write an actual post...

Essentially, to reiterate, the environment is this (or at least it'll be
once I remove/reinstall both IIS and SQL):

- XP 64-bit
- SQL Server 2005 64-bit
- IIS
- classic ASP
- whatever ADO components are present after installing the components above.
I'm not installing any other database components/tools/access layer beyond
SQL Server 2005 itself.

I should also mention that I have both Visual Studio 6 SP6 and Visual Studio
2005 installed on this machine, although I have no intention (at least for
the near future) to use VS2005 or .NET for any of this--my ASP code is
simple enough to write with Notepad. At some later point I'll probably move
this to .NET, but I'd rather tackle one problem at a time. The system is
functional under XP 32-bit; I just want the same thing to work under this
64-bit box--using the same ASP source, if it all possible.

In any case, I'll try to uninstall/reinstall SQL and IIS (hoping this'll be
sufficient to revert to all their defaults), and try to get exact error
messages before starting to make any change...


.

Relevant Pages

  • Re: Connection from ASP- ODBC vs. SQLOLEDB
    ... The ASP code is already using ADO (adodb.connection, ... The new provider is better than ODBC isn't it, ... SQL Server Client Network Utility- "Enable Shared Memory": ... ASP, ASP.NET as well as Microsoft Content Management Server 2002 SP1a. ...
    (microsoft.public.sqlserver.server)
  • Re: What is the best way to work with SQL SERVER data / tables?
    ... have to learn any of the SQL Server specific optimizations in order to ... I must make a decision soon about ASP and ADO versus ASP.NET. ... Another developer whom I respect a very great deal, ...
    (comp.databases.ms-access)
  • Re: How can I run asp pages in Local Computer?
    ... database-driven (SQL Server or another db is also an option here) website or ... Kristofer Gafvert - IIS MVP ... >> I programmed some asp pages, ... >> I need run asp pages in local computer because I 'm ...
    (microsoft.public.inetserver.iis)
  • Re: New Server RAID setup
    ... While you can certainly run IIS, ASP etc on the same server as SQL Server it ... I don't know how large your DB will be and how much memory IIS ...
    (microsoft.public.sqlserver.setup)
  • IIS on server 2000
    ... When you access a asp page from the website - it ... domain authentication - The SQL server requests a user id ... asp page is running on the IIS webserver it sends the ... Is there a setting in IIS to pass the user login ...
    (microsoft.public.inetserver.iis.security)