473,883 Members | 1,604 Online
Bytes | Software Development & Data Engineering Community
+ Post

Home Posts Topics Members FAQ

Any help here???

Have Visual Studio.NET installed on MS 2000 Professional OS laptop. No issue
ever with web development and SQL connections.
Purchased new laptop with XP Professional SP2!!!!!!!! & Visual Studio.NET
installed.
Nothing but headaches. Continually getting
System.Data.Sql Client.SqlExcep tion : Timeout expired message - The timeout
period elapsed prior to completion of the operation or the server is not
responding.
Can anyone help with this??? Why error's with LATER versions of your
software?
Nov 19 '05 #1
15 2112
TJS
seems like the sql server is not responding,. doesn't seem like it has
anything to do with the OS.

Check to make sure SQL server is running and name of the server is same as
in connection code
"DavidS" <Da****@discuss ions.microsoft. com> wrote in message
news:A1******** *************** ***********@mic rosoft.com...
Have Visual Studio.NET installed on MS 2000 Professional OS laptop. No
issue
ever with web development and SQL connections.
Purchased new laptop with XP Professional SP2!!!!!!!! & Visual Studio.NET
installed.
Nothing but headaches. Continually getting
System.Data.Sql Client.SqlExcep tion : Timeout expired message - The timeout
period elapsed prior to completion of the operation or the server is not
responding.
Can anyone help with this??? Why error's with LATER versions of your
software?

Nov 19 '05 #2
SQL server is running. I can test with my other laptop - 2K version. All is
well there. It does appear to be latest OS - I've also reviewed other posts
by others users - but noone has answered questions.

Futher, everything fine on SQL - running for every app - again, including
other 2K OS laptop - and in development mode there with no problem.
Basically the new XP SP2 has issues - but I'm not sure where to fix.

"TJS" wrote:
seems like the sql server is not responding,. doesn't seem like it has
anything to do with the OS.

Check to make sure SQL server is running and name of the server is same as
in connection code
"DavidS" <Da****@discuss ions.microsoft. com> wrote in message
news:A1******** *************** ***********@mic rosoft.com...
Have Visual Studio.NET installed on MS 2000 Professional OS laptop. No
issue
ever with web development and SQL connections.
Purchased new laptop with XP Professional SP2!!!!!!!! & Visual Studio.NET
installed.
Nothing but headaches. Continually getting
System.Data.Sql Client.SqlExcep tion : Timeout expired message - The timeout
period elapsed prior to completion of the operation or the server is not
responding.
Can anyone help with this??? Why error's with LATER versions of your
software?


Nov 19 '05 #3
PB
<<Basically the new XP SP2 has issues >>

Maybe so, but not necessarily relevant to your errors. I migrated from 2k to
XP SP2 with no issues at all - and did so on multiple development machines
(laptop, desktop). Many other developers in this group report using XP SP2
with NO problems.

As long as you are concluding that XP SP2 is "the problem" then it may take
you more time to figure out what is really causing "the problem". There are
potentially many many differences between your 2k machine and your XP
machine - the OS is just one of those many differences.

Maybe we could help you more if you were to describe specifically what your
setup is. Do you have SQL Server 2000 installed on the local machine? When
you say you can test with other laptop - 2K version - are you saying that
that machine is connecting to the XP machine and choking? If os, then XP'
firewall may need to be opened up a bit. No one can reasonably suggest you
look at the firewall NOR ANY other potential configuration issues without
knowing more about your specific setup. If it all works on your 2K machine
(everything is installed locally) but not on the XP machine (with everthing
installed locally), then its time to look at similarities and differences
between specific configuration settings - and not just conclude that the
OS - which is the most unlikely culprit here - is "the" problem.

Help us help you - and we will.

"DavidS" <Da****@discuss ions.microsoft. com> wrote in message
news:00******** *************** ***********@mic rosoft.com...
SQL server is running. I can test with my other laptop - 2K version. All
is
well there. It does appear to be latest OS - I've also reviewed other
posts
by others users - but noone has answered questions.

Futher, everything fine on SQL - running for every app - again, including
other 2K OS laptop - and in development mode there with no problem.
Basically the new XP SP2 has issues - but I'm not sure where to fix.

"TJS" wrote:
seems like the sql server is not responding,. doesn't seem like it has
anything to do with the OS.

