|
|
You're in the
sql server connect
group:ver 2000 vs 2005
sql server connect:
Hi all,
I just installed version 2005, and it is co-existing with an instance of 2000. I am trying to test the connection string fro an ASP ..Net page which works fine already in 2000. However it does not work in 2005. In 2005, I went to configuration Manager/Protocols/TCP IP, and entered 1433 as the port in IP1, IP2, and IP3 Then, in my connection string I just changes the databasename to point to 'AdventureWorks' instead of the DB that I used for 2K. The connection could not be openned. I also configured the user id, and password the same way as I have in 2K, and re-started the engine. At this point I do not know what else should I do. Any help will be appreciated. Thanks in advance, Carlos
You can not have both instances using port 1433. The default instance which
in your case is most likely the 2000 instance will have 1433. The named instance (2005) will use a port other than 1433. Do not make them both 1433. -- Andrew J. Kelly SQL MVP [quoted text, click to view] "Carlos" <chsanin@earthlink.net> wrote in message news:uXRaTpo4FHA.2524@TK2MSFTNGP10.phx.gbl... > Hi all, > > I just installed version 2005, and it is co-existing with > an instance of 2000. I am trying to test the connection string fro an ASP > .Net page which works fine already in > 2000. However it does not work in 2005. > In 2005, I went to configuration Manager/Protocols/TCP IP, and entered > 1433 as the port in IP1, IP2, and IP3 > Then, in my connection string I just changes the databasename to point to > 'AdventureWorks' instead of > the DB that I used for 2K. The connection could not be openned. I also > configured the user id, and password the same way as I have in 2K, and > re-started the engine. > > At this point I do not know what else should I do. > > Any help will be appreciated. > > Thanks in advance, > > Carlos >
Hi Andrew,
thank you for your prompt reply. I did assign a different port for the named instance in 2005. I am trying to use a connection string that already works in 2K by just changing to an already provided database, and including the named instance, and port number in the connection string. This is kind of how it looks like: this.sqlConnection1.ConnectionString = "Server=xxx.xx.xx.xx\\<myNamedServerInstance>,<port>;Database=AdventureWorks;User ID=myUID;Password=myPWD;Trusted_Connection=True"; I am still no able to at least open the connection.. Any help is appreciated. Thanks in advance. Carlos. [quoted text, click to view] "Andrew J. Kelly" <sqlmvpnooospam@shadhawk.com> wrote in message news:%23hUsMqv4FHA.2548@TK2MSFTNGP10.phx.gbl... > You can not have both instances using port 1433. The default instance > which in your case is most likely the 2000 instance will have 1433. The > named instance (2005) will use a port other than 1433. Do not make them > both 1433. > > -- > Andrew J. Kelly SQL MVP > > > "Carlos" <chsanin@earthlink.net> wrote in message > news:uXRaTpo4FHA.2524@TK2MSFTNGP10.phx.gbl... >> Hi all, >> >> I just installed version 2005, and it is co-existing with >> an instance of 2000. I am trying to test the connection string fro an ASP >> .Net page which works fine already in >> 2000. However it does not work in 2005. >> In 2005, I went to configuration Manager/Protocols/TCP IP, and entered >> 1433 as the port in IP1, IP2, and IP3 >> Then, in my connection string I just changes the databasename to point to >> 'AdventureWorks' instead of >> the DB that I used for 2K. The connection could not be openned. I also >> configured the user id, and password the same way as I have in 2K, and >> re-started the engine. >> >> At this point I do not know what else should I do. >> >> Any help will be appreciated. >> >> Thanks in advance, >> >> Carlos >> > >
Did you change the port on the default (2000) instance to something other
than 1433? -- Andrew J. Kelly SQL MVP [quoted text, click to view] "Carlos" <ch_sanin@yahoo.com> wrote in message news:%23KntJk64FHA.2092@TK2MSFTNGP12.phx.gbl... > Hi Andrew, > > thank you for your prompt reply. I did assign a different port for the > named instance in 2005. I am trying to use a connection string that > already > works in 2K by just changing to an already provided database, and > including the named instance, and port number in the connection string. > This is kind of how it looks like: > > this.sqlConnection1.ConnectionString = > "Server=xxx.xx.xx.xx\\<myNamedServerInstance>,<port>;Database=AdventureWorks;User > ID=myUID;Password=myPWD;Trusted_Connection=True"; > > I am still no able to at least open the connection.. Any help is > appreciated. > Thanks in advance. > > Carlos. > > > "Andrew J. Kelly" <sqlmvpnooospam@shadhawk.com> wrote in message > news:%23hUsMqv4FHA.2548@TK2MSFTNGP10.phx.gbl... >> You can not have both instances using port 1433. The default instance >> which in your case is most likely the 2000 instance will have 1433. The >> named instance (2005) will use a port other than 1433. Do not make them >> both 1433. >> >> -- >> Andrew J. Kelly SQL MVP >> >> >> "Carlos" <chsanin@earthlink.net> wrote in message >> news:uXRaTpo4FHA.2524@TK2MSFTNGP10.phx.gbl... >>> Hi all, >>> >>> I just installed version 2005, and it is co-existing with >>> an instance of 2000. I am trying to test the connection string fro an >>> ASP .Net page which works fine already in >>> 2000. However it does not work in 2005. >>> In 2005, I went to configuration Manager/Protocols/TCP IP, and entered >>> 1433 as the port in IP1, IP2, and IP3 >>> Then, in my connection string I just changes the databasename to point >>> to 'AdventureWorks' instead of >>> the DB that I used for 2K. The connection could not be openned. I also >>> configured the user id, and password the same way as I have in 2K, and >>> re-started the engine. >>> >>> At this point I do not know what else should I do. >>> >>> Any help will be appreciated. >>> >>> Thanks in advance, >>> >>> Carlos >>> >> >> > >
No I did not. In reality I am trying to connect to one instace at any given
time since I have the connection strings next to each other, I comment out the line that I do not wish to test, and uncomment the connection string for 2005. Kind of like this: //connection string for SQLSrvr2000 //this.sqlConnection1.ConnectionString = "Server=xxx.xx.xx.xx;Database=myDB;User ID=myUID;Password=myPWD;Trusted_Connection=False"; //connection string for SQLSrvr2005 this.sqlConnection1.ConnectionString = "Server=xxx.xx.xx.xx\\<myNamedServerInstance>,<port>;Database=AdventureWorks;User ID=myUID;Password=myPWD;Trusted_Connection=True"; Thanks again for your help. Carlos [quoted text, click to view] "Andrew J. Kelly" <sqlmvpnooospam@shadhawk.com> wrote in message news:e0Pj$%2364FHA.2888@tk2msftngp13.phx.gbl... > Did you change the port on the default (2000) instance to something other > than 1433? > > -- > Andrew J. Kelly SQL MVP > > > "Carlos" <ch_sanin@yahoo.com> wrote in message > news:%23KntJk64FHA.2092@TK2MSFTNGP12.phx.gbl... >> Hi Andrew, >> >> thank you for your prompt reply. I did assign a different port for the >> named instance in 2005. I am trying to use a connection string that >> already >> works in 2K by just changing to an already provided database, and >> including the named instance, and port number in the connection string. >> This is kind of how it looks like: >> >> this.sqlConnection1.ConnectionString = >> "Server=xxx.xx.xx.xx\\<myNamedServerInstance>,<port>;Database=AdventureWorks;User >> ID=myUID;Password=myPWD;Trusted_Connection=True"; >> >> I am still no able to at least open the connection.. Any help is >> appreciated. >> Thanks in advance. >> >> Carlos. >> >> >> "Andrew J. Kelly" <sqlmvpnooospam@shadhawk.com> wrote in message >> news:%23hUsMqv4FHA.2548@TK2MSFTNGP10.phx.gbl... >>> You can not have both instances using port 1433. The default instance >>> which in your case is most likely the 2000 instance will have 1433. The >>> named instance (2005) will use a port other than 1433. Do not make them >>> both 1433. >>> >>> -- >>> Andrew J. Kelly SQL MVP >>> >>> >>> "Carlos" <chsanin@earthlink.net> wrote in message >>> news:uXRaTpo4FHA.2524@TK2MSFTNGP10.phx.gbl... >>>> Hi all, >>>> >>>> I just installed version 2005, and it is co-existing with >>>> an instance of 2000. I am trying to test the connection string fro an >>>> ASP .Net page which works fine already in >>>> 2000. However it does not work in 2005. >>>> In 2005, I went to configuration Manager/Protocols/TCP IP, and entered >>>> 1433 as the port in IP1, IP2, and IP3 >>>> Then, in my connection string I just changes the databasename to point >>>> to 'AdventureWorks' instead of >>>> the DB that I used for 2K. The connection could not be openned. I also >>>> configured the user id, and password the same way as I have in 2K, and >>>> re-started the engine. >>>> >>>> At this point I do not know what else should I do. >>>> >>>> Any help will be appreciated. >>>> >>>> Thanks in advance, >>>> >>>> Carlos >>>> >>> >>> >> >> > >
Well if you don't change the default instance they will both be listening on
1433 and who knows what you will get. You can't have two SQL Server instances on the same server with the same port number. -- Andrew J. Kelly SQL MVP [quoted text, click to view] "Carlos" <ch_sanin@yahoo.com> wrote in message news:uIbBdK74FHA.2092@TK2MSFTNGP12.phx.gbl... > No I did not. In reality I am trying to connect to one instace at any > given time > since I have the connection strings next to each other, I comment out the > line that I do not wish to test, and uncomment the connection string > for 2005. Kind of like this: > > //connection string for SQLSrvr2000 > //this.sqlConnection1.ConnectionString = > "Server=xxx.xx.xx.xx;Database=myDB;User > ID=myUID;Password=myPWD;Trusted_Connection=False"; > > //connection string for SQLSrvr2005 > this.sqlConnection1.ConnectionString = > "Server=xxx.xx.xx.xx\\<myNamedServerInstance>,<port>;Database=AdventureWorks;User > ID=myUID;Password=myPWD;Trusted_Connection=True"; > > > Thanks again for your help. > > Carlos > > "Andrew J. Kelly" <sqlmvpnooospam@shadhawk.com> wrote in message > news:e0Pj$%2364FHA.2888@tk2msftngp13.phx.gbl... >> Did you change the port on the default (2000) instance to something other >> than 1433? >> >> -- >> Andrew J. Kelly SQL MVP >> >> >> "Carlos" <ch_sanin@yahoo.com> wrote in message >> news:%23KntJk64FHA.2092@TK2MSFTNGP12.phx.gbl... >>> Hi Andrew, >>> >>> thank you for your prompt reply. I did assign a different port for the >>> named instance in 2005. I am trying to use a connection string that >>> already >>> works in 2K by just changing to an already provided database, and >>> including the named instance, and port number in the connection string. >>> This is kind of how it looks like: >>> >>> this.sqlConnection1.ConnectionString = >>> "Server=xxx.xx.xx.xx\\<myNamedServerInstance>,<port>;Database=AdventureWorks;User >>> ID=myUID;Password=myPWD;Trusted_Connection=True"; >>> >>> I am still no able to at least open the connection.. Any help is >>> appreciated. >>> Thanks in advance. >>> >>> Carlos. >>> >>> >>> "Andrew J. Kelly" <sqlmvpnooospam@shadhawk.com> wrote in message >>> news:%23hUsMqv4FHA.2548@TK2MSFTNGP10.phx.gbl... >>>> You can not have both instances using port 1433. The default instance >>>> which in your case is most likely the 2000 instance will have 1433. >>>> The named instance (2005) will use a port other than 1433. Do not make >>>> them both 1433. >>>> >>>> -- >>>> Andrew J. Kelly SQL MVP >>>> >>>> >>>> "Carlos" <chsanin@earthlink.net> wrote in message >>>> news:uXRaTpo4FHA.2524@TK2MSFTNGP10.phx.gbl... >>>>> Hi all, >>>>> >>>>> I just installed version 2005, and it is co-existing with >>>>> an instance of 2000. I am trying to test the connection string fro an >>>>> ASP .Net page which works fine already in >>>>> 2000. However it does not work in 2005. >>>>> In 2005, I went to configuration Manager/Protocols/TCP IP, and entered >>>>> 1433 as the port in IP1, IP2, and IP3 >>>>> Then, in my connection string I just changes the databasename to point >>>>> to 'AdventureWorks' instead of >>>>> the DB that I used for 2K. The connection could not be openned. I also >>>>> configured the user id, and password the same way as I have in 2K, and >>>>> re-started the engine. >>>>> >>>>> At this point I do not know what else should I do. >>>>> >>>>> Any help will be appreciated. >>>>> >>>>> Thanks in advance, >>>>> >>>>> Carlos >>>>> >>>> >>>> >>> >>> >> >> > >
Hi again Andrew,
I am sorry but you probably misunderstood me. In my firewall I already have 1433 for the default instance, so I defined a different (new) port number for the named instance.in the 2005 configuration manager, and the firewall (say 2534). So that is why I said that I did not changed it in my default. That way I left the default port number configuration for the default instance, and configured a new port to listen for the named instance. If you see my connection string you will notice it. I followed the books online, and I believe that I am doing whatever is described there. However, it seems that I am still missing something to successfully open the connection, and I do not know how to troubleshoot it effectively. Thanks again. Carlos. [quoted text, click to view] "Andrew J. Kelly" <sqlmvpnooospam@shadhawk.com> wrote in message news:elZuDv74FHA.3876@TK2MSFTNGP09.phx.gbl... > Well if you don't change the default instance they will both be listening > on 1433 and who knows what you will get. You can't have two SQL Server > instances on the same server with the same port number. > > -- > Andrew J. Kelly SQL MVP > > > "Carlos" <ch_sanin@yahoo.com> wrote in message > news:uIbBdK74FHA.2092@TK2MSFTNGP12.phx.gbl... >> No I did not. In reality I am trying to connect to one instace at any >> given time >> since I have the connection strings next to each other, I comment out the >> line that I do not wish to test, and uncomment the connection string >> for 2005. Kind of like this: >> >> //connection string for SQLSrvr2000 >> //this.sqlConnection1.ConnectionString = >> "Server=xxx.xx.xx.xx;Database=myDB;User >> ID=myUID;Password=myPWD;Trusted_Connection=False"; >> >> //connection string for SQLSrvr2005 >> this.sqlConnection1.ConnectionString = >> "Server=xxx.xx.xx.xx\\<myNamedServerInstance>,<port>;Database=AdventureWorks;User >> ID=myUID;Password=myPWD;Trusted_Connection=True"; >> >> >> Thanks again for your help. >> >> Carlos >> >> "Andrew J. Kelly" <sqlmvpnooospam@shadhawk.com> wrote in message >> news:e0Pj$%2364FHA.2888@tk2msftngp13.phx.gbl... >>> Did you change the port on the default (2000) instance to something >>> other than 1433? >>> >>> -- >>> Andrew J. Kelly SQL MVP >>> >>> >>> "Carlos" <ch_sanin@yahoo.com> wrote in message >>> news:%23KntJk64FHA.2092@TK2MSFTNGP12.phx.gbl... >>>> Hi Andrew, >>>> >>>> thank you for your prompt reply. I did assign a different port for the >>>> named instance in 2005. I am trying to use a connection string that >>>> already >>>> works in 2K by just changing to an already provided database, and >>>> including the named instance, and port number in the connection string. >>>> This is kind of how it looks like: >>>> >>>> this.sqlConnection1.ConnectionString = >>>> "Server=xxx.xx.xx.xx\\<myNamedServerInstance>,<port>;Database=AdventureWorks;User >>>> ID=myUID;Password=myPWD;Trusted_Connection=True"; >>>> >>>> I am still no able to at least open the connection.. Any help is >>>> appreciated. >>>> Thanks in advance. >>>> >>>> Carlos. >>>> >>>> >>>> "Andrew J. Kelly" <sqlmvpnooospam@shadhawk.com> wrote in message >>>> news:%23hUsMqv4FHA.2548@TK2MSFTNGP10.phx.gbl... >>>>> You can not have both instances using port 1433. The default instance >>>>> which in your case is most likely the 2000 instance will have 1433. >>>>> The named instance (2005) will use a port other than 1433. Do not >>>>> make them both 1433. >>>>> >>>>> -- >>>>> Andrew J. Kelly SQL MVP >>>>> >>>>> >>>>> "Carlos" <chsanin@earthlink.net> wrote in message >>>>> news:uXRaTpo4FHA.2524@TK2MSFTNGP10.phx.gbl... >>>>>> Hi all, >>>>>> >>>>>> I just installed version 2005, and it is co-existing with >>>>>> an instance of 2000. I am trying to test the connection string fro an >>>>>> ASP .Net page which works fine already in >>>>>> 2000. However it does not work in 2005. >>>>>> In 2005, I went to configuration Manager/Protocols/TCP IP, and >>>>>> entered 1433 as the port in IP1, IP2, and IP3 >>>>>> Then, in my connection string I just changes the databasename to >>>>>> point to 'AdventureWorks' instead of >>>>>> the DB that I used for 2K. The connection could not be openned. I >>>>>> also configured the user id, and password the same way as I have in >>>>>> 2K, and re-started the engine. >>>>>> >>>>>> At this point I do not know what else should I do. >>>>>> >>>>>> Any help will be appreciated. >>>>>> >>>>>> Thanks in advance, >>>>>> >>>>>> Carlos >>>>>> >>>>> >>>>> >>>> >>>> >>> >>> >> >> > >
In your original post you had this:
[quoted text, click to view] >>In 2005, I went to configuration Manager/Protocols/TCP IP, and entered >>1433 as the port in IP1, IP2, and IP3 That led me to believe you had in fact attempted to use 1433 for the 2005 instance. In any case I don't believe you need to specify the instance name if you are going to specify the port and an ip address. [quoted text, click to view] >>> this.sqlConnection1.ConnectionString = "Server=xxx.xx.xx.xx,2444 >>> ;Database=AdventureWorks;User >>> ID=myUID;Password=myPWD;Trusted_Connection=True"; http://www.connectionstrings.com/ -- Andrew J. Kelly SQL MVP [quoted text, click to view] "Carlos" <chsanin@earthlink.net> wrote in message news:e2lgJD84FHA.744@TK2MSFTNGP10.phx.gbl... > Hi again Andrew, > > I am sorry but you probably misunderstood me. In my firewall I already > have 1433 for the default instance, so > I defined a different (new) port number for the named > instance.in the 2005 configuration manager, and the firewall (say 2534). > So that is why I said that I did not changed it in my default. That way I > left the default port number configuration for the default instance, and > configured a new port to listen for the named instance. If you see my > connection string you will notice it. I followed the books online, and I > believe that I am doing whatever is described there. However, it seems > that I am still > missing something to successfully open the connection, and I do not know > how to troubleshoot it effectively. > > Thanks again. > > Carlos. > > "Andrew J. Kelly" <sqlmvpnooospam@shadhawk.com> wrote in message > news:elZuDv74FHA.3876@TK2MSFTNGP09.phx.gbl... >> Well if you don't change the default instance they will both be listening >> on 1433 and who knows what you will get. You can't have two SQL Server >> instances on the same server with the same port number. >> >> -- >> Andrew J. Kelly SQL MVP >> >> >> "Carlos" <ch_sanin@yahoo.com> wrote in message >> news:uIbBdK74FHA.2092@TK2MSFTNGP12.phx.gbl... >>> No I did not. In reality I am trying to connect to one instace at any >>> given time >>> since I have the connection strings next to each other, I comment out >>> the >>> line that I do not wish to test, and uncomment the connection string >>> for 2005. Kind of like this: >>> >>> //connection string for SQLSrvr2000 >>> //this.sqlConnection1.ConnectionString = >>> "Server=xxx.xx.xx.xx;Database=myDB;User >>> ID=myUID;Password=myPWD;Trusted_Connection=False"; >>> >>> //connection string for SQLSrvr2005 >>> this.sqlConnection1.ConnectionString = >>> "Server=xxx.xx.xx.xx\\<myNamedServerInstance>,<port>;Database=AdventureWorks;User >>> ID=myUID;Password=myPWD;Trusted_Connection=True"; >>> >>> >>> Thanks again for your help. >>> >>> Carlos >>> >>> "Andrew J. Kelly" <sqlmvpnooospam@shadhawk.com> wrote in message >>> news:e0Pj$%2364FHA.2888@tk2msftngp13.phx.gbl... >>>> Did you change the port on the default (2000) instance to something >>>> other than 1433? >>>> >>>> -- >>>> Andrew J. Kelly SQL MVP >>>> >>>> >>>> "Carlos" <ch_sanin@yahoo.com> wrote in message >>>> news:%23KntJk64FHA.2092@TK2MSFTNGP12.phx.gbl... >>>>> Hi Andrew, >>>>> >>>>> thank you for your prompt reply. I did assign a different port for the >>>>> named instance in 2005. I am trying to use a connection string that >>>>> already >>>>> works in 2K by just changing to an already provided database, and >>>>> including the named instance, and port number in the connection >>>>> string. >>>>> This is kind of how it looks like: >>>>> >>>>> this.sqlConnection1.ConnectionString = >>>>> "Server=xxx.xx.xx.xx\\<myNamedServerInstance>,<port>;Database=AdventureWorks;User >>>>> ID=myUID;Password=myPWD;Trusted_Connection=True"; >>>>> >>>>> I am still no able to at least open the connection.. Any help is >>>>> appreciated. >>>>> Thanks in advance. >>>>> >>>>> Carlos. >>>>> >>>>> >>>>> "Andrew J. Kelly" <sqlmvpnooospam@shadhawk.com> wrote in message >>>>> news:%23hUsMqv4FHA.2548@TK2MSFTNGP10.phx.gbl... >>>>>> You can not have both instances using port 1433. The default >>>>>> instance which in your case is most likely the 2000 instance will >>>>>> have 1433. The named instance (2005) will use a port other than 1433. >>>>>> Do not make them both 1433. >>>>>> >>>>>> -- >>>>>> Andrew J. Kelly SQL MVP >>>>>> >>>>>> >>>>>> "Carlos" <chsanin@earthlink.net> wrote in message >>>>>> news:uXRaTpo4FHA.2524@TK2MSFTNGP10.phx.gbl... >>>>>>> Hi all, >>>>>>> >>>>>>> I just installed version 2005, and it is co-existing with >>>>>>> an instance of 2000. I am trying to test the connection string fro >>>>>>> an ASP .Net page which works fine already in >>>>>>> 2000. However it does not work in 2005. >>>>>>> In 2005, I went to configuration Manager/Protocols/TCP IP, and >>>>>>> entered 1433 as the port in IP1, IP2, and IP3 >>>>>>> Then, in my connection string I just changes the databasename to >>>>>>> point to 'AdventureWorks' instead of >>>>>>> the DB that I used for 2K. The connection could not be openned. I >>>>>>> also configured the user id, and password the same way as I have in >>>>>>> 2K, and re-started the engine. >>>>>>> >>>>>>> At this point I do not know what else should I do. >>>>>>> >>>>>>> Any help will be appreciated. >>>>>>> >>>>>>> Thanks in advance, >>>>>>> >>>>>>> Carlos >>>>>>> >>>>>> >>>>>> >>>>> >>>>> >>>> >>>> >>> >>> >> >> > >
Hi again Andrew, thanks again for your help. For the record, I was finally able to connect to the remote SQL server 2005. Unfortunately, I believe that books online does not describe that you can assign a default port for your instance when clicking the TCP properties in the network configuration. Apparently you need to define your port there too. I did not test removing the port definition from within the IP addresses dialog box, and leaving the default port. In any case it was some kind of painful learning experience. Carlos. [quoted text, click to view] "Andrew J. Kelly" <sqlmvpnooospam@shadhawk.com> wrote in message news:OJ4ewmH5FHA.444@TK2MSFTNGP11.phx.gbl... > In your original post you had this: > >>>In 2005, I went to configuration Manager/Protocols/TCP IP, and entered >>>1433 as the port in IP1, IP2, and IP3 > > That led me to believe you had in fact attempted to use 1433 for the 2005 > instance. In any case I don't believe you need to specify the instance > name if you are going to specify the port and an ip address. > >>>> this.sqlConnection1.ConnectionString = "Server=xxx.xx.xx.xx,2444 >>>> ;Database=AdventureWorks;User >>>> ID=myUID;Password=myPWD;Trusted_Connection=True"; > > http://www.connectionstrings.com/ > > > > -- > Andrew J. Kelly SQL MVP > > > "Carlos" <chsanin@earthlink.net> wrote in message > news:e2lgJD84FHA.744@TK2MSFTNGP10.phx.gbl... >> Hi again Andrew, >> >> I am sorry but you probably misunderstood me. In my firewall I already >> have 1433 for the default instance, so >> I defined a different (new) port number for the named >> instance.in the 2005 configuration manager, and the firewall (say 2534). >> So that is why I said that I did not changed it in my default. That way I >> left the default port number configuration for the default instance, and >> configured a new port to listen for the named instance. If you see my >> connection string you will notice it. I followed the books online, and I >> believe that I am doing whatever is described there. However, it seems >> that I am still >> missing something to successfully open the connection, and I do not know >> how to troubleshoot it effectively. >> >> Thanks again. >> >> Carlos. >> >> "Andrew J. Kelly" <sqlmvpnooospam@shadhawk.com> wrote in message >> news:elZuDv74FHA.3876@TK2MSFTNGP09.phx.gbl... >>> Well if you don't change the default instance they will both be >>> listening on 1433 and who knows what you will get. You can't have two >>> SQL Server instances on the same server with the same port number. >>> >>> -- >>> Andrew J. Kelly SQL MVP >>> >>> >>> "Carlos" <ch_sanin@yahoo.com> wrote in message >>> news:uIbBdK74FHA.2092@TK2MSFTNGP12.phx.gbl... >>>> No I did not. In reality I am trying to connect to one instace at any >>>> given time >>>> since I have the connection strings next to each other, I comment out >>>> the >>>> line that I do not wish to test, and uncomment the connection string >>>> for 2005. Kind of like this: >>>> >>>> //connection string for SQLSrvr2000 >>>> //this.sqlConnection1.ConnectionString = >>>> "Server=xxx.xx.xx.xx;Database=myDB;User >>>> ID=myUID;Password=myPWD;Trusted_Connection=False"; >>>> >>>> //connection string for SQLSrvr2005 >>>> this.sqlConnection1.ConnectionString = >>>> "Server=xxx.xx.xx.xx\\<myNamedServerInstance>,<port>;Database=AdventureWorks;User >>>> ID=myUID;Password=myPWD;Trusted_Connection=True"; >>>> >>>> >>>> Thanks again for your help. >>>> >>>> Carlos >>>> >>>> "Andrew J. Kelly" <sqlmvpnooospam@shadhawk.com> wrote in message >>>> news:e0Pj$%2364FHA.2888@tk2msftngp13.phx.gbl... >>>>> Did you change the port on the default (2000) instance to something >>>>> other than 1433? >>>>> >>>>> -- >>>>> Andrew J. Kelly SQL MVP >>>>> >>>>> >>>>> "Carlos" <ch_sanin@yahoo.com> wrote in message >>>>> news:%23KntJk64FHA.2092@TK2MSFTNGP12.phx.gbl... >>>>>> Hi Andrew, >>>>>> >>>>>> thank you for your prompt reply. I did assign a different port for >>>>>> the >>>>>> named instance in 2005. I am trying to use a connection string that >>>>>> already >>>>>> works in 2K by just changing to an already provided database, and >>>>>> including the named instance, and port number in the connection >>>>>> string. >>>>>> This is kind of how it looks like: >>>>>> >>>>>> this.sqlConnection1.ConnectionString = >>>>>> "Server=xxx.xx.xx.xx\\<myNamedServerInstance>,<port>;Database=AdventureWorks;User >>>>>> ID=myUID;Password=myPWD;Trusted_Connection=True"; >>>>>> >>>>>> I am still no able to at least open the connection.. Any help is >>>>>> appreciated. >>>>>> Thanks in advance. >>>>>> >>>>>> Carlos. >>>>>> >>>>>> >>>>>> "Andrew J. Kelly" <sqlmvpnooospam@shadhawk.com> wrote in message >>>>>> news:%23hUsMqv4FHA.2548@TK2MSFTNGP10.phx.gbl... >>>>>>> You can not have both instances using port 1433. The default >>>>>>> instance which in your case is most likely the 2000 instance will >>>>>>> have 1433. The named instance (2005) will use a port other than >>>>>>> 1433. Do not make them both 1433. >>>>>>> >>>>>>> -- >>>>>>> Andrew J. Kelly SQL MVP >>>>>>> >>>>>>> >>>>>>> "Carlos" <chsanin@earthlink.net> wrote in message >>>>>>> news:uXRaTpo4FHA.2524@TK2MSFTNGP10.phx.gbl... >>>>>>>> Hi all, >>>>>>>> >>>>>>>> I just installed version 2005, and it is co-existing with >>>>>>>> an instance of 2000. I am trying to test the connection string fro >>>>>>>> an ASP .Net page which works fine already in >>>>>>>> 2000. However it does not work in 2005. >>>>>>>> In 2005, I went to configuration Manager/Protocols/TCP IP, and >>>>>>>> entered 1433 as the port in IP1, IP2, and IP3 >>>>>>>> Then, in my connection string I just changes the databasename to >>>>>>>> point to 'AdventureWorks' instead of >>>>>>>> the DB that I used for 2K. The connection could not be openned. I >>>>>>>> also configured the user id, and password the same way as I have in >>>>>>>> 2K, and re-started the engine. >>>>>>>> >>>>>>>> At this point I do not know what else should I do. >>>>>>>> >>>>>>>> Any help will be appreciated. >>>>>>>> >>>>>>>> Thanks in advance, >>>>>>>> >>>>>>>> Carlos >>>>>>>> >>>>>>> >>>>>>> >>>>>> >>>>>> >>>>> >>>>> >>>> >>>> >>> >>> >> >> > >
Don't see what you're looking for? Try a search.
|
June 2003
July 2003
August 2003
September 2003
October 2003
November 2003
December 2003
January 2004
February 2004
March 2004
April 2004
May 2004
June 2004
July 2004
August 2004
September 2004
October 2004
November 2004
December 2004
January 2005
February 2005
March 2005
April 2005
May 2005
June 2005
July 2005
August 2005
September 2005
October 2005
November 2005
December 2005
January 2006
February 2006
March 2006
April 2006
May 2006
June 2006
July 2006
August 2006
September 2006
October 2006
November 2006
December 2006
January 2007
February 2007
March 2007
April 2007
May 2007
June 2007
July 2007
August 2007
September 2007
October 2007
November 2007
| home · blog · groups | Questions? Comments? Contact the dn |