Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
idsqlserver
Starting Member
1 Post |
 Posted - 2005-10-11 : 11:09:30
|
| All,We are facing a very peculiar problem..We had SQL Server installed in one of the machines.. It was working properly i.e. we were able to open query analyzer (QA), enterprise manager (EM) and also through ODBC connection from ASP programs and we also used to access from other machines.. But today suddenly we were not abl;e to access from other machines in the network although we were able access the DB from the local machine (QA, EM, ASP).. So we decided to uninstall SQL Server and reinstall.. But after reinstalling we are only able to access the database through QA and EM and not from ASP through ODBC.. It says script timed out.. ANother question..How to restore database from MDF file (not the database backupfile)..Any help..Thanks and Regards,IDSQLSERVER |
|
|
SreenivasBora
Posting Yak Master
164 Posts |
Posted - 2005-10-11 : 12:03:30
|
| Reinstalling the sql server is not the solution for checking the accessibility.If you have MDF and LDF files then use sp_attach_db to recreate the database. But your user is members of the sysadmin and dbcreator fixed server roles.With RegardsBSR |
 |
|
|
AjarnMark
SQL Slashing Gunting Master
3246 Posts |
Posted - 2005-10-11 : 13:16:46
|
| And for your original problem, I would go hunt down the network admin and ask if he modified any firewalls, perhaps blocking the port that SQL Server uses (1433 by default, but can be changed). If he says NO, then I'd ask him to monitor the network traffic while you attempt to connect again.Can you connect to the server from QA or EM on a different machine? Is the database set to auto-close and it's just taking too darn long to reopen when you are trying to connect? I never use that option myself.---------------------------EmeraldCityDomains.com |
|
|
|
eyechart
Master Smack Fu Yak Hacker
3575 Posts |
Posted - 2005-10-11 : 13:35:21
|
| also, check to see if UDP port 1434 is blocked. This is pretty common these days. If this port is blocked, then you will definitely not be able to connect without providing a port number - even if you are using the default port of 1433 for your SQL Server. This can be done easily enough by creating an alias using the client configuration tool.Anyway, before we get into a discussion of how to do this, check with your admins to see what ports are blocked at your firewall.-ec |
|
|
|
|
|
|
|
|
Unable to access SQL Server 2000 from ASP