Check to make sure SQL server is running and name of the server is same
as
in connection code
"DavidS" <Da****@discuss ions.microsoft. com> wrote in message
news:A1******** *************** ***********@mic rosoft.com...
> Have Visual Studio.NET installed on MS 2000 Professional OS laptop. No
> issue
> ever with web development and SQL connections.
> Purchased new laptop with XP Professional SP2!!!!!!!! & Visual
> Studio.NET
> installed.
> Nothing but headaches. Continually getting
> System.Data.Sql Client.SqlExcep tion : Timeout expired message - The
> timeout
> period elapsed prior to completion of the operation or the server is
> not
> responding.
> Can anyone help with this??? Why error's with LATER versions of your
> software?


Nov 19 '05 #4
WJ
By default, XP pro. Service Pack# 2 locks down your system. You will have to
do the followings:

1. Install IIS-5 and enable it.
2. Check PFW (disable it first, then gradually block certain ports).
3. Install .NetFW 1.1 and hotfixes (sp2 should have done that for you
already).
4. Enable ASPNet account if it is not.
5. Check all WinXP Services.
6. Install VS.Net.
7. Grant ASPNET account to SQL Server if you plan Windows Integrated and
allow anonymous.

I am running IBM LapTop with service Pack 2 on XP Pro. edition, SQL Server
developer edition with VS.Net 2k3 and I have no problem at all.

John
Nov 19 '05 #5
I almost was ready to look @ working with UNIX environment - but that's
statement only out of frustration. First, THANK YOU for responding. Next,
I'll answer all your questions too - and hopefully we can get solution here
to fix this for our development environment.

1) SQL 200 Server is not local - it's on separate server all by itself. I
have two laptops - both with Visual Studio.NET that I've installed. MDAC
components 2.6 is what is on laptop I believe. I've never had connection
issue to SQL databases here - very rare to get timeouts.
2) I've also installed Visual Studio.NET on 2000 server for development
server - and not issue there. MDAC 2.6 I believe is installed there. I've
installed IIS and just about everything here - and not issue. Never SQL
timeouts.
3) MDAC 2.8 is installed on 2nd laptop with Windows XP SP2. I've also
installed Visual Studio.NET here (I believe this is default with OS).
Everything works great but SQL doesn't connect & popup issue - BUT for now
lets ignore popup issue. Once in a blue-moon I can connect to SQL server -
but 98% of time it times out or simply doesn't connect. I have 20 second
default for connection string (changed to 30, 60, etc... and doesn't help) as
on Windows 2000 OS laptop. I agree there are many differences with both OS's
- DLL's are one variation, MDAC is most obvious that I see @ this time. I've
downloaded Microsoft Product Support Reporting Tools - to review what's here
too - after researching on your knowledge base.
4) Currently, I'm going to formulate more information - but what's best way
to give you what you need. My initial objective is NOT to conclude OS - but
trust me - all that's been done here was to install SP2 or upgrade of XP from
Microsoft. Next, I've completed the install of Visual Studio.NET like I've
done for 3 other computers - without issue. Again - MDAC - I've research
this myself - since it's relavent to SQL connect objects.

What would you need from me first - to check/review
similarities/dissimilarities .

Thank you kindly.

"PB" wrote:
<<Basically the new XP SP2 has issues >>

Maybe so, but not necessarily relevant to your errors. I migrated from 2k to
XP SP2 with no issues at all - and did so on multiple development machines
(laptop, desktop). Many other developers in this group report using XP SP2
with NO problems.

As long as you are concluding that XP SP2 is "the problem" then it may take
you more time to figure out what is really causing "the problem". There are
potentially many many differences between your 2k machine and your XP
machine - the OS is just one of those many differences.

Maybe we could help you more if you were to describe specifically what your
setup is. Do you have SQL Server 2000 installed on the local machine? When
you say you can test with other laptop - 2K version - are you saying that
that machine is connecting to the XP machine and choking? If os, then XP'
firewall may need to be opened up a bit. No one can reasonably suggest you
look at the firewall NOR ANY other potential configuration issues without
knowing more about your specific setup. If it all works on your 2K machine
(everything is installed locally) but not on the XP machine (with everthing
installed locally), then its time to look at similarities and differences
between specific configuration settings - and not just conclude that the
OS - which is the most unlikely culprit here - is "the" problem.

Help us help you - and we will.

"DavidS" <Da****@discuss ions.microsoft. com> wrote in message
news:00******** *************** ***********@mic rosoft.com...
SQL server is running. I can test with my other laptop - 2K version. All
is
well there. It does appear to be latest OS - I've also reviewed other
posts
by others users - but noone has answered questions.

Futher, everything fine on SQL - running for every app - again, including
other 2K OS laptop - and in development mode there with no problem.
Basically the new XP SP2 has issues - but I'm not sure where to fix.

"TJS" wrote:
seems like the sql server is not responding,. doesn't seem like it has
anything to do with the OS.

