jkwasson
asked on
SQL Server 2000 - "SQL Server does not exist or access denied"
Ok, I am relatively new to SQL Server. I just installed SQL Server 2000 Developer Edition on my development workstation, which is XP Pro SP2. In my ASP.NET application I get the error "SQL Server does not exist or access denied." I have done some troubleshooting, looking at other questions here, microsoft, etc., but no luck. I have disabled the windows firewall and I am not running any other firewall on this box.
I moved this project from a different dev box running XP Pro SP2 with a local SQL Server 2000 instance, and it was working fine. I used the import/export wizard to transfer my database to the new box. I believe my connectionstring is OK, but I'll post it here anyway:
data source=localhost;integrate d security=false;uid=mt_mast er;pwd=*** *****;data base=MT_Ca lc
mt_master is a sql server login.
I am running SQL Server 2000 SP4. I can use Enterprise Manager fine, and I can connect to the instance fine using Query Analyzer, choosing my server, etc. It just doesn't work from my application. The error occurs when it tries to open the connection. I have compared my SQL Server logins on the new dev box to those on the old and everything seems to match. I am plum out of idea!
Any help would be greatly appreciated!
jkwasson
I moved this project from a different dev box running XP Pro SP2 with a local SQL Server 2000 instance, and it was working fine. I used the import/export wizard to transfer my database to the new box. I believe my connectionstring is OK, but I'll post it here anyway:
data source=localhost;integrate
mt_master is a sql server login.
I am running SQL Server 2000 SP4. I can use Enterprise Manager fine, and I can connect to the instance fine using Query Analyzer, choosing my server, etc. It just doesn't work from my application. The error occurs when it tries to open the connection. I have compared my SQL Server logins on the new dev box to those on the old and everything seems to match. I am plum out of idea!
Any help would be greatly appreciated!
jkwasson
I found that sometimes it's better to use server name even if it's a localhost - try that.
regs,
yurich
regs,
yurich
ASKER
thanks for the replies. locahost is not a DSN, but my attempt to connect to the SQL Server directly...I tried both of these connectionstrings:
data source=(local);integrated security=false;uid=mt_mast er;pwd=*** *;database =MT_Calc
and
data source=D9150;integrated security=false;uid=mt_mast er;pwd=*** *;database =MT_Calc (D9150 is my machine name where server is running)
I got the same error with both. It is different than what I was getting before. It is:
"Login failed for user mt_master"
Seems to me like this is progress, as it seems I am now at least communicating with SQL Server enough that it is rejecting the login...Do you guys agree? I think my permissions are setup correctly for mt_master...at least they were on the other dev box before I moved to this dev box.
FYI, I also have SQLExpress 2005 running here, but I have it stopped. It installed with VS 2005...don't think it really factors into the equation here though...
so given the new error message, does that give us any more direction?
jk
data source=(local);integrated security=false;uid=mt_mast
and
data source=D9150;integrated security=false;uid=mt_mast
I got the same error with both. It is different than what I was getting before. It is:
"Login failed for user mt_master"
Seems to me like this is progress, as it seems I am now at least communicating with SQL Server enough that it is rejecting the login...Do you guys agree? I think my permissions are setup correctly for mt_master...at least they were on the other dev box before I moved to this dev box.
FYI, I also have SQLExpress 2005 running here, but I have it stopped. It installed with VS 2005...don't think it really factors into the equation here though...
so given the new error message, does that give us any more direction?
jk
The way to schedule backups in SQL Express is to use the Windows Scheduler. Have it call a cmd file.
That cmd file should contain following T-SQL syntax to back up your database:
suppose my database is test_db then
EXEC sp_addumpdevice 'disk', 'De_test_db', 'c:\test_db.bak'
BACKUP DATABASE TEST_DB TO De_test_db
That cmd file should contain following T-SQL syntax to back up your database:
suppose my database is test_db then
EXEC sp_addumpdevice 'disk', 'De_test_db', 'c:\test_db.bak'
BACKUP DATABASE TEST_DB TO De_test_db
Please ignore my last comment. It was done by mistake.
check the following
1. Does user mt_master have access on database MT_Calc on server D9150
2. For SQL 2000 , On your sql server go to sql network configuation and check if tcp \ip is enables
3. For SQL 2005 , On your sql server go to sql Server configuation Manager and check if tcp \ip is enables for network and for client
4. on your workstation from where you are unable to connect sql server check the preferd DNS name if it is correct.
Note: for option 2 and 3 go to progrm file microsoft sql server 2000/2005
1. Does user mt_master have access on database MT_Calc on server D9150
2. For SQL 2000 , On your sql server go to sql network configuation and check if tcp \ip is enables
3. For SQL 2005 , On your sql server go to sql Server configuation Manager and check if tcp \ip is enables for network and for client
4. on your workstation from where you are unable to connect sql server check the preferd DNS name if it is correct.
Note: for option 2 and 3 go to progrm file microsoft sql server 2000/2005
ASKER
imran...
1. Yes
2. Yes
3. Yes, but I am not using SQL Express for anything...
4. SQL server is loaded on my local workstation
Thanks,
jk
1. Yes
2. Yes
3. Yes, but I am not using SQL Express for anything...
4. SQL server is loaded on my local workstation
Thanks,
jk
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
that seemed to do the trick...thanks!
>> is this a DSN??...
if u meant local server ...it shud be "(local)"