Re: Any help here???

I'm using ADO.NET - specific classes used were
1) System.Data.SqlClient - connection to Microsoft SQL Server - I also have
version 08.00.0384 of SQL Server 2000
2) System.Data.OleDb - connection to other Access Databases
3) System.Data.Odbc - used this likewise.
For discussion, like to simply stay with ADO.NET - System.Data.SqlClient.

Next, I apologize for discussion concerning MDAC - I was 100% sure how this
was used - but in past - system would advise me I needed latest during
debugging. I've also researched article from Microsoft saying when you
troubleshoot SQL Server connectivity issues - you should investigate the MDAC
version on the client, not on the server. Article was MDAC Technical Article
Pg 3 - Installation Versions and SQL Server Versions. I just thought it
might apply there.

Finally, since issue now is completely understood as ADO.NET - SQL provider,
I'd like to move to next issue. What could be causing no connects during
open operation?

Thanks always,

"PB" wrote:

> <<I think MDAC Applies in this instance>>
>
> No way. ADO.NET has an entirely new SQL data provider. OLE is old-school
> COM, ODBC is totally unnecessary here and even undesirable as ADO.NET's SQL
> data provider is optimized for SQL Server. Show us how you are trying to
> connect. Show us your code.
>
> I'd sure hate to be going off into left field here - all I'm thinking is
> that you are installing MDAC which is totally unnecessary. Put another way,
> I've never had any SQL Server connectivity problems since I've switch to
> ..NET - and I've never installed MDAC or tried to use ODBC. Furthermore, I've
> never even heard of anyone trying to install or use MDAC from a .NET
> application when trying to connect to SQL Server.
>
> ADO.NET is not simply the latest version of the original ADO classic (which
> necessitated the installation of MDAC for COM applications). ADO.NET is a
> whole new thing.
>
> -HTH
>
>
>
> "DavidS" <DavidS@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
> news:AA1368BB-8633-4AC3-B41B-BC0E1650106D@xxxxxxxxxxxxxxxx
> > 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" <DavidS@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
> >> news:A6DCE8BC-FF8C-4B4D-8800-9A9F51D1AB0C@xxxxxxxxxxxxxxxx
> >> >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" <DavidS@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
> >> >> news:00CBD93C-A057-4F4E-A3BC-F3598D6AF9AC@xxxxxxxxxxxxxxxx
> >> >> > 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" <DavidS@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
> >> >> >> news:A16D9908-6EED-49A3-89BB-E0335A4C5378@xxxxxxxxxxxxxxxx
> >> >> >> > 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.SqlClient.SqlException : 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?
> >> >> >>
> >> >> >>
> >> >> >>
> >> >>
> >> >>
> >> >>
> >>
> >>
> >>
>
>
>
.

Loading