Check to make sure SQL server is running and name of the server is same
as
in connection code
"DavidS" <Da****@discuss ions.microsoft. com> wrote in message
news:A1******** *************** ***********@mic rosoft.com...
> Have Visual Studio.NET installed on MS 2000 Professional OS laptop. No
> issue
> ever with web development and SQL connections.
> Purchased new laptop with XP Professional SP2!!!!!!!! & Visual
> Studio.NET
> installed.
> Nothing but headaches. Continually getting
> System.Data.Sql Client.SqlExcep tion : Timeout expired message - The
> timeout
> period elapsed prior to completion of the operation or the server is
> not
> responding.
> Can anyone help with this??? Why error's with LATER versions of your
> software?


Nov 19 '05 #6
PB
Well, for starters, I believe MDAC is unnecessary for .NET applications - as
ADO.NET has its own SQL Server provider for data access. The only reason I
could think of off hand for installing MDAC is for any old COM applications
that may need it.

So, when you say you are connecting to SQL Server, are you doing so from an
ASP.NET Web application? or from some COM-based application? If from .NET -
then what does your connection string and connection object look like? Are
you defining them in code? If so, lets have a look.

Also, which version of Visual Studio .NET? 2003? As long as you are setting
up a new development environment for new projects that were not based on any
prior version of .NET, then you really should be using .NET Framework 1.1
(which installs with VS.NET 2003).

I personally have worked extensively with many prior versions of MDAC - and
honestly since switching to .NET development I've never had to deal with
MDAC (and good riddance!).

Finally (for now), this news group is run by Microsoft, but most of the
people who are posting here are NOT Microsoft employees. We are mostly
people just like yourself figuring out how to make all this stuff work and
helping each other out.

-HTH

"DavidS" <Da****@discuss ions.microsoft. com> wrote in message
news:A6******** *************** ***********@mic rosoft.com...
I almost was ready to look @ working with UNIX environment - but that's
statement only out of frustration. First, THANK YOU for responding.
Next,
I'll answer all your questions too - and hopefully we can get solution
here
to fix this for our development environment.

1) SQL 200 Server is not local - it's on separate server all by itself. I
have two laptops - both with Visual Studio.NET that I've installed. MDAC
components 2.6 is what is on laptop I believe. I've never had connection
issue to SQL databases here - very rare to get timeouts.
2) I've also installed Visual Studio.NET on 2000 server for development
server - and not issue there. MDAC 2.6 I believe is installed there.
I've
installed IIS and just about everything here - and not issue. Never SQL
timeouts.
3) MDAC 2.8 is installed on 2nd laptop with Windows XP SP2. I've also
installed Visual Studio.NET here (I believe this is default with OS).
Everything works great but SQL doesn't connect & popup issue - BUT for now
lets ignore popup issue. Once in a blue-moon I can connect to SQL
server -
but 98% of time it times out or simply doesn't connect. I have 20 second
default for connection string (changed to 30, 60, etc... and doesn't help)
as
on Windows 2000 OS laptop. I agree there are many differences with both
OS's
- DLL's are one variation, MDAC is most obvious that I see @ this time.
I've
downloaded Microsoft Product Support Reporting Tools - to review what's
here
too - after researching on your knowledge base.
4) Currently, I'm going to formulate more information - but what's best
way
to give you what you need. My initial objective is NOT to conclude OS -
but
trust me - all that's been done here was to install SP2 or upgrade of XP
from
Microsoft. Next, I've completed the install of Visual Studio.NET like
I've
done for 3 other computers - without issue. Again - MDAC - I've research
this myself - since it's relavent to SQL connect objects.

What would you need from me first - to check/review
similarities/dissimilarities .

Thank you kindly.

"PB" wrote:
<<Basically the new XP SP2 has issues >>

Maybe so, but not necessarily relevant to your errors. I migrated from 2k
to
XP SP2 with no issues at all - and did so on multiple development
machines
(laptop, desktop). Many other developers in this group report using XP
SP2
with NO problems.

As long as you are concluding that XP SP2 is "the problem" then it may
take
you more time to figure out what is really causing "the problem". There
are
potentially many many differences between your 2k machine and your XP
machine - the OS is just one of those many differences.

Maybe we could help you more if you were to describe specifically what
your
setup is. Do you have SQL Server 2000 installed on the local machine?
When
you say you can test with other laptop - 2K version - are you saying that
that machine is connecting to the XP machine and choking? If os, then XP'
firewall may need to be opened up a bit. No one can reasonably suggest
you
look at the firewall NOR ANY other potential configuration issues without
knowing more about your specific setup. If it all works on your 2K
machine
(everything is installed locally) but not on the XP machine (with
everthing
installed locally), then its time to look at similarities and differences
between specific configuration settings - and not just conclude that the
OS - which is the most unlikely culprit here - is "the" problem.

