New user to Snitz and first-time poster. I'm trying to get Snitz to work on Win2000 Server + MS SQL 2000 with a DSN connection. IIS and SQL are installed on the same box.
When I load setup.asp in my browser, it returns the error: [Microsoft][ODBC SQL Server Driver][SQL Server]Login failed for user '(null)'. Reason: Not associated with a trusted SQL Server connection.
If I try using the OLEDB connection string, it works fine, but not with DSN. I have another website on this server that uses DSN--it works fine.
It works fine if I change the DSN line in config.asp so it reads: strConnString = "DSN=mydsn;uid=myuser;pwd=mypwd;database=mydb" But doesn't this defeat the purpose of using DSN in the first place?
Can someone help me understand why this doesn't work without putting the uid/pwd credentials in the DSN line? Isn't one of DSN's strengths that you don't have to hardcode username/password sets like this?
I don't see your problem, just use the correct string. Personally I don't see the advantage of using a DSN to connect to any DB, but specially when dealing with a SQL DB. The OLEDB string is more robust and the forum runs faster when you use OLEDB strings.
I don't see your problem, just use the correct string. Personally I don't see the advantage of using a DSN to connect to any DB, but specially when dealing with a SQL DB. The OLEDB string is more robust and the forum runs faster when you use OLEDB strings.
The advantage to using DSN (as I understood it) is that you do not need to put the uid/pwd credentials in plain text in the script. Or at least I thought that was a major reason for using DSN. I've likewise read that OLEDB is a better, faster connection (so I'll use it). *shrug* I guess it's just one of those things: I wanted to make it work because I was having problems getting it to work.
Topic Locked
Posted - 03 November 2004 : 10:43:06
