ullenulle
asked on
Windows server with SQL Server and connection issue to database
Hi there.
I moved a web database app from a standard webhotel with classic asp and MySQL to a dedicated Microsoft server with SQL Server. There is a login page that check the user credentials in a database table in order to proceed. That used to work fine on the standard webhotel.
Now it won't work. I created a user that works fine in SQL Server Management. I used a standard connection string and included it in the login page. The page loads fine, but then the user credentials is submitted, then I just gives a blank page. Nothing to see in F12. I suspect that there may be an issue with some port permissions.
Anyone out there who knows what port that should be open and how to open it? Any other suggestion to solve this problem?
Best regards
Ulrich
I moved a web database app from a standard webhotel with classic asp and MySQL to a dedicated Microsoft server with SQL Server. There is a login page that check the user credentials in a database table in order to proceed. That used to work fine on the standard webhotel.
Now it won't work. I created a user that works fine in SQL Server Management. I used a standard connection string and included it in the login page. The page loads fine, but then the user credentials is submitted, then I just gives a blank page. Nothing to see in F12. I suspect that there may be an issue with some port permissions.
Anyone out there who knows what port that should be open and how to open it? Any other suggestion to solve this problem?
Best regards
Ulrich
Can you post the connection string that you're using?
ASKER
Sure:
"Driver={SQL Server};Server=servername\ SQLEXPRESS ;Database= databasena me;Uid=use rname;Pwd= password"
"Driver={SQL Server};Server=servername\
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
You are an angel!!! :-)))))))) I found that connection string in the server settings that said "servername\SQLEXPRESS"... Now I erased \SQLEXPRESS and BINGO! It works!!! YEEEEEEESSSS!!! Thank you thank you!!! :-)))))
ASKER
You saved my life! ;-)
Why did you use the SQLEXPRESS in the first place?