Help us help you - and we will.

"DavidS" <Da****@discuss ions.microsoft. com> wrote in message
news:00******** *************** ***********@mic rosoft.com...
> SQL server is running. I can test with my other laptop - 2K version.
> All
> is
> well there. It does appear to be latest OS - I've also reviewed other
> posts
> by others users - but noone has answered questions.
>
> Futher, everything fine on SQL - running for every app - again,
> including
> other 2K OS laptop - and in development mode there with no problem.
> Basically the new XP SP2 has issues - but I'm not sure where to fix.
>
> "TJS" wrote:
>
>> seems like the sql server is not responding,. doesn't seem like it
>> has
>> anything to do with the OS.
>>
>> Check to make sure SQL server is running and name of the server is
>> same
>> as
>> in connection code
>>
>>
>> "DavidS" <Da****@discuss ions.microsoft. com> wrote in message
>> news:A1******** *************** ***********@mic rosoft.com...
>> > Have Visual Studio.NET installed on MS 2000 Professional OS laptop.
>> > No
>> > issue
>> > ever with web development and SQL connections.
>> > Purchased new laptop with XP Professional SP2!!!!!!!! & Visual
>> > Studio.NET
>> > installed.
>> > Nothing but headaches. Continually getting
>> > System.Data.Sql Client.SqlExcep tion : Timeout expired message - The
>> > timeout
>> > period elapsed prior to completion of the operation or the server is
>> > not
>> > responding.
>> > Can anyone help with this??? Why error's with LATER versions of
>> > your
>> > software?
>>
>>
>>


Nov 19 '05 #7
Note: 2) - what I mean here is I have another server (not SQL 2000 server)
that is development server with Visual Studio.NET. IIS installed here too.
No problems.

Problem is just XP SP2 laptop as identified above. Again, I'll try
reinstalling IIS again - I believe it's 5.1 on the XP Laptop - but 5.0 on
Windows 2000 Pro Laptop - that's the only other difference I see - but I took
latest from MS.

"DavidS" wrote:
I almost was ready to look @ working with UNIX environment - but that's
statement only out of frustration. First, THANK YOU for responding. Next,
I'll answer all your questions too - and hopefully we can get solution here
to fix this for our development environment.

1) SQL 200 Server is not local - it's on separate server all by itself. I
have two laptops - both with Visual Studio.NET that I've installed. MDAC
components 2.6 is what is on laptop I believe. I've never had connection
issue to SQL databases here - very rare to get timeouts.
2) I've also installed Visual Studio.NET on 2000 server for development
server - and not issue there. MDAC 2.6 I believe is installed there. I've
installed IIS and just about everything here - and not issue. Never SQL
timeouts.
3) MDAC 2.8 is installed on 2nd laptop with Windows XP SP2. I've also
installed Visual Studio.NET here (I believe this is default with OS).
Everything works great but SQL doesn't connect & popup issue - BUT for now
lets ignore popup issue. Once in a blue-moon I can connect to SQL server -
but 98% of time it times out or simply doesn't connect. I have 20 second
default for connection string (changed to 30, 60, etc... and doesn't help) as
on Windows 2000 OS laptop. I agree there are many differences with both OS's
- DLL's are one variation, MDAC is most obvious that I see @ this time. I've
downloaded Microsoft Product Support Reporting Tools - to review what's here
too - after researching on your knowledge base.
4) Currently, I'm going to formulate more information - but what's best way
to give you what you need. My initial objective is NOT to conclude OS - but
trust me - all that's been done here was to install SP2 or upgrade of XP from
Microsoft. Next, I've completed the install of Visual Studio.NET like I've
done for 3 other computers - without issue. Again - MDAC - I've research
this myself - since it's relavent to SQL connect objects.

What would you need from me first - to check/review
similarities/dissimilarities .

Thank you kindly.

"PB" wrote:
<<Basically the new XP SP2 has issues >>

Maybe so, but not necessarily relevant to your errors. I migrated from 2k to
XP SP2 with no issues at all - and did so on multiple development machines
(laptop, desktop). Many other developers in this group report using XP SP2
with NO problems.

As long as you are concluding that XP SP2 is "the problem" then it may take
you more time to figure out what is really causing "the problem". There are
potentially many many differences between your 2k machine and your XP
machine - the OS is just one of those many differences.

