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 |
|
AskSQLTeam
Ask SQLTeam Question
0 Posts |
 Posted - 2005-04-15 : 08:00:42
|
| Naga Kiran writes "HiI am working as a DotNet programmer.My system was migrated from windows 2000 to Windows2003Earlier I was able to connect my database using following connection string...."provider=sqloledb;server=<ServerName>;uid=<username>;pwd=<password>;database=<databaseName>"After migrating to windows2003+IIS6.0 I could not connect to SQL Server through code.how can I resolve this problem?Please help me in doing so..Thanks in advanceregardsNagaKiran" |
|
|
robvolk
Most Valuable Yak
15732 Posts |
Posted - 2005-04-15 : 08:02:13
|
| The first thing you should check is whether Win2K3 is blocking ports 1433 and/or 1434, or whichever port you're using to connect to SQL Server. |
 |
|
|
derrickleggett
Pointy Haired Yak DBA
4184 Posts |
Posted - 2005-04-15 : 08:11:38
|
| What error are you getting? Are the we applications and SQL Server on the same machine? Go to the Server Network Utility under Microsoft SQL Server and make sure you have a network protocol enabled. Make sure you can ping the box SQL Server is on from the box with IIS. If that doesn't work, go into the box with SQL Server and under Component Services change the DTS settings to allow "Network Clients". See if that works.Windows 2003 changes quite a bit of security features, so it's not surprising to have issues if you haven't tested.MeanOldDBAderrickleggett@hotmail.comWhen life gives you a lemon, fire the DBA. |
|
|
|
steamngn
Constraint Violating Yak Guru
306 Posts |
Posted - 2005-04-15 : 21:16:45
|
| You may also have an issue with IIS 6.0 and the lockdown utility that goes with Win2003. Here is the download site if you need it:[url]http://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=DDE9EFC0-BB30-47EB-9A61-FD755D23CDEC[/url]There's never enough time to type code right, but always enough time for a hotfix... |
|
|
|
|
|
|
couldnot connect to SQL Server database