Maybe we could help you more if you were to describe specifically what your
setup is. Do you have SQL Server 2000 installed on the local machine? When
you say you can test with other laptop - 2K version - are you saying that
that machine is connecting to the XP machine and choking? If os, then XP'
firewall may need to be opened up a bit. No one can reasonably suggest you
look at the firewall NOR ANY other potential configuration issues without
knowing more about your specific setup. If it all works on your 2K machine
(everything is installed locally) but not on the XP machine (with everthing
installed locally), then its time to look at similarities and differences
between specific configuration settings - and not just conclude that the
OS - which is the most unlikely culprit here - is "the" problem.

Help us help you - and we will.

"DavidS" <Da****@discuss ions.microsoft. com> wrote in message
news:00******** *************** ***********@mic rosoft.com...
SQL server is running. I can test with my other laptop - 2K version. All
is
well there. It does appear to be latest OS - I've also reviewed other
posts
by others users - but noone has answered questions.

Futher, everything fine on SQL - running for every app - again, including
other 2K OS laptop - and in development mode there with no problem.
Basically the new XP SP2 has issues - but I'm not sure where to fix.

"TJS" wrote:

> seems like the sql server is not responding,. doesn't seem like it has
> anything to do with the OS.
>
> Check to make sure SQL server is running and name of the server is same
> as
> in connection code
>
>
> "DavidS" <Da****@discuss ions.microsoft. com> wrote in message
> news:A1******** *************** ***********@mic rosoft.com...
> > Have Visual Studio.NET installed on MS 2000 Professional OS laptop. No
> > issue
> > ever with web development and SQL connections.
> > Purchased new laptop with XP Professional SP2!!!!!!!! & Visual
> > Studio.NET
> > installed.
> > Nothing but headaches. Continually getting
> > System.Data.Sql Client.SqlExcep tion : Timeout expired message - The
> > timeout
> > period elapsed prior to completion of the operation or the server is
> > not
> > responding.
> > Can anyone help with this??? Why error's with LATER versions of your
> > software?
>
>
>


Nov 19 '05 #8
Doing so from ASP.NET web application. Using Visual Studio.NET 2003 -
Version 7.1.3088. Microsoft .NET Framework 1.1 (1.1.4322 SP1) it says for XP
SP2 OS. Using Visual Studio.NET 2003 - Version 7.1.3088. Microsoft .NET
Framework 1.1 (1.1.4322) NO SP1 for 2000 Pro OS.

I think MDAC Applies in this instance. @ Least as I understand it's the
core for SQL, Ole, and ODBC connections.
"PB" wrote:
Well, for starters, I believe MDAC is unnecessary for .NET applications - as
ADO.NET has its own SQL Server provider for data access. The only reason I
could think of off hand for installing MDAC is for any old COM applications
that may need it.

So, when you say you are connecting to SQL Server, are you doing so from an
ASP.NET Web application? or from some COM-based application? If from .NET -
then what does your connection string and connection object look like? Are
you defining them in code? If so, lets have a look.

Also, which version of Visual Studio .NET? 2003? As long as you are setting
up a new development environment for new projects that were not based on any
prior version of .NET, then you really should be using .NET Framework 1.1
(which installs with VS.NET 2003).

I personally have worked extensively with many prior versions of MDAC - and
honestly since switching to .NET development I've never had to deal with
MDAC (and good riddance!).

Finally (for now), this news group is run by Microsoft, but most of the
people who are posting here are NOT Microsoft employees. We are mostly
people just like yourself figuring out how to make all this stuff work and
helping each other out.

-HTH

"DavidS" <Da****@discuss ions.microsoft. com> wrote in message
news:A6******** *************** ***********@mic rosoft.com...
I almost was ready to look @ working with UNIX environment - but that's
statement only out of frustration. First, THANK YOU for responding.
Next,
I'll answer all your questions too - and hopefully we can get solution
here
to fix this for our development environment.

1) SQL 200 Server is not local - it's on separate server all by itself. I
have two laptops - both with Visual Studio.NET that I've installed. MDAC
components 2.6 is what is on laptop I believe. I've never had connection
issue to SQL databases here - very rare to get timeouts.
2) I've also installed Visual Studio.NET on 2000 server for development
server - and not issue there. MDAC 2.6 I believe is installed there.
I've
installed IIS and just about everything here - and not issue. Never SQL
timeouts.
3) MDAC 2.8 is installed on 2nd laptop with Windows XP SP2. I've also
installed Visual Studio.NET here (I believe this is default with OS).
Everything works great but SQL doesn't connect & popup issue - BUT for now
lets ignore popup issue. Once in a blue-moon I can connect to SQL
server -
but 98% of time it times out or simply doesn't connect. I have 20 second
default for connection string (changed to 30, 60, etc... and doesn't help)
as
on Windows 2000 OS laptop. I agree there are many differences with both
OS's
- DLL's are one variation, MDAC is most obvious that I see @ this time.
I've
downloaded Microsoft Product Support Reporting Tools - to review what's
here
too - after researching on your knowledge base.
4) Currently, I'm going to formulate more information - but what's best
way
to give you what you need. My initial objective is NOT to conclude OS -
but
trust me - all that's been done here was to install SP2 or upgrade of XP
from
Microsoft. Next, I've completed the install of Visual Studio.NET like
I've
done for 3 other computers - without issue. Again - MDAC - I've research
this myself - since it's relavent to SQL connect objects.

What would you need from me first - to check/review
similarities/dissimilarities .

Thank you kindly.

"PB" wrote:
<<Basically the new XP SP2 has issues >>

Maybe so, but not necessarily relevant to your errors. I migrated from 2k
to
XP SP2 with no issues at all - and did so on multiple development
machines
(laptop, desktop). Many other developers in this group report using XP
SP2
with NO problems.

As long as you are concluding that XP SP2 is "the problem" then it may
take
you more time to figure out what is really causing "the problem". There
are
potentially many many differences between your 2k machine and your XP
machine - the OS is just one of those many differences.

Maybe we could help you more if you were to describe specifically what
your
setup is. Do you have SQL Server 2000 installed on the local machine?
When
you say you can test with other laptop - 2K version - are you saying that
that machine is connecting to the XP machine and choking? If os, then XP'
firewall may need to be opened up a bit. No one can reasonably suggest
you
look at the firewall NOR ANY other potential configuration issues without
knowing more about your specific setup. If it all works on your 2K
machine
(everything is installed locally) but not on the XP machine (with
everthing
installed locally), then its time to look at similarities and differences
between specific configuration settings - and not just conclude that the
OS - which is the most unlikely culprit here - is "the" problem.

Help us help you - and we will.

"DavidS" <Da****@discuss ions.microsoft. com> wrote in message
news:00******** *************** ***********@mic rosoft.com...
> SQL server is running. I can test with my other laptop - 2K version.
> All
> is
> well there. It does appear to be latest OS - I've also reviewed other
> posts
> by others users - but noone has answered questions.
>
> Futher, everything fine on SQL - running for every app - again,
> including
> other 2K OS laptop - and in development mode there with no problem.
> Basically the new XP SP2 has issues - but I'm not sure where to fix.
>
> "TJS" wrote:
>
>> seems like the sql server is not responding,. doesn't seem like it
>> has
>> anything to do with the OS.
>>
>> Check to make sure SQL server is running and name of the server is
>> same
>> as
>> in connection code
>>
>>
>> "DavidS" <Da****@discuss ions.microsoft. com> wrote in message
>> news:A1******** *************** ***********@mic rosoft.com...
>> > Have Visual Studio.NET installed on MS 2000 Professional OS laptop.
>> > No
>> > issue
>> > ever with web development and SQL connections.
>> > Purchased new laptop with XP Professional SP2!!!!!!!! & Visual
>> > Studio.NET
>> > installed.
>> > Nothing but headaches. Continually getting
>> > System.Data.Sql Client.SqlExcep tion : Timeout expired message - The
>> > timeout
>> > period elapsed prior to completion of the operation or the server is
>> > not
>> > responding.
>> > Can anyone help with this??? Why error's with LATER versions of
>> > your
>> > software?
>>
>>
>>


Nov 19 '05 #9
Connect String -------------

Server=<server name>;database= <database
name>;uid=<uid> ;pwd=<password> ;connect timeout=30;pool ing=true

Never problem -

"PB" wrote:
Well, for starters, I believe MDAC is unnecessary for .NET applications - as
ADO.NET has its own SQL Server provider for data access. The only reason I
could think of off hand for installing MDAC is for any old COM applications
that may need it.

So, when you say you are connecting to SQL Server, are you doing so from an
ASP.NET Web application? or from some COM-based application? If from .NET -
then what does your connection string and connection object look like? Are
you defining them in code? If so, lets have a look.

Also, which version of Visual Studio .NET? 2003? As long as you are setting
up a new development environment for new projects that were not based on any
prior version of .NET, then you really should be using .NET Framework 1.1
(which installs with VS.NET 2003).

I personally have worked extensively with many prior versions of MDAC - and
honestly since switching to .NET development I've never had to deal with
MDAC (and good riddance!).

Finally (for now), this news group is run by Microsoft, but most of the
people who are posting here are NOT Microsoft employees. We are mostly
people just like yourself figuring out how to make all this stuff work and
helping each other out.

-HTH

"DavidS" <Da****@discuss ions.microsoft. com> wrote in message
news:A6******** *************** ***********@mic rosoft.com...
I almost was ready to look @ working with UNIX environment - but that's
statement only out of frustration. First, THANK YOU for responding.
Next,
I'll answer all your questions too - and hopefully we can get solution
here
to fix this for our development environment.

1) SQL 200 Server is not local - it's on separate server all by itself. I
have two laptops - both with Visual Studio.NET that I've installed. MDAC
components 2.6 is what is on laptop I believe. I've never had connection
issue to SQL databases here - very rare to get timeouts.
2) I've also installed Visual Studio.NET on 2000 server for development
server - and not issue there. MDAC 2.6 I believe is installed there.
I've
installed IIS and just about everything here - and not issue. Never SQL
timeouts.
3) MDAC 2.8 is installed on 2nd laptop with Windows XP SP2. I've also
installed Visual Studio.NET here (I believe this is default with OS).
Everything works great but SQL doesn't connect & popup issue - BUT for now
lets ignore popup issue. Once in a blue-moon I can connect to SQL
server -
but 98% of time it times out or simply doesn't connect. I have 20 second
default for connection string (changed to 30, 60, etc... and doesn't help)
as
on Windows 2000 OS laptop. I agree there are many differences with both
OS's
- DLL's are one variation, MDAC is most obvious that I see @ this time.
I've
downloaded Microsoft Product Support Reporting Tools - to review what's
here
too - after researching on your knowledge base.
4) Currently, I'm going to formulate more information - but what's best
way
to give you what you need. My initial objective is NOT to conclude OS -
but
trust me - all that's been done here was to install SP2 or upgrade of XP
from
Microsoft. Next, I've completed the install of Visual Studio.NET like
I've
done for 3 other computers - without issue. Again - MDAC - I've research
this myself - since it's relavent to SQL connect objects.

What would you need from me first - to check/review
similarities/dissimilarities .

Thank you kindly.

"PB" wrote:
<<Basically the new XP SP2 has issues >>

Maybe so, but not necessarily relevant to your errors. I migrated from 2k
to
XP SP2 with no issues at all - and did so on multiple development
machines
(laptop, desktop). Many other developers in this group report using XP
SP2
with NO problems.

As long as you are concluding that XP SP2 is "the problem" then it may
take
you more time to figure out what is really causing "the problem". There
are
potentially many many differences between your 2k machine and your XP
machine - the OS is just one of those many differences.

Maybe we could help you more if you were to describe specifically what
your
setup is. Do you have SQL Server 2000 installed on the local machine?
When
you say you can test with other laptop - 2K version - are you saying that
that machine is connecting to the XP machine and choking? If os, then XP'
firewall may need to be opened up a bit. No one can reasonably suggest
you
look at the firewall NOR ANY other potential configuration issues without
knowing more about your specific setup. If it all works on your 2K
machine
(everything is installed locally) but not on the XP machine (with
everthing
installed locally), then its time to look at similarities and differences
between specific configuration settings - and not just conclude that the
OS - which is the most unlikely culprit here - is "the" problem.

Help us help you - and we will.

"DavidS" <Da****@discuss ions.microsoft. com> wrote in message
news:00******** *************** ***********@mic rosoft.com...
> SQL server is running. I can test with my other laptop - 2K version.
> All
> is
> well there. It does appear to be latest OS - I've also reviewed other
> posts
> by others users - but noone has answered questions.
>
> Futher, everything fine on SQL - running for every app - again,
> including
> other 2K OS laptop - and in development mode there with no problem.
> Basically the new XP SP2 has issues - but I'm not sure where to fix.
>
> "TJS" wrote:
>
>> seems like the sql server is not responding,. doesn't seem like it
>> has
>> anything to do with the OS.
>>
>> Check to make sure SQL server is running and name of the server is
>> same
>> as
>> in connection code
>>
>>
>> "DavidS" <Da****@discuss ions.microsoft. com> wrote in message
>> news:A1******** *************** ***********@mic rosoft.com...
>> > Have Visual Studio.NET installed on MS 2000 Professional OS laptop.
>> > No
>> > issue
>> > ever with web development and SQL connections.
>> > Purchased new laptop with XP Professional SP2!!!!!!!! & Visual
>> > Studio.NET
>> > installed.
>> > Nothing but headaches. Continually getting
>> > System.Data.Sql Client.SqlExcep tion : Timeout expired message - The
>> > timeout
>> > period elapsed prior to completion of the operation or the server is
>> > not
>> > responding.
>> > Can anyone help with this??? Why error's with LATER versions of
>> > your
>> > software?
>>
>>
>>


Nov 19 '05 #10

This thread has been closed and replies have been disabled. Please start a new discussion.

Similar topics

22
2251
by: Rob R. Ainscough | last post by:
Sorry to hear about the job cuts and Oracle now out sourcing to India. Rob.
0
1327
by: Ramprasad | last post by:
Life is Different here, sky has no limit but you must grip it with this website, your Mirror of mind are present there. Whatever you want related to your everyday life, it can present or give information about the same, within a second, just for one click by mouse. Click here. You can get from any thing from your House, Just one click in mouse http://deysworld.bravehost.com For Food and Drink Click Here. For Latest Fashion Click Here For...
1
1611
by: leighahh | last post by:
Hi everyone i was wondering if there was a way to turn this code that is css into HTML <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> <html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en"> <head> <!-- YOUR WEBSITE TITLE --> <title>
2
3376
by: dibblm | last post by:
I'll start this hopefully simple and add code where needed or requested. Im using a combobox that bound to a DataSet. The Dataset retreives it's values from SQL. I can retreive the values fine. However only displaying (1) Column. Which is fine. Here's where it gets complicated for me. The dataset has 2 other columns that get filled. I need the resulting columns to be sent to text boxes when I select a value from the combobox. ...
0
9933
marktang
by: marktang | last post by:
ONU (Optical Network Unit) is one of the key components for providing high-speed Internet services. Its primary function is to act as an endpoint device located at the user's premises. However, people are often confused as to whether an ONU can Work As a Router. In this blog post, we’ll explore What is ONU, What Is Router, ONU & Router’s main usage, and What is the difference between ONU and Router. Let’s take a closer look ! Part I. Meaning of...
0
11114
Oralloy
by: Oralloy | last post by:
Hello folks, I am unable to find appropriate documentation on the type promotion of bit-fields when using the generalised comparison operator "<=>". The problem is that using the GNU compilers, it seems that the internal comparison operator "<=>" tries to promote arguments from unsigned to signed. This is as boiled down as I can make it. Here is my compilation command: g++-12 -std=c++20 -Wnarrowing bit_field.cpp Here is the code in...
1
10835
by: Hystou | last post by:
Overview: Windows 11 and 10 have less user interface control over operating system update behaviour than previous versions of Windows. In Windows 11 and 10, there is no way to turn off the Windows Update option using the Control Panel or Settings app; it automatically checks for updates and installs any it finds, whether you like it or not. For most users, this new feature is actually very convenient. If you want to control the update process,...
0
9563
agi2029
by: agi2029 | last post by:
Let's talk about the concept of autonomous AI software engineers and no-code agents. These AIs are designed to manage the entire lifecycle of a software development project—planning, coding, testing, and deployment—without human intervention. Imagine an AI that can take a project description, break it down, write the code, debug it, and then launch it, all on its own.... Now, this would greatly impact the work of software developers. The idea...
1
7960
isladogs
by: isladogs | last post by:
The next Access Europe User Group meeting will be on Wednesday 1 May 2024 starting at 18:00 UK time (6PM UTC+1) and finishing by 19:30 (7.30PM). In this session, we are pleased to welcome a new presenter, Adolph Dupré who will be discussing some powerful techniques for using class modules. He will explain when you may want to use classes instead of User Defined Types (UDT). For example, to manage the data in unbound forms. Adolph will...
0
5982
by: adsilva | last post by:
A Windows Forms form does not have the event Unload, like VB6. What one acts like?
1
4605
by: 6302768590 | last post by:
Hai team i want code for transfer the data from one system to another through IP address by using C# our system has to for every 5mins then we have to update the data what the data is updated we have to send another system
2
4205
muto222
by: muto222 | last post by:
How can i add a mobile payment intergratation into php mysql website.
3
3230
bsmnconsultancy
by: bsmnconsultancy | last post by:
In today's digital era, a well-designed website is crucial for businesses looking to succeed. Whether you're a small business owner or a large corporation in Toronto, having a strong online presence can significantly impact your brand's success. BSMN Consultancy, a leader in Website Development in Toronto offers valuable insights into creating effective websites that not only look great but also perform exceptionally well. In this comprehensive...

By using Bytes.com and it's services, you agree to our Privacy Policy and Terms of Use.

To disable or enable advertisements and analytics tracking please visit the manage ads & tracking page.